> For the complete documentation index, see [llms.txt](https://help.dscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.dscout.com/account-management/user-account-settings/password-expiration.md).

# Password expiration

The purpose of this document is to notify you of the preventative measures we're taking to protect your information. Reusing the same passwords and usernames on multiple websites can put your accounts at risk. Bad actors can steal lists of credentials and try them (at high speed, using automated bots) at thousands of sites on the Web, hoping to find opportunities to log in and exploit your information.

## What Dscout is doing

Dscout takes the protection of your information very seriously. As an extra precaution, on 2/24/2023 *we’re expiring all passwords.* All users with Dscout access will be logged out of their accounts. In order to log back in, you will need to reset your password by using the “forgot password” option on the Dscout login page. As of May 2024, we also require 2FA for all user accounts (Viewers excluded) who do not utilize SSO as their exclusive login option.

Please email our Support team (<support@dscout.com>) if you encounter any issues updating your password or accessing your account—our team will be happy to assist.


---

# 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.dscout.com/account-management/user-account-settings/password-expiration.md?ask=<question>&goal=<user_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.
