Skip to content
All documentation

Teams

Video

Teams, roles and shared skills

2:43 · in English, with subtitlesVideo page · All video tutorials
Chapters (6)

A team is a group of people who share skills, agents, memory and MCP connections. What you keep private stays private. A team runs on its owner’s plan, and the owner’s plan sets how many people fit in it.

Roles

Each role has everything the role below it has, and adds its own.

RightViewerMemberEditorAdminOwner
See shared memory (memory.view)yesyesyesyesyes
Add memory (memory.create)noyesyesyesyes
Edit any shared memory (memory.edit)nonoyesyesyes
Delete any shared memory (memory.delete)nonoyesyesyes
See shared skills (skills.view)yesyesyesyesyes
Add skills (skills.create)noyesyesyesyes
Edit any shared skill (skills.edit)nonoyesyesyes
Delete any shared skill (skills.delete)nonoyesyesyes
See shared agents (agents.view)yesyesyesyesyes
Add agents (agents.create)noyesyesyesyes
Edit any shared agent (agents.edit)nonoyesyesyes
Delete any shared agent (agents.delete)nonoyesyesyes
See the team connections (mcp.view)yesyesyesyesyes
Use the team tools through the gateway (mcp.use)noyesyesyesyes
Add a connection (mcp.create)nonoyesyesyes
Edit a connection (mcp.edit)nonoyesyesyes
Delete a connection (mcp.delete)nonoyesyesyes
Turn single tools on and off (mcp.tools.toggle)nonoyesyesyes
Set access credentials (mcp.credentials.manage)nononoyesyes
See the member list (team.members.view)yesyesyesyesyes
Invite people (team.members.invite)nononoyesyes
Remove people (team.members.remove)nononoyesyes
Change roles (team.roles.change)nononoyesyes
Change individual permissions (team.permissions.change)nonononoyes
Change team settings (team.settings.edit)nononoyesyes
Delete the team (team.delete)nonononoyes
Manage billing (team.billing.manage)nonononoyes

The owner always has every right and cannot be restricted. A viewer sees the team’s connections but calls none of their tools.

Exceptions for one person

The role is a default, not a cage. Whoever may change permissions, which is the owner, can tick or untick single rights for one member in the dashboard under the team’s members. The owner’s own rights cannot be reduced.

Sharing and returning

“Move to a team” makes your own item the team’s: everyone in the team sees it, and members with edit rights can change it. You can always change what you moved yourself, and “Move back to private” returns it. A whole memory folder moves together. A name that is already taken in the team is refused. Someone who leaves or is removed leaves what they shared with the team, unless they returned it first.

Seats and Pro (Team)

A seat is a person in the teams the owner pays for, the owner included, counted once however many of those teams they are in. Only the plan that is billed per seat charges for seats. A new seat is billed when an invitation is accepted, pro rata for the rest of the period, and a paid seat stays paid until the period ends, so a place that frees up can be filled again at no cost until then.

Everyone else in a team whose owner is on the per-seat plan gets Pro (Team) for their own account while they are in it. Nothing is billed for that, and Billing shows it as covered through the team and its payer. After leaving, it runs out for at least two weeks before the own plan counts again. The prices and limits are on the pricing page.

The audit log

The audit log says who changed what in the team: people, roles, settings, connections and shared content. It is kept for twelve months and read by the owner and the admins, who hold the team.settings.edit right. It exists on the plan that includes it, and the pricing page says which.

Where to go next