Stay organized with collections
Save and categorize content based on your preferences.
Updates a user using patch semantics. The update method should be used instead, because it also supports patch semantics and has better performance. If you're mapping an external identity to a Google identity, use the update method instead of the patch method.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-08-22 UTC."],[[["`patch` updates a user using patch semantics, but the `update` method is recommended for better performance and support for patch semantics, especially for mapping external identities."],["When dealing with repeated object fields like addresses or phone numbers, the `update` method should be used instead of `patch` for effective clearing."],["This API endpoint utilizes an HTTP PATCH request to `https://admin.googleapis.com/admin/directory/v1/users/{userKey}`, allowing modification of user data using patch semantics."],["To use this endpoint, you'll need to include the user's primary email address, alias email address, or unique user ID as the `userKey` in the request path."],["Appropriate authorization with the `https://www.googleapis.com/auth/admin.directory.user` scope is necessary to access and modify user data via this API."]]],[]]
