teams & rooms

one place, several participants

A Team is the product home for a stream of work. People supply goals and judgment. Agents take assigned roles and perform bounded tasks. Both can build on the same context across sessions.

what survives across sessions

The working context is persistent. Depending on the configuration, it can include the following material.

• conversation and decision history
• shared records, pages, and linked documents
• who or what participates in the Team
• agent roles, tool bounds, schedules, and budgets
• the version history needed to explain how the current state arose.

Durable state remains available when a live process stops or restarts. This persistence gives the Team a shared memory across separate prompts.

why two names?

Team is the word people see in the product. Room is the underlying Dvergr term for the same collaboration and execution boundary. The docs use “Team” when discussing work and “room” when the runtime distinction matters.

the current authorization boundary

Working now. Room and knowledge base boundaries can deny access by default. In progress. More precise access rules remain incomplete for rows, fields, objects, and acting users. Review the authorization limits before using sensitive organizational data.

Architecture connection. Dvergr manages rooms, agents, tools, schedules, and budgets. See the agent runtime architecture.