> 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/view-and-map-staff-access.md).

# View and Map Staff Access

The **Staff access** tab provides a centralised view of all employees and the systems they have access to. Sprinto automatically attempts to match users in connected systems with your organisation’s staff list and flags any mismatches or missing links.

You can review access per staff member, resolve mapping issues, and push fixes to your task tracker.

***

### View staff access overview

1. Go to **Data Library > Access > Staff access**.
2. Use the **search bar**, **staff role** filter, or **user status** filter to find specific individuals.
3. Each row displays:
   * **Staff name and email**
   * **Assigned role**
   * **Mapping status** (Mapped / Unmapped)
   * **User status** (Active / Inactive / Offboarded)
   * **Number of system accounts**
4. Click on the **download icon** next to the search bar to download a detailed staff access report.

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

Clicking on a staff member opens a detailed panel.

***

### View individual access details

Inside a staff member’s profile, you can view:

* **List of critical systems** associated with the user
* **Access status** (Active / Not connected / Orphaned)
* **Access level** (e.g. Admin, Viewer)
* **Last login timestamp**
* **Mapped user accounts**

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

This view helps you audit access granted to each user and identify any irregularities.

***

### Map user accounts to staff

If Sprinto detects a system user account that is not mapped to any staff member, you can manually resolve it:

1. Click **Map user to staff**.

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

2. Review the list of unmapped accounts from systems such as AWS, Okta, or Google Workspace.
3. Select the staff members from the list you wish to map.
4. Click **Identify and map user**.

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

5. Enter the required details.
6. Click **Save**.

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

Repeat this process to resolve all pending mapping issues.

***

### Fix mapping issues using task flows

For bulk mapping or when issues persist:

1. Click **Fix access issues** or **Fix 342 pending checks** (based on UI label).
2. Use the task flow drawer to:
   * Assign task owners
   * Escalate to HR/People Ops
   * Push resolution to Jira or another ticketing system
   * Enable **Active Sync** for real-time fixes

These automated workflows help reduce manual effort and accelerate mapping resolutions.

***

### Best practices

* Map all system accounts to corresponding staff records as part of onboarding.
* Periodically review mapping status to catch drift.
* Offboarded staff should be verified in the **Offboarded staff** tab to ensure all access is revoked.


---

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

```
GET https://docs.sprinto.com/data-library/access/dashboard-actions/view-and-map-staff-access.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
