How to filter Logs
The log stores all important actions in the company — after a month of active work, it contains hundreds of records. To find the event you need, scrolling manually makes no sense. Filters are the main
The log Logs — company activity log stores all important actions in the company — after a month of active work, it contains hundreds of records. To find the event you need, scrolling manually makes no sense. Filters are the main tool for working with the log.
How to filter Logs
When to use filters
Incident investigation — someone deleted a bot, and you need to find out who did it and when.
Auditing a specific employee — an Owner reviews an Admin’s actions.
“Before and after” period — what changed in the team over the past week.
Searching by event type — all invitations for the month for a team growth report.
How it works
Filters are applied to the required data set — the table is updated with new data. Multiple filters are combined using AND logic: for example, object = bot, Buyer = Ivan, and period = last 7 days return only the intersection.
Filters are preserved when you move between sections within a single session: if you go to another screen and come back, the values remain. After you reload the page, filters are reset.
CSV export takes the current filters into account — the file will contain exactly what is visible in the table. This lets you create a targeted report in a minute.
Available filters
Filter | What it defines | Example value |
Object | System object type — what the action was performed on | user, bot, space, role, billing |
Editor | Who performed the action. The list of company employees | email of a specific admin |
Time | Period for which to show events | Last 7 days, Last month, Custom range |
How to apply a filter
1. Open the filters panel
The Filters button above the table.
2. Select parameters
Each filter has a dropdown list. Object and Editor support multi-select. Time offers preset periods and Custom range.

3. Click Apply
The table will update. An active filters indicator will appear above it.
4. Export if needed
Usage examples
Incident analysis
The Owner noticed that one of the bots disappeared from the list. They open Logs → Filters → Object: bot + Time: Last 24 hours. They see an archiving record with the author and time — then they can follow up with the team with specific questions.
Audit of a specific admin
An external security audit was requested. The auditor wants to see all actions by Admin Ivanov. Owner: Logs → Filters → Editor: ivan@company.com + Time: Last 90 days. They get the list, export it to CSV, and send it to the auditor.
Team growth report
HR is counting how many employees were added during the quarter. Object: user + Time: quarter. The number of rows in the result reflects invitations and other user-related actions.
Security — role changes
Once a month, run a scheduled check: who changed roles. Object: role + Time: month — review each change for approval.
If you regularly create the same report, set a monthly reminder to open Logs with these filters and export CSV. This makes it easier not to miss changes that are important for security.
Frequently asked questions
Relationship with other sections
Filters are a preparatory step before How to Export Logs (the export is built from the filtered selection) or manual review. What should be considered anomalous is described in Security (team audit recommendations).
Related
Was this article helpful?





