Permissions
The granting of the ability (1) to a specific user, (2) to perform a specific action, (3) on a specific content object.
Permissions are usually granted in aggregate. For example, the Editors group has all permissions over all content. Or, Alice has publish permission on all content in the News section. Additionally, permissions on objects are often inherited from a parent object or folder, rather than being assigned directly.
Related Chapter Sections:
-
Features: What Does It Do?
Chapter 15: Determine System Requirements
The first thing to tackle in choosing a content management system is: what specifically does it do? What does it offer that others might not, and how will it fit your needs?
-
Other Development Tasks
Chapter 20: Implement the Back-End Functionality
Beyond the main back-end development tasks there's quite a few other details to be handled.
-
Verifying the Decision with a Proof of Concept (POC)
Chapter 16: Select a Content Management System
With a proof of concept, the vendor works with the actual customer team to implement some solutions to project requirements. It’s a deeper dive, where the customer can get hands-on with the system and interact with the vendor’s team
-
The Functional Question
Chapter 21: Migrate and Populate the Content
How will functional or logical aspects of the content work in the new CMS?
-
The Short List and Request for Proposal (RFP)
Chapter 16: Select a Content Management System
Once you’ve notified a handful of vendors that you’ve decided not to move forward with them, you need to prepare an RFP for the remaining vendors.
-
Policy, Standards, and Workflow
Chapter 23: Plan for Post-Launch Operations
Rules, policies, and paths for success: a website runs only as smoothly as those who create systems to ensure success.
-
Model Implementation
Chapter 20: Implement the Back-End Functionality
Remember that content model you created? It's time to convert that model into something your CMS can manage.
-
Testing the Site
Chapter 22: Test and Launch the Site
There are three axes that a QA issue can turn on when testing the site: public vs. private, absolute vs. partial, and uncontained vs. contained.