Administrative role for

Reference 360

. Allows users to configure the

Reference 360

environment.

Role for analyzing assets. Allows users to view and analyze assets, but not propose changes to them.

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.

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.

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.

Role for proposing changes to code values. Allows users to propose changes, but the proposed changes must be approved by Business Stewards.

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.