16.01.2013 Views

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 19: Working with Documents in SharePoint <strong>Products</strong> <strong>and</strong> <strong>Technologies</strong> 531<br />

Access Denied<br />

Although users who have List access to document libraries will be able to view the<br />

contents of a document library, many options visible to the user will not be available<br />

to them. In such cases, when the user comes to complete a task, a Windows security<br />

dialog box will prompt a user for a name <strong>and</strong> password. Failure to provide a user<br />

name that has the necessary rights will result in either an access denied message<br />

being displayed or, if the Request For Access feature is enabled, a Web page being<br />

displayed that the user can complete <strong>and</strong> send to the owner of the website. The<br />

Request For Access Web page <strong>and</strong> the resultant e-mail is illustrated in Figure 19-7.<br />

F21xr07<br />

Figure 19-7 Error: Request For Access <strong>and</strong> Owner E-mail<br />

At first glance, the text of the e-mail to the owner does not specify the list or the<br />

library for which the user is having access difficulties. However, this information is<br />

contained in the hyperlinks. To give the user the required access, click the grant link.<br />

This will redirect you to the list or document library where the user had the access<br />

problem. This e-mail is sent to you only if the user can’t access the document library<br />

or list. If the user has some access right but doesn’t have the necessary access rights<br />

to complete a task, the more general Access request for a site e-mail is sent. An example<br />

of such a scenario would be if a user had list rights to a document library <strong>and</strong><br />

tried to check out a document. In this case, the e-mail the user receives might lead<br />

him to believe that there is a website access problem when it is a document library<br />

access issue. To prevent misdiagnoses <strong>and</strong> to enable you to decide whether this user<br />

should have access, you should train end users to include in the e-mail a description<br />

of the task they were trying to complete <strong>and</strong> the name of the document library or list.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!