From the course: Foundations of Enterprise Content Management

Centralized permissions

From the course: Foundations of Enterprise Content Management

Start my 1-month free trial

Centralized permissions

“

- [Narrator] I want to take a position on something. I firmly believe that content management is not only useful in itself, I also believe that it's totally compatible with companies that are looking to effectively transform in the modern workplace. Why do I say that? Well, there are a few reasons which we'll explore in this chapter of the course. First of all, let's talk about permissioning. I think a lot of companies struggle with this as they grow. Rather than develop a strong system, what I see is companies trying to patch up a very messy collection of obsolete mailing lists, weird shared drive architecture and so on. Developing and implementing a comprehensive centralized security schema around all company data is a very big task, but it's one that I think is completely worth the effort in the long run. And I think that the defining of content that needs to occur when setting up your CMS, is a very good stepping stone to the larger environment. There is typically going to be a way to tie your existing directory into your CMS permissions. With SharePoint as we saw earlier, you can use Active Directory Security Groups to build Permission Groups out of the box. In WordPress, you'll need a plugin. But once you have it, it greatly simplifies matters. The point is that you can use whatever you develop for your CMS as a template for the rest of your data. You're going to need to do the work sooner or later. And I think piggybacking off of the CMS work, makes a lot of sense. Effective digital transformation is going to require that you make more data at your company available in more ways to more people. You cannot do this without centralizing and rationalizing your overall enterprise permissions. And this won't benefit just your CMS by the way. Centralizing permissions means that you'll be able to break down silos of information, throughout your enterprise. You want to encourage single sign-on and system-wide federation wherever possible. If a user can log on once and get everything they need, it will be much easier for them to do their job.

Contents