If you want to create a ticket selling platform where users can register, create their own events, and sell tickets independently under their own accounts, you can absolutely accomplish this with Tickera. The key is to run Tickera inside a WordPress Multisite environment and give each event organizer their own subsite.
Below is a practical mini-tutorial on how to set everything up.
To support multiple event organizers, you’ll need WordPress Multisite. It allows you to run many independent subsites under one WordPress installation while sharing the same core files.
If you’re not familiar with Multisite, we recommend reviewing the official WordPress documentation before you begin.
Once Multisite is enabled, you can create a separate subsite for every event organizer.
Every organizer should receive their own subsite within your network. This setup gives them:
As the Network Admin of the ticket selling platform, you decide who gets a subsite, what plugins they can use, and the themes available.
From the organizer’s perspective, their subsite behaves almost exactly like a standalone Tickera-powered website. They can create events, manage tickets, adjust settings, and access all Tickera features without affecting anyone else.
If you want to give your organizers a more polished experience when they log into their dashboards—such as custom colors, a personalized welcome message, or a branded widget—you can check out our post on branding the WordPress dashboard.
A little branding goes a long way in making onboarding smoother and giving your platform that professional finishing touch.
Network-activate Tickera to make it available on all subsites. Each organizer can then:
Each subsite stores its event data independently.
To allow organizers to receive payments directly—and to collect a commission from each sale—you’ll need Stripe Connect.
Stripe Connect enables:
Stripe is available to businesses in most countries worldwide, making it a practical choice for nearly all multi-organizer ticketing setups.
Organizers connect their own Stripe accounts through their subsites. Once connected, Stripe automatically routes each sale, pays the organizer, and applies your platform fee.
Even though organizers operate within a Multisite network, Checkinera works exactly as if they were running their own standalone Tickera-powered website.
Each organizer can go to:
Tickera Settings -> API Access
Inside this tab, they can:
The login URL reflects the structure of your network, depending on how you've configured Multisite:
Organizers use this URL—along with their API key—to log into the Checkinera mobile app or Checkinera Web. From that point on, check-ins work exactly the same as they do on any standard Tickera installation:
There is no difference at all in the check-in procedure compared to a standalone Tickera setup. Everything is clean, isolated, and fully compatible.
Organizers manage everything inside the WP admin area of their subsite. They can:
Since Tickera does not currently support front-end event creation, organizers must work from the dashboard. Because each subsite functions as a full Tickera installation, this workflow is intuitive once they learn where things are.
If you want to take onboarding a step further, you can use the dashboard branding tips mentioned earlier to place helpful links, instructions, or short welcome notes directly inside their dashboard.
Customers interact with your platform as a single unified website. They can:
Tickera handles email notifications, ticket generation, and attendee records automatically. Organizers receive revenue directly through Stripe Connect, and your platform fee is applied instantly.
With WordPress Multisite, Tickera, and Stripe Connect, you can build a complete multi-organizer ticket selling platform. Each organizer receives their own private, fully capable Tickera environment, while you keep control over the network and earn a commission from every ticket sold.
For all future scaling, custom onboarding, or interface refinements, feel free to reach out to our support team—we’re here to help.