After development has finished and testing has given the thumbs up, there comes the inevitable time on every project where the new shiny website everyone has waited for will be handed over to the business to be used in anger.
It is a very bad idea to let every content editor have access to everything. Some people aren't technically minded and shouldn't be trusted to have the power to potentially take the whole website down. Some people should only be allowed to add content, other people may need access to reports or to just review and publish content.
When handing over the website and you need to set up the roles and permissions for the content editors within the organization, you may wonder what roles do most organizations typically set-up? In today's tutorial, I'm going to cover a very standard configuration that I've seen used on many projects.
This guide is aimed at people who are new to Episerver. These roles are the bog standard roles that must project use, however, each individual company's business processes will steer the exact roles and permissions that you will need to implement.
On most projects, I will usually go and have a face-to-face conversation with the project sponsors, or, content team. Some users may be in more than one role, one person may be all roles, or there may be a separate person for each role. It’s all up to the business and it’s all customizable to the business needs.
Software Architect, Programmer and Technologist Jon Jones is founder and CEO of London-based tech firm Digital Prompt. He has been working in the field for nearly a decade, specializing in new technologies and technical solution research in the web business. A passionate blogger by heart , speaker & consultant from England.. always on the hunt for the next challenge