# Change Domain Environment | Secure Privacy Guide

> [CMP v1] Learn how to switch your Secure Privacy domain between development, staging, and production environments without buying additional licenses — edit the domain URL and rescan in a few steps.

- Canonical: https://support.secureprivacy.ai/article/cmp-v1-how-to-add-a-development-staging-or-test-domain-to-secure-privacy
- Product: Consent Management
- Category: Secure Privacy Legacy
- Published: 2026-03-06T12:44:00+00:00
- Updated: 2026-03-22T21:39:05.613+00:00
- Reading time: 2 minutes

---

You do not need to purchase additional licenses to use Secure Privacy across development, staging, and production environments. By editing your domain name in the dashboard, you can move the same configuration — including your API key and all settings — between environments without any extra cost.

## Who Is This For?

-   Developers testing Secure Privacy on a staging or development environment before going live
    
-   Website administrators switching a configured Secure Privacy domain from a dev or QA URL to production
    
-   Compliance teams managing Secure Privacy across multiple domain environments without buying additional licenses
    

## How to Change Your Domain Environment in Secure Privacy

![Secure Privacy All Domains page showing the Edit domain button for updating a domain URL in the dashboard](https://pub-7bd19505838640d0a08ef1bd6ec3fb9b.r2.dev/articles/674ae30e03983396da4c-a2583ffdec6d.webp)

1.  Log in to your Secure Privacy account. In the upper-left corner, click **All Domains**.
    
2.  Find the domain you want to edit and click the **Edit domain** button in that row.
    
3.  A modal window will appear allowing you to change the domain URL.
    
4.  Enter your staging, testing, or development server URL — for example, `dev.mydomain.com` — and click **Save**.
    

You can now use Secure Privacy on the new domain with the same API key and installation configuration.

**Note:** After changing the domain URL, trigger a website rescan from the **Report** section to update the detected cookies and services to those on your staging or development environment — particularly if you have been adding or removing scripts there.

Once you have finished testing, edit the domain URL back from `dev.mydomain.com` to your production URL — for example, `mydomain.com` — to go live with your configured settings. Run another rescan after switching to production if your environments differ in any tracked services or scripts.

## Frequently Asked Questions

### Do I need a separate Secure Privacy license for my staging environment?

No. You can use the same license and API key across your development, staging, and production environments by simply editing the domain URL in the dashboard. Only one URL can be active per domain slot at a time.

### Will my configuration be lost when I change the domain URL?

No. All your Secure Privacy settings — including banner configuration, classification, blocking rules, and language settings — are tied to the domain record, not the URL itself. Editing the domain URL retains all existing configuration.

### Why should I rescan after changing the domain URL?

Your staging and production environments may have different cookies and third-party services active. A rescan after switching URLs ensures your scan report, blocking configuration, and cookie declaration accurately reflect what is running on the current environment rather than the previous one.

## See Also

-   [Secure Privacy Pricing Plans Overview](https://support.secureprivacy.ai/article/secure-privacy-pricing-plans--consent-management-platform)
    
-   [Website Visits vs Page Views vs Consent Explained](https://support.secureprivacy.ai/article/website-visits-vs-page-views-vs-consent-explained)
    
-   [Secure Privacy Volume Discounts | Custom Consent Storage Pricing](https://support.secureprivacy.ai/article/secure-privacy-volume-discounts--custom-consent-storage-pricing)