- Getting started
- Balance
- Clusters
- Concept drift
- Coverage
- Datasets
- General fields (previously entities)
- Labels (predictions, confidence levels, hierarchy, etc.)
- Models
- Streams
- Model Rating
- Projects
- Precision
- Recall
- Reviewed and unreviewed messages
- Sources
- Taxonomies
- Training
- True and false positive and negative predictions
- Validation
- Messages
- Administration
- Manage sources and datasets
- Understanding the data structure and permissions
- Create or delete a data source in the GUI
- Uploading a CSV file into a source
- Preparing data for .CSV upload
- Create a new dataset
- Multilingual sources and datasets
- Enabling sentiment on a dataset
- Amend a dataset's settings
- Delete messages via the UI
- Delete a dataset
- Export a dataset
- Using Exchange Integrations
- Model training and maintenance
- Understanding labels, general fields and metadata
- Label hierarchy and best practice
- Defining your taxonomy objectives
- Analytics vs. automation use cases
- Turning your objectives into labels
- Building your taxonomy structure
- Taxonomy design best practice
- Importing your taxonomy
- Overview of the model training process
- Generative Annotation (NEW)
- Dastaset status
- Model training and annotating best practice
- Training with label sentiment analysis enabled
- Understanding data requirements
- Train
- Introduction to Refine
- Precision and recall explained
- Precision and recall
- How does Validation work?
- Understanding and improving model performance
- Why might a label have low average precision?
- Training using Check label and Missed label
- Training using Teach label (Refine)
- Training using Search (Refine)
- Understanding and increasing coverage
- Improving Balance and using Rebalance
- When to stop training your model
- Using general fields
- Generative extraction
- Using analytics and monitoring
- Automations and Communications Mining
- Licensing information
- FAQs and more
Communications Mining User Guide
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.
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.
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.
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.
If segregation is very important and no data should be shared with other teams, consider using a separate Automation Cloud tenant.
- 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.
- Sources - View sources
- Datasets - View labels
- Streams - View streams
- Integrations - View integrations
- Alerts - View alerts
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.
