> For the complete documentation index, see [llms.txt](https://docs.bossithq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bossithq.com/users-and-access/disabling-a-user.md).

# Disabling a User

#### In the Admin Portal:

1. Log in to the [**Admin Portal**](https://admin.gobossit.com/) and navigate to **Workforce > Users.**
2. Find the user you want to disable and untick **Active?** box.

#### In the POS:

1. In the POS, click on the **Settings** icon.
2. &#x20;Navigate to **Users Management**
3. Disable toggle for the staff member you want to disable.

## Disabling vs Deleting a User

While the system offers an option to delete a user, **we do not recommend using it**. Deleting a user removes their profile, which means, any past records linked to that user will show as “Unknown”, making it difficult to track historical data accurately.

{% hint style="success" %}
**Best Practice:**

Instead of deleting, we strongly recommend disabling the user. Disabling preserves all their past activity and records.
{% 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://docs.bossithq.com/users-and-access/disabling-a-user.md?ask=<question>&goal=<user_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.
