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 18: Managing SharePoint Portal Server 2003 485<br />

Caution Despite the security similarities between Windows SharePoint<br />

Services <strong>and</strong> SharePoint Portal Server, it is important keep in mind that<br />

while the former has the concept of Sites <strong>and</strong> Site Collections, the latter<br />

does not. A portal is a site collection <strong>and</strong> an area is a sub-web.<br />

The Show User Information link, which does not exist with Windows Share-<br />

Point Services, takes the administrator to a page summarizing all users that have a<br />

<strong>Microsoft</strong> SharePoint Portal 2003 profile. A profile is created either when an authenticated<br />

user successfully accesses the portal site for the first time or automatically by<br />

the profile import process (which creates a profile for users based on Active Directory)<br />

if it has been enabled by the portal administrator. By following the link for a listed<br />

user, the administrator can edit the user information by adding notes about the user<br />

<strong>and</strong> can even designate the user as a Site Collection Administrator.<br />

More Info You might notice that user accounts that have been granted<br />

access to portal areas <strong>and</strong> team sites continue to show in site groups <strong>and</strong><br />

permission lists in the portal site even after they have been deleted from<br />

the domain. The only two ways to get rid of them are to delete each entry in<br />

every site <strong>and</strong> site group or to delete them from the Manage Site Collection<br />

Users page, which will effectively remove them from all sites <strong>and</strong> site<br />

groups in that collection.<br />

One of the few differences in portal security from Windows SharePoint Services<br />

security is the existence of the additional Content Manager site group. By<br />

default, members of the Content Manager site group can approve or reject content<br />

posting requests <strong>and</strong> manage area settings. In addition, Content Managers can target<br />

areas for viewing by one or more audiences, which will be discussed later.<br />

Another security-related difference relates to the permission set that can be<br />

granted to a portal’s site group. For example, users can be granted or denied the Use<br />

Personal Features permission, which allows administrators to control which users or<br />

groups can use the portal site’s alert feature <strong>and</strong> the portal site’s personal site feature.<br />

Other permissions that do not exist for team sites relate to portal site feature<br />

management. Table 18-1 lists the differences in the two sets of permissions.

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

Saved successfully!

Ooh no, something went wrong!