...
- Name
- A unique name for the Chariot Role.
- Permissions
- A list of permissions for the Chariot Role.
- Permissions have the form <domain>:<action>
- The <domain> represents a service within Chariot that can be interacted with through the Chariot UI. Some examples are:
- user
- The User Service for managing Chariot UI users
- See the Chariot UI under the "Users" tab
- role
- The Role Service for managing Chariot UI roles
- See the Chariot UI under the "Roles" tab
- mqttuser
- The MQTT User Service for managing MQTT Credentials
- See the Chariot UI under the "MQTT Credentials" tab
- system
- The System Service for configuring Server Name, HTTP, Certificates, and Backup/Restore
- See the Chariot UI under the "System" tab
- server
- The MQTT Server Service for configuring and controlling the MQTT server
- See the Chariot UI under the "MQTT Server" tab
- license
- The Licensing Service for licensing the Chariot MQTT Server software
- See the Chariot UI under the "License" tab
- The <action> represents the scope of this permission for the associated domain. The available actions are:
- read
- The permission to read/view resources, configurations, and/or data
- create
- The permission to create new resources and/or configurations
- update
- The permission to update resources and/or configurations
- delete
- The permission to delete resources and/or configurations
- action
- The permission to perform any actions available from a service within Chariot (such as starting/stopping the MQTT server or activating a license)
The "Add" button in the bottom right of the form can be clicked to create the Role.
...