> For the complete documentation index, see [llms.txt](https://help.docupilot.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.docupilot.app/collaborating-with-multiple-users/manage-and-delete-users.md). # Manage & delete users Change a user's role or delete users within a workspace ### Updating User roles To modify a user's role, navigate to **Settings > Users** section. Find the user whose role needs to be changed in the list of users and select a new role for that user in the role dropdown. When updating user roles within your workspace, it's important to understand who has the capability to make changes. * The Owner has full control and can change role of all users other then self * An Admin can perform following changes * Admin -> Manager * Admin -> Member * Manager -> Member * Member -> Manager * Member -> Admin * Manager -> Admin * A Manager has the capability to perform following changes: * Manager -> Member * Member -> Manager * A Member and Billing Manager has no control on user role assignments

### Deleting a user To remove a user from your workspace, navigate to the “**User Management**” section, select the desired user, and click on the **Delete** option. {% hint style="info" %} Note that only the Owner can perform this action, and once deleted, it cannot be undone or recovered. {% endhint %}

--- # 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://help.docupilot.app/collaborating-with-multiple-users/manage-and-delete-users.md?ask=&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.