Table of Contents

Search

  1. Preface
  2. Introducing Reference 360
  3. Getting started with Reference 360
  4. Manage system reference data
  5. Manage reference data sets
  6. Manage code lists
  7. Manage code values
  8. Manage crosswalks
  9. Import data
  10. Manage hierarchies
  11. Manage attributes
  12. Manage workflows
  13. Manage jobs
  14. Reference 360 REST API
  15. Glossary

Reference 360

Reference 360

Reference 360 roles

Reference 360 roles

Reference 360
roles define a set of privileges that a user has while working in
MDM - Reference 360
. The privileges apply to all assets. To allow a user to access
MDM - Reference 360
, an administrator must assign at least one of the
Reference 360
roles to the users or to their user group.
The following list describes the
Reference 360
roles:
Reference 360
Administrator
Reference 360 Administrators configure the Reference 360 environment.
Reference 360
Planner
Planners create hierarchy assets, define hierarchy models, and import hierarchy relationships. Planners can delete hierarchies that are no longer needed. Planners can also assign the Planner role to other users for the hierarchy assets.
Reference 360
Primary Owner
Primary Owners create and define reference data structures such as reference data sets and code lists. Primary Owners can delete code lists and propose changes to code values in code lists. The proposed changes must be approved by Business Stewards.
Reference 360
Business Steward
Business Stewards are subject matter experts for reference data. They create and manage code values in code lists and value mappings in crosswalks. Business Stewards are responsible for approving changes proposed by other users. Business Stewards can send their own changes for approval or directly publish their changes without approval.
Reference 360
Stakeholder
Stakeholders propose changes to code values. The proposed changes must be approved by Business Stewards.
Reference 360
Business Analyst
Business Analysts view and analyze assets. Business Analysts cannot propose changes to assets.
Reference 360
User
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, the users require stakeholder roles for the asset.
The following table lists the privileges of the
Reference 360
roles:
Function
Planner
Primary Owner
Business Steward
Stakeholder
Business Analyst
User
System reference data
Read
-
Create
Read
Update
Delete
Read
Read
-
Reference data set
Read
Create
Read
Update
Delete
Read
Read
Read
-
Reference data set structure definition
Read
Create
Read
Read
Read
Read
-
Reference data set attributes
Read
Create
Read
Update
Delete
Read
Read
Read
-
Code list
Read
Create
Read
Update
Delete
Read
Read
Read
-
Code list structure definition
Read
Create
Read
Read
Read
Read
-
Code list attributes
Read
Create
Read
Update
Delete
Read
Read
Read
-
Code list draft
Read
Propose changes
Propose changes
Approve changes
Publish changes
Propose changes
-
-
Crosswalk
Read
Read
Create
Read
Update
Delete
Read
Read
Crosswalk value mappings
Read
Read
Create
Read
Update
Delete
Read
Read
-
Hierarchy
Create
Read
Update
Delete
Assign stakeholders
Import hierarchy relationships
Read
Read
Read
Read
-
Search and explore
Permitted
Permitted
Permitted
Permitted
Permitted
-
Export
Permitted
Permitted
Permitted
Permitted
Permitted
-
Import
-
Permitted
Permitted
Permitted
-
-
Direct import
-
-
Permitted
-
-
-
After you create an asset, you might not be able to edit some definition settings. For more information, see Reference data sets and Code lists.
For more information about Informatica Intelligent Cloud Services users, user groups, and roles, see the
Administrator
help.

0 COMMENTS

We’d like to hear from you!