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

# Quickbase

> Low-code platform — realm user access

<Tabs>
  <Tab title="Overview">
    Connect Quickbase with a User Token to sync realm users 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 Quickbase realm user list — name, email address, role and active status — which appears on your **Access** page, and which the checks below match against your **People** directory. Seeing the whole realm requires a Realm Administrator User Token, because Quickbase scopes what a token can read to the account that created it.

    It calls one Quickbase endpoint, on `https://api.quickbase.com`, for both credential validation and the user sync:

    * `POST /v1/users`

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

    ## Troubleshooting

    <AccordionGroup>
      <Accordion title="The connection fails to validate">
        An invalid, deleted or deactivated User Token, or a realm hostname that does not match your account.
      </Accordion>

      <Accordion title="The Access page shows fewer users than the realm has">
        The connected User Token is not a Realm Administrator token, so Quickbase returns only the users its creator can see. Create a Realm Administrator token, then disconnect 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">
    A Quickbase User Token and your realm hostname, entered in Nango's secure connect window. Read-only.

    **Before you begin**

    * A Quickbase realm, and an account that can open **My Preferences → My User Tokens**
    * Realm Administrator rights, to sync the full realm user list

    You will need:

    | Field              | Where to find it                                           | Example                                 |
    | ------------------ | ---------------------------------------------------------- | --------------------------------------- |
    | **Realm hostname** | The subdomain you sign in to                               | `yourcompany.quickbase.com`             |
    | **User Token**     | Quickbase avatar → **My Preferences** → **My User Tokens** | Shown when you create it — copy it then |

    <Steps>
      <Step title="Start in DSALTA">
        Open **Integrations** in the DSALTA sidebar, find **Quickbase**, 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="Find your realm hostname">
        Your Quickbase realm hostname is the subdomain you use to log in — for example `yourcompany.quickbase.com`.
      </Step>

      <Step title="Generate a User Token">
        In Quickbase, click your avatar → **My Preferences** → **My User Tokens**, and create a new token.

        <Tip>
          Use a Realm Administrator token — it is required to sync the full realm user list.
        </Tip>
      </Step>

      <Step title="Copy the token immediately">
        Copy the token somewhere safe — you'll paste it into the next step along with your realm hostname. DSALTA only reads data (realm users) and never modifies your Quickbase apps.

        <Warning>
          **This token is a live credential.** Anyone holding it can act as the user who created it, for as long as the token exists. Keep it out of chat messages, tickets and shared documents, and delete your copy once the connection is saved. If it does leak, deactivate the token in Quickbase and connect again with a new one.
        </Warning>
      </Step>

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

        <Info>
          That window is Nango's, not DSALTA's.
        </Info>
      </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.

      Open the **Access** page after the first sync to confirm your realm users are listed.
    </Check>

    <Warning>
      **If the connection is rejected.** An invalid, deleted or deactivated User Token, or a realm hostname that does not match your account.

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

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