> 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/appcademy/appfarm-fundamentals/user-handling-and-permissions/creating-users.md).

# Creating users

Using a dedicated action node in combination with the right permissions, client users can create additional users and assign roles from within an app.

{% embed url="<https://www.loom.com/share/562db988f28b4abf92f08b5555e7d08a>" %}

{% hint style="info" %}
**Tip**

You often need to create multiple users for yourself with various roles in order to test your apps thoroughly. Since each user requires a unique email address we recommend using *email aliases*.

Many email providers support aliases so that you can create unique email addresses which forward to your primary address.

In [Gmail/Google Workspace](https://support.google.com/a/users/answer/9308648?hl=en) for example, an email sent to <amanda+admin@3050labs.com> will be forwarded to <amanda@3050labs.com>.
{% endhint %}

## References

* [User handling](/how-to/authentication-and-access-control/add-users-assign-roles.md)
* [User accounts](/reference/security/users.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.appfarm.io/appcademy/appfarm-fundamentals/user-handling-and-permissions/creating-users.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.