**Activity** lists every delivery: each time Tilt Base answered a request from a member's AI. Use it to see who received which skill or file, and when.
## Before you start
Activity is for anyone who reads your organisation's usage: Admins, Contributors and approvers. People with a team role, or the **Approver** tick in a team, see their teams' deliveries only. See <mention-page url="https://app.notion.com/p/41b4815eed4f81b5a34bd334676bcbb3">Roles and permissions</mention-page>.
## Open Activity
Go to Settings › Organisation › Activity. Deliveries are listed newest first, in your time zone. Select **Load older deliveries** to see more.
Each plugin also has its own **Activity** page, in the plugin's sidebar, listing that plugin's deliveries. Skill lists aren't counted against any one plugin.
## What each column shows
<table header-row="true">
<tr>
<td>Column</td>
<td>What it shows</td>
</tr>
<tr>
<td>**Time**</td>
<td>When Tilt Base answered the request.</td>
</tr>
<tr>
<td>**Member**</td>
<td>Whose AI made it.</td>
</tr>
<tr>
<td>**Delivery**</td>
<td>The type of delivery. See below.</td>
</tr>
<tr>
<td>**Content**</td>
<td>What was delivered, such as the skill or file.</td>
</tr>
<tr>
<td>**Agent client**</td>
<td>The AI client that made the request, by its ID.</td>
</tr>
</table>
## Delivery types
<table header-row="true">
<tr>
<td>Delivery</td>
<td>What happened</td>
<td>What **Content** shows</td>
</tr>
<tr>
<td>**Skill read**</td>
<td>A member's AI retrieved a skill's instructions with **Get skill**.</td>
<td>The skill's name</td>
</tr>
<tr>
<td>**Skill loaded**</td>
<td>A member's AI platform loaded a skill by itself, where Tilt has switched this on.</td>
<td>The skill's name</td>
</tr>
<tr>
<td>**Matter recorded**</td>
<td>The AI recorded the matter for a skill its platform loaded by itself.</td>
<td>The skill's name</td>
</tr>
<tr>
<td>**Skills listed**</td>
<td>The AI listed the skills the member receives.</td>
<td>Its search in quotes, or **All skills**</td>
</tr>
<tr>
<td>**File fetched**</td>
<td>The AI fetched one of a skill's files.</td>
<td>The file's name</td>
</tr>
<tr>
<td>**Transcription prepared**</td>
<td>Tilt Base gave the AI a credential to send a recording to your organisation's transcription provider.</td>
<td>The provider and model, such as Deepgram · Nova-3</td>
</tr>
<tr>
<td>**Transcription**</td>
<td>Tilt Base passed a recording from Microsoft Copilot to your organisation's provider.</td>
<td>The provider and model</td>
</tr>
</table>
<callout icon="💡" color="blue_bg">
	**A delivery isn't proof of completed work.** It shows that Tilt Base answered a member's AI. It doesn't show that the AI used or followed the skill, or finished the work.
</callout>
## Search and filter
- **Search content or client** finds deliveries by their content or agent client.
- **Filter deliveries** narrows the list by **Delivery** type, **Member** or **Time**.
Search and filters apply to every delivery, not only those on screen. If nothing matches, **Clear search and filters** shows every delivery again.
## If you read only your teams' deliveries
You see the skills and files of plugins each of your teams owned when they were delivered, and a note saying so. Skill lists, transcriptions and deliveries from before your organisation had teams are left out.
## Activity and the Audit log
Activity records what Tilt Base gave members' AI. The <mention-page url="https://app.notion.com/p/41b4815eed4f81d4a259dbb46af306cc">Audit log</mention-page> records the changes people make to your organisation, such as publishing a plugin or changing a role. Neither holds the other's records.
## Related
- <mention-page url="https://app.notion.com/p/41b4815eed4f81c18076f1dcb64e18c5">Metrics and matters</mention-page>
- <mention-page url="https://app.notion.com/p/41b4815eed4f81d4a259dbb46af306cc">Audit log</mention-page>
- <mention-page url="https://app.notion.com/p/41b4815eed4f817fb4e3eaaa83d6218f">Ask your AI for work</mention-page>
- <mention-page url="https://app.notion.com/p/41b4815eed4f81b5a34bd334676bcbb3">Roles and permissions</mention-page>