Embed And Manage A Browser Application

1. Open System → Embedded Applications and create a definition with a stable handle.
2. Choose inline when the application mounts into the page, or iframe when it owns a complete HTML document.
3. Open Manage files. Upload site-scoped CSS and JavaScript; iframe applications may also upload the single managed index.html entry.
4. Register the managed asset URLs and define any typed settings editors may change.
5. Add an Application Block to a page, select the application, configure its instance, review and publish.

Inline applications receive a CMS-created mount element and can inherit the surrounding page theme. Iframe applications are isolated documents served from /webblocks-applications/{handle}/index.html; the request host selects the correct site's managed entry.

The database stores the application contract. CMS core does not scan arbitrary folders and no application.json manifest is required.

Site Export/Import carries referenced application definitions and their site-scoped application files. System Backup/Restore carries the database contracts and the complete public/site tree. A conflicting handle stops import instead of silently replacing a contract used elsewhere.

Grant only what the operator needs: applications.read, applications.write, and—only for destructive work—applications.delete. Managed files use GET|PUT|DELETE /webadmin/api/sites/{site}/applications/{application}/assets/{type}/{filename}. CSS and JavaScript use safe basenames; HTML is deliberately restricted to index.html.