When an employee leaves, make a list of every system they can reach, assign someone to remove each access point, and verify the changes. Start with individual logins and active sessions, then address shared passwords, devices, and vendor accounts. Record anything you cannot finish immediately, along with its owner and deadline.
Restaurant software staff offboarding is different from deciding what a current employee may see in a report. The goal here is to end access at the agreed time without locking out the people who still need to run service.
Inventory accounts before the last shift
Start with the employee’s role, but do not assume the job title tells you everything. A shift manager may use a POS, an ordering dashboard, a scheduling tool, and a personal phone to receive business messages. A temporary assignment or an old promotion may have left additional access in place.
Ask the departing employee and their supervisor which tools and devices they use. Then compare their answers with your account lists, device records, and vendor contacts. Include access that is occasional, such as a portal used only to update a menu or contact support.
- Individual accounts: POS, restaurant management dashboard, online ordering, reservations, scheduling, payroll, email, and any separate reporting tools.
- Connected services: payment provider portals, delivery services, website administration, marketing accounts, and other integrations.
- Devices and entry methods: tablets, terminals, laptops, personal devices, PINs, saved browser sessions, and authentication apps or security keys.
- Shared access: shared mailboxes, team passwords, device passcodes, Wi-Fi credentials, and recovery contacts.
- Vendor relationships: support portals and accounts where the employee is listed as an administrator, billing contact, or authorized requester.
Use the table below as a combined checklist and verification log. Its entries describe a hypothetical shift manager, not a claim about any particular system. The named owner is responsible for closing and checking the item; a vendor may still have to carry out part of the work.
| Access point | Action and owner | Verification record |
|---|---|---|
| Individual POS login | General manager disables the account at departure time. | Record account status, time, and verifier; check authorized access controls. |
| Ordering dashboard | Owner removes the individual user and ends sessions if supported. | Record status and session action; note any vendor request still open. |
| Shared tablet passcode | General manager changes it and gives the replacement to remaining authorized staff. | Record change time and owner, not the new passcode. |
| Payment provider portal | Account administrator removes the user or asks the provider to do so. | Record confirmation or ticket reference and follow-up deadline. |
Check whether the employee has more than one identity in the same product. An individual account, an old email address, and a shared manager login may be separate routes. For each one, record who can change it and whether the restaurant or the vendor controls the final step.
Revoke access in a deliberate order
Set an effective time with the person responsible for the departure. Arrange coverage first: another authorized manager may need access to refunds, menus, reservations, or support. Confirm that the replacement has their own account rather than passing along the departing employee’s login.
- Secure the account administration path. Identify who can remove users and who holds recovery methods. If the departing employee is the only administrator, arrange a supported transfer before disabling that account.
- Disable individual access at the agreed time. Remove or deactivate the person’s accounts across the inventory. Follow each system’s process rather than assuming a change in one tool applies everywhere.
- End active access where possible. Ask whether disabling an account also ends existing sessions, invalidates device access, and removes linked authentication methods. Take any separate steps the provider requires.
- Remove vendor authority. Update authorized contacts and recovery details with providers, including any contact who could request an account reset or support change.
- Review connections and devices. Remove the employee’s personal device authorization where supported, collect restaurant-owned equipment, and address shared credentials.
Keep the timing coordinated. If a departure requires immediate removal, prioritize accounts that can administer other users, move money, change orders, or expose sensitive information. If a vendor must intervene, contact it promptly and record the interim steps available to you. Do not mark a provider-controlled account as removed merely because a request was sent.
When evaluating a restaurant POS system, ask who can disable a user, whether sessions end automatically, and how quickly a vendor-controlled change can be completed. Also ask how account records are retained after deactivation, so the restaurant can maintain the records it needs without keeping the former employee’s login active.
Inspect shared credentials and recovery paths
Disabling a named account does not change a password the employee shared with a team. For each shared credential, decide whether it is still needed. If it is, assign an owner to rotate it and distribute the replacement only to staff who need it. If it is not needed, retire it using the provider’s process.
Work through shared tablet and terminal passcodes, team email, website administration, and any vendor portal used by more than one person. Consider saved passwords on browsers and devices, too. A shared login can remain usable even after the person’s company email is disabled.
Recovery is part of the same job. Check whether the former employee’s phone number, email address, authentication device, or security key can still be used to regain access. Replace those recovery methods with ones controlled by current authorized staff. Keep a backup administrator where the system permits it, so one absence does not block the next change.
Record the credential’s purpose, owner, change date, and where authorized staff can find the current instructions. Do not put passwords, passcodes, recovery codes, or security answers in the offboarding log. Use your organization’s approved secure method for distributing and storing them.
Before changing a shared credential, tell the relevant shift lead when the change will happen and how remaining staff will receive access. That helps avoid an accidental service interruption while still setting a firm completion time.
Verify removal and close the log
A completed checklist needs evidence, not just a tick beside each account. Have an authorized administrator inspect the account status and confirm that the intended user, sessions, devices, and recovery methods were handled. Record the system, action, time, verifier, result, and any reference number. Keep the log in a restricted location.
If the system supports an authorized test, plan it with the account administrator or vendor. Use a designated test account or another approved method to check the relevant control; do not use the former employee’s password or impersonate them. A simulation must not create a real payment, guest message, or courier dispatch. Confirm with the provider how to test safely before starting.
A test account can show how a control behaves, but it does not by itself prove that the former employee’s specific account was disabled. Pair the simulated check with an inspection of that account’s status and any available session or access records. If the platform cannot provide a safe test, record the administrative evidence available and ask the vendor what confirmation it can provide.
For the hypothetical manager above, the POS item can be closed after the general manager records the disabled account and the verification performed. The payment portal stays open if the provider has only acknowledged the request. The owner should log the ticket, name a follow-up person, and set a deadline for obtaining confirmation. Escalate missed deadlines rather than treating silence as completion.
After all items are closed, review the log with the person accountable for restaurant access. Note recurring gaps, such as a vendor account with no backup administrator, and assign a fix. If questions arise about preserving employment or business records, consult an appropriately qualified adviser.
Next step: Make a list for your next departure, assign an owner to every access point, and compare the workflow with your requirements when evaluating restaurant management software.
Frequently asked questions
Is disabling the POS account enough?
Usually not. Check other individual accounts, connected services, shared credentials, devices, and recovery methods. Each can provide a separate route to restaurant systems.
Should we delete a former employee’s account?
Ask the provider about disabling and deletion options, including their effect on records. Remove access at the agreed time without assuming deletion is required or appropriate.
What if only the vendor can remove access?
Submit the request promptly, record its reference and follow-up deadline, and ask about interim safeguards. Keep the item open until an authorized person receives and records confirmation.
