Skip to main content
Connect Flagsmith with an organisation API key to sync members, environments, and the audit log, 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 your Flagsmith organisation’s member list — first and last name, email address, organisation role and join date — which appears on your Access page; your environments, aggregated across every project in the organisation and each tagged with its owning project name, which appear on your Inventory page; and the organisation audit log, which appears on your Changes page. Feature flags, segments and identities are not read, and MFA reads Unknown on every Access row because Flagsmith’s user record has no per-user two-factor field — the MFA check below reads the organisation’s force_2fa setting instead. DSALTA syncs one organisation, the first the API key can see, and connecting requires a Flagsmith SaaS organisation.It calls these Flagsmith endpoints:
  • /api/v1/organisations/
  • /api/v1/organisations/{id}/users/
  • /api/v1/projects/?organisation={id}
  • /api/v1/environments/?project={id}
  • /api/v1/organisations/{id}/audit/
Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Flagsmith environment.

​
Troubleshooting

An invalid, revoked or partially copied organisation API key. Flagsmith shows the key once at creation, so a truncated paste is the common cause — create a new 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.