Re: Whatever happened to Site Groups in WSS 3.0?

I don't know what to tell you other than this is the design of the product.
Lots of groups is a possibility in WSS v3.

--
Bill English, MVP
Mindsharp


"Andrew Stokes" <AndrewStokes@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3DB39E15-B5FB-4F07-8A5D-A2866BA39B56@xxxxxxxxxxxxxxxx
Hi Bill, thanks for your reply.

The issue I have is that if I create specific groups for site level use,
e.g. site 1 managers, site 1 team members, site 2 managers, site 2 team
members etc. and I have many sites in the site collection I end up having
an
enormous number of groups at the site collection level. We create project
specific sites for each business proposal /contract and the number of
sites
soon build up.

I need to specify site specific access rather than site level, e.g. I want
user 1 to be a project manager on site 1 (giving him/her contribute access
to
certain lists that are read only to team members) while the same
individual
is a team member on site 2.
I can use groups to give a fixed set of users rights across many sites but
it gets messy when I want to change the members of groups depending upon
their role within each site.

I could add users with permissions given directly (e.g. 'Contribute' for
Team Members) then break the inheritance of permissions on certain lists
and
libraries and apply different permissions at this but this would be
difficult
to manage as when new users were added to sites they would also need
permissions adding to any objects that weren't inheriting permissions from
the parent site.

Cheers

Andy


"Bill English [MVP]" wrote:

You are correct in your assessement of how group scopes have changed in
WSS
v3. But I'm not clear on how this makes it difficult to secure lists and
libraries. Create the groups you need, populate them and apply them to
the
list or library. Perhaps I'm missing something, but this seems
straight-forward to me.

--
Bill English, MVP
Mindsharp


"Andrew Stokes" <AndrewStokes@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6A6BB1F0-7229-42ED-9DC4-39A23FE7C344@xxxxxxxxxxxxxxxx
Hi

In WSS 2.0 there were Site Groups and Cross Site groups. I believe
Cross
Site Groups worked at the site collection level and Site Groups worked
at
the
site leve. It seems that in WSS 3.0 Cross Site Groups have been
maintained,
now just termed Groups and Site Groups have been ditched. This makes
life
difficult when you want to set permissions on libraries and lists in
many
team sites.

In our situation, we have many project specific sites. I want the same
pool
of staff to access these sites but we want to give different
permissions
to
staff depending upon their position in the project. To this end I
thought
of
creating project managers, project team members and project readers
groups
for each project with some lists and libraries secured to only allow
the
project manager's group to modify items. The problem with this is that
groups no longer exist at the site level but seem to be at the site
collection level. This means that when you have a few hundred sites
the
number of groups at the site collection level gets very quickly out of
hand.

Does anyone have any ideas besides giving individual user level
permissions
on lists and libraries that don't inherit from the site?

Cheers

Andy






.

Relevant Pages

  • Re: Whatever happened to Site Groups in WSS 3.0?
    ... Team Members) then break the inheritance of permissions on certain lists ... libraries and apply different permissions at this but this would be ... Site Groups worked at the site collection level and Site Groups worked ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: compile+link Fujitsu Linux
    ... completely independent of whether it uses libraries or individual ... I talk about packaging called programs, you respond with security concerns. ... using file system permissions as program permissions. ... The faulty lists I mentioned earlier are fixed in the first test cycle. ...
    (comp.lang.cobol)
  • Re: WSS v3 Permissions
    ... Site Level permissions apply to the whole site, all libraries and lists. ... Document library and list permissions inherit from the site permissions but you can alter that at that level if you want. ... What is the primary difference between the permission setting at a library ...
    (microsoft.public.windows.server.sbs)
  • Reg. Directory listing program
    ... I am new to this mailing list and I am very new to PERL. ... I wrote a code that lists files in a directory with the permissions. ... Directory listing program ...
    (perl.beginners)
  • Re: Different Access Permission Levels on Sharepoint CompanyWeb?
    ... > WSS provides the ability to control permissions on a per-list basis, ... > users, to groups of users, or to a site group. ... > have access to all lists and document libraries on that Web site. ...
    (microsoft.public.windows.server.sbs)
Quantcast