Loading…
If your organisation uses Okta or Microsoft Entra, you sign in to webMOBI with the same account you use everywhere else — and your organisation's multi-factor policy comes with it.
Open https://events.webmobi.com/auth/login. Bookmark it — this is the address to start from, not your Okta or Entra dashboard.
Type your organisation email address (for example name@yourcompany.com). If your organisation has single sign-on set up, you'll be sent to your identity provider automatically. You can also click "Continue with single sign-on (SSO)".
Your organisation's sign-in page (Okta or Microsoft Entra) opens. Sign in the way you normally do, including any multi-factor step your organisation requires.
You're returned to your webMOBI dashboard. The first time, your webMOBI account is created for you and added to your organisation's workspace — no separate password to set.
Start from the login page, not from your Okta tile
Launching webMOBI from inside Okta or Entra currently lands on the webMOBI website rather than the app. Use events.webmobi.com/auth/login and enter your work email.
At your identity provider. webMOBI never sees your password or your MFA code; it only receives confirmation from Okta or Entra that you signed in. Whatever MFA policy your organisation enforces there applies to every webMOBI sign-in.
Your SSO sign-in creates a separate account, linked to your identity provider rather than to an email code. Both keep working. If you owned events under the older account, ask your organisation's webMOBI admin to move that role across — it's a one-time change on our side.
By default, yes — both paths work for your domain. Your organisation can ask us to make SSO the only way in, so there is no way around its MFA policy. Once that's on, the email-code option refuses your domain and points you to SSO.
Launching from inside your identity provider isn't wired into the app yet. Start from the login page instead: https://events.webmobi.com/auth/login. We'll update this page when the tile works.
webMOBI reads your name from what your identity provider sends. If it sends only your email, your profile shows no name until your IT team adds first-name and last-name attributes to the webMOBI app in Okta or Entra, or you set it yourself in Settings.
When IT deactivates them in Okta or Entra, they can no longer sign in to webMOBI. Their webMOBI record stays until an organisation admin removes it — we don't automatically delete accounts (there is no SCIM provisioning).
SSO is a SAML 2.0 connection between your identity provider and webMOBI. Okta and Microsoft Entra are supported; others that speak SAML 2.0 usually work.
Setup is done once per organisation by webMOBI support: you create a SAML app in your identity provider using the two URLs we give you, and send us its metadata URL and your email domain.
Provisioning is just-in-time. A person's account is created on their first sign-in and joins your organisation automatically with the member role; your admins promote from there. Seats count per account.
Single sign-on is included in the Enterprise plan. Contact support with your identity provider and email domain, and we'll send the two URLs your IT team needs.
Contact support →