User Administration > User roles > System-defined roles
  

System-defined roles

Informatica Intelligent Cloud Services provides system-defined roles that you can assign to users or user groups. You can't change or delete the system-defined roles.
The system-defined roles that you can assign to users and groups vary based on your organization's licenses. For example, if your organization has no access to Application Integration, you can't assign the Application Integration Business Manager or Application Integration Data Viewer role to any user or group in your organization.
There are two types of system-defined roles:
Cross-service roles
Cross-service roles define access privileges across multiple services. For example, users with the Deployer role can access some features in API Center, API Manager, Application Integration, Application Integration Console, Data Quality, and Mass Ingestion.
Service-specific roles
Service-specific roles define access privileges for one service or for a group of closely related services. For example, users with the Governance User role can access Data Governance and Catalog but have no access to other services unless you assign additional roles.
Note: Don't assign the system-defined role "Dataloader admin" to any users. This role is used with Informatica Data Loader only.

Cross-service roles

Cross-service roles are system-defined roles that define access privileges across multiple services.
The following table describes the cross-service roles:
Cross-service role
Provides access to...
Description
Admin
All services
Role for organization administrators. Provides full access to all licensed services with the following exceptions:
  • - Doesn't provide privileges to enable or disable the use of customer managed encryption keys for the organization. To provide these privileges, assign the user both the Admin and Key Admin roles.
  • - Doesn't provide full access to all MDM services. For example, doesn't allow the user to access the workflow inbox or create hierarchies in MDM business services. To provide full access to MDM services, assign the user an appropriate MDM service-specific role.
Tip: Best practice is to assign the Admin role to one or two trusted users and assign the users to an administrative user group that has full permissions on all asset types. These users can act as alternative organization administrators and can help troubleshoot access control and other organization security issues.
Data Integration Data Previewer
  • - Data Integration
  • - Data Profiling
  • - Data Quality
  • - Data Validation
Supplemental role that allows designers to preview data while creating mappings, tasks, profiles, and test cases. Allows users to perform the following tasks:
  • - Preview data in a mapping or task in Data Integration.
  • - Preview data on a data quality transformation in a mapping in Data Integration.
  • - View source object data for profiles and profile results in Data Profiling.
  • - Preview data while creating test cases in Data Validation.
Note: This is a supplemental role. Assign this role with another role, such as the Designer role, to ensure that users can access Data Integration, Data Profiling, and Data Validation.
Data Integration Task Executor
  • - Data Integration
  • - Data Access Management
Role for running tasks and taskflows and executing data access policies. Allows users to perform the following tasks:
  • - View assets and asset details in Data Integration.
  • - Run tasks and taskflows and test-run mappings in Data Integration.
  • - View user's own data integration jobs and job details in Data Integration.
  • - Start and stop user's own jobs in Data Integration.
  • - Download session logs in Data Integration.
  • - Execute data access policies in Data Integration.
  • - Access Data Access Management.
  • - View data access policies in Data Access Management.
Deployer
  • - API Center
  • - Application Integration
  • - Application Integration Console
  • - Data Quality
  • - Mass Ingestion
  • - Data Validation
Role for users that deploy assets and processes. Allows users to perform the following tasks:
  • - View and deploy assets, assign policies, manage organization settings, and add OAuth 2.0 clients in API Center when assigned with the Service Consumer role.
  • - View asset details in Application Integration.
  • - Deploy assets, view settings, and upload and deploy Process Developer-generated orchestration artifacts (BPRs) in Application Integration Console.
  • - View asset details except dictionary data in Data Quality.
  • - View application ingestion, database ingestion, and streaming ingestion tasks in Mass Ingestion.
  • - View test cases, test suites, and reports in Data Validation.
  • - Run test cases and test suites in Data Validation.
Designer
  • - Administrator
  • - API Center
  • - Application Integration
  • - Application Integration Console
  • - B2B Gateway
  • - Data Integration
  • - Data Profiling
  • - Data Quality
  • - Integration Hub
  • - Mass Ingestion
  • - Model Serve
  • - Monitor
  • - Data Validation
Role for users that create assets, tasks, and processes. Allows users to perform the following tasks:
  • - Create assets, tasks, and processes.
  • - Configure connections, schedules, and runtime environments.
  • - Monitor jobs and advanced clusters, except in Mass Ingestion.
  • - View, create, and edit test cases and test suites in Data Validation.
Provides full access to Application Integration, B2B Gateway, Data Integration, Data Profiling, Data Quality, and Monitor.
Provides full access to API Center when the Service Consumer role is also assigned.
Provides partial access to Administrator, API Center, Application Integration Console, Integration Hub, Mass Ingestion, Model Serve, and Data Validation.
Monitor
  • - Administrator
  • - API Center
  • - Application Integration
  • - Application Integration Console
  • - B2B Gateway
  • - Data Integration
  • - Data Profiling
  • - Data Quality
  • - Integration Hub
  • - Mass Ingestion
  • - Model Serve
  • - Monitor
Role for users that monitor jobs. Allows users to perform the following tasks:
  • - Monitor API Center assets, Data Integration jobs, Data Quality assets, Integration Hub assets, Mass Ingestion jobs, Model Serve assets, and Application Integration process instances.
  • - View schedules and upgrade settings for Secure Agent services in Administrator.
  • - Start and stop file servers, configure proxy servers, and view file server settings in Administrator.
  • - View asset details in Application Integration, B2B Gateway, Data Integration, Data Profiling, Integration Hub, and Model Serve.
  • - View settings in Application Integration Console.
  • - View asset details except dictionary data in Data Quality.
  • - View API invocation logs in API Center.
  • - View application ingestion, database ingestion, and streaming ingestion jobs and job details in Mass Ingestion.
  • - View data integration and job details in Monitor.
Operator
  • - Application Integration
  • - Application Integration Console
  • - Data Profiling
  • - Data Quality
  • - Model Serve
  • - Operational Insights
Role for users that manage processes. Allows users to perform the following tasks:
  • - View asset details in Application Integration, Data Profiling, and Model Serve.
  • - Manage process instances and modify some operational server parameters in Application Integration.
  • - View and edit Process Server settings and some Cloud Server settings in Application Integration Console.
  • - View asset details except dictionary data in Data Quality.
  • - View cloud and domain infrastructure and Secure Agent alert settings in Operational Insights.
Service Consumer
  • - Administrator
  • - API Portal
  • - Application Integration
  • - Data Integration
  • - Data Quality
Role for users that run tasks and processes. Allows users to perform the following tasks:
  • - View schedules, Swagger files, and upgrade settings for Secure Agent services, start and stop file servers, configure proxy servers, and view other file server settings in Administrator.
  • - Open API Portal.
  • - Invoke processes in Application Integration.
  • - View tasks, run tasks, test-run mappings, run taskflows, and download workflow XML in Data Integration.
  • - View asset details except dictionary data in Data Quality.
Provides full access to API Portal.

Administrator roles

To provide access to the Administrator service, assign users the appropriate roles. You can assign a system-defined role or create custom roles for users.
The following table describes the system-defined roles that provide access to Administrator:
Role
Description
Admin*
Provides full access to Administrator except for privileges to enable or disable the use of customer managed encryption keys for the organization. To allow this ability, assign the user both the Admin and Key Admin roles.
Designer*
Allows users to perform the following tasks in Administrator:
  • - Configure connections, runtime environments, schedules, Swagger files, and advanced configurations.
  • - Install add-on connectors and install and uninstall add-on bundles.
  • - View upgrade settings for Secure Agent services.
  • - Start and stop file servers, configure proxy servers, and view other file server settings.
Key Admin
Allows users to enable and disable the use of customer managed encryption keys for their organization on the Security tab of the Settings page. Assign this role to a user who also has the Admin role. If the user doesn't have both roles, they can't see the Security tab.
For more information about customer managed encryption keys, see Organization Administration.
Monitor*
Allows users to perform the following tasks in Administrator:
  • - View schedules and upgrade settings for Secure Agent services.
  • - Start and stop file servers, configure proxy servers, and view other file server settings.
Service Consumer*
Allows users to perform the following tasks in Administrator:
  • - View schedules, Swagger files, and upgrade settings for Secure Agent services.
  • - Start and stop file servers, configure proxy servers, and view other file server settings.
* Provides access to multiple services. For more information, see Cross-service roles.

API Center roles

To provide access to API Center, assign users the appropriate roles. You can assign a system-defined role or create custom roles for users.
The following table describes the system-defined roles that provide access to API Center:
Role
Description
Admin*
Provides full access to API Center.
API Policy Manager
Allows users to define policies. Allows users to access the following pages in API Center:
  • - Explore (read-only)
  • - Policies
Deployer*
When assigned with the Service Consumer role, allows users to view and deploy assets, assign policies, manage organization settings, and add OAuth 2.0 clients in API Center. Allows users to access the following pages:
  • - Explore (read-only)
  • - API Console
  • - Configuration
Note: To provide these privileges, you must assign both the Deployer and Service Consumer roles.
Designer*
When assigned with the Service Consumer role, provides full access to all asset privileges and allows users to assign policies in API Center. Allows users to access the following pages:
  • - New Asset
  • - Explore
Note: To provide these privileges, you must assign both the Designer and Service Consumer roles.
Monitor*
Allows users to monitor API Center assets. Allows users to access the following pages:
  • - Explore (read-only)
  • - API Monitor
Service Consumer*
Allows users to access API Center when the Designer or Deployer role is also assigned.
* Provides access to multiple services. For more information, see Cross-service roles.
For more information about API Center roles, see the API Center help.

API Manager roles

To provide access to API Manager, assign users the appropriate roles. You can assign a system-defined role or create custom roles for users.
The following table describes the system-defined roles that provide access to API Manager:
Role
Description
Admin*
Provides full access to API Manager.
* Provides access to multiple services. For more information, see Cross-service roles.
To provide different levels of access to API Manager, create custom roles. For more information, see the API Manager help.

API Portal roles

To provide access to API Portal, assign users the appropriate roles. You can assign a system-defined role or create custom roles for users.
The following table describes the system-defined roles that provide access to API Portal:
Role
Description
Admin*
Provides full access to API Portal.
Service Consumer*
Allows users to open API Portal.
* Provides access to multiple services. For more information, see Cross-service roles.

Application Integration and Application Integration Console roles

To provide access to Application Integration and Application Integration Console, assign users the appropriate roles. You can assign a system-defined role or create custom roles for users.
The following table describes the system-defined roles that provide access to Application Integration and Application Integration Console:
Role
Description
Admin*
Provides full access to Application Integration and Application Integration Console. Has the execution privileges.
Application Integration Business Manager
Role for monitoring business activity. Users with this role can view information about assets and process instances, but they can't change them.
Allows users to perform the following tasks:
  • - View folder and asset lists and asset details in Application Integration.
  • - Access the Processes, APIs, and Connections pages in Application Integration Console.
Application Integration Data Viewer
Supplemental role that allows users to view detailed logs in Application Integration Console. Assign this role along with at least one other role. For example, if you want a user with the Designer role to view detailed Process Server logs, assign the user the Application Integration Data Viewer and the Designer roles, and set the Process Server logging level to verbose.
Note: Users can view detailed logs for an artifact when the logging level is set to verbose.
Deployer*
Allows users to perform the following tasks in Application Integration and Application Integration Console:
  • - View asset details in Application Integration.
  • - Deploy assets and view settings on the Processes, Logs, Server Configuration, Deployed Assets, and Resources pages in Application Integration Console.
  • - Upload and deploy Process Developer-generated orchestration artifacts (BPRs) in Application Integration Console.
Assign this role in a production environment where deployment access is typically restricted.
Designer*
Provides full access to Application Integration.
Allows users to view and edit all settings except server configuration properties in Application Integration Console.
Monitor*
Allows users to perform the following tasks in Application Integration and Application Integration Console:
  • - View asset details in Application Integration.
  • - View settings in Application Integration Console.
Operator*
Allows users to perform the following tasks in Application Integration and Application Integration Console:
  • - View asset details in Application Integration.
  • - View and edit Process Server settings and some Cloud Server settings in Application Integration Console. For example, a user with the Operator role can create an alert service but can't view tenant details.
Service Consumer*
Allows users to execute Application Integration processes through APIs.
* Provides access to multiple services. For more information, see Cross-service roles.

B2B Gateway roles

To provide access to B2B Gateway, assign users the appropriate roles. You can assign a system-defined role or create custom roles for users.
The following table describes the system-defined roles that provide access to B2B Gateway:
Role
Description
Admin*
Provides full access to B2B Gateway.
Designer*
Provides full access to B2B Gateway.
Monitor*
Allows users to view asset details.
* Provides access to multiple services. For more information, see Cross-service roles.

B2B Partners Portal roles

If your organization uses B2B Gateway, you might want to enable access to B2B Partners Portal for your external trading partners. To give your trading partners access to B2B Partners Portal, create a custom role and assign it to partner users.
Note: There is no system-defined role for B2B Partners Portal external trading partners. Therefore, you'll need to create a custom role for them.
When you create a custom role for partner users, name the role so that you know it is for B2B Partners Portal users. For example, you might name the role "B2B Partners Portal User."
Optionally, you can give the role a description. Clearly describe the role so that you know it is for users from partner companies. For example, you might describe the role as "Role for users from partner companies to access the B2B Partners Portal service."
When you create a custom role for B2B Partners Portal users, enable the Partners Portal feature privilege for the B2B Partners Portal service. For more information about creating custom roles, see Creating a custom role.
Assign the custom role to users from your partner companies. You only need to create one role for B2B Partners Portal users. Assign the same role to all external B2B Partners Portal users.

Business 360 Console roles

To provide access to Business 360 Console, assign users the appropriate roles. You can assign a system-defined role or create custom roles for users.
The following table describes the system-defined roles that provide access to Business 360 Console:
Role
Description
Admin*
Provides full access to Business 360 Console. Allows users to perform solution upgrades.
Note: To provide full access to Business 360 Console, assign users the Admin, Designer, and MDM Designer user roles. To allow users to perform only the configuration tasks in Business 360 Console, you can assign users the Admin role or both the Designer and MDM Designer roles.
Business 360 Process Executor
Required role for users with custom user roles to perform tasks in Business 360 Console and business applications. Allows users to update business entities in Business 360 Console.
Allows users to perform the following tasks in business applications:
  • - Save records and custom reports.
  • - View, create, update, and delete hierarchies.
  • - Import records, related records, and hierarchy data.
  • - Access the Workflow Inbox page.
Designer*
Allows users to perform tasks in Business 360 Console that require integration with other services such as Data Integration and Data Quality.
Allows users to perform the following tasks in Business 360 Console:
  • - Create MDM SaaS assets except reference data assets.
  • - Define a data model and source systems.
  • - Define and monitor jobs, such as ingress and egress.
  • - Configure data quality, match and merge, survivorship, business events, and global settings.
Doesn't allow users to define reference data assets.
Job Executor
Allows users to run ingress and egress jobs in Business 360 Console.
Note: This role is not required to run jobs that business applications run when users perform tasks, such as file import.
MDM Designer
Allows users to perform the following tasks in Business 360 Console:
  • - Create MDM SaaS assets.
  • - Define a data model and source systems.
  • - Define and monitor jobs, such as ingress and egress.
  • - Configure data quality, match and merge, survivorship, business events, and global settings.
  • - Export and import assets when the user also has the Designer role.
* Provides access to multiple services. For more information, see Cross-service roles.
For more information about Business 360 Console roles, see the Business 360 Console help.

Cloud Data Integration for PowerCenter (CDI-PC) roles

To provide access to the CDI-PC service, assign users the appropriate roles. You can assign a system-defined role or create custom roles for users.
The following table describes the system-defined roles that provide access to CDI-PC:
Role
Description
Admin*
Provides full access to CDI-PC.
Domain Management
Provides full access to CDI-PC.
*Provides access to multiple services. For more information, see Cross-service roles.

Customer 360 SaaS roles

To provide access to MDM - Customer 360 SaaS, assign users the appropriate roles. You can assign a system-defined role or create custom roles for users.
The following table describes the system-defined roles that provide access to MDM - Customer 360 SaaS:
Role
Description
Customer 360 Analyst
Role for creating records. Allows users to create, edit, and delete records in MDM - Customer 360 SaaS.
When a Customer 360 Analyst creates or edits a record, the changes trigger a review process that requires approval from a Customer 360 Manager.
Customer 360 Data Steward
Role for creating records and hierarchies. Allows users to perform any task in Customer 360 SaaS, including the following tasks:
  • - Create, edit, and delete records without approval.
  • - Run jobs.
  • - Review and approve customer records.
Customer 360 Manager
Role for managing records. Allows users to perform the following tasks:
  • - Review and approve or reject customer records.
  • - Create, edit, and delete records without approval.
MDM Business User
Allows users to view records in Customer 360 SaaS but not create or edit them.
For more information about Customer 360 SaaS roles, see the MDM - Customer 360 SaaS help.

Data Access Management roles

To provide access to Data Access Management, assign users the appropriate roles. You can assign a system-defined role to or create custom roles for users.
The following table describes the system-defined roles that provide access to Data Access Management:
Role
Description
Admin*
Role for performing administrative tasks. Provides full access to Data Access Management, but cannot execute data access policies.
Data Integration Task Executor*
Role for executing data access policies. Allows users to perform the following tasks:
  • - Access Data Access Management.
  • - View data access policies in Data Access Management.
  • - Execute data access policies in Data Integration.
Data Marketplace Administrator**
Role for performing administrative tasks. Provides full access to Data Access Management, but cannot execute data access policies.
Data Marketplace Technical Administrator**
Role for performing technical administrative tasks. Provides full access to Data Access Management, but cannot execute data access policies.
Data Marketplace User**
Role for reading data access policies. Allows users to perform the following tasks in Data Access Management:
  • - Access Data Access Management.
  • - View data access policies.
Governance Administrator***
Role for performing administrative tasks. Provides full access to Data Access Management, but cannot execute data access policies.
Governance User***
Role for viewing data access policies. Allows users to perform the following tasks in Data Access Management:
  • - Access Data Access Management.
  • - View data access policies.
* Provides access to multiple services. For more information, see Cross-service roles.
** Also provides access to Data Marketplace. For more information, see Data Marketplace roles.
*** Also provides access to Data Governance and Catalog. For more information, see Data Governance and Catalog roles.
For more information about Data Access Management roles, see the Data Access Management help.

Data Governance and Catalog roles

To provide access to Data Governance and Catalog, assign users the appropriate roles. You can assign a system-defined role or create custom roles for users.
The following table describes the system-defined roles that provide access to Data Governance and Catalog:
Role
Description
Governance Administrator*
Role for administering assets and operations in Data Governance and Catalog and Metadata Command Center. Allows users to perform the following tasks in Data Governance and Catalog:
  • - View business assets, data classifications, profiled stats, sensitive data, technical assets, and unpublished content.
  • - Curate automatic glossary associations and data classifications.
  • - Assign stakeholders for technical assets.
  • - Participate in change approvals.
  • - Export and import assets.
Governance User*
Role for viewing and exporting assets in Data Governance and Catalog. Allows users to perform the following tasks in Data Governance and Catalog:
  • - View business assets, data classifications, profiled stats, and technical assets.
  • - Export assets.
* Also provides access to Metadata Command Center and Data Access Management. For more information, see Metadata Command Center roles and Data Access Management roles.
For more information about Data Governance and Catalog roles, see the Data Governance and Catalog help.

Data Integration roles

To provide access to Data Integration, assign users the appropriate roles. You can assign a system-defined role or create custom roles for users.
The following table describes the system-defined roles that provide access to Data Integration:
Role
Description
Admin*
Provides full access to Data Integration.
Data Integration Data Previewer*
Supplemental role that allows users to perform the following tasks in Data Integration:
  • - Preview data when they select a source, target, or lookup object for use in a mapping or task.
  • - Preview data when on a data quality transformation that they select in a mapping.
Assign this role with another role, such as the Designer role, to ensure that users can access Data Integration.
Data Integration Task Executor*
Role for running tasks and taskflows. Allows users to perform the following tasks in Data Integration:
  • - View assets and asset details.
  • - Run tasks and taskflows and test-run mappings.
  • - View user's own data integration jobs and job details.
  • - Start and stop user's own jobs.
  • - Download session logs.
Designer*
Provides full access to Data Integration.
Monitor*
Allows users to view asset details in Data Integration.
Service Consumer*
Allows users to view tasks, run tasks, test-run mappings, run taskflows, and download workflow XML in Data Integration.
* Provides access to multiple services. For more information, see Cross-service roles.

Data Marketplace roles

To provide access to Data Marketplace, assign users the appropriate roles. You can assign a system-defined role to Data Marketplace users.
The following table describes the system-defined roles that provide access to Data Marketplace:
Role
Description
Data Marketplace Administrator*
Role for performing administrative tasks. Provides full access to access to Data Marketplace.
Data Marketplace Category Owner
Role for users that have the rights to a category. Allows users to perform the following tasks:
  • - Create and bulk create data collections within the user's category.
  • - Add and remove data assets inside data collections within the user's category.
  • - Approve and reject data orders for data collections.
  • - Approve and reject data collection requests on categories that the user is responsible for.
  • - Add and edit delivery targets inside data to collections within the user's category.
  • - Link and remove variants to data collections within the user's category.
  • - Delete data collections within the user's category.
  • - Rate data collections that the user has access to against the context the user has access with.
  • - Search for published data collections.
  • - Compare collections.
  • - Add and bulk add data assets to data collections.
  • - Create an order and raise data collection requests.
  • - Create, bulk create, modify, and delete categories.
  • - Add and remove terms of use inside data collections within the user's category.
  • - Participate in public discussion channels.
  • - Comment on private channels that the user has access to.
Data Marketplace Data Collection Owner
Role for users that have rights to a data collection. Allows users to perform the following tasks:
  • - Create, bulk create, modify, and delete data collections.
  • - View data collections that the user owns.
  • - Add and bulk add terms of use and data assets to data collections that the user owns.
  • - Remove terms of use and data assets from data collections that the user owns.
  • - Search for published data collections.
  • - Compare collections.
  • - Add and edit delivery targets inside the data collections that the user owns.
  • - Rate data collections that the user has access to against the context the user has access with.
  • - Create an order for collections and raise data collection requests against collections or categories.
  • - Complete and reject data collection requests raised on data collections that the user owns.
  • - Approve and reject data collection access requests.
  • - Link variants.
  • - Participate in public discussion channels.
  • - Comment on private channels that the user has access to.
Data Marketplace Data Collection Technical Owner
Role for users that have technical rights to a data collection. Allows users to perform the following tasks:
  • - View orders for data collections.
  • - Add and edit delivery targets to data collections.
  • - Request withdrawal and withdraw access to data collections.
  • - Add and remove data assets and terms of use inside data collections.
  • - Rate data collections that the user has access to against the context the user has access with.
  • - Search for published data collections.
  • - Compare collections.
  • - Create an order on collections and raise data collection requests against collections and categories.
  • - Bulk create "terms of use - data collection" relationships and "delivery target - data collection" relationships.
  • - Deliver data that is ordered by a data user.
  • - Participate in public discussion channels.
  • - Comment on private channels that the user has access to.
Data Marketplace Delivery Owner
Role for managing the delivery option for delivering data collections. Allows users to perform the following tasks:
  • - Search and compare data collections.
  • - Rate data collections that user has access to.
  • - Create delivery options and delivery targets.
  • - Bulk create delivery formats, delivery methods, delivery templates, and "delivery target - data collection" relationships.
  • - Request withdrawal of consumer access, withdraw consumer access, and fulfill data orders for data collections that have a delivery option that the user is responsible for.
  • - Participate in public and private discussion channels that the user has access to.
Data Marketplace Technical Administrator*
Role for performing technical administrative tasks. Allows users to perform the following tasks:
  • - View data orders for and add delivery targets to data collections.
  • - Deliver requested data collections to data users.
  • - Search and compare data collections.
  • - Rate data collections that the user has access to.
  • - Add data assets, delivery targets, and terms of use to data collections.
  • - Bulk create data elements, data assets, and consumer accesses.
  • - Delete data elements and data assets.
  • - Modify object labels.
  • - Configure data delivery formats and methods.
  • - Configure default delivery targets to deliver data.
  • - Link assets from Data Governance and Catalog.
  • - Configure the general "terms of use" message and create new terms of use.
  • - Create cost centers.
  • - Request withdrawal and withdraw consumer accesses.
  • - Bulk create cost centers, delivery formats, delivery methods, delivery templates, "terms of use - data collection" relationships, and "delivery target - data collection" relationships.
  • - Configure star owners.
  • - Participate in public and private discussion channels that the user has access to.
  • - Customize the Data Marketplace user interface.
Data Marketplace User*
Role for using data collections. Allows users to perform the following tasks:
  • - Order, and compare data collections.
  • - Search for published data collections.
  • - View requested and delivered data collections.
  • - View data collection details.
  • - Rate data collections that the user has access to.
  • - Create and cancel data collection requests on collections and categories.
  • - Participate in public and private discussion channels.
* Also provides access to Data Access Management. For more information, see Data Access Management roles.
For more information about Data Marketplace roles, see the Data Marketplace help.

Data Profiling roles

To provide access to Data Profiling, assign users the appropriate roles. You can assign a system-defined role or create custom roles for users.
The following table describes the system-defined roles that provide access to Data Profiling:
Role
Description
Admin*
Provides full access to Data Profiling.
Data Integration Data Previewer*
Supplemental role that allows users to preview source object data when they create a profile or view profile results.
Assign this role with another role, such as the Designer role, to ensure that users can access Data Profiling.
Designer*
Provides full access to Data Profiling.
Monitor*
Allows users to view asset details in Data Profiling.
Operator*
Allows users to view asset details in Data Profiling.
* Provides access to multiple services. For more information, see Cross-service roles.

Data Quality roles

To provide access to Data Quality, assign users the appropriate roles. You can assign a system-defined role or create custom roles for users.
The following table describes the system-defined roles that provide access to Data Quality:
Role
Description
Admin*
Provides full access to Data Quality.
Deployer*
Allows users to view asset details except dictionary data in Data Quality.
Designer*
Provides full access to Data Quality.
Monitor*
Allows users to view asset details except dictionary data in Data Quality.
Operator*
Allows users to view asset details except dictionary data in Data Quality.
Service Consumer*
Allows users to view asset details except dictionary data in Data Quality.
* Provides access to multiple services. For more information, see Cross-service roles.

Integration Hub roles

To provide access to Cloud Integration Hub, assign users the appropriate roles. You can assign a system-defined role or create custom roles for users.
The following table describes the system-defined roles that provide access to Cloud Integration Hub:
Role
Description
Admin*
Provides full access to Cloud Integration Hub.
Designer*
Allows users to create, view, edit, delete and run Cloud Integration Hub assets.
Doesn't provide privileges to perform provisioning, set system properties, or set permissions for Cloud Integration Hub assets.
Monitor*
Allows users to view asset details in Cloud Integration Hub.
* Provides access to multiple services. For more information, see Cross-service roles.
For more information about Cloud Integration Hub roles, see the Cloud Integration Hub help.

Mass Ingestion roles

To provide access to Mass Ingestion, assign users the appropriate roles. You can assign a system-defined role or create custom roles for users.
The following table describes the system-defined roles that provide access to Mass Ingestion:
Role
Description
Admin*
Provides full access to Mass Ingestion.
Deployer*
Allows users to view application ingestion, database ingestion, and streaming ingestion tasks.
Designer*
Allows users to create, view, edit, delete, run, and set permissions on application ingestion, database ingestion, and streaming ingestion tasks.
Monitor*
Allows users to view application ingestion, database ingestion, and streaming ingestion jobs and job details.
* Provides access to multiple services. For more information, see Cross-service roles.

Metadata Command Center roles

To provide access to Metadata Command Center, assign users the appropriate roles. You can assign a system-defined role or custom roles for users.
The following table describes the system-defined roles that provide access to Metadata Command Center:
Role
Description
Admin*
Role for performing upgrades. In addition, this role can perform all tasks that a Governance Administrator can perform in Metadata Command Center.
Governance Administrator**
Role for administering assets and operations in Data Governance and Catalog and Metadata Command Center. Allows users to perform the following tasks in Metadata Command Center:
  • - Create, read, update and delete AI models, business reports, business terms, catalog source configurations, catalog source types, custom models, data quality, data sets, glossary domains and subdomains, metrics, policies, processes, and systems.
  • - Run and set permissions on catalog source configurations.
  • - Read and update technical assets.
  • - Manage access control, connection assignments, custom attributes, data classifications, reference data, system settings, and workflow settings.
  • - Monitor jobs.
  • - View custom attributes, data classifications, and reference data.
Governance User**
Role for viewing and exporting assets in Data Governance and Catalog. Allows users to view AI models, business reports, business terms, custom catalog source types, custom models, data quality, data sets, glossary domains and subdomains, metrics, policies, processes, systems, and technical assets in Metadata Command Center.
* Provides access to multiple services. For more information, see Cross-service roles.
** Also provides access to Data Governance and Catalog. For more information, see Data Governance and Catalog roles.
For more information about Metadata Command Center roles, see the Metadata Command Center help.

Model Serve roles

To provide access to Model Serve, assign users the appropriate roles. You can assign a system-defined role or create custom roles for users.
The following table describes the system-defined roles that provide access to Model Serve:
Role
Description
Admin*
Provides full access to Model Serve.
Designer*
Allows users to perform the following tasks in Model Serve:
  • - Create, view, edit, and delete machine learning models.
  • - Create, view, edit, delete, and run model deployments.
  • - Generate predictions from a deployed machine learning model.
Model Serve Admin
Role for Model Serve administration. Allows users to perform the following tasks:
  • - Assign permissions for other Model Serve users.
  • - Register and deploy machine learning models.
  • - Generate predictions from a deployed machine learning model.
Model Serve Predictions User
Role for generating predictions. Allows users to perform the following tasks:
  • - Generate predictions from a deployed machine learning model.
  • - View, but not change, model deployment assets.
Model Serve System Role
Role for the Model Serve system user. Assigns necessary permissions so that the system user can perform tasks such as provisioning resources for model deployments.
Do not assign this role to users.
For more information about the Model Serve system user, see Model Serve system user.
Monitor*
Allows users to view asset details in Model Serve.
Operator*
Allows users to view asset details in Model Serve.
* Provides access to multiple services. For more information, see Cross-service roles.

Monitor roles

To provide access to Monitor, assign users the appropriate roles. You can assign a system-defined role or create custom roles for users.
The following table describes the system-defined roles that provide access to Monitor:
Role
Description
Admin*
Provides full access to Monitor.
Designer*
Provides full access to Monitor.
Monitor*
Allows users to view data integration jobs and job details in Monitor.
Doesn't allow users to view export or import jobs.
* Provides access to multiple services. For more information, see Cross-service roles.

Operational Insights roles

To provide access to Operational Insights, assign users the appropriate roles. You can assign a system-defined role or create custom roles for users.
The following table describes the system-defined roles that provide access to Operational Insights:
Role
Description
Admin*
Provides full access to Operational Insights.
Operator*
Allows users to perform the following tasks in Operational Insights:
  • - View cloud and domain infrastructure.
  • - View Secure Agent alert settings.
* Provides access to multiple services. For more information, see Cross-service roles.

Product 360 SaaS roles

To provide access to MDM - Product 360 SaaS, assign users the appropriate roles. You can assign a system-defined role or create custom roles for users.
The following table describes the system-defined roles that provide access to MDM - Product 360 SaaS:
Role
Description
Product 360 Manager
Role for managing records. Allows users to perform the following tasks:
  • - Review and approve records.
  • - Create, edit, and delete records without approval.
Product 360 Read-Only
Role for viewing records. Allows users to view records in Product 360 SaaS but not edit them.
For more information about Product 360 SaaS roles, see the MDM - Product 360 SaaS help.

Reference 360 roles

To provide access to MDM - Reference 360, assign users the appropriate roles. You can assign a system-defined role to Reference 360 users.
The following table describes the system-defined roles that provide access to MDM - Reference 360:
Role
Description
Reference 360 Administrator
Administrative role for Reference 360. Allows users to configure the Reference 360 environment.
Reference 360 Business Analyst
Role for analyzing assets. Allows users to view and analyze assets, but not propose changes to them.
Reference 360 Business Steward
Role for the subject matter experts for reference data. Allows users to perform the following tasks:
  • - Create and manage code values in code lists and value mappings in crosswalks.
  • - Approve changes proposed by other users.
  • - Send their own changes for approval or directly publish their changes without approval.
Reference 360 Planner
Role for creating and managing hierarchies. Allows users to perform the following tasks:
  • - Create hierarchy assets, define hierarchy models, and import hierarchy relationships.
  • - Delete hierarchies that are no longer needed.
  • - Assign the Planner stakeholder role to other users for a hierarchy.
Reference 360 Primary Owner
Role for creating and defining reference data structures. Allows users to perform the following tasks:
  • - Create and define reference data structures, such as reference data sets and code lists.
  • - Delete code lists.
  • - Propose changes to code values in code lists. The changes must be approved by Business Stewards.
  • - Assign users access to code lists and reference data sets using Stakeholder roles.
Reference 360 Stakeholder
Role for proposing changes to code values. Allows users to propose changes, but the proposed changes must be approved by Business Stewards.
Reference 360 User
Restricted access role. By default, users with this role can't access any assets. To allow users to access a specific asset, such as a code list or crosswalk, assign this role along with the stakeholder role for the asset.
For more information about Reference 360 roles, see the MDM - Reference 360 help.

Supplier 360 SaaS roles

To provide access to MDM - Supplier 360 SaaS, assign users the appropriate roles. You can assign a system-defined role or create custom roles for users.
The following table describes the system-defined roles that provide access to MDM - Supplier 360 SaaS:
Role
Description
Supplier 360 Analyst
Role for analyzing records. Allows users to create, read, edit, and delete records in Supplier 360 SaaS. When a Supplier 360 Analyst creates or edits a record, the changes trigger a review process that requires approval from a Supplier 360 manager.
Supplier 360 Commodity Manager
Role for managing commodity evaluation tasks. Has the originator and approver privileges. Allows users to perform the following tasks:
  • - Claim and disclaim commodity evaluation tasks.
  • - Act on the commodity evaluation tasks in the approval workflow.
  • - Create, read, edit, and delete records.
Supplier 360 Contract Manager
Role for managing contract evaluation tasks. Has the originator and approver privileges. Allows users to perform the following tasks:
  • - Claim and disclaim contract evaluation tasks.
  • - Act on the contract evaluation tasks in the approval workflow.
  • - Create, read, edit, and delete records.
Supplier 360 Credit Manager
Role for managing credit evaluation tasks. Has the originator and approver privileges. Allows users to perform the following tasks:
  • - Claim and disclaim credit evaluation tasks.
  • - Act on the credit evaluation tasks in the approval workflow.
  • - Create, read, edit, and delete records.
Supplier 360 Data Steward
Role for managing records. Allows users to perform the following tasks:
  • - Create, read, edit, and delete records with or without approval.
  • - Run jobs.
  • - Review and approve records.
  • - Match, merge, and unmerge records.
Supplier 360 Read Only
Role for viewing records in Supplier 360 SaaS. Allows users to view records but not create or edit them.
Supplier 360 Risk Manager
Role for managing risk evaluation tasks. Has the originator and approver privileges. Allows users to perform the following tasks:
  • - Claim and disclaim risk evaluation tasks.
  • - Act on the risk evaluation tasks in the approval workflow.
  • - Create, read, edit, and delete records.
Supplier 360 Task Admin
Role for administering evaluation tasks. Has the originator and approver privileges. Allows users to view all unclaimed evaluation tasks.
For more information about Supplier 360 SaaS roles, see the MDM - Supplier 360 SaaS help.