Permissions and approvals for AI assistants
Your AI assistant works in Netos as you. It sees what you can see, it can only ask for changes you are allowed to make, and every change waits for a person to approve it in Netos Atlas. This guide is for users of Claude, ChatGPT or Copilot with Netos, and for the Netos administrators who grant their access.
What you need
- A connected assistant. See AI assistants.
- The table permissions for what you want to read or change. See Groups and permissions.
- Someone who can approve changes in Netos Atlas.
The rules
- Permissions are NetBox table permissions. Access is granted per table. A user with access to a table gets all of its fields. The assistant, the zone and the sign-in never narrow or widen this; there is no separate AI permission.
- Access comes from groups. Your sign-in groups map to NetBox groups per environment, so the same person can edit on a lab environment and only read on production.
- Writes need an approval in Netos Atlas. The assistant stages a change, and it is written only after an approver approves it in Atlas. A staged change can be discarded instead.
- The change runs as the person who asked for it, not as the approver. It still needs that person's table permissions.
- One approver is enough for a change. Netos asks for two only for destructive production actions, or where your organization opts in.
- No payments. Contracts, invoices and run rates are records. The assistant never moves money.
How a change is approved
sequenceDiagram
actor U as You
participant C as AI assistant
participant A as Netos Atlas
actor P as Approver
participant N as NetBox
U->>C: Ask for a change
C->>A: Stage the change as you
A->>C: Awaiting approval, with a review link
C->>U: Review link
P->>A: Review and approve, or discard
A->>N: Write the change as you
A->>C: Result
Steps
Ask for a change
- Ask your assistant for the change, for example "Stage this device spreadsheet for import."
- The assistant returns a review link to the run in Netos Atlas. The run shows awaiting approval.
- An approver opens the link, reviews the change and approves or discards it.
- Ask the assistant for the result, or open the run in Atlas.
When access is refused
If a request needs a table you cannot use, the assistant shows this message:
Contact your administrator for access to
<Table>, which was blocked when trying to access via<tool>, for flow ID<id>.
For a refused change, the table names the action, for example "change Devices" or "add Tags". Send the full message to your Netos administrator. The flow ID lets them, or Netos support, find the exact request.
Grant access (administrators)
- Read the table named in the message.
- Decide which group should have that access on that environment.
- Add the user to that group in your sign-in, or ask Netos to link the group to the right NetBox group.
- The user signs in again for the new groups to apply.
Example
Sam asks Claude to update the serial number of a device on production.
- Sam's group can read devices on production but not change them. Claude shows: "Contact your administrator for
access to change Devices, which was blocked when trying to access via
<tool>, for flow ID<id>." - Sam sends the message to the Netos administrator, who moves Sam into the engineers group. Sam signs in again.
- Sam asks again. Claude stages the change and returns a review link.
- A team lead approves it in Netos Atlas. The change is written as Sam.