nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Web Project User Roles

edgar

Hi,

I do not quite understand how the Web Project user roles (Content Manager, Content Publisher, Content Contributor and Content Reviewer) are supposed to be used.

Like the WCM Tutorial says I create a new user in Alfresco and invited this user to my Web Project in the role Content Manager.

This new user has now access to his own Sandbox in the Web Project but he also has full access to the sandboxes of the other users (like the admin user). Furthermore he can also edit content in the staging sandbox en he can even edit the Web Project settings.

What do I need to do if I want to restrict the access of all Content Managers in this project so that these users do not see any other Sandboxes but their own (including the staging sandbox) and so that they cannot edit the web project settings.

Is there any documentation about this?

regards,

Edgar

Find more posts tagged with

Comments

kvc

Edgar:

Currently, both the Content Publisher and Content Contributor roles limit the user's ability to access any sandbox other than their own. These roles also limit the ability of those users to edit Web Project settings or edit content in Staging (which should technically be disabled for all roles). All roles can "see" other user's sandboxes, though the Publisher and Contributor cannot do anything within those non-owned sandboxes.

What would you like to see here?

Kevin

edgar

Currently, both the Content Publisher and Content Contributor roles limit the user's ability to access any sandbox other than their own. These roles also limit the ability of those users to edit Web Project settings or edit content in Staging (which should technically be disabled for all roles). All roles can "see" other user's sandboxes, though the Publisher and Contributor cannot do anything within those non-owned sandboxes.

What would you like to see here?

Thanks Kevin! At present I was just looking for documentation about these roles. And maybe also about how to go about creating a new one.

Like: how would I go about creating "Web Developer" users that can edit all Web Forms in the Data Dictionary and all items in the Web Projects Space?

PS: Is there any difference then between the Content Publisher and Content Contributor roles?

PPS: I believe at present it is not possible to shield certain user groups from access to specific folders in a Web Project right? Right now our content managers can edit all content items in the Web Project, including for example the web.xml file. We only want our Web Developers (and admin) to be able to do this.

cheers,

Edgar

edgar

One more question: is the Admin user the only user that has edit rights on content items in the Staging Sandbox?

Content Managers can only edit content items in user sandboxes right?

Is there a way to create a user group that also has edit rights in the Staging Sandbox just like the Admin user? Or in fact: is it possible to create multiple admin users? Why is the admin user not part of a "administrators" system group?

Hmm, that was more then one question.. 😉

regards,

Edgar