History & Access
Review company changes and manage which agent connections can access the company.
History & Access overview
Open History & Access in Settings. Owners and Admins can use its History and Access tabs. Members and Viewers see an access explanation.
History additionally requires an active paid subscription. On Free, events are still recorded but the journal is closed; upgrading opens entries within the available time window. Access management uses a separate role gate and remains available while the company is frozen.
Read and filter the activity history
History shows company changes from the last 30 days. Entries identify the responsible person and available details, sometimes with before/after values. Agent actions can identify the connection acting for that person. System background events and personal profile changes are excluded.
Use Show to filter prompts and categories, brands, competitors, manual scans, account settings or Campaigns and tasks. The last category includes campaigns, tasks, documents, publishing channels and library changes. Load more loads the next page when available.
For older entries, contact support. An empty filtered list means no matching visible entries, not that no activity has ever happened.
Review a member’s agent connections
Access groups credentials by company member. It shows tokens or connected apps, their access level, brand scope, deletion permission and last call when available. A token is shown by its prefix, not its secret.
Compare the scope with the work the connection should perform. For the connection owner to edit selected resources or permissions, use AI agents (MCP). Company access restrictions do not replace the underlying role, plan or resource permissions.
Revoke or restore one connection’s company access
Use Revoke access beside a token or connected app. It blocks that credential’s access to this company. It does not delete the personal token, revoke access to other companies or remove the member’s normal browser access.
Restore access removes this company-level block. The connection still needs a valid credential, membership and the original permissions. For a leaked token or an app you want disconnected everywhere, the owner must revoke it in their personal connection settings.
Block all of a member’s agent connections
Use Block all MCP for this member on the member’s card to block all current and future tokens and connected apps for this company. This also covers new connections the member creates later.
Restore MCP for this member removes the member-wide restriction. It does not remove individual credential blocks. Likewise, restoring one credential cannot override a member-wide block. Manage human membership separately in Team members.