Securing Your PeopleSoft Proposal Management System

Use the Proposal Management Security (GM_PM_SEC_OPR_GBL) component to define operator security for PeopleSoft Proposal Management.

This chapter provides an overview of PeopleSoft Proposal Management security.

Click to jump to parent topicUnderstanding PeopleSoft Proposal Management Security

This section discusses:

Click to jump to top of pageClick to jump to parent topicMultilevel Security

PeopleSoft Proposal Management uses multilevel security. Use the security setup pages in PeopleTools to provide access to the data, functions, and pages that give users the ability to perform their work. To define security for the organization, you must:

PeopleSoft Proposal Management supports user security, which enables you to limit access to specific PeopleSoft Proposal Management proposals based on the user and department. Therefore, it is possible for a user to have access to a subset of all the proposals that may be stored in the system. This security feature augments the normal PeopleSoft security based on the user class, which defines the menus and components available to a given user ID.

By default, if you have not set up department-level security, users only have access to their own proposals. That is, they can only access a proposal if these conditions are met:

You can associate each user ID to an employee ID (EMPLID) when you create it.

Click to jump to top of pageClick to jump to parent topicSecurity by Department and User ID

Implementing security within PeopleSoft Proposal Management is optional. If you want to restrict the list of users who can view proposals, select Yes in the Security group box on the Contracts BU Setup page. If you want all proposals under a business unit to be visible to all users, select No. When you enable security, the list of users who can view proposals is limited to those who have been granted security access on the Proposal - Set Up Options page.

Establish PeopleSoft Proposal Management security by setting up a series of associations that limit or provide user access to components. Set up these associations by linking user IDs with a security tree node that represents a department or group of departments. When a user attempts to open a component, the system examines the associations between that user's ID and user class. If you have established appropriate links, the user can open the pages. Additionally, the search records for each component only enable the user to access the records that have departments that are associated with the security tree.

Note. The pages listed in this procedure are fully documented in PeopleTools documentation.

To set up security by Department ID:

  1. Create a new role by selecting PeopleTools, Security, Permissions & Roles, Roles.

    You can create as many roles as necessary. You will want to create a role for every set of users that needs a different level of security access to the data.

  2. Create user IDs and assign roles to user IDs by selecting PeopleTools, Security, User Profiles, User Profiles.

    Note. Be sure to assign a valid employee ID. This ID will be matched with the proposal or proposal project to determine which proposals can be accessed by this user ID when no department-level access is specified.

  3. Define the PeopleSoft Proposal Management security tree by selecting Tree Manager, Tree Manager.

    Set up the security tree based on an analysis of business processes within the organization. If a department tree already exists and mirrors a department hierarchy that would provide the appropriate coverage for security needs, we recommend that you copy that tree.

    Note. The department security tree must be a node-oriented tree. That is, each node on the tree must represent a valid department that exists in the Department table (DEPARTMENT_TBL). When you define the detail tree structure, make sure that the node record equals the Department table and the field equals Department ID (DEPTID).

  4. Assign an object group to a permission list by selecting PeopleTools, Security, Permissions & Roles, Permission Lists.

  5. Define operator security by selecting Set Up Financials/Supply Chain, Security, Proposal Management Security.

    Select the tree setID, tree name, and the effective date of tree. In the lower section of the page, select the department designation and access code. You can enter as many departments as you need.

  6. Change the search records for PeopleSoft Proposal Management components by selecting PeopleTools, Application Designer, File, Open, Components.

    The search record that we deliver for these proposal components provides department-level security. Currently, the search records that are defined below are delivered with the system. You may replace these security search records if you require a different security scheme.

    This table lists the menu navigations, components, and search records used in PeopleSoft Proposal Management:

    Menu Navigation

    Component

    Search Record

    Proposal Management, Proposal and Version, Maintain Proposal

    GM_OPPTY_HDR

    GM_OPTY_SRCH_VW

    Proposal Management, Proposal and Version, Maintain Version Estimate

    GM_OPPTY_PRJCT

    GM_OPVR_SRCH_VW

    Proposal Management, Proposal and Version, Maintain Version Est. Detail

    GM_PM_RSRC_DTL

    GM_PM_ACTV_RSRC

    Proposal Management, Proposal and Version, Copy Proposal

    GM_BUD_PPSL_CPY

    GM_PROP_SRCH