> 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/yoplanning-academy/yoplanning-au-quotidien/planning-et-indisponibilites-avec-yoplanning/choix-des-couleurs-au-planning.md).

# Choosing colors for the schedule

### Introduction

The "Schedule Color Picker" feature allows you to customize the display of different sessions and activities on your schedule using color codes. This customization helps to quickly identify sessions and their status, improving visual management.

### Access the feature

1. From your schedule, click on your profile icon at the top right.
2. Select “Preferences” from the drop-down menu.

### Set session colors

By default, colors are set per product. Here's how to customize colors:

#### Color per session

1. Access the product sheet of the session you wish to customize.
2. In the product description section, look for the color option.
3. Select the desired color from the color palette.
4. Save the changes.
5. You can do the same operation directly on a session if you want to give it a particular color relative to the product.

#### Color by number of participants

1. In the "Preferences" drop-down menu, in the "Display" section, choose the "Number of participants" option in "Session colors depend on".
2. Colors will be automatically assigned based on session fill rate.

#### Color by team

1. For users working with multiple teams, choose the "Team" option in "Session colors depend on".
2. Each team will have a specific color, making it easier to differentiate sessions according to their team membership.
3. This option is particularly useful in "All Teams" view mode.

### Usage tips and best practices

* **Visual Clarity**: Use contrasting colors for better visibility.
* **Consistency**: Maintain consistent color codes for the same session types to avoid confusion.

### Common Problems and Solutions

* **Problem:** Colors are not displaying correctly **Solution**: Make sure you have saved any changes in your session or display settings.
* **Problem:** Difficulty distinguishing certain colors **Solution**: Choose colors that are very distinct and avoid shades that are too similar. You can also increase the contrast of your screen for better visibility.
* **Issue:** Color settings are not syncing between different devices **Solution**: Make sure you are signed in to the same account on all devices and that the settings have been saved correctly on each of them.


---

# 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/yoplanning-academy/yoplanning-au-quotidien/planning-et-indisponibilites-avec-yoplanning/choix-des-couleurs-au-planning.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.
