> For the complete documentation index, see [llms.txt](https://docs.lithnet.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lithnet.io/password-protection/help-and-support/faqs.md). # Frequently asked questions ## Can I apply the password filtering to only a specified group of users? Unfortunately not. The password filter applies to all users in the domain. A future version of Lithnet Password Protection is planned which will implement fine-grained password policies. ## Can users be shown a more informative message about why their password was rejected? Windows does not provide a native mechanism to report the reason why a password change was rejected. ## I've added a banned word, but passwords containing that word are still being accepted. Why? The banned word feature isn't designed to block strings of text. It's an intelligent filter designed to prevent users creating passwords based on simple words and common substitutions. It will prevent the creation of passwords that are susceptible to offline brute force attacks and password guessing techniques, while allowing users to create longer, more complex passwords and passphrases that may include those words. The password goes through a normalization process that removes common substitutions (e.g. "@" to "a", "1" to "i", etc) and then checks for the presence of the banned word. If the banned word is part of a longer password that has not been altered with common substitutions, it will not be blocked. For example, if "blue" is a banned word, "blue123" will be blocked, but "myfavoritecolorisblue" will not be blocked. If you need to block a string of text outright, use the regex policy to block that specific sequence of characters. You can read up on the specifics of how our [normalization algorithm works](/password-protection/advanced-help/normalization-rules.md). --- # 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://docs.lithnet.io/password-protection/help-and-support/faqs.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.