> For the complete documentation index, see [llms.txt](https://docs.cloudnotte.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cloudnotte.com/admin/users/staff-overview/how-to-delete-a-staff-on-cloudnotte.md).
# How to delete a staff on Cloudnotte
Staff View Button
Click on the staff button to get the staff's different profiles. You"ll then click on the search button to look for the exact staff you want to delete.
Staff profile
Click on the 3 dotted vertical icons at the right corner of your screen.
Click on Delete
You can decide to cancel or proceed with the delete action, if cancel it doesn't delete, If proceed the students record is automatically deleted
Note:\
If you encountered error while deleting a staff , you should check for the following:\
1\. Ensure your internet connection is active\
If the issue persist you can contact support: [hello@meghee.com](mail:hello@meghee.com)
---
# 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.cloudnotte.com/admin/users/staff-overview/how-to-delete-a-staff-on-cloudnotte.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.