Review Standards role holders
The Role Holders page under Standards reports every party currently responsible for a requirement across your site's standards: direct assignees on requirements, holders of named site roles, and default Owners inherited from adoption settings. The report is read-only. You change a direct assignment on the requirement itself, and you change a shared role holder in Contacts > Roles.
Who can use this report
You need at least the Member role for the Standards module to view the report. Without Standards access, the page shows: You do not have permission to view role holders. Please contact your administrator.
Holder details are restricted to what your access allows. If you are not permitted to see a holder's identity, the row shows a restricted label such as Assigned user (no access) instead of a name. The assignment still counts toward the totals and health states.
Open the report
Open Standards from the main navigation.
Select Role Holders.
The report covers all current responsibility holders at the site, including roles that are not tied to a single standard.
What the summary metrics show
Four metrics at the top of the report summarise responsibility coverage:
Metric | What it counts |
|---|---|
Holders | Distinct holders visible to you. |
Assignments | Requirement role slots that are filled. |
Reqs Covered | Distinct requirements with at least one filled responsibility. |
Need Attention | Distinct linked requirements that need attention. |
Read the holder sections
Holders are grouped into three sections. Rows start collapsed; expand a holder to see the responsibility details for that holder.
Needs Attention: holders with at least one linked requirement that needs attention. This section lists failing holders first.
Healthy: holders with no failing requirements. This section is collapsible.
Missing Required Roles: required responsibility slots with no holder. This section only appears when something is missing and starts collapsed. Its header shows how many roles and requirements are missing a holder. An archived named role counts as missing.
Each expanded responsibility shows the role, the standard name, the requirement code and title, the current setup or compliance status, and the reasons a setup gap was flagged. Up to two reasons show directly, with any further reasons behind a +N more label. Where linked evidence needs attention, the row shows Linked evidence needs attention.
A restricted label such as Assigned group (no access) means your access hides that holder's identity, not that the role is vacant. The requirement still counts as filled.
Understand how a holder was assigned
Each responsibility row carries an assignment-route label showing where the assignment came from:
Route label | Meaning |
|---|---|
Direct | A party was assigned directly on the requirement. |
Inherited Default Owner | The Owner comes from the standard's default Owner rather than an explicit assignment. |
Via [role name] | The responsibility is filled by the current holder of a named site role, for example Via DPO. |
The report shows the effective assignment, so a requirement-level Owner override stays in place instead of being replaced by the default.
For a named site role, the route label links to the Contacts > Roles page when your access lets you view site roles, such as the Site Member role or above. Without that access, the same label shows as plain text and you see the responsibility context without the linked role details.
Fix a responsibility
The report does not edit assignments; it links you to where the change happens.
For a direct assignment, a default Owner, or a requirement-level override, open the requirement from the report and edit its Roles section. See Assign roles to a requirement.
For a named site role shown as Via [role name], change the holder in Contacts > Roles. That change cascades to every requirement using the role. See Manage site roles in Contacts.
For a slot in Missing Required Roles, open the requirement detail from the row and assign a holder.
Next steps
For how site roles, default Owners, and requirement assignments work together, see Roles and Owners in Standards.
To set the default Owner a standard inherits from, see Set a default owner for a standard.