Skip to main content

Module Permissions

Module permissions configure the access level for each user by feature module, on top of the role. The role sets the visible range in the sidebar, and module permissions decide whether a user can enter a feature page and call its APIs.

Module permission configuration

Configuration

ItemContent
Single userManage → Users → the "Permissions" row action for that user
Batch configurationManage → Users → select users → "Batch actions → Batch Set Permissions"
PermissionsViewing the permission matrix requires "View Users", and modifying requires "Manage Users"
Role scopeAdministrators can modify any user; other roles can modify only users whose role rank is strictly lower
Administrator exceptionAn administrator's effective permissions are always read/write on everything and are not configured in the user permission dialog

Permission Levels

When configuring a user, each module takes one of the following four values.

LevelMeaning
Inherit role defaultWrites no user override and keeps the value from the role default template
DenyThe page cannot be entered and the API denies access
Read OnlyCan view but cannot change
Read & writeCan view and operate

Effective Rules

OrderRule
1The user-level override takes precedence
2With no override, the value from the role default template applies
3With no override and no role default, the value is "Deny"
AdministratorBypasses the rules above and always has read/write on every module

The platform writes the role default templates during initialization. When viewing a user's permission matrix, the dialog lists three columns at once: "Role Default", "Custom Override", and "Effective".

Certain permissions satisfy the requirements of others, so they do not need to be granted again.

Granted read/write permissionsRequirements met
Dataset Annotation, Perform Annotation, Review AnnotationThe read-only requirement of Dataset List
Perform Annotation, Review AnnotationThe read-only requirement of View Annotation Tasks
Perform Annotation, Review AnnotationThe read/write requirement of Dataset Annotation

Configuration Steps

To configure a single user:

  1. Find the target user in the user list and click "Permissions".
  2. Set the "Custom Override" for each module in the dialog.
  3. Click "Save" to submit the changes; click "Reset All to Role Defaults" to clear every override for that user.

To configure in bulk:

  1. Select the target users in the user list.
  2. Click "Batch actions" and choose "Batch Set Permissions".
  3. Select the module and the value, then click "Confirm".

Skipped users are reported with the reason in the result message.

Permission Reference

There are 50 configurable module permissions across 6 groups. The interface shows them by group, and the permissions in each group are listed below.

Overview

PermissionScope
View OverviewMetrics and recent activity on the Overview page

Data

PermissionScope
Dataset ListList, search, and preview on the data management page
Dataset AnnotationStart annotation and maintain data tags
Dataset ExportOpen the dataset export page
Dataset Compute / PreprocessCompute operations such as updating metadata
Data UploadUpload data and import external datasets
View Collection TasksView the list and progress of collection tasks
Manage Collection TasksCreate, edit, and delete collection tasks and change their status
View DictionariesView annotation definitions such as skills, objects, and tags
Manage DictionariesMaintain annotation definitions
View ChartsView analysis charts
View Skills / ActionsView the skill library and action data
Manage Skills / ActionsMaintain the skill library and action data
View TeleoperationRead device registration and activation records
Manage TeleoperationRegister and delete robot devices

Annotation Tasks

PermissionScope
View Annotation TasksView the task list and task details
Perform AnnotationClaim tasks and submit annotation results
Review AnnotationReview annotation results and mark them as passed or returned
Manage Annotation TasksCreate tasks, assign people, and change task status

QC & Export

PermissionScope
View QCView QC rules and QC reports
Run QCStart QC jobs
QC Rule ManagementMaintain QC rules
View Export ListView the export history
Create Export JobStart an export

Model

PermissionScope
View TrainingView training jobs and metrics
Create Training JobStart training
View InferenceView inference services and test results
Manage Inference JobsDeploy and take inference services offline

System Management

PermissionScope
View ProjectsView the project list and project details
Manage ProjectsCreate, edit, and delete projects and maintain members
View UsersView the user list and permission matrix
Manage UsersCreate users, assign roles, and configure module permissions
View RobotsView robot models and maintenance records
Manage RobotsRegister and maintain robot models
View DevicesView the device list and monitoring data
Manage DevicesRegister devices, dispatch tasks, and take over remotely
View Cloud StorageView cloud storage connections
Manage Cloud StorageCreate and maintain cloud storage connections
View WorkflowsView matching rules, action rules, and workflows
Manage WorkflowsMaintain workflow configuration
View PluginsView installed plugins
Manage PluginsInstall, enable, and disable plugins
View TrashView soft-deleted data
Restore / Empty TrashRestore or permanently delete data
View QuotasView quotas and usage for export, training, and inference
Manage QuotasAdjust quotas
View System SettingsView system parameters and branding settings
Edit System SettingsEdit system parameters and branding settings
View Ops MonitorView system logs, task queues, and audit records
Manage Ops MonitorPerform operations actions

Constraints and Limits

ItemValue and description
Operator rankAdministrators can modify any user; other roles can modify only users whose role rank is strictly lower
Grant ceilingCannot grant a permission above one's own effective level; lowering a level and "Reset to role default" are always allowed
Administrator targetAdministrator accounts have no override; batch settings skip them and give the reason
Unconfigured defaultWhen a module has neither an override nor a role default, the value is "Deny"
CacheEffective permission results are cached for 5 minutes; a permission change immediately invalidates the cache for that user or role
ScopeModule permissions constrain page access and API calls; sidebar entries are filtered by role and do not change with module permissions

Troubleshooting

SymptomPossible causeResolutionOwner
Permissions do not change after savingThe permission data in the active login session is not refreshedHave that user sign in againAdministrator
Message "Cannot grant the level for the module"The granted level is above the operator's effective levelHave an administrator perform it, or use a value no higher than one's own levelAdministrator
Message "Cannot modify permissions for a user with role X"The target's role rank is not lower than the operator'sHave a higher-ranked role perform itAdministrator
Batch settings show "Skipped N users"The target includes an administrator, or a target's rank is not lower than the operator'sHave an administrator perform itAdministrator
A page redirects to the home pageThe module permission is set to DenyGrant the matching permission in user permissionsAdministrator
The API returns 403The matching permission is missingGrant the matching permission in user permissionsAdministrator

Audit

Permission changes are written to the permission audit record, which includes the operator, the target user, the before and after values, and the source address; a denied module access is recorded as well.

For business operations such as users and projects, see "Operations → Logs → Operation logs".

PagePurpose
User ManagementCreate accounts and assign roles and projects
Project ManagementProject members and visible scope
PermissionsRoles and the visible menu range
Ops MonitorOperation logs and login logs