Activity Log
Read every change recorded in your team, see who made it and whether it came from a person, a token, an agent, an integration or the system, and open an item's full history with its field-by-field changes.
By the end of this page you will know what the activity log records, how to read your team's log and narrow it to what you are looking for, what the origin of an entry tells you, and how to open the full history of one record with every field that changed.
Every create, update and delete on a project, a client, a project member and your own account writes one entry: what happened, who did it, when, and the fields that changed with their old and new values. Entries are kept for good and are never edited, so the log is the place to answer "who changed this, and when".
Before you begin
| You need | Why |
|---|---|
A role carrying activity:read | Every default role except Guest carries it. Without it the page shows a notice instead of the log. |
| To be in the team whose log you want | The page shows your current team. Switch teams from the account menu to read another one you belong to. |
Where the log lives
Account Settings → Activity is the team's log: every entry of the team itself and of the projects you may see, newest first. A members-only project you are not a member of contributes nothing to your view, so two people on the same team can see different logs.
Activity History is the same data for one record, opened from the log's row menu today and from each record's own page as those pages land. It shows that record's entries only, with the changes rendered field by field.
Read the log
- Open Account Settings → Activity.
- Read the entries, newest first. Each row says when it happened, what happened, what kind of record it is about, who did it and where the change came from.
- Use Search the log to find words in an entry, such as a project name or "archived".
- Use the Origin list to keep only the changes made by people, by API tokens, by MCP tools, by integrations, by webhooks, by Heimdall or by the system.
- Page through with the controls under the table. Twenty-five entries fit on a page.
What an entry carries
| Column | What it says |
|---|---|
| When | How long ago the change was made. Hover for the exact moment in your timezone. |
| Entry | What happened, in a sentence that names the record: Project 'Payments' was updated. |
| Record | The kind of record: Project, Client, Project member or Account. |
| By | The person who made the change, or System when nobody did, and under the name the origin the change came from. |
Origins
| Origin | Meaning |
|---|---|
| Human | Someone signed in to the app made the change. |
| API token | A request to the REST API carrying a personal access token made it. |
| MCP tool | An agent connected over MCP made it with one of its tools. |
| Integration | An inbound delivery did: a Git hosting event, a pipeline report or a Telegram update. |
| Webhook | A listener reacting to an outbound event made it. |
| Heimdall | An AI draft someone accepted made it. |
| System | A scheduled command or a background job made it, with nobody acting. |
The origin is recorded on every entry as it is written, so a change made by an agent on your behalf is never mistaken for one you made by hand.
Open a record's history
- Press the row's menu and choose History. The menu appears on entries about a project, a client or a project member.
- The Activity History flyout lists that record's entries, newest first, each with who made it and its origin.
- An update shows each changed field with the old value struck through and the new value beside it. Dates read as dates, switches as Yes and No, and an empty value as None.
- Press Load more to reveal the next ten entries.
History is offered only for records you can open. If the record was deleted or moved out of your view since the entry was written, the page says so instead of opening an empty flyout.
All the fields
What happens next
- Nothing is written by reading. The log and the history flyout only read what other pages recorded.
- Entries are never changed or removed by anyone. A record's deletion is one more entry about it.
- The same entries will be readable by integrations through the REST API and by agents over MCP as those surfaces land, filtered to the same records you may see here.
Permissions
| Action | Who may do it |
|---|---|
| Read the team's log | The team owner, and any member whose role or group carries activity:read. |
| Open a record's history | Anyone who may read the log and may see the record. |
| See a members-only project | Its members only, whatever their role; its entries are left out of everyone else's log. |
Frequently asked
Related
- Roles: which roles carry
activity:read. - Members and guests: why a guest never reads the team log.
- API tokens: the tokens behind the API token origin.
How is this guide?
Last updated on
Groups
Grant a set of permissions to several members at once, on top of their roles, and keep the group's membership in step with the team.
AI Settings
Read where the team's AI budget stands this month, set the cap and the warning line, read the statement per feature and model and the latest calls, and see which model each job runs on.