PlugsightDocs

Review Activity regularly

A five-minute weekly check of the Activity page - what your AI did, what was blocked or failed, and sign-ins - with what to do when something looks wrong.

Activity lists everything on your account: sign-ins, changes you made in the app, and every read and write your AI apps made. A short look once a week tells you whether everything is as you expect, and catches problems while they're small. Entries are kept for one year.

How the page works, column by column: Activity log.

The weekly check

About five minutes. Use the filters at the top of the page; they combine.

1. What your AI changed

  1. Click the AI apps chip.
  2. Set Result to Succeeded.
  3. Scan for sends and changes, such as "Sent an email…" or ticket updates. Each one should be something you approved in a chat.

To find one thing, type in Search what happened…, for example a recipient's address or "Sent".

2. What was stopped

  1. Keep AI apps, and set Result to Blocked.

Blocked means one of your own safety settings stopped it and nothing happened: an account switch was off, the server was read-only, something was paused, the daily email limit was reached, or the change wasn't approved. The reason is under the badge.

A few blocked entries are normal. Many in a row, or blocked attempts you don't recognise, are worth a closer look.

3. What failed

  1. Set Result to Failed.

Failed means the service refused or didn't answer, for example an expired sign-in or a ticket that no longer exists. If the reason says to reconnect, do that on Connections. See Reconnect needed.

4. Sign-ins

  1. Click the Sign-ins chip and set Result to Any result.
  2. Check the times and IP addresses (shown under the time). Hover over a time to see it in UTC.

5. Settings changes

  1. Click the Connections, MCP servers and Settings chips in turn.
  2. Check that every switch turned on, server created or edited, API key created and limit changed was you.

What to look for

You see It may mean Do this
A send or change you don't remember approving An AI app or key used in a way you didn't expect Pause everything, then see Keep app passwords and API keys safe.
"Developer API" entries you don't expect An API key in use somewhere Find which server ("via …"), then revoke or regenerate its key.
An AI app name you don't use An app you once connected is still allowed Disconnect all AI apps on that server, then reconnect your own.
Sign-ins from times or places you don't recognise Someone may know your sign-in Change your password and Pause everything. Email info@plugsight.app.
Many blocked sends at the daily limit A routine sending more than you expected Check the routine; adjust the limit if it's right. See Stay within your limits.
Repeated failures for one account A sign-in that has expired Reconnect the account on Connections.

Make it easier

  • Name servers clearly, so "via Acme (client)" tells you at once where a request came from.
  • One server per AI app or script, so each source shows up under its own name. See One MCP server per client or purpose.
  • Remember what Activity doesn't keep: email bodies, attachments and report contents are never recorded. It shows what was done, not the content.