Overview
Use this guide for a blank Backend page, missing icons, overlapping content or a control that does not respond. First establish whether the problem is visual, an access restriction, or a request that failed.
At a glance |
|
Who can do this | The affected User; an administrator for access checks |
Where | The affected page at app.mobaro.com |
Works on | Backend (web) |
Availability | All organizations |
Narrow down the problem
1. Keep the current evidence
Record the page address, organization, exact time and time zone, browser version, screenshot and error. Save any work normally if possible before leaving a page. Do not repeatedly submit a form when you cannot tell whether the first attempt saved.
2. Distinguish access from display
Symptom | Check | Next step |
A menu is absent | Organization, feature availability and permissions. | |
A visible control is disabled | Selection, required fields and permissions. | Record any displayed explanation. |
The page or icons render incorrectly | Whether other pages, users or devices show the same problem. | Send a full screenshot and browser details. |
A request fails | Exact message, time and affected action. | Ask Support to investigate; do not assume every failure is an access issue. |
3. Compare supported surfaces
The Backend and the Mobile app serve different workflows. Identify whether you are using a desktop browser or a mobile browser, then check compatibility. With unsaved work protected, an authorized comparison in another supported browser can help determine whether the fault is browser-specific. Do not disable organization security controls.
4. Check the organization
If data or settings appear missing, confirm the active organization. Access and records differ between organizations. Follow working in more than one organization.
[Insert image: Backend-display/01-membership-fields-annotated.png – Roles, User Groups and Location memberships are separate checks for an administrator; no values are changed in this illustration.]
Send an actionable report
Tell Mobaro Support which page fails, what still works, and whether the issue follows one browser, User or record. Include screenshots without credentials or unrelated personal details. If Support requests console or network evidence, use their approved collection method and remove secrets before sharing it.
Best practices
Preserve the first error and avoid duplicate form submissions.
Check the active organization before changing Roles.
Escalate unfamiliar labels instead of assuming they are a local translation.
Frequently asked questions
A page is blank. Should I clear all browser data?
Do not start by clearing all browser data. Capture the page, error and browser version, protect unsaved work, and compare the affected scope. Clearing RideOps site data can delete locally queued work; treat that surface separately.
My colleague can see a menu that I cannot. Is the page broken?
Not necessarily. Compare the active organization, feature availability and access. Follow missing-feature checks before treating the difference as a rendering defect.
Can I test by submitting the form again?
Only after establishing the first attempt did not save. Check the intended record or ask an authorized administrator. Repeating a request with an unknown outcome can create duplicate work.