> For the complete documentation index, see [llms.txt](https://docs.snowddl.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snowddl.com/guides/other-guides/team-workflow.md).

# Team workflow

{% hint style="info" %}
This page will be updated with more detailed information soon. Please stay tuned!
{% endhint %}

![](/files/4gIHSCJXnWUfmsXBguH6)

The intended setup and workflow for data engineering team using SnowDDL is the following:

1. Create a separate Snowflake account for development purposes. You may do it using [CREATE ACCOUNT](https://docs.snowflake.com/en/sql-reference/sql/create-account.html) and "organizations" feature.
2. Create an initial SnowDDL configuration, keep it in Git or another version control system.
3. When developer starts to work on new ticket, he or she creates a new branch, pulls config with latest changes and creates a separate "environment" in DEV Snowflake account using SnowDDL with [env prefix](/guides/other-guides/env-prefix.md). "Environment" can be destroyed and fully re-created at any moment.
4. When developer finishes coding, he or she pushes the code and sends it for review. Reviewer validates changes in config and approves or declines it.
5. All approved branches are merged into single "release" branch and automatically tested in a separate "environment" on the same DEV Snowflake account. This step is necessary to make sure that changes from multiple different branches are compatible with each other.
6. If "release" branch test was successful, config can now be deployed to production. SnowDDL should apply config to PROD Snowflake account without [env prefix](/guides/other-guides/env-prefix.md).
7. "Safe" changes are applied automatically. "Unsafe" changes are reviewed by release engineer once again and applied manually.

\---

This workflow provides the robust, flexible and controlled release cycle. Developers have their own personal copy of DEV environment. Release branches are always tested before deployment. The process of rolling out config changes is as "safe" or "unsafe" as you want it to be. 


---

# 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.snowddl.com/guides/other-guides/team-workflow.md?ask=<question>&goal=<endgoal>
```

`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.