Skip to main content
Activity logs capture every meaningful community interaction — posts, edits, deletions, auth events, and more — as a structured, chronological stream. Every activity consists of a type (what happened), a version (describing the schema of its payload), an initiator (who performed the action), sometimes a recipient (who was the target of the action, e.g. the member who received an award), and a metadata payload of related entity IDs and point-in-time info (like a post title or feed label as it was when the event occurred).
Did you know you can ask our MCP server this too? Try asking: “What happened in the community yesterday?”

Reading the activity log in Studio

Studio’s Activity page is the chronological record of everything that has happened in your community. Use it to answer “what happened, and when?” for a specific member or a specific day. It is not listed in the Studio sidebar. Reach it with Cmd+K and type activity, click View all activity on the Recent Activity card at the bottom of the Overview dashboard, or go straight to Activity.
The Activity page in Studio

The Activity page in Studio

Searching and filtering

Search matches on activity content and on the member who performed it. Three filters narrow the feed:
  • Activity - the activity type. Every type listed under Activity types below can be filtered for.
  • Team - include all members, only your teammates, or exclude your teammates.
  • Type - humans only, all including bots, or bots only.
Sort by newest or oldest.
Filtering to Posts Deleted and Comments Deleted gives you a deletion audit trail, which is the fastest way to confirm whether content was removed by its author or by a moderator.

A single member’s activity

To see one member’s history instead of the whole community, open their profile from Members and use the activity tab there. It carries the same activity-type filter.
Viewing activity requires community data access. See Access and roles.

Activity types

Each event is tagged with an activity type that identifies what happened.

Metadata versioning

Every activity event carries a version number that describes the shape of its payload. When we add new fields or event types, we bump the version and publish the change on the Versions page.