> 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-generale/pourquoi-les-sessions-sur-mon-planning-sont-elles-estompees.md).

# Why are the sessions on my schedule faded?

### Introduction

If some sessions appear dimmed on your **Yoplanning** schedule, this is usually due to enabled team filters. This behavior is intended to make schedules easier to read and organize by highlighting certain sessions based on the selected context. Here's how to identify and adjust these settings for optimal display.

### Checking and managing filters

#### **1. Check team filters**

* Go to **Filter Management** at the top right of your schedule.
* Make sure your **context selector** is configured correctly.

#### **2. Understand how filters work**

* If the **context is set to "All Teams"**, you will view the schedules of all the teams you belong to.
* If you select a **specific team**, the sessions of other teams will appear **dimmed** to highlight those of the chosen team.

#### **3. Change the context to avoid faded sessions**

If you prefer to display only the sessions of your active team without seeing the others in the background:

* Change the context by selecting **"Current Team"** from the left menu.

### Conclusion

Faded sessions appear on your schedule as a feature designed to improve the readability of multi-team schedules. By adjusting the **team filters** and **display context**, you can customize your view for better session management.


---

# 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://docs.yoplanning.support/en/faq/faq-generale/pourquoi-les-sessions-sur-mon-planning-sont-elles-estompees.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.