Teams

Teams are organizational groups that help you manage access, visibility, and collaboration within your workspace.

What Are Teams?

Teams provide:

• Organizational grouping — Group users by department, function, or project
• Scoped data access — Limit visibility to team-specific data
• Collaboration boundaries — Define who works together
• Simplified permissions — Assign access by team rather than individual

Common Team Structures

Creating a Team

1. Navigate to Teams in the sidebar
2. Click Create Team
3. Enter team details:

4. Click Create

Adding Members to Teams

During Team Creation

Add initial members from the team creation dialog:

1. Search for users by name or email
2. Click to add them
3. Set their team role:
   • Lead — Can manage team settings and members
   • Member — Regular participant

After Creation

Add members to existing teams:

1. Go to Teams
2. Click on the team
3. Click Add Members
4. Search and select users
5. Assign roles
6. Confirm

Bulk Adding

To add multiple users at once:

1. Hold Cmd (Mac) or Ctrl (Windows)
2. Click each user to add
3. Click Add Selected

Team Settings

Team Profile

Update team information:

1. Open the team page
2. Click Settings
3. Edit name, description, or color
4. Save changes

Default Project Template

Set a default template for projects created within this team:

1. Go to team Settings
2. Select Default Template
3. Choose from available project templates
4. New team projects will use this template automatically

Ticket Templates

Configure default templates for support tickets created by team members:

1. In team Settings, go to Templates
2. Select a default ticket template
3. This pre-fills fields when team members create tickets

Team-Scoped Data

Knowledge Base Documents

When creating documents, you can scope them to a team:

1. Create a new Knowledge Base document
2. In Scope, select Team
3. Choose the team
4. Only team members can view and edit the document

Project Visibility

Projects can be visible to:

• Workspace — Everyone can see
• Team — Only team members can see
• Private — Only assigned members

To set project visibility:

1. Create or edit a project
2. In Visibility, select Team
3. Choose the team

Team Collaboration Features

Team Dashboard

Each team has its own dashboard showing:

• Team member activity
• Assigned tasks
• Upcoming deadlines
• Recent achievements

Team Calendar

View team-specific events:

• Sprint start/end dates
• Team meetings
• Deadline reminders

Team Reports

Generate reports scoped to the team:

• Task completion rates
• Time tracking summaries
• Support ticket metrics

Managing Teams

Editing a Team

1. Navigate to Teams
2. Click on the team
3. Click Edit
4. Modify settings
5. Save

Archiving a Team

When a team is no longer active:

1. Open team Settings
2. Click Archive Team
3. Confirm

What happens:

• Team becomes read-only
• Members retain access to existing data
• No new projects can be assigned to the team
• Team can be restored later

Deleting a Team

1. Open team Settings
2. Click Delete Team
3. Confirm understanding of consequences:
   • Team-specific data may become inaccessible
   • Projects must be reassigned
   • Knowledge Base documents may need new scoping
4. Enter team name to confirm
5. Delete

Team Permissions

Team Roles

Cross-Team Visibility

By default:

• Team members see their team's data
• Admins and Owners see all teams
• Members can belong to multiple teams

To restrict cross-team visibility:

1. Go to Settings > Roles & Permissions
2. Edit the Member role
3. Disable "View cross-team data"

Best Practices

Team Design

1. Keep it simple — Start with fewer, broader teams
2. Clear naming — Use obvious, descriptive names
3. Document purpose — Add descriptions for clarity
4. Review periodically — Merge or split teams as the org evolves

Member Management

1. Assign leads — Every team should have at least one Lead
2. Avoid over-assignment — Users in too many teams get overwhelmed
3. Offboarding — Remove departed users from teams promptly

Data Governance

1. Default to workspace scope — Use team scope only when necessary
2. Sensitive projects — Use team scope for confidential work
3. Regular audits — Review team-scoped data access quarterly

---

Next Steps

• Projects — Create team-scoped projects
• Knowledge Base — Team-scoped documentation
• Roles & Permissions — Control team access