> ## Documentation Index > Fetch the complete documentation index at: https://help.dsalta.com/llms.txt > Use this file to discover all available pages before exploring further. # Flagsmith > Feature flags — members & access 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](/guides/data-library/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](/troubleshooting/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. A Flagsmith organisation API key, sent as an `Api-Key` authorization header. Read-only. **Before you begin** * A Flagsmith account * **Organisation Administrator** role — creating the key requires it * A Flagsmith SaaS organisation; self-hosted instances are not supported You will need: | Field | Where to find it | Example | | ------------------------ | ------------------------------------------------------------------------------------------------------------- | -------------------------------- | | **Organisation API Key** | [Open](https://docs.flagsmith.com/integrating-with-flagsmith/flagsmith-api-overview/admin-api/authentication) | `Flagsmith organisation API key` | Open **Integrations** in the DSALTA sidebar, find **Flagsmith**, and click **Connect** to open the connect panel. Leave it open — it lists every value you need, and you create those in the steps below. In Flagsmith, click your organisation name in the top navigation, then go to **Organisation Settings**. If you do not see **Organisation Settings**, you are not an Organisation Administrator. Ask an administrator to create the key for you — no lesser role can. Go to the **API Keys** tab and click **Create API Key**. Copy it — it's shown only once. **This key grants full read and write access to the organisation.** Flagsmith does not offer a read-only variant, so the credential you paste into DSALTA is more powerful than what DSALTA uses it for: DSALTA only ever issues GET requests. Treat the key like a password — keep it out of chat messages, tickets and shared documents, and delete your copy once the connection is saved. If it leaks, revoke it in Flagsmith and connect again with a new one. Paste your organisation API key, then click **Connect**. DSALTA reads organisation members, environments and the audit log, and nothing else. It never reads or changes a feature flag's value, so connecting cannot alter live application behaviour. DSALTA verifies the API key before saving it. On success the integration moves to the **Connected** tab, and **Manage → Status** reads **Connected and working properly**. Checks begin reporting after the first sync. **If the connection is rejected.** An invalid API key — revoked, mistyped, or never fully copied, since Flagsmith displays it once. The on-screen message is generic — see [Connection error messages](/troubleshooting/connection-error-messages). Each check below re-runs once a day, at 02:00 America/New\_York, while this integration is connected. Click any check for step-by-step remediation guidance. | Check | Severity | What it verifies | | ------------------------------------------------------------------------------------------------------------------------ | -------- | ------------------------------------------------------------------------------------------ | | [User access to Critical System should be valid](/integrations/flagsmith/user-access-to-critical-system-should-be-valid) | Info | Checks that everyone with Flagsmith access is an active employee on the People page. | | [Offboarded users should not have active access](/integrations/flagsmith/offboarded-users-should-not-have-active-access) | High | Checks that offboarded employees no longer have active Flagsmith access. | | [MFA should be enabled for all users](/integrations/flagsmith/mfa-enabled-for-all-users) | High | Checks that the Flagsmith organisation enforces two-factor authentication for all members. | | Topic | Link | | ------- | ------------------------------------------------------------------------------------------------------------------------------------------- | | Setup | [Flagsmith Admin API authentication](https://docs.flagsmith.com/integrating-with-flagsmith/flagsmith-api-overview/admin-api/authentication) | | General | [Flagsmith website](https://flagsmith.com) | | DSALTA | [Connection error messages](/troubleshooting/connection-error-messages) |