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

# ilert

> Incident management & on-call — members & access

<Tabs>
  <Tab title="Overview">
    Connect ilert with a user API key to sync account members, services, alert sources, status pages, heartbeat monitors, and alerts, and run access reviews. Read-only. Data feeds into your Access accounts, Inventory and Incidents pages.

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

    <Info>
      **What you'll see.** The Access page lists the users of the one ilert **account** the key belongs to, with their name (or their username or email address when ilert has no name for them), their email, their ilert role (**Admin**, **Responder** or **User**, or **Member** when ilert reports none) and the date the user was created in ilert. Users with the **Guest** or **Stakeholder** role are left out. ilert removes a user outright rather than deactivating them, so every listed user is shown as **Active**. ilert does not mark an invited user who has not yet signed in, so such a user appears like any other. ilert reports no per-user MFA state, so the **MFA** column is blank (shown as a dash).
    </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 ilert account user roster — names, usernames, emails, roles and creation dates — which appears on your **Access** page; your ilert **services** (status, public status and whether they allow one open incident only), **alert sources** (integration type, status and whether they are active — never the integration key or URL), **status pages** (visibility, whether they are activated and their host) and **heartbeat monitors** (state and interval), which appear on your **Inventory** page; and your **alerts** in the pending, accepted and resolved states, which appear on your **Incidents** page. Each alert carries its summary as the title, and its details, alert source, priority, assignee and resolution time in the description. A pending alert shows **Open**, an accepted alert shows **Investigating** and a resolved alert shows **Resolved**; an alert whose ilert severity is critical or major is recorded as **Critical**, otherwise a high priority is **High**, a low priority is **Low** and anything else is **Medium**. Every alert is typed **Alert**. Incidents fills once an alert has been raised in your account. Teams, on-call schedules, escalation policies, declared incidents and deployment pipelines are not read, and neither is any user's last login.

    It calls these ilert endpoints on `api.ilert.com/api`:

    * `/users/current` (the key's own user, used to validate)
    * `/users`
    * `/services`
    * `/alert-sources`
    * `/status-pages`
    * `/heartbeat-monitors`
    * `/alerts` (with the `states` filter set to pending, accepted and resolved)

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

    ## Troubleshooting

    <AccordionGroup>
      <Accordion title="The connection is rejected">
        The key is not a **user API key**: an alert-source integration key or a metric API key cannot read users, and ilert answers with a 401 or 403. Create a user API key from your avatar → **Profile → API Keys** as the account owner or an Admin, then connect again. A key pasted with a leading `Bearer ` prefix is accepted — the prefix is stripped.
      </Accordion>

      <Accordion title="The Access page shows fewer users than expected">
        A user API key sees only what its creator can see, and ilert answers a partial roster with no error. A key created by a **Responder** or **Guest** returns only part of the roster, or nothing. Create the key as the account owner or an Admin, then disconnect and connect again. Note that disconnecting permanently deletes the data already collected from ilert.
      </Accordion>

      <Accordion title="Inventory or Incidents is empty while Access works">
        Services, alert sources, status pages, heartbeat monitors and alerts are read best-effort after the user roster: a failure on one of those calls leaves that part of the page empty without failing the sync. A new account has none of these objects until you create them, and Incidents fills once an alert has been raised. Click **Sync from integrations** on the **Integrations** page to retry.
      </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/compliance/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 ilert user API key created by the account owner or an Admin. Read-only.

    **Before you begin**

    * An ilert account.
    * The account owner or an **Admin** user to create the key — a key created by a Responder or Guest sees only part of the roster.

    You will need:

    | Field | Where to find it | Example |
    | - | - | - |
    | **API key** | Your avatar → **Profile → API Keys → Create API Key** | `ilert user API key` |

    <Steps>
      <Step title="Start in DSALTA">
        Open **Integrations** in the DSALTA sidebar, find **ilert**, and click **Connect** to open the connect panel.
      </Step>

      <Step title="Sign in as the account owner or an Admin">
        Sign in at [app.ilert.com](https://app.ilert.com) with the account owner or an Admin user. A key created by a Responder or Guest sees only part of the roster, or nothing.
      </Step>

      <Step title="Create a user API key">
        Click your avatar, then **Profile → API Keys → Create API Key**, and copy the key.

        <Warning>
          **This must be a personal user API key.** Do not use an alert-source integration key or a metric API key: those cannot read users, and DSALTA rejects them at connect time.
        </Warning>
      </Step>

      <Step title="Connect ilert">
        Return to the connect panel, paste the key, and click **Connect**.
      </Step>
    </Steps>

    <Check>
      DSALTA validates the key when you click **Connect**, by reading the key's own user record and then listing the account's users. 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.** An invalid key, an alert-source integration key or metric API key instead of a user API key, or a key that cannot read users.

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

  <Tab title="Useful links">
    | Topic | Link |
    | - | - |
    | Setup | [ilert API authentication](https://docs.ilert.com/developer-docs/rest-api/api-reference/introduction/authentication) |
    | Remediation | [User roles and permissions](https://docs.ilert.com/users-and-access-management/user-roles-and-permissions) |
    | General | [ilert console](https://app.ilert.com) |
    | DSALTA | [Connection error messages](/troubleshooting/connection-error-messages) |
  </Tab>
</Tabs>