DocsAPI ReferenceChangelogSupport
Concepts

Sandbox & isolation

Plugin UI renders in a sandboxed iframe and reaches Atlas only through window.atlas. It cannot read Atlas's state, DOM, or internals on its own. The SDK is the one channel.

How it works

A window, panel, or overview loads in an iframe. Before any of your code runs, Atlas puts a frozen window.atlas in place, then loads your HTML with a base pointing at your package. Every namespace checks its permission inside each call, so access is enforced method by method, not just at the edge.

Package-relative paths only

Every path your manifest names, whether an entry, an icon, or the overview, resolves inside your package and is checked to stay there. Absolute paths, parent-directory escapes, and protocol URLs are rejected.

Today's sandbox is a practical isolation layer for first-party and development plugins. Stronger isolation for untrusted third-party plugins lands with the open submission and trust model.