Permissions

Decide what each person on your team may reach. The box office sees bookings and not the payment gateways; the person who runs the class sees their own events and nobody else's.

A role, and the people in it

A role has a name and a list of what it opens: Events, Bookings, Payments, Customers, Settings and the rest, each with the finer actions underneath. Tick what that group needs. Anything left unticked is refused — not hidden behind a message, but refused by the server, so the address bar is no way round it either.

Every module starts with View. A clerk who should read bookings but not change them gets View and nothing else. Granting Add, Edit or Delete grants View with it, and the box on a module's header selects everything in it at once.

Put staff into the role and they carry it. Somebody can hold more than one, and the answers merge to the most restrictive: adding a role can only ever take away, never add, so a limit you wrote cannot be undone by giving that person a second one.

Pause a role rather than deleting it and the people in it are no longer limited by it.

Only their own

Two sections narrow further than on and off. Bookings can be limited to the ones that person took, and Events to the ones they are assigned to as staff.

That holds in the list and when a row is opened directly, so a booking a clerk cannot see in the list does not open for them through a link from an email either.

Settings, panel by panel

Settings is not one switch. Its panels are granted separately, so letting somebody fix a typo in the company address does not also hand them the payment gateways and the SMTP password.

The interface follows the role

The menu, the sidebar and the buttons on a row are drawn from the same answers the server enforces with. Somebody who may not open Payments is not shown Payments — rather than being shown it and refused on arrival.

Signing in

Staff need a WordPress account to sign in with, and one can be made from the staff screen in a couple of fields. If the email already belongs to a user, it says so and offers to link that person instead of creating a second account for them.

Administrators are never limited, on any plan.

Without Permissions

The free plugin is not unguarded. A staff member with an account reaches Dashboard, Calendar, Bookings, Customers, Payments and Staff, and may correct a colleague's details but not add or remove anybody. That set is fixed. Permissions is how you write it yourself.