> ## 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.

# Aiven

> Managed data infrastructure — users & access

<Tabs>
  <Tab title="Overview">
    Connect Aiven with a personal API token to sync organization users, projects and services, and run access reviews. Read-only.

    <Info>
      **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.
    </Info>

    <Info>
      **What you'll see.** The Access page lists the human users of one Aiven **organization** — the one with the lowest organization ID among those the token can see — with their name, email, whether they are a **Super Admin** or a **Member**, whether they are managed by SCIM, the date they joined, and Aiven's own active or inactive state. Application users (Aiven's machine accounts) are left out. Aiven reports no MFA state on this endpoint, so the **MFA** column shows **Unknown**.
    </Info>

    <Note>
      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.
    </Note>

    ## What DSALTA reads

    DSALTA reads the Aiven organization user roster — names, emails, super-admin status, SCIM management, join dates and account state — which appears on your **Access** page; and your Aiven **projects** and the **services** inside them, which appear on your **Inventory** page with their cloud, tier, service type, plan and state.

    It calls these Aiven endpoints:

    * `/v1/me`
    * `/v1/organizations`
    * `/v1/organization/{id}/user`
    * `/v1/project`
    * `/v1/project/{name}/service`

    Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Aiven environment.

    ## Troubleshooting

    <AccordionGroup>
      <Accordion title="The Access page is missing users, or shows the wrong organization">
        A personal token inherits the permissions of the user who created it, and among the organizations that token can see, DSALTA syncs the one with the lowest organization ID. Create the token as an organization admin who belongs to the organization you want reviewed. If your admin belongs to several organizations, create the token from a user who belongs only to the one you want.
      </Accordion>

      <Accordion title="The token stopped working">
        Aiven tokens carry a session duration chosen at creation, and an organization can enforce an authentication policy that limits personal tokens. Generate a new token, then disconnect and connect again. Note that disconnecting permanently deletes the data already collected from Aiven.
      </Accordion>
    </AccordionGroup>

    <AccordionGroup>
      <Accordion title="How do I check whether the connection is healthy?">
        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.
      </Accordion>

      <Accordion title="A check shows Failed and nothing changed on my side">
        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/compliance/test-results).
      </Accordion>

      <Accordion title="Data looks out of date">
        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.
      </Accordion>

      <Accordion title="How do I repair a broken connection?">
        There is no Reconnect, Repair or Refresh Token button. The only repair available is to disconnect and connect again.

        <Warning>
          **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).
        </Warning>
      </Accordion>

      <Accordion title="Configure scope will not let me change anything">
        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.
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="How to connect">
    An Aiven personal API token. The organization is detected automatically. Read-only.

    **Before you begin**

    * An Aiven organization, and a user in it whose permissions cover the whole user list — the token acts as that user.

    You will need:

    | Field         | Where to find it                                              | Example    |
    | ------------- | ------------------------------------------------------------- | ---------- |
    | **API Token** | Profile icon → **User information → Tokens → Generate token** | Shown once |

    <Steps>
      <Step title="Start in DSALTA">
        Open **Integrations** in the DSALTA sidebar, find **Aiven**, and click **Connect** to open the connect panel.
      </Step>

      <Step title="Generate a personal token">
        In the [Aiven Console](https://console.aiven.io), click your profile icon, choose **User information**, open **Tokens**, and click **Generate token**. Enter a description, set the session duration, and click **Generate token** again.

        <Info>
          Copy the token with the copy icon before closing the window — Aiven warns that "you cannot view the token after you close this window". If you lose it, generate a new one. Pick a session duration long enough for a standing connection: when the token expires, the DSALTA connection fails until you generate a new one and reconnect.
        </Info>
      </Step>

      <Step title="Connect Aiven">
        Return to the connect panel, paste the token, and click **Connect**. The organization is detected automatically.
      </Step>
    </Steps>

    <Check>
      DSALTA validates the token when you click **Connect**, by reading your own user record and listing the organizations it can see. On success the integration moves to the **Connected** tab, and **Manage → Status** reads **Connected and working properly**. Checks begin reporting after the first sync.
    </Check>

    <Warning>
      **If the connection is rejected.** Invalid or expired token, or a token whose user belongs to no organization.

      The on-screen message is generic — see [Connection error messages](/troubleshooting/connection-error-messages).
    </Warning>
  </Tab>

  <Tab title="Automated checks">
    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/aiven/user-access-to-critical-system-should-be-valid) | Info     | Checks that everyone with Aiven access is an active employee on the People page. |
    | [Offboarded users should not have active access](/integrations/aiven/offboarded-users-should-not-have-active-access) | High     | Checks that offboarded employees no longer have active Aiven access.             |
  </Tab>

  <Tab title="Useful links">
    | Topic       | Link                                                                                        |
    | ----------- | ------------------------------------------------------------------------------------------- |
    | Setup       | [Create a personal token](https://aiven.io/docs/platform/howto/create_authentication_token) |
    | Remediation | [Manage organization users](https://aiven.io/docs/platform/howto/manage-org-users)          |
    | General     | [Aiven Console](https://console.aiven.io)                                                   |
    | DSALTA      | [Connection error messages](/troubleshooting/connection-error-messages)                     |
  </Tab>
</Tabs>