Introduction
Sandbox Programmes give clients a controlled way to test selected changes in an environment connected to production infrastructure, without affecting their live programme. This article is intended for client admins, HR teams, and implementation stakeholders who need to understand what Sandbox is, when to use it, and what to expect.
Phase 1 of Sandbox Programmes is focused on end-to-end member provisioning testing.
Sandbox Overview
A Sandbox Programme is a separate test programme linked to your live client programme. It is designed to let you validate certain changes in a more realistic environment than staging or UAT, while keeping testing activity clearly separated from live employee activity.
Sandbox is useful when you need more confidence before making a production change. Instead of testing directly in your live programme, you can use a dedicated sandbox to trial selected setup changes and provisioning journeys.
Key benefits include safer testing, reduced risk to live users, and better confidence when changing provisioning or integration-related setup.
Test selected changes without using your live programme
Validate provisioning journeys in a realistic environment
Reduce the risk of accidental impact on employees
Support change planning for integrations and user data flows
Prerequisites
Sandbox access is controlled and is not available as a self-serve feature.
| Prerequisite | Who it applies to | Details |
Existing live client programme | All clients | A sandbox is created in relation to an existing live programme and is not a standalone environment. |
First sandbox administrator | Client or internal contact | The first admin must already be a member of the connected live programme (or be an internal contact). |
Request through your CSM | All clients | Sandbox creation is initiated through your Customer Success Manager or relevant internal contact. |
If you are unsure who should be the first sandbox administrator, work with your CSM to confirm the most suitable contact.
Enablement and Configuration
Sandbox Programmes are enabled through a managed request process. Clients cannot currently create a sandbox directly in the platform.
To get started, contact your CSM with the details of the testing need. The sandbox will then be created and linked to your live programme.
What Can Be Set Up
A dedicated sandbox URL or alias
The first sandbox administrator
Optional branding copied from the live programme, such as colours and logos
The link between the sandbox and your production programme
Important Limits To Know
Up to 3 active sandbox programmes can exist per client scheme
Each sandbox has a 2-month lifecycle
Phase 1 sandboxes are created empty
Client self-serve sandbox creation is currently out of scope
Core Feature Summary
Sandbox Programme Creation
A separate programme is created specifically for testing. This gives your team a controlled space for test activity without reusing the live programme.
Value: helps keep testing organised and reduces the chance of live and test activity being mixed.
Linked Relationship To Your Live Programme
The sandbox is connected to your existing client programme for visibility and control, while remaining a distinct testing environment.
Value: makes it easier to understand what the sandbox relates to and who it belongs to.
First Administrator Setup
A first sandbox administrator is created during setup so the environment is ready to use.
Value: reduces setup effort and helps your team begin testing faster.
Automated Lifecycle Management
Each sandbox is available for a limited period and is automatically moved toward closure at the end of its lifecycle.
Value: keeps testing environments controlled and prevents outdated sandboxes remaining active longer than needed.
Provisioning Journey Testing
Phase 1 supports end-to-end member provisioning testing, including adding a user, sending a welcome email, and activating the account.
Value: gives teams a practical way to validate key onboarding journeys before making live changes.
Key Benefits
Sandbox Programmes help solve a common problem: many clients need a safer, more realistic place to test changes than staging or UAT can provide.
Value for HR and admin teams
More confidence before changing provisioning or integration setup
A safer way to test user data and onboarding flows
Reduced risk of live disruption
Better control through managed access and expiry rules
Value for employees
Lower chance of being affected by untested live changes
Better onboarding experience when changes are validated first
More reliable activation journeys after production updates
Personalisation options currently include optional branding copied from the live programme and a dedicated sandbox access path.
How It Works
Your team identifies a change that should be tested before it is made in the live programme.
You contact your CSM and explain the testing requirement.
A sandbox is created and linked to your live programme.
The first sandbox administrator is set up and given access.
Your team carries out the agreed testing activities in the sandbox.
The sandbox is automatically retired at the end of its lifecycle.
If screenshots are added later, this section is a good place to include them to support the request and access journey.
Use Cases
Provisioning method change: test a move from manual provisioning to an automated flow.
HRIS or integration update: validate how user data will flow before switching the live process.
Email domain change: test employee onboarding behaviour after a bulk email update.
Implementation validation: confirm key onboarding steps work as expected in a realistic platform setup.
User Experience
The sandbox experience is designed to feel familiar, clear, and low risk. For client admins and HR teams, it should feel like a recognisable version of the live programme while staying clearly separate from live employee activity.
The overall experience is intentionally governed rather than open-ended. Managed creation, role-based access, environment limits, and expiry rules are part of the product design and help keep testing safe and controlled.
Compliance and Security
Sandbox Programmes are designed to support testing while maintaining control and separation from live operations. Access is role-based, creation is managed, and each sandbox has a defined lifecycle.
Testing activity is kept separate from live programme use
Access is restricted to approved users
Sandboxes expire automatically to reduce long-lived exposure
There is a limit on the number of active sandboxes per client scheme
Comments
0 comments
Please sign in to leave a comment.