> For the complete documentation index, see [llms.txt](https://docs.novacura.com/flow-connect/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.novacura.com/flow-connect/working-with-connect/deploy/environments.md). # Environments There are three types of environments utilized in the application development process. ### Development Firstly, we have the Development environment, which serves as the platform where we develop and debug our applications. In this environment, only Hub admins have permission to run applications. ### Test Following the development phase, applications progress to the Test environment. Here, applications are deployed from Development and undergo thorough verification by Quality Assurance (QA) teams and/or a limited set of users. This ensures that the applications are functioning correctly and meeting specified requirements before advancing further. Only users that have been granted end user permissions can run applications in Test environments. ### Production Finally, once applications have been verified in the Test environment, they are deployed to the Production environment. In Production, these verified applications are made available to end users for regular use. Additionally, it's worth noting that each environment has its own specific connector configurations tailored to its respective needs and functionalities, ensuring seamless integration and operation within each stage of the development lifecycle. Only users that have been granted end user permissions can run applications in Production environments. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://docs.novacura.com/flow-connect/working-with-connect/deploy/environments.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.