User Access Manager

This page is accessed via Configuration and Administration > User Configuration > Manage User Access.

Note: You must be logged in with ADMIN privileges to access this page.

The User Access Manager provides options that control access to objects of the a variety of User Access Types. Access to these objects is based on a hierarchical security model. The top of the hierarchy is the DOMAIN. All objects configured for access at this level are visible to all users in that domain. The most specific level contains items defined for an individual user and cannot be seen by other users.

Note: Level and User Role can be used in much the same way. You may choose to only use one or the other.

The security model is defined as hierarchical because each level can inherit access to objects from the level above it (select both a level and a user role for an additional level in the hierarchy). The following is from general to most specific:

Domain
User Role + Domain
User Level + Domain
OR
User Level + User Role + Domain
User + User Level + User Role + Domain

If there is conflicting access between levels, the access from the lowest, most specific level is used. So if the user role and domain have conflicting access, the access for the user role is used.

Note: Be careful when assigning broad User Access at the Domain, and Domain+Level level since it will impact all users in that Domain or with that Level.

Include.../Exclude...

However, this inheritance is configurable for the following pages: Ask Oracle Saved Query, Global Search, Saved Query, Screen Set, and User Menu. When defining access for these pages, one of the following types of inheritance can also be defined:

Include... allows you to specify data to include such as saved queries
Exclude... allows you to specify data to exclude such as saved queries

Preventing Access Changes

In addition to defining the type of inheritance, administrators can also define objects at a given level as being the final level for access configuration. This allows administrators to prevent users from altering the behavior of the Oracle Transportation Management system and ensure a more consistent application behavior for all users.

Defining User Access

Select a User Access Type from the drop-down list.
Select a User.
Select a Level for the user.
Enter a User Role ID.
If you have proper access to choose a Domain, the Domain Name field will be a drop list. Select the Domain Name you want the associated User Access Records to be created or modified in. This domain selection is typically only different from user's domain when the user will be changing user roles that have a different VPD Domain Name specified.
Click the Edit User Access button. The layout of the following page changes depending upon which user access type you selected.

User Access Types

Default Access

Menu Access

By default, all new users in a domain are assigned access to the ADMIN or DEFAULT public menus depending on the level that was assigned to the user. However, you can configure new menus and override the default access grants.

If you unassign access to a user-defined menu, the system defaults are used.

Action Checks Access

By default, there are no checks.

Action Execution Access

By default, there is no security change so you have access as the user that is logged in. See the Action Execution topic for more details.

Action Reasons Access

By default, no reasons are required.

Ask Oracle Saved Query

By default, any user-specific saved query will be visible on the Rate Inquiry window unless excluded on this page.

Field Screen Set Access

By default, all field screen sets are configured using the PUBLIC screen sets. Use the Screen Set Manager to create new screen sets that can be used as field screen sets and assign the appropriate access. See the Configure Field Screen Set Access topic for more details.

Global Search Access

By default, when you enter characters to search for in Global Search you only see matching menu links and saved queries. Users have no screen sets added to the Global Search access by default. You must include access to screen sets (such as buy shipment or order releases) to search for business objects like shipments and orders in the Global Search field.

Note: The default criteria on the specified screen sets are used when searching.

Power Actions Access

If no power actions are defined for a user, then they have access to all actions. If some power actions are defined then that user has access to only those actions.

Report Workspace Access

By default, there are no reports pre-configured. See the Configuring Report Workspace User Access topic for more details.

Saved Query Access

By default, a user has access to all saved queries that are created in a domain. Use the Access Manager to limit the saved queries that appear on Search pages.

Screen Set Access

By default, all new users in a domain are assigned access to the public Screen Sets which are configured on the ADMIN and DEFAULT public menus. You can configure a new Screen Set, add it to a user-defined menu, and then assign access to the Screen Set. If you do not assign access to the Screen Set, it appears as a link on a menu but an error results if the user clicks the link.

If you unassign access to any user-defined screen set, Oracle Transportation Management reverts back to the default system default assignments to the public screen sets.

Settings and Actions

By default, all users can see all sections of the Settings and Actions page. See Settings and Actions User Access for more details.

Status Type Filter

If you have created a status type filter you must associate it with a user and domain in order for the filter to take effect. See the Status Type Filter Access topic for more details.

User Preference Access

By default, all users inherit default system preferences until you create a new preference set and make an assignment.

Workbench Access

By default, a user has access to all workbench layouts in any domains to which they are granted access. See Configure Workbench User Access for more details.