Go 4 Sharepoint

Search:

Welcome: Guest!

Sharepoint Forum

Home » Forum » Sharepoint

Ask a question

RSS Feeds

Document Library Permission Issue

Asked By: Tanya Ramos Date: Aug 25, 2006 Category: Sharepoint Views: 315

I have a situation I hope someone can give me some advice. Here is my
scenario -- I have a set of Windows SharePoint Services templates that
are executed with a user interface script off of the SharePoint Portal.
Five separate templates that create five different web sites each time
the site builder user interface is executed.

As a part of the templates is that a specific Document Library of each
web site is connected to the top-site through a Page Viewer web part
linked to the Document Library. This allows that Document Library to
act as a conduit for all completed work to be available to the top-level
project site (like a rollup).

All of this works, the problem is that I set permission levels of these
rolled up Document Library so people can only see this particular
Document Library and nothing else on the child web sites (for privacy
sake). To accomplish this, we have set Active Directory group user
lists that are set as guest account on the Document Library. This works
great when I set them on the site, but I want them to be set while the
user interface script is executed. For some strange reason is that the
permissions set on the templates for these Document Libraries are not
transferring during this build process.

Tagged:document library permission issue

5 Answers Found

Answer #1 Answered By: Kalyan Pujari Answered On: Aug 25, 2006

What do you mean by user interface script?

Answer #2 Answered By: Isidro Berger Answered On: Aug 25, 2006

We had Microsoft build us a Customer Opportunities Management interface (COMI for short). The purpose of the script interface if to make building project web sites easier and keep a level of continuity. The user only needs to enter some specific information, run the script and the interface builds 5 separate web sites (Company level, Engagement level, and three child sites for specific solution building).

The really cool thing about the site builder tool is that it uses a impersonation methodology that imitates a higher access permission for the build process then returns the user back to their original permission level once the script completes.

Answer #3 Answered By: Schuyler Le Answered On: Aug 25, 2006

It’s likely that the code is getting an error – and ignoring it. If MCS built it for you, it’s likely that you’ll have to have someone manually debug it -- either MCS or someone else with the source code.

Feel free to send me a message off-list if you’re interested in having me take a look at it for you.

Answer #4 Answered By: Kristina Cox Answered On: Aug 25, 2006

Security is not being maintained during the site provisioning process. We had similar issues with a solution close to yours and we had include code that set the security attributes during the site creation process.

Let me know if you need more information.

Answer #5 Answered By: Delbert Frederick Answered On: Aug 25, 2006

This thread is hard to follow so I'm not sure if this helps or not.

I usually use the <ExecuteUrl> tag in my custom site definition
Configuration to run code just after a web is provisioned. This is a
handy way to create custom Site Groups which cannot be captured in a
site definition or in a custom Web Template.

Didn't find what you were looking for? Find more on Document Library Permission Issue Or get search suggestion and latest updates.