A Copy of Your Setup to Break
The safest place to find out that a new approval rule stops every branch from buying fertiliser is not your live workspace in planting season. A sandbox is a second workspace with your roles, approval rules and procurement settings, none of your records, and no way to send an email.
An agro-dealer with six branches around Eldoret decides in February that any purchase request over KES 500,000 should need the finance manager as well as the branch manager, and that a request with no budget left should be stopped rather than warned about. Both are good controls. Both, switched on in the live workspace the week before the long rains, could hold up every order for seed and fertiliser while someone works out why.
Configuration is code without a test
A software team would never ship a change without trying it somewhere first. An operations team changes the rules that decide who can spend money directly in production, because there has been nowhere else to change them. The result is familiar: a rule saved on Tuesday, a branch manager on the phone on Wednesday, and a rule switched off again on Thursday, with nobody sure what it was meant to catch. Budget control is the clearest case: what warn and block each do to an over-budget request is set out in the budget warning arrives after the approval.
The sandbox is that somewhere else. It is a separate workspace linked to yours, built on request from Settings, and it starts with a copy of how your workspace is set up. Not what is in it.
What is copied, and what is not
| Copied | Left behind |
|---|---|
| Roles and their permissions | Items, suppliers, customers and documents |
| Approval rules and their steps | People and departments |
| Procurement defaults, including budget control | Budgets themselves |
| AI settings | Integrations, API keys and audit streaming |
The line is deliberate. Rules behave the way they would for real because they are your rules. Records stay where they are, so nothing tried in the sandbox can touch a stock balance, a supplier’s bank details or a payslip. It also means the sandbox is not a copy of your data to experiment on: for a rule to have something to act on, you add the handful of records a test needs.
Two translations to know before testing an approval rule
People are not copied, so a step that names a particular person becomes an Admin step in the sandbox. Departments are not copied either, so a rule scoped to one department applies to every department there. Test the amounts and the order of steps; test who exactly receives a request in the live workspace.
Stepping in
Nobody signs in to a sandbox. An administrator steps in from their own session, and the workspace swaps them to a sandbox user of their own, with full administrator rights there. That user’s address is on a reserved domain that can never receive mail, and its password is never usable, so there is no account anyone could be phished for. A banner sits on every page while you are inside: Sandbox. Nothing here is real, and it sends no email, with a button back to your workspace. Leaving takes you back as yourself, and only from your own workspace’s sandbox.
-
Create
Settings, Sandbox, create. One per workspace, named after yours with “(Sandbox)” added.
-
Step in
Add the two approval steps and raise the KES 500,000 threshold. Switch budget control from warn to block.
-
Add what the test needs
A supplier, two items, a budget with KES 300,000 left, and a request for KES 620,000.
-
Watch it run
The approval is refused on the budget. Raise the budget, and the request waits for both approvers in order.
-
Step out and set it up for real
Then rebuild the sandbox from today’s setup, or discard it.
A rule that surprised you in the sandbox cost you an afternoon. The same rule in the live workspace costs you a week of orders.
Nobody hears about it
Approval rules send email. So do purchase orders, reminders and half the workflows in a workspace, and the most embarrassing thing a test can do is reach a real supplier. Any email sent while the sandbox is the current workspace, or addressed only to a sandbox user, is cancelled before it leaves. Not delayed. The suppliers you added to make the test work will never know they exist.
In your own workspace’s activity log, creating the sandbox, stepping into it and discarding it are recorded with who did it and when. Only someone who can edit settings can do any of the three, and nobody can step in while impersonating another user.
Rebuild, or throw it away
A sandbox drifts. After a month your live roles have changed and the sandbox still holds February’s. Rebuild from current setup throws the old sandbox away, everything tried in it included, and makes a fresh copy of today’s configuration. Discard removes it altogether. Neither touches your live workspace, and nothing in the sandbox is ever copied back into it on its own. A change you are happy with goes live when someone sets it up there. For how we prove the other half of the safety net, our own backups, see a backup nobody has restored.
From a tested rule to a live one
The sandbox, its copied configuration and its silenced email are in place. These are the extensions most often asked for, and we can add them to your workspace.
Promote to live
A rule or role that worked in the sandbox copied into your workspace in one step, with the change recorded.
Sample records
A starter set of masked suppliers, items and budgets, so a test does not begin with data entry.
An outbox
The emails the sandbox held back, listed so you can read what real people would have received.
Before you change a control
Where was this rule tried first?
The usual answer
Nowhere; it is a small change.
What it risks
The first test is a real request from a real branch.
Who receives each step?
The usual answer
The finance manager.
What it risks
Check in the live workspace; the sandbox routes named people to Admin.
What happens to a request with no budget?
The usual answer
It gets a warning.
What it risks
Blocking is a different control. Watch one stop before it stops a branch.
The short version
Try a new approval chain, role or procurement control in the sandbox first, with a few test records, and watch it run. It has your setup and none of your data, and it cannot email anyone. When the rule behaves, set it up in the live workspace and rebuild the sandbox for the next change.
What AWRA OpsHub does today
- A sandbox workspace per workspace, created, rebuilt or discarded from Settings by someone who can edit settings.
- A copy of roles with their permissions, approval rules, procurement settings and AI settings, with no records, people or departments.
- Stepping in from your own session as a sandbox administrator who cannot be signed in to, with a banner on every page and a way back.
- Email cancelled for anything sent inside the sandbox or addressed to a sandbox user.
- Create, step-in and discard recorded in your own workspace’s activity log.
More we can add to your workspace
- Promote to live, copying a tested rule or role into your workspace in one step. Commission it
- Sample or masked records in the sandbox, so stock, budget and payroll changes have realistic data to act on. Commission it
- An outbox in the sandbox listing the emails it held back. Commission it
- Departments and custom fields copied across, so department-scoped rules and required fields behave as they do live. Commission it
Where we point you to a specialist
- We will not let a sandbox email your suppliers, customers or staff. Mail from it is cancelled, not queued.
- We will not copy anything from a sandbox into your live workspace on our own. A change goes live when someone in your organization sets it up there.
Promote to live and sample records are the two extensions organizations ask for first.
See the sandbox and restore drills
How the sandbox is built and kept separate, and how we test that our own backups restore.
Explore the sandboxFrequently asked questions
Does the sandbox contain our real records?
No. It copies roles and their permissions, approval rules, procurement settings and AI settings. Items, suppliers, customers, documents, budgets, people and departments stay in your live workspace. You add the few records a test needs.
Can the sandbox send email to our suppliers or staff?
No. Any email sent while the sandbox is the current workspace, or addressed only to a sandbox user, is cancelled before it leaves.
Why did my approval step go to Admin in the sandbox?
People are not copied, so a step that names a particular person becomes an Admin step there. A rule scoped to one department applies to every department, because departments are not copied either.
Who can create or enter the sandbox?
Anyone who can edit settings in your workspace. They step in from their own session as a sandbox administrator; nobody signs in to the sandbox directly.
Does a change made in the sandbox reach our live workspace?
Never on its own. When a rule behaves the way you want, set it up in your live workspace. Rebuilding the sandbox then gives you a fresh copy of the new setup.