> For the complete documentation index, see [llms.txt](https://docs.sprinto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinto.com/data-library/access/dashboard-actions/add-and-manage-critical-systems.md).

# Add and Manage Critical Systems

The **System accounts** tab allows you to define which systems hold sensitive data and should be monitored for access compliance. Sprinto supports integrations with commonly used identity providers, HR platforms, cloud services, and developer tools.

Once connected, Sprinto pulls user access data, enabling real-time access validation and monitoring.

Here's a short video on how to set up and manage the Access module.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEsyn5VMU6e0OyGjRtKgx%2Fuploads%2FhkQ1eiT0ov1clvDB0OtU%2FSetting%20Up%20and%20Managing%20Access%20Module%20in%20Sprinto.mp4?alt=media&token=ce1150b8-a5fb-48ab-ba9a-88fb5e5cf5d6>" %}

***

### Add a system

1. Go to **Data Library > Access > System accounts**.
2. Select **Add systems** at the top right.

<figure><img src="/files/CY2tERPyiaq6Irwvs8fQ" alt="" width="563"><figcaption></figcaption></figure>

3. In the left panel, choose the appropriate category:
   * Identity Provider (e.g. Okta, Microsoft Entra ID)
   * HR Platform (e.g. BambooHR, Workday)
   * Cloud Infrastructure (e.g. AWS, GCP)
   * Developer Tools, SaaS Applications, or Custom
4. Select a system from the available list.
5. Click **Add systems**.

<figure><img src="/files/jHq0AhQyh65aXJgtsa5b" alt="" width="563"><figcaption></figcaption></figure>

{% hint style="info" %}
You can add multiple systems across categories. Each added system becomes visible in the list with its connection status.
{% endhint %}

***

### Connect a system

1. In the **Critical systems** list, locate the system you want to connect.
2. Click **Connect**.

<figure><img src="/files/cErTv1xf6MXpPR8JDExA" alt="" width="563"><figcaption></figcaption></figure>

3. Follow the on-screen integration steps. This may include:
   * Authorising Sprinto via OAuth
   * Providing API keys
   * Granting read-only access for compliance review
4. Click **Next** and complete the setup flow.

<figure><img src="/files/FOakN8Q4UjLAIPgMpj9A" alt="" width="375"><figcaption></figcaption></figure>

Once connected, the system status updates to **Connected**. Sprinto begins pulling user data for access checks.

***

### View system details

For any added system, you can:

* Hover over the info icon to view required permissions.
* See the **last sync** timestamp and connection status.
* View **number of users** or accounts associated with the system.
* Check the **provider** (e.g. Okta, Google, AWS) for identity mapping.

***

### Track system status

Each system is labelled with its current status:

<table><thead><tr><th width="179.4921875">Status</th><th width="419.03125">Description</th></tr></thead><tbody><tr><td><strong>Connected</strong></td><td>System is integrated and data is syncing correctly.</td></tr><tr><td><strong>Not Connected</strong></td><td>System has been added but is not yet integrated.</td></tr><tr><td><strong>Disconnected</strong></td><td>Integration is broken or access has been revoked.</td></tr></tbody></table>

***

### Best practices

* Prioritise adding identity and access systems first (e.g. Okta, Microsoft Entra ID).
* Ensure that each system is actively connected before proceeding with staff mapping.
* Periodically review the list to retire unused systems.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sprinto.com/data-library/access/dashboard-actions/add-and-manage-critical-systems.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.