User permission management

A hostess doesn't need to see last quarter's revenue. A floor manager shouldn't be editing venue settings mid-service. And an admin changing a table layout shouldn't have to do it through someone else's account.

Reservation.Tools has role-based permissions built into every screen. Hostess, Manager, and Admin roles each see a different slice of the system — the hostess gets today's bookings and the floor plan, the manager adds reports and history, the admin gets configuration, users, and venue setup. You decide who is what.

This does two things. First, it limits the blast radius when someone makes a mistake — a new hostess can't accidentally delete a table or change opening hours. Second, it makes the activity log meaningful: when every action is tied to a named user with a known role, you can settle disputes, spot training gaps, and trust what the audit trail tells you.

For multi-venue operators, roles scope to specific venues too — a manager for Venue A doesn't see Venue B's data unless you grant it.