iOrganizations has evolved: better organization mapping, Assets-driven sync, and stronger governance

[#1]

Managing customer organizations in Jira Service Management becomes increasingly difficult as the number of service projects, customers, groups, and business rules grows.

That is why we have continued evolving iOrganizations for Service Collection from a centralized administration experience into a broader organization management, synchronization, and governance layer.

At its core, iOrganizations helps administrators work with one of the most important operational concepts in this space: mappings.

A mapping is the relationship between a source and a destination organization.
It defines how users and memberships should be synchronized, reviewed, and governed.

What is new in mappings

In Standard

The Standard edition gives administrators a clearer and more controlled way to manage mappings manually.

With Standard, teams can:

• create and manage mappings from a centralized interface;
• review source and destination relationships before execution;
• preview synchronization results before applying changes;
• compare memberships and understand what will be added, removed, or kept;
• run synchronization manually when they are ready;
• use Audit Log history to review what happened.

This makes Standard a strong fit for teams that need control, transparency, and operational confidence without immediately moving to automation.

In Advanced

The Advanced edition extends mappings into a more scalable and automated model.

With Advanced, teams can:

• use Jira Assets as a source for organizations and users;
• define object sources for organizations and user membership resolution;
• reconcile Assets objects with existing Service Collection organizations;
• create missing organizations through a controlled process;
• schedule synchronization for selected mappings;
• automatically detect new or removed source objects;
• govern recurring updates with auditability and eligible rollback.

This turns mappings from a manual administration task into a more complete synchronization framework.

Jira Assets as a source of truth

One of the biggest steps forward is the ability to use Jira Assets as a source for organization management scenarios.

This is especially valuable when customers already model business data in Assets, such as:

• customers
• departments
• contracts
• products
• entitlements
• business units

Instead of maintaining Service Collection organizations manually, administrators can align them with structured data that already exists in Assets.

That means iOrganizations can help bridge the gap between business objects and actual Service Collection organization membership.

Governance and traceability

We also expanded the operational governance layer through Audit Logs.

Administrators can review:

• mapping lifecycle activity;
• synchronization history;
• added, removed, skipped, or unresolved users;
• search by user and other execution details;
• and, in Advanced, roll back the latest eligible synchronization run.

Standard or Advanced?

Standard is designed for centralized, controlled administration:
visibility, mappings, comparison, preview, manual synchronization, and audit history.

Advanced includes all Standard capabilities and adds automation:
Jira Assets-based sources, scheduled sync, auto-discovery, deeper traceability, and rollback.

iOrganizations is not just a group-to-organization sync utility.
It is designed to help administrators understand, control, synchronize, and govern Service Collection organizations at scale.

📘 Documentation:
https://idevsolucoes.atlassian.net/wiki/spaces/iorgII/overview

We would love to hear how your teams currently manage organization membership, especially when Jira Assets is already being used as a source of truth.