Contribute case studies
33
Unlike sites that don’t use Publishing Services to manage users, the User Directory does not create
an administrative file at the folder level to which you limit access. Instead, the User Directory
stores and maintains all user and connection information. When a user logs in, the User
Directory retrieves the connection information associated with that user, and provides access to
the sites the administrator has assigned. By maintaining site connection information within the
User Directory, administrators can add or remove access to websites without having to resend
connection information.
This example provides a partial listing of employees from an organization’s user directory. The
employees, their workgroup affiliations, and the sites they can access are listed in the following
table:
Although this user list is oversimplified, it demonstrates one possible scenario for the way that
users within an organization might be assigned access to websites. This scenario divides users
according to their role within the organization, and assumes that they have full editing and
publishing privileges within their respective sites. Certain users have access to all the sites. For
example, the product managers, John Lydon and Malcolm McClaren, work with all the teams in
developing and launching products, and need to contribute to all the sites.
User
Workgroup
websites
John Lydon
Product Management
Sales, Production, Marketing
Malcolm McClaren
Product Management
Sales, Production, Marketing
Martin Atkins
Marketing
Marketing
Keith Levine
Sales
Sales
John Savage
Production
Production
Laura Logic
Web Designer
Sales, Production, Marketing
Jah Wobble
Contribute Administrator
Sales, Production, Marketing
Содержание CONTRIBUTE 3-DEPLOYING CONTRIBUTE
Страница 1: ...CONTRIBUTE 3 Deploying Contribute...
Страница 4: ...4 Contents...
Страница 38: ...38 Index...