- Introduction
- Balance
- Clusters
- Concept drift
- Coverage
- Datasets
- General fields (previously entities)
- Labels (predictions, confidence levels, hierarchy, etc.)
- Models
- Streams
- Model Rating
- Projects
- Precision
- Recall
- Annotated and unannotated messages
- Extraction Fields
- Sources
- Taxonomies
- Training
- True and false positive and negative predictions
- Validation
- Messages
- Access Control and 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 dataset 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 practices
- Analytics vs. automation use cases
- Turning your objectives into labels
- 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 (RBAC)
The role-based access control (RBAC) in Communications Mining is integrated with the AuthZ authorization system RBAC service of Automation Cloud. This integration allows you to assign roles to Automation Cloud user groups in Communications Mining. For more details on Automation Cloud groups, check the About accounts and groups and Managing access pages.
The RBAC experience is available to all Communications Mining users in Automation Cloud. Initially, RBAC is available for any newly created tenants, followed by its availability for existing tenants once they have been migrated to the new experience.
If you integrate with Automation Cloud through SSO, you can manage permissions through Automation Cloud user groups. Next, you can apply these permissions in Communications Mining to ensure a seamless and consistent access control experience. For more details, check Understanding authentication models.
Beginning in the week of February 24, 2025, existing Communications Mining tenants will be migrated to the new role-based access control (RBAC) experience. RBAC is integrated with Automation Cloud through the AuthZ authorization system, and allows administrators to provision roles to Automation Cloud groups as well as users.
The goal of the new experience is for the Communications Mining access management to be properly integrated with Automation Cloud, and allow users to assign roles to Automation Cloud groups instead of just users.
Communications Mining does not yet support custom roles. Therefore, we have mapped the granular Communications Mining legacy permissions to a set of temporary legacy roles. These will be deprecated in the future, when custom roles are supported.
The legacy roles are an exact mapping of the old permissions that required migrating, to ensure that none of the underlying permissions of the users were changed in the migration. For a complete list of the roles, check Legacy roles.
After the migration, your existing permissions are preserved; first through Automation Cloud roles. Then, we have used legacy roles to cover any gaps with additional permissions.
