> 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/advanced-help/configuring-a-points-based-complexity-policy.md).

# Configuring a points based complexity policy

The password filter policy allows you to require that passwords meet a certain number of points in order to be approved by the filter.

You first select the minimum number of points required for the password to be approved, and then determine how the points are calculated. The following categories can be used to assign points;

* Each character used
* Each number used
* Each lower case letter used
* Each upper case letter used
* Each symbol used
* Use of at least one number
* Use of at least one symbol
* Use of at least one uppercase letter
* Use of at least one lowercase letter

Given the following points allocations, we can see what how many points would be allocated to each password

| Rule                                 | points |
| ------------------------------------ | ------ |
| Each character used                  | 1      |
| Each number used                     | 1      |
| Each lower case letter used          | 2      |
| Each upper case letter used          | 5      |
| Each symbol used                     | 2      |
| Use of at least one number           | 1      |
| Use of at least one symbol           | 5      |
| Use of at least one uppercase letter | 1      |
| Use of at least one lowercase letter | 1      |

### P\@ssword1!

| Rule                                 | points |
| ------------------------------------ | ------ |
| Each character used                  | 10     |
| Each number used                     | 1      |
| Each lower case letter used          | 12     |
| Each upper case letter used          | 5      |
| Each symbol used                     | 4      |
| Use of at least one number           | 1      |
| Use of at least one symbol           | 5      |
| Use of at least one uppercase letter | 1      |
| Use of at least one lowercase letter | 1      |
| Total                                | 40     |


---

# 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/advanced-help/configuring-a-points-based-complexity-policy.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.