Understanding Atlassian Teams and IDP-Synced Groups

Key Concepts at a Glance

What is an Atlassian Team?

An Atlassian Team is a named collection of people that you can @mention, assign ownership to, and report on across products. Teams are visible in Answers (e.g., page owners), Orange Tracker (e.g., issue fields, on-call ownership via integrations), and provide a human-friendly handle for work coordination.

Core Capabilities

• Collaboration: @mention a Team in pages, comments, and issues to notify all members.

• Ownership and accountability: Set a Team as a service owner, component owner, or knowledge base owner to clarify responsibility.

• Work routing: Use Teams in JSM for triage queues, escalation policies (via integrations), and shared inbox notifications.

• Lightweight governance: Licensed users can create and manage Teams quickly for projects, squads, or initiatives.

Membership Models

• Manually managed Teams: Any licensed user can create and maintain membership; ideal for ad hoc collaboration.

• Verified Teams (admin-managed): App admins can create verified Teams that are connected to existing IDP groups for dynamic, automatic membership.

What is an IDP-Synced Group?

An IDP-synced group is a centrally managed set of users provisioned from Entra to Atlassian. These groups are authoritative for access control, licensing, product roles, and permission schemes. Membership is governed by enterprise policies (SCIM/SSO).

Core Capabilities

• Access and permissions: Assign product access, space/project permissions, and admin roles using groups.

• Lifecycle and compliance: Membership reflects HR systems of record; joiners/movers/leavers are updated automatically.

• Policy enforcement: Ideal for standardized security requirements and audit readiness.

How Teams and IDP Groups Differ

When to Use Each

• Use an Atlassian Team when you need a collaboration identity to route work, mention a group, or declare ownership in Orange Tracker/Answers. Great for day-to-day operations and project squads.

• Use an IDP-Synced Group when you need to grant or restrict access or implement formal permission models and audit-ready controls.

Common JSM and Confluence Use Cases

• Orange Tracker queues and escalations: Route incidents or requests to a Team responsible for a service or component; mention the Team in comments to engage responders.

• Knowledge base ownership: Set a Team as the owner of an Answers space or article set to signal accountability and streamline updates.

• Change/Release communication: @mention a Team on change records or Confluence release notes to notify all impacted members.

Governance and Good Practices

• Name clearly: Use consistent naming like “Team – Platform API” for Teams.

• Prefer verified Teams for critical services: Link to IDP groups where accuracy and continuity matter (on-call, high-severity ownership).

• Keep permissions in groups: Do not rely on Teams for access control; use IDP groups for product/space/project permissions.

How to Request or Create

1. Create or update an Atlassian Team: Licensed users can create a Team and add members. For verified Teams, contact your site/app admins to link to an IDP group.

2. Set as owner/assignee: Add the Team to service/component ownership in Orange Tracker (JSM projects) or as page/component owners in Answers/Orange Tracker (JWM projects) where supported.

3. For access/permissions: Submit a request to Identity/IT to add users to the proper IDP group and apply permissions accordingly.

FAQ