This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
wiki:administration [2017/10/30 15:27] tda [Manage data] |
wiki:administration [2018/10/04 15:47] (current) ghi |
||
|---|---|---|---|
| Line 13: | Line 13: | ||
| ==== User ==== | ==== User ==== | ||
| - | User is dedicated to a customer – can perform all the operations on fleets, stations, clusters and end-devices 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 |
| ==== Reader ==== | ==== Reader ==== | ||
| Line 22: | Line 22: | ||
| ===== Configuration ===== | ===== Configuration ===== | ||
| - | This section allows you to configure: | + | This section allows you to configure via the Dashboard: |
| * Customers (group of fleets and clusters) | * Customers (group of fleets and clusters) | ||
| - | * Fleets (group of stations) | + | * Fleets (group of gateways) |
| - | * Stations | + | * Gateways |
| * Clusters (group of end-devices) | * Clusters (group of end-devices) | ||
| * End-devices | * End-devices | ||
| Line 41: | Line 41: | ||
| {{:wiki:admin_stations.png|}} | {{:wiki:admin_stations.png|}} | ||
| - | A similar behavior is observed when managing clusters and end-devices. | + | A similar procedure can be performed for managing clusters and end-devices. |
| For end-devices, here is how the activation parameters can be specified : | For end-devices, here is how the activation parameters can be specified : | ||
| Line 54: | Line 54: | ||
| * Super admins and admin users can create user accounts. | * Super admins and admin users can create user accounts. | ||
| * All other user roles can manage fleets, stations, clusters and end-devices | * All other user roles can manage fleets, stations, clusters and end-devices | ||
| + | |||
| + | ===== IDs ===== | ||
| + | |||
| + | All customers, clusters, fleets and users are identified with an ID. These IDs can be used to send [[wiki:oss_api| REST API]] commands. | ||
| + | |||
| + | ==== Customer ID ==== | ||
| + | |||
| + | Super Admin users can check customer IDs in the //Customers// page of web interface, in the top left of each customer element. \\ | ||
| + | |||
| + | {{:wiki:customerpage.png?600|}} | ||
| + | |||
| + | This ID can also be retreived by [[wiki:oss_api| 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. | ||
| + | |||
| + | ==== Cluster ID ==== | ||
| + | |||
| + | Super admin and admin users can check cluster IDs in the //Cluster// page, in the top right of each customer element. \\ | ||
| + | |||
| + | {{:images:clusterid.png?800|}} | ||
| + | |||
| + | This ID can also be retreived by [[wiki:oss_api| 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. | ||
| + | |||
| + | ==== Fleet ID ==== | ||
| + | |||
| + | Super admin and admin users can check fleet IDs in the //Fleets// page, in the top right of each customer element. \\ | ||
| + | |||
| + | {{:images:fleetid.png?800|}} | ||
| + | |||
| + | This ID can also be retreived by [[wiki:oss_api| 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. | ||
| + | |||
| + | ==== User ID ==== | ||
| + | |||
| + | Super admin and admin users can check user IDs in the //Users// page, in the top right of each customer element. \\ | ||
| + | |||
| + | {{:images:usersid.png?500|}} | ||
| + | |||
| + | This ID can also be retreived by [[wiki:oss_api| 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. | ||
| + | |||