An instructor preparing a lesson needs different information from the person reviewing invoices. Define the work first, then configure access and test the view each role actually receives.
Front desk and daily planning
The front desk needs to find bookings, participants and relevant payment or document questions. The person planning the day needs groups, instructors, equipment and current changes. Agree which role can edit the plan and which should only use the result.
A clear handover matters when different people handle arrival and delivery. A chat notification should point back to the maintained record rather than become an alternative plan.
Instructors and rental staff
Instructors need the relevant participant context, meeting information and reporting tasks. Rental staff need the booked item, handover and return workflow and condition evidence. Test these tasks on the devices used at the station.
Do not grant broader finance or customer-history access merely to solve a navigation problem. If the needed task is not accessible, review the role configuration with an administrator.
Owners and external providers
Owners can review the business records their permissions allow. Provider access should be limited to the agreed service and data. Multi-location history also remains permission-aware; a shared customer relationship does not open every location to every user.
Guest access is a separate surface from staff administration. Mobile team search and its scanner are not a promise that customers receive the same search tools or a universal passwordless booking journey.
Recheck when responsibilities change
Review access when people join, change duties or leave. Test a representative task for each role rather than judging only the administrator's screen.
See operations for team work and providers for external collaboration.
How does this work at your school?
Bring an everyday task from your school. We’ll show you how it could work in TIDEFORCE.
Request a demo →