Teams and Collaboration

Feature Overview

The team module defines resource ownership and collaboration boundaries. When the platform is no longer used by only one person, teams are the most basic organizational unit.

It usually carries ownership relationships for the following objects:

• Members
• Agents
• Workflows
• Knowledge bases
• Model authorization
• Usage quotas

Applicable Scenarios

Team capabilities are suitable for these scenarios:

• Dividing resources by department
• Isolating data by customer, project, or business line
• Letting multiple people jointly maintain the same group of Agents or workflows
• Tracking costs and usage by team

Prerequisites

Before creating teams, we recommend clarifying:

• Which dimension the organization will use to divide teams
• Which resources need team-level isolation
• Who is responsible for managing each team

Operation Steps

Step 1: Determine Team Division Principles

We recommend prioritizing long-term stable division methods, such as:

• Department
• Business line
• Customer unit
• Cost center

Do not use short-term temporary tasks to define teams. Otherwise, later adjustment costs will be high.

Step 2: Then Decide Team Roles

Usually, at least these should be distinguished:

• Owner: responsible for the team's highest management authority
• Admin: responsible for daily team management
• Member: responsible for normal use and collaboration
• Viewer: read-only viewing

Step 3: Put Resource Ownership into Teams

Once teams are established, Agents, knowledge bases, workflows, and model authorization should gradually be included within team boundaries. This prevents later permission, cost, and audit governance from getting out of control.

Step 4: Establish Collaboration Rules

We recommend agreeing as early as possible on:

• Who is responsible for publishing apps
• Who is responsible for maintaining knowledge bases
• Who is responsible for model and cost strategies
• How resources are handed off after members leave the team

Result Validation

After the team system is established, we recommend confirming:

• Team members can see resources in their own team
• Different teams do not interfere with each other by default
• Team administrators can manage members and resources
• Resource ownership is clearly visible on list and detail pages

Value Description

The core value of the team module is:

• Giving multi-person collaboration clear boundaries
• Making resource ownership clearer
• Making costs, permissions, and audit easier to govern

Notes

• Once team division is implemented, do not frequently adjust top-level rules
• High-value models and data resources of different teams should be isolated by default
• If a resource needs to be reused by multiple teams, define a sharing strategy first instead of directly opening permissions