Activity Log

The activity log records all significant actions taken by portal users: creating clients, changing permissions, updating settings, rotating upstream credentials, and more. Every entry captures what was done, who did it, and when.

This is distinct from the audit log, which records Docker image pull attempts through the proxy. The activity log is about admin actions; the audit log is about image access.

What is recorded

Action type	Examples
Upstream management	Created upstream, updated credentials, deleted upstream
Client management	Created client, set expiration, deleted client
Permission management	Added permission, removed permission
User management	Created user, changed password, deleted user
Settings	Updated license key, enabled SSO provider, changed settings
Cache	Cleared blob cache

Each entry includes:

• The action type and description
• The portal user who performed it
• The timestamp (UTC)

Viewing the activity log

Go to Activity Log in the portal sidebar. The activity-log:view permission is required.

Browse chronologically or search by user or action type. Entries are paginated.

GDPR actor erasure

When a portal user account is deleted, their activity log entries are anonymised rather than removed. The action records are preserved (what was done and when) but the actor is replaced with an anonymised identifier.

This satisfies both the GDPR right to erasure and the operational need to maintain an intact audit trail. You can see that an action happened without retaining the deleted user’s identity.

Difference from audit logs

	Activity Log	Audit Log
What it records	Admin portal actions	Docker image pull attempts via the proxy
Who appears	Portal user accounts	Proxy clients
Use case	Internal accountability, change tracking	Compliance, access control evidence
GDPR erasure	Actor anonymised on user deletion	Not applicable