in

SharePoint University

Clean slate. Nothing but SharePoint.
Go, SharePoint!

Security inheritance and unique permissions

Last post 09-27-2007 8:56 AM by Scott. 1 replies.
Page 1 of 1 (2 items)
Sort Posts: Previous Next
  • 09-26-2007 10:10 AM

    Security inheritance and unique permissions

    Hi All,

    A brief description of the problem
    Say we've got 3 sites named SiteA, SiteB and SiteC. SiteB is a subsite of SiteA. SiteC is a subsite of SiteB. So the following chain applies: SiteA=>SiteB=>SiteC.

    The following permissions exist at site-level;

    SiteA (unique permissions, no inheritance)
    User1 - Administrator
    User2 - Reader
    User3 - Reader

    SiteB (unique permissions, no inheritance)
    User1 - Administrator
    User2 - Reader
    User3 - Reader

    SiteC (unique permissions, no inheritance)
    User1 - Administrator
    User2 - Reader
    User3 - Reader

    No problem here. The users can look at the information on all sites. But what if we take away the rights of User2 at SiteB. After this we'll get the following situation;

    SiteA (unique permissions, no inheritance)
    User1 - Administrator
    User2 - Reader
    User3 - Reader

    SiteB (unique permissions, no inheritance) <notice that User2 is deleted>
    User1 - Administrator
    User3 - Reader

    SiteC (unique permissions, no inheritance)
    User1 - Administrator
    User2 - Reader
    User3 - Reader

    User2 can now look at SiteA without any problems. SiteB is not accessible for User2 because he/she has no permission here. That's also OK.
    But when User2 visits SiteC he doesn't have access to this site although it is configured in the (unique) permissions which are set at Site-level!

    Is this behaviour 'by design', and if so, where can I find any proof about this?

    With kind regards,

    ThaYoung1!

  • 09-27-2007 8:56 AM In reply to

    • Scott
    • Top 50 Contributor
    • Joined on 08-28-2007
    • Missouri

    Re: Security inheritance and unique permissions

    Not to question anyones capabilites,

    I understand your permission set of logic, no it does not sound like a design flaw...it sounds like it is just something wrong/just not working correctly.

    Just a thought,

    Process of elimination...Have you tried the same with user 3, or by doing the same from from site c or a...if so did you get he same effects. 

    If you did then my guess would be something corrupt in the site/s...if not then I would guess something in site c and or the user 2's name in that site.

    My start would be to remove and re add user 2 to the site c and see if the problem is one of the above.. 

     

    Hope this helps...
    Scott C
    WSS V2 and SPS 2003 with CorasWorks
    Client Side Person..
Page 1 of 1 (2 items)

Need SharePoint Training? Attend a SharePoint Bootcamp!
Forum content (c) original posters. Everything else (c) 2008 SharePoint Experts, Inc.