> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tightknit.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Activity Logs

> Tightknit captures every community interaction — posts, edits, deletions, auth events, and more — as a structured, versioned activity stream.

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).

<Tip>
  Browse your community's activities in Studio at
  [studio.tightknit.ai/\~/activities](https://studio.tightknit.ai/-/activities),
  where you can search, filter, and drill into any event.
</Tip>

<Tip>
  Activities can also sync to your CRM via the
  [Salesforce integration](/integrations/salesforce), so customer
  success and community teams can see community engagement alongside account
  records.
</Tip>

## Activity types

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

| Type                                   | Description                                                  |
| -------------------------------------- | ------------------------------------------------------------ |
| `award.given`                          | An award was given to a member.                              |
| `badge.given`                          | A badge was given to a member.                               |
| `calendar_event.user_registered`       | A member registered for a calendar event.                    |
| `calendar_event.user_unregistered`     | A member unregistered from a calendar event.                 |
| `comment.created`                      | A member commented on a post.                                |
| `comment.deleted`                      | A comment was deleted.                                       |
| `comment.edited`                       | A comment was edited.                                        |
| `credential.given`                     | A credential was given to a member.                          |
| `journey.completed`                    | A member completed a journey.                                |
| `milestone.completed`                  | A member completed a milestone.                              |
| `poll.created`                         | A poll was created.                                          |
| `poll.vote_added`                      | A member voted on a poll.                                    |
| `post.created`                         | A member created a new post.                                 |
| `post.deleted`                         | A post was deleted.                                          |
| `post.edited`                          | A post was edited.                                           |
| `site.auth.login_failure`              | An authentication attempt on the companion site failed.      |
| `site.auth.login_success`              | A member successfully authenticated on the companion site.   |
| `slack_message.created`                | A top-level Slack message was posted in a community channel. |
| `slack_message.threaded_reply.created` | A threaded reply was posted in a community channel.          |
| `slack_reaction.added`                 | An emoji reaction was added to a Slack message.              |
| `slack_reaction.removed`               | An emoji reaction was removed from a Slack message.          |
| `workspace.user_joined`                | A user joined the Slack workspace.                           |

## 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](/activity-logs/versions) page.