This page (revision-11) was last changed on 26-Nov-2021 10:22 by RForbes

This page was created on 26-Nov-2021 10:22 by Administrator

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
11 26-Nov-2021 10:22 4 KB RForbes to previous
10 26-Nov-2021 10:22 4 KB JMyers to previous | to last
9 26-Nov-2021 10:22 4 KB JEscott to previous | to last
8 26-Nov-2021 10:22 3 KB JMyers to previous | to last
7 26-Nov-2021 10:22 3 KB JMyers to previous | to last
6 26-Nov-2021 10:22 3 KB JMyers to previous | to last
5 26-Nov-2021 10:22 3 KB JMyers to previous | to last
4 26-Nov-2021 10:22 4 KB JMyers to previous | to last
3 26-Nov-2021 10:22 1 KB Administrator to previous | to last
2 26-Nov-2021 10:22 1 KB Administrator to previous | to last
1 26-Nov-2021 10:22 166 bytes Administrator to last

Page References

Incoming links Outgoing links
IMUR
IMUR

Version management

Difference between version and

At line 16 added 32 lines
ASSIGN ROLES TO USERS
The Assign Roles to Users (IMUR) screen is used to assign roles to users, giving them certain security restrictions or other capabilities.
This section explains the Assign Roles to Users screen and its associated fields.
You may access this feature through the Screens/Forms menu:
Application Administration > Security > Assign Roles to Users
There are several base roles in the application supplied by High LineMckesson.
P2K_USER
This role is required for all users and provides the user with basic rights and privileges.
P2K_MASTER P2K_Master is an application role only with no database rights or privileges assigned. This is an initial startup role that has all screen and report execution rights in it. As such, this role should not be assigned to your regular users, but rather to new roles with execution rights specific to the tasks assigned to that user.
P2K_DBA This is the database administrative role that should only be given to a minimum number of users that are part of your technical team and senior users.
DISC_USER This is an optional role that can be defined with a High LineMckesson supplied script to create a default role in both the database and the application. This role can now be added to a user and removed inside of the application. This role will allow those users to make use of the discoverer application with all the database selectivity within the user’s application rights.
‘Assign Roles to Users’ Usage and Examples
User
This field identfies the user you wish to assign the role to.
Seq #
If the user profile has been assigned more than one role, this field identifies the order in which the roles will be presented when the user logs in. (Mandatory)
All roles must have unique sequence numbers.
This is important as there is a direct correlation between the sequence number and the order in which the icons are displayed in the Self Service header.
The lowest sequence number will be displayed furthest to the left whereas the role with the highest sequence number will be displayed furthest to the right.
The role with the highest sequence reflects the default module that the user will be in when they sign into Self Service.
Role
This field allows you identify the role you wish to assign to the user.
Role Type
The role is categorized into a specific type in this field.
Business Focus Role
Default
If this toggle is checked, the role will be the user’s default role.
This page (revision-11) was last changed on 26-Nov-2021 10:22 by RForbesTop