Last week, I attended FutureM 2016 at the Boston Innovation and Design Building. Attendees ranged from ad agency folks like myself, vendors and publishers, brand marketers, and even the press. There were back-to-back sessions, tons of pastries, and immeasurable learnings. But I figured I could distill those learnings in a few key points:
The Best Recipe for Roles
Because Sitecore security is a single system that is used to cover many bases, and because it is evaluated based on user activity, it is very easy to paint yourself into a corner. It is easy to end up with users who have insufficient privileges to perform a new activity, or worse, users who are elevated to admin because it’s “the only way” they can have sufficient rights to do their job. Both of these conditions are preventable through careful security role design.
Sitecore Security is like an onion. It has layers.
CMS security can be a complex topic, but is critical to understand when you have a rich governance model that includes multiple departments, levels of approval, translation requirements, and shared content needs. This blog series will cover the important concepts that have to be adhered to when creating your Sitecore security model to ensure content authors only have access to the features, content, and approval steps appropriate to their role in the organization.