- Introduction
- Setting up your account
- Balance
- Clusters
- Concept drift
- Coverage
- Datasets
- General fields
- Labels (predictions, confidence levels, label hierarchy, and label sentiment)
- 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
- Creating or deleting a data source in the GUI
- Uploading a CSV file into a source
- Preparing data for .CSV upload
- Creating a dataset
- Multilingual sources and datasets
- Enabling sentiment on a dataset
- Amending dataset settings
- Deleting a message
- Deleting a dataset
- Exporting a dataset
- Using Exchange integrations
- Model training and maintenance
- Understanding labels, general fields, and metadata
- Label hierarchy and best practices
- Comparing analytics and automation use cases
- Turning your objectives into labels
- Overview of the model training process
- Generative Annotation
- Dastaset status
- Model training and annotating best practice
- Training with label sentiment analysis enabled
- Training chat and calls data
- Understanding data requirements
- Train
- Introduction to Refine
- Precision and recall explained
- Precision and Recall
- How validation works
- Understanding and improving model performance
- Reasons for label 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™
- Developer
- Exchange Integration with Azure service user
- Exchange Integration with Azure Application Authentication
- Exchange Integration with Azure Application Authentication and Graph
- Fetching data for Tableau with Python
- Elasticsearch integration
- Self-hosted Exchange integration
- UiPath® Automation Framework
- UiPath® Marketplace activities
- UiPath® official activities
- How machines learn to understand words: a guide to embeddings in NLP
- Prompt-based learning with Transformers
- Efficient Transformers II: knowledge distillation & fine-tuning
- Efficient Transformers I: attention mechanisms
- Deep hierarchical unsupervised intent modelling: getting value without training data
- Fixing annotating bias with Communications Mining™
- Active learning: better ML models in less time
- It's all in the numbers - assessing model performance with metrics
- Why model validation is important
- Comparing Communications Mining™ and Google AutoML for conversational data intelligence
- Licensing
- FAQs and more
Communications Mining user guide
This section addresses Automation Cloud users and describes how to manage your projects and user access on existing projects.
The role-based access control (RBAC) in IXP/CM product name 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 IXP/CM product name. For more details on Automation Cloud groups, check the About accounts and groups and Managing access pages.
The RBAC experience is available to all IXP/CM product name 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.
Single sign-on (SSO) integration
If you integrate with Automation Cloud through SSO, you can manage permissions through Automation Cloud user groups. Next, you can apply these permissions in IXP/CM product name to ensure a seamless and consistent access control experience. For more details, check Understanding authentication models.
Migrating to the new RBAC experience
Beginning in the week of February 24, 2025, existing IXP/CM product name 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 IXP/CM product name access management to be properly integrated with Automation Cloud, and allow users to assign roles to Automation Cloud groups instead of just users.
IXP/CM product name 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 during 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.
