Skip to main content

Require sign-on for a site

Turn on gated access so visitors must sign in before they can view a microsite. Gating is useful when a site contains internal, licensed, or subscriber-only content and you want to confirm identity before the page loads. The underlying sign-on method (SSO, such as Microsoft Entra ID) is configured once in Administration; on the site itself you simply switch gating on and choose who is allowed in.

Before you begin​

  • Your account must already have a sign-on method configured. SSO setup lives in Administration and is typically handled by an admin — (confirm the exact steps in your account).
  • Know which subscribers or groups should be allowed through the gate.
  • Have the microsite published or ready to publish, so you can test the sign-in flow end to end.

Steps​

  1. Open the microsite you want to protect and go to its access or security settings.
  2. Turn on the option to require sign-on (gated access) for the site.
  3. Choose the sign-on method to enforce (for example, SSO / Microsoft Entra ID) if more than one is available.
  4. Set who is allowed in — everyone who can authenticate, or only specific subscribers or groups.
  5. Save your changes, then publish or re-publish the site so the gate takes effect.

(Confirm the exact menu labels and toggle names in your account.)

Result​

Visitors who open the site are now prompted to sign in first. Authorized subscribers reach the content after signing in; anyone who cannot authenticate is blocked. Test by opening the published URL in a private browser window and completing the sign-in flow yourself.

Canonical terms: Author, Edition, Folder (Project Folder), Broadcast. See the Glossary.