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:
User
John Lydon
Malcolm McClaren
Martin Atkins
Keith Levine
John Savage
Laura Logic
Jah Wobble
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.
Workgroup
Product Management
Product Management
Marketing
Sales
Production
Web Designer
Contribute Administrator
websites
Sales, Production, Marketing
Sales, Production, Marketing
Marketing
Sales
Production
Sales, Production, Marketing
Sales, Production, Marketing
Contribute case studies
33
Need help?
Do you have a question about the CONTRIBUTE 3-DEPLOYING CONTRIBUTE and is the answer not in the manual?
Questions and answers