Per-collection, per-action grants
Assign find, create, update, and delete independently for each collection and role — not one blanket permission level.
ProductWORKSPACES, ROLES & MEDIA
Build components once. Assemble pages without a ticket.
Every workspace is tenant-isolated with its own members, roles, and permissions. Engineers define the content model and templates once; editors and reviewers work within it — assembling and updating pages without needing a deploy or an engineering ticket for routine changes.
01 / ACCESS THAT MATCHES RESPONSIBILITY
Per-collection roles & permissions
Access isn't all-or-nothing. Grant find, create, update, or delete per collection and per role, so a content reviewer can approve copy without touching schema, billing, or another team's collections.
Workspace-scoped membership
Every request is bound to the caller's workspace membership, so members and data never leak across workspaces.
Auditable membership changes
Adding, updating, or removing a member is a tracked action, not a silent database edit.
02 / ONE LIBRARY, MANY SITES
Shared media, redirects, and sitemaps
Assets, redirects, and sitemaps are managed per site within a workspace, so a media library that grows with your content doesn't turn into an untraceable pile of orphaned files.
Usage-tracked media library
Upload once, and see exactly which records reference an asset before you delete it.
301–308 redirects, managed
Manage a full redirect table per site as your page inventory changes, without editing server config.
Auto-generated sitemaps
Each site's sitemap.xml reflects its current page inventory automatically as pages publish, rebuild, or retire.
INVITE YOUR TEAM
Add a role-scoped teammate.
Open a workspace and invite an editor, reviewer, or developer with exactly the access they need.