Logs · Help

"Who switched this automation off?" or "why was the account disconnected?" are not questions to answer by guessing. Portfolio settings › Logs keeps every administrative change made in the portfolio, with who made it and when. This guide explains how to read the three columns and what the log does and does not cover.

⚠️ This screen is open to those who can view logs: the portfolio owner and its admins. Log entries cannot be deleted or edited; there is no button in the panel to clear them.

What it is for

The log does three jobs:

Accountability. As a team grows, so do "it wasn't me" arguments. The log ends them.
Troubleshooting. If an automation worked yesterday and doesn't today, the log holds the change in between.
Remembering history. The log tells you what date you moved an account, or when you invited whom.

How to reach the screen

Open the account switcher at the top left.
Click the gear icon next to the portfolio name.
Pick Logs from the menu.

The three columns

The table is sorted newest first and has three columns.

When

The date and time of the change, formatted in your interface's time zone — not the account's.

Who

The name of the person who made the change. There are two special cases:

System — entries with no person. Work the panel does on its own looks like this: applying a scheduled plan change, processing Meta's data deletion request and so on.
Support actions — where our support team acted, the action name says so explicitly.

Someone who has left the team keeps their name in the log; removing a person does not erase their history.

Action

What was done. The action name is a plain sentence: "Connected an account", "Published an automation", "Invited a member". If the panel meets an action it doesn't recognise it writes Other action; that may be a record left from an older version or one not yet named.

Beneath the action name a small detail line sits. It takes one of three forms:

Account name — if the action concerned an account, which one (for example @nurbakery).
Account → Portfolio — on moves, which account went to which portfolio (or came from where).
Person name — on member actions, which person it concerned.

Older entries may lack that detail; then the line isn't drawn. The entry itself is still valid.

Which actions are logged

The list is long; grouped under headings:

Account actions. Adding an account, changing account settings, splitting an account by channel, moving an account to another portfolio (a separate row on each side), deleting an account.

Connection actions. Connecting an account, disconnecting.

Portfolio actions. Creating the portfolio, renaming it, scheduling its deletion, cancelling the deletion.

Team actions. Inviting a member, cancelling an invitation, joining the team, changing a role, changing account access, removing a member.

Automation actions. Creating, publishing, enabling, disabling, trashing and permanently deleting an automation. Global rules and sequences have their own rows too (created, updated, enabled, disabled, deleted).

Conversation actions. Assigning a conversation.

Contact actions. Deleting a contact, exporting contacts.

Media actions. Deleting a media file.

Integration actions. Adding, changing and deleting an AI key; adding, changing, deleting and testing a connection; Meta app setting and webhook verification token changes.

Plan and order actions. Creating an order, payment, cancellation, payment failure; cancelling a subscription, resuming it, downgrading to the free plan, scheduling a plan change and applying a scheduled one; updating billing details.

Data protection actions. Processing Meta's data deletion request.

Which actions are not logged

Knowing the log's boundaries matters. These are not here:

Customer messages. Messages sent and received are conversation data, not log entries; they live in the inbox.
Automation runs. A flow running for one contact doesn't show here; for that, check the automation's session log.
Sign-in and session records. Who signed in when is not on this screen.
Read actions. Who looked at which page isn't recorded; only changes are.
User settings changes. Changing your password or picking your theme is not a portfolio log entry.

Pagination

The log paginates; move through it with the Previous / Next buttons underneath, with your page number between them. There is no filter or search: the list is chronological and you walk backwards through it.

With no entries yet it reads "No entries yet." In a portfolio you just created, the first entry is usually "Created the portfolio".

A concrete example

A shop's campaign automation sends nothing on Monday morning. The manager opens Logs and sees two rows from Friday evening:

Disabled an automation — the account's name in the detail line, a team member's name in the "Who" column.
Deleted an AI key — same person, ten minutes later.

Those two rows explain the problem: the automation was switched off and the AI step's key was deleted. The manager re-enables the automation, re-adds the key, and also reviews that person's role.

Common mistakes

Looking for messages in the log. Customer conversations are in the inbox.

Looking for an automation's run history in the log. Each run of a flow is in that automation's session log, not here.

Trying to delete or edit an entry. The log is immutable; this is deliberate.

Taking "System" rows for errors. That is how the panel's own work appears.

Worrying about an "Other action" row. The panel couldn't name that action; the entry itself is valid.

Taking the When column to be in the account's time zone. It is formatted in your interface's time zone.

For the screen where team changes are made see Team and invitations, for the AI usage record see Usage, and for the source of move and delete entries see Moving an account to another portfolio.