> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to Detect Unusual Activity in Your Workspace
- URL: https://blog.jestor.com/detect-unusual-activity-in-your-workspace/
- Published: 2026-09-17T22:36:50.000Z
- Updated: 2026-09-17T22:36:50.000Z
- Author: Bruno Bannach

To **detect unusual activity in your workspace**, you look at patterns rather than individual changes. A single edit tells you little; a cluster of them at an odd time tells you more.

## What to look for

None of these prove anything on their own. Together they warrant a look.

- **Bulk edits** outside a known migration or cleanup
- **Deletions** of records or fields nobody announced
- **Changes at unusual times**, well outside working hours
- **API-sourced changes** where no integration should be writing
- **Permission changes** nobody requested

## How to investigate

| Filter          | What it isolates                            |
| --------------- | ------------------------------------------- |
| **Action type** | Creations, edits, or deletions specifically |
| **Source**      | User, automation, or API                    |
| **Date range**  | A specific window                           |
| **User**        | One person's activity                       |
| **Table**       | Activity scoped to one process              |

## How to check it in Jestor

1. Open the general history in **Jestor**, or the history view inside a specific table.
2. Filter by action type to isolate deletions specifically.
3. Filter by source to separate user edits from automation and **API** changes.
4. Narrow to a date range covering the period in question.
5. Export the filtered result if the finding needs to be documented.

## Why choose Jestor for workspace oversight?

**Jestor** records the source of every change, which means an unexpected edit is attributable rather than mysterious — usually the fastest way to rule out anything concerning.

Because changes saved together are grouped with their before-and-after state, a review reads as a sequence of actions rather than as a stream of disconnected field updates.

## Frequently Asked Questions

### Can I filter history by source?

Yes — user, automation, or API. See [jestor.com](https://jestor.com/?ref=blog.jestor.com).

### Can I isolate deletions?

Yes, by filtering on action type.

### Can I export a finding?

Yes, as a filtered spreadsheet.

## Video Tutorial: Step by Step

Check out other practical tutorials on the Jestor YouTube channel.

## Get to know Jestor

With **Jestor**, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by **AI**. Discover Jestor at [jestor.com](https://jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.