Introducing the Staff role: front-desk access without admin permissions

Venuo has a new role: Staff. It is built for whoever is on the desk — reception in an office, the counter at a sports club, or the front of house in a studio.

Until now, venue operators had two imperfect options. Make that person an Admin and they can also change venue settings and manage colleagues. Leave them a Member and they cannot book on someone’s behalf, clear the approval queue, or check a visitor in.

Staff is the middle ground: everything needed to run the day, without access to account administration.

Where it sits

What Staff can and cannot do

Staff can: book on behalf of someone else, see the whole venue’s schedule, approve or decline requests, cancel bookings, register visitors, check them in, and read the people directory.

Staff cannot: create or edit spaces, change locations, operating hours or closed dates, invite people, change roles, edit branding, or access billing.

Two limits are worth highlighting. Staff cannot book outside your operating hours because that would override a rule set by an Owner or Admin. Staff also does not see the payment breakdown on a booking.

These permissions are enforced on the server, not only by hiding controls in the interface. Hiding a button is a convenience. It is not a permission.

The same role in every kind of venue

A receptionist in an office and the person behind the desk at a sports club often perform the same operational job: someone is standing there, someone needs a space, and the booking needs to happen now.

Staff is therefore not tied to a particular venue type. Only the language displayed in the product changes with the category.

Setting it up

Assign the Staff role from the People page, either when inviting someone or by changing their role later.

The People page is divided into All · Team · Members, making it easier to distinguish the people who operate the venue from those who book its spaces.

The step-by-step lives in the documentation:

• Team & permissions overview — the permission tree, the role table, the invite flow
• Roles and groups — the full matrix, and how groups control which spaces someone can book