> ## Documentation Index
> Fetch the complete documentation index at: https://docs.izumi.akiaconsulting.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How access works

> Who sees what in Izumi, and why.

Checked on Izumi 0.5.7, 2026-11-21.

Access in Izumi rests on three terms: company, domain and role. The same rules apply to you and to every AI tool you connect.

## Company, domain and role

* The company is the data boundary. Another company does not see your documents, sources or access records.
* Inside a company there are domains, areas of knowledge such as Finance or HR.
* A role binds a person to one domain. A member sees only documents from domains where they have a role.

| Role | What it does |
| - | - |
| **Reader** | Reads and searches the documents of a domain. |
| **Editor** | Everything a reader does, sends web clips into the domain and approves or rejects the proposed notes of that domain. |
| **Company admin** | Manages members, domains, sources and settings. Is not automatically an editor of any domain. |

## An AI tool has your rights, no more

* A connected AI tool sees only what you may see, in all your companies.
* When you connect over OAuth, reading is always on. Proposing notes is optional and you can switch it off when you connect. You can narrow a personal token to some companies and domains.
* The connection lasts at most 90 days. You revoke it yourself on **My tokens and profile**.

## How people get in

* By invitation only. The server operator creates the first one, a company admin creates all others. The link is valid for 72 hours and works once.
* Izumi does not send email (from the code). The admin sends the link through a channel they trust.
* There are no passwords: you sign in with a Google or Microsoft account. Google was checked live, signing in with a Microsoft account was not.

## Who decides on proposals

* The editor of the domain the proposal is for decides, in the **Review queue**.
* A company admin who is not an editor does not see that domain's proposals. Every domain needs at least one editor, otherwise proposals wait until they expire.

## Who asked what

* The **Access log** records every call: from the web, from AI tools, from the web clip extension and through the push API. An admin sees everyone in the company, a member sees only their own.
* A document title in the log is visible only to someone who may read that document. Everyone else sees just a count.
* How long records are kept is set by the company, 365 days by default.

## Limits

* What you may not see appears in neither the results nor the result count.

> [!WARNING]
>
> Not checked live yet: accepting an invitation all the way with a second account, suspending and removing a member, restricting sign-in by Google domain or Microsoft tenant, signing in with a Microsoft account, proposals expiring after 30 days, a regular member's view of search and of the log, and deleting records when the retention period ends.

## Next

* For admins: [Companies, domains, roles](https://docs.izumi.akiaconsulting.com/en/admin/companies-domains-roles.md), [People and invitations](https://docs.izumi.akiaconsulting.com/en/admin/people.md), [Review queue](https://docs.izumi.akiaconsulting.com/en/admin/review-queue.md) and [Access log](https://docs.izumi.akiaconsulting.com/en/admin/access-log.md).
* For users: [Proposals and review](https://docs.izumi.akiaconsulting.com/en/using/proposals.md), [My tokens and log](https://docs.izumi.akiaconsulting.com/en/using/tokens-and-log.md) and the [AI tools overview](https://docs.izumi.akiaconsulting.com/en/ai-tools/overview.md).
* How sign-in is set up: [Sign-in (Google, Entra)](https://docs.izumi.akiaconsulting.com/en/install/sign-in.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.