Role-Based Access Control

This section describes the Role-Based Access Control (RBAC) experience in Communications Mining™ .

Role-Based Access Control (RBAC) in Communications Mining™ is integrated with Automation Cloud’s AuthZ RBAC service. This integration allows you to assign roles within Communications Mining to user groups in Automation Cloud. For more details, read about accounts and groups and managing access in the Automation Cloud guide for more information.

Note: The RBAC experience is currently available on demand for new tenants in Communications Mining by request to the Product team.

SSO Integration

If you integrate with Automation Cloud via Single Sign-On (SSO), you can manage permissions through user groups in Automation Cloud. These permissions can then be applied within Communications Mining, ensuring a seamless and consistent access control experience. Check out authentication in Automation Cloud in the Automation Cloud guide for more information.

Data segregation when provisioning project roles

When you provision project roles to groups, users in those groups will have access to any projects the groups are added to. This means they will see the data within those projects, which might not be appropriate for a large group of users, especially in regulated industries. Learn more about the data structure and permission hierarchy in Communications Mining.

When using SSO

We recommend segregating groups at relevant and appropriate access levels. For example, if only a limited set of users should access each project, create per-project groups to provision access to each project. Otherwise, unauthorized people might access the data.

Hinweis:

If segregation is very important and no data should be shared with other teams, consider using a separate Automation Cloud tenant.

When using Automation Cloud groups

When you use Automation Cloud groups, consider whether everyone in the group should have access to the data in the projects. This ensures that you only grant access to the right people and maintain proper data security.

Roles in Communications Mining

Note: The CM Tenant Admin role has been renamed to CM Service Admin.

The following roles apply for Communications Mining:

• UiPath Organization Admin: While this role is not specific to Communications Mining, Organization administrators in Automation Cloud can assign roles to anyone in Communications Mining.
• CM Service Admin: This role is the Communications Mining Service Administrator for the Tenant. CM Service Admins can create and delete projects, and perform tenant-level administration tasks. UiPath Organization administrators are automatically granted this role.
• CM Project Admin: This role allows you to manage a project, including users, integrations, sources, datasets, models, streams, and alerts. You cannot create or delete projects.
• CM Model Trainer: This role allows you to view a project, review and label data, update dataset settings, and pin model versions. You can create datasets but you cannot delete them.
• CM Developer: This role allows you to view a project, upload and export data, configure integrations, pin model versions, manage streams, and consume predictions from them. You cannot review and label data, nor create, update, or delete datasets and alerts.
• CM Analyst: This role allows you to view a project and create, update, and delete dashboards and alerts. You cannot import or export data, review and label data, modify or consume streams, or set up integrations.
• CM Viewer: This role allows you to view a project. You cannot create, update, or delete anything.

Each role definition includes the set of actions (permissions) that it allows. For example,the CM Viewer role has the following permissions:

• Quellen – Quellen anzeigen
• Datasets – Beschriftungen anzeigen
• Streams – Zeigen Sie Streams an
• Integrationen – Integrationen anzeigen
• Warnungen – Warnungen anzeigen

For details on the specific roles available, and the permissions that they grant, check out User permissions explained. Permissions are not assigned individually to users. Instead, users are assigned roles, which provide a set of underlying permissions to perform certain actions.