# The operator role and the three locks

Understand why a button is missing, and know who can open it.

## One capability, three locks, one role

Collection stays read-only, whatever happens. Acting relies on separate **capabilities**, closed by default: power, snapshots, migration, console. A capability only works if all of this is open at the same time:

| Condition | The question | Who decides |
|---|---|---|
| **The company** | Has it subscribed to this capability? | Naoshift |
| **The connector** | On this source, and with which account? | A company administrator |
| **The person** | Who on the team may use it? | A company administrator |
| **The Infrastructure operator role** | Does this person work on the infrastructure? | A company administrator |

Closing any one of them cuts everything off. Withdrawing a capability even cancels an action that was requested and has not left yet.

> Being a company administrator grants no write access on the hypervisor: it is a separate axis. An administrator can grant themselves a capability, but that level alone makes no button appear.

## The steps

1. Open **Settings › Infrastructure actions › Write access**. This screen is reserved for company administrators.
2. Under **1. Tenant**, read what is open. If the capability you want is closed, ask Naoshift: only Naoshift changes this level.
3. Under **2. Targets**, tick the capability on the source concerned.
4. Under **3. Users**, give the person the **Infrastructure operator** role, click **Apply**, then grant them the capability.

## Opening in bulk

Several people or several connectors? Create a capability **role**, or a **connector group**, on the same screen. Removing from the role or group removes from everyone, and the screen says where an inherited capability comes from.

## What someone without the right sees

No button: no greyed-out button, no tooltip. Only two entries of the sidebar's **Actions** group, **Deploy** and **Migrations**, stay visible with a padlock: they say, condition by condition, what this account is missing.

### Everything looks ticked, and the action is still refused

Look at **1. Tenant** first. It is the most frequent block: targets and people ticked, company lock closed. Next comes the account used on the source: see the next lesson.

### A capability cannot be ticked on a source

The collector declares what it can do. The box says why: a collector to update from **Data sources**, or a platform that does not offer this action.

### A person has the capability, but sees no button

Without the **Infrastructure operator** role, a capability has no effect. The screen flags it on their row.
