# What your organisation can see

HarnessLink keeps your work private unless an owner of your organisation turns something on. This guide lists what other people in a Team or Enterprise organisation can see about you, what stays private, and how you are told when that changes. Free and Pro accounts have no sharing at all: nobody else is in your organisation.

## Always visible

Every member of an organisation sees the members list: each member's email, role and team, and the organisation's seat count. That is all owners and admins see about you by default.

## What an owner can turn on

Settings › Organisation › Visibility has five switches. Every one is off for every organisation, including organisations created before this setting existed. Only an owner can change them; admins cannot. Each switch shows exactly one thing:

| Switch | What owners and admins then see |
| --- | --- |
| Devices | The name, platform, harnesses, version and last active time of each of your devices, and whether its HarnessLink client is flagged as modified (it does not match a signed release) |
| Spend | Your model spend and token count this month, and your team's total against its team budget |
| Agent inventory | The names of the agents and skills on your machines, never their content, and which onboarding pack items you installed or removed |
| Activity counts | Your prompt, session and memory counts in the team digest email |
| Audit detail | The names of your artifacts and devices in the organisation's audit logs |

While a switch is off, the matching page or API answers that it is private (`403 visibility_off`), the team digest names only how many members there are, and audit lines about your artifacts or devices keep the action, who did it and when, but not the names.

## Team memory

Memory is per person by default. An owner can share a project's memory: then every member can read the memory entries saved in that project, each labelled with who wrote it, on the Team page and through `memory_search` / `memory_get` in any harness. Everything in other projects stays private to you. A project is matched by its memory folder name, so your entries are shared only when your project's folder name matches the shared one. Settings › Organisation lists the shared projects and marks the ones that include your memory. If you leave the organisation, your entries stop being served.

## Onboarding pack

An owner or admin can pick shared skills, agents and MCP servers that `hnl` installs on every member's machine (Team › Onboarding). A pack never carries a secret: MCP settings are 1Password references or environment variable names, resolved on your machine. You can see what it installed with `hnl team pack` and remove an item with `hnl team pack remove <name>`; your machine reports that it installed or removed each item. Owners and admins see only how many machines did; who did what needs the Agent inventory switch. An item the organisation marks as required by policy cannot be removed.

## What never leaves your account

Your prompts, session transcripts, history, runs and memory outside shared projects are never shown to an owner or admin. No setting turns them on.

## How you are told

Every member sees "Visible to your org" on the Team page and in Settings › Organisation, listing exactly what is switched on. When an owner changes a switch or shares a project's memory, every other member gets an email and a notice on those pages until they dismiss it. Every change is also recorded in the organisation's audit log.

## Policies are separate

Organisation policies (tool rules, limits and instructions) work the same with every switch off. A blocked tool call is still recorded with the tool and rule names, never the call's arguments; while Audit detail is off, the policy audit leaves out other members' device names.