# A dedicated action account

Separate writing from collection, with only the privileges needed.

## Why a second account

The collection account is read-only: that is what protects your infrastructure. The hypervisor therefore refuses any write made with it, console included. It is the first cause of a correctly granted capability that does not work.

## The steps

1. Open **Settings › Infrastructure actions › Write access**, and tick the capabilities you want on the source, under **2. Targets**.
2. Expand **Privileges to grant on the hypervisor, and a ready-to-paste script**: the screen only gives what the ticked capabilities require.
3. On the hypervisor, create the account, and run this script.
4. Open **Data sources**, at the bottom of the sidebar, then the settings of the source.
5. Under **Action account**, enter this account, and save.

The secret is encrypted, and the collector is the only one to use it against the hypervisor: it never reaches your browser.

> Tick what you need, no more: the script is regenerated with each capability added. One more capability means running the script again on the hypervisor.

## Reduce the scope further

A permission set at the root is the simplest, and the widest. Limit it if your platform allows it: a folder or cluster on vSphere, a pool or machine on Proxmox, a project or category on Nutanix.

Some platforms only offer fixed roles. Naoshift then picks the lowest one that covers your capabilities, and the screen says so.

### The action account is empty, what happens?

Naoshift falls back on the collection account, and warns you. The action will almost certainly come back **refused**, naming the missing privilege: you will know what to grant.

### Proxmox refuses the console ticket or the action

Proxmox VE console and action operations refuse API tokens, whatever their privileges. Enter a username and password, on an account without TOTP. A token works perfectly well for collection.

### I added a capability, and it is refused

The existing account does not have its privilege yet: run the updated script again.
