> ## Documentation Index
> Fetch the complete documentation index at: https://faqs.xoxoday.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Does Xoxoday Plum support separate deployment environments?

> Xoxoday Plum provides three segregated environments — Development, UAT, and Production — so teams can build, test, and release safely.

<Note>
  Xoxoday Plum maintains three dedicated deployment environments — Development, UAT, and Production — ensuring changes are validated at every stage before reaching live users.
</Note>

## How Xoxoday Plum Structures Its Deployment Environments

Xoxoday Plum operates across three distinct, isolated environments: Development (Dev), User Acceptance Testing (UAT), and Production (Prod). Each environment serves a specific stage in the release lifecycle, and access between them is strictly controlled to prevent untested changes from affecting live reward programmes.

This separation matters most during integrations and configuration changes. When your IT or HR operations team connects Xoxoday Plum with systems such as Workday, SAP SuccessFactors, or Darwinbox, the integration is first built and validated in Dev, promoted to UAT for business-side sign-off, and only then released to Production. This workflow eliminates the risk of a misconfigured HRMS sync disrupting active reward balances or redemption flows for your employees.

## What Each Environment Is Used For

The **Development environment** is where Xoxoday Plum's engineering team builds new features, fixes defects, and experiments with configuration changes. It is not connected to live data and is intended purely for internal build-and-break cycles.

The **UAT environment** is where your organisation's administrators and integration partners conduct acceptance testing. If your team is rolling out a new MS Teams notification workflow or a Slack-based reward nudge, UAT gives stakeholders a production-equivalent sandbox to validate behaviour before go-live. Changes here reflect the real platform configuration without touching live employee accounts or points balances.

The **Production environment** is the live instance serving your workforce. Only changes that have passed both Dev and UAT gates are promoted here, ensuring stability and data integrity across your reward programmes.

## Why Environment Segregation Matters for Enterprise Deployments

For organisations operating at scale — spanning multiple geographies, business units, or HR systems — environment segregation is a prerequisite for safe change management. Xoxoday Plum's three-tier model aligns with enterprise IT governance standards and supports the audit trail requirements associated with certifications such as ISO 27001 and SOC 2 Type II.

It also gives your IT team a clear rollback boundary. If a configuration promoted to UAT produces unexpected behaviour, it can be corrected before it ever touches Production, protecting the end-user experience and the integrity of your incentive data.

When onboarding, your implementation team will receive environment-specific credentials for Dev and UAT. Production access is provisioned separately following sign-off, keeping the promotion path deliberate and auditable.

**Learn more:** \[Xoxoday Plum Help Centre — General]\(

<CardGroup cols={2}>
  <Card title="Security & Compliance Standards" href="/plum/rewards/gift-cards">
    Understand how Xoxoday Plum meets ISO 27001 and SOC 2 Type II requirements, including data segregation and access controls across environments.
  </Card>

  <Card title="HRMS & SSO Integrations" href="/plum/rewards/sso-tokenization-approach-customer-identity-session">
    Connect Xoxoday Plum with Workday, SAP SuccessFactors, Darwinbox, and other HR systems using environment-safe integration workflows.
  </Card>
</CardGroup>