eBrigade Test environment module
An isolated copy of your eBrigade to test and train risk-free
Test new settings, train your key users or prepare a migration on a full copy of your production instance — refreshed automatically and completely sealed off. Nothing done in the test environment reaches your real data, and no email is ever sent to your members. Activation on quote.
Activation on quote: this button is about an additional eBrigade instance dedicated to testing.
Train your administrators and validate your settings on an isolated copy of your production, refreshed automatically and without a single email sent to your real members. Activation on quote.
What is the eBrigade Test environment module?
Train your administrators and validate your settings on an isolated copy of your production instance, refreshed automatically and without a single email sent to your real members. Activation on quote. It is available as an option so that each organisation can enable it as needed.
Why use the test environment?
Training new administrators or testing a reorganisation of your structure directly in production means risking corrupting real data. A wrong click on a reference list, a badly configured scheduling rule — or worse, an email campaign sent by mistake to hundreds of members — can do damage before it is even noticed. And without a testing ground, every change to your settings becomes a risky bet.
What the test environment changes in eBrigade
The test environment is a second eBrigade instance, an isolated copy of your production, in which your teams can configure, break and start again without any consequences. Its content is refreshed automatically from production on the schedule you choose, and a TEST marker is displayed throughout the interface to avoid any confusion. In test mode, all emails are redirected to the administrator: your members never receive anything. Activation on quote, configuration reserved for super-administrators.
What you can do with Test environment
The test environment is a second eBrigade instance that carries over the data, settings and modules of your production. Your administrators and trainers work in a context true to real life, not on empty data.
In test mode, all notifications and email campaigns are automatically redirected to the administrator. You can trigger sends to test them without a single message going to your real members.
Choose to copy production into the test environment on a recurring basis (selected days of the week, at 4:00 am) or as a one-off (a specific date). Each test environment thus starts from an up-to-date state, with no manual intervention.
As long as the instance is marked as the test environment, a TEST indicator is displayed in the interface. There is no way to confuse the trial environment with the production instance in use.
A History tab records each operation with its date, its frequency (recurring or one-off), its status (success, pending, error) and a comment. You always know when the test environment was updated and whether everything went well.
The test environment is a second eBrigade, separate from your main plan. It is activated on quote by the eBrigade team, and its refresh is set by administrators with General configuration rights, ensuring a clear separation between testing and production.
Step by step
The test environment is an instance separate from your main plan. The first step is to subscribe to a second eBrigade, activated on quote.
Open a ticket with the eBrigade team: they link the instance to your production and take care of activation.
Turn on the “This is the test database” switch. The TEST marker appears in the interface and email redirection to the administrator takes effect immediately.
Set how often production is copied — recurring (chosen days, at 4:00 am) or one-off (a specific date). Your test environment stays aligned with real life automatically.
Your teams experiment freely. Validated settings are then carried over to production with confidence, and the History tab keeps a record of every refresh.
Where this module really pays off
eBrigade administrators: test complex configurations (permissions, workflows, reference lists) on a copy of production, with no risk to real data.
Trainers and key users: train new administrators on an environment true to real life, without ever emailing members.
Multi-site roll-out: prepare and rehearse the setup of new organisations before they actually go live.
IT teams: validate advanced integrations (SSO, API, bulk imports) on a dedicated instance before enabling them in production.
Migration projects: try out a reorganisation of your structure or reference lists on a refreshed copy, then carry the validated settings over to production.
Frequently asked questions
Does the test environment contain the same data as production?
Yes. The test environment is a copy of your production, refreshed automatically on the schedule you set (recurring or one-off, at 4:00 am). Any change made there stays sealed off and never affects production.
Could my members receive emails from the test environment?
No. As long as the instance is marked as the test environment, all outgoing emails are automatically redirected to the administrator. You can test sends and campaigns without a single message going to your real members.
How do I know I am in the test environment and not in production?
A TEST marker is permanently displayed in the interface when the instance is marked as the test environment. This avoids any confusion with production.
How is the test environment updated?
You choose a recurring refresh (one or more days of the week, at 4:00 am) or a one-off refresh (a specific date). A History tab records each operation with its date, frequency and status (success, pending or error).
Who can activate and configure the test environment?
Activation is carried out by the eBrigade team; the refresh is then set by administrators with General configuration rights. It is a second eBrigade, separate from your main plan, activated on quote: contact the eBrigade team to discuss it.
How do I activate the test environment?
In two steps: subscribe to a second eBrigade, then open a ticket with support to finalise activation. Our team links the instance to your production and takes care of the setup.