office, meeting room, business, design, interior, architecture, building, interior design, meeting room, meeting room, meeting room, meeting room, meeting room
Photo by lixiao496168 on Pixabay

Access

Part of Coworking booking systems

Reviewing access controls in a workspace booking tool

“Can see” and “can book” are different permissions. A member may need to see that an event room exists without being allowed to reserve it, while a manager may need …

This is an editorial pen name used by the publication, not a claim of an independently verified personal identity. Original editorial credit: Desk Workspace.

“Can see” and “can book” are different permissions. A member may need to see that an event room exists without being allowed to reserve it, while a manager may need to book it on someone else’s behalf. Map those roles before opening a booking portal.

Build a small access matrix for members, day-pass visitors, reception staff and administrators. For each role, test whether they can view availability, see booking details, create a reservation, override a rule, change someone else’s booking and export member information. Use a test account for each role; an admin view will hide many problems.

Test the unhappy paths as well as the successful ones. Try to book a space the role should not reach, open another member's reservation and export a list the role should not see. A control that blocks the action but reveals the data in an error message or notification has not done its job.

Skedda documents conditions that restrict booking by user tag, space and time, while system users can bypass those conditions. Cobot’s external-booking feature is an add-on for non-members. OfficeRnD Flex documents approval policies and admin-created bookings outside member rules. Treat these as specific controls to investigate, not as proof that every role is configured safely by default.

Check the information displayed alongside a reservation. Members usually need to know that a room is occupied, not the meeting topic or another member’s contact details. Separate public availability from private booking information.

Review former members’ access and staff permissions after role changes, and make someone responsible for granting exceptions.

Record the date of each access review and the person who carried it out. Roles drift as staff change jobs, visitors become members and temporary exceptions stay in place long after they were needed. A dated record shows which permissions were checked, which were changed and which are due for another look.

The practical acceptance test is this: each role can complete its legitimate booking task, and cannot use the same interface to change or inspect a reservation outside its remit.

Key Access Control Metrics

Booking Conditions Configured
User tag, space, time
External Booking Support
Cobot add-on
Admin Approval Policies Available
Yes (OfficeRnD Flex)
Data Export Permissions Restricted
No for non-admins
Private Info Hidden from Members
Yes (e.g. contact details, topics)

Further reading: Set up booking policies (help-flex.officernd.com).

More from Access