Publishing teams

A team is a group of agents published together as one experience, fronted by a lead agent. It's published much like a single agent — with its own public handle and a page at an address like yourdomain/team/<handle>.

For how teams are built, see Agent teams.

Publishing a team

Teams use the same access controls as single agents — open, password, organization, or private/invite-only — with reusable invite links and single-use email invites. One difference from single agents:

• The payer (owner-pays vs. end-user-pays) is set once, for the whole team, and applies across it.

As with single agents, every visitor signs in with their own account — there is no anonymous access.

What end-users get

Visitors reach the whole team through one gated page and chat through the lead agent (the header shows something like "Chat via {team name}"), in the same chat-and-canvas panel as a single published agent — next to the lead's own interface, or full-size if the lead has none. The lead's interface can ask to confirm an action, just like a published agent's. Behind the scenes the lead delegates to other member agents as needed, and that delegated work is shown inline in the conversation.

• If the team has a shared team database, end-users follow the same access policies and per-user isolation there as anywhere else — they only ever see their own records in tables scoped that way.

Note

End-users of a team are always viewers — there's no promotion to editor for teams in this version. The interaction model is "talk to the lead, it delegates," not a manual teammate picker.