> 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

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

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

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

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

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

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

4. Update the following as required:
   * Register name
   * Description
   * Selected systems
5. Click **Save changes**.

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

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

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

3. Review the confirmation message.
4. Click **Archive register** again to confirm.

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

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

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

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 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/create-and-manage-access-registers.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.
