RE: Permissions Problems HELP

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



Dave,
Thank you for your input.

I did what you recommended. I have 1 Master_Edit_Only site group that
everyone is a member of. Then I created DL_Name_Edit groups for each
Document Library. Now as an administrator it's fairly easy to control.

The next step for me is to have the Team and Group Sites self-managing. If
a Team Leader (who is not brightest pixel on the screen) wants to create a
Document library and have Edit_Only permissions it would be very difficlut
for them. I'm not sure I want them going into Manage Site Groups.

I just wish there were more granular permissions to choose from when you Add
a User in a document library. It goes from View Only to
View,Add,Edit,Delete. Those should be individual selections not grouped.

Thanks again for taking the time to help.
If you think of anything that could make it easier, let me know.
Email address is: monbleau(AT)palmbeach(DOT)k12(DOT)fl(DOT)us

Ron


"dave nixon" wrote:

> why not make all users (domain\domain users) edit only and then if u need to
> add exceptions such as users who need to have write or delete access then you
> can create a separate group for them...that way u will only have X amount of
> groups for users requiring special access and one group to cover the edit
> only permissions
>
> "Capt_Ron" wrote:
>
> > Dave,
> > I know how to do that. Ok. I create a site Group that has everything
> > except delete. That's easy. I can only add users to that site group by
> > Manage Users and Manage Site Groups. What if I have a site group called
> > Edit_Only. I add 10 users to the group. I add that group to the Doc Library
> > and remove all other groups. Now that Edit_Only group is the only group to
> > be able to access that DL. Now I create a second DL with the exact same
> > permissions. (Edit_Only grpon is the only group) However there is 1 more
> > user that needs edit permissions to the DL. How can I get that one user to
> > have Edit Only permissions without adding them to the Edit_Only group.
> > (Because I do not want them to have access to the first Doc Library.)????
> >
> > That is the crux of my problem. The way things stand, I'd have to add tons
> > of Site Groups just to cover the odd users.
> >
> > If I have 50 Documant Libraries on one site and the Edit_Only group is a
> > member of all of them, then any "odd" users would have their own site groups
> > just for those specific DLs. That's over 50 site groups!!!
> >
> > And I haven't even gotten into the situation where a User created their own
> > Document Library (not an admin) and they want to have Edit_No_Delete
> > permissions. They don't have access to site group creation so they?
> >
> > Is this any clearer?
> >
> > Thanks for the reply
> > Ron
> >
> > "dave nixon" wrote:
> >
> > > Ron
> > > clcik on site settings on your site.
> > > click on go to site administration
> > > clcik on manage site groups
> > > add a site group
> > > add the permission u need and click 'create'
> > >
> > > when u go back to the DL permissions your new site group will be there
> > >
> > > Dave
> > >
> > >
> > >
> > > "Capt_Ron" wrote:
> > >
> > > > I'm using WSS and have created a top level site and multiple sub-sites.
> > > > When I create a document library and I want to add users or site groups to
> > > > the DL I get a generic set of permissions. It starts out at View then goes
> > > > to View, Add, Edit, Delete. How can I add users and have them edit but not
> > > > delete. I'm deathly affraid that users may intentionally or unintentionally
> > > > delete a document that should not be deleted.
> > > >
> > > > I know I can go into Site Groups and create an Edit_No_Delete group and add
> > > > the users into there. But when I try to add the group to the DL I still only
> > > > get the defaults. I have to inherit permissions then remove the ones I don't
> > > > want. Then if I have a user that needs access to this one DL but not all the
> > > > others the Edit_No_Delete group can get to I have to do it all over again for
> > > > this one user!!!
> > > >
> > > > What a collossal waste of time.
> > > >
> > > > Is there an easier way to do this?
> > > >
> > > > BTW: I do have Portal Server 2003 installed. But I've had absolutely no
> > > > training in it and it confuses the hell out of me.
> > > >
> > > > All my boss wants is to have the department broken into: Department ->
> > > > Division 1, Division2: Division 1 -> Team 1, Team 2, Team 3...: Division 2
> > > > -> Group 1, Group 2...
> > > >
> > > > He wants each Division/Team/Group to have it's own site with specific
> > > > Document Libraries. However the DLs in the Department and Division Sites
> > > > must have specific sets of permissions based on the user.
> > > >
> > > > Please help. If I can't get this working properly, this project is gonna
> > > > bust. And I KNOW that SPS and WSS are going to be really beneficioal to the
> > > > Deaprtment.
> > > >
> > > > Thank you very much
> > > > Ron
> > > > PS: I have a couple of books (Windows SharePoint Services Inside Out, and
> > > > SharePoint Services Products and Technologies Resource Kit) While these may
> > > > be good books for someone who has a deeper understanding of the system, for
> > > > me they read like bricks. Are there any books or tutorials that can help
> > > > explain all this?
.



Relevant Pages

  • 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)
  • Re: Document library Delete permission.
    ... Create a Site Group and give the group only Edit, Add, and View ... (Site groups can have granular permissions). ... Any user you add to the new Site Goup will only be able View, Edit and Add ... >> different document libraries each of which all people could read but for ...
    (microsoft.public.sharepoint.windowsservices)
  • How to Keep Document Editors From Deleting Documents in a Library
    ... I have a document library that I want some users to be able to add, edit ... group to the document library without giving the group delete rights. ... When adding the site group it requires you give them a choice from the list ... edit permissions to it. ...
    (microsoft.public.sharepoint.windowsservices)
  • RE: Document Library Delete option
    ... having issues with the unique permissions on the document library. ... figured it out and the Inherit Permissions From The Parent Web Site is the ... be a member of a site group that has edit but not delete rights. ... Now you have the Inherit Permissions From the Parent Web Site ...
    (microsoft.public.sharepoint.windowsservices)
  • RE: How to Keep Document Editors From Deleting Documents in a Library
    ... You can add a new group, but I usually just remove "Delete" permissions from ... Click the "Edit Site Group Permission" button at the top of the list. ... > group to the document library without giving the group delete rights. ...
    (microsoft.public.sharepoint.windowsservices)