Skip to main content
Most deployments require guests to accept terms of service before joining the network — for legal, compliance, or brand reasons. Sign In records the exact terms version each guest accepted, so you always know which policy applied to which login. Terms and conditions live under Administration → Compliance → Terms and Conditions in the Context admin.

​
How it works

  1. You author terms content per language in the admin.
  2. The Captive Portal shows a short acceptance line with a link to the full text on every sign-in form.
  3. When the guest submits a sign-in, the portal records the currently active terms version alongside the login for compliance purposes.

​
Editing terms

You can keep terms in two forms:
  • Short acceptance text — a one-liner shown on the portal next to a checkbox, for example “I accept the terms of service”.
  • Full text — the longer document linked from the acceptance line. Typically formatted as a simple HTML document served by the portal.
Edit terms in plain language and keep formatting simple. Guests are impatient and will skim. Keep the short acceptance line under ten words, and structure the full text with clear headings.

​
Versioning

Every time you edit terms, a new terms version is created. Active logins remain valid — they already reference the version that was in effect when the guest accepted. Future logins use the new version. The per-login terms reference is recorded internally for compliance purposes. It is not currently surfaced in the admin UI.

​
Languages

Terms text is stored per language, using the same locale codes as the rest of the portal. See Languages for the list of supported locales and how overrides work. At minimum, author terms in your venue’s primary language plus English.

​
Per-module behaviour

All Sign In Modules include the terms-acceptance step. Some modules make this more visible than others:
  • Email, SMS, Password, Meeting Host, Conference, Self-Provisioning — explicit checkbox on the sign-in form.
  • SAML, RADIUS — acceptance happens at the portal before the guest is redirected to the IdP or authenticated against RADIUS.
  • Quick Access — acceptance happens on the Click-to-Connect tile itself, alongside the connect button.
  • Whitelist — headless devices bypass the Captive Portal entirely, so terms acceptance never runs in that path. Ensure your terms explicitly cover devices whitelisted by their owner.

​
GDPR and data retention

Terms are separate from — but often reference — data retention policies and GDPR data-subject rights. Coordinate terms copy with Compliance settings so your guests see a consistent story.

Languages

Localize terms copy per supported locale.

Sign In Modules

Each module presents acceptance slightly differently.