# Shared Cache

Shared Cache allows multiple accounts or domains to use the same cache structure by applying a Domain Cache Key. When set to **Share**, identical content is cached only once and served across participating accounts, improving efficiency and reducing redundant origin requests.\
When set to **Default**, each account maintains its own isolated cache.

You can manage Shared Cache in the [Medianova Control Panel](https://cloud.medianova.com) or via [API](https://clients.medianova.com/api-documentation/performance-cdn/caching#put-api-v1-cdn-organization_uuid-resource-resource_uuid-5).

Log in to the Medianova Control Panel, select a CDN resource in the CDN section, and navigate to the **Caching** tab.

## Configure Shared Cache

{% stepper %}
{% step %}

### Select the Cache Status

Choose one of the following options:

* **Default** — Each account maintains a separate cache structure.
* **Share** — Cache is shared across accounts using the Domain Cache Key.
  {% endstep %}

{% step %}

### Submit the Configuration

Click **Submit** to apply the selected cache status.
{% endstep %}
{% endstepper %}

## **Behaviour**

* When set to **Share**, CDN edge nodes use the same cache namespace for resources that match the Domain Cache Key.
* Cache hits increase across accounts that serve identical content.
* Changing the status does not purge existing cache; behavior changes apply to future caching operations.
* When set to **Default**, each account's cache becomes isolated again.

## **FAQ**

**Does enabling Shared Cache expose content from one customer to another?**\
No. Shared Cache only applies where explicit Domain Cache Key alignment exists and is intentionally configured.

**Does switching from Default to Share purge existing cache?**\
No. Existing cached content expires naturally according to its TTL.

**When should Shared Cache be enabled?**\
It is beneficial when multiple accounts deliver the same static assets (e.g., white-label platforms, partner domains).