> 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/release-notes/fenixpyre-cloud-releases/november-2025.md).

# November 2025

## Introducing FenixPyre's Audit Logs for Admins

### What's New? 🌟

* **Audit Logs Dashboard**: Introducing a comprehensive Audit Logs feature that enables administrators to view, filter, and analyze audit events within the admin dashboard.

<figure><img src="https://3947089720-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOuMyGdeUQs2m5OYPFuwT%2Fuploads%2FUm6eyQtcJtLdvULz4u6u%2Fimage.avif?alt=media&amp;token=8d20e1fa-5281-4654-b6df-602fcdf562b5" alt=""><figcaption></figcaption></figure>

### Features :fire:

* **Dynamic Filter Sets**: Configurable filter sets that define available columns and default views for different audit log scenarios. Easy switching between different audit log views based on your needs.
* **Advanced Filtering System**:

  * Nested filter groups with AND/OR logical operators for complex queries

  <figure><img src="https://3947089720-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOuMyGdeUQs2m5OYPFuwT%2Fuploads%2FISBiBkl0zlPpEAasgIyR%2Fimage%20(3).avif?alt=media&amp;token=69ed8aa1-21b9-47cc-a54a-55bccd1628db" alt=""><figcaption></figcaption></figure>

  * Support for multiple filter conditions within groups
  * Intuitive date range filtering with a user-friendly date picker
* **Flexible Table View**:
  * Dynamic columns that adapt based on your selected filter set
  * Custom cell renderers for time stamps, status indicators, file names, connectors, and event sources
  * Context menu support for adding filters directly from table cells
* **Event Details Page**: Comprehensive view of individual audit log events with:

<figure><img src="https://3947089720-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOuMyGdeUQs2m5OYPFuwT%2Fuploads%2FKoOow66ODX8uKl4le5qo%2FScreenshot%202025-11-16%20at%201.17.53%E2%80%AFPM.png?alt=media&amp;token=d49073c6-9a7c-486b-b295-60b1f5d6fcab" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3947089720-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOuMyGdeUQs2m5OYPFuwT%2Fuploads%2FwMGiwiAzu9qBrykcQKAz%2FScreenshot%202025-11-16%20at%201.18.46%E2%80%AFPM.png?alt=media&amp;token=be5aa12d-7b20-4015-8b51-0557559800c9" alt=""><figcaption></figcaption></figure>

* Event information (ID, action, type, timestamp)
* Actor information (user details, role)
* Target information (file details, paths)
* Location information (geo-location, IP address)
* Device and network information
* Event result and source details
* Raw JSON data with copy-to-clipboard functionality


---

# 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/release-notes/fenixpyre-cloud-releases/november-2025.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.