Sandbox - How To Use the Sandbox (for clients) – RG Help Center

Introduction

This guide explains what your team can expect once your sandbox programme has been created, what happens next, and how to use the sandbox during its active lifecycle. It is written for client admins.

A sandbox is a separate test programme linked to your live programme. It is designed to let you safely test selected changes and member provisioning journeys without affecting your live production programme.

What Happens First

Once your sandbox has been created, it is launched and prepared for use. A few setup actions happen automatically in the background so your team can begin testing.

Your sandbox is linked to your live client programme.
A dedicated sandbox URL is created for access.
Your first sandbox administrator is set up.
A welcome email is sent to that first administrator.
The sandbox is made available for testing.

Your sandbox is created as an empty sandbox programme. This means it is ready for controlled testing, but it is not intended to behave as a copy of your live programme in every respect.

Your Journey as a Client

1. Access is provisioned: Your named first administrator receives access to the sandbox and a welcome email. Open the email, follow the access steps, and sign in to the sandbox.

2. Initial review: You can enter the sandbox Admin Portal and confirm the programme is available. Check the programme name, URL, and administrator access.

3. Test preparation: Your team prepares the scenarios you want to validate in a safe environment. Agree your test cases, users, and expected outcomes before starting.

4. Testing: You use the sandbox to run supported test journeys, including member provisioning flows.Carry out your planned tests and record outcomes.

5. Lifecycle management: The sandbox remains available for a limited time.Complete testing within the active window and save any findings you need to retain.

6. Sandbox closes: When the lifecycle ends, the sandbox moves toward closure and is deprovisioned. Make sure testing is complete before the sandbox expires.

What Your Administrator Receives

The first sandbox administrator is the main starting point for access. This person is created during sandbox setup and receives a welcome email so they can begin using the environment:

The first sandbox administrator clicks on Activate your account to log into sandbox programme. The sandbox homepage will appear (as shown in the below image):

Next, access the Admin Portal by navigating to Account > then Reward Manager.

The Admin Portal Homepage for the sandbox opens, and can be used straight away:

What You Can Use the Sandbox For

The first phase of the sandbox journey is intended to support safe testing of selected client changes, especially around member provisioning.

Testing member provisioning end to end
Adding a user
Sending a welcome email as part of the flow
Activating the user journey
Validating changes such as provisioning method changes or HRIS-related testing scenarios
Testing changes like bulk workforce email domain updates

The main purpose of the sandbox is to help you validate changes safely before making decisions about your live programme.

What To Expect

Your sandbox is logically separated from your live programme, even though it is created within the production environment model. For clients, the practical outcome is simple: you should treat the sandbox as a safe place to test without changing your live programme.

The sandbox is a separate programme, not your live site.
It has its own access URL.
It is intended for testing and validation, not everyday live operations.
It is time-limited.

Do not treat the sandbox as a permanent environment. It is designed for temporary testing and will be closed after its lifecycle ends.

Key Limitations

Two-month lifespan: your sandbox is available for a limited testing window.
Maximum of 3 active sandboxes per client programme: your organisation cannot hold unlimited active sandboxes at once.
Impersonation is not allowed: Some live-style admin behaviours are intentionally restricted.
SmartSpending is disabled: This product is not available in sandbox programmes.

End of Lifecycle: What Happens Later

Your sandbox does not remain active permanently. It is managed through a defined lifecycle.

The sandbox is created and launched.
It remains active for its testing lifespan.
Once the lifespan expires, it is marked for closure.
It then moves through closure and deprovisioning processes.

If your live client programme enters a closing state, any linked sandboxes may also be moved toward closing as part of that lifecycle.

If you need the sandbox for planned testing, do not wait until the end of the lifecycle window to begin. Start early and allow time for retesting if needed.

FAQs

Q: How will we know the sandbox is ready?

A: Your first sandbox administrator will receive a welcome email and can use the provided access details to log in and confirm the sandbox is available.

Q: Is the sandbox the same as our live programme?

A: No. It is a separate sandbox programme linked to your live programme for testing purposes. It is intended to support safe validation without affecting live operations.

Q: How long can we use the sandbox?

A: A sandbox has a two-month lifespan from creation.

Q: Can we have more than one sandbox?

A: Yes, but there is a limit of up to 3 active sandbox programmes per client scheme at one time.

Q: Can we use every product and feature in the sandbox?

A: No. The first phase supports specific testing goals, especially member provisioning journeys. SmartSpending is disabled in sandbox programmes.