> 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/admin-guide/overview.md).

# Overview

The **Infraon Admin Guide** is explicitly designed for administrators responsible for configuring, managing, and maintaining the Infraon Infinity platform. This guide focuses on modules and functionalities exclusive to the Management Admin role, such as system configuration, user management, and platform settings.

## Why do I see only a few modules here?

This guide includes **only those modules and features that are exclusive to  Management Admin users**, such as:

* Platform Configuration
* User & Role Management
* System Settings

The remaining modules are shared between both users and admins. To avoid duplication and provide a clear, role-based experience, these shared modules are documented under the [**Infinity User Guide** ](/infinity/user-guide/introduction.md)section.

### Where can I view the full product documentation?

If you’re an Admin looking for detailed documentation on all other modules:

* Navigate to the [**Infinity User Guide** ](/infinity/user-guide/introduction.md)for technician-level modules and operational features.
* Use the left-side navigation menu to explore topics by module.
* Use the search bar at the top of the page to quickly find specific content.


---

# 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/admin-guide/overview.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.