Skip to main content
Connect Deepgram with an Admin-role API key to sync project members with their roles, projects and API keys, 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 Deepgram project the key can see, combined into one roster: a person who is a member of several projects appears once, with the scopes Deepgram reports for them joined in the role column (for example Owner, Admin or Member, or Member when Deepgram reports none). Each row shows the member’s first and last name, or their email address when Deepgram carries no name. Pending invitations are not members and are not read, and API keys belong to members rather than appearing as accounts of their own. Deepgram reports no membership status or join date, so every row is shown as Active and stamped with the date of the sync. Deepgram 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 project member rosters — names, emails and scopes — which appear on your Access page; and your Deepgram projects and the API keys in each project (the key’s name, its scopes, when it was created, when it expires or never, the project it belongs to and the email of the member who owns it — never the secret), which appear on your Inventory page. API keys are read best-effort per project after the roster. Members’ sign-in method, project invitations, models, agents, usage, balances and requests are not read.It calls these Deepgram endpoints on api.deepgram.com:
  • /v1/projects
  • /v1/projects/{project_id}/members
  • /v1/projects/{project_id}/keys
Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Deepgram environment.

​
Troubleshooting

The key was created without opening Advanced and choosing the Admin role. Such a key authenticates and lists projects but cannot read a project’s members, and DSALTA checks the members call at connect time, so it is rejected with an Admin-role remedy rather than connecting with an empty Access page. Create the key again in Settings → API Keys, click Advanced, set the role to Admin, and connect again. An invalid or deleted key is rejected too, with a hint to check the key.
A key created with an expiration date stops working when it lapses. Create a new key with Expiration set to never expire, then disconnect and connect again. Note that disconnecting permanently deletes the data already collected from Deepgram.
API keys are read best-effort per project after the member roster: a failure on that call leaves the keys off the Inventory page without failing the sync. Click Sync from integrations on the Integrations page to retry.
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.