> For the complete documentation index, see [llms.txt](https://docs.yoplanning.support/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yoplanning.support/en/faq/faq-des-staffs/travailler-dans-plusieurs-structures-differentes-avec-yoplanning.md).

# Travailler dans Plusieurs Structures Différentes avec Yoplanning

Yoplanning is designed to be a collaborative and flexible tool, allowing users to participate in several teams or structures simultaneously. Here's a guide to navigating this feature.

#### What is this feature for?

This feature allows users to collaborate with different teams or structures without needing separate accounts for each organization. It is particularly useful for professionals working with several entities who use Yoplanning to manage their activities.

#### How to use this feature

1. **Team Invitation:** Make sure to use the same email for all invitations to the Teams you want to collaborate with. This allows you to centralize your commitments in a single Yoplanning account.
2. **Access to Teams:** Once invited by a Team, the name of this team will appear in your menu on the left of the Yoplanning interface. You can display the list of all the Teams to which you belong by clicking on the name of the team located at the top left of your screen.
3. **Viewing Assigned Sessions:** By clicking on the sessions assigned to you, you will be able to see the name of the team that assigned you to this session. This helps to quickly identify which Team each session is scheduled for.
4. **Using Filters:** A filter button, located at the top right, allows you to filter and display information specific to each Team. This simplifies the management of your tasks and responsibilities for each structure.
5. **Unavailability Management:** When creating unavailability, pay attention to the name of the team concerned. This is crucial to ensure that you are marked as unavailable for one team while remaining available to others.

#### Tips for Use and Best Practices

* **Email Uniformity:** Make sure to systematically use the same email for all your collaborations. This ensures smooth management of your multiple commitments.
* **Attentive Management of Unavailability:** Be precise when you define unavailability, by correctly selecting the team concerned to avoid blocking reservations everywhere if it is not necessary.
* **Exploit Filters:** Actively use filters to navigate between different teams. This will help you stay organized and prioritize your tasks efficiently.

#### Troubleshooting Common Problems

* **Incorrect Unavailability:** If you accidentally declared yourself unavailable for the wrong Team, return to the unavailability section and delete your selection to correct the error.
* **Team Display Issues:** If a team you were invited to does not appear, first check that you used the correct email for the invitation. If the problem persists, contact the team administrator to verify the invitation.

By following these steps and tips, you will be able to effectively collaborate with several teams or structures within Yoplanning, thus maximizing your productivity and flexibility.


---

# 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.yoplanning.support/en/faq/faq-des-staffs/travailler-dans-plusieurs-structures-differentes-avec-yoplanning.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.