Team, roles & permissions

Users is where you add your team and control what each person can see and do. Open Users from the operator-wide main menu. It has two subtabs: Users and Roles.

Adding a user

1. Open Users → Users and choose + Add User.

2. Enter the name and email (both required), and optionally a phone and a password.

3. Choose the role that sets their access.

4. Save. There’s no separate invite or pending step — the user exists as soon as you save.

The Users list shows Name, Email, Phone and Role, with search and a role filter. Each user has exactly one role.

How permissions work

SideDoor’s permission model is deliberately simple:

• Flat and global. A role grants access across all your venues, unless you restrict it with a venue whitelist (below).
• Write implies read. Granting write access to something automatically includes read access — you never need to tick both.
• Venue whitelist. A role can be limited to specific venues. Leave the whitelist empty to grant access to all venues.

Permissions are organised as a grid of areas — Dashboard, Guests, Bookings, Reservations, Events, Resources, Users and Roles, Operator Settings, and the per-venue sub-areas — each with Read and Write columns.

The Owner role

There’s one built-in system role: Owner. It has every permission, can’t be deleted, and only its name and description are editable. Use it for the people who run the whole operation.

Caution

There are no pre-seeded “manager” or “door staff” roles. Aside from Owner, every role is one you create yourself — so you have full control over exactly what each job can do. See the examples below.

Creating a custom role

Open Users → Roles and choose + Add Role. The Roles list shows each role’s Name, Description and Users count.

1. Give the role a name (required) and a description.

2. In the Permissions grid, tick Read or Write for each area. Remember write includes read.

3. Under Venue access, leave it empty to grant all venues, or pick the specific venues this role can work in.

4. Save the role, then assign it to users.

Role examples to build

Because roles are yours to design, here are a couple of common shapes:

• Floor manager — read/write on Reservations, Bookings and Guests; read on the Dashboard; limited to their venue via the whitelist.
• Door staff — read on Bookings and Guests so they can check people in; no access to Settings or Users.

Note

System roles like Owner can’t be deleted, and only their name and description can be changed — their permissions are fixed.