Sharing a container

Invite existing ZeroLog users with explicit read-only or read-write access.

How a container is sharedThe owner, on Pro, Max or Ultra, invites an existing ZeroLog user by name or creates an invite link with a fixed role, an expiry of seven days by default and an optional use limit. The person who opens the link sees the owner, the container and the role before accepting. The role is read-only or read-write. When someone else can write to the workspace, the owner's personal Claude Code and Codex logins are not mounted there. The owner can change roles, remove members and revoke links, and a removed member cannot rejoin through an old link.Role you grantTwo ways to inviteOwner on Pro, Max or Ultraopens the container'ssharing panelInvite by username.Must be an existingZeroLog userCreate an invite link.Role fixed, expires after7 days by default,optional use limitPerson opens the link,sees owner, containerand role, then acceptsRead-only: view files,attach to the terminal,cannot typeRead-write: edit files,run commands.Code-execution trustOthers can write here:your personal Claude Code andCodex logins are not mountedYou can change a role,remove a member or revoke alink.A removed member cannotrejoin with an old link
Access is an explicit grant with a fixed role, and a workspace others can write to never receives your personal vendor logins.
Diagram as text
  1. The owner, on Pro, Max or Ultra, opens the sharing panel of the container.
  2. Option one: invite an existing ZeroLog user by username. A name that does not exist is refused.
  3. Option two: create an invite link. The role is fixed when the link is made. It expires after 7 days by default and can have a use limit. The person who opens it sees the owner, the container and the role before accepting.
  4. Read-only members can view files and attach to the shared terminal but cannot type.
  5. Read-write members can edit files and run commands. Treat this as code-execution trust.
  6. If someone else can write to the workspace, the owner's personal Claude Code and Codex logins are not mounted in it.
  7. The owner can change a role, remove a member or revoke a link at any time. A removed member cannot rejoin through an old link; only the owner can invite them again.

Current availability

Owners on plans with sharing (standard configuration: Pro, Max and Ultra) choose who can access a container. Read-only terminal access cannot type; read-write access permits edits and commands. Treat that as code-execution trust.

Keep personal credentials private

Invite someone by username, or create an invite link. The person must already have a ZeroLog account. A link carries a fixed role and expires after 7 days unless you choose otherwise; you can also limit how many people may use it. Whoever opens a link sees the owner, the container and the role before accepting.

Change the role, remove a member or revoke a link whenever you like. A member you removed cannot rejoin through an old link; only you can invite them again. Knowing a container ID grants nothing.

Personal native Claude Code and Codex credentials require a workspace owned by you that nobody else can write to. Keep shared work and personal vendor-account sessions in separate workspaces. When you invite someone, any Claude Code or Codex agent container of yours that has this workspace is stopped, so your personal logins are no longer mounted next to the new member.

See containers, native account setup and current plans. These are the implemented access rules, not a claim of a new two-account invitation test.