Add and Manage Critical Systems

Learn how to add, connect, and manage your organisation’s critical systems in Sprinto for effective access tracking.

The Critical systems 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.

---

Add a critical system

1. Go to Data Library > Access > Critical systems.

2. Select Add Critical System at the top right.

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

2. Select a system from the available list.

3. Click Add System.

You can add multiple systems across categories. Each added system becomes visible in the list with its connection status.

---

Connect a critical system

1. In the Critical systems list, locate the system you want to connect.

2. Click Connect.

1. Follow the on-screen integration steps. This may include:

   • Authorising Sprinto via OAuth

   • Providing API keys

   • Granting read-only access for compliance review

2. Click Next and complete the setup flow.

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:

Status	Description
Connected	System is integrated and data is syncing correctly.
Not Connected	System has been added but is not yet integrated.
Disconnected	Integration is broken or access has been revoked.

---

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.