How access works
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).
Roles add up
A user with several roles gets everything those roles allow together. There is no "deny".
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.
Group and tag mean "either one"
A policy with Group X and Tag Z gives access to both circles, not only the overlap.
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 it | Limits access? |
|---|---|
| Users › Edit user › Resource Group | No |
| Roles › Edit role › Resource Group | No |
| Roles › Policy › Resource | Yes |
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.
| Role | Can |
|---|---|
| Administrator | Everything |
| Automation Engineer | Create and change devices, gateways, projects, pipelines, documents |
| Technician | Back up, deploy, run pipelines, save project versions |
| Read-Only User | View only |
How a user gets a role
| Way | Where |
|---|---|
| Directly | Users › user › add role. Optional expiry date. |
| Through SSO | Roles › 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