> For the complete documentation index, see [llms.txt](https://support.emsigner.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.emsigner.com/administrator-settings/admin-settings/password-settings.md).

# Password Settings

**Step 1:** Login to emSigner Super Admin account. Click on ‘Settings’ tab to open the Admin Settings. Click on ‘***Password Settings***’ below Admin Settings

<figure><img src="/files/9jWEvw7wRmXHHU37bZwu" alt=""><figcaption><p>Password Settings under Admin Settings</p></figcaption></figure>

**Step 2**: You can define your password policy for your organization here, by setting the number of days for Password aging, the complexity of characters in the password, the Number of old passwords, and incorrect attempts. Once you have defined the policy, click on “***Apply***” to save the changes.

<figure><img src="/files/3NbMLORELSbUqySPzYdp" alt=""><figcaption><p>Configuring Password Settings</p></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://support.emsigner.com/administrator-settings/admin-settings/password-settings.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.