The heart of the Team edition is the team space: a shared resource library where templates and standards documents are maintained centrally, so every member — and every AI tool they use — starts new projects from the same place.

Prerequisites

Every member has registered an AgileBuilder account (SSO sign-in; first sign-in auto-creates a personal space)
Writing to a team space (adding resources, adding members, etc.) requires a Trial or Pro subscription; free team spaces cannot add members
Pricing: China ¥199/seat/year; Global $49/user/year. The Trial lasts 14 days, with team spaces capped at 10 seats during the trial

Step 1: Create a team space

Sign in to the console (China: https://app.agilebuilder.cn; Global: https://app.agilebuilder.net) and create a team space under space management (it lives alongside your personal space — they don't affect each other).

The creator automatically becomes the space's owner.

Step 2: Invite members

Invite members by email from the space settings. Invitees receive an invitation notification and join once they accept it.

Each member is assigned one of three roles:

Role	Description	Default permissions
Owner	The space creator	All permissions, including danger-zone operations such as transferring, archiving, resetting, and deleting the space
Admin	Space manager	Resource management + space settings + member management + permission configuration + log viewing; no danger-zone operations
Member	Regular member	View and use resources in the space; can create/edit/delete resources

Role permissions can be fine-tuned per permission point in space settings (e.g. whether members may edit resources or view operation logs). The table above shows the system defaults.

Step 3: Build the shared team template library

Maintain two kinds of shared resources in the team space (same as Pro — via the console or the CLI):

Templates: the team's standard project skeletons, pointing to Git repositories (branch and subdirectory supported)
Docs: coding standards, architecture conventions, technology-selection notes, etc., exposed to AI tools over MCP

ag space use <team-space-id>

ag res add template \
  --name team-service \
  --git-url https://github.com/your-org/service-template.git \
  --branch main \
  --tags "service,standard"

ag res add doc \
  --name coding-standards \
  --file ./docs/coding-standards.md \
  --format markdown

Step 4: Each member signs in from their own CLI

Every member signs in and selects the space independently on their own machine:

ag login                       # each member completes SSO authorization
ag space list                  # team spaces they belong to are listed
ag space use <team-space-id>   # switch to the team space
ag res list                    # see the shared team templates and docs
ag create <resource-id> --target ./new-service --var appName=new-service

Once members configure MCP (see MCP Integration), the AI tools they use — Cursor, Claude Code, and so on — read the very same templates and standards docs from the team space. Humans and AI start from the same place.

Team vs. Pro at a glance

	Pro (personal space)	Team (team space)
Members	Fixed at 1 seat	Per-seat subscription, variable
Member & role management	None	Three roles: owner / admin / member
Permissions & operation logs	None	Permission-point configuration, space operation logs
Resource library	Personal templates	Team-shared template library
Price (China)	¥199/year	¥199/seat/year

Everything else — console operations, CLI commands, template format, MCP integration — is identical. Every flow in the Pro quickstart applies to a team space as-is.

Next steps

Cloud Spaces — the space model and permissions in depth
Billing & Subscription — seats, renewal, and upgrades
Core Concepts — the overall model of resources, templates, and MCP