Want to trial new workflows, automations or integrations without any risk to live projects? Asana Sandboxes give admins a safe, separate environment that mirrors your organisation’s setup so you can validate changes, train teams and document processes—then roll out with confidence. You can request and manage a Sandbox from the Admin Console.

Key points / benefits

• Isolate testing from live data: Experiment freely without impacting production.

• De-risk changes and integrations: Validate rules, forms, automations and app connections before launch.

• Train without consequences: Onboard new joiners and practice admin tasks safely.

What’s new or how it works

Asana added a Sandboxes landing page in the Admin Console so qualified admins can request and manage a Sandbox directly—no tickets required. From there, you can invite members and run realistic tests with familiar projects, teams and permissions.

Step-by-step: set up and use an Asana Sandbox

1. Check eligibility & access the Admin Console
   From your profile menu, open Admin Console. Look for Sandboxes. (Availability depends on your plan and admin role.)
   
   

2. Request a Sandbox
   Use the Sandboxes page to request your environment. This creates a non-production Asana space for testing.
   
   

3. Invite only the people you need
   In the Sandbox’s Admin Console → Members, invite testers, trainers or vendors. Keep membership tight for clean results and cost control.
   
   

4. Recreate (or import) representative projects
   Build a few realistic projects with the same custom fields, forms and rules you use in production—so tests reflect real life. (Tip: duplicate templates you rely on.)
   
   

5. Connect integrations you plan to use
   Re-authorise apps and webhooks in the Sandbox (API tokens are environment-specific). For API or app testing, you can also use an Asana Developer Sandbox—a temporary domain intended for integration work.
   
   

6. Run end-to-end test scenarios

   • Create → triage → approve → deliver flows

   • Automation checks (rules, forms, custom fields)

   • Permission & sharing behaviour

   • App behaviours (e.g., Jira, Slack, BI connectors)
     
     

7. Document what works, then promote
   Save playbooks and screenshots. When you’re satisfied, reproduce the configuration in production (projects, rules, templates) and communicate the change window.

Practical examples

• Train new project leads: Use the Sandbox to practise creating templates, rules and dashboards without touching real portfolios.

• Trial an integration: Connect a staging app to the Sandbox to confirm OAuth scopes, field mappings and webhook triggers before enabling in production.

• Change management rehearsal: Dry-run a workflow change (e.g., new intake form + rule set) with a pilot group; gather feedback; then deploy confidently.

FAQs

What is the Asana Sandbox?
A separate, non-production environment for testing features, workflows and integrations without affecting live data. Managed from the Admin Console. Asana Help Centre

How do I access it?
Open Admin Console from your profile menu and look for Sandboxes. Eligible admins can request/manage a Sandbox directly there. Asana Help Centre+1

Is this the same as the Developer Sandbox?
Not quite. The organisation Sandbox is for teams/admins to test workflows. The Developer Sandbox is a temporary domain primarily for API and third-party integration development. Asana Docs

Who gets access?
Sandbox availability is linked to plan and admin permissions (typically higher-tier/Enterprise). Check the Asana feature list and your plan. Asana Help Centre

Will changes in Sandbox affect production?
No—Sandbox is isolated from your live environment. Re-apply validated changes manually when ready. Asana Help Centre