Actions27
- Administration Management Actions
- Asset Management Actions
- Assistance Management Actions
- Management Actions
- Other Action Actions
- Setup Management Actions
- Tool Management Actions
Administration Management → Update a User
AI-generatedSummary
Updates an existing GLPI user via PUT /api.php/v2.1/Administration/User/{itemId}. The request payload includes login name, first name, email (added to User Emails), active status (1/0 only when explicitly set), and default entity ID (only when non-zero). Password is sent only when 'Send Email for Password' is disabled; otherwise GLPI triggers a password-reset email. Optional collection fields—Cell Phone, Last Name, Phone, Profile ID, and Recursive—are mapped to the API payload when provided.
Inputs
- User ID (required) — ID of the user to update. Drives the PUT endpoint path.
- Login — Login of the user. Included in the payload when provided.
- First Name — First name of the user. Included when provided.
- Email — Email of the user; added to User Emails array when provided.
- Active — Whether the user is active. Converted to 1/0; only sent when explicitly set per source logic.
- Default Entity ID — ID of the default entity; only included when non-zero.
- Send Email for Password — Boolean, default true. When true, no password included in request; GLPI sends a password-reset email. When false, the 'Password' field must be provided.
- Password — Password for the user. Only included when 'Send Email for Password' is false and a value is provided.
- Confirm Password — Confirm the password. Only shown/processed when 'Send Email for Password' is false.
- Options (Cell Phone, Last Name, Phone, Profile ID, Recursive) — Collection of optional fields. Each is mapped to the API payload only when provided: Cell Phone (mobile), Last Name (realname), Phone (phone), Profile ID (profiles_id), Recursive (is_recursive).
Output shape
The GLPI API response body as JSON, returned on the node's main connection.
No additional side effects beyond the API PUT request.