For teams and agencies
The right person. The right access. Event software for teams and agencies — one workspace per client.
Roles that match how an event team actually works, a workspace per client for the people who run events on behalf of others, and an Agency plan sized for doing it continuously.
Workspace
- OwnerEverything, billing included
- ManagerEvents, guests, reports
- MarketingCampaigns, senders, consent
- Guest listGuest lists and invitations
- Door staffThe scanner only
- Reports onlyReports and exports
- Partner staffA named door at a named event
Who sees what?
Choose a role. See exactly what it opens.
Door staff should not see billing. A guest manager should not be able to delete the event. These are not permission checkboxes invented for a settings screen — they are the jobs people actually do on the night. Read from the product’s own permission table — the same one the server enforces — so this view cannot promise more than a role really has.
Owner — Everything, including billing and deleting the organisation.
- Guest dataNames and contact detailsFull
- InvitationsCreate and sendFull
- DoorScan and approve exceptionsFull
- ReportsFullFull
- BillingFullFull
- Team and settingsFullFull
- Client scopeEvery clientFull
| Choose a role | Guest data | Invitations | Door | Reports | Billing | Team and settings | Client scope |
|---|---|---|---|---|---|---|---|
| Owner | Full: Names and contact details | Full: Create and send | Full: Scan and approve exceptions | Full: Full | Full: Full | Full: Full | Full: Every client |
| Manager | Full: Names and contact details | Full: Create and send | Full: Scan and approve exceptions | Full: Full | No access: No access | Full: Full | Full: Every client |
| Marketing | Limited: Names, contact details masked | Limited: Read only | No access: No access | Full: Full | No access: No access | No access: No access | Limited: Assigned clients only |
| Guest list | Full: Names and contact details | Full: Create and send | Limited: Scan and admit | Full: Full | No access: No access | No access: No access | Limited: Assigned clients only |
| Door staff | Limited: Names, contact details masked | No access: No access | Limited: Scan and admit | No access: No access | No access: No access | No access: No access | Limited: Assigned clients only |
| Reports only | No access: No access | No access: No access | No access: No access | Full: Full | No access: No access | No access: No access | Limited: Assigned clients only |
| Partner staff | No access: No access | No access: No access | Limited: Scan and admit | No access: No access | No access: No access | No access: No access | Limited: Granted per event |
One team, different responsibilities
Roles that match a real event team.
The assistant needs the list, the agency needs its client, the receptionist needs a scanner and management needs the report. Giving everyone everything is the easy setting and the wrong one.
- Marketing
- Executive assistant
- Agency
- Reception
- Door staff
- Management
Role-based control
Agencies and client workspaces
Several clients, one agency, no crossed wires.
Tell us how many events you run and how big they are, and we will tell you whether Agency is the right shape — including when it is not.
The Agency plan
- A separate workspace per client, separated on the server
- The highest ceilings on every limit — events, guests, sending, doors
- The Winglark mark removed; your brand on invitations and door screens
- One subscription covering every client
Agency
- Client A
- Manager
- Door staff
- Client B
- Partner staff
- Guest list
- Client C
- Reporter
Four team contexts
Four ways teams use it.
Agencies
Several clients, several live events, and a team that changes per job. A separate workspace per client, your own brand on everything a guest sees, and one subscription over all of it.
- Workspace per client
- Your brand on guest surfaces
- Staff assigned per client
- One subscription
Venues
A calendar rather than an event. A different organiser every week, the same doors, the same staff, and the same need to prove how many people came through.
- Several live events
- Multiple doors
- Door staff accounts
- Capacity enforced at the door
- An audience kept between events
Companies
Launches, conferences, dealer meetings, internal days. Approvals, brand control, and a report somebody upstairs will ask for.
- Team roles
- Custom design
- Attendance against replies
- A report you can hand over
- Programme and networking
Cultural institutions
Private views, press previews, collector invitations. Who came matters more than how many, and the record feeds the relationship afterwards.
- Guest segments
- Press lists
- Attendance by segment
- CSV and Excel export
Client boundaries
Client data should not bleed across workspaces.
Every lookup is checked on the server against the workspace and the client it belongs to. Somebody who does not run the workspace sees only the clients they are assigned to, and a record from another client behaves as if it does not exist.
How isolation works →Client sign-off
Your client approves the seating plan from a link.
Agencies send a review link from SeatMap; the client approves the plan or asks for changes.
See SeatMap →Name badges
Each client’s badges, in that client’s colours.
With BadgeDesk, a guest manager designs the badge once with the client’s logo, door staff print each one after the scan, and a tablet kiosk lets guests check themselves in — every badge recorded against the event.
See BadgeDesk →On the night
Live operations follow the same roles.
In Event Control Room, owners and managers run the evening, guest managers run polls, questions and announcements, marketing watches, and the door team keeps its own door view — the roles your workspace already has.
Integrations
A key for each system, not a shared password.
Each workspace creates its own API keys with only the scopes a system needs, revokes them at any time, and sees every webhook delivery in a log.
See the integrations →Questions
Which roles exist?
Seven: organisation owner, manager, marketing, guest manager, door staff, report viewer and partner staff — each with the access its job needs and no more. Door staff see the scanner and nothing else.
Can a role be given for one event only?
Yes. A role is assigned for one event or for the whole organisation, and door staff can be given limited, time-bound access for a device.
How does an agency keep its clients apart?
The Agency plan gives a workspace per client, with the data separated on the server. Partner staff see only the event and the door they are given.
Is every action attributed to a person?
Yes. Every privileged action is recorded with the name of the person who did it — including every admission at the door.
Can sponsors and exhibitors work their stands without seeing our event?
Yes. Each stand has a console of its own for its lead and staff. They see only their own sponsor’s visitors and the contacts guests agreed to share with that sponsor — never your guest list, other stands or your settings.
Work together without giving everyone everything.
Roles for the people who run the event, a workspace per client for the agencies who run them for others.