Hi Leonard!

I followed your steps in a my local 6R2 site, and got the expected result all the way down to the But:, (using an AuditingSqlRoleProvider though) but do you go back into admin mode and reexamine the Administer Groups list? or which list do you mean? not quite following ^^;

//Mathias

I cannot either fully understand what you problem is. When you are inside edit mode and select "Change Access Rights" any changes will only effect that one single page. Any changes to the page tree have to be done in admin mode.

Also - "EPiServerCommonRoleProvider" - does this mean that you have a Relate site?

Hi Mathias, Thanks for your quick reply! 

I'm not going back to the admin mode, I'm staying at the same place: so, I go to CMS > Edit Mode > and I select the website, and click 'Change Acces Right' (the yellow key), then the screen with title 'Set Access Rights for Page "Site"' appears, with the text "You can select which users and groups that will have access to this page as well as what they are allowed to do with the page." and then with a list of groups. This list also contains the group "Admins_International_Test". At the bottom of the page there are 2 buttons: "Add Users/Groups" and "Administer Groups". If I click this "Administer Groups"-button, then a popup appears: after clicking Search in the popup, a list of groups is displayed, but the "Admins_International_Test" group is not there. 

I also created a user and added this user to the "Admins_International_Test" group. I tried to login with that user in EPiServer, but that does not work. 

In a standard CMS 6 installation, the Change Access Rights UI in Edit mode consists of "Add Users/Groups" button. There is no "Administer Groups". 

You can see this yourself by logging in to the http://demo.episerver.com/ site (epiuser/episerver).

Could this be a custom button for your project?

Hm, I'm sorry but I can't remember ever seeing the Administer Groups button there. I only have one; Add User/Groups. Are there any customizations made to the access rights page in edit mode? I believe it's called EditSecurity.aspx. Or any PageAdapter changing the page?

Is the user that you added to Admins_International_Test also a member of WebEditors (or whichever group you have in the location-tags for allowing access to the UI path)? If not, that may be why you can't use it to get into edit mode.

 Update: Mari, you write faster than me >_<

Thank you Mari and Mathias! I see, this "Administer Groups" button is a custom thing, I didn't know that, I will dive into it to check what it does :-)

To be clear, I'm trying to create a Group with Administrator Right for a newly created site (called 'International'), and then I want to add users to this Group. 

So, I created a Group 'Admins_International_Test', set the Acces Rights of this group, create a new user and made this user member of the WebEditors and Admins_International_Test group. Then I logged in with this user-account, I expect to be able to see the Admin Mode stuff, but I don't see that, so something goes wrong somewhere....

Try add the user to WebAdmins to get access to the Admin Mode.

I don;t have a WebAdmins group. I do have a Administrator group. This gives the user access to the Admin Mode, but it also gives the user access to the Admin Mode of all other sites...

Hm, I don't think there are separate admin modes for multiple site solutions by default, nor is it configurable in regards of access to different parts of it (please correct me if I'm wrong). Could this be a reason for the custom Edit-mode Administer Groups-button? I mean, that someone wanted to give access to admin mode features to certain groups and does this by supplying it in edit mode.

Interesting problem though..

Okay, thanks. I'm actually not sure where the default EPiServer behaviour ends, and where our customizations start. 

We have different sites for different countries, and we have Admin Groups for every country (Admins_Sweden, Admins_Netherlands, etc), and a 'Global' admin account, which gives Administrator rights to all different sites. I was under the impression that this was default EPiServer behaviour, but apparently this is custom made. 

I will explain the situation to the end user, and will dive into the world of Admin right at a later moment. Thank for now for your help, and for your patience :-)