Assigning Permissions

OPTIONAL FEATURE - Contact your RizePoint representative to enable/disable this option.

If you're going to provide access to program administration through a role assignment, you'll need to create a role for the person administering the program, then assign the required permissions to the role. See Creating a Role, below.

In most cases, however, you'll only have a single person administering a program, so it would be easier to assign access directly to the user.

You'll need to make sure that the required permissions are assigned to the user or role.

On the Permissions tab of the User or Role profile, add the following permissions:

• PROGRAM ADMIN - Allows users to edit existing programs, manage the Notification Library, and edit Task Types.
• PROGRAM ASSIGN - Allows users to specify which locations are included in a program.
• PROGRAM CREATE - Allows users to create new programs or delete existing programs.
• PROGRAM VIEW - Allows users access to the Program menu option.

Optional permissions:

• PROGRAM VIEW ALL - Allows users to view all programs that have been created, not just those to which they have been given access. You may or may not want to assign this permission to the program administrator. In many cases, this permission may be reserved for the System Administrator of your organization only.
• LOCATION - PROGRAMS TAB - Displays the Programs tab in the Location profile. It also allows users to complete tasks and to undo the completion of tasks. If you want the program administrator to also have access to the Programs tab of the Location profile, this permission must also be granted.

PROVIDING PERMISSION TO COMPLETE TASKS

The Primary Contact of any location assigned to a program must have the LOCATION - PROGRAMS TAB permission. Without it, he/she will not have access to programs to which they have been assigned. This permission not only provides access to the tab, it also allows users to complete tasks. Note that if the program, or tasks within the program, are to be delegated to other users, those users (secondary contacts) must also have the this permission in order to view programs and complete assigned tasks.

CREATING A PROGRAM COMPLIANCE ROLE (optional)

If the number of users required to administer programs is quite small, you may want to consider assigning programs to users directly, rather than through a role assignment.

In many cases you may require only a single role. In addition, you may only need a single user assigned to this role. For example, if only one person in your organization is responsible for overseeing all programs, then you would create a single role, perhaps called Program Administrator, and then assign that person to the Program Administrator role. If, instead, your organization has one person in charge of Safety programs, and another person in charge of Training programs, then you might want to create two roles; one for each type of program. Even so, assigning access directly to a user may be preferable.

ref: Programs