Organization Onboarding Guide
Use this guide to prepare a new AWRA workspace before teams begin daily operations.
An organization is your organization's AWRA workspace. It contains your company profile, users, roles, branches, warehouses, items, vendors, customers, billing visibility, notifications, and support contacts. Good onboarding makes daily work easier because users know where records live, what they are allowed to do, and who can help when something is missing.
Onboarding should be led by the people who understand how your organization actually works. AWRA can support many workflows, but the first setup should match the real branches, warehouses, approvals, stock movement rules, and reporting needs your team uses every day.
Who Should Be Involved
| Role | What They Confirm | Why It Matters |
|---|---|---|
| Organization admin | Users, roles, company settings, support contacts, plan visibility, and launch readiness. | Admins control the foundation users depend on. |
| Inventory lead | Warehouses, locations, item categories, units, opening stock approach, scanner expectations, and count rules. | Bad stock setup creates confusing movements and reports. |
| Procurement lead | Request types, approvers, RFQ process, vendor records, purchase order expectations, and receiving handoff. | Procurement needs clear approval and supplier flow. |
| Finance lead | Taxes, invoice expectations, payment process, reports, reconciliation needs, and integration readiness. | Financial review depends on clean source records. |
| Team leads | Who needs access, which tasks each role performs, and which exceptions need escalation. | Users should have access to their real work, not everything. |
Recommended Onboarding Sequence
- Confirm organization identity: Company name, logo, tax details, address, support email, phone, currency, and time zone.
- Define operating structure: Branches, warehouses, locations, bins, departments, cost centers, and stock responsibility.
- Invite core admins first: Start with a small group that can review settings before wider rollout.
- Create role groups: Admin, manager, inventory user, procurement user, sales/POS user, finance user, approver, warehouse team, and vendor-facing users where needed.
- Prepare master data: Items, categories, units, vendors, customers, tax settings, opening balances, and required document references.
- Run pilot transactions: Test one item setup, one stock movement, one request, one approval, one report, and one support path.
- Train users by role: Show each group the tasks they perform, the records they should not change, and the person to contact for help.
- Go live carefully: Start with a small team or one branch, correct setup issues, then expand to the rest of the organization.
Before You Invite Everyone
- At least one admin can log in and access settings.
- Company profile, branch names, warehouse names, and contact details are clear.
- Users have role assignments that match their jobs.
- At least one item, vendor, customer, workflow, report, and support path has been tested if relevant to your rollout.
- Team leads know how to request access changes and how to report issues.
Common Onboarding Mistakes
- Inviting everyone before roles, warehouses, and first workflows have been tested.
- Creating duplicate warehouses, vendors, customers, or item categories because naming rules were not agreed.
- Giving broad admin access to users who only need daily operational tasks.
- Starting live stock movements before opening quantities and locations are agreed.
- Skipping support contacts, which leaves users unsure where to ask for help.
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.