Creating Roles & Using Permissions
All operations related to managing roles and permissions are made through /roles and /permissions pages.
These pages may be accessed by clicking on the User Management icon on RTLS Studio's Homepage.
Please note, that only rtlsadmin and users with appropriate permissions will be able to access this page.
Roles
Roles are simply sets of permissions. To give a user only some specific permissions, you have to create a role containing these permissions first.
There are three predefined roles in every RTLS Studio:
- rtlsadmin - a role with access to everything the RTLS Studio has to offer including user management;
- supervisor - a role with access to managing the whole system, except its users;
- observer - a role with access to getting information from RTLS Studio, not being able to make any changes to the system whatsoever;
Adding Role
1.) Click on ADD ROLE button in Roles tab of Users Management.
2.) Select a unique name for your new role.
3.) Select as many permissions as you want for this new role.
4.) Click ADD button.
Permissions
Permission | Description |
---|---|
access rtlsmanager | access RTLS Manager, control over the devices (tags, anchors) |
access sensmap | access Sensmap, it needs GET FROM API permission as well to be able to use Sensmap |
access sensmap3d | access Sensmap 3D, it needs GET FROM API permission as well to be able to use Sensmap 3D |
access sage | access Sage, manage charts, manage tag categories, manage dashboards |
access backup-restore | access Backup & Restore, empty database, manage backups, manage captures, update RTLS Studio |
access user himself | edit your profile |
access users | access Users, manage users, roles and permissions |
access io | access .IO, manage devices, events and actions |
access monitor | access RTLS Monitor, start, stop and restart RTLS services, monitor system |
get from api | obtain information from REST (view tags and anchors in Sensmap, list buildings from API, etc.) |
post to api | create new items via REST (create new plans, create new zones, etc.) |
put to api | edit existing items via REST (edit zones, change anchor's position, rename plan, etc.) |
delete from api | delete items from REST (delete zones, delete buildings, etc.) |