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

# ClickUp

> Project management — members, Spaces & access

<Tabs>
  <Tab title="Overview">
    Connect ClickUp via OAuth to sync workspace members (excluding guests) and Spaces, 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 ClickUp user roster — names, emails and roles, which appears on your **Access** page; and your ClickUp resources, which appear on your **Inventory** page. ClickUp's workspace members carry no account status, so everyone is listed as Active, and guests are left off the roster entirely.

    It calls these ClickUp endpoints:

    * `/api/v2/team`
    * `/api/v2/user`
    * `/api/v2/team/{teamId}/space`

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

    ## Troubleshooting

    <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">
    <Steps>
      <Step title="Open the integration">
        In the DSALTA sidebar, go to **Integrations**, find **ClickUp**, and click **Connect**.

        <img src="https://mintcdn.com/dsalta/4UzgskHSsjeDN5e5/images/integrations/clickup/01-link-clickup-account-panel.png?fit=max&auto=format&n=4UzgskHSsjeDN5e5&q=85&s=06706018a36f07ae0555b20f90db7ccc" alt="DSALTA Link ClickUp Account panel stating that a pop-up will open and that the browser must not block pop-ups, with a Connect button" style={{maxWidth:"340px",width:"100%",borderRadius:"8px"}} width="984" height="1390" data-path="images/integrations/clickup/01-link-clickup-account-panel.png" />
      </Step>

      <Step title="Authorize access">
        A secure ClickUp window opens. Sign in if prompted and approve the request. DSALTA does not ask you to choose which resources to monitor — the connection covers everything the credential you authorize can read.

        ClickUp's authorization screen asks which Workspace(s) to grant access to. You can tick more than one, and DSALTA only ever sees the ones you tick — members and Spaces belonging to a Workspace you leave out never reach the Access or Inventory pages. If you add a Workspace in ClickUp later, you have to disconnect and connect again to include it.

        <Tip>Sign in as someone who belongs to the Workspace you want reviewed — the Access page is built from that Workspace's member list. ClickUp guests (external collaborators invited into a single Space) are filtered out before they reach the Access page, so DSALTA's count will be lower than ClickUp's total people count.</Tip>

        <Tip>There is nothing to tick or untick on the ClickUp consent screen beyond the Workspace itself — ClickUp's OAuth does not use scopes, so authorization is all-or-nothing for the Workspaces you select.</Tip>
      </Step>
    </Steps>

    <Check>
      Once connected, ClickUp appears on the **Connected** tab and the checks below begin reporting after the first sync.
    </Check>
  </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/clickup/user-access-to-critical-system-should-be-valid) | Info     | Checks that everyone with ClickUp access is an active employee on the People page. |
    | [Offboarded users should not have active access](/integrations/clickup/offboarded-users-should-not-have-active-access) | High     | Checks that offboarded employees no longer have active ClickUp access.             |
  </Tab>

  <Tab title="Useful links">
    | Topic   | Link                                                                            |
    | ------- | ------------------------------------------------------------------------------- |
    | Setup   | [ClickUp API authentication](https://developer.clickup.com/docs/authentication) |
    | General | [ClickUp website](https://clickup.com)                                          |
    | DSALTA  | [Connection error messages](/troubleshooting/connection-error-messages)         |
  </Tab>
</Tabs>