> For the complete documentation index, see [llms.txt](https://docs.appfarm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appfarm.io/library/action-nodes/delete-user-account.md).
# Delete user account
The Delete user account action node removes a [user](/reference/security/users.md) from the solution.
## Usage
This action node is used when you would like client users to be able to delete other users in a solution. For example, a client user with a custom *Administrator* role may be granted the permission to remove other users.
When the action node successfully completes, the User object is immediately removed from the database.
{% hint style="warning" %}
**Important**
* A user cannot delete themselves.
* The user running this action node must have a role with the appropriate permissions to delete a user and remove any assigned roles. Read more under [Users](/reference/security/users.md#permissions).
* The appropriate user account manipulation properties must be enabled for the relevant [environment](/reference/configuration/environments.md#user-account-manipulation).
{% endhint %}
## Properties
Property
Description
User Account
The data source containing the User object to delete.
---
# 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.appfarm.io/library/action-nodes/delete-user-account.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.