Skip to main content
Event Access is the simplest sign-in option Sign In offers: a pass-through. The guest picks Event Access on the Captive Portal and network access is granted immediately, with no verification step, no credentials, and no personal data collected. The session runs for a fixed timeout defined by the Context. Typical audiences: temporary events where guest identification isn’t required, open-to-the-public venues, guest access where the venue already knows the audience from context (ticketed events, restricted venues), situations where the captive portal’s only job is to show terms of service.
Event Access module admin page

​
How a guest signs in

  1. The guest picks Event Access on the Captive Portal.
  2. Access is granted immediately. No form, no code, no verification.
  3. The guest is redirected to the Context’s anonymous redirect URL.
  4. The session runs for the Context’s anonymous-login timeout.

​
When to use (and not use) Event Access

Use it when:
  • The venue already controls who reaches the network (ticketed, gated, or physically restricted).
  • You don’t need to identify individual guests.
  • You want to show terms of service but don’t need a verification flow.
Don’t use it when:
  • You need to know who signed in (reporting, marketing, compliance). Use one of the identity-collecting modules instead.
  • The venue is open to the public and you need some friction to discourage abuse. Use Self-Provisioning by Email or SMS.

​
Activate the module

1

Open the module

Go to Sign In Modules → Event Access.
2

Activate

Click Activate Event Access Login Module.
3

Set session defaults

The Configuration tab has a single Session Length & Redirect sub-tab. Set how long a pass-through session lasts and where guests land after sign-in.

​
Access Policies

Event Access is not gated by an Access Policy — if the module is active at Context level, it is available to any guest who reaches the Captive Portal. Keep the session length short; pass-through sessions are the easiest to abuse when timeouts are long.

Self-Provisioning by Email

When you need a low-friction flow but still want to identify guests.

Opening hours

Pair Event Access with tight Opening Hours when access should only be available during a fixed window.