> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/api-reference/users.md).

# Users

Manage application users through the Built-in tools API.

Manage application users through the Built-in tools resource.

```
https://data.jetadmin.io/projects/{{project_id}}/prod/__jet_app__/models/users
```

Find the generated API under **Data → Users → API**. Send the Built-in tools static API token directly in the `Authorization` header.

### Endpoints

* [List users](/api-reference/users/list-users.md)
* [Create a user](/api-reference/users/create-a-user.md)
* [Retrieve a user](/api-reference/users/retrieve-a-user.md)
* [Update a user](/api-reference/users/update-a-user.md)
* [Delete a user](/api-reference/users/delete-a-user.md)

### User fields

Users have `uid`, `email`, `group`, and `date_add`, with nullable `first_name` and `last_name`. The `group` value is the related team's UID; use the [Teams API](/api-reference/teams.md) to find it.

Creating a user requires `email` and `group`. The supplied update schema accepts only `group`. Deletion returns HTTP 204 with an empty response body.

Lists support `page`, `_per_page`, and `_no_pagination`. See [Resources](/api-reference/resources.md) to reload the shared Built-in tools structure cache.


---

# 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.jetadmin.io/api-reference/users.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.