Glossary
Teams terminology and definitions
Definitions of teams-related terms used throughout the documentation.
Core Concepts
Team
A group of organization members who work together. Teams can be used purely for organization, or to control who can access Decision Sites (depending on Team Access Control setting).
Example: "Enterprise Sales Team"
Key properties:
- Name
- Members with roles (OWNER or MEMBER)
- Optional description and logo
- Decision Sites assigned to the team
Related: Team Organization
Default Team
A special team automatically created for every organization. It cannot be deleted and receives orphaned Decision Sites when other teams are deleted.
Special behaviors:
- Cannot be deleted
- Receives Decision Sites from deleted teams
- Excluded from TEAM access control restrictions
- Always exists
Default properties:
- Name: "Default Team" (can be renamed)
- organizationDefault: true (cannot be changed)
Related: Team Organization
Team Access Control
Your organization's setting that determines who can access Decision Sites. It's organization-wide and affects all teams.
The three options:
- ORGANIZATION - All internal users can access all Decision Sites
- TEAM - Only team members can access team Decision Sites
- OWN - Only owners can access their own Decision Sites
Important: This is ONE setting for your entire organization. You cannot have different settings for different teams.
Who can change: Organization ADMIN only
Related: Team Access Control
Team Membership
The relationship between a user and a team. Each membership has a role (OWNER or MEMBER).
Example: "Sarah is a MEMBER of the Enterprise Team"
Key points:
- Users can be on multiple teams
- Each membership has a role
- Membership can be added or removed
Related: Team Organization
Team Roles
Team OWNER
A team member who can manage the team's settings and membership.
What OWNERs can do:
- Add or remove team members
- Promote MEMBERs to OWNER
- Demote OWNERs to MEMBER
- Change team settings (name, description, logo)
- Delete the team (except default team)
What OWNERs cannot do:
- Change organization-wide Team Access Control (needs ADMIN)
- Create Decision Sites (needs CREATOR organization role)
- Manage other teams (only their team)
Best practice: Have 2-3 OWNERs per team for continuity
Related: Team Roles
Team MEMBER
A team member who can access team content but cannot manage the team.
What MEMBERs can do:
- Access team Decision Sites (based on Team Access Control setting)
- View team membership
- See team details
What MEMBERs cannot do:
- Add or remove team members
- Change team settings
- Delete the team
- Promote or demote members
Related: Team Roles
Access Control Terms
ORGANIZATION Access Control
A Team Access Control setting where team membership doesn't restrict access. All internal users with appropriate organization roles can access all Decision Sites.
Effect:
- Everyone can see all Decision Sites
- Teams are organizational only
- No privacy between teams
Use case: Small companies, full transparency
Related: Team Access Control
TEAM Access Control
A Team Access Control setting where only team members (plus owner) can access Decision Sites assigned to their team.
Effect:
- Team membership controls access
- Privacy between teams
- Structured access
Use case: Regional teams, medium/large companies
Related: Team Access Control
OWN Access Control
A Team Access Control setting where only the Decision Site owner can access it. Team membership doesn't matter.
Effect:
- Maximum privacy
- Only owner has access
- Teams don't control access
- Collaboration difficult
Use case: Consulting firms, law firms, individual contributors
Related: Team Access Control
Organization ADMIN Bypass
The ability of organization ADMINs to access all Decision Sites regardless of Team Access Control setting.
Effect:
- ADMINs can access all Decision Sites
- Bypasses ORGANIZATION, TEAM, and OWN restrictions
- Full edit permissions
Use case: Emergency access, fixing access issues, auditing
Related: Team Access Control
Contacts Bypass
The ability to add people as contacts to a Decision Site, granting them access regardless of team membership or Team Access Control setting.
Effect:
- Contacts can access Decision Site even if not on team
- Works with all access control settings
- Explicit access grant
Use case: Cross-team collaboration, sharing with specific people
Related: Team Access Control
Organizational Terms
Organization Role
A user's role within the organization, separate from team roles.
The four organization roles:
- ADMIN - Full organization management and Decision Site access
- CREATOR - Can create Decision Sites
- COLLABORATOR - Can edit shared Decision Sites
- GUEST - View-only access to assigned Decision Sites
Key point: Organization roles are independent from team roles
Example: You can be COLLABORATOR (organization role) and team OWNER (team role)
Related: Team Roles
Decision Site
A collaborative workspace for a deal, project, or initiative. Can be assigned to a team.
Team relationship:
- Each Decision Site can be assigned to one team (or no team)
- Has an owner (user who created it)
- Team assignment affects who can access it (based on Team Access Control)
Access depends on:
- Team Access Control setting
- Team assignment
- Ownership
- Contact additions
Related: Team Organization
Decision Site Owner
The user who created a Decision Site or has been assigned ownership.
Special access:
- Always has access to their Decision Sites
- Access regardless of team membership
- Even with OWN access control
Related: Team Access Control
Orphaned Decision Sites
Decision Sites that would have no team if their team were deleted. These automatically move to the default team when their team is deleted.
Example:
Before: Decision Site on Enterprise Team
Action: Delete Enterprise Team
Result: Decision Site moves to Default Team
Why: Ensures Decision Sites always have a team and aren't lost
Related: Team Organization
Team Structure Patterns
Flat Structure
A team organization pattern with just the default team. Everyone on one team, full transparency.
Use case: Small companies (< 15 people)
Team Access Control: ORGANIZATION
Related: Team Structure Patterns
Geographic Teams
A team organization pattern based on regional locations.
Example: US-East, US-West, EMEA, APAC teams
Use case: Regional sales organizations
Team Access Control: TEAM (regional privacy)
Related: Team Structure Patterns
Product Teams
A team organization pattern based on product lines.
Example: Product A Team, Product B Team, Product C Team
Use case: Multi-product companies
Team Access Control: TEAM (siloed) or ORGANIZATION (cross-selling)
Related: Team Structure Patterns
Hierarchical Structure
A team organization pattern matching traditional management hierarchy.
Example: Sales Leadership, Enterprise Team, Mid-Market Team
Use case: Manager/rep structure
Team Access Control: TEAM
Related: Team Structure Patterns
Account Tier Teams
A team organization pattern based on account size or value.
Example: Enterprise Accounts, Mid-Market Accounts, SMB Accounts
Use case: Different processes per account size
Team Access Control: TEAM
Related: Team Structure Patterns
Functional Teams
A team organization pattern based on departments or functions.
Example: Sales Team, Engineering Team, Support Team
Use case: Department-based organization
Team Access Control: ORGANIZATION (cross-functional visibility)
Related: Team Structure Patterns
Matrix Organization
A team organization pattern with multiple dimensions (region, tier, product, etc.). Users are on multiple teams.
Example: User on US-East, Enterprise, and Product A teams
Use case: Complex organizations with multiple organizational dimensions
Team Access Control: TEAM
Related: Team Structure Patterns
Common Phrases
"Team Access Control is organization-wide"
Means: Your organization has ONE Team Access Control setting (ORGANIZATION, TEAM, or OWN) that affects ALL teams. You cannot have different settings for different teams.
"Default team doesn't restrict access"
Means: With TEAM access control, the default team is excluded from access restrictions. Decision Sites on the default team can be accessed by all organization members (similar to ORGANIZATION access).
"Teams are organizational only"
Means: With ORGANIZATION or OWN access control, teams don't control who can access Decision Sites. They're used for labeling and organization only.
"Organization ADMIN bypasses all restrictions"
Means: Organization ADMINs can access all Decision Sites regardless of Team Access Control setting, team membership, or ownership.
"Team OWNER doesn't grant Decision Site access"
Means: Being a team OWNER is about team management, not Decision Site access. Access depends on Team Access Control setting, not team role.
"Users can be on multiple teams"
Means: A user can be a member of multiple teams simultaneously, giving them access to Decision Sites from all those teams (with TEAM access control).
"Team membership and organization role are independent"
Means: Your organization role (ADMIN, CREATOR, COLLABORATOR, GUEST) is separate from your team roles. You can be COLLABORATOR (org role) and team OWNER (team role).
"Contacts bypass team restrictions"
Means: Adding someone as a contact to a Decision Site grants them access, even if they're not on the team or Team Access Control would normally restrict them.
Related Topics
- Complete access control reference: Access Control Options
- Understand team roles: Team Roles
- Learn team organization: Team Organization
- Choose your pattern: Team Structure Patterns
- Follow best practices: Best Practices