Written by DROPS.ST.
An employee leaves. Orders still need packing, customers still need answers, and tomorrow’s menu still needs an owner. A good offboarding process removes the worker’s access while keeping the shop running.
DROPS brings your products, Customer Accounts and orders into one connected shop workflow. Your replacement manager can work from that shared business context instead of reconstructing a shift from scattered messages and spreadsheets. Separate order permissions and administrator-only shop settings give you concrete access decisions to review during the handover.
The practical job is to identify every account, name its business owner, remove the departing worker’s access, and prove both sides of the change: the worker cannot continue operating, and the remaining team can.
Set the cutoff and name the person responsible
Assign one person to coordinate the departure and one accountable owner for each system. Record the approved access cutoff, the work that needs handing over, and any unresolved account ownership.
Use your shop’s departure process to decide timing. Complete a planned handover beforehand when practical, but do not let an unfinished spreadsheet silently postpone the approved cutoff.
NIST’s account-management and personnel-termination guidance connects departures with account controls, credential revocation, changes to shared credentials, and continued organizational access to business information. The checklist below applies those principles to everyday shop operations. NIST SP 800-53, AC-2 and PS-4.
Build an account and channel-owner matrix
Make one row for each actual account or service. “Telegram” or “email” alone is too broad: a worker might have channel privileges, mailbox access and a separate recovery address.
| Surface and owner | What to inventory | What to prove afterward |
|---|---|---|
| DROPS staff access — shop administrator | Staff identity and granted permissions | Former access is blocked; replacement access works |
| Order handling — operations manager | Assigned work and permitted order actions | Open orders have a responsible person |
| Telegram channels and bot administration — channel owner | Administrator membership, ownership and connected services | Business retains control; departed worker has no administrative access |
| Email and shared files — workspace administrator | Mailboxes, groups, folders and recovery ownership | Team can reach required correspondence and documents |
| Payment-provider administration — authorized finance owner | Individual access and business recovery contacts | Authorized people retain access; removed access fails |
| Domain and external work tools — business account owner | Registrar, support tools, password manager and billing ownership | Business can administer each service independently |
| Integrations and shared credentials — technical owner | Credentials the worker knew or could retrieve | Necessary replacements work and old access is retired |
Keep passwords and tokens out of this matrix. Record account references, responsible people, completed actions and verification results.
Review what the worker could actually do
Start with permissions, not the employee’s job title. “Menu manager” does not tell you everything their account can reach.
In DROPS, product viewing, creation, editing and deletion use broader shop permissions. Those permissions can also affect Customer Accounts, and broad shop editing includes wallet-adjustment access. Include those powers in the departure review even if the worker’s daily task was updating product descriptions.
Order permissions distinguish actions such as viewing orders, changing status, handling assigned orders, assigning staff, marking paid, cancelling and refunding. Review each granted action. Shop settings require administrator access, so establish whether the departing person also held an administrator account.
The store manager permissions checklist helps you review those boundaries before giving the replacement access.
Run the cutoff as a coordinated handover
Use this sequence as a working checklist:
- Preserve business continuity. Identify unfinished orders, customer follow-ups, menu changes and documents that need a new owner.
- Remove individual access through each service’s supported controls. Include shop administration and external tools from the matrix.
- Review shared access. Replace shared credentials the worker knew, coordinating dependent integrations so the shop keeps functioning.
- Check recovery ownership. Remove departed-worker recovery routes and confirm the business controls the remaining recovery options.
- Verify and record the result. Note what passed, what failed, and who owns the next corrective action.
If the worker knew a shared storefront password, review that separately. A password-protected storefront controls access to a customer-facing menu; it does not replace individual staff access controls.
Do not treat a password change as proof that every existing session or external integration has stopped working.
Check the boundary before and after
Use authorized test accounts and disposable records for action checks. Avoid testing a refund or wallet change against a real customer simply to prove a permission boundary.
| Check | Before the change | After the change |
|---|---|---|
| Fresh sign-in | Confirm which identity reaches the system | Removed identity cannot sign in |
| Existing session | Identify a controlled session for verification | Check whether it can still retrieve protected information or perform actions |
| Remaining manager | Confirm required menu and order access | Required work still succeeds |
| Business ownership | Identify who controls recovery and administration | Business owner retains those controls |
An open screen can show previously loaded information. Verify the next protected request rather than judging access from what remains visible.
Hypothetical example: a departing shift manager
Maya manages menu updates and helps with orders. She also moderates the shop’s Telegram channel and can read a shared support mailbox.
Her departure therefore creates three separate access tasks: shop permissions, Telegram privileges and mailbox membership. Removing her shop access alone leaves two unfinished rows.
The owner reviews Maya’s broader shop-editing powers, assigns open work to the next manager, and asks each channel owner to complete their row. Verification checks removed access and confirms the replacement can handle the next shift. Any session behavior that remains uncertain stays an open task.
Keep the handover inside an organized shop
DROPS gives the next manager connected product, customer and order context, with separate order-action controls and administrator-only shop settings. That makes a staff change easier to manage: the business workflow stays with the shop, while access decisions follow the people doing the work.
See how that operating workflow fits your team at DROPS.ST and explore the shop demos. Bring your access matrix and review the exact responsibilities your next manager needs.