Record Access Tab of Roles
Use the Record Access tab to determine a role's access rights to specific menus and records in DPS. For example, a project manager needs full access to records in the Projects hub, but a project consultant only needs read access to these records.
Even if a role does not have access to a hub, you can still set up record level read and update criteria for reporting purposes. Before you can assign access rights to any DPS application, you must activate the application on the Modules tab in
in the browser application.Contents
Application Record Access Grid
Use this grid to control the role's access to portions of DPS, including access to menu items and records. Options on this grid depend on the DPS modules that are activated.
Field | Description |
---|---|
Application Record Access Drop-down |
Click the drop-down arrow on a grid header to complete any of the following actions:
Not all options are available on all grids. |
Application | Select the DPS application for which you want to establish access rights. The applications that display depend on the DPS applications that you install. |
Access | Click in this field, and use the drop-down list to select the access rights for the selected item.
The Access column is view-only for certain applications. You must use the DPS default for these applications. Options for Billing Terms If you did not select
Billing Terms on the General tab, you can select one of the following settings to specify access to billing terms:
Users who only have this access to fee information and the description in Billing Terms cannot use the Billing Terms link in the Navigation pane, in the Projects hub, or in Interactive Billing to display the Billing Terms form. They can only display the fee information using the Update Fees options in Invoice Approvals, Interactive Approvals, or Interactive Billing (assuming they have access to one or more of those forms). Options for Employee Assignments and Generic Assignments The access options for Employee Assignments and Generic Assignments are Can Add and Can't Add. If you select Can Add, use the Record Level Update field to specify the employees and generic resources for which the role can add and update assignments in project and opportunity plans. Regardless of the option you select, you can use Record Level View to specify the employees and generic resources for which the role can view plan assignments. |
Record Level View |
Click in this field, and then click to open a lookup dialog box and determine the records that members of this role can view within the selected application. For example, you might give a role the ability to see a client type firm's information in the Firms hub for only a subset of firms that are identified as clients. This setting also controls the list of records that are returned in the search results list in lookup fields and user-defined lookup fields for this application that appear in other applications (such as in the Primary Client lookup field in the Projects hub). The role's access rights that are entered in the Access field in the Application Record Access grid supersede the record level view rights that are entered in the Record Level View field. You cannot give a role permission to view a record if the role does not have permission to access the corresponding application. The default entry for this field is Not in Use. Exceptions and Additional Information for the Employees Hub The record level view setting that you assign for the Employees hub application:
For more information about the Employee Card, see Employee Card. Employees Hub Example You set up record level view security so that security role A can view only one employee, Emily Collins. John is assigned to role A. Outcome:
Firms Hub Example You set up record level view security so that security role A can view only one client, Brown and Associates. John is assigned to role A. Outcome:
|
Record Level Update | Click in this field, and then click
to open a lookup dialog box and determine the records that this role can update within the selected application. For example, you might give a role the ability to update information about only a subset of
client type firms in the
Firms hub.
The default for this field is Same as View, meaning that the Record Level Update setting is the same as the Record Level View setting. The role's Access settings supersede Record Update View rights. You cannot give a role permission to update a record if the role doesn't have permission to access the corresponding application. |