# Access levels and permissions

Ototo sets access **per person, per company and per tool**.

Each tool is in a group, for example **Reports**. Each tool is one of three kinds:

- **R** (read): the tool reads data or runs a report.
- **W** (write): the tool creates or changes a record.
- **X** (delete): the tool deletes or voids a record, or makes it inactive.

For the full list of tools, see [All tools](../reference/tools.md).

## The access levels

| Level | What it allows |
| --- | --- |
| **No access** | The person cannot use the company. The company does not show in their assistant. |
| **Read only** | The person can find all data and run reports, but not employee information. They cannot make changes. |
| **Bookkeeper** | The person can read, create and change all data, but not employee information. They cannot delete. |
| **Full access** | The person can do all actions, including employee information, deletes and voids. |
| **Custom** | An admin sets the tools one by one. The web app shows **Custom** when the tools of a person are not the same as one level. |

## What each level includes, by group

| Group | Read only | Bookkeeper | Full access |
| --- | --- | --- | --- |
| Sales & payments | R | R W | R W X |
| Bills, vendors & purchases | R | R W | R W X |
| Customers | R | R W | R W X |
| Products & services | R | R W | R W X |
| Accounting | R | R W | R W X |
| Reports | R | R | R |
| Taxes | R | R | R |
| Company & settings | R | R W | R W X |
| Employees & time | None | None | R W X |

**Reports** and **Taxes** have only read tools.

## Change the access level of a person

**Who:** owners and admins.
**Where:** the Ototo web app, or your assistant with `ototo_set_access`.

1. In the web app, open **Team & permissions**.
2. Select the person.
3. Under **Company access**, find the company.
4. Click the level: **No access**, **Read only**, **Bookkeeper** or **Full access**.

The web app saves the change immediately.

From your assistant, ask for example: `Give maria@example.com Bookkeeper access on Acme Supplies.`
From an assistant, you can set a level on one company or on all companies.
You cannot set tools one by one from an assistant.

## Set tools one by one (Custom)

**Where:** the Ototo web app only.

1. In the web app, open **Team & permissions**.
2. Select the person.
3. Under **Company access**, click **Custom** on the row of the company.
4. Turn tools or groups on or off.

The web app saves each change immediately.

To start from a level, select it in **Permission set**.

To copy the access of a different person:

1. Open **Copy permissions from**.
2. Select a person and a company.

The access of that person replaces the current access.

> **Note:** If you select a level later, the level replaces the custom settings.

## Starting access

The organization has a starting access level. The default is **Read only**.

- People get this level on each company that an admin connects.
- People get this level when they join, if their invitation does not give a different level.

To change it, open the **Setup guide** and go to the step **Choose what Ototo can do**.

> **Caution:** In the **Setup guide**, **Save and continue** also sets this level for each person on each company that is connected now.

## Changes apply immediately

Ototo checks the access of a person each time their assistant uses a tool.
The assistant sees all tools, also the tools that the person cannot use.

If the person does not have access to a tool, Ototo tells the assistant:

- The tool, and the access level that includes it.
- For an admin: the link to the **Team & permissions** page.
- For a member: the names of the admins to ask.

After an admin changes the access, the person can ask again in the same chat.
They do not have to connect their assistant again.

## Company policy

The company policy can stop writes or deletes in a company for all people.
The policy can only make access smaller.
See [Company policy](../companies/company-policy.md).

**Activity:** the **Usage** page records each change to access, for example "Read only → Bookkeeper".
