Don't know about changing the default group, but what I did was this. Removed the All users group from the top workspace where all our internal stuff resides. This will prevent the All users group from even seeing the workspace and everything beneath it. I had to create a group which is allowed to see the workspace offcourse and gave the appropriate users membership to this group.

Marcel

Thanks for the suggestion and yes I would be removing the all users group from the workspace but with the volume of users I am looking at adding all of these as and when they first login will be a nightmare.  What I really need is within the LDAP lookup a way of pre-defining a group for my 500+ users.  Then when it comes to customers and suppliers access i add them to Teaming under a different group.

This is the only way I can see a true collab. environment for large scale users can work.

Has anyone tried this ?

Hi Andrew, by using LDAP you should be able to import groups as well. You can then simply add one of those groups to the Access Control List.

I'm not sure if this would work but eDir has the ability to do dynamic groups.  If you could use a dynamic group and sync it through to teaming it might work.  Just create a group with particular search criteria that would include all employees but not customers.  Then assign rights to that group.  Not sure if teaming would be able to deal with eDir dynamic groups, though.  It may be worth a try.

I managed to setup a group under eDir pointing to an OU.

Teaming has created the two groups I setup but the few test users I added to either group did not get added to the group automatically.  Whats the use of group imports then ?????

Regards

Andy

Anyone.

I have groups importing from LDAP now into Teaming but the memberships do not follow.  Am I expecting too much here or is the group aspect of the import only to setup the group in Teaming.

Regards

Andy

I've got the same expereince. Groups show up without members (also in beta3) must be a bug.

Marcel.