Working with other capabilities
Most of what makes PDF Embed worth having in the suite comes from what sits next to it. This page is the summary; each connection has its own page with the detail.
Where a connection does not exist, it is listed as such rather than left out, so you can stop looking.
#Every connection
Connects to | What you get |
|---|---|
No external account | There is no sign-in, no OAuth, no API key and no per-tenant credential. |
Page attachments | Read in the reader's own browser through the Confluence bridge, acting as that reader. Confluence enforces page and attachment permissions directly. There is no server-side copy or cache of the file. |
Public PDF links | Fetched by Capable's own URL proxy rather than by the reader's browser, because most PDF hosts will not allow a browser on another domain to read their files. The bytes pass through Capable infrastructure. This is why no per-domain admin approval is needed for arbitrary PDF links, and also why the p |
Confluence permissions requested | Read access to content, spaces, users and groups, plus attachment read, attachment write and file write so the macro can list, download and upload PDF attachments. The scope list is deliberately matched to what the old Connect app already had so the upgrade needs no fresh admin consent. |
Error reporting | Browser and server errors are reported to Sentry, declared as an analytics-category external connection. |
Legacy Connect key | The key is fixed and the build refuses to produce an app without it. |
#The pages
#A few things worth knowing
A connection needs both halves installed. In a standalone app most of these do not exist.
Anything that depends on search only reflects pages that have been indexed.
Published sites render Capable macros properly, which is where several of these pay off.
#Related
Better with company.
