Understanding Roles & Permissions
Your role controls which people, organisations, assets and actions are available to you. This article outlines the different roles that exist within TMdesk and their responsibilities.
Purpose of Roles
The roles within TMdesk help us administer the platform and ensure that users have appropriate permissions for their job function. By having clearly defined roles and permissions we ensure the integrity and security of the data, maintain privacy and access and minimise user error. Roles differ between customer organisations and Traffic Group Signals.
Customer roles
|
Role |
Typical access |
|
Manager |
Manages users for their own organisation and can work with owned or operated equipment where permitted. |
|
Operative |
Views and works with equipment operated by their organisation. Intended for day-to-day field use. |
TGS roles
- System Admin. Has overall responsibility for TMdesk and the highest level of user and organisation control.
- Administrator. Handles day-to-day TMdesk administration across organisations and equipment.
- Engineer. Uses broad visibility to support and diagnose equipment, with fewer administrative permissions.
Who creates accounts?
- The System Admin creates TGS Administrator accounts.
- A TGS Administrator creates one or more Manager accounts for a customer organisation.
- The customer Manager creates and maintains Operative accounts for that organisation.
Permission-sensitive actions: Editing asset ownership, marking an asset as found, sending controller protection commands and changing organisation settings are restricted. If a control is missing, your role or relationship to the asset may not permit that action.