Restaurant Staff Shifts and Permissions

In short: give every person their own identity and only the access their work needs. Shared tills and kitchen screens can use controlled staff sessions without sharing a manager password. Review permissions when roles or branches change, and use two factor authentication for sensitive access.

DineHarbor's team and shifts tools support unlimited staff on public plans, branch roles, shared devices, screen lock, two factor authentication and audit records.

Start with jobs, not titles

List the actions people perform: take an order, prepare food, open a shift, issue a refund, count cash, edit the menu, view reports, manage staff and change billing.

Group actions into roles that match the restaurant. Owner, manager, waiter, cashier and kitchen can be useful names, but the capabilities behind them matter more.

Give the minimum needed for ordinary work. A waiter needs to serve tables but may not need billing access. A kitchen lead may manage station availability without seeing customer account details.

Avoid creating a special role for every person. Too many roles become impossible to review. Use a small baseline and documented exceptions.

Use individual staff identities

Every person should have a traceable identity, even when several people use the same till or waiter phone. This allows the restaurant to remove one person's access, apply correct permissions and understand the audit record.

Never write a shared manager password beside a device. A shared credential makes every sensitive action look the same and remains known after someone leaves.

DineHarbor supports shared operator devices with staff session controls. Staff can unlock according to the configured route rather than signing the whole device into a general account.

Keep invitation and recovery details current. Do not use an address controlled by a former agency or employee as the only owner login.

Configure branches and roles

A staff member may work at one or several branches. Grant only the locations required. A regional manager can receive wider scope; a temporary cover shift should not silently become permanent group access.

Roles such as owner, admin and member control broad branch access, while capabilities and policies protect actions. Test with an ordinary account rather than assuming a role name behaves as expected.

When a person changes job, review access from zero. Removing one capability from memory can leave other old permissions behind. Record who approved the new role and when it begins.

For several locations, read multi branch restaurant management before assigning group access.

Open and close shifts clearly

A POS shift creates an operating boundary for the till and cash. Assign the device and responsible person, record opening values according to policy and avoid carrying unresolved payments into close.

DineHarbor's POS includes shift opening and closing, cash movements and variance controls. Managers can set thresholds and approvals for relevant cash events.

At close, count honestly and let the system show variance. Do not edit a figure merely to make it balance. Investigate sales, refunds, payouts, petty cash and safe drops.

Keep shifts distinct from employee scheduling. A till shift records an operational session; a staff rota records planned work. Confirm what the current Team screen supports before promising scheduling functions beyond the verified team and shift facts.

Lock shared screens

A screen lock should be quick enough to use and strong enough to stop a guest or unauthorised colleague acting on an open session. Configure inactivity and session limits for the device's location and risk.

Staff should lock when stepping away. Position devices to reduce casual viewing of customer details. Kitchen screens may show less sensitive information than a manager tablet but still need controlled setup.

DineHarbor operator sessions have bounded lifetimes and device claims. Do not work around a lock by keeping a permanent general account signed in.

At handover, the outgoing person should finish or transfer active work through the supported flow. The next person unlocks with their own identity.

Use two factor authentication

Two factor authentication adds a second check beyond a password. DineHarbor supports it and can enforce it in branch security settings.

Use it for owners, administrators and sensitive access. Store recovery codes securely, separate from the ordinary password. Do not photograph them onto a shared staff phone.

Plan recovery before enforcement. Confirm at least two authorised owners can regain business access through approved routes. Remove old trusted sessions and devices when a phone is lost.

Two factor authentication does not repair poor permissions or a shared password. It belongs beside individual accounts, password hygiene and timely offboarding.

Read the audit log responsibly

An audit log can show who changed a record and when. It helps trace menu edits, access changes and other sensitive actions.

Use it to understand events and improve controls. Do not assume the person named acted maliciously. A confusing interface, shared unlocked device or manager instruction may explain the action.

Protect audit access and retain records according to legal and business needs. The log can contain personal information and should not become general staff gossip.

Review unusual refunds, permission changes and manual adjustments with the underlying order or process. Context turns an event into useful evidence.

Joiners, movers and leavers

For a new staff member, create the individual identity, assign the minimum branch and role, enrol required security and rehearse only their tasks. Give wider access after the job requires it.

For a move, remove old branch or role access as well as adding new access. Review active device sessions.

For a leaver, disable access promptly, revoke sessions and recover business equipment. Transfer ownership of duties, not the person's password. Review shared secrets they may have known outside the platform.

Keep a simple checklist with owner and completion time. Sensitive offboarding should not depend on somebody remembering every system during a busy shift.

Review access every month

Export or view current people, branches, roles and devices through supported screens. Ask each branch lead to confirm who still works there and what they do.

Remove stale accounts, old devices and temporary access. Check that owners use two factor authentication and recovery details belong to the business.

Compare plan device limits with the real estate. Unlimited staff does not mean unlimited registered operator devices on every plan. Starter and Growth have defined device allowances; Unlimited removes the stated limits.

Watch the team and devices guide, then have a new shift lead practise login, lock, handover and escalation.

Good permissions are quiet. Staff can complete ordinary work, sensitive actions require the right person, and access ends when the job does.

Test permissions before opening

Create or use approved test identities for each role in a safe environment. Ask a waiter to take an order and attempt a manager only action. Ask a kitchen user to handle tickets and confirm they cannot reach billing or staff administration.

Test the refusal message as well as success. It should tell the person what to do without exposing sensitive information. Confirm that a manager can complete the escalation through their own account.

Repeat after changing roles, adding a branch or enabling a new app. Permissions that were sensible for one till may not cover a driver phone or kiosk. Keep the expected access matrix with the monthly review so drift becomes visible.

Ready to configure roles on a test team? Start the 30 day free trial with no card needed.