User Permissions
VisionCMS provides comprehensive mechanisms to control user permissions. These are split into 4 categories that allow administrators to control the level of permissions based on complexity. In VisionCMS, the SuperUser role is considered the CMS administrator which provides full control over content as well as CMS security roles.
Categories:
- Content Roles: Content-related permission such as Edit, Move, Delete, Archive, etc. These are assigned to Content Groups.
- Content Groups: Allows content to be categorized by areas such as departments.
- Workflow States: Allows content publishing permissions to be divided into states. Hernando County only uses a 2 step workflow where step 1 allows adding content, and step 2 allows publishing.
- Security Roles: CMS Configuration-related permissions such as managing users, folder structures, system variables, redirects, and other application related operations.
In context, the content of a page (HCUD homepage) is assigned to a Content Group (such as Utilities). A user with a (Utilities) step 1 workflow state can add a new message on an (HCUD) page. Another user with the Page Edit Content Role (assigned to Utilities) can go in and edit this content. This or any other user with (Utilities) step 2 workflow state can see the Publish button and will be able to publish the newly added content.
This user will need to be assigned:
- Utilities - Editor (Content Role)
- Utilities - Step 1 & Step 2
County Configuration
Content Roles were created for each department to control who has editor permissions to each content group as this is considered best practice by the vendor, Granicus. An example of this is "Utilities - Editor" which allows any user on this Content Role to edit, move, archive, but not delete page content assigned to the Utilities Content Group. The same applies to the Workflow states. There are 2 steps for each Content Group which means that a department will have Step 1 for users assigned to "add" and "save" content on a page but not publish it. The user will need Step 1 and Step 2 to be able to publish content on the respective Content Group. Something to be aware of when working with Workflow states, Step 1 only requires one step, but Step 2 will have two substeps that need to be enabled for the user to have full publish permissions. The reason for this is to allow us to have more granular control over publishing permissions. An example can be assigning Step 1/Step 1 to add Page Content while Step 2/Step 1 can allow adding Content, uploading an Image to Image Central, and adding a document to Document Central. Each step can be assigned a "Publishing" privilege to each area of the CMS (Pages, Forms, Images, Documents, News, Calendars, etc.).
In regards to Security Roles, content editors do not need any CMS security permissions as these are handled by IT Techs who should already have Super User access.
Example: The below image shows a user that can add and publish content on the Utilities Content Group. If the user did not have Step 2 on "Utilities 2 Step", they would not be able to publish content.