# How To Use The Logs Page

## Objective

Find a workspace event, narrow the activity list, and inspect the details recorded for an action.

## Environment

- Your account has the **Admin** role and access to **Settings** > **Logs**.

## Resolution

1. Open **Settings** and select **Logs**. The list shows **ZenOps** workspace activity, with the newest matching entries first. It is an application activity history, not a complete history of changes in external support platforms.
2. Choose a **Time** range: **Last hour**, **Last 24 hours**, **Last 7 days**, **Last 30 days**, **Custom range**, or **All time**. For a custom range, set the start and end in your browser's local time. The result timestamps use your preferred timezone, which can differ from your browser's timezone.
3. Narrow the list with **Log Type**, **Status**, or **Action**. Enter a name, email address, or role in **Actor** to find activity associated with that person or role. Results refresh when you change a filter; select **Refresh** to reload the current results. Select **Reset filters** to return to **Last 24 hours**, all types, statuses, and actions, with the **Actor** search cleared.
4. Read the matching rows. **Type** groups the event, **Action** names the operation, **Status** indicates whether the action was recorded as **Succeeded** or **Failed**, **Actor** identifies the person when available, **Target** shows the affected record type and identifiers, and **Summary** gives a brief outcome or error message.
5. Select the chevron at the start of a row to expand **Metadata** and **Error Details**. Use these fields to understand what the entry recorded. The page shows up to the latest 200 matching rows; if you cannot find an older event, narrow the time range or add filters.
6. After reviewing the details, confirm the current state in the relevant **ZenOps** page before repeating an operation. The **Logs** page records activity; it does not undo an action. If you need help, share the approximate time, action, status, and relevant details through [a support request](/help/articles/what-to-include-in-a-support-request/), after removing personal or customer-specific values.

> Canonical page: https://zenops.cx/help/articles/use-the-logs-page/
> Audience: For workspace administrators with Logs access
> Summary: Filter workspace activity, inspect a log entry, and understand recorded outcomes.

## Notes on this article

### Important: Protect sensitive details

After step 5 in resolution. Expanded metadata and error details can contain user, customer, or record identifiers. Review and redact them before sharing outside your workspace.

## Visual references

- Example Logs page with a generic product label. Fictional actor names, example.com email addresses, and sample record identifiers replace the original personal and customer details. The displayed dates, activity counts, and notification count are retained for context. Select the image to inspect it at full size.: [Logs page labeled Ops Console with filters and an activity table showing fictional actor names, example.com email addresses, and sample record identifiers.](https://zenops.cx/help/assets/logs-audit-trail-anonymized.png)