# Team Management
### Working as a Team
The Team function in Depence is designed to allow multiple show programmers to work on different shows within the same project at the same time.
In Depence, these show programmers are called **Choreographers**. Each Choreographer has their own dedicated workspace inside the project. This allows every team member to work independently on their own scenes, sequences, and show content without directly changing the work of others.
This function is especially useful for larger projects where multiple shows need to be programmed for the same installation. The basic project, including the patch, hardware configuration, fixtures, media, network settings, and other shared project data, is prepared centrally and then distributed to all Choreographers.\
\
### Preparing the Project
Before a project is distributed to multiple Choreographers, a complete and clean main version of the project must first be created.
This includes in particular:
* the complete patch
* all required fixtures
* the hardware and network configuration
* all required global settings
* shared scenes or content
* all Choreographers created in the Team Management
The Team Management can be found in the main menu under:
{% hint style="info" %}
**File → Team → Team Manager**
{% endhint %}
All team members are created once in the Team Manager. This preparation should be done on the main system, meaning the computer from which the project copies for the individual Choreographers will later be created.
### The Public Workspace
Every Team project automatically contains a Choreographer named:
**Public Workspace**
This workspace is always present and cannot be deleted.
The Public Workspace is intended for shared content that can be used by all team members. For example, general scenes, base effects, or prepared content required for multiple shows can be stored here.
However, this is important:
Changes in the Public Workspace can affect all Choreographers and their shows. If scenes are changed or deleted here, this may affect existing shows created by other team members.
For this reason, the Public Workspace should only be modified with great care. Once the project has been distributed to the individual Choreographers, changes in the Public Workspace should only be made after consultation with all team members.
### Creating Choreographers
In addition to the Public Workspace, all participating Choreographers are created in the Team Manager.
Each Choreographer receives their own workspace. In this workspace, they can later create their own scenes and shows. Only content created inside this dedicated Choreographer workspace can later be exported and imported back into the main project.
After all team members have been created and the project has been fully prepared, the complete project folder is copied and distributed to all Choreographers.
Each Choreographer then works locally on their own PC with their own copy of the project.
### Logging in as a Choreographer
After a Choreographer has received their project copy, they must log into the project with their own user.
This is done via:
{% hint style="info" %}
**File → Team → Change current User**
{% endhint %}
After logging in, the Choreographer is working inside their own workspace.
At the top of the Repository, there is a selection box. Here, the user can switch between the **Public Workspace** and their own Choreographer workspace.
The Choreographer should now work exclusively in their own workspace.
### Working in Your Own Workspace
All scenes, sequences, and shows that a Choreographer wants to return to the main project later must be created in their own workspace.
Only this data can later be exported cleanly and imported into the main instance.
The Public Workspace should no longer be modified on the individual Choreographer systems. Content in the Public Workspace only serves as a shared basis there. Changes made to the Public Workspace on a Choreographer PC cannot later be exported back and merged into the main project.
This means:
After the project copies have been distributed, the Public Workspace should be treated only as a shared reference. The actual work of each Choreographer must take place in their own workspace.
### Exporting Choreographer Data
Once a Choreographer has completed their work, their show data can be exported.
The Export function can be found under:
{% hint style="info" %}
**File → Team → Team Manager**
{% endhint %}
There, the Choreographer selects their own name and uses the Export function.
This creates a separate export file containing their own Choreographer data. This file can then be passed on to the person managing the main project.
### Importing into the Main Project
On the main system, the export files from the individual Choreographers are imported back into the main instance.
This function can also be found under:
{% hint style="info" %}
**File → Team → Team Manager**
{% endhint %}
The respective Choreographer file is imported using the Import function.
After the import, the shows and scenes of this Choreographer are available in the main project and can be combined with the work of the other Choreographers.
### Important Note When Importing
{% hint style="danger" %}
When importing a Choreographer file, the old data of this Choreographer on the main system will be overwritten.
{% endhint %}
This means:
If a Choreographer has already been imported once and is imported again later, the new import replaces the previous data of this Choreographer in the main project.
Therefore, before each import, make sure that the correct export file is being used. It is also recommended to create a backup copy of the main project before performing larger import operations.
### Recommended Workflow
A typical team workflow looks like this:
1. The main project is fully prepared.
2. All Choreographers are created in the Team Manager.
3. Shared scenes are created in the Public Workspace.
4. The project folder is copied and distributed to all Choreographers.
5. Each Choreographer logs in with their own name via **Change current User**.
6. Each Choreographer works exclusively in their own workspace.
7. After programming is complete, each Choreographer exports their data.
8. The export files are imported back into the main system.
9. The individual shows are combined in the main instance.
### Summary
Team Management in Depence makes it possible to efficiently divide larger projects between multiple show programmers. The Public Workspace serves as a shared area for general content, while each Choreographer works in their own dedicated workspace.
The key to a clean workflow is that, after the project has been distributed, no further changes are made to the Public Workspace on the individual Choreographer systems. All exportable content must be created inside the respective Choreographer workspace.
By exporting and importing the individual Choreographer data, the shows can later be merged back into the main project. This keeps the project structured, traceable, and controlled, even when several programmers are involved.
---
# 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://help.depence.com/depence-show-and-animation/depence-repository/depence-team-management.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.