You can restrict a user's access to assets and only grant access to the assets that the user needs to view and work on. To restrict a user's access, assign the user the
Reference 360
User role.
To grant privileges for only the assets that a user needs to view and work on, you assign the user a stakeholder role for the code list or crosswalk. The stakeholder role that you assign depends on the privileges that you want to grant the user.
When you grant privileges to code lists or crosswalks, the user gets access to the related assets.
You must be assigned the
Reference 360
Primary Owner role or the Primary Owner stakeholder role for the asset and the related assets to which you want to grant, change, or revoke access.
For example, assign Jane Smith the
Reference 360
User role to restrict her access to assets. Then you assign Jane the Business Analyst stakeholder role for the Enterprise Language code list. The role allows her to view and analyze the Enterprise Language code list and the Languages reference data set.
The following table lists the assets for which you can assign stakeholders, and the assets and related assets to which users get access:
Stakeholder for
Access to
Code list
The code list to which you granted access.
The reference data set to which the code list is associated.
Code list with a dependency
The code list to which you granted access.
The reference data set to which the code list is associated.
The parent code list.
The reference data set to which the parent code list is associated.
Code lists with Reference Data attributes
The code list to which you granted access.
The code lists referenced as Reference Data attributes.
The reference data sets to which the referenced code lists are associated.
Crosswalk
The crosswalk to which you granted access.
The source and target code lists used in the crosswalk.
The reference data sets to which the code lists are associated.