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

# Avoma

> Meeting intelligence — org access

<Tabs>
  <Tab title="Overview">
    Connect Avoma with an API key to sync organization members 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>

    <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 Avoma organization member list — first and last name, email address, role display name and active status — which appears on your **Access** page, where every row is recorded as a Human account and a member reads as Inactive when Avoma reports the membership or the user as inactive. Meeting content — meetings, calls, recordings, notes and transcripts — is never read, so nothing is synced to **Inventory**, **Incidents** or **Changes**. **People** is your own DSALTA directory, which the checks below match Avoma members against by email.

    It calls this Avoma endpoint:

    * `/v1/users`

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

    ## Troubleshooting

    <AccordionGroup>
      <Accordion title="MFA reads Unknown for every Avoma user">
        Avoma's user record carries no MFA field, so DSALTA records **Unknown** and ships no MFA check for this integration. Enforce and evidence MFA through your identity provider instead.
      </Accordion>

      <Accordion title="The connection fails to validate">
        An invalid, revoked or deleted API key. Only organization admins can create, view and revoke Avoma API keys, so generate a new key as an admin and connect again.
      </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/data-library/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 Avoma API key, entered in Nango's secure connect window. Read-only.

    **Before you begin**

    * An Avoma organization
    * Organization **Admin** access — creating an API key requires it

    You will need:

    | Field       | Where to find it    | Example         |
    | ----------- | ------------------- | --------------- |
    | **API key** | See the steps below | `Avoma API key` |

    <Steps>
      <Step title="Start in DSALTA">
        Open **Integrations** in the DSALTA sidebar, find **Avoma**, 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.
      </Step>

      <Step title="Open Avoma's API Keys settings">
        In Avoma, go to **Settings → API Keys** (organization Admin access required), and create a new API key.

        <Tip>
          If you cannot find that screen, Avoma's own help center documents the path as **Settings → Organization → Developer → Add API Key**, and states that only org admins can create, view and revoke API keys — so if the menu is missing entirely, you are not an admin. See [Avoma: create and manage API keys](https://help.avoma.com/api-integration-for-avoma).
        </Tip>

        <img src="https://mintcdn.com/dsalta/50UUP7lNdp3gnRd3/images/integrations/avoma/01-developer-api-keys.png?fit=max&auto=format&n=50UUP7lNdp3gnRd3&q=85&s=f94195b0b38263eb46d258acaf8ae95a" alt="Avoma's Developer Settings page with Developer selected in the Settings sidebar and the Create API Key button" style={{maxWidth:"720px",width:"100%",borderRadius:"8px"}} width="1919" height="821" data-path="images/integrations/avoma/01-developer-api-keys.png" />
      </Step>

      <Step title="Copy the key immediately">
        Avoma only shows the full key once. Copy it somewhere safe — you'll paste it into the next step.

        <Warning>
          **This key is a live credential.** Anyone holding it can read your Avoma organization data for as long as the key exists. Keep it out of chat messages, tickets and shared documents, and delete your copy once the connection is saved. If it does leak, delete the key in Avoma and connect again with a new one.
        </Warning>
      </Step>

      <Step title="Connect Avoma">
        Enter your Avoma credentials in the secure Nango window. DSALTA never stores them directly — it keeps only a connection reference.

        DSALTA reads organization members and nothing else. It never modifies your Avoma account, and it never opens a meeting, recording, note or transcript.
      </Step>
    </Steps>

    <Check>
      DSALTA validates the credential when you finish the connect window. 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.** An invalid, revoked or deleted API key, or a key that was never fully copied — Avoma displays it once.

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

  <Tab title="Useful links">
    | Topic   | Link                                                                                  |
    | ------- | ------------------------------------------------------------------------------------- |
    | Setup   | [Avoma: create and manage API keys](https://help.avoma.com/api-integration-for-avoma) |
    | Setup   | [Avoma API documentation](https://help.avoma.com/api-documentation)                   |
    | General | [Avoma website](https://avoma.com)                                                    |
    | DSALTA  | [Connection error messages](/troubleshooting/connection-error-messages)               |
  </Tab>
</Tabs>