As the saying goes… practice makes perfect, and now you can with the Rosterfy Sandbox.

We wanted to create a safe space to test, experiment, learn and explore Rosterfy with data, without impacting your live environment.

The Rosterfy Sandbox will allow you to do just that!

With the Rosterfy Sandbox, you can:

✅ Try out new features risk-free

✅ Train your team in a safe environment

✅ Build confidence before going live

✅ Experiment, learn, and refine without stress

Whether you’re testing workflows, exploring new functionality, or onboarding staff, Sandbox gives you the freedom to experiment safely and scale with confidence.

There are a few important things for admins to note, in relation to the sandbox environment:

Administrators can replicate production configurations and data - excluding all Personally Identifiable Information (PII)—within the sandbox environment, however cannot push changes back to production.

This enables secure, real-world testing scenarios without impacting live operations.

Admins will be able to test workflows and settings within the sandbox before applying them manually in the live production environment.

The sandbox environment has some limitations on what data is available. The following data types are included in the one-way sync from production:

To ensure data security and privacy compliance, certain sensitive information is excluded from the sandbox environment.

Data that is NOT available in the sync from production to sandbox, includes all user related data, such as;

As well as any records history and integration related settings.

To request access to a sandbox environment, please contact your Rosterfy Client Support Manager.

Once initiated, Rosterfy will provision a dedicated sandbox for your organisation. Administrator permissions within the sandbox are managed using role-based access controls, enabling you to restrict sandbox access to specific users as needed.

Sandbox permission is available for System Admin permission types only.

The permission can be restricted to Sandbox Access only or granting permission to Reset and/or Refresh the sandbox.

Follow these simple steps to control Sandbox permissions for your admins:

For more information on admin permissions, check out the Admin Permissions article.

To access the Sandbox, follow these simple instructions:

Whether you need to revert the changes you have made to your sandbox or align the environment with your live production, we have an option available to you.

For more information, check out the Resetting vs Refreshing the Sandbox article.

1. What are the limitations of the data imported into Sandbox?

2. Are third party integrations supported?

3. Is SSO supported?

4. Are there limitations to the number of admins that can access Sandbox?

5. If my organisation has multiple accounts (sub-accounts), will they all be enabled in sandbox?

6. When triggering a reset / refresh, will this apply for all accounts my organisation has?

There will be no PII (Personally Identifiable Information) imported into sandbox and the Sandbox Use policy stipulates not to add any PII to Sandbox.

Third party integrations are not supported within Sandbox.

Unfortunately, we do not support SSO within the Sandbox environment.

If your organisation enforces SSO for administrators, you will still be able to access the Sandbox environment through the admin console.

However, if you currently enforce SSO for both your admins and your volunteers, you will need to contact your Client Support Manager for assistance with the Sandbox Environment.

There are currently no limitations to the number of admins that can access sandbox, access is controlled through Admin Permissions.

Yes, all accounts will be included as sandbox is enabled.

The reset / refresh function will apply for all accounts in the sandbox for your organisation, and does not trigger on an account by account basis.