Export (0) Print
Expand All

How to Configure Non-Enterprise Security for Microsoft Project Server 2002

Archived content. No warranty is made as to technical accuracy. Content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
Published: June 1, 2003

Applies to:
Microsoft Project Server 2002
Microsoft Project Professional 2002

Summary Learn how to configure security in a non-enterprise (also known as a workgroup) environment.

On This Page

Introduction
Non-Enterprise Configuration
Additional Resources

Introduction

This article is part of a series of six articles about Microsoft Project Server 2002 security. You can access the other security articles from the links below:

Non-Enterprise Configuration

Microsoft Project Server 2002 users in a small business or other small organization may find that the non-enterprise (also known as workgroup) configuration for security deployment suits their needs. An example of an appropriate non-enterprise situation would involve less than 10 project teams within a handful of departments within a company.

Customers deploying Microsoft Project Server in a non-enterprise environment can begin using the server immediately after running the Microsoft Project Server Setup program. Project manager and team member accounts can be created directly from Microsoft Project Professional 2002. Executive accounts should be created by the administrator and added to the Executives group. Users will have access to all the non-enterprise features (timesheet, views, status reports, document library, and issue tracking). Typically, the server requires minimal administration and can be managed part-time by a user with no prior Windows NT server management experience.

Planning Requirements

None.

Post-setup Configuration

Executive accounts must be created and added to the Executives group. These users can view all information, but do not have the ability to edit any information.

Maintenance

As users join and leave the organization, accounts need to be added and removed. As new executives join a team, executive accounts need to be added. Generally, project manager and team member accounts are added and granted appropriate permissions automatically through the publish process. If you have installed SharePoint Team Services from Microsoft for document library and issue tracking features, you should synchronize users on a project in which executives are added or removed.

To synchronize users

  1. Log in to Microsoft Project Web Access as an administrator.

  2. On the Admin tab, in the left pane, click Manage SharePoint Team Services.

  3. On the next page, in the left pane, click Manage subwebs.

  4. On the next page, under Manage project subwebs, click Synchronize users.

Security Map Example for the Non-Enterprise Configuration

The map below illustrates the default categories and groups created by Microsoft Project Server setup. The configuration works well for a single department or business unit where executives should be able to view information for all projects and resources.

Cc768058.pj4scw01(en-us,TechNet.10).gif

Figure 1: Security map example for non-enterprise configuration

Note: If a team member delegates a task to another user, regardless of the delegation approval status, the user who is delegated the task automatically becomes a team member on this project. The user can then view tasks assigned to him or her. The next time the project is published, either by the project manager or via the synchronize user action by the administrator, the user can then view documents and issues submitted to this project. To prevent this, you can modify the global permission for team members so the team members cannot delegate tasks.

Additional Resources

The following links provide more information about security and Microsoft Project Server 2002:

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft