> ## Documentation Index
> Fetch the complete documentation index at: https://university.triggr-app.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Change User Details
> Updates a user's job title, department and mobile phone in your client's Microsoft 365, or in Active Directory for an AD-synced account.
Change User Details updates a user's job title, department and mobile phone. Use it when someone changes role, moves team or gets a new number. Fill in only what's changing: a field left blank keeps its current value. It needs [Microsoft 365 connected](/core/get-started/connect-microsoft-365). Under GDAP, the client's relationship needs User Administrator (see [Recommended roles](/integrations/microsoft-graph/recommended-roles)). For a client that syncs on-premises Active Directory, it also needs the [desktop agent](/desktop-agent/overview).
## What the form asks
| Field | |
| - | - |
| User | Required, always on. The account to update, picked from the client's users |
| Job title | Optional by default. The new job title; leave it blank to keep the current one |
| Department | Optional by default. The new department; leave it blank to keep the current one |
| Mobile phone | Optional by default. The new mobile number; leave it blank to keep the current one |
| Reason / ticket reference | Optional by default. For your records and the approver; not sent to Microsoft |
## What it does
1. Creates a ticket in your PSA, if Ticketing is on.
2. Waits for approval, if Approval is Internal or External, or a conditional override matches.
3. Update Details: sets the job title, department and mobile phone you filled in on the user in the client's Microsoft Entra ID. Blank fields aren't changed.
For an AD-synced account on a client that syncs on-premises Active Directory, Set On-Prem Attributes runs instead: the desktop agent sets the same details on the user in Active Directory, then starts a delta sync if it runs on the Microsoft Entra Connect server. Cloud-only accounts on that client take Update Details. If the Active Directory change fails, the run stops with the error.
With Log actions to the ticket on, the ticket also gets a note when the run starts and when it completes.
## Configure it
Go to **Config** and click Change User Details.
| Setting | Where | What it does |
| - | - | - |
| Availability | Header | Internal only, Public form only, Internal + public or Disabled. List on homepage needs a public form. Base config only |
| User | Form config | Always on: the automation needs it |
| Job title, Department, Mobile phone | Form config | Hidden, Optional or Required. Hidden means the form never asks, so that detail is never changed. Required means every request must fill it in. Can differ per client |
| Reason / ticket reference | Form config | Hidden, Optional or Required. Can differ per client |
| Add field, Add section | Form config | Your own questions. They're saved with the request and can go in ticket templates, but aren't sent to Microsoft. Add client section asks one client only |
| Approval | Execution config | None runs on submit. Internal waits for a teammate or group; External waits for the client's approver, set on each client. Conditional overrides use a different approval when the answers match |
| Ticketing | Execution config | Create a PSA ticket for each run, with its type, priority, status, subject and body. Log actions to the ticket adds an internal or public note as the run starts and completes |
| User directory filters | Execution config | Which users the User picker lists: licensed, active, no guests, and not in the Entra roles you exclude (for example Global Administrator). Exclude specific users at a client's scope |
Approval, Ticketing and User directory filters are set on Base config and apply to every client unless you override them for one. For how Base config and client overrides work, see [How configuration works](/core/get-started/configure-user-onboarding#settings-for-each-client).
## Troubleshooting
The run form shows this when the client's GDAP relationship doesn't give Triggr a role that can edit users. Assign User Administrator to Triggr's security group in that relationship. See [Recommended roles](/integrations/microsoft-graph/recommended-roles).
Check User directory filters. By default the list leaves out unlicensed users, accounts whose sign-in is blocked and guests, as well as anyone in an Entra role you've excluded.
This ticket note means the desktop agent couldn't update the user in Active Directory. The note includes the error. Make the change in Active Directory, or fix the cause and run it again.
For an AD-synced account, Microsoft 365 picks up the change at the next Microsoft Entra Connect sync.
## Related
* [Workflow catalogue](/core/reference/workflow-catalogue)
* [Run a workflow](/core/use/run-a-workflow)
* [Executions](/core/use/executions)
* [User Onboarding](/core/workflows/user-onboarding), which sets a new starter's job title and department
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.