Why collaborators, not just co-owners
Most events are run by more than one person: someone at the door, someone on the mic, someone posting announcements. That doesn't mean everyone needs full control of the event. From your event → Collaborators, you invite people by email and grant only the specific permissions their job needs.
Inviting someone
- 1
Send the invite
Enter their email and pick which permissions to grant. They'll get an email with a link to accept. If they don't have a Joinlah account yet, accepting creates one.
- 2
Pick permissions for what they'll actually do
Common combinations: check-in staff get scan-check-in only; someone running the lucky draw gets that permission and nothing else; a co-organizer helping with logistics might get manage-RSVPs and view-stats without edit-event.
- 3
Narrow it further if needed
For check-in staff and queue operators specifically, you can go one step further and assign them to one particular session or queue, so a collaborator who should only work the Saturday session, or only Booth B's queue, can't touch the others even though they technically have the broader permission.
What each permission unlocks
- Edit event: change event details and settings.
- Manage RSVPs: approve or reject registrations, edit attendee info.
- Scan check-in: operate the check-in scanner.
- View stats: see the stats and activity pages.
- Manage agenda / slides / lucky draw / announcements / queues / ticketing: control over that specific module and nothing outside it.
Tip
A collaborator only sees the sidebar sections their permissions actually unlock: someone with just scan-check-in doesn't see a Tickets or Lucky Draw link cluttering their view at all.
Changing or removing access
Permissions, session assignments, and queue assignments can all be edited from the same collaborators page at any time; nothing requires re-inviting someone from scratch. Removing a collaborator revokes their access immediately; anything they did while they had access (check-ins they scanned, RSVPs they approved) stays in the event's activity log with their name attached, so the history doesn't disappear along with their access.