Issue Summary

Rovo’s integration setup with third-party systems (e.g., ServiceNow, Microsoft 365) requires a single user to have administrative permissions in both Atlassian and the external system to complete the OAuth authorization flow. This is not feasible for organizations where these systems are managed by different providers or teams, due to security and governance policies. This limitation blocks organizations from using Rovo integrations in cross-vendor scenarios.

Steps to Reproduce

• Step 1
  Attempt to configure Rovo integration with ServiceNow (or another third-party system) where Atlassian and ServiceNow are managed by different administrators or vendors.

• Step 2
  Proceed with the OAuth authorization flow and observe the permissions required for setup.

Expected Results

Each system’s administrator should be able to authorize only their respective side of the integration, allowing for a delegated or flexible authorization flow without requiring cross-system admin rights.

Actual Results

The integration setup requires a single user to have admin rights in both Atlassian and the third-party system. This is not possible in environments with strict vendor separation.

Workaround

Required, if there is no workaround please state:
Currently there is no known workaround for this behavior. A workaround will be added here when available