Signed-out readers on a public page see "Sign in to view this PDF" or "PDF unavailable" instead of t
What you are seeing
Signed-out readers on a public page see "Sign in to view this PDF" or "PDF unavailable" instead of the document.
#Why it happens
Signed-out visitors are never issued a Capable access token, so the app cannot fetch the file for them, whether it comes from a link or an attachment. The macro itself still renders.
#What to do
Expect this on externally shared or anonymous-access spaces. There is no configuration that changes it. If the document must be visible to the public, publish the page to a Capable Site instead, where the PDF is baked into the published output.
#Settings involved
Setting | Where | What it does |
|---|---|---|
Unlicensed and anonymous access | Built into the macro registration | - |
#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 |
#A few things that catch people out
Signed-out readers never see the document, on any source, even on a public page.
A PDF behind a login, a signed URL, a firewall or a bot manager may fail even though the reader's own browser can open it.
#Related
"This PDF is too large"
A PDF loaded from a web address is fetched through Capable's proxy, which refuses anything
"The website hosting this PDF blocked the request."
The file sits behind a login, a signed or expiring URL, a firewall or a bot manager. The p
Export and published sites
The rest of this family.
Found it? Good.
