Skip to content
English
Sign in
Go to goconsensus.com
  • There are no suggestions because the search field is empty.

Restricting DemoBoard Sharing by Email Domain

 

Restrict DemoBoard sharing to specific email domains

For accounts where a demo must stay inside a specific buyer's organization (NDA-bound demos, competitive risk, regulated industries), Consensus lets you restrict DemoBoard sharing to viewers whose email domain matches the recipient list — and its subdomains. This is an account-wide setting in Global Demo Settings; once on, it applies to every DemoBoard in the account.

Where to find the setting

Click Settings in the bottom-left sidebar, choose Global Demo Settings, then find the Restrict Sharing by Email Domain toggle in the Privacy & Security section.

Privacy & Security section — Restrict Sharing by Email Domain with the "Viewer Can Request Access" / "Viewer Cannot Request Access" dropdown.

Two access modes

Viewer Can Request Access (default)

When a viewer outside the allowed domain tries to enter the DemoBoard, they see a "Request Access" button instead of being granted access. What happens:

  • On the Who Are You page, the viewer is prompted to request access.
  • On the Invite Others page, anyone trying to share with an outside-domain email sees a "Sharing is restricted for this demo" warning and a notice that an access request will be sent.
  • The DemoBoard creator and any additional notifiers receive an email — they can Accept or Reject the request from there.
  • On accept, the new viewer (and any other future requests from the same email domain) is added to the DemoBoard.

Important: Once you accept an access request from a new email domain, every other viewer with that same domain will also be able to access the DemoBoard. Accepting one Gmail user effectively unlocks every Gmail user.

Viewer Cannot Request Access

The locked-down version. Viewers from outside the allowed domains cannot enter, cannot request access, and the Invite Others flow blocks them entirely. Use this when you want zero exception path — typical for highly-regulated demos or competitor-sensitive content.

When to use this

  • Healthcare / financial services demos with PHI or PII shown.
  • Pre-release product demos under NDA.
  • Competitor-sensitive content where you don't want shadow access.
  • Channel partner demos that should stay scoped to a specific partner organization.