How DSALTA integrates with Netlify — data collected, setup guide, and automated compliance checks.
Overview
How to connect
Automated checks
Useful links
DSALTA connects to Netlify using read-only API access to collect compliance evidence automatically. Data feeds into your Data Library modules.
Read-only access. DSALTA never modifies, creates, or deletes resources in your Netlify environment.
DSALTA collects this integration’s data when you connect it — you can refresh it at any time with Sync from integrations on the Integrations page. The compliance checks below re-run once a day at 02:00 America/New_York.
DSALTA reads the Netlify user roster — names, emails and team roles, which appears on your Access page; and your Netlify resources, which appear on your Inventory page. Netlify’s team-members API returns no account status, so every member is listed as Active.It calls these Netlify endpoints:
/accounts
/{accountSlug}/members
/sites
Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Netlify environment.
There is no Reconnect button. Open Integrations → Connected, click Manage on the Netlify card, and check the Status tab — it shows either Connected and working properly or Connection issues detected. To restore a broken connection you must Disconnect and connect again, which permanently deletes the data and tests collected from Netlify. This usually happens when API tokens expire.
Data is not syncing
Verify the connected account still holds the permissions listed under Before you begin. Then open Integrations in the DSALTA sidebar, stay on the Connected tab, and click Sync from integrations at the top right. That button refreshes every connected integration at once — there is no per-integration sync control.
Create a Netlify personal access token and paste it below to connect.Before you begin
Netlify team with Owner/admin access
You will need:
Field
Where to find it
Example
Netlify Personal Access Token
Create one at Netlify → User settings → Applications → Personal access tokens → New access token. · Open
nfp_…
1
Start in DSALTA
Open Integrations in the DSALTA sidebar, find Netlify, and click Connect to open the connect panel. Leave it open — it lists every value you need, and you create those in the steps below.
2
Integrating Netlify with DSALTA means
DSALTA will only be able to read your Netlify team members (access reviews) and your sites (inventory) for security compliance.DSALTA uses read-only access and never modifies your Netlify sites, teams, or resources.A personal access token acts as the person who created it, so DSALTA walks every team that account belongs to — GET /accounts, then /{team_slug}/members for each — and syncs their members and sites. Netlify paginates both lists at 100 items per page and DSALTA reads only the first page, so a team with more than 100 members or more than 100 sites arrives truncated on the Access and Inventory pages — and a truncated Access page also skews the two access checks. If the creator is in several teams, expect members and sites from all of them on the Access and Inventory pages; if you want one team only, create the token from an account that belongs to just that team.
3
Create a Personal Access Token
Sign in to Netlify, then follow these steps:
Go to User settings → Applications → OAuth, then scroll to the Personal access tokens section.
Click New access token.
Enter a name (for example DSALTA) and choose an expiration.
Click Generate token, then copy it immediately — it’s shown only once.
Create the token as a Team Owner or admin so DSALTA can see every member of the team.
If your Netlify team requires SAML SSO, tick Allow access to my SAML-based Netlify team on the New access token form — and be signed in to that team with SSO when you create it. Netlify: “If your team requires SAML SSO login, your personal access tokens will be denied access to the team by default. You can grant access when generating a new token, but you must be logged in to the team with SSO to do so.” Miss it and DSALTA still connects, but the Access page stays empty and no sites reach Inventory.
Create the token from an account that will outlive this setup, and note the expiry you chose. Netlify: “If you reset your Netlify password, all personal access tokens and OAuth tokens created before the reset will be permanently invalidated.” A password reset, an expiry date passing, or that person leaving the team all break the connection — and since there is no Reconnect button, recovery means Disconnect (which permanently deletes the evidence and tests collected from Netlify) plus a fresh connect with a new token.
4
Enter your token
Paste the Personal Access Token you copied and click Connect.Personal Access Token — Example: nfp_xxxxxxxxxxxx
DSALTA validates the credential when you click Connect. On success the integration moves to the Connected tab, and Manage → Status reads Connected and working properly. Checks begin reporting after the first sync.
If the connection is rejected. Invalid token or insufficient permissions.The on-screen message is generic — see Connection error messages.
Each check below re-runs once a day, at 02:00 America/New_York, while this integration is connected. Click any check for step-by-step remediation guidance.
.png?fit=max&auto=format&n=tsMQJyneJ1xquFUo&q=85&s=4d401cc03b547d99b6f75a6bd170c334)
