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

Stakeholder roles

Stakeholder roles

Stakeholder roles define a set of privileges for each asset in
Reference 360
. An asset might be a reference data set, code list, or crosswalk. Users with the
Reference 360
Primary Owner role are responsible for assigning stakeholder roles to users and groups for each asset.
The following list describes the stakeholder roles that you can assign to users and groups for an asset:
Planner
Planners define the hierarchy model and import hierarchy relationships to hierarchy assets. Planners can also assign the Planner role to other users for the hierarchy assets.
Primary Owner
Primary Owners create and define the asset. Primary Owners can propose changes to the asset, but their changes must be approved by Business Stewards.
Business Steward
Business Stewards are subject matter experts for the asset. They create and manage data values in the asset. 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.
Stakeholder
Stakeholders propose changes to the asset. The proposed changes must be approved by Business Stewards.
Business Analyst
Business Analysts view and analyze the asset. Business Analysts cannot propose changes to the asset.
The following table lists the privileges that are assigned to users with a stakeholder role:
Function
Planner
Primary Owner
Business Steward
Stakeholder
Business Analyst
Reference data set
-
Read
Update
Delete
Read
Read
Read
Reference data set structure definition
-
Read
Update
Delete
Read
Read
Read
Reference data set attributes
-
Create
Read
Update
Delete
Read
Read
Read
Code list
-
Read
Update
Delete
Read
Read
Read
Code list structure definition
-
Read
Update
Delete
Read
Read
Read
Code list attributes
-
Create
Read
Update
Delete
Read
Read
Read
Code list draft
-
Propose changes
Propose changes
Approve changes
Publish changes
Propose changes
-
Crosswalk
-
Read
Read
Update
Delete
Read
Read
Crosswalk value mappings
-
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
Export
-
Permitted
Permitted
Permitted
Permitted
Import
-
Permitted
Permitted
Permitted
-
Direct import
-
-
-
-
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.
The Planner stakeholder role is the only stakeholder role that you can assign to hierarchy assets.

0 COMMENTS

We’d like to hear from you!