> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-heartcore/getting-started/deployment-workflow/structure-deployment.md).
# Structure deployments
Structure changes like new and/or updated Document Types need to be deployed through environments using the Project View in the Cloud Portal.
In the screenshot above, changes made on a Development environment are ready to be deployed to the Live environment, as indicated by the blue button: "*Deploy changes to Live*". Had there been a Staging environment on the project, the changes would first be sent to the Staging and then opened up for the option to deploy from Staging to Live.
A deployment from one environment (source) to another (target) goes through the following steps:
1. The target environment is checked for changes
2. If changes are found, these are pulled down and merged into the source environment
3. The changes in the source environment are then pushed to the target environment
This process might take a few minutes, depending on the amount of changes being deployed.
Once your structure has been deployed, it will be possible to transfer your content and media as well. This is done from the Umbraco Backoffice - read more about this in the [Content transfer/restore article](/umbraco-heartcore/getting-started/deployment-workflow/content-transfer.md).
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.umbraco.com/umbraco-heartcore/getting-started/deployment-workflow/structure-deployment.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
