Thread

As a follow up to my earlier post.

Using MSM I have setup a default site (A) and a copy site in a different language (B).

My aim is to have separate membership for each site and I have created site specific member groups limiting their privileges to site A or B as appropriate.

My problem is that if I give someone membership management privileges for site B then they can also see and access members from site A (despite the fact that in all other respects I have successfully limited their privileges to site B).

Is there no way to limit the administrator of site B so that he can see and manage members of site B only?

That the site B admin can see members from site A would be bearable - but I am very troubled by the fact that he can actually modify the profiles of members of site A. This was not what I was led to believe would happen in my earlier post on this issue, which I wrote before buying MSM.

Can you advise?

(In all cases member profiles are being accessed via the cp, not via the EE members templates).

Thanks

Chris

My problem is that if I give someone membership management privileges for site B then they can also see and access members from site A (despite the fact that in all other respects I have successfully limited their privileges to site B).

Is there no way to limit the administrator of site B so that he can see and manage members of site B only?

Is that a Superadmin, or some other, custom admin group?

Sorry should have said. My site B admin has a custom profile with publish/edit and membership management rights (for site B only),  but is not a super admin.

Hi agregat -

I did say that member permissions are set per group/per site; however, membership accounts are installation-wide.  So yes, all members will be visible to those able to administer members, across all Sites.

I apologize for the confusion there.  Does that help answer your question? Right now there isn’t a way to make members show only on specific Sites in the back-end.  You could always post a feature request for this to change in the future.

Hi Lisa
thanks for your note.

The fact that my site B admin can see all members of the site-wide installation is not really a problem - though in the commercial world the names of contacts are valuable property and are best protected; no, the real problem, and one which I think goes against the whole idea of MSM and the way we are led to believe we can configure our different sites, is that my site B admin can actually go and alter the profiles of users in groups which he shouldn’t have access to. This is serious.

In setting up the profile for my site B admin account/group I have disabled all membership management functions regarding site A. But this is essentially a redundant configuration as, in fact, member groups are not related to a specific site and therefore access to them cannot be controlled on a per-site basis.

To be frank with you, this was not what I had been led to expect from our previous exchange. And the reason I adopted MSM was precisely because I thought that I could control memebrship management in this way.

I’m not saying this to gripe - but because I think it is an serious limitation in the use of MSM which should perhaps be made clearer in the support literature.

I would certainly recomend that this sort of feature be implemented in the future.

regards

Chris

Hi, Chris. This would make a great user story as a Feature Request, and our dev team uses that forum to find items to add to the core product.

As far as the user docs are concerned, Lisa manages that process, and if you also mention in the feature request what you would find more helpful in the docs, she can implement those changes as well. Does that help?