> For the complete documentation index, see [llms.txt](https://apidocs.zerionsoftware.com/doc/iformbuilder-v81/llms.txt)

# Update a List of Users

> PUT /profiles/{profile_id}/users



## Servers
- https://api.iformbuilder.com/exzact/api/v81/[servername]: https://api.iformbuilder.com/exzact/api/v81/[servername]


## Authentication methods
- Oauth2


## Parameters
### Headers

- **Authorization** (string)
  e.g. Bearer {access_token}


### Path parameters

- **profile_id** (string)
  id of the profile


### Query parameters

- **fields** (string)
  extra information of each user on the list

- **limit** (number)
  maximum count of the user list

- **offset** (number)
  skip that many users before beginning to return

- **validate_grammar** (string)
  returns an error for incorrect field grammar when set to true


### Body: application/json (object)

- **id** (number)

- **password** (string)
  At least 8 characters (the minimum is configurable per server).
  Servers with password complexity enabled also require an uppercase letter,
  a lowercase letter, a number, and one of `` !@#$%^&*()-_=+~`,. ``. Servers that
  enforce password history reject a previously used password.
  ZIM-integrated servers also enforce ZIM's policy: at least 8 characters
  with an uppercase letter, a lowercase letter, and a number.
  A failing password is reported in that user's `error_message`, which names
  the rule it failed (ZIM's own error text on ZIM-integrated servers). The
  response is 400 if every user in the request fails, otherwise 207.

- **first_name** (string)

- **last_name** (string)

- **email** (string)

- **role** (string)
  must match "server", "company" or "basic"

  Only a Server Admin can set `server` or update a `server` user.
  On a role change, omitted `can_assign`, `can_edit_records` and `can_delete_records`
  reset to the new role's defaults. `can_manage_templates` and `can_generate_documents`
  keep their stored values.

- **can_form_edit** (boolean)

- **can_thunderplug_sync** (boolean)

- **can_assign** (boolean)
  Record Assignment. Company Admins, and Server Admins holding the company scope,
  always have it. Omitted, it keeps the stored value unless `role` changes to
  `basic`, which clears it. For a server-only user (server scope without the
  company scope) `true` changes nothing, as GET already reports every permission
  true for them, and `false` clears it.
  On a role change a `true` sent here is kept, so a client that demotes a user by
  editing their GET body (every flag `true` for an admin) MUST send `false`.
  On ZIM-integrated servers a grant made here survives detaching the ZIM
  Record Assignment policy, and `false` doesn't remove a grant that comes from
  that policy.
  Permission bits this endpoint has no field for are kept unless `role` changes.

- **can_edit_records** (boolean)
  Edit Records. Lets the user edit records on forms they can view.
  On ZIM-integrated servers the user's ZIM policies grant or revoke this permission,
  and replace a value sent here at the user's next sign-in.

- **can_delete_records** (boolean)
  Delete Records. Lets the user delete records on forms they can view.
  On ZIM-integrated servers the user's ZIM policies grant or revoke this permission,
  and replace a value sent here at the user's next sign-in.

- **can_manage_templates** (boolean)
  Manage Document Templates. Lets the user create, edit and delete document templates.
  On ZIM-integrated servers the user's ZIM policies grant or revoke this permission,
  and replace a value sent here at the user's next sign-in.

- **can_generate_documents** (boolean)
  Generate Documents. Lets the user generate documents from document templates.
  On ZIM-integrated servers the user's ZIM policies grant or revoke this permission,
  and replace a value sent here at the user's next sign-in.

- **is_locked** (boolean)
  Can only unlock by using false



## Responses
### 200
OK

#### Body: application/json (object)
- **id** (number)
  the updated user id



[Powered by Bump.sh](https://bump.sh)
