> 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/channels/session-vs-team.md).
# Session vs Team
{% hint style="info" %}
If in doubt, use Session setting which is the default.
{% endhint %}
Under `Configuration` > `Channels`, designers have the option to toggle between session or team settings for certain channels.
## Why is there a Session vs Team setting?
In some circumstances you may wish to **run the same exercise in parallel for multiple teams** and hence be able to compare team performance. This is when a team is often better described as a *syndicate* - each team has the same make-up of participants.
The Team setting, available on some channels, puts each team in their own information bubble meaning that although an inject will publish to all teams, an interaction with the content will only be seen by those in the same team as the participant interacting.
Do **not** use the team setting if your teams are "legal", "HR", "IT" etc as these are not syndicates and the teams likely need to share the same information (hence stick with Session setting).
Note that Pattern of Life stax, once published, can be edited by the Facilitator to send to a particular team - hence allowing the Facilitator to control the information published to a particular syndicate.
In summary:
* **Session** - all players share the same information space
* **Team** - players in the same team share the same information space (which could be different for other teams)
{% hint style="info" %}
To learn about setting up 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/channels/session-vs-team.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.
