Control Capabilities

Pass capabilities to PageBuilderEditor to control which editing affordances a document exposes.

const capabilities = {
  insert: true,
  delete: false,
  duplicate: true,
  publish: false,
  bindings: false,
  aiFill: true,
};

<PageBuilderEditor
  {...editorProps}
  capabilities={capabilities}
/>

Available capabilities

Capability	Controls
insert	Section library, insert-between actions, and pasting sections
delete	Removing sections
duplicate	Duplicating and copying sections
publish	Permission signal for host save or publish affordances
bindings	Live-data binding UI
aiFill	Copilot and AI-fill affordances

Omitted keys default to true.

The editor cannot hide controls supplied through topBarRight on your behalf. Your host action component must honor the resolved publish capability.

Capabilities are not authorization

Capabilities shape the interface. They do not replace backend authorization.

The server must still reject an action when the current user, tenant, page state, or plan does not permit it. Never trust a hidden button as a security boundary.

Derive them from host policy

A useful flow is:

Host authorization and product rules
        ↓
BuilderDocument.capabilities
        ↓
PageBuilderEditor capabilities
        ↓
Visible editing affordances

Examples:

• A locked template may disable insert and delete.
• A reviewer may edit copy but not publish.
• A plan without dynamic content may disable bindings.
• A document without an AI configuration may disable AI fill.

Keep the policy in one host-owned service and pass the resolved result to the client.