How Quillio handles sandbox environments
Enterprise firms can request a sandbox environment — a separate tenant used for testing, training, and integration development. Sandboxes are isolated from your production firm tenant and refresh with synthetic data. Sandboxes are included on Enterprise plans.
Use cases
Sandboxes are used for onboarding training (new users practise on synthetic matters), integration development (build and test Actionstep or API integrations without affecting production), and evaluating new features before enabling them firm-wide.
Data handling
Sandboxes should not contain real client matter data. Synthetic data is available or you can upload de-identified sample documents. Production client data should never be uploaded to a sandbox — this is contractually committed.
Refresh and isolation
Sandboxes are reset on request or on a scheduled basis. Sandbox changes never propagate to production — you test safely. User accounts in the sandbox are separate from production so you can use different roles for testing.
Common issues
- Real client data in sandboxes breaches our terms — do not upload
- Sandbox features can differ slightly from production during preview releases
- Sandbox-to-production migration of configuration is manual — plan accordingly
Try Quillio on a real matter.
The fastest way to know if Quillio fits your practice is to use it on your own work. The free trial requires no credit card and no sales call.
Start your free trial