Activity
The Activity page is a single, filterable timeline of everything that happened in your organization: who deployed what, which server settings changed, who was invited to the team, and when. It lives in the top navigation of the Console, next to Deployments and Monitoring.
Activity is scoped to the organization you are currently in. Switching organizations changes the feed — see Organizations.
Who can see it #
The Activity tab only appears for Owners, Admins, and Managers. Developers and Viewers do not see the tab and cannot open the page directly.
Your role is checked in the organization you are currently viewing, not globally. If you are an Admin in one organization and a Developer in another, you only see Activity in the first one. Roles are explained in Members.
What gets recorded #
Events are grouped into categories. The category is shown as a badge on every row, and you can filter by it.
| Category | Examples |
|---|---|
| Deployment | Deployment triggered, rolled back, rerun |
| Project | Project created, updated, deleted, moved; environment variables updated; auto deploy updated; Nginx configuration updated or reset |
| Server | Server created, updated, deleted, transferred, rebooted; root password revealed; service restarted; service configuration updated; PHP settings updated; queue settings updated; scheduled jobs created, updated, paused, resumed, deleted; background jobs created, updated, deleted, started, stopped, restarted |
| Member | Member invited, invite resent, invite cancelled, joined, added, removed, role changed |
| Organization | Organization created, updated, deleted |
| Token | API token created, updated, deleted |
| Settings | Notification settings updated, maintenance template updated |
| Provider | Server provider created, updated, deleted |
Reading a row #
Every entry answers four questions:
- Actor — the member who performed the action, with their name and email. Events that were not started by a person — a webhook-triggered deployment, for example — are attributed to System.
- Activity — the category badge plus a plain-English description of what happened, such as “Environment variables updated”. When the event has a named target, its name appears underneath as a link.
- Target — the type of resource the action applied to, linking to that server or project where one exists. Organization-wide events, such as a settings change, have no target.
- When — a relative timestamp (“3 hours ago”). Hover it for the exact date and time.
Click the chevron at the end of a row to expand it. The expanded view shows the raw action name, the IP address the request came from, the exact timestamp, and a details block with any extra data recorded for that event.
Filtering #
The filter row sits above the table, and results update as you type or select:
- Search — matches the raw action name, so
deploymentnarrows to every deployment event andmember.role_changednarrows to a single one. - Member — show only what one person did.
- Category — one of the categories in the table above.
- Action — a single specific action. Picking a category first narrows this list to that category’s actions.
- Origin — where the action came in through: MCP for an AI assistant, Webhook for a push, API for a direct call. The Console, the CLI and the mobile app are left blank, because they cannot be told apart from here.
- From / To dates — limit the feed to a date range.
Filters combine, and a Clear button appears once any of them is set. The feed is paginated, newest first, with the total event count shown under the page title.
Reading one assistant’s run #
An assistant usually does several things in a row — deploy, read the failure, roll back — and those land as separate rows. Rows from the same MCP session carry the same session, so clicking the MCP badge on any of them narrows the feed to that one run. A bar above the table says how many events it holds and offers a way back to everything.
Only clients that keep a session are grouped this way. A client that keeps none still gets the MCP badge on each row; those rows simply cannot be tied to each other.
What members with limited access see #
If a member is scoped to specific servers or projects (see Members), their Activity feed is trimmed to match: they see events for the servers and projects they have access to, plus organization-wide events such as team and settings changes. They never see activity for resources outside their scope.
Privacy and retention #
- Environment variable values are never recorded. When someone updates a project’s environment variables, Depfloy stores only the names of the variables that changed — never their values. See Project Environments.
- Entries are kept for 90 days, then deleted automatically.
Related pages #
- Console Overview — where the Activity tab sits in the Console.
- Project Deployments — full history and logs for a single project’s deployments.
- Members — roles and per-resource scoping that determine what a member sees here.
- Organizations — how organizations separate teams, servers, and activity.