Roles not configured correctly on Starter

Problem Statement

In our starter site there are several roles, including the Content Editor and Content Publisher, that are not configured correctly so they do not work as expected.

1. They do not support log in as, so when an admin goes to log in as a user with that role there is a login error.
2. They do not support actually editing, or publishing content as they should.

We should review the roles that come OOTB for the starter and make sure the correct permissions are granted to those roles.

We should also review the users that come OOTB for the starter and make sure they have all the needed roles to perform the activities they have been created for (editing, or viewing, or publishing, etc) and that the admin can log in as them. Please note, this may require that these users have some system roles like 'Anyone who can edit content' etc.

Steps to Reproduce

https://github.com/user-attachments/assets/fee45953-d1aa-4d15-8856-05077fab81eb

1. login to demo.dotcms.com as admin
2. sign in as Joe Contributor
3. view the error message

Acceptance Criteria

Starter site should come with specific roles that enable the OOTB users to perform the specific tasks they were created for.

Starter site should have a role and permission structure that is straightforward and complete so it is understandable by customers and prospects and can be duplicated or copied as needed

Starter site should come with specific users that are configured with the needed roles to accomplish the specific tasks those users are needed for - like Joe Contributor should be able to create content and save it, etc

dotCMS Version

latest

Severity

Medium - Some functionality impacted

Links

https://dotcms.slack.com/archives/C035XMEDQ4F/p1771613838933739

Start by reproducing the Joe Contributor login-as failure on demo.dotcms.com, then inspect the Starter site's built-in roles and users described in the issue. Done means the named users can perform their intended editing, viewing, and publishing tasks, administrators can log in as them, and the resulting role and permission structure is complete and understandable.