# Activity log

The activity log shows requests made through a workspace without recording the content handled by a tool. Every active workspace member can open **Activity** under **Gateway**.

## What each row shows

| Field | Meaning |
|---|---|
| Name | The operation or tool name |
| Actor | The workspace member or labeled credential that made the request |
| Source | The gateway or connection that handled the operation |
| Event type | The protocol operation, such as `tools/list` or `tools/call` |
| Status | Whether the request was accepted, rejected, succeeded, or failed |
| Access level | The recorded classification when one applies |
| Duration | The execution time, when available |
| Error category | A short operational category, when the request failed |
| Time | When the event occurred |

The newest events appear first. Retained actor labels keep an event attributable even if a member or label later changes.

## Filter activity

Use the controls above the log to narrow results by actor, source, status, or time period. Search can match operation names, actor labels, and an exact request ID. Filtered pages have shareable URLs, and pagination retains the selected filters.

## What is recorded

The log stores operational metadata needed to answer questions such as:

- Did the AI client reach the intended workspace?
- Which operation ran?
- Was the request allowed?
- Did it succeed or fail?
- How long did it take?

## What is not recorded

Connector Central does not store the following in the activity log:

- Prompts or conversation messages
- Tool arguments
- Tool results
- Upstream request or response payloads
- API keys, OAuth tokens, or other credentials

## Troubleshoot a connection

1. Ask the member to retry the request.
2. Open **Activity** and look for the newest event.
3. If no event appears, reconnect the client and confirm the intended workspace was selected.
4. If `tools/list` succeeds but an expected tool is absent, review the member's current workspace access.
5. If a call fails, use the operation name, status, error category, request ID, and duration when contacting support. Do not send prompts, payloads, or credentials.

## Next steps

- [Connect ChatGPT](/docs/connect-ai-clients/chatgpt)
- [Connect Claude](/docs/connect-ai-clients/claude)
- [Review the MCP server reference](/docs/api/mcp)