Super Admin has a global view of the whole platform – whatever the customer.
Admin is dedicated to a customer – can perform all the operation limited to a specific customer
User is dedicated to a customer – can perform all the operations on fleets, gateways, clusters and end-devices limited to a specific customer
Same as USER but read only.
This section allows you to configure via the Dashboard:
Note: any given end-device can belong to one and only one cluster.
The gateways can be added manually, or as a batch using the CSV import feature:
A similar procedure can be performed for managing clusters and end-devices.
For end-devices, here is how the activation parameters can be specified :
Here is a brief overview of the roles and permissions:
All customers, clusters, fleets and users are identified with an ID. These IDs can be used to send REST API commands.
Super Admin users can check customer IDs in the Customers page of web interface, in the top left of each customer element.
This ID can also be retreived by REST API method getAuthenticatedUser
. Unlike the use of web interface, this REST API method can be used by all the users independently of their role.
Super admin and admin users can check cluster IDs in the Cluster page, in the top right of each customer element.
This ID can also be retreived by REST API method getClusters
. Unlike the use of web interface, this REST API method can be used by all the users independently of their role.
Super admin and admin users can check fleet IDs in the Fleets page, in the top right of each customer element.
This ID can also be retreived by REST API method getFleets
. Unlike the use of web interface, this REST API method can be used by all the users independently of their role.
Super admin and admin users can check user IDs in the Users page, in the top right of each customer element.
This ID can also be retreived by REST API method getAuthenticatedUser
. Unlike the use of web interface, this REST API method can be used by all the users independently of their role.