> 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/definir-une-indisponibilite-pour-un-membre-de-lequipe/modifier-ou-supprimer-une-indisponibilite-dun-staff..md). # Modify or delete a staff member's unavailability. ### **Introduction** In the Yoplanning.pro application, managing staff unavailability is essential to ensure efficient and precise planning of your activities. However, it can happen that errors are made when entering these unavailabilities. This guide will explain how to delete unavailability for a staff member and what the limitations are for modifying these unavailability. ### **Access to unavailability management** 1. **Go to the main menu** located on the left side of your screen. 2. **Click on the "Unavailability" section** to open the list of unavailability entered for the entire team. ### **Delete an unavailability** It is important to note that **you cannot directly modify an unavailability**. The only option available is to delete the existing unavailability and then enter a new one if necessary. Here is how to proceed with the deletion: 1. **Filter the unavailability list** according to the staff whose unavailability you wish to remove. This will make it easier to find the specific entry you want to manage. 2. **Select the unavailability** you want to remove by checking the corresponding box. 3. **Use the delete option**. Once unavailability is selected, use the delete button or icon to remove the entry from the list. ### **Limitations** * **General type unavailabilities**, i.e. those which affect the total availability of staff for all teams, **cannot be modified by managers or team administrators** . In this case, the modification must be requested directly from the staff concerned. * This limitation ensures that overall outages, which could affect multiple teams or activities, are managed with direct communication to avoid any confusion or scheduling conflicts. ### **Advice and best practices** * **Communicate clearly** with the staff whose unavailability must be removed, especially if a new unavailability must be entered. This will help avoid mistakes and misunderstandings. * **Regularly check the unavailability** entered to ensure it is up to date and accurately reflects your team's availability. ### **Problem resolution** If you are having difficulty removing an outage, make sure you have the necessary rights to perform this action. If the problem persists, contact Yoplanning.pro technical support for assistance. This guide has provided you with the necessary steps to manage the removal of downtime in the Yoplanning.pro application, as well as important information regarding the limitations and best practices associated with this task. --- # 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/yoplanning-academy/yoplanning-au-quotidien/planning-et-indisponibilites-avec-yoplanning/definir-une-indisponibilite-pour-un-membre-de-lequipe/modifier-ou-supprimer-une-indisponibilite-dun-staff..md?ask=&goal= ``` `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.