Troubleshooting
First checks
Escalation
Troubleshooting: Missing Menus & Buttons
Use this guide when a menu, button, report, warehouse, customer, vendor, approval action, export, or record is not visible.
Missing menus and buttons are often caused by role settings, branch or warehouse assignment, module availability, record status, plan limits, or workflow stage. A missing action does not always mean AWRA is broken.
First Checks
- Confirm you are signed into the correct organization workspace.
- Check whether another user with the same role can see the same page.
- Confirm your branch, warehouse, department, vendor, or customer assignment.
- Check whether the record is draft, approved, posted, cancelled, closed, received, paid, synced, or waiting for another step.
- Search the left nav or dashboard in case the page lives under another module name.
- Ask your organization admin whether your role includes the task you need.
What Might Be Missing
| Missing Item | Likely Cause | Who Can Help |
|---|---|---|
| Whole module | Role, plan, or module access does not include it. | Organization admin. |
| Create/Edit/Delete button | Your role may allow viewing but not changing records. | Organization admin or manager. |
| Approve button | You are not the assigned approver or the record is not at approval stage. | Process owner or organization admin. |
| Warehouse or branch | Your user is not assigned to that location. | Organization admin or warehouse lead. |
| Report or export | Report contains restricted data or export permission is limited. | Finance lead or organization admin. |
How To Request Access
- Name the exact task, such as "approve PO", "export inventory valuation", or "receive transfer".
- Include the module, page, record number, branch, warehouse, and visible status.
- Explain whether the access is temporary or part of your ongoing job.
- Ask your manager or organization admin to confirm policy before broad access is granted.
- Sign out and back in after access changes if the page does not refresh.
Common Mistakes
- Borrowing another user's account instead of requesting access.
- Asking for admin access when one specific permission is enough.
- Ignoring record status when the button is hidden because the record is already closed or posted.
- Forgetting warehouse or branch assignment when the module itself is visible.
Best request format: "I need to [task] in [module] for [record/page] at [branch/warehouse]. I cannot see [menu/button/report]."
Support escalation
Open support guide
Need help with this topic?
Capture the module, record number, branch or warehouse, user, visible message, and what you expected to happen before contacting support.