Plugins
Plugin permissions and safety
Understand the access a plugin requests, how network permissions work, and how to turn a plugin off.
The install confirmation lists the permissions a plugin requests. Read them in light of the document and workspace where the plugin will run. A plugin that draws objects needs different access from one that only reads the current selection.
| Permission | What it allows |
|---|---|
content:read |
Read the open document and selection through the plugin API. |
content:write |
Create or change document content; this includes read access. |
ui |
Open a plugin panel and exchange messages with it. The panel is a web page from the plugin's publisher and can reach the internet, whether or not the plugin has network. |
network |
Fetch from the domains named in the plugin manifest, including images the plugin inserts from a web address on one of those domains. |
export |
Export supported image data through the plugin API. |
brand:read |
Read the active workspace's brand kit. |
A plugin does not get unrestricted access to the editor. It runs through a limited API, and its network permission must name allowed domains. Still, a plugin with both document access and network access can send information to those domains. Install plugins only when you trust their publisher and understand the requested access.
A plugin without network cannot reach the network through an image. To insert a picture it passes the image itself, and Popcorn stores it in your workspace. A plugin with network can insert an image from a web address on one of its allowed domains: Popcorn downloads it once, without your sign-in and without following redirects, and stores the copy, so the design never points at that address. The image must be PNG, JPEG, WebP, GIF or SVG. Earlier versions loaded any image address a plugin gave, which let a plugin without network permission send document content to any site inside the address. That was a bug against this permission model, and it is fixed.
To stop a catalog plugin, open Plugins → Manage plugins… → Installed and clear its Enabled checkbox. Choose Uninstall to remove it from the workspace. A plugin loaded through Developer is stored only in this browser; choose Remove on the Developer tab (or on the Installed tab, where it carries a dev label). For how the manifest declares permissions, see building a plugin.