> 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/open-user-dialog.md).

# Open user dialog

The **Open User Dialog** action node opens the built-in **Account Settings** dialog for the logged-in user. It is available in apps.

## Usage

Use it for a menu item or button such as *My account*. The dialog needs no setup and the action node has no settings.

The dialog has two sections:

* **Device Activity**: the devices that have signed in to the user's account and when they were last used. The user can sign out any other device from here.
* **Personal Info**: the user's name, email and phone number.

If a temporary drawer is open, it closes when the dialog opens. A responsive drawer also closes on small screens.

## Example

In the app bar, add an **Icon Button** with an account icon. In its **On Click** action, add **Open User Dialog**. Users can now check where they are signed in and sign out a lost phone without contacting an administrator.


---

# 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/open-user-dialog.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.
