Team Activity Log

The team activity log is a running ledger of what your staff are doing inside a team workspace -- sessions created, athletes viewed, members joining, consents signed. It exists for the people responsible for safeguarding, accountability, and continuity: the head coach who needs to see who exported a roster last week, the welfare officer reviewing access to a minor's record, the new admin trying to understand why a season plan changed shape over the weekend.

Where to find it

Open your team workspace and look for Activity under Team workspace in the sidebar. The route is /team/activity. The link only appears when you're working inside a team -- personal workspaces have nothing to log.

Coaches, admins, and owners can open the page. Assistants and viewers cannot. Platform admins (the data-protection officers who manage clubs across Planner.coach) can also view activity for any team they are responsible for.

What gets recorded

Every entry is sorted into one of five categories. The category drives both the icon you see in the feed and who is allowed to see the row.

Athlete access -- views and exports of athlete records. This is the category that matters most under safeguarding rules: if a coach opened a minor's profile or downloaded a progress report, it shows up here, with the actor's IP stamped on the row at write time.

Team settings -- changes to the team's name, logo, branding, status, or membership caps. Useful when you want to know who renamed the team or shifted the member limit.

Membership -- invitations sent, joins, role changes, removals, and people leaving the team.

Content -- sessions, activities, training programs, custom surfaces, and other coaching content created, edited, or deleted by the team.

Consent -- guardian-consent workflows: when a consent request was sent, when it was signed, and when it was revoked.

Who can see which events

Some categories are admin-only because they are designed for safeguarding investigations rather than day-to-day coordination.

Coaches working in the feed will not see the admin-only category chips at all -- the page hides categories they aren't entitled to view rather than returning empty results.

Filtering and search

The top of the page is a single search box and a Filter popover.

• Search runs across the actor's name, the event summary, and the target's name (athlete, session, activity, and so on).
• Category chips sit below the search box. Click as many as you like to combine.
• Actor lives in the Filter popover -- a dropdown of everyone who has ever produced an event in this team, including former members.
• Date range is also in the Filter popover, with quick 7 days, 30 days, and 90 days presets next to the calendar.

Active filters update the URL, so any view you build can be sent to a colleague (or bookmarked for a recurring review) and arrives looking the same on their screen.

Saved presets

If you find yourself rebuilding the same filter shape -- for example "athlete data exports, last 90 days" -- save it once via the Presets menu. Presets are stored locally on your device and are not synced between machines. Treat them as a personal shortcut, not as a shared team resource.

Hide your own activity

The Hide my activity on this device toggle removes events you produced from the visible feed. It's useful when you want to scan what your teammates have done without your own work crowding the list. The setting only affects what you see -- your teammates still see your activity.

Opening an event

Click any row to open the detail drawer. The drawer shows:

• Actor -- who performed the action (and a fallback "Removed user" label if the actor's account has since been deleted).
• Time -- a friendly absolute timestamp alongside the raw ISO string.
• Target -- the athlete, session, activity, program, or workflow involved, with a link to open it where one exists.
• Role change -- the before and after roles when membership has shifted.
• Fields changed -- a list of which fields moved on a settings update.
• Export scope -- the report type, recipient, and column list when an export was the cause.
• Page -- the route the action was performed from.
• IP and Device -- the actor's IP and a short device summary (for example, Chrome on Mac) when the row was captured with that context.
• Raw event payload -- a collapsible JSON block, plus a Copy JSON button for forensic note-keeping.

Exporting to CSV

Admins (and platform admins) can download the filtered feed as a CSV. The button sits at the top right of the page and is disabled until you pick a date range.

• A date range is required for every export.
• Exports are capped at a 90-day window for safeguarding compliance.
• The file name follows the pattern team-audit-{teamId}-{from}-to-{to}.csv.
• Every export is itself logged -- so the record of who downloaded what is part of the same ledger.

If you need a longer window, run successive 90-day exports.

Keyboard shortcuts

Press ? anywhere on the page to bring up the shortcuts dialog.

The shortcuts are skipped while you're typing in any input, so search-as-you-type still feels native.

Pagination and freshness

The feed shows 25 events per page. When you have more than one page, paging controls appear at the bottom along with a Jump to input for moving directly to a specific page.

The page polls the server every 30 seconds. When new events arrive between polls, a banner appears at the top of the feed inviting you to scroll up to view them -- the cursor never jumps under your gaze. The Refresh control next to the date stamp triggers an immediate refetch.

What this is not

A few things the activity log is deliberately not:

• Not retroactive. Events appear from the point the feature was switched on. Anything that happened before that does not show up here.
• Not a real-time alerting system. It's a ledger you read, not an alarm. The 30-second poll is fast enough for an admin reviewing the page; it isn't designed to page you when something happens.
• Not a replacement for the encrypted audit trail behind athlete deletion. The internal compliance log described in Data Security and Retention is a separate, hashed audit record. The team activity log gives staff visibility into live work; the deletion audit log is the long-term compliance record after personal data has been removed.

Related

• Teams Overview -- Workspace structure, credit pooling, and context switching.
• Roles and Permissions -- Which roles see which categories.
• Data Security and Retention -- Encryption, the six-year retention rule, and the hashed deletion audit log.
• Parental Consent -- The consent workflows whose events surface here.