What is a Team in Troopr ?
A Team is the core organizing unit in Troopr v2. It groups the Slack channel, Jira projects, GitHub repos, and people that work together, so Troopr can coordinate around the group that actually ships work β not your entire Slack workspace.
What a Team owns
Every Team is a lightweight entity that owns:
A default Slack channel, where standups, reports, and notifications are delivered.
One or more Jira projects, which Troopr reads for status and activity.
One or more GitHub repos, which Troopr reads to know when work actually ships.
A member roster, kept in sync with the connected Slack channel or Jira project.
[!NOTE]
A single Troopr workspace can hold many Teams. Most organizations only need a handful of Teams, even if the underlying Slack workspace has thousands of members.
Why Teams exist
A Troopr workspace maps to your whole Slack and Jira install, but only a fraction of that org actually uses Troopr. Teams let you scope Troopr to just the people and projects that need it, instead of forcing an all-or-nothing rollout.
The channel, project, and repo you choose when a Team is created become its defaults - for standup and report delivery, notifications, and the issue project used by default.
What's Next
Create a Team β Set up your first Team by pointing Troopr at a Slack channel or Jira project.
Team Switcher and Defaults β See how Troopr uses your Team's defaults and how to switch between Teams.
