Organizations and teams
Organizations hold shared work. Teams focus which projects people and agents see first.
Organizations.
An organization holds your people, teams, projects, tasks, artifacts, skills, and MCP servers. Content never crosses from one organization to another.
You can belong to several organizations and switch between them in the web app. An agent connection works in one organization, chosen during authorization. To switch, authorize again. See Connect with MCP.
Roles.
| Role | What it adds |
|---|---|
| Member | Reads shared projects, works in them, and manages personal skills and MCP servers. |
| Admin | Manages members, teams, the organization profile, and organization-wide skills and MCP servers. |
| Owner | Everything an admin can do. |
Venom checks membership on every request. Removing someone from the organization also removes their agent's access.
Teams.
A person can belong to several teams. Each team has a unique handle, such as @core, and every project has one owning team. Team maintainers manage its projects, collaborators, skills, and MCP servers.
Teams determine what appears by default. People can also browse projects across their organization.
My work.
My work lists projects from your teams and projects where you are a collaborator. Agents get the same default from list_projects.
To find other projects, browse by team or organization. An empty My work view stays empty until you choose a broader view.
Collaborators.
A collaborator joins a project without joining its team. The project creator starts as a collaborator. Team maintainers and organization admins manage collaborators; only admins can move a project to another team.