---
nav: wcp_docs
parent_url: /wcp_docs/
title: >- 
  Reference: Implementation Best Practices for Gold Tenants
layout: subsection
---

<a id="section_1"></a>
![](GUID-8efbfc9c-0d11-4c18-b471-a4f821682539.png)

GOLD tenants are Implementation tenants that eventually become a Production tenant. To install and configure an app in a GOLD tenant, you only need to promote the app to Implementation. In order for an app to appear in a Production tenant, it must be promoted to Production in the Developer site even if it is already installed on the GOLD tenant. Otherwise, the app won’t be available for you to install and configure in the Production tenant.

## <a id="section_2"></a>Best Practices

We recommend using one of these general approaches to working with GOLD tenants:

-   Follow the typical app lifecycle. Install and configure the app directly in the Production tenant and avoid doing anything in the GOLD tenant. Use this approach when:

    -   You do not intend to use your Extend app during the first 2 weeks of production. This limitation doesn't apply to integration apps.
    -   Significant data conversion is not required.

-   If you do intend to use your app immediately after the creation of the Production tenant from the GOLD tenant, ensure that your app's source code is promoted to Production at least 1 week prior to the creation of the Production tenant from the GOLD tenant

    <b>Note:</b> Workday can't make exceptions to promote apps that miss the 1-week cut-off before Production tenant creation. If your app misses the cut-off, your app's tenanted data may be corrupted in these ways:

    -   Duplicate or orphan domain security domain policy.
    -   Missing functional areas.
    -   Non-functional Calculated Fields or WQL statements.
    -   Corrupted business process (BP) definitions, BP security policies, and BP notifications.

    To correct these issues, you must recreate the corrupted data, and Workday must run backend processes to clear the corrupted data.

    .