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

# Audit Log & Resource Management

> Review team activity history and move resources between members.

Team owners get two extra capabilities beyond inviting and removing members:

* A complete audit log of team activity
* The ability to move resources between team members, such as campaigns and contacts

## Audit log

The audit log records every significant team event. It is append-only: entries cannot be edited or deleted, so the history is permanent. You can see who did what and when.

### What is logged

| Action                     | When                                                            |
| -------------------------- | --------------------------------------------------------------- |
| `team_created`             | The team was first created                                      |
| `team_renamed`             | The team's display name was changed                             |
| `member_invited`           | An invite was sent                                              |
| `invite_canceled`          | An invite was revoked before being accepted                     |
| `member_joined`            | An invitee accepted and joined the team                         |
| `member_scheduled_removal` | The owner started removing a member (grace period begins)       |
| `member_canceled_removal`  | A scheduled removal was cancelled                               |
| `member_removed`           | A member's removal was finalized at the end of the grace period |
| `subscription_updated`     | The team's subscription changed                                 |
| `allotment_updated`        | A member's monthly call allotment was changed                   |
| `credit_transfer`          | The owner transferred credits to a member on demand             |
| `resources_claimed`        | The owner claimed personal resources into the team              |
| `resource_transferred`     | A single resource was reassigned to another member              |
| `team_deleted`             | The team was deleted                                            |

Each entry captures four things:

* The **actor**, who did it. `system` names an automated action
* The **target**, which member or resource it affected
* A **timestamp**
* The **details** specific to the action, such as how many credits moved or which resource ID was reassigned

### Where to view

Open **Teams** from the sidebar and look for the **Activity** section. The full audit log is visible to the team owner only.

## Resource management

Personal resources you created **before** forming a team do not automatically belong to the team. You bring them in by **claiming** them. Once they are team-owned, you can also **reassign** individual resources between team members.

### Claimable resource types

Both claiming and reassignment work on the same set of collections:

* **AI Calling**: campaigns, contacts, voices, call queue, execution queue, scripts
* **AI Receptionist**: agents, FAQ entries, phone numbers, messages
* **Email**: email campaigns, email signatures, signature builder
* **Integrations**: webhooks
* **Content**: training materials

### Claim personal resources

When you first create a team as the owner, your existing resources stay personal until you claim them. That covers campaigns, contacts, and everything else. To bring them into the team:

1. Open the relevant resource section (e.g. **Campaigns** under **Outbound Campaigns**)
2. Choose the resources you want to bring in (up to 100 at a time)
3. Trigger the **Add to Team** action

The resources stay yours, but they now belong to the team. Audit log entries therefore reference them, and you can reassign them to another member if needed.

### Reassign resources between members

As the owner, you can move a single resource from one member to another:

* Choose the resource, or a batch of up to 100 resources
* Choose the source member (where the resource currently lives) and the destination member
* Confirm the reassignment

The destination member becomes the new owner of those resources and can use them as if they had created them. The reassignment is logged in the audit log as `resource_transferred`.

<Note>
  Reassignment is a permission-and-ownership change, not a copy. The original
  owner loses access to the resource. There is no "shared" middle state.
</Note>

<Warning>
  Ask the team owner to reassign a resource. Only the owner can claim or reassign
  one. A member cannot move their own resource to another member. If a member
  wants to hand a campaign to a teammate, the owner must do it.
</Warning>