Skip to main content
Connect Couchbase Capella with an organization API key to sync organization members, projects, API keys, clusters and organization events, 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 one Capella organization — the one whose ID you paste at connect time, or otherwise the one with the lowest organization ID among those the key can see — with their name, email, their organization roles (Organization Owner, Organization Member, Project Creator, or Member when Capella reports none) and the date they were added. People who have not yet accepted their invitation are left out. A member Capella reports as verified is shown as Active; any other verification state is shown as Inactive. Capella 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 Capella organization member roster — names, emails, organization roles, verification state and join dates — which appears on your Access page; your Capella projects, the organization’s API keys (name, roles, expiry and the number of allowed IP ranges — never the secret) and the clusters in each project (cloud provider, region, server version and state), which appear on your Inventory page; and the organization’s events from the last 365 days, which appear on your Changes page. Each event arrives as a change that has already happened — status Deployed, with its priority derived from the event severity (Capella’s informational events are Low), the actor and the affected resource in the description, and the organization (plus the project, when the event names one) as the environment. Members’ last-login times are not read.It calls these Couchbase Capella endpoints on cloudapi.cloud.couchbase.com:
  • /v4/organizations
  • /v4/organizations/{id}/users
  • /v4/organizations/{id}/projects
  • /v4/organizations/{id}/apikeys
  • /v4/organizations/{id}/projects/{projectId}/clusters
  • /v4/organizations/{id}/events
Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Couchbase Capella environment.

​
Troubleshooting

When the key can see several organizations and the Organization ID was left empty, DSALTA syncs the one with the lowest organization ID. To pin a different one, disconnect, then connect again with the Organization ID filled in. A key generated with the Organization Member role, or scoped to a project, passes the connection check but returns only part of the roster — generate the key with the Organization Owner role. Note that disconnecting permanently deletes the data already collected from Capella.
A Capella API key expires after 180 days unless Key Expiration was set to does not expire when it was generated, and a key restricted to specific IP addresses cannot be used from DSALTA. Generate a new key, then disconnect and connect again.
Projects, API keys, clusters and events 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. Clusters only appear once a project has one deployed, and only events from the last 365 days are read. 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.