I have a user who has 'Full Control' permissions on a WSS 3.0 sub-site. However, when they go to add web parts to their page, they get a 'no web parts found' message for the All Web Parts section of the dialog box. I've checked the web parts gallery on the top level site and it is still inheriting it's permissions from the top-level site.  Publishing has never been turned on for this site. I've read posts where people have manually changed the permissions for the web part gallery or have exported web parts and then re-imported them to make them show up. Both solutions feel like 'bandaids' to me and I'd prefer to get to the root of the problem. Does anyone have suggestions?© 2009 Microsoft Corporation. All rights reserved.Tue, 27 Oct 2009 14:17:27 Z2d85dfec-7cd4-4824-8731-1a2cf6a50ee3http://social.technet.microsoft.com/Forums/en-US/sharepointcollaboration/thread/2d85dfec-7cd4-4824-8731-1a2cf6a50ee3#2d85dfec-7cd4-4824-8731-1a2cf6a50ee3http://social.technet.microsoft.com/Forums/en-US/sharepointcollaboration/thread/2d85dfec-7cd4-4824-8731-1a2cf6a50ee3#2d85dfec-7cd4-4824-8731-1a2cf6a50ee3codegrlhttp://social.technet.microsoft.com/Profile/en-US/?user=codegrlI have a user who has 'Full Control' permissions on a WSS 3.0 sub-site. However, when they go to add web parts to their page, they get a 'no web parts found' message for the All Web Parts section of the dialog box. I've checked the web parts gallery on the top level site and it is still inheriting it's permissions from the top-level site.  Publishing has never been turned on for this site. I've read posts where people have manually changed the permissions for the web part gallery or have exported web parts and then re-imported them to make them show up. Both solutions feel like 'bandaids' to me and I'd prefer to get to the root of the problem. Does anyone have suggestions?Thu, 25 Jun 2009 16:35:11 Z2009-06-25T16:35:11Zhttp://social.technet.microsoft.com/Forums/en-US/sharepointcollaboration/thread/2d85dfec-7cd4-4824-8731-1a2cf6a50ee3#a8a65c9d-ac50-46c4-b9ee-6ce2ed7f1eddhttp://social.technet.microsoft.com/Forums/en-US/sharepointcollaboration/thread/2d85dfec-7cd4-4824-8731-1a2cf6a50ee3#a8a65c9d-ac50-46c4-b9ee-6ce2ed7f1eddDan Usherhttp://social.technet.microsoft.com/Profile/en-US/?user=Dan%20UsherWas the sub-site created from a site collection that was upgraded at one point from WSS v2 to WSS v3?  I've seen this cause issues if there were custom site definitions in the v2 instance being upgraded to v3 and the schema mapping not being proper.<br/><br/>I realize this isn't a solution, but hoping to at least gather a little more information to assist in diagnosis.Sun, 28 Jun 2009 22:48:23 Z2009-06-28T22:48:23Zhttp://social.technet.microsoft.com/Forums/en-US/sharepointcollaboration/thread/2d85dfec-7cd4-4824-8731-1a2cf6a50ee3#485d5e4b-0703-4643-80b5-7d0056e003d5http://social.technet.microsoft.com/Forums/en-US/sharepointcollaboration/thread/2d85dfec-7cd4-4824-8731-1a2cf6a50ee3#485d5e4b-0703-4643-80b5-7d0056e003d5codegrlhttp://social.technet.microsoft.com/Profile/en-US/?user=codegrlNo, it's always been a WSS v3 site. <br/>THanks,<br/>LauraMon, 29 Jun 2009 11:36:38 Z2009-06-29T11:36:38Zhttp://social.technet.microsoft.com/Forums/en-US/sharepointcollaboration/thread/2d85dfec-7cd4-4824-8731-1a2cf6a50ee3#33ee7e16-6159-42a3-9e56-67d7d0f663f0http://social.technet.microsoft.com/Forums/en-US/sharepointcollaboration/thread/2d85dfec-7cd4-4824-8731-1a2cf6a50ee3#33ee7e16-6159-42a3-9e56-67d7d0f663f0Dan Usherhttp://social.technet.microsoft.com/Profile/en-US/?user=Dan%20UsherHave you tried reinheriting permissions from the top level site to see if the web parts become available once more?<hr class="sig">http://www.spdan.comMon, 29 Jun 2009 12:42:07 Z2009-06-29T12:42:07Zhttp://social.technet.microsoft.com/Forums/en-US/sharepointcollaboration/thread/2d85dfec-7cd4-4824-8731-1a2cf6a50ee3#2836832e-4768-451e-a985-8f61a6524643http://social.technet.microsoft.com/Forums/en-US/sharepointcollaboration/thread/2d85dfec-7cd4-4824-8731-1a2cf6a50ee3#2836832e-4768-451e-a985-8f61a6524643codegrlhttp://social.technet.microsoft.com/Profile/en-US/?user=codegrl<p>We just tested that and it worked to make inherit the permissions and then make them an admin at the top-site level. The problem is that is not a long term solution for this particular site collection. It seems like the 'trend' is that the individual can see the web parts at the sub-site level, only if they have admin privileges at the top-site level. I've not known this to work this way in the past.</p>Mon, 29 Jun 2009 19:54:21 Z2009-06-29T19:54:21Zhttp://social.technet.microsoft.com/Forums/en-US/sharepointcollaboration/thread/2d85dfec-7cd4-4824-8731-1a2cf6a50ee3#ffc5928e-1cef-4c1a-9074-99932e7432d8http://social.technet.microsoft.com/Forums/en-US/sharepointcollaboration/thread/2d85dfec-7cd4-4824-8731-1a2cf6a50ee3#ffc5928e-1cef-4c1a-9074-99932e7432d8Pratik FTWhttp://social.technet.microsoft.com/Profile/en-US/?user=Pratik%20FTW<p>Well, just give read access to Web Part gallery on top level site. If required, break inheritance and do it. Top level site -- site actions -- site settings -- web part gallery -- settings -- gallery settings -- permissions.<br/>No need to do anything else. This will work.</p>Tue, 27 Oct 2009 14:17:26 Z2009-10-27T14:17:26Z