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

# Attio

> CRM — workspace members & access

<Tabs>
  <Tab title="Overview">
    Connect Attio via OAuth to sync workspace members and run access reviews. Read-only; tokens are held by Nango.

    <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 Attio workspace member list — first and last name, email address, access level and creation date — which appears on your **Access** page, where the access level is used as the role and every row is recorded as a Human account. Attio is a CRM, so its records are your own customer and deal data rather than infrastructure, and nothing is synced to **Inventory**, **Incidents** or **Changes**. **People** is your own DSALTA directory, which the checks below read to match members by email.

    It calls this Attio endpoint:

    * `/v2/workspace_members`

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

    ## Troubleshooting

    <AccordionGroup>
      <Accordion title="Every member shows as Active">
        Attio's workspace member object carries no status field. Removing someone from the workspace takes them off the member list, and their Access row clears at the next sync.
      </Accordion>

      <Accordion title="The connection fails to validate">
        DSALTA validates by listing workspace members. Authorize again with an Attio account that has permission to view the workspace's members.
      </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">
    OAuth. Read-only; tokens are managed by Nango, so there are no API keys to copy.

    **Before you begin**

    * An Attio workspace — a standard account works, and no paid plan is required
    * An Attio account with permission to view workspace members
    * A browser that will let the authorization window open

    <Steps>
      <Step title="Start in DSALTA">
        Open **Integrations** in the DSALTA sidebar, find **Attio**, and click **Connect** to open the connect panel. Leave it open — the whole connection happens from here.
      </Step>

      <Step title="Authorize as a workspace member with access permissions">
        You'll be redirected to Attio to log in and approve DSALTA's access. Sign in with an account that has permission to view workspace members — a standard Attio account works; no paid plan is required.

        <Tip>
          Sign in as a member of the workspace you actually want reviewed — the Access page is built from that workspace's member list. To review a different workspace, disconnect and connect again.
        </Tip>
      </Step>

      <Step title="Approve the requested access">
        Attio asks you to grant read-only access. DSALTA never sees your password.

        <Info>
          The consent screen lists `user_management:read`, `record_permission:read` and `object_configuration:read`.
        </Info>
      </Step>
    </Steps>

    <Check>
      DSALTA validates the connection by listing workspace members. 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.** The authorization was cancelled or timed out, or the account you signed in with cannot view the workspace's members.

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

  <Tab title="Useful links">
    | Topic   | Link                                                                    |
    | ------- | ----------------------------------------------------------------------- |
    | General | [Attio website](https://attio.com)                                      |
    | DSALTA  | [Connection error messages](/troubleshooting/connection-error-messages) |
  </Tab>
</Tabs>