> For the complete documentation index, see [llms.txt](https://docs.kick.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kick.co/working-with-your-team/activity.md). # Activity A complete log of every change made in your workspace - who did what and when. The Activity tab is a full audit trail of everything that's happened in your workspace. Every transaction change, categorization update, and sync event is logged with a timestamp and the name of whoever or whatever made the change. Go to **Activity** in the sidebar to view the log. *** ### What you can see Each entry shows: * **Date** - the exact time the change happened * **Updated by** - the team member, integration, or Kick automation that made the change * **Activity** - a description of what changed * **Entity** - the business the change applies to *** ### Who shows up in the log * **Your team members** - any change made by your accountant, bookkeeper, or other workspace members appears under their name * **Kick** - automated categorization, transfer matching, and other AI actions are logged under the relevant Kick agent * **Integrations** - transactions synced from [Ramp](/integrations/ramp.md), [Mercury](/integrations/mercury.md), Stripe, etc. are logged under the integration * [**Rules**](/common-workflows/rules.md) - when a rule updates a transaction, it's logged and attributed to that rule *** ### When to use it * To see what your accountant changed and why * To verify that a specific transaction was updated correctly * To check whether an integration synced recently * To understand why a report number changed unexpectedly --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.kick.co/working-with-your-team/activity.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.