> 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-2-system-administrator-manual/menu_-_administration/application_settings_-_general.md).

# Application settings… - General

![](https://800956157-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvyGt5xgoAU3kZytuvW1J%2Fuploads%2Fgit-blob-091c18faddfaa94e192ff3c132d7416dc74b7b2a%2Fimage58.png?alt=media)

**Use pre-filled username and password**

For signing it is necessary to enter user’s name and password into a sign form. If this option is selected then the username and password of a logged-in Boomerang client is filled in by the system automatically.

**Revise password periodically**

When selected it forces a periodic password revision. The validity period is set in months.

**Block the user account after 3 incorrect login attempts**

When selected the user account is blocked after 3 incorrect login attempts. To unblock the account, a system administrator must generate a new password for the user.

**System name**

The system name is shown on top of the application window. It is also used in reports and emails sent from the system.

To change any setting, make the modification, click “Apply” and sign.


---

# 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-2-system-administrator-manual/menu_-_administration/application_settings_-_general.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.