OAuth · Dropbox source
Your Dropbox files on the page, with no copy in the wiki
With the Dropbox source the design sources, video and archives your team has kept in Dropbox for a decade render on the Confluence page from a shared link. You get the file where the decision is written down, and no copy lands in the wiki.
Your heavy files stay where they belong
Confluence attachments are not the right home for a long video or a folder of large originals. Point the macro at the Dropbox link instead and your page plays, previews or offers the file for download while the bytes stay in Dropbox - no duplicate to keep in step.
You authorise once, and your readers sign in to nothing
The person adding the macro connects their Dropbox once; readers connect nothing. A page shared with the whole company shows the content to all of them, and nobody is asked to sign in to a service they may not even use.
One connection feeds every format
29 of the 31 macros read from it, so the design file, the spreadsheet, the PDF and the video on four different pages all come from the same connection. Your team learns where a macro gets its content once, for the whole pack.
You update the file and every page follows
Because the macro references the file rather than importing it, updating the file behind the link updates every page pointing at it. Your wiki stops being a place old copies of things go to be believed.
Dropbox 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