> For the complete documentation index, see [llms.txt](https://guides.noloco.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.noloco.io/users-and-permissions/offboarding-users.md). # Offboarding Users Deactivate user accounts without losing their data When someone leaves your organisation, you can deactivate their account in your Noloco app to prevent them from logging into it. Deactivating their account like this rather than deleting it will preserve their user record so you can still see their dat,a including comments or any records related to their user. ## Deactivating a user To deactivate an account, go to your Users Table on the left sidebar or click here: , navigate to the user you want to deactivate, and select "Deactivate this user" in the popover for their record.

You will then see a modal where you will confirm this choice.

You will then see that the user has been deactivated in your User Table. Hovering over the Deactivated badge will tell you when the deactivation was done.

## Reactivating a user At any point after offboarding a user by deactivating their account you can reactivate them to allow them to use your app again. Simply go back to the same popover on the User Table and this time select "Reactivate this user".

You will be shown a similar modal to explicitly confirm your choice, after which the user will regain access to your app.

--- # 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://guides.noloco.io/users-and-permissions/offboarding-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.