Sharing sessions

BuildAutomaton lets you share sessions with teammates and other stakeholders so you can collaborate, review progress, and make decisions while you work with agents. Permissions help you control who has access to that session content and who can use the bridges that run agents.

Sharing sessions

Session sharing is useful because it exposes the work product without handing over the controls. Internal teammates can review implementation details, compare approaches, inspect previews, and stay aligned without needing direct bridge access.

It also works well for external stakeholders. You can share a session with a customer, partner, or reviewer so they can see progress and test a preview, while your team keeps control over the agent, bridge configuration, repositories, files on the bridge, and dev server setup.

Session permissions

Session permissions control access to an individual session. People with session access can inspect the transcript, understand the agent's decisions, review changed files, and open dev server previews that belong to the session.

Session access is useful when someone needs the context and output of the work, but does not need direct access to the bridge that produced it. They can follow progress, review implementation details, and test the preview without needing access to the underlying agent host.

  • Use session access when you want someone to review or follow along.
  • Share sessions freely when the session content is appropriate for the recipient.
  • Use bridge access only when someone should be able to control agents.

Bridge access

A bridge connects BuildAutomaton to agents running on a laptop, workstation, server, or cloud environment. People with access to a bridge can use agents over that bridge: they can create sessions, send follow ups, manage dev servers, view files on the bridge, and manage configuration for the agent environment.

Treat bridge access like access to the machine and agent it represents. If a bridge points at a developer's personal machine or private checkout, access should generally be limited to that person. If a bridge points at a team-managed cloud agent, it can be appropriate to grant broader team access.

Team bridges

Many teams set up a small number of cloud or VPC-hosted agents for shared use. These are the bridges that should usually receive general team access because they are built for shared workflows, shared configuration, and repeatable development environments.

Individual bridges are different. A bridge running on someone's laptop or personal development box should usually stay private to that person, while the sessions created from it can still be shared with others for collaboration.

See also