> ## Documentation Index
> Fetch the complete documentation index at: https://docs.atllasx.com/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, and the ability to move resources (campaigns, contacts, etc.) between team members.

## Audit Log

The audit log records every significant team event. It's append-only — entries can't be edited or deleted — so you have a permanent history of who did what and when.

### What's 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 finalised 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 the **actor** (who did it, including `system` for automated actions), the **target** (which member or resource was affected), a **timestamp**, and **details** specific to the action (e.g. how many credits were transferred, the resource ID that 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 don't automatically belong to the team. You bring them in by **claiming** them. Once they're 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, voices, call queue, execution queue, scripts
* **AI Receptionist**: agents, FAQ entries, phone numbers, messages
* **CRM**: contacts, email campaigns, email signatures, signature builder
* **Integrations**: webhooks
* **Content**: training materials

### Claiming Personal Resources

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

1. Open the relevant resource section (e.g. **AI Calling → Campaigns**)
2. Select the resources you want to bring in (up to 100 at a time)
3. Trigger the **Claim into Team** action

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

### Reassigning Resources Between Members

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

* Pick 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>
  Only the team owner can claim or reassign resources. Members cannot move their own resources to other members; if a member needs to hand a campaign to a teammate, the owner has to perform the reassignment.
</Warning>