> 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/set-user-account-image.md).

# Set user account image

The Set user account image action node triggers a file upload dialog for a [user](/reference/security/users.md) to add or update their own profile image.

## Usage

This action node is useful when you would like client users to upload their own profile images. You can then display user avatars in the UI, for example to show a picture of the user who is responsible for a specific customer or project.

The URL of the image is stored in the **Profile Image** property of their User object. When an image has been uploaded, the **Profile Image Exists** property on their User object will be `true`.

Once an image is uploaded, the User object is immediately updated in the database. It is not necessary to persist any changes.

{% hint style="warning" %}
**Important**

* Set user account image is considered to be an update to a user account, and the logged-in user must have a Role membership allowing update of user accounts.
* The appropriate user account manipulation properties must be enabled for the relevant [environment](/reference/configuration/environments.md#user-account-manipulation).
  {% endhint %}

## Properties

<table><thead><tr><th width="241">Property</th><th>Description</th></tr></thead><tbody><tr><td><strong>Clear Image</strong></td><td>Do not trigger the file upload dialog and instead clear the existing image. The <strong>Profile Image Exists</strong> property on the User object will become <code>false</code>.</td></tr><tr><td><strong>Throw Cancel Exception</strong></td><td>Throw a exception if the user cancels the file upload dialog and does not upload an image. The exception can be caught using a <a href="/library/action-nodes/catch-exception.md">Catch exception action node</a>.</td></tr></tbody></table>


---

# 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/set-user-account-image.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.