> ## 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.
# Password Reset
> Sets a new temporary password on a user's Microsoft 365 account in your client's tenant, and can email it to an address or their manager.
Password Reset gives a user a new temporary password, shown to you once and, if you choose, emailed to an address or their manager. Use it when someone's forgotten their password or a password needs changing. It needs [Microsoft 365 connected](/core/get-started/connect-microsoft-365), and the [desktop agent](/desktop-agent/overview) for a client that syncs on-premises Active Directory.
## What the form asks
| Field | |
| - | - |
| User | Required, always on. The account to reset, picked from the client's users |
| Require a change at next sign-in? | Always on. Starts on No; choose Yes to make the user set their own password when they next sign in |
| Send the new password to | Required, always on. A specific email address, Their manager, or Don't send — I'll hand it over |
| Email address | Required when you choose A specific email address |
| 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.
3. Reset Password: sets a generated temporary password, such as `Swift-Harbor-4826!`, in the client's Microsoft 365. For an AD-synced user on a client that syncs on-premises AD, Reset On-Prem Password sets it in Active Directory through the desktop agent instead.
4. Send Password: emails the password to the address or manager from the form, with the subject "Your password has been reset". It's skipped if you chose Don't send — I'll hand it over.
With Log actions to the ticket on, the ticket also gets a note when the run starts, after Reset Password and Send Password, and when the run completes. The notes don't include the password.
The run result shows the temporary password once, with **Copy**, even when the run is waiting for approval; it's set once the request is approved. Someone who submits Password Reset on a public form never sees it, so it reaches only the recipient the form names.
## Configure it
Go to **Config** and click Password Reset.
| 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, Require a change at next sign-in?, Send the new password to, Email address | Form config | Always on: the automation needs them. Each run chooses who gets the password, so there's no Credential delivery card |
| 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 | Approval | 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 | Ticketing | 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 each action completes |
| User directory filters | User directory filters | 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 user has no manager in Microsoft 365. Set their manager in the client's tenant, or choose **A specific email address** on the form. The same fix applies to "…'s manager has no email address in Microsoft 365".
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.
## Related
* [Workflow catalogue](/core/reference/workflow-catalogue)
* [Run a workflow](/core/use/run-a-workflow)
* [User Offboarding](/core/workflows/user-offboarding), which can also reset a leaver's password
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.