Atlassian Integration Overview

The ObserveID Atlassian integration provides a REST API–based connector that enables centralized visibility, governance, and control over Atlassian accounts, access to the Jira app and the Confluence app, and entitlements. It supports secure data aggregation, access analytics, and access governance, with optional extensions for full lifecycle management and policy-driven access control.

The current version of the integration operates on the Jira REST API, which defines the Jira data model and provides access to standard, out-of-the-box operations. The integration also incorporates additional security-focused capabilities exposed by the Organization REST API and the User Management REST API, enabling the creation of a centralized, organization-wide administration layer.

Base configuration

The initial setup of the integration enables data aggregation and synchronization. To support full read-write functionality, additional configuration is required to align the integration with the organization’s business context, security policies, and compliance requirements.

The base configuration includes the following steps:

  1. Required prerequisites must be configured in Atlassian for ObserveID.
  2. Connection parameters must be configured in ObserveID for Atlassian.
  3. The initial data load from Atlassian to ObserveID must be completed successfully.

Baseline capabilities

Once the base integration setup is complete, the following standard read-only capabilities are available:

  • Aggregation and synchronization of identity, access, and entitlement data based on the baseline schema.
  • Access analytics and risk analysis across users, projects, groups, project roles and issues (tickets).
  • Access reviews and certification, provided that a ticketing system is integrated.

Optional configuration

Additional configuration enables read-write and governance capabilities, including:

  • Identity lifecycle management, which requires configuration of Atlassian account correlation logic and customization based on account types, such as user accounts, privileged accounts, service accounts, firecall accounts, orphaned accounts.
  • Access control and account administration, which require configuration of Atlassian account attributes through provisioning rules.
  • Automated access provisioning for onboarding/reinstatement scenarios, which requires configuration of the birthright access assignment.
  • Automated access termination for offboarding scenarios, which requires configuration of the leaver rule.
  • Other custom integration operations, driven by specific business or security requirements.

The Atlassian integration enables tightly controlled user provisioning and de-provisioning, role-based access control (RBAC), and real-time synchronization of group memberships, Jira projects, and issues (tickets). This approach reduces the risk of unauthorized access while ensuring auditability, policy compliance, and operational consistency at scale.