> For the complete documentation index, see [llms.txt](https://help.boomerang3.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.boomerang3.com/boomerang-3-domain-administrator-manual/admin/users/edit-user/set-pin-for-a-user.md).
# Set PIN for a user
A user may sign using a PIN instead of a password. A PIN consists of 4 to 6 digits.
The PIN can be used only if PIN usage is enabled in [System Group Settings](/boomerang-3-domain-administrator-manual/admin/settings/settings__system_group_settings.md).
The PIN can be set and enabled by a user as described in [Set PIN](/boomerang-3-domain-administrator-manual/dashboard/profile_settings_and_logout/set-pin.md).
It can be also done by an admin in user settings.
To set it up, open the user for edition.
1. Click the Edit  icon to edit the user settings as described in [Edit user](/boomerang-3-domain-administrator-manual/admin/users/edit-user.md).
2. Click “SET PIN” button at the bottom of the form.
3. Enter PIN twice.
4. Click “SAVE” and sign.
5. A confirmation is displayed.
6. After PIN is set, a checkbox “Use PIN for signing” is activated. Check it to use PIN.
7. Click “NEXT” to go to groups and alarm groups selection, click “SAVE” and sign to activate PIN usage. A confirmation is displayed.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.boomerang3.com/boomerang-3-domain-administrator-manual/admin/users/edit-user/set-pin-for-a-user.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
