Granting Access to Users

This topic discusses how to:

  • Grant business unit access.

  • Grant tableset access.

  • Grant ledger access.

  • Grant nVision reporting access.

  • Grant project access.

  • Grant business unit book access.

  • Grant pay cycle access.

  • Grant grants access.

  • Grant proposal management access.

  • Grant planning instance access.

Access the Business Unit Security by Permission List page (Set Up Financials/Supply Chain, Security, Unit by Permission List, Business Unit Security by Permission List).

For each primary permission list, select the accessible business units.

Access the Business Unit by User ID page (Set Up Financials/Supply Chain, Security, Unit by User ID, Business Unit Security By User ID).

For each user ID, select the accessible business units.

Access the TableSet Security by Permission List page (Set Up Financials/Supply Chain, Security, TableSet by Permission List, TableSet Security by Permission List).

For each primary permission list, select each accessible SetID.

Access the TableSet Security by User ID page (Set Up Financials/Supply Chain, Security, TableSet by User ID, TableSet Security by User ID).

For each user ID, select each accessible SetID.

Access the Ledger Security by Permission List page (Set Up Financials/Supply Chain, Security, Ledger by Permission List, Ledger Security by Permission List).

For each primary permission list, select each accessible ledger type. Commitment and Summary ledger types require a ledger name. Detail ledger types require a ledger group name.

Access the Ledger by User ID page (Set Up Financials/Supply Chain, Security, Ledger by User ID, Ledger Security by User ID).

For each user ID, select each accessible ledger type. Commitment and Summary ledger types require a ledger name. Detail ledger types require a ledger group name.

Access the nVision Ledger Security page (Set Up Financials/Supply Chain, Security, nVision Ledger Security).

For each user ID, select each accessible business unit and corresponding ledger. You can specify multiple ledgers for each business unit.

While the purpose of all these pages is to provide row-level security, the appearance of the pages varies based on the method of project row-level security that you implement.

This table lists the purpose of each project security method and the actions that you take on the Security Options page (Set Up Financials/Supply Chain, Security, Security Options, Security Options) and Project Security page (Set Up Financials/Supply Chain, Security, Project Security, Project Security) to implement each method:

Security Method

Purpose

Security Options Page Actions

Project Security Page Actions

Team-based security

Grants access to projects based on an employee's membership in a project team.

  1. Select User ID Level Security in the Type of Security group box.

  2. Select Project in the Secured Fields group box.

  3. Select Use list in the Proj Security Type (project security type) field.

View a read-only list of all projects for which the user is a team member, and the member's security profile for each project.

User, tree-based security

Grants access to projects based on selected nodes on a project tree.

  1. Select User ID Level Security in the Type of Security group box.

  2. Select Project in the Secured Fields group box.

  3. Select Use tree in the Proj Security Type field.

Define security for a user. Specify the project tree that the system uses for controlling project security, select nodes (projects) on the tree to grant each user access to specific projects, and select the user's project role on each project.

Permission list, list-based security

Grants access to permission lists that enable users to access projects that are attached to that permission list.

  1. Select Permission List Level Security from the Type of Security group box.

  2. Select Project in the Secured Fields group box.

  3. Select Use list in the Proj Security Type field.

Define security for a permission list. Within a specific permission list to which users have access, specify the business units, project IDs, and project roles.

Permission list, tree-based security

Grants access to permission lists that enable users to access projects that belong to a tree that is attached to that permission list.

  1. Select Permission List Level Security from the Type of Security group box.

  2. In the Secured Fields group box, check Project.

  3. Select Use tree in the Proj Security Type field.

Define security for a permission list. Specify the project tree, project (tree node), and project role.

A user's project security profile further defines the degree and type of access that the user has to project data.

See Defining Project Security.

Access the BU Book/Perm List page (Set Up Financials/Supply Chain, Security, AM Book by Permission List, BU Book/Perm List).

For each primary permission list, select each accessible business unit and corresponding book name. You can specify access to multiple books for each business unit.

Access the BU Book by User ID page (Set Up Financials/Supply Chain, Security, AM Book by User ID, BU Book by User ID).

For each user ID, select each accessible business unit and corresponding book name. You can specify access to multiple books for each business unit.

Access the PayCycle by Permission List page (Set Up Financials/Supply Chain, Security, Pay Cycle by Permission List, Pay Cycle by Permission List).

For each primary permission list, select the accessible pay cycles.

Access the PayCycle by User ID page (Set Up Financials/Supply Chain, Security, Pay Cycle by User ID, Pay Cycle by User ID).

For each user ID, select the accessible pay cycles.

Access the Grants Operator Security page (Set Up Financials/Supply Chain, Security, Grants Security, Grants Operator Security).

For each user ID, enter the grants security tree SetID, tree name, and the effective date of the tree. On the lower section of the page, enter the departments and an appropriate access code. You can enter as many departments as needed.

This is one step in a multistep security process that is described in detail in the PeopleSoft Grants product documentation

Access the Proposal Management Security page (Set Up Financials/Supply Chain, Security, Proposal Management Security, Proposal Management Security).

For each user ID, enter the proposal security tree SetID, tree name, and the effective date of the tree. On the lower section of the page, enter the departments and an appropriate access code. You can enter as many departments as needed.

This is one step in a multistep security process that is described in detail in the PeopleSoft Proposal Management product documentation.

Access the Planning Instance page (Set Up Financials/Supply Chain, Security, Problem Instance by User ID, Planning Instance).

If you access problem instance by user ID, you can grant access to planning instances by user ID.

If you access problem instance by permission list, you can grant access to planning instances by permission list.

Security for planning instances is further described in Supply Planning documentation.