Webhooks

Sign In emits the richest event stream of any service on the platform. Where the other services publish only configuration changes, Sign In also publishes what happens to guests and their devices, which is what makes it useful for occupancy reporting, visitor analytics and building integrations rather than only for audit.

Event catalogue

Session lifecycle

The record of a guest signing in and what became of that session.

Event	Emitted when
`signin.session.created`	A guest started a new sign-in on the captive portal
`signin.session.resumed`	A returning guest resumed a previous session on the same device
`signin.session.requested`	The sign-in needs approval, from a meeting host or a device-approval policy, and is waiting
`signin.session.approved`	An approval was granted
`signin.session.verified`	The guest completed a verification step, such as an email link or an SMS code
`signin.session.denied`	The sign-in was denied
`signin.session.revoked`	An active session was ended by an administrator, a device block, or a policy change

Arena sessions

Arena sessions are the venue-bound access records used by the event-access and whitelisted-device flows: a device joins the network inside a venue’s space, and the arena session tracks that visit.

Event	Emitted when
`signin.arenasession.login`	A device joined the venue’s network and an arena session was created
`signin.arenasession.resumed`	A device with an active arena session re-associated, for example after a brief disconnect

DHCP

Available where Sign In serves DHCP through a Service Gateway.

Event	Emitted when
`signin.dhcp.granted`	A lease was granted to a device associated with a Sign In session
`signin.dhcp.expired`	The lease ended, through expiry, disconnection, or a missed expiry the platform detected

Configuration audit

Event	Emitted when
`signin.configuration.audit`	Any audited configuration change inside the context, such as a login module, an access policy, a site or a service setting

Delivery

Destination, scope, instant or batched delivery, the secret token, retries and the delivery history are the same across every service and are described under Integrations.

Login modules: the sign-in methods that produce these session events.
Logging, Reporting, and Retention: the in-portal audit record, as opposed to the stream.

Compliance

How Sign In supports the legal side of running a guest network: versioned terms, a privacy policy, configurable retention, end-user reports, and opt-out.

Introduction

Cloud DNS is a managed, filtering DNS resolver for a Sign In Enterprise network: subscribe to blocklists or build your own, allow the domains you trust, and apply rulesets network-wide or per site, on a schedule.