It is good practice to organize the content of a content management system in a way that separates different types of content in different locations and to have user groups that attach role depending rights to these locations. This fits with CoreMedia access rights, which are assigned to groups and grant rights to folders and their content, including all sub folders, to all members of that group. See Section 3.16, “User Administration” in CoreMedia Content Server Manual for details about the CoreMedia rights system.
CoreMedia Blueprint comes with demo sites that provide a proposal on how to structure content in a folder hierarchy and how to organize user groups for different roles. A more fine grained folder and group configuration can easily be built upon this base. For details on site specific groups and roles have a look at Groups and Rights Administration for Localized Content Management and for a set of predefined users for that groups and roles see Appendix - Predefined Users.
CoreMedia Blueprint distinguishes between the following types of content in the repository:
Content: These are the "real" editorial contents like Articles, Images, Videos, and Products. They are created and edited by editorial users. In a multi-site environment editors are usually working on one of the available sites and they can only access that site's content.
Navigation and page structure: These types represent the site's navigation structure - both the main navigation as well as the on-page navigation elements like collections or teasers linking to other pages. They are readable by every editorial user, but only the site manager group may maintain them.
Technical content types like options, settings and configuration: These types provide values for drop down boxes in the editorial interface, like view types. They also bundle reusable sets of context settings, for example API keys for external Services. These types are readable by every editorial user but can only be created and edited by Administrators or other technical staff.
Client code: Consists of Javascript and CSS and is maintained by technical editors.
CoreMedia Blueprint comes with a folder structure that simplifies
groups and rights management in that way that users taking specific roles only get rights to
those contents they are required to view or change. Most notably you will find a /Sites folder
which contains several sites and several other folders which contain globally used content like global or default
settings. For details on the structure of the /Sites folder have a look at
Section 6.5.1.2, “Sites Structure”.
Commonly used content is stored below dedicated folders directly at root level. Web resources like CSS
or JavaScript is stored under /Themes.
Global settings, options for editorial interfaces, and the like are stored under
/Settings.
Along with the site specific groups which are described in Groups and Rights Administration for Localized Content Management there are also groups representing roles for global permissions required by some of the predefined workflows. These workflows are especially dedicated to the publication process and are bound to the following roles:
composer-role
This site-independent group allows members to participate in a workflow as a composer, that is each member of this group may compose a change set for a publication workflow.
approver-role
This site-independent group allows members to participate in a workflow as an approver, that is each member of this group may perform approval operations within a publication workflow.
publisher-role
This site-independent group allows members to participate in a workflow as a publisher, that is each member of this group may publish the content items involved in a workflow.
For details on these groups and how to connect them to a LDAP server have a look at CoreMedia Workflow Manual.
 |  |  |
 |