When you connect Jira to Huddle, you're authorizing access to all Jira sites (formerly called instances) associated with your Atlassian account in a single authorization step. However, you'll select which specific sites to grant access to during the authorization process.
Jira uses an Atlassian account-level OAuth authorization model with site selection. When you click "Connect Jira" and sign in through Atlassian's authorization screen, you'll see a list of all Jira sites associated with your Atlassian account and choose which ones to authorize.
This means:
Jira's approach is a hybrid model. Unlike Asana, ClickUp, and Basecamp—where a single connection automatically grants access to all workspaces—Jira lets you explicitly choose which sites to include. But unlike Linear and Monday.com, you don't need to go through a completely separate OAuth flow for each site; you can select multiple sites in a single authorization.
This gives you control over which client or organization sites you share with Huddle while keeping the connection process streamlined.
Atlassian organizes Jira access around "sites" (like yourcompany.atlassian.net). Each site can contain multiple Jira projects. When you authorize a site, Huddle gains access to all projects within that site where you have permission.
After authorization, Huddle can retrieve your issues, projects, and site information from the Jira sites you selected. We only pull the data needed to display your tasks in your Huddle dashboard.
If you need to connect additional Jira sites: