Deplo

Activity

Every meaningful action on your team, on one timeline, with filters for who, when, what and where.

Activity, in the sidebar, is the trail of who did what on your team, and when.

On a wide screen the filters and a breakdown of the period sit in a column down the right-hand side, with the trail taking the rest of the width. On a narrow one the filters sit above the trail and the breakdown at the end of the page.


The timeline

One vertical timeline, newest first, split by month. Each entry reads in the order you ask the question in:

  1. the face of the person who acted,
  2. their name, and how long ago it was,
  3. what they did, in one sentence, with the exact time at the end of the line.

The app or database an entry names carries its own picture, and the name is a link straight to it.

The same action repeated by the same person folds into one entry: you get the sentence once per run with its own time beside it, so seven deploys in a row read as seven lines under one heading instead of burying everything else.

The month heading stays pinned to the top as you scroll, with how many events that month holds, so you always know where you are in the trail.

Actions taken by the system or by a git provider are attributed to System, never to a person who happened to be nearby. They get the event's own icon instead of a face.

More entries load on their own as you reach the bottom.


Filters

Four filters, and they combine: picking several values inside one filter widens it, picking two different filters narrows it.

Prop

Type

The filters live in the address bar, so a filtered view is a link. Send someone "what did Ada change last week" instead of describing it.

Every option carries how many events it covers, so you can see where the activity is before you narrow anything. An option showing 0 had nothing in the period - it stays in the list rather than disappearing.


The breakdown

Under the filters, Events and People list what the period holds, busiest first. Click a line to narrow the trail to it, click it again to let it go.

The heading says which period the numbers describe: the dates you picked, or the last 30 days when you have picked none. With no date filter the trail itself goes back further than that, so the two can disagree - the heading is what tells you by how much.

Each list stays blind to its own filter: picking a person narrows the events beside them, and still shows everyone else's totals to compare against. Each list shows five lines, and the rest are one click away at the bottom.

Filtering by Resource hides team-level events on purpose. Adding a member or rotating a token did not happen to an app, so asking about an app leaves them out.


One app, one database

Every app and every database has its own Activity page, in its menu just above Settings. It is the same timeline, already narrowed to that one thing: no Resource filter to set, and Clear filters comes back to that page rather than to the team-wide one. User, Date and Event still work.

A database's history starts where the link to it does. Events recorded before the release that added this page still show on the team-wide Activity, but Deplo cannot tell which database they belonged to, so they do not appear on the database's own page.


One person

A member's own trail is a page too: Settings -> Members -> the member -> Activity. Same timeline, already narrowed to them - no User filter to set, and no face repeated down every row, because the page already says whose it is. Date, Event and Resource still work, and Clear filters comes back here.

Reaching it needs Manage members, the same capability as the rest of a member's page.


Events

Every event carries one type, and the Event filter groups them:

GroupCovers
AppsDeployments, apps, projects, domains, variables
DataDatabases, backups, backup destinations, cron jobs
TeamMembers and roles; tokens, passkeys and two-factor
PlatformServers, integrations, instance settings, Docker cleanup, monitoring, MCP access

What you can see

Activity needs the View activity capability. A member whose role only reaches part of the team sees the trail for the apps they reach, and not the team-wide events.

If an entry could not be written, the next successful write says so in the trail, out loud, rather than leaving a silent gap. A hole in an audit log has to be visible in the audit log.


See also

Did this page help you?

On this page