The team activity log records changes, never reads. Five areas produce entries: the team itself, its memberships, campaigns, pages, and billing. Each entry names who acted, what they did, and one identifying detail. Some entries carry a value such as an email address, a page name or an amount; others carry only a pointer to the object they acted on, and the app shows a shortened identifier for those. Anything not listed here is not recorded.
| Area | Entries |
|---|
| Team | 4 |
| Membership | 13 |
| Campaigns | 6 |
| Pages | 8 |
| Billing | 6 |
| Action | Recorded when | Detail carried |
|---|
| Team created | A team is created | The team name |
| Team renamed | The name changes | The new name |
| Team deleted | The owner dissolves the team | None |
| Ownership transferred | Ownership moves to another member | The account it moved to |
| Action | Recorded when | Detail carried |
|---|
| Member invited | A new invitation is sent | The invited email address and the role |
| Invitation refreshed | A second invitation to an address that already had a live one replaces it | The email address, the role |
| Invitation resent | An existing invitation is sent again | The invitation it re-sent |
| Invitation revoked | An invitation is withdrawn | The email address and the invitation |
| Invitation declined | The recipient refuses | The invitation declined |
| Member joined | An invitation is accepted | The invitation accepted, and the role joined into |
| Member removed | Someone removes another member | The removed account and the role it held |
| Member left | Someone leaves on their own | The role they held |
| Role changed | A member’s role changes | The role before and after |
| Access mode changed | A member moves between scoped and whole-workspace access | The mode before and after |
| Permissions changed | An individual permission switch is turned on or off | The switches before and after |
| Page access changed | A member’s assigned pages are replaced | The member, and the pages added and removed |
| Account access changed | A member’s assigned accounts are replaced | The member, and the accounts added and removed |
| Action | Recorded when | Detail carried |
|---|
| Campaign created | A campaign is created | The campaign name |
| Campaign updated | Campaign settings change | The campaign name |
| Campaign deleted | A campaign is deleted | The campaign name |
| Campaign activated | A campaign is switched on | The campaign it points at, without a name |
| Campaign deactivated | A campaign is switched off | The campaign it points at, without a name |
| Canvas saved | The campaign graph is saved | The campaign it points at, without a name |
| Action | Recorded when | Detail carried |
|---|
| Page linked | A page is linked to the workspace | The page it points at, without a name |
| Page added | A page is added | The page it points at, without a name |
| Page relinked | A page is linked again after being unlinked | The page it points at, without a name |
| Page reconnected | A page’s access is restored | The page it points at, without a name |
| Page unlinked | A page is unlinked | The page it points at, without a name |
| Page deleted | A page is deleted | The page it points at, without a name |
| Instagram connected | An Instagram account is connected | The account name |
| Instagram disconnected | An Instagram account is disconnected | The account it points at, without a name |
| Action | Recorded when | Detail carried |
|---|
| Payment started | A payment is initiated | The amount |
| Payment confirmed | A payment settles | The amount |
| Add-on top-up started | An add-on purchase is initiated | The amount |
| Invoice cancelled | An unpaid invoice is cancelled | The transaction it points at, without an amount |
| Subscription created | A subscription is created | The plan it points at |
| Plan changed | A plan or add-on set changes | The plan it points at, and which payment method was used |
- Membership and team entries are written by the team itself. Campaign, page, and billing entries are written by the feature that performed the action, which is why one list holds both.
- Some entries carry a name, captured at the time, so the record survives the thing being renamed or deleted. Others carry only a pointer to the object, by design rather than as a fallback — campaign toggles and every page action work this way — and the app shows a shortened identifier for those rows.
- A single change to a member records one entry, not one per field. Changing someone’s role also moves their access mode, and that is recorded as a role change alone.
- Every member of the team reads the same log. Access assignments do not narrow it.
- Entries are ordered newest first and grouped by day, with a count for each day.