English English Spanish EspañolKorea한국어
Straker»Products»Shado CMS»Features»Managing Content» User Management

User Management

Shado CMS Content Management System has a powerful role-based permissions architecture enabling inherited permissions to be applied to any object in the system. It also allows for easy integration with LDAP and Active Directory.

Users/Groups and Permissions

ShadoCMS has a very powerful user permissions architecture enabling inherited permissions to be applied to any object within ShadoCMS. The permissions model allows for users, groups and roles to be applied against objects such as sections, pages, containers or files.

Permissions can be linked to existing windows or active directory permissions utilizing our LDAP Module.

The users section in ShadoCMS is extremely powerful and comes with a pre-built Users and Permissions Function Library that empowers developers. To extend the base functionality of Shado’s user permissions you can apply the permission function in conjunction with standard ColdFusion ‘if’ statements either in your templates or in the app_templates/index.cfm

Whilst ShadoCMS inherently respects the permissions applied throughout the ShadoCMS interface and Site Tree it does not automatically apply these permissions to the "front end" of the site, ie. it will not automatically limit viewing of a specific page if a user does not have the correct permissions. There is a default mask "B" which stands for ‘browse’ which allows users to browse to pages in the live site.

ShadoCMS will automatically respect permissions applied in the ShadoCMS interface but will require a developer to code in a template or app_templates/index.cfm if they want the permission applied to a site.

Users can be members of one or more user groups, and Site Tree permissions are applied to each group. Access to the various features of ShadoCMS is controlled at the user level.

For each group, permissions can be set at the section, page or container level. Permissions are inherited from their parent unless specifically prevented from doing so.

User Group Roles and Permissions

ShadoCMS works on three general user types for managing site content – administrators, editors and publishers. Each user group has one of these roles assigned for each section or page in the Site Tree. This means for any one user group you can specify which role they have for each area of the site, right down to the individual container level.

Users are members of groups, and take on the combined permissions of all groups they are members of.


 

Here is an overview of the rights associated with each user group role:

Administrators (ShadoCMS Masters)
Section administrators have the ability to:

  • Create the site structure – sections, subsections and pages
  • Add/Modify and delete sections/pages and containers
  • Assign page owners and templates
  • Assign section and page variables
  • Re-order pages within a section
  • Translate a section (multi-language)
  • Manage permissions against a section
  • Manage the workflow notification against a section or page
  • Add/modify/delete meta data
  • Directly modify and publish content
  • Publish or decline content in the publishing workflow


Editors
Section editors have the ability to:

  • Manage meta data against a page or section
  • Commit content to the publishing workflow, but they require a publisher to approve new content before it goes live. The check-in/check-out functionality of ShadoCMS ensures they can work and save content changes as many times as they require before submitting it to the publishing queue
  • Recall content committed to the workflow queue before it is approved


Section Editors cannot:

  • Add new pages or containers
  • Modify existing section or page details


Advanced Editors
Advanced editors have the same publishing workflow permissions as editors, however they can also:

  • Add new sections, pages, and containers to the sections they have rights to
  • Modify section and page information
  • Manage section and page variables
  • Re-order pages within a section


Publishers
Publishers have the similar permissions as advanced editors, except they can also:

  • Publish or decline content submitted to the publishing workflow queue
  • Directly modify and publish content


Publishers do not have rights by default to manage section and page variables or translate sections.