---
title: "Creating a new App User"
method: POST
path: "/v1/projects/{projectId}/app-users"
tags: ["App Users"]
---

# Creating a new App User

`POST /v1/projects/{projectId}/app-users`

The only information required to create a new `App User` is its `displayName` (this is called "Nickname" in the administrative panel).

When an App User is created, they are assigned no rights. They will be able to authenticate and list forms on a mobile client, but the form list will be empty, as the list only includes Forms that the App User has read access to. Once an App User is created, you'll likely wish to use the [Form Assignments resource](/central-api-form-management/#form-assignments) to actually assign the `app-user` role to them for the Forms you wish.

You may also optionally provide a `properties` object to set pre-registered [Actor Property](/central-api-accounts-and-users/#actor-properties) values on the App User at creation time.

## Path parameters

- `projectId` number, required

## Response `200`

OK

- object
  - `createdAt` string, required — ISO date format
  - `displayName` string, required — All `Actor`s, regardless of type, have a display name
  - `id` number, required
  - `type` 'user' | 'field_key' | 'public_link' | 'singleUse', required — the Type of this Actor; typically this will be `user`.
  - `updatedAt` string — ISO date format
  - `deletedAt` string — ISO date format
  - `token` string — If present, this is the Token that can be used to authenticate a request as this `App User`. If not present, this `App User`'s access has been revoked.
  - `projectId` number, required — The ID of the `Project` that this `App User` is bound to.

## Other responses

- `400` — Bad Request

---

[API](https://skmtc.net/getodk/apis/odk-central-api.md) · [All operations](https://skmtc.net/getodk/apis/odk-central-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/getodk/odk-central-api/versions/d8f5a0886a8b/schema)