Skip to content

Winglark

Stage 01 · PrepareEvent operations5 min read

Event team roles and permissions: who does what, and who sees what

Event team roles and permissions decide two things at once: who does each job on the night, and who can see each guest’s details. Most teams get the first part right on a whiteboard and leave the second to chance, so that the freelance door host can export the whole list, a sponsor’s stand staff can read every guest’s phone number and the intern who left in spring still has a login. Getting roles right is not bureaucracy. It is how a team moves fast without stepping on each other, and how a guest list stays the private thing guests assumed it was.

Start from the jobs, not from the people

Write down the jobs the event needs before you write down names. A small dinner may need two: someone who owns the event and someone at the door. A conference needs a dozen, and some people will hold several. Naming jobs first stops the common mistake of giving everyone the same full access because it was quicker to set up.

Each job then gets the smallest set of permissions that lets it be done well. When a person holds two jobs, they get both sets, and nothing more.

The roles a real event team has

Names vary between organisations, but the jobs repeat. Most events of any size need some version of these, and a team that has them clear can staff a new event in minutes.

  • Owner: responsible for the event, its settings, its budget and who is on the team; usually one or two people.
  • Guest list: builds and cleans the list, sends invitations and reminders, follows up replies.
  • Design: prepares the invitation and other guest-facing pages, without needing to see guests’ contact details.
  • Door staff: admit guests on the night; see names and admission status, not email addresses or notes meant for the organiser.
  • Live moderator: approves questions, runs polls and decides what reaches the big screen.
  • Sponsor or exhibitor desk: sees the leads that visitors chose to share with that sponsor, and nothing else.
  • Viewer: reads progress and reports, changes nothing; the right role for a client, a manager or finance.

Least access is a kindness, not a suspicion

Giving someone less access is sometimes read as distrust. It is the opposite: it protects them. A door host who cannot export the list cannot be blamed for a leak; a sponsor team that sees only consenting visitors cannot be accused of harvesting. Explain it that way and most people are relieved.

Least access also reduces mistakes. A person who can only scan at the door cannot accidentally resend the invitation to four hundred people, and a viewer cannot delete a guest while trying to read a report.

Door staff on their own phones

Door teams are often hired for one night, and the simplest scanner is the phone already in their pocket. That works well if the door role is narrow: the phone shows the door list for this event, scans guests in, and stops working for that person when the event is over. It should not open the organiser’s inbox, the full guest record or any other event.

Brief the door team before guests arrive: how to sign in, what to do when someone is not on the list, who to call for a VIP or a problem, and which entrance each person covers. A role on the screen is only half the job; the other half is knowing whom to ask.

Live moderators and sponsor desks

Anyone who decides what appears on a screen in front of the room holds a sensitive role. Give live moderation to named people, briefed on what the host wants and what is out of bounds, and keep the moderation queue off the public screen.

Sponsor and exhibitor staff are outside your organisation, so their view should be the narrowest of all: the visitors who chose to share details with that sponsor, with the consent they gave, and no access to the wider guest list. That boundary is what lets guests trust the stand.

Handover between shifts and coordinators

Long events change hands. The morning door team leaves at two; the coordinator who built the list is off on the day. Write a short handover note per role: what is done, what is waiting, which guests need attention and who to ask. The note matters more than the login, because a new person with full access and no context is still guessing.

  • Who holds which role, by name, with a phone number for the day.
  • Open items: replies to chase, guests to add, questions waiting.
  • Exceptions agreed in advance: VIPs, press, late arrivals.
  • Who can approve something unusual at the door.
  • When each person’s shift ends and who takes over.

After the event: close the doors behind you

The easiest permission to forget is the one nobody needs any more. When the event ends, remove door staff, freelancers and sponsor teams from it, and review the remaining team once the report is sent. Keep a record of who had which role, so that a later question about who changed a guest’s details has an answer.

Do the same with shared devices. A tablet used at the door should be signed out of the event before it goes back into a drawer.

Questions

What roles does an event team need?

At minimum someone who owns the event and someone at the door. Larger events add guest list management, design, live moderation, sponsor desks and read-only viewers for clients or managers. Name the jobs first, then assign people.

Should door staff see guests’ contact details?

Usually not. Door staff need names, admission status and any instruction for that guest, such as a VIP note. Email addresses, phone numbers and internal notes should stay with the people who manage the list.

Can volunteers or temporary staff use their own phones at the door?

Yes, if their role is limited to scanning for that event and their access ends with it. Brief them on signing in and on what to do when a guest is not on the list.

How does Winglark handle team roles?

Winglark has seven roles that match a real event team, so each person sees and changes only what their job needs. Door staff check guests in on their own phones, and any phone becomes a scanner.

Keep reading

The rest of the journey

  1. 02 · InviteNext stage

    Event invitation email best practices

    Sender, domain, deliverability, the one link that matters, versions, resends and the delivery record — how to send event invitation emails that arrive and are answered.

  2. 03 · RSVP

    RSVP management guide: replies, plus-ones, no-shows

    How to collect replies that mean something, handle plus-ones and dietary questions, follow up the silence, and measure RSVPs against who actually came.

  3. 04 · Door

    Event check-in guide: QR codes, offline, walk-ins

    How to run event check-in that holds up on the night: personal QR codes, a phone as the scanner, no signal, repeated scans, walk-ins, several doors and a report you can trust.

  4. 05 · Live

    How to run live Q&A at an event, without an app

    How to run live Q&A at an event: one QR code, questions moderated before the room sees them, upvotes, and a fair close — no app for the audience to install.

  5. 06 · Review

    Corporate event guest management checklist

    From the first list to the report upstairs: a checklist for the guest side of a company event — roles, segments, the sender domain, doors, exceptions and data.

Your first event is free.

Fifty guests, real invitations, real replies. No card required.