FAQ – Deny a Need 1. What does “Deny a Need” mean? Denying a need allows a contributor or approver to reject a training need submitted in a Task Plan. When a need is denied, the reason must be provided and recorded in the system. 2. Where can I deny a need? Needs can be approved or denied in the Training Needs tab. To deny a need: Click the “Deny” button next to the need. Enter the reason for denial in the required field. Confirm to proceed. This information is stored in the audit log and visible in the need’s details. 3. Who can deny a need? Task Plans with Workflow Hierarchical Approval enabled Any user, organizational unit, or relationship higher than the contributor/approver of the training need can deny it. Task Plans with Workflow Hierarchical Approval disabled Any configured approver of the contributor can deny the need. 4. Contributors without approvers A new configuration allows contributors who have no approvers to deny a need that they assigned and that was automatically approved. This can be configured: Globally : Preferences > Task Plans Global Configurations (section 3.2.1 of the User Manual) Per task : Task Configuration > General > Additional Information (section 6.4.8 of the User Manual) When enabled: Needs assigned by a contributor with no approvers are automatically approved. The contributor can reverse the approval and deny the need . This applies to needs from both the catalog and imported needs . 5. Examples when the Deny button configuration is enabled Manager without approvers A manager assigns a need to a subordinate. The need is automatically approved. He can still reverse the approval and deny the need. End-user without approvers An employee assigns a need to himself. The need is automatically approved. He can reverse the action and deny the need. L&D with multiple profiles Users can select which profile to use when denying a need. 6. Examples when the Deny button configuration is disabled L&D without approvers An RH responsible (L&D) assigns a need to a user. The need is automatically approved. The L&D cannot reverse the approval or deny the need. End-user without approvers An employee assigns a need to himself. The need is automatically approved. He cannot reverse the action and deny the need. 7. Effect on budget When denying a need in a Task Plan with a budget, the cost of the denied need is removed from the budget . 8. Bulk Deny Users with deny permission can perform a bulk deny operation during the planning phase and within their contribution period. This allows multiple needs to be denied in a single action. For details on bulk operations, see section 7.7.13 of the User Manual . 9. Audit and tracking All Deny actions are recorded in the audit log for transparency. The original contributor remains associated with the need for tracking and notifications.

Deny a Need - Training Plans Support

FAQ – Deny a Need

1. What does “Deny a Need” mean?

Denying a need allows a contributor or approver to reject a training need submitted in a Task Plan. When a need is denied, the reason must be provided and recorded in the system.

2. Where can I deny a need?

Needs can be approved or denied in the Training Needs tab. To deny a need:

Click the “Deny” button next to the need.
Enter the reason for denial in the required field.
Confirm to proceed.

This information is stored in the audit log and visible in the need’s details.

3. Who can deny a need?

Task Plans with Workflow Hierarchical Approval enabled

Any user, organizational unit, or relationship higher than the contributor/approver of the training need can deny it.

Task Plans with Workflow Hierarchical Approval disabled

Any configured approver of the contributor can deny the need.

4. Contributors without approvers

A new configuration allows contributors who have no approvers to deny a need that they assigned and that was automatically approved.

This can be configured:
- Globally: Preferences > Task Plans Global Configurations (section 3.2.1 of the User Manual)
- Per task: Task Configuration > General > Additional Information (section 6.4.8 of the User Manual)
When enabled:
- Needs assigned by a contributor with no approvers are automatically approved.
- The contributor can reverse the approval and deny the need.
- This applies to needs from both the catalog and imported needs.

5. Examples when the Deny button configuration is enabled

Manager without approvers
- A manager assigns a need to a subordinate.
- The need is automatically approved.
- He can still reverse the approval and deny the need.
End-user without approvers
- An employee assigns a need to himself.
- The need is automatically approved.
- He can reverse the action and deny the need.
L&D with multiple profiles
- Users can select which profile to use when denying a need.

6. Examples when the Deny button configuration is disabled

L&D without approvers
- An RH responsible (L&D) assigns a need to a user.
- The need is automatically approved.
- The L&D cannot reverse the approval or deny the need.
End-user without approvers
- An employee assigns a need to himself.
- The need is automatically approved.
- He cannot reverse the action and deny the need.

7. Effect on budget

When denying a need in a Task Plan with a budget, the cost of the denied need is removed from the budget.

8. Bulk Deny

Users with deny permission can perform a bulk deny operation during the planning phase and within their contribution period.
This allows multiple needs to be denied in a single action.
For details on bulk operations, see section 7.7.13 of the User Manual.

9. Audit and tracking

All Deny actions are recorded in the audit log for transparency.
The original contributor remains associated with the need for tracking and notifications.

Deny a Need