---
title: "Update user information using userID"
method: PATCH
path: "/usermanagement/v1/users/{userID}"
tags: ["User Management"]
---

# Update user information using userID

`PATCH /usermanagement/v1/users/{userID}`

## Request

- Base URL: `https://apis.druva.com/insync`
- URL: `https://apis.druva.com/insync/usermanagement/v1/users/{userID}`
- Auth: API key in header `Authorization`

Use this API to update username, profile, and storage region of an existing user.

## Path parameters

- `userID` integer, required

## Request body

- object: Specify the new value only for those parameters that you want to update for a user in Druva inSync.
  - `userName` string: Specify the new username for the user.
  - `profileID` integer: Specify the ID of the new profile that you want to associate with the user account. The new profile settings are applied to the user account in the next backup cycle.Get the profile ID using the 'List all profiles' API. :fa-info-circle: If you are changing user's profile to a profile where the Privacy Settings conflicts with the Privacy Settings in the old profile, which may result in administrators getting an unintentional access to the user's data, inSync does not allow you to update the profile. In such a case, you must request the inSync user to allow the inSync administrators to access their backed up data (setting on inSync Client) and try again.
  - `storageID` integer: Specify the ID of the new storage that you want to associate with the user account.Get the storage ID using the 'List all storages' API. After you change the user's storage: 1)User data is backed up to the new storage. 2)Snapshots on the old storage are retained and compacted following the retention policy. 3) User can restore data from snapshots saved on old as well as the new storage.

## Response `200`

OK

- UserCreate
  - `userID` integer: The unique id of the user in Druva inSync. Example - 1
  - `userName` string: The user name of the user in Druva inSync. Example - Ernie Carter
  - `emailID` string: The email address of the user. Example - ernie.carter@druva.com
  - `status` 'active' | 'preserved': The status of the user account. Example - active
  - `profileID` integer: The profile ID of the profile associated with the user. Example - 1
  - `storageID` integer: The storage ID of the storage associated with the user. Example - 1
  - `quota` string: The storage quota assigned to the user in inSync. Example - 50 GB
  - `quotaInBytes` integer: The storage quota (in bytes) assigned to the user in inSync. Example - 53687091200
  - `addedOn` string, date-time: The date on which the user was added in inSync. Example - 2019-10-25T00:00:00Z
  - `privacySettingsEnabled` string: Displays the status of the privacy setting of the user. If the value returned is True, privacy setting is enabled by the user. If the value returned is False, privacy settings is not set or user has allowed admin access to their data.
  - `ldapGUID` boolean: The AD or LDAP object GUID of the user in a hex string format. Example: B1C47201C67910458867BA19982E353E. The ldapGUID displays objectGUID if the user is imported from AD and displays entryUUID if imported from LDAP.
  - `additionalProperties` object: Contains the two keys of userIdentifierCustomAttribute and userIdentifierCustomAttributeValue if the User-Identifier Custom Attribute feature is enabled for the account and the administrator has opted to display it on the inSync UI. This field remains empty if the administrator has opted to hide the User-Identifier Custom Attribute.

## Other responses

- `400`: Bad Request
- `401`: The request did not include an authentication token or an expired authentication token was supplied.
- `403`: Access denied: Insufficient permissions. User requires specific access rights and minimum permissions. Details: https://help.druva.com/en/articles/15069296
- `404`: The requested resource was not found.
- `422`: The request was well-formed but was not processed due to semantic errors.
- `500`: The request was not processed due to an internal error in inSync Cloud.
- `501`: Requested HTTP method is not implemented.

---

[API](https://skmtc.dev/druva/apis/insync-cloud.md) - [All operations](https://skmtc.dev/druva/apis/insync-cloud/llms.txt) - [OpenAPI document](https://skmtc.dev/druva/apis/insync-cloud/revisions/a0ce6d05033c?raw)