Roles, languages and traceability
Who gets to see what, what things are called, and who changed that thing last Tuesday. The dull part that lets five people work in the same event without getting in each other's way.
The essentials first
Roles and permissions
Let the communications officer edit the text without being able to see the finances. A matrix, not a negotiation.
Languages and labels
Swedish and English side by side — and every word in the interface can be changed to the event's own terminology.
Log and copy event
A timeline of who changed what. And next year starts from last year's set-up.
Everything included
All of the administration in plain words — every feature included, nothing left out. Ask if your organisation needs something that isn't listed here.
Users and roles
- Roles with preset permission levels
- Custom roles built around a function rather than a person
- Permissions per module: read, edit, none
- Permissions per event — access only to what you are working on
- Temporary access for a volunteer or consultant, with an end date
- Sign in with a link or a password
- Two-factor authentication where you require it
- Single sign-on with your own login
Several events and organisations
Event overview with every event, upcoming and completed
Copy an event as a template for next year
Organisation profile: logo, colours, sender addresses
Shared resources — hotels, templates and venues
Archived events that can be opened but not changed
Languages and texts
- System language for those of you working in the tool
- Participant language per event, with a language choice
- Your own terms — call things what you call them
- Text library for emails, forms and confirmations
- Translation per field instead of separate events
Traceability
- Event log per record: what changed, when and by whom
- Login log
- Versions of texts and templates
- Export log — who took out which personal data
Data and regulations
- Retention rules with automatic clean-up after a set time
- Subject access reports per participant
- Deletion on request, with statistics kept
- Consents logged with timestamp and wording
- Data within the EU and a data processing agreement
- Backups and restore
The details that make the difference
The things that turn up in week three of planning — built in from the start.
Policy and GDPR
Retention rules, consents and data processing agreements in place from the start.
Custom roles
Build the role that suits the organisation instead of choosing from three ready-made ones.
Volunteer views
Give the staff exactly the view they need at the entrance — and nothing more.
Two-factor authentication
Strong sign-in required for the roles that handle finance and personal data.
Five people in the same event and nobody changed the wrong thing by mistake.Project manager, recurring trade fair