| AWRA OpsHub

 Search
Intermediate Certificate on pass

Admin, Tenant, and Platform Operations

Run the account layer: tenant setup, users, roles, settings, notifications, imports, search, and support routines.

3 lessons 40 min 5-question assessment 70% to pass
Take the assessment

What you’ll learn

  • Set up tenant foundations that every module depends on
  • Manage user lifecycle without creating access drift
  • Use settings, notifications, and imports as platform controls
  • Support users through search, tickets, and clear admin routines

Course content

3 lessons · 40 min of reading
01
Lesson 1 of 3 Workshop 13 min

Tenant setup is the operating system

Tenant setup is not a one-time form. Company profile, currency, tax details, timezone, warehouses, locations, users, roles, receipt settings, inventory defaults, and security settings become the operating system for every transaction.

When these basics are weak, every module feels harder. When they are correct, teams move faster because the system already knows how the business works.

First control layer

Company profile and tax details are correct
Branches, warehouses, and locations match reality
Roles are designed before users are invited
Inventory defaults are set before stock is imported
Receipt and notification settings match operations
Security settings reflect company risk
02
Lesson 2 of 3 Lab 14 min

Users, roles, and settings without drift

Access drift happens when old roles, inactive users, changed responsibilities, and one-off fixes accumulate. Admins keep AWRA healthy by reviewing users, forcing logout when needed, resending welcome messages, disabling access, and keeping roles aligned to real jobs.

Settings drift works the same way. A custom field, notification preference, or import default can be useful today and confusing later if nobody owns it.

Admin routine table

Routine Frequency Purpose
User review Monthly Remove inactive access and update role fit
Role audit Quarterly Catch over-permissioned users
Settings review After rollout or module change Keep defaults and fields relevant
Import template check Before every migration batch Avoid bad data entering at scale
Notification review When users report noise or silence Balance visibility with focus

Key takeaways

  • Admin work is recurring governance, not only setup.
  • Access and settings both drift without ownership.
  • A small scheduled review prevents painful cleanup later.
03
Lesson 3 of 3 Practice 13 min

Support, search, and communication habits

A good admin reduces support load by helping users find records, understand missing permissions, submit useful tickets, and read notifications correctly.

Search, messages, email logs, notification display settings, pinned menus, and public docs are part of platform operations. They shape whether people feel guided or stranded.

Support habit

1

Clarify the task

What was the user trying to do?

2

Check access

Is the role, plan, branch, or module permission blocking them?

3

Find the source record

Use search and module pages before guessing.

4

Record the support trail

Use messages, replies, and logs so the issue can be followed later.

Finished the material?

Take the 5-question assessment and earn your certificate — 70% to pass.

Take the assessment

More in this path

Workflow Builder Basics

Open course

Approval Workflows

Open course

Security & Data Protection

Open course

Help Center

Need a quick answer while you read?

Run inventory, procurement, assets, sales, and field work with approved AWRA guidance for setup, migration, integrations, security, pricing, and support.

Search all approved AWRA public help articles.

Open Help Center