Running an event alone doesn't scale past a certain size. Co-hosts let you add other people to an event with a defined level of access, instead of sharing your login.
Inviting a co-host
Go to Host → your event → Co-hosts, or the co-host field on the create/edit form. Enter the person's email or @username and pick a role.
Only the organizer — the person who created the event — can invite, remove, or change the role of a co-host. An Editor co-host has full run of the event itself but can't reshape the host roster; that stays with the organizer.
Invites are two-step
Adding someone doesn't make them a co-host right away. It sends an invitation that shows up on their Invitations page (in the nav once they're signed in), and nothing about their access changes until they accept it. Until then they show up in the Co-hosts panel as a pending invite, and you can revoke it any time.
If the invitee doesn't have an Offkai account yet, they get a sign-up link by email — creating the account via that link counts as accepting, so there's no separate accept step for brand-new users.
Once accepted, the co-host sees the event under Host in the nav alongside their own events, so they don't need your login or a shared link to find it.
A co-host says they can't see the event. They haven't accepted yet — point them at their Invitations page. Nothing happens on your side until they click Accept.
The two roles
Editor — full access to the event. That includes editing every field, managing guests, approving payments and refunds, sending broadcasts, and cancelling a live event. The only things an Editor can't do are:
- Change the organizer's payout/Stripe setup (an Editor can add their own Venmo, Zelle, Wise, or other handle to the event, but can't touch the Stripe connection or fee configuration unless they're the host whose Stripe account is actually bound to the event).
- Delete a still-in-draft event — draft deletion is organizer-only. (A live event can still be cancelled by an Editor; cancelling and deleting are different actions with different guards.)
Scanner — door-only access. A Scanner can open the guest list and check people in, full stop. No editing, no financial access (no viewing or approving payments, no refunds), and no attendee contact details beyond what's needed to check someone in. This is the role to hand a friend who's just working the door for the night.
See Approving payments for what an Editor sees on the payments queue, and Check-in modes for what a Scanner sees at the door.
Payment methods are per co-host
Each co-host who has their own saved payment methods (Venmo, Zelle, PayPal, Wise, Cash, or Other) can select which of their own methods apply to a shared event — not the organizer's. That's how a co-hosted event ends up listing several people's payment handles side by side: everyone picks their own, and the combined set is what attendees see when they RSVP. Removing a co-host also removes their payment handles from that combined set.
Changing or removing a co-host
From the Co-hosts panel, the organizer can change a co-host's role (Editor ↔ Scanner) or remove them entirely, at any time. Removing someone immediately drops their access — they stop seeing the event under Host on their next page load.