What it does Expands Grip's SSO support to work across multiple live events under a single OIDC configuration. Organisers running several events no longer need a separate SSO application per event — one setup covers them all.
Why it matters
🗝️ One login, every event Attendees authenticate once and move seamlessly between events in a portfolio, without hitting separate login flows or being prompted to re-authenticate for each one.
📈 Unblocks SSO adoption at scale The previous single-event limitation was a hard blocker for organisations wanting to roll SSO out across a full event programme. That ceiling is now gone.
⚙️ Built on OIDC — the standard teams actually use OIDC is the most widely requested SSO protocol Grip receives. This update makes multi-event support available to the majority of customers looking to implement SSO, not just those on SAML.
🛡️ Same security, broader reach All existing SSO scope and configuration requirements still apply — the change is purely in how many events a single configuration can serve, not in the security model underpinning it.
The result Organisations running multiple events can now implement SSO properly, once — with a single OIDC configuration that works across their entire Grip portfolio.