Skip to main content
Procore

About On-Demand Sandboxes

  1. Last updated
  2. Save as PDF
 In Beta
On-Demand Sandboxes are currently in Beta. Limits, availability, and copied data may change as the feature evolves.

On-Demand Sandboxes let you spin up safe, production-like Procore accounts to test, train, and validate changes—on your schedule, without risking your live projects.

Think of an On-Demand Sandbox like a paper towel: grab one when you need it, use it for a specific purpose, then throw it away when you’re done.

What is an On-Demand Sandbox?

An On-Demand Sandbox is a separate Procore company account that:

  • Lives in the same Procore production environment and zone as your source (parent) company.

  • Has feature parity with production and supports the same security model, including mobile and integrations.

  • Can be created, used, and deactivated by your internal admins directly from Procore—no Support ticket required.

When you create an On-Demand Sandbox, Procore copies selected settings and data from your production company into the new Sandbox account, giving you a realistic environment for testing without impacting live work. This “Smart Copy” approach focuses on the data that matters most for validation, rather than cloning your entire database.

Why use an On-Demand Sandbox?

On-Demand Sandboxes are designed to solve several long-standing pain points with traditional sandboxes and second production accounts:

  1. Control & timing

    • You choose when to create and when to deactivate a Sandbox—there are no forced monthly resets.

    • You can maintain a Sandbox for as long as you need, then clean it up when the project or testing cycle is complete.

  2. Realistic, production-like testing

    • On-Demand Sandboxes inherit your company-level security settings and permission templates, so governance stays consistent between Sandbox and production.

    • Financial tools and configuration behave more like your real account, making it easier to validate workflows, reports, and integrations before you go live.

  3. Safer change management

    • Experiment with new configurations, workflows, and Marketplace or custom integrations without touching real projects or budgets.

    • When you’re confident in the setup, replicate those changes in production using your usual change-management process.

  4. Reduced overhead vs. legacy sandboxes

    • On-Demand Sandboxes are not wiped on a fixed schedule, avoiding the “data destruction” cycle that forces teams to rebuild test environments every month.

    • Because Smart Copy targets specific datasets, they are lighter-weight to provision and maintain than full database clones. No Support ticket required to create or manage them.

How On-Demand Sandboxes Work

Lifecycle

 Important
Deactivation is permanent. Once deactivated, a Sandbox cannot be restored.

On-Demand Sandboxes follow a simple lifecycle:

  1. Create – A Company Admin uses the Sandbox Management area in Company Admin to create a new Sandbox account.

  2. Use – Teams log in, test, train, and integrate just as they would in production.

  3. Deactivate – When the Sandbox is no longer needed, the admin deactivates it from the same Sandbox Management screen to keep things tidy and within your Sandbox limits.

What gets copied — and what doesn’t

 Note
Creating or using an On-Demand Sandbox never deletes or modifies data in your production account.

Smart Copy focuses on configuration and structure — it’s designed to recreate how your account behaves, not duplicate everything in it. The goal is to give you a Sandbox that behaves like your production account without carrying over records that could create confusion or compliance risk.

As a general rule:

  • Copied: Company-level settings, security configuration, permission templates, and — for the projects you select — tool settings and data based on the tools you choose during setup.

  • Not copied: Unsupported tools, integration connections, and Directory users (to prevent unintended access to the Sandbox environment).

During Sandbox creation, you’ll select which supported tools to include and whether to copy settings only or settings and data. Coverage is expanding over time — the tool selection screen in Procore always reflects what’s currently available.

Availability and limits

Who can create On-Demand Sandboxes?

Procore Company Admins can create and manage Sandboxes from the Sandbox Management area.

How many Sandboxes can I have?

During the Beta, each participating company can have up to 3 active On-Demand Sandboxes at a time.

Which environments are supported?

On-Demand Sandboxes are hosted in the same zone as your production company and are designed to support all Procore zones, including US, international regions, and (as work completes) FedRAMP-aligned environments.

Do On-Demand Sandboxes support mobile and integrations?

Yes. On-Demand Sandboxes offer full integration compatibility and mobile support, matching production. Integrations are not copied from your production account — you’ll need to connect them to the Sandbox separately.

For more detail on limits and entitlements as we approach GA, see your Procore account team or the Sandbox Packaging documentation.

What On-Demand Sandboxes are best for

Here are some of the most common scenarios where an On-Demand Sandbox is a better fit than the legacy Monthly Sandbox or a second production account:

Test new workflows or integrations

  • Connect Marketplace apps or custom integrations to a Sandbox and validate:

    • Authentication and permissions

    • Data flows (create/update operations)

    • Custom field mappings and automation behavior

    • Iterate quickly without waiting for a monthly refresh or risking real project data.

Train new users

  • Give new team members access to a safe environment that feels like your production account, with familiar tools and settings.

  • Use copied projects or templates so they can practice on realistic scenarios without touching live jobs.

Experiment with new features

  • Use a Sandbox to explore new Procore features, workflows, or configurations before rolling them out to the whole company.

  • Pair Sandboxes with feature-flagged or beta functionality to collect feedback from a small group of users in a low-risk environment.

Validate changes before going live

  • Trial changes to:

    • Company-level permission templates

    • Financial settings and workflows

    • Project configuration (statuses, locations, custom fieldsets, etc.)

  • Once validated, replicate the configuration in production following your internal governance process.

See Also