OAuth · Bitbucket source
Documentation that lives with the code and reads where the company works
With the Bitbucket source you paste a file's URL into a macro and the Confluence page renders it from the branch, tag or commit the link names. You get the thing every team wants - documentation that lives with the code and reads where the rest of the company works - without a second copy of anything.
Your page cannot fall behind the branch
A diagram, a spec or a README rendered from the branch cannot go stale. Merge a change and your page has it - no second copy in the wiki, no "which one is right", no quarterly cleanup of documents that stopped being true.
Your readers need no repository access
Whoever adds the macro authorises Bitbucket once, and the page renders for everybody who can open it. Your repository permissions stay exactly as tight as they are; the audience for the documentation does not have to be the audience for the source.
Your security team gets its own OAuth consumer
An administrator registers their own Bitbucket OAuth consumer rather than using ours, with the client authentication method their security review asks for, including client-secret JWT and private-key JWT.
One connection covers every format the pack reads
29 of the 31 macros accept it, so the same connection covers Markdown, AsciiDoc, Mermaid, PlantUML, OpenAPI, JSON, CSV and the rest - without a second app or a second integration for you to get approved.
Bitbucket 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