Skip to main content
Connect Typeform with a read-only personal access token to sync workspace members with their roles, workspaces, and forms, and run access reviews. Read-only. Data feeds into your Access accounts and Inventory pages.
Read-only access. DSALTA only reads data from this integration. It never creates, modifies, or deletes anything in your environment, and every remediation step is performed by your team directly in the third-party product.
What you’ll see. The Access page lists the members of every Typeform workspace the token can see, combined into one roster: a person who sits in several workspaces appears once, with their roles from each workspace joined in the role column (Owner or Member, or Member when Typeform reports no role). Each row shows the member’s name, or their email address when Typeform carries no name. Rows whose member type is anything other than user are left out; a collaborator invited into a shared workspace is listed like any other member. Typeform reports no account status or join date, so every row is shown as Active and stamped with the date of the sync. Typeform reports no per-user MFA state, so the MFA column is blank (shown as a dash).
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.

​
What DSALTA reads

DSALTA reads the Typeform workspace rosters — names, emails and roles — which appear on your Access page; and your Typeform workspaces (form count, and whether each is the default or a shared workspace) and forms (type, public or private, the workspace they belong to and when they were last updated), which appear on your Inventory page. Forms are read best-effort after the roster and appear once you have created one. Form responses and themes are not read.It calls these Typeform endpoints on api.typeform.com (or api.eu.typeform.com when the region is set to eu):
  • /me
  • /workspaces
  • /workspaces/{id}
  • /forms
Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Typeform environment.

​
Troubleshooting

The token is invalid, or it was generated without the workspaces:read scope (or without accounts:read, which the first call needs). Typeform fixes a token’s scopes when it is generated, so a token missing one cannot be edited: delete it, generate a new one with accounts:read, forms:read and workspaces:read, and connect again. A token whose first workspace lists no members is also rejected.
A personal token only sees the workspaces its creator can see. A token generated by a member other than the organization owner covers that member’s workspaces alone, so the roster is incomplete. Generate the token as the organization owner, then disconnect and connect again. Note that disconnecting permanently deletes the data already collected from Typeform.
A token deleted from Personal tokens stops working immediately, and Typeform automatically disables a personal access token that is detected in a GitHub repository. Generate a new token, then disconnect and connect again.
Open Integrations in the DSALTA sidebar, stay on the Connected tab, and click Manage on the integration’s card. Open the Status tab: it shows either Connected and working properly or Connection issues detected.Use the Status tab, not Overview — Overview always reports Connected regardless of the real state.
On an integration-powered check, Failed normally means DSALTA was blocked rather than that you are non-compliant. Open the test, go to Source Data, and read the result code: 403 is a missing permission, 428 is a setting DSALTA still needs, 500 is a failure on DSALTA’s side.A real compliance gap shows 207 and leaves the test looking Completed. See Understanding Test Results.
Compliance checks re-run once a day at 02:00 America/New_York. To refresh sooner, open Integrations → Connected and click Sync from integrations at the top right — it refreshes every connected integration at once.
There is no Reconnect, Repair or Refresh Token button. The only repair available is to disconnect and connect again.
Disconnecting is destructive and cannot be undone. DSALTA removes the access records, inventory, vulnerabilities, code changes, incidents and device records collected from this integration, and deletes the test results tied to the connection. Export anything you still need as audit evidence first — see Integration errors.
That is expected. Configure scope is read-only — it shows what DSALTA is permitted to read, and has no Save action. To change what DSALTA can see, change the permissions on the credential in the third-party product, then disconnect and connect again.