Skip to main content
Choose who can view your published guideline. Set a default for the whole guideline, then add exceptions for pages that need different security, such as a public home page on an otherwise private guideline. Guideline Settings Security

​
Open the Security page

1

Select guideline

From the dashboard, select the guideline you want to manage
2

Open Security

Select Security from the left column
Make your changes, then select Save in the bar at the bottom of the page.
Once saved, security changes apply to a published guideline right away. You don’t need to publish again. Guidelines published with an earlier version of Standards are re-published the first time you save. Learn more in Web address.

​
Default

Security Default 1
The default security applies to every page of the guideline that isn’t part of an exception. Select the security option to choose a different one, then fill in any settings it needs, such as a password. A guideline that has never had its security set is fully public, with No restrictions.

​
Exceptions

Security Exception
Exceptions let some pages use different security from the default. This is ideal when pages of a guideline can be shared publicly but some contain information that should be restricted, or the other way around.
1

Add an exception

Under Exceptions, select Add
2

Choose its security

Select the security option for the exception, and fill in any settings it needs
3

Add pages

Under Pages, select Add, choose the pages the exception applies to, then select Add
4

Save

Select Save in the bar at the bottom of the page

​
Keep in mind

  • Every exception needs at least one page.
  • A page can only belong to one exception. Pages already in another exception can’t be chosen.
  • Select Remove on an exception to delete it. Its pages go back to the default.
  • Hidden pages aren’t published, so they can’t be added to exceptions.
  • Exceptions can’t use Secure embed, since an embedded guideline is always embedded as a whole.
  • Exceptions are available on every plan. Each exception can use any security option your plan includes.

​
Security options

Security Security Types

​
Standard

No restrictions
  • Anyone with the URL can view. This is ideal for guidelines that can be shared with anyone.
Plain password protected
  • Only people with the password can view.
  • Set a password of at least 5 characters. The password is shown in plain text, so it’s easy to copy and share.
  • Limit incorrect attempts is on by default. After several incorrect passwords, the viewer is locked out for a while before they can try again.
  • Requires a paid plan.

​
Enhanced

Enterprise Sign-in required
  • The most secure and configurable security option. Only allowed people and groups can view.
  • Choose the sign-in methods viewers can use, and who is allowed to view. See Sign-in methods and Allowed viewers below.
Logged public access
  • Anyone can view after entering their email address and selecting the verification link that is automatically sent to them.
  • Views are logged and accessible from the guideline’s Tracking page. Learn more about Tracking.
Secure embed
  • Secured from public and direct access. Only people with access to the host page can view.
  • The guideline must be embedded on a host page served from an allowed domain. See Secure embed below.
Options not included in your plan are shown but can’t be selected.

​
Sign-in methods

Enterprise Pages with Sign-in required security choose how viewers sign in. Each exception with sign-in required has its own sign-in methods.
Security Sign In Methods

​
Standard (choose one)

  • Magic link: Viewers enter their email address to receive a secure link that signs them in.
  • Email & password: Viewers sign in with their Standards account email and password.

​
Single Sign-On (choose any)

  • Google: Viewers sign in using their Google account credentials.
  • Microsoft: Viewers sign in using their Microsoft account credentials.
  • SAML SSO: Viewers sign in using your organization’s single sign-on service. Set up SAML SSO in your workspace settings first. Learn more about SAML SSO.
The sign-in methods you choose are the options shown on the guideline’s Sign-in page.

​
Allowed viewers

Enterprise Pages with Sign-in required security list who can view them. Add groups, individual email addresses, and email domains. Viewers must sign in with an email address that is on the list, belongs to an allowed domain, or belongs to an allowed group. Learn more about Allowed viewers.

​
Secure embed

Enterprise Embed your guideline inside an existing website, team portal, or DAM. When the default security is Secure embed, the Security page shows the embed settings in place of exceptions.

​
Embed code

Select Save to generate the embed code, then select Copy and paste it into the host page. The host website must be served over HTTPS and send the Referer header.

​
Allowed domains

Enter each domain that is allowed to embed the guideline, then select Add. The embed only loads on pages served from these domains.

​
FAQ

Restricted pages are now Exceptions. Instead of moving pages between a restricted and a public list, set a default for the guideline and add an exception for the pages that should be different. Each exception can have its own security, password, sign-in methods, and allowed viewers.
Yes. Add an exception for each set of pages, give each one Plain password protected security, and set a different password on each.
Content a viewer can’t access is left out of their search results. Learn more about Search.