> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to Run an Annual Access Review
- URL: https://blog.jestor.com/run-annual-access-review/
- Published: 2026-09-17T22:33:36.000Z
- Updated: 2026-09-17T22:33:36.000Z
- Author: Bruno Bannach

An **annual access review** answers three questions: who has access, what does that access permit, and does it still match what each person does.

## Why access drifts

Access is granted continuously and revoked almost never.

- Permissions granted for a project that ended
- Builders who should have become members
- Role membership nobody has checked since creation
- Super root held by more people than anyone realizes

## The review, step by step

| Step                   | What to confirm                        |
| ---------------------- | -------------------------------------- |
| **Filter by status**   | Inactive users are genuinely inactive  |
| **Filter by type**     | Every builder still needs to build     |
| **Review roles**       | Each grants what its function requires |
| **Check super root**   | One or two people at most              |
| **Sample the history** | What people actually changed           |

## How to do it in Jestor

1. Open user management in **Jestor** and filter by status.
2. Filter by type to isolate builders, members, and viewers.
3. Open the roles area and review each role's access, noting its ID.
4. Confirm super root is held by one or two people at most.
5. Export a filtered slice of the table history as evidence of the review.

## Why choose Jestor for access governance?

**Jestor** keeps removed users as inactive rather than deleting them, so historical changes always resolve to a person — which is what an access review usually needs to explain.

Role IDs are visible in the roles area, closing a gap where exported user lists previously lacked the identifier needed to match them against roles.

## Frequently Asked Questions

### How often should this run?

At least annually, and after any significant reorganization. See [jestor.com](https://jestor.com/?ref=blog.jestor.com).

### Can I filter users by type?

Yes, builders, members, and viewers each have an icon.

### What evidence should I keep?

An export of the filtered change history.

## Video Tutorial: Step by Step

Check out other practical tutorials on the Jestor YouTube channel.

## Get to know Jestor

With **Jestor**, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by **AI**. Discover Jestor at [jestor.com](https://jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.