CodeHerderSearch⌘KRequest access →

Administrator briefing: visibility and trust

What every workspace member can read, what a group passes to child workspaces, and what each isolation level trusts. Your administrator signs it.

Read this page before live work starts. Your administrator signs the acknowledgement at the end.

What a member can see

Every member of a workspace reads all of its content. A role changes what a member can change. It does not change what they can read. A team is not a boundary. To restrict a project, put it in its own workspace. The full rules are in Who can see what.

What a group passes down

A role on a group reaches every workspace beneath it. Group resources inherit to each child workspace. These are agents, repositories, devices, wiki pages, workflows, integrations and variables. See Workspaces.

A device that serves several workspaces shares some components between them. See What a shared device shares.

What each isolation level trusts

Your install runs devices at two levels: isolated and unisolated.

Level and backend Where it runs What it trusts
unisolated/host Laptops only. Your organization must accept this risk in writing. The agent runs as the device user. It reads everything that user can read. Sessions and workspaces on the device share that user.
isolated/container (ch device-server --isolation isolated) Laptops, EC2 and other hosts. Each stage runs in its own container with filtered egress and scoped credentials. A device still shares one credential pool, and one git mirror for each workspace and repository.

Use neither unisolated backend to separate two workspaces that must not see each other. Give each such workspace its own device. For agents you do not trust, run the device with --isolation isolated. It puts each stage in its own unprivileged container. See Isolating agent runs on a device.

For more, see What an agent can reach on the device and Who can run code on your device.

Acknowledgement

The administrator signs this line:

I have read this briefing. I understand that every workspace member reads all workspace content, that group resources and roles pass to child workspaces, and what each isolation level trusts.

Name Date Signature

Record the signed acknowledgement in the Launch acceptance record.

Last updated

Try it on one repository for two weeks.

File a task. An agent builds it. A person reads every request. You see the cost of each task.

Try "pricing", "connect a device", or "who reviews the code"

↑↓ move · ↵ open · esc close