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

# Shortcut

> Project management — members & projects

<Tabs>
  <Tab title="Overview">
    Connect Shortcut with an API token to sync workspace members and projects, 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 your Shortcut workspace members — name, email address, role, active status and per-member two-factor status — which appear on your **Access** page, and which the checks below match against your **People** directory by email; and your Shortcut Projects, which appear on your **Inventory** page. Deactivated members stay on the Access page marked **Inactive**.

    It calls these Shortcut endpoints:

    * `/api/v3/member`
    * `/api/v3/members`
    * `/api/v3/projects`

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

    ## Troubleshooting

    <AccordionGroup>
      <Accordion title="The connection fails to validate">
        An invalid, revoked or truncated API token.
      </Accordion>

      <Accordion title="A Shortcut member is reported as having no matching person on the People page">
        Either the person is not on your People page, or their Shortcut profile has no email address for the review to match on. Add the email address in Shortcut and re-sync, and the row will match on the next run.
      </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 Shortcut API token, entered in Nango's secure connect window. Read-only.

    **Before you begin**

    * A Shortcut account that can open **Settings → Your Account → API Tokens**. A standard account works; no paid plan is required.
    * Somewhere safe to hold the token between generating it and pasting it — it grants full workspace access.

    You will need:

    | Field         | Where to find it                                             | Example                                                |
    | ------------- | ------------------------------------------------------------ | ------------------------------------------------------ |
    | **API token** | [Open](https://app.shortcut.com/settings/account/api-tokens) | `Generated in Shortcut — grants full workspace access` |

    <Steps>
      <Step title="Start in DSALTA">
        Open **Integrations** in the DSALTA sidebar, find **Shortcut**, 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 Shortcut's API Tokens settings">
        In Shortcut, go to **Settings → Your Account → API Tokens**, or visit `app.shortcut.com/settings/account/api-tokens` directly.

        <Tip>
          A standard Shortcut account is enough — this integration does not require a paid plan.
        </Tip>
      </Step>

      <Step title="Generate a token">
        Give it a name (e.g. DSALTA) and click **Generate Token**, then copy the token — you will paste it in the next step.

        <Warning>
          **This token grants full workspace access.** Treat it exactly like a password: paste it straight into the connect window, keep it out of tickets and chat messages, and delete your copy once the connection is saved. If it leaks, revoke it in Shortcut and connect again with a new one.
        </Warning>
      </Step>

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

        <Tip>
          That window is Nango's, not DSALTA's. Nothing in it asks you to choose scopes or pick which projects to monitor: the connection covers everything the token can read.
        </Tip>
      </Step>
    </Steps>

    <Check>
      DSALTA validates the credential when you finish the connect window, by calling `/api/v3/member` through the Nango proxy and confirming it resolves to a Shortcut member. 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 **Inventory** page after the first sync to confirm your projects are listed.
    </Check>

    <Warning>
      **If the connection is rejected.** An invalid, revoked or truncated API token.

      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/shortcut/user-access-to-critical-system-should-be-valid) | Info     | Checks that everyone with Shortcut access is an active employee on the People page. |
    | [Offboarded users should not have active access](/integrations/shortcut/offboarded-users-should-not-have-active-access) | High     | Checks that offboarded employees no longer have active Shortcut access.             |
    | [MFA should be enabled for all users](/integrations/shortcut/mfa-enabled-for-all-users)                                 | High     | Checks that every active Shortcut member has multi-factor authentication enabled.   |
  </Tab>

  <Tab title="Useful links">
    | Topic   | Link                                                                                 |
    | ------- | ------------------------------------------------------------------------------------ |
    | Setup   | [Shortcut API Tokens settings](https://app.shortcut.com/settings/account/api-tokens) |
    | General | [Shortcut website](https://shortcut.com)                                             |
    | DSALTA  | [Connection error messages](/troubleshooting/connection-error-messages)              |
  </Tab>
</Tabs>