Skip to main content
Connect GrowthBook with an admin Secret Key to sync organization members with their roles, projects, environments, SDK connections, feature flags and experiments, and the feature revision history, and run access reviews. Read-only. Data feeds into your Access accounts, Inventory and Changes 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 the one GrowthBook organization the Secret Key belongs to — GrowthBook resolves the organization from the key itself. Each row shows the member’s name (or their email address when GrowthBook reports none), their email, their global role (for example Admin, Read Only, Collaborator, Engineer, Analyst or Experimenter, or Member when GrowthBook reports none) and the date they were added to the organization. Pending invitations are kept by GrowthBook in a separate list and never appear, and API keys are separate objects that never appear as members. GrowthBook reports no account status, so every member is shown as Active. GrowthBook 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 GrowthBook organization member roster — names, emails, global roles and join dates — which appears on your Access page; your GrowthBook projects, environments (default state and project scope), SDK connections (environment, languages, SDK version and proxy setting — never the connection’s keys), feature flags (value type, tags, owner and archived state), experiments (status, owner and archived state) and data sources (type), which appear on your Inventory page; and the feature revision history, which appears on your Changes page. Each revision arrives as a change titled with the feature key and revision number, with the actor (a member, an API key or the system), the comment, the base version and the publish or creation date in the description, priority always Low because GrowthBook attaches no severity to a revision, type feature-revision, and GrowthBook as the environment; a published revision has status Deployed, an unpublished one Draft. When GrowthBook’s revision list answers empty — as it does on GrowthBook Cloud — the page falls back to the latest revision of each feature flag, so it shows one row per flag rather than a per-edit history. Feature flags, experiments and data sources appear once you have created them. Members’ last-login dates, project-level roles and teams are not synced.It calls these GrowthBook endpoints on api.growthbook.io/api (or <your API host>/api for a self-hosted GrowthBook):
  • /v1/members
  • /v1/projects
  • /v1/environments
  • /v1/sdk-connections
  • /v2/features
  • /v1/experiments
  • /v1/data-sources
  • /v2/feature-revisions
Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your GrowthBook environment.

​
Troubleshooting

The key is a readonly Secret Key — it cannot list the organization’s members, so GrowthBook refuses the call — or an SDK Connection client key from Features → SDKs, which is public and rejected by the REST API. Create a Secret Key with the admin role. For a self-hosted GrowthBook, enter the API host only (for example growthbook-api.example.com): DSALTA strips any scheme or path and always calls https://<host>/api, so an API host that is not served over HTTPS cannot be connected.
A Personal Access Token stops working when its user leaves the organization or when personal access tokens are disabled for the organization. Create an organization Secret Key instead, then disconnect and connect again. Note that disconnecting permanently deletes the data already collected from GrowthBook.
Projects, environments, SDK connections, feature flags, experiments, data sources and revisions are read best-effort after the member roster: a failure on one of those calls leaves that part of the page empty without failing the sync. On GrowthBook Cloud the revision list answers empty, so the Changes page shows the latest revision of each flag rather than every edit. 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.