SharePoint University

Hi,
Can anyone help? We have created a subsite and have added usernames to access the site. All is working okay.

We have permissioned one of the usernames to have Full Control over that site, to allow them to add new web parts and create further sub sites if needs be.

The problem is, is that the user cannot create subsites (keeps getting 'Error Access Denied' message) and also the list of Web Parts when adding a new one is not the full list (I'm the admin user for all sites and I get a much bigger list of Web Parts).

The user of the site is not in a specific group.

Thanks in advance
Jason 

Hi Jason,

 A couple things to check for. First, it sounds like a permissions issue. Verify visually the permissions, just to be sure. Then, look at the features and make sure they are turned on. Specific features drive specific web parts.

Hope that gets you started.
Mark
EndUserSharePoint.com

Hi Mark,

Thanks for the info. I tried turning on the Site Features but it did not solve the problem. The user still has an incomplete list of Web Parts and they still cannot create additional sites.

Any other info would be greatly received.

Thanks
J

Did you solve it?

I have the same problem. I have a Site Collection with 3 levels of subsites. Users with Full Control on level 2, should be able to create subsites on level 3. But they can not! I can without any trouble create subsites.

As the creator of the Site Collection I am a "Site Collection Administrator" (toplevel site -> Site Actions -> Site Settings -> User and Permissions -> Site Collection Adminstrator). If I add anybody to this group, they can create subsites, but they also get permissions to see all other subsites.

Is it possible to give a person that is not "Site Collecion Administrator" permission to create a subsite under a subsite? I cant get it to work, even if I give the person Full Control over the subsite.

 Greetings from Denmark

Erik Kjær-Larsen

I just saw a blog entry on something similar to this.  I don't think they solved their problem (or if they did, they didn't blog about it yet).  Anyway, can you maybe create a new group with specialized permissions that allow the user to do everything you want them to?  

Linda 

It seems that I have solved my problem. I found a newsgroup about it. Well it was not about subsites but creating webpages on sub-sub-sites. I tried the fix and it worked.

The trick is that the person who has "Full Control" over the subsite (sub-sub-subsite) has to have (at least) "Read - Can view and read" rights to the top-site. Thats it! The he can create new sub-sub-sub-subsites.

With my collection site it is no problem. Permission are unique and not inheritted and the top-level site is OK to be seen by anyone. I btw just gave "Read - Can view and read" rights to "NT AUTHORITY/Authenticated Users". That solved it. 

 Greetings from Denmark

Erik Kjær-Larsen

this work for anyone else?

i have the same problem and even when i give that user ful control over the top level site this is no go.

to be more specific, they can click create, sites and workspaces and fill out the form. but when they click create they get error denied.

 the site gets created and when they select it they need to select the template, and by default the site doenst inhertit the top navigational bar like it should.

any ideas, its driving me crazy.

i got it to work by adding them to a group called "ESP Owners" which has Full controll at the top level.

 Obviosuly i dont want them a part of this group. any ideas would be good.

As I wrote later, it worked for me, just to give people read-rights to the top-level. When they have that, there is no problem for me, to create sub-sub sites where I have given them full-control.

Greetings Erik

they have both contribute and read.

 they can get to newsbweb.aspx just fine. fill it out click create and get a access denied message.

 after this the site is actually created but when you click it you need to choose a template, a bit like wss2 site creation. They are able to do all this its just the access denied and the longer process.

fixed it!,

we had taken permissions away from the site directory as did not want them using it. but it seems because they didnt have contribute access to that site the lists coudlnt be accessed for the site directory updates.

Sounds like another reason to never, ever change anything set by default in SharePoint... especially permission levels.

Regards,
Mark
EndUserSharePoint.com

I hate digging up old threads, but I figured I will let people know what a "true" answer is (at least in my mind).

Problem -- Users cannot add many web-parts to subsites even though they have "Full" control on the site.  They are however restricted from the top level site.  They live in their sub-world and have no reason to come out, and the company prefers it that way :)

Work-around -- Give users read access to top level site.  This unfortunately doesn't work when you have sensitive data higher up than you want the users to go (I know, flaw in site structure design, but that is besides the point).  We cannot give users access to higher level sites..

Real problem -- Users only on subsites do not have access to any of the top-level site galleries (web part, masterpage, content type etc...) And galleries only exist at the top level site

Real solution.  Add them to the gallery permission level (Site actions - Site Settings - Web Part Gallery - Settings Gallery Settings - Permission' - Break inheritence, add what you need)

Am I missing or forgetting anything?  Hope it helps

Hello,

Actually you are missing something. There is a setting in SPList called AllowEveryoneViewItems which allows any user to view items in a list. It is quite useful for allowing access to such things as style libraries, webpart and master page galleries, etc. that are stored in a central location. The user does not need any kind of access to the site as long as the list has AllowEveryoneViewItems set. Note that you still cannot 'browse' the list using forms such as allitems.aspx as this is not part of the list items per se but rather a page supporting the list.

.b