The Admin role for the Standards module is required. Ask your organisation administrator to check your role assignment.
Manage org-wide push policies for standards
Workspace admins can control how each standard rolls out across sites by setting an org-wide push policy. For each standard and published version, you choose whether every site sees it as None, Recommended, Hidden, or Mandatory. You can also copy a policy from one site to another and review rollout progress before your changes take effect.
Who can configure org policy
Only users with the Admin role for the Standards module can open the org policy surface. Members and Managers cannot view or change org policy.
If you do not have the Standards policies page under your site Settings, check your site role or ask your organisation administrator to confirm you have Admin access for the Standards module.
What the four policy choices mean
Org policy is set per published version, per site. The available choices are:
None — no policy is set for this site. The standard does not appear in the site’s Standards Library.
Recommended — the site may adopt it, and it appears in the Standards Library with a recommended label.
Hidden — the standard is not available for the site to adopt.
Mandatory — the site is expected to adopt the standard. A mandatory policy creates a compliance gap if the site has not adopted it.
Set org-wide push policies for a standard
On the parent site, open Settings → Standards policies. The page loads a sidebar of standard definitions on the left and a policy panel on the right.
Choose a standard from the sidebar. Each row shows the standard name and a rollout progress indicator. If no standards match your search, the sidebar shows:
No standards match your search.
In the Required Version section, pick the published version your organisation expects sites to adopt. Each item is labelled
v{versionNumber}, with the latest version marked (Latest). Before a version is selected, the panel shows:Select a published version to configure site policy.
For each site listed in the panel, use the policy selector — labelled Policy for {site name} — to set the status to None, Recommended, Hidden, or Mandatory. Users without the Admin role see the policy control disabled.
If you want to copy a policy from one site to another, use the copy action on the site row. This copies the selected site’s policy and required version to the target site.
Review the rollout progress indicators in the panel and sidebar to confirm which sites are Active, Adopting, or Missing before you finish. When mandatory policy is active, the indicator uses Gap instead of Missing to highlight sites that are required to adopt but have not yet done so.
Apply to all child sites at once
When the parent site row is selected and there are child sites, the panel shows an Apply to All Sites action on the parent row. Clicking it copies the parent site’s policy to every child site for the selected standard version.
After the action completes, the parent row shows a confirmation:
Applied to all sites
This action is only available when you have the Admin role and the selected version is configured for the parent site.
View org policy from a child site
Child sites cannot configure org policy. When you open the Standards policies page on a child site, the panel shows:
Org standards policy is configured at the parent site. You can view this site’s policy here.
The panel subtitle is:
View the published version and org policy assigned to this site.
A Go to Parent Site button links to the parent site’s org policy page, keeping the selected standard in view so you can continue from there.
On a child site, the policy selectors are disabled. You can see which version is required and which policy is applied, but you cannot change it.
What the rollout progress means
The sidebar and panel progress indicators give a quick overview of how widely a standard is adopted across your organisation. The colours map to:
Active — the standard is adopted and live at that site.
Adopting — the site has started adoption but has not yet activated the standard.
Missing / Gap — not adopted. Gap is used when the standard is mandatory to highlight non-compliance.
Common issues
You don't have permission to view org standards policy
No sites are available for org standards policy
This page is intended for parent sites that manage child sites. If your site has no child sites, or if the organisation structure does not support multi-site policy, the page will show this empty state. Confirm you are on the parent site and that your organisation has multiple sites configured.
Failed to load org policy
The page could not retrieve the policy data from the server. Refresh the page. If the error persists, check your network connection or contact your organisation administrator to verify the Standards module is enabled and your permissions are correct.
What’s next
After you have configured org policy, child sites will see the updated availability and mandatory status in their Standards Library. Site managers can then adopt the standards you have made available or recommended. For details on how a site adopts a standard, see Adopt a Standard at This Site. For a full breakdown of who can view or manage standards, see Standards Permissions and Access.
Was this helpful?
Was this helpful?