> For the complete documentation index, see [llms.txt](https://docs.welkinhealth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.welkinhealth.com/designer/version-and-configuration/multi-user-collaboration-in-designer.md).

# Multi-User Collaboration in Designer

## Overview

Designer supports multiple users working on the same environment's configuration. However, Designer does not sync draft state between users in real time: the draft you see in your browser reflects the state loaded when the page was opened. If a teammate makes changes in the same draft, your view may be out of date until you refresh the page. This page describes the recommended workflow to avoid version conflicts and lost work when several users collaborate in Designer.

## How Draft State Behaves with Multiple Users

* All users in the same environment work against the same draft on the server
* Each user's browser shows the draft state as of the moment the page was loaded
* Changes made by another user do **not** appear automatically — they appear after a page refresh
* A full logout/login is **not** required; a browser page refresh is enough to load the latest draft state

If users do not refresh, they may see different "versions" of the draft, and publishing from a stale view can result in incorrect version differences or loss of another user's recent changes.

## Recommended Workflow

### 1. Refresh the page before publishing

Always complete a full browser page refresh before publishing a draft. This loads any changes completed by other users, so the publish includes the actual latest state of the draft rather than a stale view. This is the single most important habit for avoiding lost work.

### 2. Coordinate before publishing

Confirm with other team members that no one is in the middle of edits before anyone publishes. Ideally, agree on who publishes and when — for example, designate one person as the publisher for a given working session.

### 3. Divide work by area

When possible, avoid having multiple people edit the same resources at the same time. Splitting work by configuration area (for example, one person works on CDTs while another works on Automations) reduces the chance of overlapping changes.

### 4. Review the Change Summary before publishing

After refreshing, review the Change Summary to verify the full set of changes about to be published — including changes made by teammates. If you see unexpected items, check with the team before proceeding.

## Quick Checklist Before Publishing

1. Refresh the browser page
2. Confirm no teammates are mid-edit
3. Review the Change Summary
4. Publish

## Related Pages

* [Change Summary and Version History](/designer/version-and-configuration/change-summary-and-version-history.md)
* [Export Designer Configuration](/designer/version-and-configuration/export-designer-configuration.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.welkinhealth.com/designer/version-and-configuration/multi-user-collaboration-in-designer.md?ask=<question>
```

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.