Skip to content

Teams

A Team in GuideMode represents a group of people who work together. Teams can be imported from external providers (GitHub, Jira, Linear, Notion) or created manually. They serve as the primary way to organize people, filter dashboards, and target surveys.

Teams in GuideMode:

  • Group people together for analytics and surveys
  • Own repositories and projects
  • Receive targeted surveys for feedback collection
  • Filter dashboards to show team-specific metrics
  • Organize into groups (tribes/departments) for high-level views
Diagram
Field Type Description
name string Team display name (e.g., “Frontend Team”)
slug string URL-friendly identifier (e.g., “frontend-team”)
description string Team description (optional)
avatarUrl string Team avatar/logo URL
iconEmoji string Emoji icon (from Linear)
provider enum Source: ‘github’, ‘jira’, ‘linear’, ‘notion’, ‘manual’
groupName string Group/tribe name for organizing teams
privacy enum ‘secret’ or ‘closed’
isEnabled boolean Whether team is active (for billing limits)
isSeedData boolean Demo/seed data (excluded from billing)

Teams can be imported from various providers, each with their own team model:

Field Description
githubOrgId GitHub organization ID
githubOrgLogin Organization login (e.g., “acme-corp”)
githubOrgName Organization display name
githubTeamId GitHub team ID within the organization

GitHub teams are synced from your connected GitHub organization. They maintain their GitHub structure and can be refreshed during sync.

Field Description
jiraTeamId Jira team ID
jiraOrgId Jira organization ID
jiraSiteName Jira site name
jiraCloudId Jira cloud instance ID (for multi-site)

Jira teams are imported from your connected Atlassian workspace.

Field Description
linearTeamId Linear team UUID
linearTeamKey Team key (e.g., “ENG”, “PROD”)

Linear teams map directly to Linear’s team concept and include the short team key.

Field Description
notionDatabaseId Source Notion database ID
notionTeamValue Multi-select option value

Notion “teams” are derived from multi-select properties in your Notion databases.

Teams with provider: 'manual' are created directly in GuideMode without an external source. They’re useful for:

  • Cross-functional teams not represented in any tool
  • Temporary project teams
  • Teams that span multiple providers

Groups provide a way to organize teams into higher-level categories without creating hierarchy. They’re perfect for departments, tribes, or business units.

Diagram
  • Groups are defined by the groupName field on each team
  • Teams with the same groupName belong to the same group
  • Groups are not separate entities - just a shared label
  • Dashboards can filter by group to see aggregate metrics

People join teams with specific roles:

Role Description
maintainer Team lead, can manage team settings and members
member Standard team member

People can belong to multiple teams simultaneously:

  • A developer on both “Frontend” and “Design System” teams
  • A tech lead who’s a maintainer of their team and member of the Platform team
  • Cross-functional participants in multiple project teams

Teams can be assigned to repositories, creating ownership relationships:

Diagram

This assignment enables:

  • Filtering issues/PRs by team
  • Team-specific DORA metrics
  • Ownership visibility in dashboards

For subscription management, teams have an isEnabled flag:

State Description
isEnabled: true Team is active, counts toward subscription
isEnabled: false Team disabled (over limit), data still collected
isSeedData: true Demo data, excluded from billing counts

When you exceed your team limit:

  • Existing teams continue working
  • New teams are created as disabled
  • You can choose which teams to enable
  • Data for disabled teams is still collected

Teams track their synchronization status:

Field Description
lastSyncedAt Last successful sync from provider
githubCreatedAt When team was created in GitHub
createdAt When created in GuideMode
updatedAt Last modification in GuideMode