Teams

Organize Decision Sites by team with flexible access control

Teams let you organize members and control who can access which Decision Sites. Your organization has one Team Access Control setting (ORGANIZATION, TEAM, or OWN) that affects how all teams work.

Getting Started

What are Teams? - Overview and benefits
Quick Start - Create your first team

How Teams Work

Team Access Control - ORGANIZATION, TEAM, OWN options
Team Organization - Structure and hierarchy
Team Roles - OWNER vs MEMBER roles

Guides

When to Use Teams - Decision framework
Team Structure Patterns - Common organizational models
Best Practices - Effective team management

Reference

Access Control Options - Complete specification
Glossary - Team terminology

Troubleshooting

Common Issues - Access and visibility problems
FAQ - Frequently asked questions

Team Access Control

Your organization has ONE Team Access Control setting that affects ALL teams:

Setting	Who Can Access	Use Case
ORGANIZATION	Everyone (team membership doesn't restrict)	Full transparency, small orgs
TEAM	Only team members + owner	Regional teams, structured access
OWN	Only Decision Site owner (most restrictive)	Personal deals, maximum privacy

Important: Team Access Control is organization-wide, not per-team. All teams follow the same setting.

Team Roles

Role	Permissions
OWNER	Manage team settings, add/remove members, delete team
MEMBER	Access team Decision Sites based on TeamAccessControl setting

When to Use Teams

Good Use Cases

Multiple sales teams or regions (US-East, US-West, EMEA, APAC)
Product line segmentation (Product A team, Product B team)
Account size tiers (Enterprise, Mid-Market, SMB)
Need for access control within organization

When NOT to Use Teams

Small organization (< 10 people)
Flat structure with full transparency
Single sales team
Overhead not worth the benefit

Common Team Structures

Geographic Teams

text

Teams:
├── US-East (TeamAccessControl: TEAM)
├── US-West (TeamAccessControl: TEAM)
├── EMEA (TeamAccessControl: TEAM)
└── APAC (TeamAccessControl: TEAM)

Product Teams

text

Teams:
├── Product A (TeamAccessControl: ORGANIZATION)
├── Product B (TeamAccessControl: ORGANIZATION)
└── Product C (TeamAccessControl: ORGANIZATION)

Key Behaviors

Decision Site Assignment

Decision Sites can be assigned to a team (optional)
Each Decision Site has an owner (required) and optional team assignment
Changing team doesn't change ownership

Default Team

Every organization has one default team
Default team cannot be deleted
When teams are deleted, their Decision Sites move to the default team
Default team doesn't restrict access in Team Access Control logic

Access Control

Organization ADMIN can access ALL Decision Sites (bypasses Team Access Control)
TeamAccessControl=OWN means only owners can access (team members cannot)
TeamAccessControl=TEAM restricts to team members + owner + contacts
TeamAccessControl=ORGANIZATION allows all internal users (CREATOR, COLLABORATOR)

Need Help?

Deciding: When to use teams
Setting Up: Team structure patterns
Troubleshooting: Common issues | FAQ

Ready to create teams? Learn when to use them →