> ## Documentation Index
> Fetch the complete documentation index at: https://docs.assuric.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Import incidents from incident.io

> Connect incident.io, then bring its incidents into your Assuric incident log as clinical or security incidents.

<Note>
  **Quick summary**

  * You can bring incidents from incident.io into Assuric instead of retyping them.
  * The **Import** button on the incidents page only appears once an admin connects incident.io under **Workspace → Integrations**.
  * Imported incidents stay in sync with incident.io for fields like title and status, so edit them in incident.io.
</Note>

If you import from **Privacy & Security → Incidents**, *Security* is already ticked under *Import to*.

## Connect incident.io

Only admins can connect or disconnect incident.io.

<Steps>
  <Step title="Create an API key in incident.io">
    As an admin in incident.io, go to **Settings → API keys** and click **Add new**. Name the key, tick only *View data, like public incidents and organisation settings*, and click **Create**. Copy the key straight away: incident.io only shows it once.
  </Step>

  <Step title="Connect it in Assuric">
    Go to **Workspace → Integrations** and click **Connect** on the **Incident.io** card. Paste the key into *Incident.io API key* and click **Validate**: Assuric confirms your incident.io workspace or names the permission the key is missing. Then click **Connect**: Assuric syncs on a schedule, and **Import** appears on the incidents page.
  </Step>
</Steps>

Statuses arrive as incident.io's own values, so there's nothing to map. To use a different key, click **Settings**, then **Disconnect**, and reconnect.

## Import incidents

<Steps>
  <Step title="Select the incidents">
    Click **Import** on the incidents page to open the *Import from Incident.io* dialog, which lists your latest incident.io incidents that aren't in Assuric yet. Click **Sync Now** to refresh the list, then tick each incident you want. If you filter the list, use only one multi-select filter at a time.
  </Step>

  <Step title="Choose where they land, then import">
    Under *Import to*, tick *Clinical*, *Security* or both, and pick the *Products* the incidents affect. Then click **Import N**, where N is how many you selected. It's available once *Clinical* or *Security* is ticked.
  </Step>
</Steps>

Each imported incident comes with:

* *Incident ID*, *Incident Title*, *Summary*, *Status*, *Severity* and *Date Occurred* filled in and kept in sync, so change them in incident.io.
* *Source* set to *Incident.io*, so you can filter for it.
* An *Imported from Incident.io* link to the original, with a refresh icon to pull the latest data.

Fill in the rest in Assuric, such as *Cause(s)*, *Products*, linked hazards or risks, *Root Cause Analysis* and *Date Closed*.

## Related articles

<Columns cols={2}>
  <Card title="Manage your incident log" icon="list-filter" href="/privacy-security/managing-incidents">
    Link imported incidents and track them to closure.
  </Card>

  <Card title="Create an incident" icon="siren" href="/privacy-security/incidents">
    Add an incident by hand.
  </Card>
</Columns>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.