Roles and access
Owner, manager, concierge β exactly what each one can reach.
Roles and access
Three roles, and each one is a decision about what someone at your desk
can break.
What each role can do
| Owner | Manager | Concierge | |
| --- | --- | --- | --- |
| Track guest flights, book taxis | β | β | β |
|---|---|---|---|
| Screens: create, edit, delete | β | β | β |
| Content and slides | β | β | β |
| Airports | β | β | β |
| Analytics | β | β | β |
| White-label | β | β | β |
| Transport partner, pickup defaults | β | β | β |
| Invite and manage people | β | concierges only | β |
| Billing | β | β | β |
| Add or remove a property | β | β | β |
| Organization brand and shared content | β | β | β |
Owner is organization-wide: every property, every setting, the
invoice. Manager and concierge are granted per property β someone
can manage Vienna and be a concierge in Salzburg.
A manager can invite and manage concierges, not other managers. That
keeps the ability to widen access with the owner.
Inviting someone
Users β Invite. Give the email, the role, the properties they should
reach, and the language the invitation is written in. They set their own
password from the link; nobody types a password for anyone else.
An invitation that goes unread can be sent again from the same page.
Taking access away
Disable rather than remove when someone is off for a season β their
history stays and the account comes back with one click. Remove when they
have gone for good.
The last owner cannot be removed or disabled. An organization without an
owner has no one who can pay the bill or let anyone back in.
Who can reach what
Group β Team lists everyone with the houses they can reach and when
they last signed in. That last column is the useful one: an account
nobody has used in six months is access you are still granting.