Solved the issue by adding Create, Change, Delete, Publish access rights on the Extension Data Container node but is this really the right way to go? The WebAdmin user does not has these these settings applied but still can create and edit functions and I think this is because they are added as Composer administrators so obviously Composer solves the issue somehow for that group.

Can someone shine some light on this or direct me to documents explaining this?

HI Tobias

No, you don't need to re-assign access rights on the Extension Data Container, it should be handled by Composer itself. I think your problem may depend on the issue with the cache notifying for Composer.

Composer has a known issue regarding the load balancing environment, which may cause that the changing of Composer settings (i.e. functions settings like name and access rights) in admin mode doesn't raise any cache notifying for the change in other servers.

When you re-assign the access rights for the Extension Data Container, which is used for storing all Composer settings, the system clears the cache for this page, and raised a cache notifying which force the system reload all settings again. And I thing that explains why it worked for you after chaning the access rights for the container page and not depended on which access right level it has.

Regards
Hieu Doan

So the solution is what? Because if I remove the access settings for the Extension Data Container the problem comes back. Is there something wrong with the loadbalancing settings in EPiServer since the change didn't seems to affect the settings.

Hi Tobias.

Please try to give the "Administer" access right to WebEditors for the page he/she has right to work with and try again.

Regards
Hieu Doan

hi

we had the same issue in our envierment ( epi 6 + composer 4) and the soultion we tried is given administrator to the user ( on the page he need to edit) and the probelm vanished,  i think that is not a good soultion becasue now he can do some harm

Hi, Someone from our company deleted the WebEditors group from our EpiServer 6 R2 CMS. Can you tell me if this is a huge issue or can the Group be re-added and the users assigned back to the Group? Or will this cause a huge issue for reasons such as an ID is assigned to the group and can never be reassigned correctly? The thing that worries me is that I have to go through each Composer element on ever page of the site re-setting the permissions and there seems to be an issue where a member from the newly created WebEditors group can add a Composer element to a page and it turns grey and is unusable - only when an Administrator edits the permissions to the new control can the WebEditor add edit the control.