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

Guidelines for assigning roles

Guidelines for assigning roles

To provide users with access to
MDM - Reference 360
, administrators must assign at least one
Reference 360
role to users or groups to which the users belong. Then primary owners can assign stakeholder roles for assets to users. Role privileges are cumulative. Users who have multiple roles or who belong to groups receive the combined privileges associated with each role.
When administrators assign
Reference 360
roles to users or groups, assign the role with the minimum number of privileges that are required for each user to work with
Reference 360
. Assign stakeholder roles only to those users or groups that work with an asset.
For example, you assign John the
Reference 360
User role. He cannot view any assets in
Reference 360
. John is the subject matter expert for the Enterprise Language code list, so you assign John the Business Steward stakeholder role for the code list. The role allows him to create, manage, and approve code values in the Enterprise Language code list. He can also directly publish his changes to the code list. For all other assets, John's
Reference 360
User role applies.

0 COMMENTS

We’d like to hear from you!