Overview
When several people use the same phone or tablet, hand over the Mobaro session as well as the device. Each person should work under their own User account.
This guide is for the Mobaro mobile app. For an Operator change on a RideOps tablet, use RideOps staff handovers.
At a glance |
|
Who can do this | Each User manages their own session; administrators arrange accounts and work access. |
Where | Mobile app › home screen and Profile |
Works on | Mobile app |
Availability | All organizations |
💡 Why this matters: Checking uploads and unfinished work before switching accounts keeps the record attributed to the right person and avoids leaving completed work on the device.
Finish the outgoing work
1. Reconnect and check uploads
Connect the device to a working network, open Mobaro and wait for the upload count on the home-screen connection tile to clear. In the layout shown below, the tile then displays Connection available. Photos upload before Results, so a photo-heavy Checklist can take longer. Check important Results in the Backend when needed.
2. Decide what happens to unfinished work
Finish the Checklist before its deadline where possible. Save to this Device leaves progress locally; it is not a completed Result or a handover to another User.
For an eligible Checklist, use the supported cloud save-and-resume workflow if another person must continue. Confirm the incoming User can resume it before leaving. Certification Process Checklists can only be saved on their current device. See saving and resuming across Users.
🛑 Critical: Do not uninstall Mobaro, clear its data or reset the device while work is queued. That can delete the only copy. If uploads are stuck, keep the device and account available and follow recovering unsent data.
Switch the account
3. Review automatic sign-in
Open Profile and check the displayed User and organization. Turn off Automatic Login on a device that changes hands. See Profile settings.
4. Log out deliberately
Select Logout only after checking the upload queue yourself. The Profile logout path does not show the pending-upload warning, so the absence of a warning is not confirmation that everything uploaded.
5. Sign in as the next User
The incoming person signs in using their own password or company sign-in. Check the name and organization in Profile, refresh the app, and confirm their assigned work is available. A shared device does not transfer the previous User’s permissions.
Check the device is ready
The displayed name is the incoming User’s.
The correct organization and Location filters are selected.
The next Checklist and required reference files open.
Any agreed cloud handover is available to the incoming User.
No saved-password or company sign-in prompt exposes the outgoing person’s credentials.
If the device’s password manager or company sign-in keeps offering another person’s credentials, ask your device administrator to correct the shared-device setup. Mobaro’s Automatic Login switch does not control every operating-system credential store.
Best practices
Make the upload check part of the shift handover.
Use named accounts instead of a shared team password.
Reconnect and refresh before the incoming User leaves Wi-Fi coverage.
Frequently asked questions
Why are credentials still offered after logging out?
The device’s password manager or company sign-in can remember credentials separately from Mobaro. Turn off Automatic Login and have your device administrator review autofill and shared-device sign-in. Do not assume Logout clears those stores.
I completed work offline but cannot find the Result. Can I hand over?
First reconnect as the User who completed it and wait for uploads. If it was only saved locally, it is unfinished progress. Resolve that before the handover; see unsent-data recovery.
Where do I log out?
Open Profile › Logout. Check that the upload queue is empty first: this logout path does not display the pending-upload warning.