Decision Site

Search documentation

Search for pages in the documentation

Team Organization

How teams structure your organization and Decision Sites

Teams organize both your people and your Decision Sites. Understanding this structure helps you set up effective teams.

The Organizational Structure

Your organization has three layers:

text
Organization
├─ Teams
│  ├─ Default Team (special)
│  ├─ Team 1
│  ├─ Team 2
│  └─ Team N
├─ Members (users with organization roles)
└─ Decision Sites (assigned to teams)

The Default Team

Every organization has one special default team.

Automatic Creation

Created when:

  • Organization is first set up
  • Cannot be manually created
  • Always exists

Default properties:

  • Name: "Default Team" (can be renamed)
  • Description: "The default team for the organization" (can be changed)
  • organizationDefault: true (cannot be changed)

Cannot Be Deleted

You cannot delete the default team:

What happens if you try:

text
Action: Click "Delete Team" on default team
Result: Error message - "The default team cannot be deleted"

Why: Default team ensures there's always a team to receive orphaned Decision Sites.

Receives Orphaned Decision Sites

When you delete a team, its Decision Sites move to the default team:

Example:

text
Before deletion:
├─ Enterprise Team
│  └─ Decision Site: Acme Corp Deal
├─ SMB Team
└─ Default Team

Action: Delete Enterprise Team

After deletion:
├─ SMB Team
└─ Default Team
   └─ Decision Site: Acme Corp Deal (moved here)

Result: Decision Sites are never orphaned.

Doesn't Restrict Access

The default team has special behavior in access control:

With TEAM access control:

  • Regular teams restrict access to team members
  • Default team doesn't restrict access
  • Default team excluded from TEAM access logic

Why: Default team is a safety net, not a real access control boundary.

Default Team Membership

Common patterns:

Pattern 1: Everyone

  • All organization members added to default team
  • Acts as company-wide team
  • Useful for organization

Pattern 2: New Members Only

  • New members added until assigned to real team
  • Temporary holding area
  • Move to appropriate team once role clear

Pattern 3: Unassigned

  • People not on any other team
  • Catches people who don't fit elsewhere

You decide: Choose pattern that fits your organization.

Additional Teams

Beyond the default team, you can create as many teams as needed.

Team Creation

Who can create: Organization ADMIN only

Process:

  1. Go to Settings → Teams
  2. Click "Create Team"
  3. Enter name, description, optional logo
  4. Click "Create"
  5. You become team OWNER automatically

Result: New team appears in teams list.

Team Properties

Each team has:

Required:

  • Name: Identifies the team
  • Members: People on the team with roles (OWNER or MEMBER)

Optional:

  • Description: Explains team purpose
  • Logo: Visual identifier
  • Decision Sites: Assigned to team

Team Limits

No hard limits:

  • Can create unlimited teams
  • Teams can have unlimited members
  • Can assign unlimited Decision Sites to a team

Practical limits:

  • Too many teams creates confusion
  • Very large teams (100+ members) hard to manage
  • Consider splitting if team grows too large

Team Membership

How Membership Works

Users can be on multiple teams:

Example:

text
User: Sarah
Organization Role: CREATOR

Team Memberships:
├─ Enterprise Team (OWNER)
├─ Strategic Accounts (MEMBER)
└─ Default Team (MEMBER)

Result: Sarah can manage Enterprise Team and access Decision Sites from all three teams (depending on Team Access Control).

Adding Members

Who can add: Team OWNER or organization ADMIN

Process:

  1. Open team
  2. Click "Add Members"
  3. Select users
  4. Choose role (OWNER or MEMBER)
  5. Click "Add"

Result: Users are now team members.

Removing Members

Who can remove: Team OWNER or organization ADMIN

Process:

  1. Open team
  2. Find member
  3. Click "Remove"
  4. Confirm removal

Result: User no longer on team, loses access to team Decision Sites (if TEAM access control).

Overlapping Teams

Members can be on multiple teams:

Example:

text
User: Alex
Teams:
├─ US-East (MEMBER)
├─ Strategic Accounts (OWNER)
└─ Product A Team (MEMBER)

Decision Sites Alex can access:
- All US-East Decision Sites (team member)
- All Strategic Accounts Decision Sites (team owner)
- All Product A Decision Sites (team member)
- Plus any Decision Sites Alex owns

Use case: Cross-functional roles, matrix organizations.

Decision Site Assignment

How Assignment Works

Each Decision Site can be assigned to one team (or no team):

Properties:

  • Owner (required): User who created it
  • Team (optional): Team it belongs to

Example:

text
Decision Site: Acme Corp Deal
├─ Owner: John
├─ Team: Enterprise Team
└─ Contacts: Buyer contacts

Assigning Decision Sites

When creating:

  1. Create new Decision Site
  2. Select team from dropdown
  3. Click "Create"

After creation:

  1. Open Decision Site settings
  2. Change team selection
  3. Click "Save"

Result: Decision Site is assigned to team.

No Team Assignment

Decision Sites can exist without a team:

Example:

text
Decision Site: Personal Deal
├─ Owner: Sarah
├─ Team: None
└─ Contacts: Buyer contacts

Access with different Team Access Control:

ORGANIZATION:

  • Everyone can access (no team doesn't matter)

TEAM:

  • Only owner + contacts can access
  • No team members (because no team)

OWN:

  • Only owner can access
  • Team wouldn't matter anyway

Changing Team Assignment

You can change which team a Decision Site belongs to:

Who can change:

  • Decision Site owner
  • Organization ADMIN

Effect:

  • Immediately affects access (with TEAM access control)
  • Old team members lose access
  • New team members gain access

Example:

text
Before:
Decision Site: Acme Corp Deal
Team: US-East
Members who can access: US-East team members

Action: Change team to US-West

After:
Decision Site: Acme Corp Deal
Team: US-West
Members who can access: US-West team members

Warning: Changing teams can break access for collaborators.

Team Hierarchy

Teams are flat - there's no parent/child relationship:

What you cannot do:

text
Sales Team
├─ US-East Team (sub-team) ❌
└─ US-West Team (sub-team) ❌

This hierarchy doesn't exist.

What you can do:

text
Teams (flat list):
├─ Sales Team
├─ US-East Team
├─ US-West Team
├─ Enterprise Team
└─ SMB Team

All teams are equal level.

Workaround: Use naming conventions for logical grouping:

  • Sales - Enterprise
  • Sales - SMB
  • Sales - US-East
  • Sales - US-West

Organization Patterns

Pattern 1: Geographic Teams

Use case: Regional sales teams

Structure:

text
Teams:
├─ US-East Sales
├─ US-West Sales
├─ EMEA Sales
├─ APAC Sales
└─ Default Team

Team Access Control: TEAM

Result: Each region only sees their deals.

Pattern 2: Product Teams

Use case: Different products

Structure:

text
Teams:
├─ Product A Team
├─ Product B Team
├─ Product C Team
└─ Default Team

Team Access Control: ORGANIZATION

Result: Teams for organization, everyone can access all Decision Sites.

Pattern 3: Account Size Tiers

Use case: Enterprise vs SMB

Structure:

text
Teams:
├─ Enterprise Accounts
├─ Mid-Market Accounts
├─ SMB Accounts
└─ Default Team

Team Access Control: TEAM

Result: Each tier manages their own size category.

Pattern 4: Functional Teams

Use case: Sales, Engineering, Support

Structure:

text
Teams:
├─ Sales Team
├─ Engineering Team
├─ Support Team
├─ Marketing Team
└─ Default Team

Team Access Control: ORGANIZATION

Result: Cross-functional visibility, teams for organization.

Pattern 5: Matrix Organization

Use case: Users on multiple teams

Structure:

text
Teams:
├─ US-East Region
├─ Enterprise Tier
├─ Product A
└─ Default Team

User: Sarah
├─ US-East Region (MEMBER)
├─ Enterprise Tier (MEMBER)
└─ Product A (OWNER)

Team Access Control: TEAM

Result: Sarah can access Decision Sites from all three teams.

Team Management Responsibilities

What Team OWNERs Manage

Membership:

  • Add new members
  • Remove members who leave
  • Promote/demote roles

Settings:

  • Update team name/description
  • Upload team logo
  • Delete team (if not default)

Doesn't manage:

  • Organization-wide Team Access Control (ADMIN only)
  • Decision Site creation (needs CREATOR role)
  • Other teams

What Organization ADMINs Manage

All teams:

  • Create new teams
  • Manage all teams (bypass OWNER requirement)
  • Delete teams
  • Change organization Team Access Control

Organization:

  • Set organization-wide Team Access Control
  • Manage organization settings
  • Add/remove organization members

Scaling Team Structure

Small Organizations (< 20 people)

Recommendation:

  • Default team + 1-2 additional teams
  • ORGANIZATION access control
  • Teams for organization, not restriction

Example:

text
Teams:
├─ Sales Team
├─ Engineering Team
└─ Default Team

Access Control: ORGANIZATION
Everyone sees everything.

Medium Organizations (20-100 people)

Recommendation:

  • 3-7 teams based on function/region
  • TEAM access control
  • Clear team boundaries

Example:

text
Teams:
├─ US Sales
├─ EMEA Sales
├─ Engineering
├─ Customer Success
└─ Default Team

Access Control: TEAM
Regional privacy enforced.

Large Organizations (100+ people)

Recommendation:

  • 10+ teams
  • TEAM access control
  • Clear naming conventions
  • Regular audits

Example:

text
Teams:
├─ Sales - US-East
├─ Sales - US-West
├─ Sales - EMEA
├─ Sales - APAC
├─ Enterprise - East
├─ Enterprise - West
├─ SMB - US
├─ SMB - International
├─ Engineering
├─ Support
└─ Default Team

Access Control: TEAM
Structured access at scale.

Common Organizational Issues

"Too many teams - can't find anything"

Problem: Created team for every use case.

Solution:

  • Consolidate similar teams
  • Delete unused teams
  • Use naming conventions
  • Limit team creation

"Wrong people on teams"

Problem: Team membership out of date.

Solution:

  • Quarterly team audits
  • Remove departed employees
  • Update roles when responsibilities change
  • Document team purpose

"Decision Sites on wrong teams"

Problem: Assigned to incorrect team.

Solution:

  • Reassign Decision Site to correct team
  • Update team assignment when ownership changes
  • Default team as temporary holding

"Can't delete team with Decision Sites"

This is allowed. Decision Sites move to default team when team is deleted.

If error occurs:

  • Verify you're not trying to delete default team
  • Check you're team OWNER or organization ADMIN

Next Steps