Admin, Workspace, and Platform Operations

Workspace 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.

In practice, a new workspace starts at Settings → Setup Templates and Settings → Admin Command Center. A template (Retail shop, Wholesale & distribution, Manufacturing, NGO & donor-funded or Professional services) fills gaps in inventory defaults, roles, workflows, scheduled reports and notification switches; it previews what it would add and skip, never overwrites anything already set, and installs its workflows as inactive drafts. The command center then shows what is still missing, such as no base currency, no country, no warehouse, tax not switched on, admins without multi-factor authentication, or no approval rules, each linked to the screen that fixes it. Load data last and in dependency order, warehouses and locations before items with stock and accounts before anything that posts to them, using each module’s template and the Check File dry run before the real import.

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.

In practice, the monthly user review starts at Settings → Stale Access, which lists dormant users (no sign-in for 90 days, or never signed in on an account over 30 days old), unused roles, and people who hold a risky pair of permissions such as raising and approving the same document. Fix each item on its usual screen. For a group change, select people on the Users list and choose one action, such as sending the invitation again, suspending, reactivating, moving department, forcing a multi-factor reset, signing out everywhere or changing role, for up to 200 people at once. A reason of at least five characters is required, and every audit entry from that action carries the same batch id, so the whole change can be found and explained later as one decision.

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.

In practice, most reports that something is broken turn out to be access or setup. When a user cannot see a menu, check their role, branch or warehouse assignment, the module’s plan availability and the record’s status before escalating; that is the organization admin’s decision, not AWRA Support’s. When someone says an email never arrived, check the email column for that row in Settings → Notification Preferences, then Email Logs: a message that was sent and not received is a mailbox problem, and one that was never sent is a preference or data problem. A push that never arrives is usually a stale device registration, cleared under Settings → Push Notifications. When a ticket does go to AWRA, include the page, record number, visible message and what you expected, so support can act on the first reply.