According to Wikipedia, Content Management is “... a set of processes and technologies that supports the collection, managing, and publishing of information in any form or medium.” Incorta, as a unified data analytics platform, does all of these things. This article will cover the recommended best practices for Content Management with Incorta.
We recommend that you be familiar with these Incorta concepts before exploring this topic further.
These concepts apply to all releases of Incorta.
There are different role-dependent reasons for getting your content management strategy right in Incorta.
The bottom line, regardless of role, is that managing your content right makes it easier for your users to do their job.
Incorta uses a sharing model that is similar to Google docs. You can create a folder structure and give your dashboards a home at every level within the structure. You can then share folders or dashboards with groups or individual users. When you share, you can give different privileges depending on what you want those you share with to be able to do.
With this sharing model, Incorta enables self service which translates to speed to insight for your users. This is great, but it can also lead to a spaghetti bowl of content that makes it difficult for users to find what they are looking for and for administrators to sort out and protect the content and configuration from being overwritten. The reason this can happen is that there is no role in Incorta that is allowed to see all objects in Incorta automatically.
This has both advantages and disadvantages.
|PROS - better security
|CONS - content tracking
|Every object has its own security and therefore security control is fine tuned
|Because Administrators do not necessarily see all objects, it is difficult to know what is out there and whether it is worthwhile keeping
|No one can automatically see everything
|It makes it easier to overwrite or lose content that is important when migrating
If security is very important, you should consider having multiple administrators/superRole users who manage and have access only to the Incorta objects/content that are related to their area. They would be in charge of maintaining the content for their distinct set of users.
That said, unless private content is shared with them, administrators still will not be able to see all the content in their area when logged into Incorta. Incorta provides a couple of additional tools to help administrators find content that has not been shared with them:
Your public content should be well organized with proper security rules applied so that those who should see it can quickly find what they need to do their jobs. Private content will not be strictly controlled as it is owned by individual contributors but it makes sense to have some procedures defined such that it is not overwritten or lost.
Make your analysts and other creators of private content-aware of how content is being managed and what they should do to make sure what they build is not compromised in any way. Here are the processes that we suggest you document and share with your Incorta creators.
For your public content, Incorta documentation covers the best practices for folder structure design, group, and user assignment, and sharing very well. Refer to the Manage content with folders article for recommendations. The following two images help to illustrate some of the concepts covered in the article.