Atlassian · Atlassian OAuth source
Content from your other Atlassian site, on the page that needs it
With the Atlassian OAuth source the acquisition's instance, the separate business unit's site or the customer-facing instance stops being unreachable from the page that needs it. You show the file that lives there, and nobody exports, copies or reconciles two documents that started identical.
You show the file across the boundary, without a copy
Authorise an account on the other site once and a page here shows a file that lives there - the shared standard attached to a policy page, the diagram source the platform team keeps in their own instance, the spreadsheet a business unit maintains. 29 of the 31 macros accept it, so the file can be a PDF, a table, a diagram or an image. No export, no copy, no quarterly reconciliation of two documents that started identical.
You show what is attached to a Jira issue, where it was filed
Pick an issue on the other site and your page shows any file attached to it: the incident report, the signed-off spec, the dataset someone dropped on the ticket. The evidence stays on the issue where it was filed and appears in the document that discusses it.
One person authorises, every reader sees it
The person adding the macro authorises their Atlassian account; readers do not. Someone with no account on that instance - which is most of your audience, in every organisation that has two - still sees the content on the page they were already reading. If your policy says otherwise, an administrator requires every reader to authorise for themselves instead.
You skip the migration project
The usual answer to "we have two instances" is a project to merge them, or a person who copies things across by hand until they stop. Reading across is neither: your sites stay as they are, and the pages that need each other stop pretending the other one does not exist.
Atlassian OAuth is one of 13 places Macro Pack reads from
One app, one licence, one connection your admin sets up - and 12 more places a page can pull content from, whether that is a page attachment, a Git repository, an S3 bucket or your database.
See every source compared