Teams
Activity log and usage per member
Updated September 2026
Two admin tools answer “who did that?” and “who uses what?”: the activity log records every change in the workspace, and the usage page breaks this month’s work down per member. Both are on every plan, under Team, for owners and admins.
On this page
Activity log
Open Team → Activity. Entries are newest first, with who did it, what and when. Scroll down to load older entries.
| Area | What is recorded |
|---|---|
| Links | Created, edited (which settings changed, never the password itself), disabled, enabled, made private or shared with the team, deleted, bulk actions, CSV imports, and links handed to the owner when someone leaves. |
| Reports | QA reports and visual compares that were run, QA report share links that were reset, and live compare share links that were created or revoked. |
| Team | Members joining, leaving, being removed or changing role; invitations; join requests; ownership transfers; workspace renames. |
| Domains | Domains added, verified, failed verification, lost verification or removed. |
| Settings | API keys created or revoked, branding and policy changes, notification channels added, changed, removed or marked failing. |
Private links in the activity log
A private link is visible only to the person who created it, so the log records what happened to it without saying which link it is:
- The entry reads Private link instead of the link’s alias and domain, for the link itself and for its QA reports, compares and share links. Owners and admins see that a private link had activity, who did it and when, but not which link.
- The object ID of such an entry is a one-way code starting with
h:instead of the link’s ID, in the Object ID filter and in the CSV export. Filtering by the link’s real ID finds nothing. The same link always gets the same code, so its entries can still be listed together: copy theh:value from thetarget_idcolumn of the export into Object ID. - When a shared link is made private, its earlier entries are rewritten the same way, and an earlier “shared with the team” entry reads Private link · shared with the team. This can’t be undone: sharing the link again doesn’t restore them, but new entries show the link as usual.
- The Private link · made private entry keeps, in the
metadatacolumn of the export, how many QA report share links were reset, live compare and readiness share links revoked, channel rules removed and DNS webhooks cleared by the switch (see What happens when you make a link private).
This applies to the link’s creator too: if they are an owner or admin, they find their private link’s entries in the log by the h: code, like everyone else.
Filter and export
Combine any of the filters above the list:
- Member: one person, or everyone.
- Action: a single action such as “link deleted”, or a whole family such as every link action.
- Object type and Object ID: everything that happened to one link, member or API key.
- From and To: whole days, both included (UTC).
Export CSV downloads the filtered log, newest first, up to 50,000 rows, with the columns created_at, actor_id, actor_email, action, target_type, target_id and metadata (JSON).
How long activity is kept
| Plan | Activity kept for |
|---|---|
| Free | 7 days |
| Pro | 30 days |
| Agency | 90 days |
| Provider | 365 days |
Older entries are deleted automatically every night. Export what you need to keep for longer.
Usage per member
Team → Usage shows the plan quotas used by the whole team this month (QA reports, visual compares and live compare sessions, against the plan limit, or “unlimited” when the plan has no cap), plus links created. By member lists what each person created. Pick an earlier Period to look back month by month.