Overview
Deactivating a Super User revokes their unrestricted access to your Mobaro account. Like activation, deactivation is handled directly by Mobaro Support to maintain an auditable trail and confirm the request comes from an authorized party. This article walks through when to deactivate, who can request it, and how to send the request.
Why this matters: Super Users have account-wide access. Removing that access promptly when it is no longer needed is a key part of your security posture — both for compliance and to limit your account's exposure during personnel changes.
Step 1: Decide when to deactivate
Deactivate a Super User any time their unrestricted access is no longer required. Common triggers include:
Personnel changes — the User is leaving the organization or changing roles.
Scope reduction — the User no longer needs unrestricted access; a scoped Role can replace it.
Compliance reviews — quarterly or annual access audits identify Super User entitlements that should be reduced.
Account consolidation — Super User counts need to be reduced to a small, well-known set after a transition or reorganization.
Best practice: Build Super User access reviews into your recurring compliance cadence (quarterly is a common interval). Catching stale access proactively is easier than handling it during an incident.
Step 2: Confirm you are authorized to request
To request deactivation of a Super User, the requester must be one of the following:
An existing Super User on the account.
An account owner or known organizational decision-maker on file with Mobaro.
A direct manager of the Super User being deactivated, with verification routed through the account's Customer Success Manager.
Important: A Super User cannot deactivate themselves through the Mobaro Backend, and another Super User cannot deactivate them either. All Super User deactivations go through Mobaro Support so that the change is logged and verified.
Step 3: Send the deactivation request
Use the button below to open a pre-filled email to [email protected]. Fill in the placeholders and send it from the email address Mobaro has on file for you.
Information to include
Name of requesting User — your name as the requester.
Name of Organization — the Mobaro Organization where the Super User access should be removed.
Name of Super User to deactivate — full name of the User losing access.
Email of Super User to deactivate — the email address associated with the Mobaro User account.
Effective date — when the deactivation should take effect (immediate, end of day, or a specific future date).
Action after deactivation — choose one: Remove Super User access only, Replace with a scoped Role (specify the Role), or Disable the User entirely.
Heads up: For time-sensitive deactivations (for example, an immediate termination), call Mobaro Support directly in addition to sending the email. Standard email turnaround is one to three business days, which may be too long for urgent security situations.
Step 4: After deactivation
What changes immediately
The User loses unrestricted access. Depending on the option you selected in Step 3, they will either:
Retain a regular User account with no permissions until a Role is assigned, or
Have a scoped Role applied as a replacement, or
Be fully disabled and unable to log in.
Active sessions are terminated; the User will be logged out on their next request to the Mobaro Backend.
What persists
All historical data tied to the User remains in the system — completed Checklists, Assignments, audit log entries, and reporting all retain their original attribution.
If the User is fully disabled rather than just demoted, mappings persist (User Group memberships, Location memberships, etc.) so they can be re-enabled later if needed.
Note: If the User belongs to multiple Mobaro Organizations, deactivation must be requested for each Organization separately. Mention every Organization in your request to have all deactivations processed together.
Best practices for Super User offboarding
Plan ahead — initiate the deactivation request a few business days before a known departure to avoid last-minute coordination.
Document the replacement — if the departing Super User owned specific configurations (Notification Rules, Dashboards, RideOps Keys), assign ownership to a successor before deactivation.
Use Roles for partial offboarding — when a User changes roles internally but stays at the company, replace Super User access with a Role rather than disabling the account entirely.
Confirm completion — Mobaro Support will reply when the change is applied. Save that confirmation for your audit records.
See also
Activating a new Super User — the companion process for granting Super User access.
How to deactivate a User — for deactivating regular Users (non-Super Users) directly from the Mobaro Backend.
How to set up Roles — for replacing Super User access with a scoped Role.
Frequently asked questions
Q: Why can't I deactivate a Super User from the Mobaro Backend?
A: Super User changes are intentionally gated through Mobaro Support to maintain an audit trail, prevent accidental lockout, and confirm the change is authorized.
Q: Can a Super User remove themselves?
A: No. Self-deactivation is not supported through the Mobaro Backend. Submit a deactivation request like any other User.
Q: How quickly will deactivation take effect?
A: Standard email requests are processed within one to three Mobaro support business days. For immediate deactivations, contact your Customer Success Manager directly to expedite.
Q: Will historical reporting still show this User?
A: Yes. Historical data is preserved with original attribution. The User will simply no longer be available as an active filter or assignee for future records.
Q: What if the User belongs to multiple Mobaro Organizations?
A: Deactivation must be requested for each Organization individually. Include all relevant Organization names in your request so Mobaro Support can process them together.
Q: Can a deactivated Super User be reactivated later?
A: Yes. The same activation request flow applies — see Activating a new Super User.