How do you fix site collection permissions when only site collection admins can access the site?

Robert
  • How do you fix site collection permissions when only site collection admins can access the site? Robert

    I have a site collection and the only way for people to access the site is by adding them to the site collection administrators group. I have several SharePoint Groups setup with varying permission levels from readonly to full control, but none of the users in these groups can access the site. Has anyone seen this before and if so how do you fix it?

  • Can they not access any part of the site? Can they access the view all site content page? http://siteurl/_layouts/viewlsts.aspx

    If they can view all site content then I'm guessing there is an issue with a webpart on your homepage.

  • It sounds to me that the content on the site does not inherit from the site permissions. A site collection administrator is always going to have full control which is what allows you to repair mistakes like this.

    Is it a publishing site or a regular team site? In a regular team site the default.aspx page should allow access based on the site's permissions.

  • Try creating a new site collection (team site) under the same web app. Perform the same security configuration with the groups and all that. Do you experience the same behaviour?

    Also, do you have a custom master page? If so, firstly ensure it is in a published state. Are there any custom controls on it that try to access protected resources (i.e. a control that reads data from a list in a subsite that has unique permissions)?

Tags
permissions site-collection
Related questions and answers
  • have observed to exhibit this 'bug' is: a site collection or site is based on a publishing template (can be built-in e.g. collaboration portal or custom site template) SharePoint 2007 with updates... only site collections/sites using non-publishing templates. All other content is availble e.g. documents, lists Has anyone else come across this? UPDATE 08/05/10: I have been doing some further... in the index under the contentclass:STS_Site and the sites (SPWeb's) are contentclass:STS_Web. The following people seem to have come across this issue and assumed it was just a limitation. I think

  • the Central Admin app pool account can write to the config database But then we lose the whole point - I want my site collection administrators to be able to manage the schedule! The only alternative solution I can think of is to have another timerjob that polls some kind of queue (for example a sharepoint list in my site collection) for new timerjobs to create, and creates it if an item has been added...I have run into a problem several times now where I have developed a custom timer job, and I want my site collection administrators to manage the schedule of this job with a custom application page

  • "publishing portal" for the site collection. I have also enabled anonymous access. Now the basic function is fine, except that I do not know how to change the first front page (i.e. the page showed to end users who have not logged in yet) of the site. Here is a screen snapshot. Any ideas how to edit this page? Publishing home page http://i33.tinypic.com/2hex08j.png BTW: I have tried to edit the default.aspx after login but anonymous users could still see content like in the following list. How do I remove this for an anonymous user? Enable anonymous access You must enable anonymous access

  • I'm trying to create a site collection via stsadm. I do: STSADM -o createsite ` -url "<url>" ` -title "<title>" ` -description "<desc>" ` -lcid 1033..., at the Powershell prompt I get only the following output: User cannot be found. If I look into the ULS logs, I see the following related logs (truncated a bit for clarity): Creating site http... to contact the global catalog server If I create a site collection through Central Administration, using the same <domain\user.name> credentials, the site collection is created fine. Any ideas

  • I'm some kind of admin on my sharepoint site, but not the big kahuna who runs it all. I can add users and groups and set permissions within my site. What I can't figure out how to do is actually make a user a member, so that when they use the My Links dropdown, they'll be able to see the sites I run as one of the options (that arise from the My SharePoint Sites option). How do you make, and in fact even tell that a user is a member (in 2007)?

  • and clicking the "Next" button, they receive an Access Denied error. Thinking that the branching may have been causing an issue, I removed it. The users can now see the whole survey at one time, but when... possible. Can anyone tell me what I may have misconfigured or need to change? Update I've worked with the problem a little more. If I just create a survey with one question using only a yes...I have created a simple survey with SharePoint Server 2010 with the intent of allowing all our domain users to access and complete it. I added some basic branching logic to this survey as well

  • ) Board description (editable) My questions: What tool is most appropriate for making the forms? Infopath? SPD? VS2010? How do I handle rights to make sure only the board can access the board edit form? What kind of workflow do I use? When do I start the workflow(s)? What do I use to develop the workflow(s)? How do I handle rights when showing the listview with all requests? How can I build... practise solution. This is the requested flow: A user can make a request with a title and a description. A mail gets sent to the representative with a link to a form. A representative can approve

  • /img34/3389/webpartzoneedit.png Now how can we do that in code ? I have more then 30 aspx webpart pages on a site, I want to be able to do that so no one can change webparts properties (close, delete them etc.) The only thing I did find is this link: spwebpartzonetools. Reading more in SDK at: wss 3.0 sdk, at the second Important paragraph it says: Although you can add Web Parts to the Display, Edit, and New... (AllItems.aspx) is supported. So that's my mistake that I want to fix :). I did break that rule. My problem can be fixed in SPD but I don't know if that can be fixed in code. The mistake was "inspired

  • Using the following code I should be able to access the Taxonomy Term Stores: $site = new-object Microsoft.SharePoint.SPSite("http://localhost") $session = new-object Microsoft.SharePoint.Taxonomy.TaxonomySession($site) $session.TermStores.Count Yet the TermStore count is always 0. I know I have Term Stores and Term Groups and Terms because I'm able to tag items using the terms and view them in the Term Store Management Tool. For the SPSite I have tried localhost, the actual computer name, and even the Central Admin site. Based on my research this shouldn't be that difficult. http

Data information