CMS user roles and permissions, per website and per module.
Role based access control built for client work. Give each person a level for every module of every website they work on, so a client edits their own pages and a freelancer builds three sites without ever seeing a fourth.
- Skyline HomesProperty listings
- PagesDeveloper
- ContentDeveloper
- Forms & LeadsDeveloper
- Developer settingsDeveloper
- TeamViewer
Developer on 8 · Viewer on 2 across all 10 modules
- Spice RouteRestaurant
- PagesEditor
- ContentEditor
- Forms & LeadsViewer
- Developer settingsNo access
- TeamNo access
Editor on 3 · Viewer on 1 across all 10 modules
- CityCare ClinicHealthcare
Not shared with RaviNo access to any module
No access
Access levels
Four levels. Each includes the one below.
Every module of a website gets its own level, from Viewer to Admin. Each level is a bundle of permissions such as page.update, and a module you leave unset has no access at all.
Viewer
Can view
- See pages
- See forms and leads
- See who has access
Adds on Pages and Releases
- page.view
- release.view
Editor
Can edit content in Development. Includes Viewer.
- Edit pages in Development and release content
- Work leads: status, owner, notes
- See the team and invite people
Adds on Pages and Releases
- page.update
- release.create
Developer
Can change structure. Includes Editor.
- Change the structure of pages
- Work leads and build forms
- See the team and invite people
Adds on Pages and Releases
- page.create
- page.delete
- section.manage
Admin
Full control, including approvals. Includes Developer.
- Everything in pages, including approving Releases
- Everything, including deleting leads
- Invite, change access and remove people
Adds on Pages and Releases
- page.publish
- checkout.manage
- release.approve
- release.merge
The same levels apply in Development and Production. The API checks the permissions on every request; admin only hides what someone can’t use.
Client access
Give a client limited access to their own website.
Invite your client’s marketing lead with the Content editor preset. This is what they see when they sign in.
- One website, nothing else. Your other clients never appear, not even their names.
- Only what they can open. API keys, domains, the team and website settings stay out of their sidebar, and the API refuses them too.
- Edits wait in Development. Their changes reach the live site through a Release, with your approval if you turn it on.
- A sales team on leads only. The Leads only preset opens Forms & Leads and nothing else.
Organization roles
Owners and admins see every website. Members see theirs.
Your organization is your agency, with every client website inside it. Its owners and admins run all of them; everyone else is invited website by website. Being in the organization never opens another organization.
Owner
Admin on every website, and the organization itself: its name, its members, billing, transfer and deletion.Admin
Admin on every module of every website in the organization. Creates websites and sees billing.Member
Only the websites they're given, with a level for each module. Nothing else in the organization.
ApprovalAgency plan
Decide whose changes need a second look.
Turn on “Releases need approval” for a member, and their Releases wait until someone else with approval rights approves them. Leave it off and they release straight away, still recorded in the history. The website’s Admin sets it for each person, on the Agency plan.
FAQ
Questions about roles and permissions.
Who sees what, what it costs and how the checks work.
Get started
Build your next client site on mywebcms.
Start from a screenshot, give your client one simple place to run it, and ship it on any stack you like.
- Two steps to your first website:
- 1Create your workspace
- 2Add a client website
Everything that comes with mywebcms
Tap any feature to learn more.