We haveused MOSS 2007 to develop our organization's Intranet and for the most part it's working fine, however I have run into an issue with granting limited access to lists within subsites.For example, the structure of the site is similar to this: Intranet (root site) Departments Finance Human Resources Information Technology Committees Employee Recognition Policy Safety All domain users have Contribute access to the root site (http://intranet) and to the department and committee sites(http://intranet/departmentsand http://intranet/committees).Permissions for the individual department and committee sites are then restrictedto the respective groups.This is working fine, however if I want to allow all users to submit items to a list within, say, the IT department page (such as an issues list) using a link I place on the root site, I am running into a problem. What I've done is change permissions on the issues list to allow all users to add and edit items, and this in turn then appears to update the IT department Site permissions so that all users have "Limited Access" - so far that makes sense. Unfortunately, when a user clicks the link to submit a new issue to the list the form they see is not formatted with the correct CSS settings - fonts are different, spacing is strange and some features are usable (such as changing the list view).In reading about "Limited Access" on the Microsoft site I ran across this, which I understand, but I think the highlighted section is what I can't figure out how to work around in my scenario:"The Limited Access permission level is designed to be combined with fine-grained permissions to give users access to a specific list, document library, item, or document, without giving them access to the entire site. However, to access a list or library, for example, a user must have permission to open the parent Web site and read shared data such as the theme and navigation bars of the Web site. The Limited Access permission level cannot be customized or deleted."So from what I can tell if I don't give all users at least the ability to open the parent web site then the CSS settings for the theme are not applied, but if I do give them these permissions then they can view the entire IT department site, which I can't have in this scenario. Does anyone have a suggestion for how I might get this to work?Chanda

Turns out the problem is not being able to access 2 .css files within the sub-site: core.css and the theme.css.Core.css is stored in http://site/_styles, while the theme's css file is stored in http://site/_themes. Both of these files are not accessible to users that do not have read rights to the site, so the solution is to redirect to copies of those files that exist in a location that IS accessible to all users.In my scenario I modified the default.master file to add a link to the core.css file that resides at the top-most site since all my users have access to that. Additionally, I used the master page settings option for Alternate CSS file to also redirect to a copy of the theme.css file that uploaded to the top-level site under the Style Library. This way all styles that are used in our site and sub-sites are covered by one of the two .css files that I've redirected to, and since they exist at the top site all users can access them so the pages now look correct.Chanda

Hi Chanda I have similar problem, I unghost Core.css and edited now I lost my security settings for core.css for anonymous access to the one Survey (List). It was not supposed to ask User name and Password and it askes now every Pages of Survey for not able to access CORE.CSS file. When you cancel on login screen , it losses all formatting . I have manyllay places link of CORE.CSS file in master file so now formatting stays but it still asks for username/password. Please help a