Admin Command Center, Setup Templates & Stale Access
One page that tells an administrator what is unfinished, what is switched off and what has gone stale, a template that fills the gaps in a new workspace without overwriting anything, and bulk user changes that carry a reason and one audit batch.
These screens are for whoever looks after the workspace. They sit under Settings on the web, and the command center and stale access lists are also in the AWRA mobile app.
Admin Command Center
Settings → Admin Command Center shows a setup progress figure and three lists. Each item links to the screen that fixes it. You only see items for areas your permissions cover, so a finance admin is not shown warehouse gaps.
- Required defaults — no base currency, no country, no warehouse, or tax not switched on.
- Incomplete controls — admins without multi-factor authentication, more than three active admins, no approval rules, no change-review guards switched on, or no access review in the last 180 days.
- Stale configuration — API keys, users or devices that have gone unused, a security policy unchanged for over a year, or change requests waiting more than a day for a second person.
Opening it needs the manage settings permission.
Industry Setup Templates
Settings → Setup Templates offers five starting points: Retail shop, Wholesale & distribution, Manufacturing, NGO & donor-funded and Professional services. A template covers inventory defaults, a set of workflows, roles, scheduled reports and notification switches.
- It only fills gaps. Anything you have already set is left exactly as it is.
- You see a preview first, listing what would be added and what would be skipped because it already exists.
- Workflows arrive as inactive drafts, so nothing starts running until you switch it on.
- The last ten applications are kept as a history on the same page.
Stale Access
Settings → Stale Access lists access that nobody is using but that still works. It reports only; you fix each item on its usual screen.
- 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.
- API keys unused for 90 days or older than a year.
- Devices still waiting for approval, or trusted but not seen for 90 days.
It needs the view roles permission.
Bulk User Actions
On the Users list, select people and choose an action: send the invitation again, suspend, reactivate, move to another department, force a multi-factor reset, sign them out everywhere, or change their role. Up to 200 people at a time.
- A reason is required (at least five characters), and every audit entry from the action carries the same batch id, so the whole change can be found and explained later as one decision.
- Anyone who cannot be changed is skipped with a reason, and the rest go through.
- The last active Admin is protected: no bulk action can suspend them or take the role away. Only an Admin can give someone the Admin role.
Access Evidence For An Auditor
A Compliance Evidence Pack now carries five access sections: users and their access, roles and permissions, permission and admin changes, a snapshot of workspace settings, and any access by AWRA staff. That is the material an access review asks for, produced from the records rather than from screenshots.
Related: Change Reviews, Delegated Admins & Role Impact and the guide for admins.
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.