Databases
StackOverflow2013
Postsdbo
POUsers have "read" access to Sharepoint site even when all user permissions were removed
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POUsers have "read" access to Sharepoint site even when all user permissions were removed
    primarykey
    data
    text
    <p>I have a Sharepoint site (MOSS 2007 SP2) that all domain users seem to have read access to even if I remove all user permissions to the site. I have no problem granting users all levels of permissions. For example, I can grant userA full access to my site, but when I remove the user completely from the site they still have read access. </p> <p>This is actually a subsite that does not inherit permissions from the parent. THis subsite also has subsites that either inherit or dont inherit permissions. Either way, the issue seems to exist on all subsites of the affected site.</p> <p>What makes this even stranger is that if I run a sql query to show who has access to a site it displays the same users that are listed on the permissions page for the site. For example, I give a user "read" access to the site then run the query, that user will appear in the query results as having "read" access. Then I remove the user from the site permissions page and run the query again, that user is gone from the query results and the permissions page, but they still have "read" access to the site. </p> <p>All users seem to have "read" access to this site and all its subsites even if they were never granted permissions to the site.Recently, I installed a microsoft security patch that fixes a known issue caused by installing SP2. This is a link to that issue and the patch that fixes it <a href="http://support.microsoft.com/kb/971620/" rel="nofollow">http://support.microsoft.com/kb/971620/</a> I am not sure if installing that patch was the cause of the issue. But if it is why would it affect just that particular subsite and its decendants? Has anyone encountered anything like this before?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USMike B
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POUsers have "read" access to Sharepoint site even when all user permissions were removed
      1. USHenrik
      1. VTFavorite
    1. COVery strange indeed. Anonymous access does not happen to be enabled for this site? (e.g. like explained in http://weblogs.asp.net/bsimser/archive/2006/09/25/Enabling-anonymous-access-in-SharePoint-2007.aspx)
      singulars
      1. POUsers have "read" access to Sharepoint site even when all user permissions were removed
      1. USDennis G
    2. CONo it isnt. I wish it were that simple :) There are no web application policies set up that would grant all users read access either. Whats even more strange is that this is affecting a particular subsite within a site collection. The sibling/parent sites are all fine.
      singulars
      1. POUsers have "read" access to Sharepoint site even when all user permissions were removed
      1. USMike B
    3. COIt turns out it was. See the comment to Vladi's answer below. Thanks for the response.
      singulars
      1. POUsers have "read" access to Sharepoint site even when all user permissions were removed
      1. USMike B
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload