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

While some of the global groups contain users directly, most of them serve only as parent groups for the site-specific groups.

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 eCommerce web presence. The roles of the Brand web presence are basically the same, and use similar names that you will easily recognize.

eCommerce

Brand web presence