Application Policies Overview

Application Policies determine how users are allowed to interact with the Eclipse PPM application as a whole. They are often reserved for users that are expected to be more than just Resources on Projects and Tasks. Members of these policies will be given the ability to interact with Eclipse PPM components outside of specific Projects.

Traditionally, an organization will designate (or even hire) individuals that will serve as administrators. These individuals may be responsible for managing the configuration, users, security, and general operation of the application as it relates to the organization and its users. However, many organizations enlist different types of administrators to be responsible for different types of application components (i.e. Project Administrators that can access and edit all Projects, Security Administrators that are responsible for distributing permissions to users, etc.). Application Policies allow administrators to create multiple custom sets of application-level permissions that can be applied to different types of administrators.

Example: Jack is one of the Eclipse PPM administrators for his organization. He is one of the few individuals trusted to access and interact with everything in his organization's Eclipse PPM environment. He is a member of the "Administrators" Application Policy, which has been created to give its members the ability to interact with all Eclipse PPM data and configure all of its settings. The Check All button has been pressed to give each member every Application permission available.

The members of this Application Policy can be reached out to whenever users have any configuration requests.
Additionally to the full administrators, Jack also wants to put together a group of users that can be responsible for going into Projects and interacting with the data. He creates a "Project Administrators" Application Policy for these users. The members of this policy will be given the "Create Projects" permission so they can add new Projects. They will also be given the "Modify All Data" permission so they can access any Project and edit its data. However, these individuals should not be able to edit any of Eclipse PPM's configuration data, so none of these checkboxes will be selected.

Tip: User Groups make Application Policies much easier to maintain. See User Groups for more information.

Application Policy permissions fall under the following categories.

  • Application Behaviors: These permissions allow members to create Projects and Programs, access Timesheets and impersonate others on a Timesheet, and create shared searches and Dashboard views.

  • Reports and Dashboards: These permissions allow members to access the Portfolio Summary and Resource Management Dashboards, as well as the Resource-related Eclipse Reports. Additionally, they can determine how much access members will have to Upland Analytics.

  • Risks & Issues: These permissions determine how members are allowed to interact with Risks and Issues that are not attached to Projects.

  • Administration & Configuration: These permissions allow members to access the Eclipse PPM Administration page and configure the administration options ("Modify All Data", "Configuration Administration", "User Administration", "Create Project Templates", "Bulk Import", etc.).

Tip: Users that are responsible for creating and/or maintaining Application Policies should familiarize themselves with the listed permissions. Clicking directly on any permission will display a quick description of its benefits:

See the following pages for more information on Application Policies: