Teams
Group users so you can see aggregated activity, per-member stats, and shareable read-only reports.
What teams are
A team groups Trenchcoat users so their activity can be viewed together — aggregate cost and sessions, per-member breakdowns, and a shareable read-only report.
A team is a reporting grouping, not a shared workspace, and not a permission boundary. API keys belong to the individual user who created them and are visible only to that user. There is no team-owned key, no shared key vault, and no role-based restriction on creating or revoking keys. Do not use team membership as an access control.
Your own data always lives in your own account. A team reads across its members' accounts to build aggregates; it does not hold data of its own.
Viewing your teams
Teams in the left sidebar lists the teams you belong to. There is no workspace switcher — the rest of the dashboard always shows your own data, and team views live under the Teams section.
Creating a team
- Click New Team.
- Enter a name.
- Click Create.
You are recorded as its owner.
The team view
Selecting a team gives you:
Overview — four cards (Sessions, Total Cost, Active Members, Avg Duration), a members list, and a sessions-over-time chart.
Members — every member with their session count, top tool, and last-active time. You can sort by column, and click through to a member's sessions.
Export — download the team's data.
Share — mint a read-only link at /share/<token> scoped to a date range,
for someone with no Trenchcoat account. Anyone holding the link can view it.
Team Total Cost is computed by a different function from the three cards beside it, and can disagree with them. This is a known open defect.
Managing members
From the Members tab you can Invite (by email address and role) and Remove a member.
Inviting does not currently send anything. The action records an invitation row; no email is dispatched and there is no acceptance flow that turns that row into a membership. Adding a member end-to-end is not yet a working path.
Roles (owner, admin, member) are stored and enforced by database policies
governing who may modify the team and its membership. They do not govern API
keys, and they do not govern what data a member can see.
What does not exist yet
Named explicitly, because earlier versions of this document described all of it:
- No team-scoped API keys. Keys are per-user. A team member cannot see, create, or revoke another member's keys — and a "Member" role does not restrict anyone from creating their own.
- No invitation email or acceptance flow (above).
- No leave-team action.
- No delete-team action, no Settings tab, no Danger Zone. Nothing schedules team data for deletion.
- No role-change UI.
- No workspace selector, and no notion of moving events between workspaces.
Dashboard visibility is not scope-governed
Dashboard pages authenticate with your own login and are filtered by row-level security on your user id — never by an API key. An API key's capture level decides what Trenchcoat records; it has no bearing on what a page can display to someone already authorised to see that account's data.