User roles

User roles, such as supervisor and manager, describe the duties that an employee performs and the relationship of the user to other employees. For example, if Employee A is the supervisor of Employee B, then Employee A’s user account is assigned the Supervisor role for Employee B's team. User roles apply to the entire team, so now Employee A is Supervisor for that entire group of employees.

The system comes pre-configured with a number of roles. Some of these roles have very specific behaviors while other roles are for use in any implementation:

  • GENERAL ACCESS

    Typically used for non-supervisory access such as users who perform schedule edits or administrators.

  • Can Approve Time

    Used to control approvals when work detail approval is enabled.

  • Supervisor Role

    Used to control a manager's ability to set their own availability. Operates in conjunction with the registry parameter CAN_SUPERVISOR_APPROVE_OWN_AVAILABILITY. See "Availability Management Registry Parameters" in the Infor Workforce Management Registry Parameter Reference Guide.

  • PAYROLL

    Standard role for payroll access. With this role, the user will typically modify timesheets and export payroll.

  • MANAGER

    This role is optional and can be used in addition to or in place of the SUPERVISOR role.

  • BUDGET MANAGER

    This role is used in conjunction with the Budget Creation and Management module. This role indicates that the user is the person in charge of making or approving budget changes for their part of the organization.

  • GATEKEEPER

    This role is used in conjunction with the Task Management module. This role indicates that this user is the person responsible for releasing tasks that are assigned to teams within their part of the organization.

Additional roles can be created within any implementation. When creating user roles for teams, you can create a regular role or a “virtual” role for the team. A role is defined as virtual if more than one user fulfills the same role for the same team. For example, if two employees co-manage a store, each of their users could be designated as a virtual-manager role for the store. If only one person will ever fill the role, the role does not need to be a virtual role.

Parameters on each role determine if users with that role are supervisors and if the users can approve time. Roles are also used to route different processes through workflows. The workflow specifies a role and the system will find the user who fills that role. The system then routes the workflow to that user for action. All workflows in the system are initially set to use one of the pre-configured roles that are listed above. You can change those workflows to be routed to any role your organization creates.