Skip to content
EventProgrammer

Who sees what: roles, links and history

Your team signs in with a role; field teams and hotels work without an account, from a link that shows only their own job.

Company roles and event access

Owner, admin, editor and viewer roles, with a permission matrix you can edit. Members can be given access to specific events only. The viewer role can serve as read-only access for someone on the client side.

Event history

Who did what and when, across accommodation, links, registration and transfers, filterable by date.

What it doesn’t do yet

  • There’s no dedicated client summary screen; read-only access is given with the viewer role.
  • The history summarises guest changes; it doesn’t show field-by-field before and after values.

Frequently asked questions

Do hotels and drivers need accounts?
No. Hotels, the registration desk and the transfer team work from the link you send them, and you can switch a link off at any time.

Keep the list live, not in a spreadsheet.

In EventProgrammer each hotel sees only its own guests on a live link, so changes reach it without a new version. After the event, planned and actual nights come out room by room in the reconciliation report, with no-shows and early departures flagged.