> AI agents: this is one page from Mammoth Analytics documentation. The index of all pages as Markdown is https://mammoth.io/docs/llms.txt. Append `.md` to any docs URL, or send `Accept: text/markdown`, to get Markdown.

# Review your team's work in the Mammoth Activity Log

> Use the Mammoth Activity Log to see what your team did, how far back it goes on each plan, which patterns to act on, and what to do when someone leaves.
>
> Applies to: Roles: Workspace Owner or Workspace Member. Where: Monitor › Activity Log

The Activity Log, under **Monitor** in the left sidebar, records what your team does in Mammoth: who created, changed or ran what, and when. Every Workspace Owner and Workspace Member can open it; how far back it goes depends on your plan.

## Open the Activity Log and read an entry

Open **Monitor** in the left sidebar, then the **Activity Log** tab. Use the **Project** and **Workspace** buttons to switch scope. Every Workspace Owner and Workspace Member can open it.

Actions are recorded automatically in these categories: Dataset, Pipeline, View, Automation, Connector, Project, Folder, Workspace, Data Retention, Dashboard and Parameter (for example adding data, editing tasks, running automations, inviting users, changing roles, renaming projects). Each entry shows **Date**, **Events**, **Details**, **Object**, **Category** and **Author**. The range defaults to **Last 30 days**.

For how far back it goes on each plan, see [Export the Activity Log](https://mammoth.io/docs/learn/automate/export-activity-log/#how-far-back-the-activity-log-goes); to read entries, see [Activity log](https://mammoth.io/docs/learn/automate/activity-log/).

![Activity Log filtered by 4 authors and 41 events, listing Create dataset, Invite users to workspace, Create view, and Create project](https://mammoth.io/docs/images/20260408_154349_Activitylog_from_team-1.webp)

The log shows what happened, not data contents: an *Add tasks to pipeline* event with the view and the teammate, but not revenue values or rows.

| Pattern in the log | Suggests |
| --- | --- |
| The same file uploaded by hand every week | A connector and Dataset Refresh (or, for files, a Data Consolidation automation) |
| Heavy Excel exports, few dashboards | Dashboard training |
| Similar pipelines rebuilt from scratch | A reference template and a short training session |
| Pipeline creation in the first weeks, steady activity from most of the team | Adoption is working |

Other signs of success: several people use reference workflows, naming is consistent, recurring reports come from Mammoth, and team members build stakeholder dashboards on their own. Ask in one-to-ones which workflows they have automated.

## When a team member leaves

Work stays in the project, not with the person: pipelines, datasets and shared dashboards keep working.

1. In the Activity Log, filter **Author** to that person to see their key contributions.
2. Decide who maintains each workflow, and hand off complex pipelines.
3. A Workspace Owner removes them in **Workspace Settings** > **User Management**. Make sure each project still has a Project Admin.

## Related

- [Filter the Activity Log](https://mammoth.io/docs/learn/automate/filter-activity-log/): by event, category, author or date.
- [Export the Activity Log](https://mammoth.io/docs/learn/automate/export-activity-log/): CSV, XLSX or a dataset, and history by plan.
- [Mammoth for managers](https://mammoth.io/docs/learn/start/for-managers/): the rest of the manager plan.
- [Invite your team](https://mammoth.io/docs/learn/start/invite-your-team/): add and remove people.

---
Source: https://mammoth.io/docs/learn/start/review-team-activity.md · Updated: 2026-11-08