Skip to main content

How access works

The one rule

A user can do something only if at least one of their roles allows it.

Users get roles, roles hold policies​

A policy is an action (what) plus a resource (where).

User A has Role 1. Role 1 has a policy: read devices in Group X. User A can read Device 1 and Device 2.USERROLEPOLICYRESOURCESUser ARole 1ActionRead devicesResource: Group XGroup XDevice 1Device 2User A can read Device 1 and Device 2, nothing else.

Roles add up​

A user with several roles gets everything those roles allow together. There is no "deny".

Who can see Device 7 in Group Y? User A with Role 1 on Group X cannot. User B with Role 1 and Role 2 on All can. User C with Role 3 on Group Y can.User AUser BUser CRole 1 · Group XRole 1 · Group XRole 2 · AllRole 3 · Group YDevice 7Group YGroup X only"All" wins
warning

One role with All resources is enough to see everything of that type, whatever the user's other roles say.

A group includes its subgroups​

Choose a group in a policy and everything below it is included.

A policy on Group X covers Group X, Group X1 and Group X2, not Group Y or Group Y1.TenantGroup XGroup YGroup X1Group X2Group Y1CoveredNot covered

Group and tag mean "either one"​

A policy with Group X and Tag Z gives access to both circles, not only the overlap.

Group X and Tag Z combine: the user gets everything in either circle.Everything inGroup XEverything withTag Z

The Resource Group field on a user or role​

It decides where the user or role is managed, not what it can access.

Where you set itLimits access?
Users › Edit user › Resource GroupNo
Roles › Edit role › Resource GroupNo
Roles › Policy › ResourceYes

Example: User A is in Group X and has a role on All. User A still sees everything.

Always tenant-wide​

Policies for Audit Log, IDEaaS, Custom Fields and Vulnerabilities always cover the whole tenant.

Built-in roles​

They cover the whole tenant. To limit someone to a group, create your own role.

RoleCan
AdministratorEverything
Automation EngineerCreate and change devices, gateways, projects, pipelines, documents
TechnicianBack up, deploy, run pipelines, save project versions
Read-Only UserView only

How a user gets a role​

WayWhere
DirectlyUsers › user › add role. Optional expiry date.
Through SSORoles › Edit role › SSO Group Mapping. Members get it at sign-in.

Quick answers​

User A is in Group X but sees Group Y. Why?

One of User A's roles has a policy on All. Change it to Group X.

Can I block one thing?

No. Remove or narrow the role that grants it.

Two roles: which one wins?

Neither. The user gets both.

Temporary access?

Add the role with an expiry date.

See also: Role Based Access Control · Common resource scope