Background
There's no limit to the number of users that you can add to the CMS to manage content. Every user should have their own account with appropriate permissions afforded as outlined below.
User roles and permissions
Your CMS comes with predefined ‘user roles’. Each user will need to be assigned a ‘role’. Each role has different capabilities/permissions. The table below outlines the roles and the capabilities/permission each has.
Permission / Role | Contributor | Post Editor | Author | Academia Editor | Event Editor | Editor | Admin |
Push to Live | ⨯ | ⨯ | ⨯ | ⨯ | ⨯ | ⨯ | ✔ |
Delete post | ✔ | ✔ | ✔ | ✔ | ⨯ | ✔ | ✔ |
Edit posts | ✔ | ✔ | ✔ | ✔ | ⨯ | ✔ | ✔ |
Read | ✔ | ✔ | ✔ | ✔ | ⨯ | ✔ | ✔ |
Upload files | ⨯ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Publish posts | ⨯ | ✔ | ✔ | ⨯ | ⨯ | ✔ | ✔ |
Edit published posts | ⨯ | ✔ | ✔ | ⨯ | ⨯ | ✔ | ✔ |
Delete published posts | ⨯ | ✔ | ✔ | ⨯ | ⨯ | ✔ | ✔ |
Publish events | ⨯ | ⨯ | ✔ | ⨯ | ✔ | ✔ | ✔ |
Edit events | ⨯ | ⨯ | ✔ | ⨯ | ✔ | ✔ | ✔ |
Delete events | ⨯ | ⨯ | ✔ | ⨯ | ✔ | ✔ | ✔ |
Delete other pages | ⨯ | ⨯ | ⨯ | ⨯ | ⨯ | ✔ | ✔ |
Delete others posts | ⨯ | ⨯ | ⨯ | ⨯ | ⨯ | ✔ | ✔ |
Delete pages | ⨯ | ⨯ | ⨯ | ⨯ | ⨯ | ✔ | ✔ |
Delete published pages | ⨯ | ⨯ | ⨯ | ⨯ | ⨯ | ✔ | ✔ |
Delete published posts | ⨯ | ⨯ | ⨯ | ⨯ | ⨯ | ✔ | ✔ |
Edit others pages | ⨯ | ⨯ | ⨯ | ⨯ | ⨯ | ✔ | ✔ |
Edit pages | ⨯ | ⨯ | ⨯ | Academia pages only | ⨯ | ✔ | ✔ |
Edit published pages | ⨯ | ⨯ | ⨯ | ⨯ | ⨯ | ✔ | ✔ |
Publish pages | ⨯ | ⨯ | ⨯ | ⨯ | ⨯ | ✔ | ✔ |
List users | ⨯ | ⨯ | ⨯ | ⨯ | ⨯ | ⨯ | ✔ |
Remove users | ⨯ | ⨯ | ⨯ | ⨯ | ⨯ | ⨯ | ✔ |
Promote users | ⨯ | ⨯ | ⨯ | ⨯ | ⨯ | ⨯ | ✔ |
Create users | ⨯ | ⨯ | ⨯ | ⨯ | ⨯ | ⨯ | ✔ |
Edit users | ⨯ | ⨯ | ⨯ | ⨯ | ⨯ | ⨯ | ✔ |
Delete users | ⨯ | ⨯ | ⨯ | ⨯ | ⨯ | ⨯ | ✔ |
Access site settings | ⨯ | ⨯ | ⨯ | ⨯ | ⨯ | ⨯ | ✔ |
Pushing Live
Only users with the Admin role can Push to Live.
It is essential to assign appropriate permission levels to users to prevent multiple people pushing live simultaneously, especially when others have content that should not yet appear on the main website.
Example
- A Content Marketing Manager has created a new guided tour and wants to publish it live.
- Meanwhile, an Event Organiser is setting up scheduled events and needs to review these in staging before publishing.
To avoid timing conflicts, assign the Admin role to one or more individuals who have an overview of all Vepple developments. Regular CMS users should typically be assigned the Editor role.
Best Practice
When multiple teams are working on the platform, establish an internal communication process to coordinate and confirm before pushing live.
Comments
0 comments
Article is closed for comments.