Enterprise event ticketing
your IT team will sign off on.
Single sign-on with your identity provider, access limited to the events each person runs, an API for your own systems, and invoices for buyers whose employer pays. The code is open source, and all of it is included.
Single sign-on is switched on by request. Everything else on this page is in every account.
For teams that run a lot of events, with a lot of people
Corporate events teams
Customer conferences, partner summits and internal events, run by people who sign in with the company account.
Conference ticketing ›Universities and colleges
Each department or society as its own organizer, with staff limited to their own events and finance kept to the finance office.
Associations and member bodies
An annual conference, regional events and training days, with invoices and bank transfer for members whose employer pays.
Agenda and speakers ›Agencies
Every client as a separate organizer with its own branding and Stripe account, and client staff who can see their event and nothing else.
Sign in with the company account
Connect Okta, Microsoft Entra ID, Google Workspace or any OpenID Connect provider, verify your email domain, and choose whether everyone on it must use single sign-on. Once it is required, someone switched off in your identity provider can't sign back in.
- Once SSO is required, nobody can sign up separately with an email on your domain
- New people added on first sign-in, with the role you choose
- Exempt a contractor or a service account, one person at a time
- The owner keeps a break-glass sign-in, and admins hear when it is used
Everyone sees what they need. Nothing else.
Give each person a role and decide what it covers: the whole account, one organizer and all of its events, or a single event. Finance can see revenue without editing an event, and the venue team can see attendees without seeing a single price.
- Admin, Organizer and view-only Viewer roles
- Revenue, reports and payouts hidden unless someone needs them
- Refunds given to the people you choose
- Two-factor sign-in required for the whole account, in one switch
Your systems, kept in step
A REST API for your CRM, badge printing or finance system, with an interactive reference inside the app. Keys are read-only or read and write, act with the access of the person who made them, and can be set to expire. Webhooks push orders, refunds and check-ins to you as they happen.
- Events, products, orders, attendees, check-in and reports
- Keys can't touch the team, payouts or security settings
- Signed webhook deliveries, with a log of the most recent ones
Paperwork your finance team expects
Invoices with your numbering, business details and tax number on every order. Bank transfer for buyers who can't pay by card. VAT or sales tax inside the price or added at checkout. And the money goes into your own Stripe account as tickets sell, not into ours.
One account, every department
Each department, brand or client gets its own organizer, with its own public page, branding, payouts and event defaults. Give people access to their organizer and they see its events, including the ones created next year.
What your IT team will ask about
Identity
- Okta, Microsoft Entra ID, Google Workspace or any OIDC provider
- Verified email domains, rechecked daily
- SSO required, with exemptions per person
- New people added on first sign-in, with a default role
- Session length from 1 hour to 7 days
- Owner break-glass access, with every admin alerted
Access
- Admin, Organizer and Viewer roles
- Whole account, or specific organizers and events
- Financials hidden from people who don't need them
- Refund rights given separately
- Team access on each event and organizer
- The owner alerted when an admin is added
Integrations
- REST API with an OpenAPI reference
- Read-only or read and write keys
- Keys that expire, with a reminder first
- Signed webhooks for orders, attendees and check-ins
- Spreadsheet exports of attendees and answers
- Sales events from the widget for your analytics
Security
- Two-factor sign-in, required for everyone if you like
- Recovery codes and 30-day trusted devices
- Email alerts for new keys and security changes
- Card-testing protection at checkout
- Open source code anyone can read
- Payments in your own Stripe account
What Hi.Events doesn't do yet
Better you hear it here than halfway through a security review.
- SAML
- Single sign-on uses OpenID Connect. Okta, Entra ID and Google Workspace all support it, and so do most other identity providers.
- SCIM provisioning
- People are added the first time they sign in through SSO, with the role you choose. To remove someone, deactivate them on the Team page.
- Custom domains
- Event pages live on hi.events. To sell on your own domain, embed the ticket, lineup or schedule widget on your site.
Enterprise ticketing, answered
How do we get single sign-on?
Which identity providers work?
What if our identity provider goes down?
Can we give a contractor or a venue access to one event only?
Can our CRM or finance system pull the data?
Can delegates pay by invoice?
What does it cost?
Can we read the code or run it ourselves?
We have a security questionnaire. Who do we send it to?
Bring Hi.Events to your team
Tell us how many events you run and who needs access, and we'll get single sign-on set up with you.
Free for organizers, with no monthly fee, seat licence or contract.