Skip to main content
Connect Confluent Cloud with a Cloud API key and secret to sync organization users and environments, 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.
What you’ll see. The Access page lists the user accounts of your Confluent Cloud organization with their name, email and the date they were created. Confluent’s users endpoint exposes no role, so every user is shown as Member, with (SSO) added when Confluent reports that they sign in through single sign-on. Service accounts live on a separate endpoint and never appear. Confluent reports no account status or MFA state, so every user is shown as Active with MFA Unknown.
The key must be created under “My account” with Global scope. A Service-account key starts with no role bindings and cannot read the user roster; a key scoped to a single Kafka cluster or resource cannot either. DSALTA rejects a key that returns no users at connect time.
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 Confluent Cloud user roster — names, emails, sign-in type and creation dates — which appears on your Access page; and your Confluent Cloud environments, which appear on your Inventory page with their Stream Governance package.It calls these Confluent Cloud endpoints:
  • /iam/v2/users
  • /org/v2/environments
Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Confluent Cloud environment.

​
Troubleshooting

Wrong key or secret, a key that has been deleted, or a key created for a Service account or with a resource scope instead of Global — those return no users, and DSALTA refuses to connect on an empty roster. Create a new key under My account with Global scope, then connect again.
The key inherits the permissions of the user who created it. Create it as an OrganizationAdmin so that every user in the organization is visible, then disconnect and connect again. Note that disconnecting permanently deletes the data already collected from Confluent Cloud.
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.