Overview
When a seasonal team leaves, close out its work before disabling accounts. Disabling preserves memberships for a future return, so it does not perform the ownership handover for you.
At a glance |
|
Who can do this | Super Users, or the User administration permissions and group authority described below. |
Where | Assignments, Schedules, Checklists and Users |
Works on | Backend (web), Mobile app |
Availability | All organizations |
💡 Why this matters: A planned closeout leaves work with an active team and keeps the returning-User decision separate from permanent deletion.
Before you start
Agree the departure date and list the accounts in scope. Ask Users to finish uploads and hand over unfinished work while their accounts are still available. For shared devices, follow the device handover procedure.
Walkthrough
1. Transfer open Assignments
Review open Assignments assigned directly to departing Users and to seasonal groups. Reassign continuing work to the agreed active team, keeping its Location and history. Confirm the receiving team can open it; use bulk management when the selected tasks share the same change.
2. Check future inspection ownership
Review Schedule assignees, reviewers and owners. Replace personal references that would leave no active coverage. Check Notification Rules and Checklist Assignment Triggers too; moving existing tasks does not change where tomorrow’s tasks will go.
3. Disable the departing Users
In Users, select the agreed accounts and choose Disable. This action takes effect without a confirmation dialog. You need the applicable User administration authority; you cannot disable yourself or a Super User through this toolbar.
4. Verify the disabled records
Find the Users again using the search box. Disabled records remain listed with a pause icon and shaded row. Record who should review them before next season. Repeat the access review separately for any other Mobaro organizations they belong to.
Check the outcome
Disabling preserves Roles, User Groups and Location memberships. Deleting removes mappings and Certifications and cannot be undone by an administrator in the Backend. Use the disable-and-delete reference before considering permanent deletion. Super User departures require Mobaro Support.
Best practices
Disable seasonal accounts when a return is expected.
Check future routing as well as today’s task queue.
Assign one administrator to the return review.
Frequently asked questions
Can I schedule an automatic account end date?
No. Mobaro has no scheduled end date for Users. Arrange the administrative action for the agreed departure date.
Does disabling remove completed work?
No. The User record and completed history remain. Disabling also retains their memberships, which need review before a future return.
Does disabling cover every organization?
No. It applies to the active organization. Review each organization separately, and involve Support for Super User access.