Role path
Daily work
Permissions
Admin Help Path
Admins prepare the workspace, manage access, keep settings clean, and coordinate support so every team can work safely in AWRA.
Organization admins are usually the first line of help inside an organization. They confirm company settings, invite users, assign roles, manage branches and warehouses, review billing visibility, check reports, and gather useful context before escalating issues to AWRA Support.
What Admins Usually Do
- Maintain company profile, branches, warehouses, locations, departments, roles, and user accounts.
- Invite users, resend invitations, help with access checks, review MFA issues, and remove access when people leave.
- Confirm plan status, billing visibility, notification preferences, and integration readiness where enabled.
- Review reports, activity history, and workflow status when teams need to understand what changed.
- Coordinate support requests with record numbers, screenshots if allowed, affected users, and business context.
First Workflows To Learn
- Complete Company Settings and confirm document previews look correct.
- Create or review branches, warehouses, locations, departments, and base preferences.
- Invite a test user, assign a role, confirm the user can log in, and adjust access if needed.
- Review billing or plan status if your organization gives admins that responsibility.
- Open key reports and support pages so you know where to troubleshoot user issues.
- Run through the First-Day Checklist before wider rollout.
Admin Responsibility Map
| Area | Admin Responsibility | Help Page |
|---|---|---|
| Setup | Company settings, branches, warehouses, locations, and support contacts. | Organization Onboarding |
| Users | Invitations, account status, profile corrections, role assignment, and access review. | Roles Overview |
| Billing | Plan visibility, billing contact coordination, invoices, failed payment routing, and entitlement questions. | Billing guide |
| Reports | Help users confirm filters, dates, branch, warehouse, status, and export expectations. | Reports Overview |
| Support | Collect details, confirm whether issue is access/setup, and escalate with clear evidence. | Getting Support |
Common Admin Issues
| Issue | First Check | Read Next |
|---|---|---|
| User cannot see a menu | Role, branch, warehouse, module access, and record status. | Permissions Guide |
| Documents show wrong details | Company name, logo, address, tax, currency, and contact settings. | Company Settings |
| Notifications not received | Email, phone, user status, notification preferences, and workflow recipient rules. | Notification Problems |
| Support needs more information | Module, record number, user, expected result, actual result, time, and screenshot if allowed. | Getting Support |
Admin rule: Do not give broad admin access just to solve one missing button. Confirm the real task, assign the narrowest useful access, and review it again after the work is complete.
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.