Understanding Teams Fundamental Concepts

​

What are Teams?

• Determine resource access (workspaces, agents, tools)
• Could link users and give access to workspaces through team membership

​

Architecture

Users
  ↓
Teams (member : controls access)
  ↓
Workspace (organizational container)
  ↓
Collection (document storage)
  ↓
Documents

​

Key relationships

1. Team → Members: A team contains users
2. Team → Workspaces: A team grants access to one or more workspaces
3. Workspace → Team: Each workspace is associated with exactly one team
4. User → Multiple Teams: Users can be members of multiple teams

• Scalability: Manage access for groups instead of individuals
• Maintainability: Update once (team membership) instead of updating every workspace
• Organization: Mirror your company structure (departments, projects, functions)

​

Team Types

​

1. Company Team

• Automatically created when a company is created
• Includes ALL company users automatically
• Cannot be deleted - exists as long as the company exists
• Membership is automatic - users added when they join the company
• Exactly one per company

• Company-wide shared resources
• General documentation accessible to all employees

​

2. Private Team

• Automatically created when a user joins
• Single member only - the user who owns it
• Cannot be deleted - exists while user account exists
• Cannot add other members - strictly personal
• Exactly one per user

• Private agent configurations
• Personal workspace isolation

​

3. Custom Team

• Manually created by Admins through Admin Panel
• Custom membership - Admins explicitly add/remove members
• Can be deleted by Admins
• Flexible membership - any number of users
• Can be SCIM-synced with external groups

• Project teams (“Project Phoenix Team”)
• Departmental teams (“Engineering”, “Sales”, “Product”)
• Cross-functional workgroups (“Security Committee”)
• Client-specific teams (“Client ABC Team”)
• Temporary collaboration groups

​

Type comparison