Admin Setup & First-Run Configuration

Stand up a new AWRA workspace the right way — company profile, locations, users, and the settings everything else depends on.

4 lessons 35 min 5-question assessment 70% to pass

What you’ll learn

Configure a new workspace’s company profile and preferences

Set up locations, warehouses, and bins

Create users and assign roles

Sequence first-run setup so later steps are not blocked

Lesson 1 of 4 Reading 8 min

First-run essentials

A new AWRA workspace begins with a handful of foundational settings: your company profile, currency, tax details, and timezone. These are the assumptions every later transaction inherits, so setting them correctly up front saves re-work across the whole system.

Think of first-run configuration as laying a foundation before building. A wrong currency or timezone discovered after months of data is far more painful than two minutes of care at the start.

Some of these are effectively one-way doors, so treat them with extra care: the base currency and the tax configuration shape how thousands of past transactions are stored, and changing them after go-live can mean re-stating history rather than flipping a switch. Before processing a single live sale, double-check currency, the tax rate and whether prices are tax-inclusive, and the timezone — these are the settings you least want to discover were wrong in month three.

Key takeaways

A new workspace starts with company profile, currency, tax, timezone.
These settings are inherited by every later transaction.
Correct foundations up front prevent costly re-work later.
Treat base currency and tax setup as one-way doors — verify them before the first live sale, as changing them later re-states history.

Lesson 2 of 4 Reading 9 min

Locations, warehouses, and structure

Before stock and sales can flow, AWRA needs to know where your business operates — your warehouses, locations, and optionally bins. Configuring this structure early means items have somewhere to live and movements have somewhere to go.

This mirrors your physical reality. A workspace whose locations match the real shelves and branches is one where on-hand numbers mean something from day one.

Resist modelling every shelf on day one — start with the locations you genuinely operate (each branch, the main store, perhaps a quarantine area) and add finer bins only once daily work proves you need them. The expensive setup mistake is the reverse pair: too few locations, so all branches share one pooled total and you can never tell where stock sits; or a sprawl of bins nobody updates, which drift into fiction within weeks.

Key takeaways

Configure warehouses, locations, and bins before stock flows.
Structure gives items a place and movements a destination.
Locations that match physical reality keep on-hand meaningful.
Start with the locations you actually operate and add bins later — too few pools stock blindly, too many drift into fiction.

Lesson 3 of 4 Practice 9 min

Users and roles

People come next: create user accounts for your team and assign each a role that matches their job. Because roles carry permissions, this is also where least-privilege access begins — give each person what they need, no more.

Setting roles thoughtfully at setup avoids a scramble later. It is easier to start tight and grant access on request than to claw back permissions everyone already has.

The trap at setup is making everyone an admin “just so they can get started,” then never walking it back — every account becomes a full-access key and least privilege is dead before day one. Create one or two genuine admins, give the rest the role that fits their job, and use a real per-person account for each (never a shared “cashier1”) so that from the first transaction the audit trail can name who did what.

Key takeaways

Create users and assign each a job-matching role.
Roles carry permissions, so setup is where least privilege starts.
Start tight and grant on request rather than clawing back.
Limit admins to one or two and give everyone a per-person account from day one — never a shared “cashier1” login.

Lesson 4 of 4 Reading 9 min

Sequencing the setup

Order matters. Company settings, then locations, then users and roles, then catalogue and opening balances — each step unlocks the next. Trying to import stock before locations exist, or assign roles before users exist, simply stalls.

A sensible sequence turns setup from a frustrating loop into a checklist. Do the foundations first and the later steps fall into place without backtracking.

A concrete go-live checklist captures the order: company settings confirmed → locations created → roles defined and users invited → catalogue (items, prices, barcodes) loaded → opening stock balances entered at the right locations → one test sale and one test receipt that reconcile. Treat that final reconciling test as the gate: if the test sale shows up correctly in stock and on the sales report, you are ready to open; if it doesn’t, you have found the problem before customers did.

Key takeaways

Setup has an order: settings, then locations, then users/roles, then data.
Each step unlocks the next; skipping ahead stalls.
A sensible sequence makes setup a checklist, not a loop.
Gate go-live on a test sale and receipt that reconcile — if they don’t flow correctly, fix it before opening to customers.

| AWRA OpsHub

Admin Setup & First-Run Configuration

What you’ll learn

Course content

First-run essentials

Locations, warehouses, and structure

Users and roles

Sequencing the setup

Finished the material?

More in this path

Data Migration in Practice

Rollout & Change Management

AwraIQ, Help Center, and Customer Success

Need a quick answer while you read?

AwraIQ