Content editors don’t need to worry about permissions as the system is tailored to them. They have access only to the pages and tools provided; they won’t see anything else.
Page element-level permissions
You can even control permissions for editing elements within a page. If you only want a single box, image or feature area to be controlled by specific individuals, then you can implement this using HTML snippets or sub-templates.
Creating pages in this way ensures that the workflow, version control and permissions can be controlled down to individual paragraphs.
We find that many projects no longer have a separate sense of intranet, extranet and website; they can all be the same site. The only thing that separates them is the permissions you assign to different types of user.
If an article requires permission to view, the hyperlink or menu simply shows a padlock icon. If you try to access it when you're not logged in, you are presented with a sign-in page.
In many cases you don't want to display links to content the user does not have permission to view; this is straightforward to implement and is covered in more detail under 'securing your menus' below.
Securing your search
Restrict content in search results by ticking a box to enable permissions on that content. Once you have ticked the box, a user will only get the search results they have permission to see.
To allow the results to be shown, but for the user to be sent to a call to action or access denied screen when they attempt access, just don't tick the enable permissions box.
Securing your menus
You can easily configure a menu so that users logging-in with different permissions will see different content in the project explorer. Many of our customers use this on their extranets to show certain information to clients and other information to suppliers.
Functionality can be developed to draw data from a CRM to drive the navigation and content available to users.
Securing general content
You can configure exactly which users and groups are able to see which specific content. This functionality simply relies on permissions being configured.
Enabling a folder password
Assign a password to a folder and access will be only be provided once that password has been entered. This functionality is very useful when you want to give out blanket access to anyone with a password.
This is useful for allowing delegates from an event to be able to access a shared resource, or for publishing resources on the web when marketing a book. A simple password is all that should be required.
Users are the heart of your content management system, making it come alive and deliver what your organisation requires.
Because we’re catering for both system users and end users, we’ve built features which are both flexible and easy to manage around user accounts.
profiles which users can edit, both through the CMS and website interface
ability to opt-in and out of system notifications
full integration with any third party user management system that has a .NET interface
full support for active directory synchronisation
user-level permissions available for any piece of content
dashboard with active widgets and collaboration feeds
Google integration for Google Mail, Docs and RSS
who's who functionality to provide searchable staff directories
When looking at user permissions, you can assign any permission to an individual user, but more commonly you would assign permissions to groups of users.
Groups make permissions easier to manage; rather than configuring permissions for every user, you can group users by their requirements.
Groups can be created in Contensis, synchronised with active directory, any existing CRM or internal database.