Zenex CMSDocs

Members & roles

Invite people to a blog by email and choose what they can do with a role.

Roles

  • Viewer. Reads everything in the blog and changes nothing.
  • Member. Writes and publishes content and works with Autopilot ideas. No settings, keys or members.
  • Admin. Everything in the blog, including settings, Autopilot, API keys and members.
  • Owner. Created the blog and pays for its AI and SEO usage. Admin, plus billing and deleting the blog.
PermissionViewerMemberAdminOwner
Content
View posts, drafts, calendar, categories, tags and authors
Create, edit, publish and delete posts; manage categories, tags and authors; upload images; translate; import
Autopilot
View Autopilot ideas and their progress
Add and remove ideas, write a draft now, redraw a post's cover
Settings, schedule, turning it on or off, finding ideas with SEO research
Blog
Change the blog's name and languages
Invite people, change their role and remove them
Create and revoke API keys
Account
Providers, usage and billing (the owner's account)
Turn SEO research on or off, pick the DataForSEO connection and set its spending limits
Delete the blog

Inviting people

In Settings → Members, enter an email and pick a role. The person gets access as soon as they sign in or sign up with that email; copy the invite link to send it to them. Owners and admins can change a role or remove someone at any time, and the change applies on their next click.

Each blog has one owner: the account that created it. The owner's OpenAI and DataForSEO keys (or plan) pay for the blog's AI and SEO work, which is why spending settings and billing stay with the owner.

MCP and the API

When a member connects an MCP client, it can never do more on a blog than their role allows, whatever scopes the connection asked for. Changing someone's role changes what their connection can do right away.

RoleMost an MCP connection can use
Viewercontent:read
Membercontent:read content:write content:publish content:delete media:write
Admincontent:read content:write content:publish content:delete media:write blog:write seo:write
Ownercontent:read content:write content:publish content:delete media:write blog:write seo:write

API keys belong to the blog, not to a person: admins create them with the scopes they choose.