> 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-parametrage/gestion-staffs/supprimer-un-staff-de-lequipe.md).

# Remove a staff member from the team

Effectively managing your team in Yoplanning.pro includes the ability to remove a staff member's access when necessary. Whether for administrative or personal reasons. This article will explain how to delete a staff securely, while preserving the integrity of your data.

**What is this feature for?**

Deleting a staff member from your team allows you to revoke this member's access to the Yoplanning.pro application. It is important to note that this action does not delete past data or your ability to view that data. You can re-invite the same staff at any time using their email address, and all previously established settings will be restored.

**Steps to delete a staff**

1. **Access the staff list**:
   * Open Yoplanning.pro and log in to your account.
   * In the navigation menu on the left, click **Administration** then select **Staff** to open the list of your team members.
2. **Find the staff to delete**:
   * Use the available filter to quickly find the staff concerned. You can filter by name, role, or any other relevant criteria.
3. **Remove staff access**:
   * Next to the name of the staff you want to remove, click on the **Three Little Dots** menu to open the advanced options.
   * Select **Remove access**. You will be asked for confirmation to ensure that this action is not accidental.
4. **Confirmation**:
   * Confirm the deletion. The staff will be immediately removed from your team on Yoplanning.pro and will lose all access to the system.

**Tips for use and best practices**

* **Check before deleting**: Make sure deleting staff is the right decision. Consider the implications for your daily operations and data management.
* **Inform the staff**: It is recommended to inform the staff of its deletion before proceeding, to avoid any confusion or misunderstanding.
* **Data retention**: Rest assured, deleting a staff will not affect the historical data or the reports in which they are involved.

**Common problems and solutions**

* **Unable to find staff**: Make sure you use the filters correctly. If the staff still does not appear, check if it has not already been deleted or if you have the necessary rights to perform this action.
* **Error deleting**: If an error occurs, check your internet connection and try again. If the problem persists, contact Yoplanning.pro technical support for assistance.

Deleting a staff is a sensitive feature that must be used judiciously. By following this guide, you will be able to manage this task securely and efficiently, while maintaining the integrity of your team management and associated data.


---

# 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-parametrage/gestion-staffs/supprimer-un-staff-de-lequipe.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.