> 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/identify-and-map-users-in-a-critical-system.md).

# Identify and map users in a critical system

Use Sprinto to identify and map accounts discovered in critical systems to the appropriate employee or contractor records. This helps maintain accurate access inventories, improves access reviews, and ensures user accounts are correctly classified for audit and compliance purposes.

### Before you begin

* Ensure the critical system has been added to Sprinto.
* You must have permission to manage access records within the critical system.
* User accounts must be synced or imported into the selected critical system.

### Identify and map a user

1. Log in to the Sprinto dashboard.
2. Navigate to **Data Library > Access**.
3. Select the **System accounts** tab.

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

4. Open the critical system where you want to identify or map users.
5. Select the **Users** tab.
6. Locate the user account you want to classify.
7. Click the **Edit** icon next to the user record.

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

8. In the **Identify & map user** dialog, select one of the following options from the **User is** dropdown:
   * **Existing staff in Sprinto** – Map the account to an employee or contractor that already exists in Sprinto.
   * **New staff in Sprinto** – Map the account to an employee or contractor who has not yet been added to Sprinto.
   * **Not a staff account** – Mark the account as a shared, service, system, or non-human account.
   * **Not identified** – Mark the account as unidentified when ownership cannot be determined.
9. Enter the employee or contractor details.
10. Click **Save**.

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

The selected classification is applied to the user account and displayed in the Users table.

### Classification options

<table><thead><tr><th width="205.42578125">Option</th><th>Description</th></tr></thead><tbody><tr><td>Existing staff in Sprinto</td><td>Links the account to an existing employee or contractor record in Sprinto.</td></tr><tr><td>New staff in Sprinto</td><td>Associates the account with a staff member who has not yet been added to Sprinto.</td></tr><tr><td>Not a staff account</td><td>Identifies shared mailboxes, service accounts, support accounts, automation accounts, or other non-human accounts.</td></tr><tr><td>Not identified</td><td>Flags accounts whose ownership cannot currently be verified.</td></tr></tbody></table>

### What happens after mapping?

Once a user is classified:

* The account ownership information is updated in Sprinto.
* Access reviews use the mapped user information during review cycles.
* Non-staff accounts are clearly identified and separated from employee accounts.
* Unidentified accounts remain visible for further investigation and remediation.
* Audit evidence reflects the latest user classification information.


---

# 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/identify-and-map-users-in-a-critical-system.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.
