AWRA Help Center

Copy link

Tenant Onboarding Guide

Use this guide to prepare a new AWRA workspace before teams begin daily operations.

A tenant is your organization workspace in AWRA. Tenant onboarding is the process of confirming your company identity, users, roles, warehouses, stock structure, billing visibility, notifications, and support contacts. A clean onboarding setup reduces duplicate records, missing approvals, stock confusion, and reporting gaps later.

Who Should Lead Onboarding

  • Tenant admin: Owns users, roles, company settings, billing visibility, and general workspace readiness.
  • Inventory lead: Confirms warehouses, locations, item categories, opening stock rules, and scanner expectations.
  • Procurement lead: Confirms vendors, approval flow, purchase request rules, and RFQ expectations.
  • Finance lead: Confirms taxes, payment expectations, accounting reports, and integration readiness.
  • Team leads: Confirm who needs access, what they need to do, and which workflows need approval.

Recommended Onboarding Sequence

  1. Confirm organization details: Company name, logo, tax details, address, currency, time zone, and support contact.
  2. Define operating structure: Branches, warehouses, locations, bins, departments, cost centers, and stock responsibility.
  3. Invite core admins first: Start with a small admin group that can review settings before wider rollout.
  4. Create role groups: Admin, manager, inventory user, procurement user, sales/POS user, finance user, approver, and vendor-facing roles as needed.
  5. Prepare master data: Items, categories, vendors, customers, tax settings, opening balances, and required documents.
  6. Run pilot transactions: Test one item setup, one stock movement, one request, one approval, one report, and one support path.
  7. Train users by role: Give each user only the workflows they need for their day-to-day work.
Read next: First Login, Company Settings, Branches & Warehouses, Roles Overview, and First-Day Checklist.

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.

Open support guide