The record of team changes

You should not have to rely on memory to answer "who made this person an admin?" or "when was that account disconnected?". The Logs screen lists the changes made in your portfolio in order, with who, what and when. This guide covers the screen, the membership action names, and how far the record goes.

⚠️ Note: Only the portfolio owner and its admins can open the Logs screen. Editors, agents and viewers never see portfolio settings, so they cannot reach it either.

Opening the screen

1. Open the account switcher and click the gear icon next to the portfolio name.
2. Click Logs in the list on the left.

Under the page title sits a one-line description: it says the screen shows who changed what and when in this portfolio. When there is nothing yet, it reads "No records yet."

The columns and how to read a row

The table has three columns:

• When — The date and time of the action. Records are sorted newest first.
• Who — The name of the person who did it. If the action was performed by the system rather than a person (a scheduled change being applied, for instance), this reads System. If the person was deleted later, the cell can be blank.
• Action — What was done. Below this cell there may be a second, smaller line: what the action was about.

That detail line takes one of three forms:

• An account's name — For account actions (connecting, changing a setting, deleting).
• Account → portfolio — For account moves; the arrow says which portfolio the account left and which it joined.
• A person's name — For membership actions: invitation, role, access and removal.

Older records may not carry this detail; then the line is not drawn and only the action name appears.

The action names you will see for the team

Every membership change is recorded under its own name:

• Invited a member — A new invitation was sent.
• Canceled an invitation — A pending invitation was withdrawn.
• Joined the team — An invitation was accepted and the membership opened.
• Changed a member's role — A member's role was updated.
• Changed a member's account access — The accounts a member can reach were updated.
• Removed a member — A member was taken out of the team.

Read together, those six lines give you your team's history: when someone joined, when their role was raised, and when they left.

Actions in the same list that are not about the team

The Logs screen is not limited to membership; other changes made in the portfolio sit in the same list. Seeing them makes team oversight easier, because the answer to "who did this?" is usually in the same place:

• Accounts and channels — Added an account, changed account settings, connected an account, disconnected an account, deleted an account, moved an account to another portfolio.
• The portfolio — Created the portfolio, changed the portfolio's name, scheduled the portfolio's deletion, called the deletion off.
• Automations and content — Created, published, enabled, disabled, trashed or permanently deleted an automation; rule and sequence actions.
• Contacts and conversations — Deleted a contact, exported contacts, assigned a conversation.
• Keys and connections — Added, changed or deleted an AI key; added, changed, deleted or tested a connection.
• Payments and plan — Created an order, an order was paid, canceled a subscription, scheduled a plan change.

An unrecognised or very old action appears as Other action.

💡 The "Exported contacts" row is especially valuable: it tells you when your customer list was downloaded, and by whom.

Paging

The records are paged. You move through them with Previous and Next at the bottom, and the "Page 2 of 7" status between them tells you where you are. The list always starts with the newest record, so you never have to page around to find today's change.

Limits of the screen

There are a few points where this screen is deliberately kept plain:

• There is no filter or search. You cannot filter the records of one person or one action type; you page through and read.
• There is no export. The records cannot be downloaded.
• In-conversation traces are not here. Who changed an assignment, added a tag or took over from an automation inside a conversation shows up in that conversation's own trace strip. See Conversation traces.
• Records are never deleted or edited. Undoing an action creates a new record; the old row stays where it is.
• The person recorded is a name, not an email. If two people share a name, you have to look at the Team screen to tell them apart.
• Records do not travel with a moved account. Audit records stay in the portfolio; the move itself is written to both portfolios.

A concrete example

A furniture shop's owner notices one morning that some records have disappeared from the contact list.

1. They open Portfolio settings › Logs.
2. In the top rows they see Deleted a contact actions dated yesterday, with the name of an employee they had made an admin in the Who column.
3. A few rows further down in the same list they also see a Changed a member's role record, and realise that person was made an admin a week ago.
4. They go to the Team screen and lower the person's role to Agent, which removes the contact-deletion permission.

Common mistakes

• Taking the logs for message history. Conversations with customers are not here; they are in the inbox.
• Reading a blank "Who" cell as an error. When the system performed the action, or the person was deleted, the cell is blank or reads System.
• Treating an old record without a detail line as incomplete. Older records may lack the detail; the action name is still correct.
• Auditing the team from the Team screen alone. The Team screen shows today; the logs show the past.

Related articles

• The Team screen
• Removing a team member
• Roles and permissions
• Conversation traces
• Limiting access per account