User Roles and Scopes for MindConnect Nano¶
There are multiple roles that are available for MindConnect device controlling. A device can be configured and can send the command to the device by an “Admin” user. If you want to ensure that a user cannot configure but can send a command, then you can use “DeviceCommander” role. If you want to ensure that a user can configure but cannot send a command, then you can use “DeviceConfigurator” role.
The following table shows the list of MindConnect device roles and scopes:
|User role||Functionality or Scope|
|StandardUser (uipluginassetmanagermcnano:user)||This role grants the permission to visualize the MindConnect device plugin, but cannot change the device configuration and cannot send commands to the device.|
|DeviceConfigurator (uipluginassetmanagermcnano:deviceconfigurator)||This role grants the permission to visualize the MindConnect device plugin and update the device configuration, but cannot send commands to the device.|
|DeviceCommander (uipluginassetmanagermcnano:devicecommander)||This role grants the permission to visualize the MindConnect device plugin and can send the commands to the device, but cannot update the device configuration.|
|Admin (uipluginassetmanagermcnano:admin)||This role grants the permission to configure and command the MindConnect device.|
By default, these roles are not enabled on the tenant. To enable these roles you need to navigate to the "Settings" app.
In "Settings" app, click on "Roles" tab and click to enable the new roles. For more information about roles, see "Roles" chapter in "Settings" documentation.
In case of role change, you need to logout and login. It might take up to 15 minutes for the current configuration to be effective depending on the system.
Any questions left?
Except where otherwise noted, content on this site is licensed under the MindSphere Development License Agreement.