SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

On the "My site" feature of MOSS 2007 there is a "memberships" Web part that shows the distribution list that the user is a member of.

This is picking up several groups that we would rather not be shown e.g. some that have been set up for administrative purposes only.

Is there any way to control which groups are shown; ideally this would be using (EDIT) the hide from exchange option in AD.

share|improve this question
Thanks for answers, but we're looking for a server side method; I'm not sure hiding items with jQuery is a workable longterm solution. – Anonymous Nov 23 '09 at 10:18
Then it sounds like you need to build a custom web part that shows the filters out the records you do not want before it is rendered. The membership information is available via both the API and WebServices so getting the data for the specified user shouldn't be a big deal. Replacing the default Membership with the Custom Membership Web Part on the individual MySites is going to be the biggest challenge. – Mike Oryszak Dec 5 '09 at 15:47
up vote 1 down vote accepted

Someone on stackoverflow answered the question - deny the account that trawls ADpermission to read the groups (whether individually or by OU).

share|improve this answer

You could write a little jQuery script that would hide certain items for the user, if you are happy to accept that you will have to update the script once you add another distribution list that needs to be hidden (unless they all conform to a certain naming convention i.e. starts with "testlist-xxxx").

share|improve this answer

I can see where it could get cluttered in a large org with a lot of Distro Lists. Users can remove individual ones but that would be tedious. I like Japp's answer with hiding it via jQuery if there is a standard naming convention and they can be identified from the others.

share|improve this answer

That's an interesting problem to have, lots of approaches, the custom web part is a good one.

If you go down the path of custom web part, removing the sharepoint one and adding your own is easy via the WebPartPages web service or even the object model. You must also remove it and replace with yours in the site def so new sites don't have it when created.

Finally, another solution would be to remove them out of the profile database via a trigger, but you'd have to be open to that idea as a very last resort.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.