Scoped collaboration

Teams

Teams are dedicated collaboration and resource-sharing groups in Computer Agents. Use them to give a defined set of people access to selected projects and resources without widening access across the entire company workspace.

The team collaboration boundary

A team combines membership, role permissions, and explicit resource shares. Membership alone does not transfer ownership of a resource; the resource must be shared with the team at the required access level.

Focused collaboration

Create a stable group for the people who work together on selected projects, agents, computers, databases, and workflows.

Resource sharing

Share an existing resource with a team without widening access to every member of the organization.

Role permissions

Assign member, contributor, or admin responsibility and refine what each team role may do.

Lifecycle control

Invite and remove members, revoke invitations, change roles, and remove resource shares through one control surface.

Use organizations and teams together

Organizations are the top-level tenancy, usage, billing, and governance boundary. Teams provide narrower sharing groups for dedicated work. Select the organization first, then use teams to control who participates in each project or resource.

Primitive
Responsibility
Organization
Company membership, tenant isolation, resource ownership, usage, budgets, credits, and billing.
Team
A defined group of collaborators with role permissions and access to explicitly shared resources.

Create and list teams

Team endpoints require an eligible paid plan. The creator becomes the team administrator and can immediately invite members or add resource shares.

Create a team
Loading...
List your teams
Loading...

Roles and permissions

The platform presents four team roles. Owner access is permanent; admins can assign the remaining roles and refine the action-level permission set from the team details page.

Role
Access intent
Owner
Permanent full control of the team, permissions, shared resources, and governance.
Member
Participates in shared work, with elevated operations routed through approval.
Contributor
Can contribute to shared resources while administrative team changes remain protected.
Admin
Can manage members, invitations, resource shares, role permissions, and team settings.
The REST API preserves the original role identifiers for compatibility: create maps to Member, configure and develop map to Contributor, and adminmaps to Admin.

Invite members

Admins invite a person by email and choose the initial permission level. Invitations can be accepted only by an authenticated account using the invited email address.

Invite a contributor
Loading...
Accept a pending invitation
Loading...

Share resources with a team

Share an owned project, computer environment, agent, database, Imagine template, or metronome workflow. Choose the lowest access level that supports the team's work.

Access level
Capability
use
Use or run the shared resource without changing its configuration.
edit
Use the resource and modify its working configuration.
manage
Full team-level management of the shared resource and its access.
Share a database
Loading...

Remove access cleanly

Removing a resource share revokes the team's access without deleting the underlying resource. Removing a member revokes that person's team-derived access while preserving the team and its other shares.

Remove a resource share
Loading...

Team API endpoints

Team management is available under /v1/teams. All requests require an authenticated Computer Agents API key; administrative mutations also require team admin access.

Endpoint
Purpose
GET /v1/teams
List teams where the authenticated user is an active member.
POST /v1/teams
Create a team and add the authenticated user as its administrator.
GET /v1/teams/{teamId}
Read one team workspace.
PATCH /v1/teams/{teamId}
Rename the team or update its permission set.
GET /v1/teams/{teamId}/members
List active team members.
PATCH /v1/teams/{teamId}/members/{memberId}
Change a member permission level.
POST /v1/teams/{teamId}/invitations
Invite a person by email.
POST /v1/teams/{teamId}/resource-shares
Share an owned resource with the team.
DELETE /v1/teams/{teamId}/resource-shares/{shareId}
Remove a resource from the team.