# How does environment promotion work?

Source: https://govform.com/resources/documentation/article/help-centre-how-does-environment-promotion-work
Topic: Architecture & integrations

**Govform gives you a clear, controlled route from an instantly updated prototype to a tested QA service and a published Production version.**

You can improve a design without immediately changing the live journey. Each environment has a purpose, and saved service versions and deployment records help your team understand what is being tested and what users are running.

## Use each environment for the right work

Develop quickly and test real behaviour before launch
| Environment | What it is for |
| --- | --- |
| Prototype / User view | Instant feedback on content, validation and routes, with shareable previews and mock or suppressed external actions. |
| QA | End-to-end integration testing and user acceptance testing using deployed service versions and test connections. |
| Production | The reviewed live service, using Production identity, integration and domain configuration. |
| Optional Staging | An additional deployment environment where enabled for your library. |

## Keep every release understandable

-   **Review saved versions.** Change history lets you inspect earlier designs and compare them with the current service.
-   **See what is deployed.** Environment records identify the service version deployed, when it was deployed and by whom.
-   **Separate test and live connections.** QA and Production authentication, storage and API configuration support realistic testing with suitable destinations.
-   **Match deployment rights to roles.** Team permissions can allow QA deployment while reserving Production access for authorised users.
-   **Recover a previous design.** Change management supports returning to a saved version and deploying the reviewed version through the normal release process.

Use the prototype to refine the experience, then QA to prove real sign-in and integration behaviour. Changes to library authentication, branding or portal configuration may need their own environment application or deployment alongside the service.

See [environments and deployments](<https://govform.com/resources/documentation/article/21-09-service-environments-and-deployments>) and [change management](<https://govform.com/resources/documentation/article/21-08-service-change-management>).