> For the complete documentation index, see [llms.txt](https://docs.infraon.io/infinity/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infraon.io/infinity/user-guide/infraon-configuration/general-settings.md).

# General Settings

The general settings module is a part of Infraon Configuration and is accessible by administrators and other users authorized by administrators.&#x20;

This module of Infraon consists of three additional modules. They are:&#x20;

* **Audits:**  Infraon monitors and records every user's actions. Only the administrator can access these audits.&#x20;
* **Business Hours:** Configure business hours to control SLAs and better efficient work allocation.&#x20;
* **Tag Management:**  Tagging is a way of grouping assets, users, etc. Tags can be applied to multiple categories across Infraon.&#x20;
* **Template: L**ets administrators create predefined templates to standardize and speed up recurring processes across modules like Ticket, Request, Change, Release, and Risk.

Let's see each of these in detail. &#x20;


---

# 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.infraon.io/infinity/user-guide/infraon-configuration/general-settings.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.
