> 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/create-and-manage-access-registers.md).
# Create and Manage Access Registers
Create, organise, and manage access registers to group critical systems for streamlined access reviews and compliance monitoring.
Access registers let you group related systems into a single register for managing user access and conducting access reviews. You can create registers based on business functions, departments, environments, or any other organisational requirement.
You can also update a register by modifying its details or assigned systems, and archive registers that are no longer in use.
### Before you begin
* Ensure your critical systems have been added to **System Access**.
* You must have permission to create and manage access registers.
***
## Create an access register
1. Log in to the Sprinto dashboard.
2. Navigate to **Data Library > System Access**.
3. On the **Access registers** tab, click **Create Register**.
4. Enter a **Register name**.
5. (Optional) Enter a **Description**.
6. Under **Select systems**, choose the systems you want to include in the register.
* Select individual systems.
* Use the search bar to find a specific system.
* Select **Select all** to include every available system.
7. Click **Create register**.
The access register is created and appears in the **Access registers** list.
***
## Edit an access register
You can update the register name, description, or the systems assigned to a register.
1. Navigate to **Data Library > System Access > Access registers**.
2. Open the access register you want to edit.
3. Click **Edit details**.
4. Update the following as required:
* Register name
* Description
* Selected systems
5. Click **Save changes**.
Your changes are applied immediately.
***
## Archive an access register
Archive a register when it is no longer required. The systems assigned to the register are retained and restored if the register is unarchived later.
1. Open the access register.
2. Click **Archive register**.
3. Review the confirmation message.
4. Click **Archive register** again to confirm.
The register status changes to **Archived** and it can no longer be used until it is restored.
***
## Unarchive an access register
You can restore an archived register at any time.
1. Open the archived access register.
2. Click **Unarchive register**.
The register is restored along with all previously assigned systems.
***
### What happens next?
After creating an access register, you can:
* Review the systems included in the register.
* Monitor access across grouped systems.
* Perform access reviews for the selected systems.
* Update the register as your infrastructure changes.
* Archive registers that are no longer required.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.sprinto.com/data-library/access/dashboard-actions/create-and-manage-access-registers.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
