It should look like your event, not like our system
The crew meets the portal, the email and the pass. All three can carry your name, your colours and your sender address, and the rules behind them are set per event instead of being the same for everyone.
From logo to your own domain
Every event has its own expression. Logo, favicon, sidebar colour and primary colour are set per event, so an organizer with several events does not have to pick one shared design. If it needs to go further, the portal can run on your own domain with your own sender address, and the layout can be rewritten with your own CSS. We set that up together with you.
What you can set up yourself
- Logo, favicon and colours: set per event, both on the sidebar and as the primary colour in the portal.
- Email templates: your own texts per language and per user type, with your sender name and sender address.
- The crew portal: you add tiles and links on the portal front page yourself, so the crew can move on to what sits outside the system.
- Ticket designer: upload your own background and place the QR code or barcode, the product list and fields from the registration exactly where they should be, so passes come out as a PDF in your design.
- Your own domain: the crew portal can run on your own domain with your own sender email. We do the setup together with you.
- Full CSS and page layout: if the design has to follow your graphic line all the way, the layout can be rewritten through templates. That is set up as part of the setup.
Settings and integrations
Part of the adaptation is not about design, but about which rules apply at your event, and what the system has to talk to.
Rules per event
Waiting list, withdrawal, several teams per crew member, minimum age, team tags, shift swaps and shift picking are turned on and off per event. Two events at the same organizer do not have to run the same way.
Stripe
The registration can require payment, and guests can pay a fee or give a donation for the ticket. The payments go through Stripe.
Mailchimp
The crew members can be synced to a list in Mailchimp, if you run newsletters from there.
RFID and NFC wristbands
Access and product rights can be synced to wristbands. EventPos and Corego are integrated today, and other providers are connected by agreement.
Passes per user type
The ticket templates can vary per user type and per language, so an artist and a crew member do not get the same pass.
Several events at the same organizer
The setup is reused across years and events. Schedules can be pulled in from an earlier event and placed on new dates.
There is currently no public API, no webhooks and no SSO. The integrations above are the ones that exist, and new ones are built by agreement.
See the system in your colours
Tell us what your registration and your passes look like today, and we will show you how close we get.