> For the complete documentation index, see [llms.txt](https://docs.fenixpyre.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fenixpyre.com/fenixpyre-for-admins/admin-dashboard/home.md).

# Home

The **Admin Dashboard** in FenixPyre provides administrators with a comprehensive view of user activity, file interactions, and platform performance. This centralized panel is designed to make monitoring and managing your organization’s data security and user behavior easier.

<figure><img src="https://3947089720-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOuMyGdeUQs2m5OYPFuwT%2Fuploads%2FvqJHZhflmMjhj0vzzMLc%2FScreenshot%202025-02-11%20at%201.47.35%E2%80%AFPM.png?alt=media&amp;token=c76b7226-8bae-4088-9341-3b5dc350f709" alt=""><figcaption></figcaption></figure>

### **Key Sections of the Admin Dashboard:**

1. **Overview**:
   * Displays key metrics such as the total number of active files and users.
   * **Active Files**: Shows the number of files being actively managed, including changes over time.
   * **Active Users**: Displays the number of active users, allowing administrators to track user engagement with the platform.
2. **Recent Activity**:
   * A feed that highlights the latest actions taken by users, such as modifying files.
   * Each activity entry includes information on the user and the file they interacted with, as well as the action performed (e.g., **ANCHOR**, **UNANCHOR,** etc.).
3. **Active File Actions**:
   * Provides insights into specific file interactions (e.g., co-editing) performed by users.
   * The section displays the number of file actions (e.g., co-editing, file modifications) .
4. **Active Applications**:
   * Displays a breakdown of the active applications used within your organization, visualizing how different apps are being utilized for file access and management.


---

# 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.fenixpyre.com/fenixpyre-for-admins/admin-dashboard/home.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.
