Groups and permissions

Netos uses NetBox's own groups and permissions. A permission says what a group may do on a table, such as view devices or change sites. Your sign-in groups decide which NetBox groups a person holds in each environment. This guide is for the administrator who decides who can do what.

What you need

  • A list of the levels of access you need, for example viewers (read everything) and engineers (edit inventory).
  • For each level, the environments it applies to: the same person can edit on lab and only read on production.
  • One group per level in your sign-in (Okta, Microsoft Entra ID), or a list of people per level for Netos ID.

The rules

  • Permissions are per table. A permission names a table, for example devices or circuits, and the actions allowed on it: view, add, change, delete.
  • A table permission covers all of its fields. A person who can view a table sees every field in it. There is no field-level filtering.
  • Permissions belong to groups, and people get them through groups. Assign permissions to groups, never to one person: you set a level once, and changing someone's access means moving them between groups.
  • Nothing else widens or narrows access. The sign-in, the zone and your AI assistant all work with the same NetBox permissions. There is no separate AI permission.
  • Access is per environment. Each of your sign-in groups is linked to NetBox groups on specific environments.
%%{init: {"themeVariables": {"mainBkg": "#eef2f7", "textColor": "#1f2937"}}}%%
flowchart LR
  P["Person"] --> S["Sign-in group<br/>for example netos-engineers"]
  S -->|"linked per environment"| G["NetBox group<br/>for example engineers on lab"]
  G --> T["Table permissions<br/>view, add, change, delete"]
  T --> R["What the person can see and change"]
  classDef step fill:#dbeafe,color:#1e3a8a,stroke:#2563eb
  class S,G,T step

Start from the Netos default groups

Setting up groups and permissions from nothing takes time, so Netos provides a standard set of groups and permissions to start from. On Netos Cloud, ask Netos to install it in your environments. On your own NetBox, it ships in the bundle as the netbox-rbac content package (see Content packages).

Treat the standard set as a starting point. Review each group and its permissions against how your teams work before you link your sign-in groups to it.

Steps

  1. Agree the levels of access and which environments each applies to.
  2. Create one group per level in your sign-in, or list the people per level for Netos ID.
  3. Send Netos the groups and the access each should get on each environment, for example netos-viewers: read on all environments; netos-engineers: edit on lab, read on production.
  4. Netos links each group to the NetBox groups on those environments and confirms.
  5. Test with one person per level (see the test checklist in the Okta or Entra guide).

To change what someone can do, change their group membership in your sign-in. It applies at their next sign-in. To change what a group can do, ask Netos.

When access is refused

A person in no linked group is refused at sign-in with Access denied.

A person who is signed in but lacks a table permission sees this message, in Netos and in their AI assistant:

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". The flow ID lets you, or Netos support, find the exact request.

To grant the access:

  1. Read the table named in the message.
  2. Decide which group should have that access on that environment.
  3. Move the person into that group in your sign-in, or ask Netos to give the group the permission.
  4. The person signs in again for the new groups to apply.

Changes and approvals

Holding a permission lets a person ask for a change. Changes made through an AI assistant also wait for a person to approve them in Netos Atlas, and run as the person who asked, with that person's permissions. See Permissions and approvals.

Troubleshooting

What you see Likely cause Fix
"Access denied" at sign-in The person is in no group linked to this environment Add them to a linked group
"Contact your administrator for access to <Table> ..." Their groups lack that table permission Move them to a group that has it, or ask Netos to add it
A group change has no effect Groups apply at the next sign-in Sign out and sign in again
Someone can see more than expected A table permission covers every field of the table Remove the table permission from their group, or move them to another group