Roles
Role-based access using permission blocks and assignments.
Roles are the normal way to give access in Atom.
A role is a friendly name for one or more permission blocks. A role assignment gives that role to an entity or principal group.
Example
That means meter-001 can read and publish to channels covered by the Plant-A permission block.
Role Parts
| Part | Meaning |
|---|---|
| Role | Name shown to operators, such as Plant-A Publisher. |
| Permission Block | The actual rule attached to the role. |
| Role Assignment | The row that gives the role to an entity or principal group. |
Principal Groups
Use principal groups when many subjects should receive the same role.
Each member receives the role through the group. Removing a device from the group removes that inherited access.
Object Groups
Use object groups when one rule should apply to many protected objects.
A permission block can target direct objects in the group, descendant objects, child groups, or descendant groups.
Admin Access
Platform administrators use permission blocks with broad scopes and management actions. Tenant administrators use tenant-scoped permission blocks. The same evaluation engine handles both.