The console the event is actually run from
The organizer console is the browser application behind the attendee app: where events, sessions, speakers, sponsors and attendees are created, where photos and questions are moderated, where campaigns are sent and where the numbers are read. It is responsive, so the person at the door and the person at the desk are using the same tool.
What this looks like in the product
Twenty-two pages, grouped by the job being done rather than by the part of the system doing it.
- Multi-tenant organisations
- One organisation can hold many events, with access scoped per event.
- Four levels of access
- Platform staff, organisation super-admins, organisation admins and per-event moderators.
- Audit logging
- Console actions are recorded, which is what makes delegating moderation to volunteers safe.
- Live moderation
- Approvals for photos and Q&A, plus dedicated poll and Q&A moderator views.
- Admin team chat
- An organiser-only channel with reactions, replies, delivery ticks and an audit trail.
Console sections
- Events, Sessions, Speakers, Sponsors
- Attendees, RSVPs, Approvals
- Q&A and Polls moderation
- Communications, Templates, Forms
- Engagement, Reports, Billing, Team, Theme
Roles are the feature that makes a volunteer team possible
Most events are run by more people than have any business holding full administrative access. A student volunteer on the photo queue, a client's marketing manager who wants to watch the numbers, a moderator who is only there for the Thursday keynote.
Giving all of them an organisation admin login is how a roster gets deleted the week before the event. Refusing to give them anything is how the organizer ends up personally approving four hundred photos.
event67 has four: platform staff, organisation super-admins, organisation admins, and per-event moderators. A moderator is scoped to one event and to the moderation work, which means the Thursday volunteer can approve the Thursday queue and cannot touch the attendee list, the billing or next month's event.
Two console areas write an audit record: admin chat and billing. Moderation does not, and neither does check-in, so if somebody asks afterwards who removed a photo or admitted a person who was not on the list, the product cannot tell you. Scoping the role is therefore the control that matters, and we would rather say that plainly than let a buyer assume an audit trail that is not there.
Two different jobs at two different times
The console does two jobs that barely resemble each other, and it is worth knowing which pages belong to which.
Build the event
Sessions, tracks, rooms, speakers and sponsors, in the console.
Invite from a CSV
Bulk import, with delivery tracked per recipient.
Open the doors
Scan badges at the desk; a second scan says "already", not "error".
Read the room
Active attendees, funnels and which sessions are filling, live.
| Phase | Pages | What good looks like |
|---|---|---|
| Preparation | Events, Sessions, Speakers, Sponsors, Theme, Attendees, Communications | Slow, careful, done days ahead |
| Live | Approvals, Q&A Moderator, Polls Moderator, Activity, Engagement, Announcements | Fast, glanceable, done standing up |
| After | Feedback, Reports, Billing | Read once, exported, archived |
The live pages are the ones that decide whether a console is any good, because they are used by a tired person on a phone at the side of a room. That is also why the console is responsive rather than desktop-only: a moderator at the back of a hall is not carrying a laptop.
The team's own channel
Admin chat is an organiser-only channel inside the console, with reactions, replies and delivery ticks, and an audit trail behind it. Attendees do not have chat and cannot see this.
It exists because the alternative is a group message thread on somebody's personal phone, which is where event decisions go to become undocumented. Keeping the operational conversation next to the operational tools means the instruction to hold the keynote and the button that announces it are in the same window.
Setting the team up, the week before
Access is the piece most teams do at the last minute, and it is the piece that is expensive to get wrong. It takes about ten minutes if it is done deliberately.
Decide who genuinely needs the attendee list
Usually two people. Everybody else is doing a job that does not require it, and giving it to them anyway is how a roster gets edited by somebody who thought they were in a different event.
Make the volunteers per-event moderators
Scoped to the one event and to the moderation work. They can clear a photo queue and a Q&A queue; they cannot reach billing, the roster or next month's event.
Agree the moderation rule before the queue exists
What gets held, what gets dismissed, and who decides when it is genuinely ambiguous. A volunteer facing a hostile question at 14:20 should be executing a decision, not making one.
Put one person on announcements
Announcements are the loudest thing the product does. One owner is the difference between a useful channel and one the audience mutes on the first morning.
Say out loud what is not recorded
Admin chat and billing are recorded; moderation and check-in are not. Tell the team that at the start, because it means a disputed removal cannot be settled by looking it up, and the answer has to be an agreed rule rather than a log.
What the console will not do
- No registration or ticketing pages, because event67 does not sell tickets. Your list comes from wherever registration already happens.
- No budgeting, supplier management, contracts or venue sourcing. This is not an event-management suite.
- No custom fields, custom pages or a plugin model.
- No public API, no webhooks catalogue and no integration marketplace.
- No white-labelling of the console itself. The attendee app carries your brand; the console is an internal tool and looks like one.
- No in-app attendee account deletion, and the deletion that does run leaves attendee-authored content in the event. Requests go to privacy@event67.com and through the delete-account page. Both gaps are real.
Who is in here every day
The producer who owns the event end to end. The communications person who sends the four emails. The two volunteers on the approvals queue for two days a year. The finance contact who looks at Billing twice and never opens anything else.
The design consequence of that mix is that the console has to be legible to somebody who uses it once. Most of the roles above are not power users, will not be trained, and will be doing this while something else is going wrong.
Last updated
What it costs
- Free up to 50
- activated attendees, on one live event
- $5
- per activated attendee beyond 50
- $4,750
- the most one event can ever cost, whatever happens past 1,000
Activated means the person claimed their invite and opened the app. Not when you import them, not when the invite is delivered, and not if they register and stay home.
Questions people actually ask
Can we give a volunteer access to moderation only?
Yes. A per-event moderator role is scoped to one event and to the moderation work: they can work the approvals and Q&A queues and cannot reach the attendee list, billing or your other events. Their reach is the control here, since moderation actions are not attributed to a person.
Does the console work on a phone?
Yes, it is responsive, and that is a requirement rather than a nicety. The live pages get used by somebody standing at the back of a hall, and a moderator carrying a laptop is a moderator who has stopped moderating.
Is this an event management system?
No, and it is worth being clear about it. There is no registration, no ticketing, no budgeting, no supplier or contract management and no venue sourcing. event67 runs the attendee experience and the organiser's side of it. The rest of your event stack stays where it is.
Can we integrate the console with our own systems?
No. There is no public API, no webhook catalogue and no integration marketplace. Attendees come in by CSV import and results leave in the end-of-event report.
Can attendees see the admin chat?
No. Chat is admin-to-admin only. Attendees have no chat feature at all, and the organising team's channel is not visible to them in any form.
How many admin users can we have?
There is no seat charge for console users and no per-admin fee. Pricing counts activated attendees only: 50 free, $5 each after that, capped at $4,750 per event.
Keep reading
What you run from here
Event types that lean on this
See it in your own event
Your first 50 attendees are free on every event, so the smallest version of this costs nothing to try.