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

# Insightly

> CRM — account users & access

<Tabs>
  <Tab title="Overview">
    Connect Insightly with an API key to sync account users and run access reviews. Read-only; the key is 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 your Insightly account users — user id, first and last name, email address, the administrator and account-owner flags, active status and creation date — which appear on your **Access** page. Roles come from those two flags and read **Administrator**, **Owner** or **User**; Insightly's own permission sets and profiles are not read. **Access** is the only page this integration populates, since the Organisations Insightly holds are your customer and prospect records rather than infrastructure.

    It calls this Insightly endpoint:

    * `/v3.1/Users`

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

    ## Troubleshooting

    <AccordionGroup>
      <Accordion title="A user I deactivated in Insightly is still listed">
        Insightly keeps returning deactivated users, so the row stays on the **Access** page with the status **Inactive**. Run **Sync from integrations** after a change in Insightly, then read the status column.
      </Accordion>

      <Accordion title="The connection fails to validate">
        The API key is invalid or has been regenerated, or the pod entered during the connect flow is not the one your account lives on.
      </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 Insightly API key plus your pod, entered in Nango's secure window. Read-only.

    **Before you begin**

    * An Insightly account whose **User Settings** page exposes an API key. A standard Insightly account works; no paid plan is required.
    * Your pod — the short data-centre code in your Insightly API URL. Nango uses it to build the base URL DSALTA calls.

    You will need:

    | Field       | Where to find it                                               | Example                        |
    | ----------- | -------------------------------------------------------------- | ------------------------------ |
    | **API key** | Insightly → profile icon (top-right) → User Settings → API Key | `Shown in the API Key section` |
    | **Pod**     | The short code in your Insightly API URL                       | `na1`                          |

    <Steps>
      <Step title="Start in DSALTA">
        Open **Integrations** in the DSALTA sidebar, find **Insightly**, and click **Connect** to open the connect panel. Leave it open — it lists every value you need, and you collect those in the steps below.
      </Step>

      <Step title="Open your Insightly User Settings">
        In Insightly, click your profile icon (top-right) → User Settings, then scroll down to the API Key section. A standard Insightly account works; no paid plan is required.
      </Step>

      <Step title="Copy your API key and pod">
        Copy the API key shown. Also note your "pod" — the short code in your API URL (e.g. if it reads api.na1.insightly.com, your pod is na1). You'll enter both in the next step.

        <Tip>
          Nothing on the Insightly page is labelled "pod" — read it out of the API URL itself: the segment between `api.` and `.insightly.com` is the value you need.
        </Tip>
      </Step>

      <Step title="Connect Insightly">
        Back in the connect panel, click through to the **Connect Insightly** step and enter your Insightly credentials in the secure Nango window. DSALTA never stores them directly — it keeps only a connection reference, and the key itself is held by Nango.

        <Warning>
          The API key carries whatever the Insightly user it belongs to can do, and is not narrowed to the endpoint DSALTA calls. Treat it as a secret, and regenerate it in Insightly if you disconnect the integration.
        </Warning>
      </Step>
    </Steps>

    <Check>
      DSALTA validates the credential as soon as the Nango window closes, by calling `/v3.1/Users` and confirming it resolves to an Insightly account. 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 API key is invalid or has been regenerated, or the pod does not match the data centre your account lives on.

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

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