> For the complete documentation index, see [llms.txt](https://kbase.whitelabel-loyalty.com/product/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kbase.whitelabel-loyalty.com/product/loyalty-engine/loyalty-console/production-and-staging-environments.md). # Production & staging environments Learn how to use the staging and production environments in the Loyalty Console for testing and live deployment, along with key differences, limitations, and considerations for each mode. ## About staging & production The “Live & Test” toggle in the Loyalty Console allows you to switch between your production and staging environments. These environments operate independently, each with its own set of resources such as event types, users, rewards, and audiences. The only shared element between the two is your console administrators, which are managed through the Settings > Administrators screen. {% hint style="warning" %} **Take care when making changes in live mode, as changes will reflect immediately to your users** (or in the case of scheduled campaigns and rewards, changes will reflect once they are scheduled to begin). {% endhint %} *** ## Staging environment **The staging environment is intended for proof of concept (PoC) and functional testing**, providing a safe space to validate your setup before replicating in production. Consider your staging environment as a sandbox where you can experiment with new event types, campaigns, audiences, and reward flows. When you're satisfied and ready to make these features available to your loyalty program end-users, deploy them in your production environment (also known as 'live mode'). #### Staging environment considerations * The staging environment is not intended for performance, load or stress testing. * When using staging, reactions and audience calculations may take longer to occur than in your production. * The staging environment operates with restricted resources and does not support scaling, making it unsuitable for testing scenarios that require high availability or large-scale demand. * There is no guaranteed uptime or service level agreement (SLA) for the staging environment. * Data dashboards & analytics are not available in test mode. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://kbase.whitelabel-loyalty.com/product/loyalty-engine/loyalty-console/production-and-staging-environments.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.