> For the complete documentation index, see [llms.txt](https://helpdocs.conducttr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocs.conducttr.com/feature-documentation/designing-and-running/publishing/live-vs-local-teams.md).

# Live vs local teams

When publishing an exercise, you have **2 options for teams uploads**:

<table><thead><tr><th width="237.111083984375">Option</th><th>Definition</th></tr></thead><tbody><tr><td>Live teams</td><td>These are the teams already uploaded to your space</td></tr><tr><td>Local teams</td><td>These are the exercise teams in the Editor</td></tr></tbody></table>

Your **live teams could be different from your exercise teams** (local teams) if you haven't uploaded them to the selected space.&#x20;

In the example below, the live and local teams don't align. This is because the teams from a different exercise or from an earlier upload are currently active in the selected space. To correct this, select `Upload exercise teams` to overwrite the live teams in the space.

<figure><img src="https://3476309720-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsNKxYbIPgfYmCR9EJgAu%2Fuploads%2FhCriR6kbwBJ0pkgsGpyo%2Flive%20v%20local.png?alt=media&amp;token=47ffdd4d-4be3-4453-b9eb-87dded4282d6" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
To find out about configuring exercise teams, visit the page below:
{% endhint %}

{% content-ref url="/pages/ezFsBUecds4TROGiLo7j" %}
[Setting up your teams table](/feature-documentation/designing-and-running/teams-roles-positions-and-groups/setting-up-your-teams-table.md)
{% endcontent-ref %}


---

# 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://helpdocs.conducttr.com/feature-documentation/designing-and-running/publishing/live-vs-local-teams.md?ask=<question>&goal=<user_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.