---
title: "Name technicians in the activity log"
description: "Decide whether a client's portal activity log shows your technicians by name or by a stable pseudonym, and what the client can see and export."
url: "https://support.outpostplatform.com/client-portal/activity-log/"
product: "depot"
type: "how-to"
status: "draft"
ai_summary: "MSP plan. The portal Activity log shows the client's audit trail: what the MSP's technicians and the client's people did, sign-ins, ticket and recording links, filters, a chain check, and CSV or JSON export with hashes. Technicians appear by name by default, or as stable pseudonyms. Practice default on Settings > Client portal > Defaults, per-client override on Audit naming."
availability:
  plans: ["msp"]
  permission: "clientportal:manage"
  preview: false
source: "https://gitlab.com/outpostplatform/docs/-/edit/main/src/content/docs/client-portal/activity-log.md"
license: "CC BY 4.0"
---

# Name technicians in the activity log

People at a client with **View the audit log** see the client's own activity
log in the portal: what your technicians did in their organization, what their
own people did, and who signed in. This page shows how to choose how your
technicians are named there, and what the client can see and export.

## Before you begin

- You need `clientportal:manage`.
- The naming changes only what the client reads. The recorded entries and
  their hashes are the same either way.

## What the client sees

The portal **Activity log** lists each entry as a sentence with who, what,
and when, and links to the ticket when the entry is about one. Entries come
from:

| Who | Shown as |
| --- | --- |
| A technician working in the client from your console | Their name, or their pseudonym |
| A person signed in to the client's portal | Their name |
| Outpost itself | **System** |
| An endpoint's agent | The endpoint's name |
| Someone using a public link, such as a quote link | **Public link** |

Sign-ins, lockouts, and changes to a person's second factor or passkeys are
recorded in every organization the person belongs to. An action an AI app
took for a person shows **via AI assistant** and the app's name.

A remote session that was recorded says so, and asks the client to contact you
to see the recording.

The client can check that the log is intact, and download it as **Spreadsheet
(CSV)** or **JSON with fingerprints**. The JSON file carries each entry's
hash and the hash of the entry before it, so an auditor can check the chain
without the portal. Downloading needs **Export the audit log**.

## Choose how technicians are named

| Choice | The client sees |
| --- | --- |
| **Technicians by name** | Each technician's name. This is the default. |
| **Stable pseudonyms** | Your portal name and a number, such as `Acme IT technician #3`. Each technician keeps the same number for that client, and a number is never reused. |

### For every client

1. Select **Settings** > **Client portal**, then **Defaults**.
2. In **Technician names**, choose **Technicians by name** or **Stable
   pseudonyms**.
3. Select **Save defaults**.

### For one client

1. Select **Clients**, then **Record** on the client's row, then the **Client
   portal** tab.
2. Select **Audit naming**.
3. Choose **Use the practice default**, **Technicians by name**, or **Stable
   pseudonyms**.
4. Select **Save**.

Entries recorded before the client portal existed show **MSP technician**
rather than a name.

## Your own view

The console's audit log shows the same entries with their source, including
**MSP technician** and **Client portal**, and exports them as CSV or JSON. See
[Audit logs](/depot/audit-log/).

## Next steps

- [Portal defaults](/client-portal/defaults/)
- [Using the client portal: activity log](/portal-guide/activity-log/)