Set up integrations
Add integrations for the apps your team already uses: GitHub or GitLab for code, Linear or Jira for issues, Slack for updates, and Google Calendar for meetings.
You can plan directly in the workspace without integrations. If current work already lives in other apps, choose the integrations that help with the next step: inviting the team, syncing issue context, reading code activity, adding meeting context, or sharing updates.
Choose the integrations that matter now
Slack is often useful during onboarding because it makes team invitations, channel updates, and async standups easier.
Add GitHub or GitLab when code activity should feed recaps and delivery context. Add Linear, Jira, or another issue tracker when active issues should appear in planning and reporting. Add Google Calendar when meetings should help explain the workday.
Replacing an issue tracker or roadmap tool? Use Slack for invitations and updates, version control for delivery context, and initiatives for current product bets. If Jira, Linear, or Trello still owns active execution, add that issue tracker during the transition.
You can add integrations in phases. Connect the smallest set that makes the current workflow useful, then add more when the team needs them.
Browse integrations
Open an integration page for setup details.
Version control
Issue tracking
Communication
Calendar and meetings
AI assistants and coding apps
Automation
Personal and workspace integrations
Some integrations are personal. Each developer connects their own GitHub, GitLab, Linear, Jira, Google Calendar, or AI account so work is attributed correctly.
Other integrations are workspace or team level. Slack channels, custom apps, webhook subscriptions, and some app installations are configured by admins because they affect shared behavior.
When a connected issue tracker still owns execution, we follow that provider's status, priority, assignment, and visibility rules. When work is created here, manage those fields in the workspace.
Keep access narrow
Access stays scoped to each provider's grants. We use provider controls for organizations, repositories, projects, channels, and accounts.
After the first integrations are set up, create your first initiative so the workspace has a real roadmap item to plan around.