CoreMedia Blueprint provides some default users and groups that represent typical roles in an editorial staff. There are technical users with repository wide permissions and editorial users whose permissions are predominantly limited to a particular site or web presence (aside from a few exceptions like home folder access). The editorial users and groups are only available if you activate the particular extension. Depending on your specific processes and roles, the default groups may be a more or less useful starting point for a production systems. The users, however, are meant as examples only. You are supposed to replace them with users that match your actual staff. The password of all default users is the same as the name.
In the Blueprint workspace you will find some test-data/users
directories (one global and some in the extensions). The XML files in those directories declare the default users,
groups and rules. They can be imported with the restoreusers command line tool. For the
initial setup of your systems, you can adapt those files to your needs. The test-data/content
sets provide home folders with suitable editor preferences documents for the users.
The following tables show the most important default users and groups in detail.
Global
| Group name | Description |
|---|---|
| staff | Root group, essential common read permissions, home folder access |
| administratoren | All possible permissions |
| developer | All possible permissions but user authorization |
| global-manager | Editorial permissions for global themes and settings |
| composer-role, approver-role, publisher-role | Publication workflow roles |
Table 9.14. Global groups
While some of the global groups contain users directly, most of them serve only as parent groups for the site-specific groups.
| User name | Group | Description |
|---|---|---|
| Adam | administratoren | Administrator: IT operations, configuration, user authorization, workflow maintenance, recovery, performance analysis |
| Teresa | administratoren | Online Marketing Manager: Analytics analysis, campaign management, supervision |
| Dave | developer | Developer: Feature development, template development, performance tuning |
| Amy | asset-manager | Asset Manager: managing digital assets |
Table 9.15. Global users
Since user and group names are unique within one repository, they differ for the members of the various web presences of Blueprint. The following users and groups reflect the e-Commerce web presence. The roles of the Brand web presence are basically the same, and use similar names that you will easily recognize.
e-Commerce
| Group name | Description |
|---|---|
| global-site-manager | All permissions for a web presence |
| manager-en-US | Editorial permissions for a site, read rights for the master site |
| online-editor-en-US | Finegrained permissions for his particular tasks |
Table 9.16. Site specific groups e-Commerce
| User name | Group | Description |
|---|---|---|
| Rick | global-site-manager | Global site manager: organization of internal processes |
| Peter, Piet, Pedro, Pierre (for their respective regions) | manager-en-US, manager-de-DE, manager-es-ES, manager-fr-FR | Local content manager: management of dynamic content, targeting rules, A-B-testing, topic pages for their particular regions |
| George | online-editor-en-US | Online editor: writing articles, creating slideshows, editing images, tagging contents |
Table 9.17. Site specific users e-Commerce
Brand web presence
| Group name | Description |
|---|---|
| global-site-manager-c | All permissions for a web presence |
| manager-c-en-US | Editorial permissions for a site, read rights for the master site |
| online-editor-c-en-US | Finegrained permissions for his particular tasks |
Table 9.18. Site specific groups Brand web presence
| User name | Group | Description |
|---|---|---|
| Rick C | global-site-manager-c | Global site manager: organization of internal processes |
| Peter C, Piet C, Pedro C, Pierre C (for their respective regions) | manager-c-en-US, manager-c-de-DE, manager-c-es-ES, manager-c-fr-FR | Local content manager: management of dynamic content, targeting rules, A-B-testing, topic pages for their particular regions |
| George C, Marc C | online-editor-c-en-US | Online editor: writing articles, creating slideshows, editing images, tagging contents |
Table 9.19. Site specific users Brand web presence
 |  |  |
 |