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.
#Where you do it
Task | Where |
|---|---|
Approve the app's Confluence permissions | Confluence admin > Apps > Manage apps, at install or upgrade time |
Embed a PDF already attached to the page | Macro config > Types of file = Existing Page Attachment > Attached File |
#Limits that apply here
Limit | Value | What happens |
|---|---|---|
Linked PDF size ceiling | 2.5 MB | A PDF fetched from a public web address is refused above 2.5 MB and the macro shows "This PDF is too large". Attachments do not go through the proxy and are not subject to this cap. The limit is not s |
Attachment picker size | 250 attachments | The Existing Page Attachment dropdown lists at most the first 250 attachments on the page. There is no search or paging, so a PDF beyond that cannot be picked. |
#Worth knowing
The attachment picker lists at most the first 250 attachments and has no search or paging. It also includes files with a generic or missing type, so a non-PDF can be selected by mistake.
PDFs loaded from a web address pass through Capable's hosted proxy, so the file bytes transit Capable infrastructure. Attachments do not.
#Related
Better with company.
