Role permissions¶
Roles configure AI Studio workspace permissions. A member’s available operations depend on the selected role’s permission items and object scopes. For member assignments, see User management.
View roles¶
Search the role list or filter by status. The list shows role IDs, names, status, creation and update times, and descriptions. Available actions depend on the role and the operator’s permissions: view or edit permissions, manage inheritance, enable or disable, delete, and inspect logs.
Editing, status changes, and deletion are disabled for protected roles. Check the action’s current availability before proceeding.
Create and edit roles¶
The creation entry is available when the operator has permission and the permission context is ready.
Click Create role.
Enter a name and description.
Configure Global permissions or Object permissions.
Use the available validation or inspection controls to check the configuration.
Save, return to the list, and confirm the role’s status and description.
Changes affect subsequent permission checks for members associated with the role. Review their responsibilities before saving.
Configure global and object permissions¶
The role editor divides permission configuration into two page scopes:
Scope |
Configuration object |
|---|---|
Global permissions |
Permissions at workspace or feature-area level |
Object permissions |
Configure permissions for the specific resource selected on the page |
Only permission items and resource selectors displayed under Object permissions support object scopes. Configure the options shown in the current editor.
Row and column permissions on table data¶
Select a supported table and permission item under object permissions.
Choose the allowed columns and row conditions.
Check every value in multi-value conditions. For example,
NOT INexcludes the specified values; confirm that all exclusions remain after saving.Reopen the saved configuration, then query sample data using the authorized identity.
Check both allowed and excluded data. A successful request alone does not establish that the rules are correct.
View permissions¶
Open the role’s permission view to inspect global and object permissions. To change the configuration, return to the role editor and save the changes.
Role inheritance¶
Open the role’s inheritance entry to select a parent or add and remove relationships. Inspect both roles inherited by the current role and roles that inherit it. Use names and relationship labels together with graph direction.
For A inheriting B, check B among A’s inheritance sources and A among B’s inheritors. After a change, read the relationships and permission view again. Follow validation feedback for invalid relationships such as cycles.
If A inherits B, check B among A’s inheritance sources and A among B’s inheriting roles. After adding or removing a relationship, read relationships and permission views again. Resolve cycles and other invalid relationships using the page’s message.
These relationships govern role permissions; they are distinct from MatrixOne SQL GRANT and temporary permissions assigned directly to a member.
Role audit information¶
Role details provide audit records with operator, operation, status, and version information. Filter and paginate records to investigate configuration or relationship changes.
Inspect ownership information and the objects reported by a deletion check. Use the actions offered for those objects; an available transfer action does not imply permission to take over arbitrary resources.
Role ownership information¶
Select the role and start a deletion check.
Relationship to MatrixOne permissions¶
Manage MatrixOne database users, database roles, table permissions, and SQL grants separately under MatrixOne permissions.
Resolve user and object dependencies before deletion¶
Select the role in the role list and start a deletion check.
Inspect remaining user bindings, blocking dependencies, and objects awaiting transfer.
Follow the check’s links to resolve member bindings or object ownership. Before transferring ownership, confirm the receiving role, target object, and permissions.
Check again after resolving dependencies. If objects or ownership have changed, continue using the latest result rather than an older check.
Confirm deletion only after its conditions are met, then return to the list to verify it.
Visibility of the delete entry point does not mean protected roles or roles with unresolved dependencies can be deleted. Retain the specific failure message, then resolve the corresponding dependencies.