Features/Teams

Roles and permission system

Create custom roles from a set of permissions (styles, SEO, developer, publish, CMS view/write/delete) and assign them per project.

Owners can create named roles for their organization and choose which permissions each role has. A role is then assigned to a collaborator on a project. The builder shows or hides tools based on these permissions, and the same roles cap what AI agents can do through MCP for that person.

How it works

  • Role create/update: name + permissions array, per organization (owner only).
  • No role entry for a site = full access ('*').
  • Builder: builder.view needed to open the builder; builder.developer for the history panel and many developer tools; builder.publish for Publish.
  • MCP role ceiling: builder.view opens reads; builder.styles opens classes, colors, breakpoints, fonts; builder.seo opens SEO writes; builder.developer opens page, form, site, media, language writes and custom code; builder.publish and collections.publish open publishing; collections.* open CMS reads/writes/deletes. Personal data and member deletion are '*' only. Unknown operations are denied.

Limitations

  • Roles are per organization, assigned per project
  • Fixed permission list, no custom permissions

Availability

  • Works in Designer and MCP.

Related features.

No card needed

Build it today.Pay when it goes live.

Every feature is unmetered while you build. Checkout opens the first time you publish.