Skip to main content
Connect Fireflies with an API key to sync workspace users and run access reviews. Read-only.
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.
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 Fireflies workspace roster — each user’s name, email address, user id and whether they are an admin, recorded as the role Admin or Member — which appears on your Access page. Meeting transcripts, recordings and notes are never read, and no other DSALTA page is populated from Fireflies. The Fireflies user record carries no status or MFA field, so every Access row is recorded as Active with MFA Unknown.It calls these Fireflies endpoints:
  • POST /graphql — { user { name email } }, used to confirm the credential
  • POST /graphql — { users { name email user_id is_admin } }, used to fill the Access page
Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Fireflies environment.

​
Troubleshooting

A Fireflies API key is issued per user, so the roster DSALTA sees is the one that key can see. Connect with a key from an account that sees the full workspace roster.
An invalid or regenerated API key. Regenerating the key in Fireflies invalidates the one DSALTA holds — copy the current key 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.