Skip to main content

Reset a User's Password

Goal​

Give somebody a new password — because they forgot theirs, or because you have reason to believe the old one is no longer private.

Prerequisites​

  • You are signed in to the Admin Control Center as a platform administrator.
  • You have a way to hand the new password over. The platform sends no email.

Steps​

  1. Open the Users page from the left navigation.

  2. Tick the box beside the person. Reset password turns on once exactly one person is selected — a password belongs to one account, so the command acts on one.

  3. Select Reset password. A panel opens.

  4. Type the new password.

    The box has an eye button beside it. Select it to read back what you typed — you are about to pass this on to somebody, and seeing it is the only check that tells you what you are actually handing over.

  5. Select Save.

The password changes immediately.

What this does, and does not, do​

  • It takes effect at once. The next sign-in uses the new password; the old one stops working.
  • It signs the person out everywhere. Any session or refresh token issued under the old password stops being accepted. If you are resetting because a password leaked, that is the part that matters.
  • It sends nobody an email. There is no notification and no reset link — you hand the password over yourself.
  • It does not ask for the old password. You do not have it; that is the point. This is an administrative reset, not the person changing their own.
  • It does not force a change at next sign-in. The password you type is the password they use until somebody changes it again.

Choosing the password​

The same rules apply as when creating a user: at least 12 characters, and whatever else your deployment's password policy requires. A password that is refused here would have been refused on the create form too, and for the same reason — this route deliberately has no way around the policy.

Troubleshooting​

"Reset password" is greyed out. Nobody is selected, or more than one person is. Tick exactly one row.

The password was refused. It does not satisfy the password policy — most often it is too short. The message says which rule it failed.

The person still cannot sign in. Check you handed over the password you actually saved (use the eye button next time), and that they are typing the right email address. If they hold no roles they can still sign in — they will simply see nothing they may open, which is a different problem, and one the Roles page fixes.