# Deployment **Deployment** holds all the environment details like URL and data base details.‌ Each team are given a particular environment in which they run there Project or product like the development team are given Developer environment(deployment A), the QA team are given QA environment (deployment B) and finally the actual product or project is released in the Production environment (deployment C).‌ Here different deployments are used to avoid bewildered situations among the teams.‌ Lets say why Deployment. To clear understand lets get into a example.‌ An Organisation having a QA Team and Developer Team, both the teams will be running their work on same Websites. A changes made by developer team on a website will not be affecting the work done by the testing team website.There will two separate versions of website will be maintained.​ ![](https://gblobscdn.gitbook.com/assets%2F-MgdWk21zETVSCGfZEts%2F-Mgl-_81dDSSg5ka4-8W%2F-Mgl0LwVU45veaekM1--%2FDeployemnt.png?alt=media\&token=4edecba5-7a14-4044-810c-e6f71650ab68) ​ ​ --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.qatts.com/v-3.0/administration/deployment.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.