Storage & data · Google Drive source
The living document from Drive, not an export of it
With the Google Drive source the spreadsheet finance maintains, the deck from last week and the diagram the design team exported render on the Confluence page from Drive itself. Your readers see the living document rather than an export, and nobody loosens sharing to make that happen.
One person connects, everyone reads
Whoever adds the macro authorises Google once and picks the file in Google's own picker. Readers open the page and see the content - no account to connect, no permission to request, no login screen for the contractor or the auditor. You publish a document instead of sending someone a link they have to be granted access to. If your policy says otherwise, an admin flips one setting and every reader authorises with their own Google account instead.
You never loosen sharing to publish
The usual way to get a Drive file in front of a wide audience is to loosen its sharing, and then it stays loose. Here the file keeps the permissions it has: the macro reads it with the access of the person who set it up, and the app itself is scoped to the files that were picked - Google's drive.file permission - not to the whole Drive. Everything else about the document is unchanged.
You get the right rendering for whatever the file is
A PDF renders as a paged document, a CSV as a table, a diagram as a diagram, and Google's own formats are exported on the way in - a Sheet arrives as a spreadsheet, a Slides deck as a PDF, a Drawing as an image. 29 of the 31 macros accept a Drive file, so you get one source for the whole pack rather than a Drive-shaped feature bolted onto one format.
You can always see what a page points at
The macro keeps the file's name, type, size and last-modified date from the moment it was picked. The editor shows which file a macro points at, and the File macro puts the size and date on its card - so a reader knows what they are about to open, and so do you, six months later, when you have forgotten which of the four spreadsheets this page uses.
Google Drive 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