PDF Embed settings
PDF Embed is configured from the shared Capable settings surfaces rather than a tab of its own in every case. This is the complete list.
#Every setting
Setting | Level | What it does |
|---|---|---|
PDF Gallery (admin page, standalone app only | - | The app's admin entry point. In practice it contains only the Introduction panel. There are no Features, Capabilities, Approval, Permissions, Egress, Indexing or Migration sections for this app, so there is nothing to co |
Get started page | - | The post-install welcome page pointing admins at how to use Capable in the instance. |
Approved external domains (Capable Suite onl | - | Lets a site admin approve hostnames the app may reach directly instead of through the Capable proxy. Saving is admin-only and Atlassian shows a consent prompt. A PDF on an approved host bypasses the proxy and its size ca |
App licensing | - | Licensing is enforced in production. With no licence or an expired licence, every app surface including the rendered macro is replaced by a licence banner. |
Unlicensed and anonymous access | - | Signed-out readers still cannot see the document itself. |
Edition | - | PDF Embed is a Standard-edition capability. It is not held back for Advanced Suite installs. |
Space settings | - | There are none. PDF Embed has no space-level configuration of any kind. Everything is configured per macro. |
#A few things worth knowing
Settings changes can take a minute to reach other people.
Hiding a capability removes it from the navigation; macros already on pages keep rendering.
Some settings are per space and need only a space administrator.
#Related
The complete list, in one table.
