Improved feature: Training request display logic

(Note: This feature was improved during sprints 628–630, with the latest update deployed on June 27.)

Small adjustments have been made to the training request logic to fix inconsistencies in how training buttons and messages were shown to users. While the functionality itself isn’t new, this is a good opportunity to provide a clear overview of how it works, especially for those who may not be familiar with all the options.

Resources can be configured to require training, display training as optional, or use both settings together offering flexibility depending on the access and training needs.

Available training settings per resource

Each resource can be configured to:

• Require training – Users must complete a training before booking
• Display training – Training is optional and shown as an available action

Both of these settings include an additional option:

• "Only if access" – The training button is only shown to users who already have access to the resource

How it works in practice

Training required

• Button is shown whether or not the user has access
• Button is hidden if the user has a closed training request
• The message “Training requested” appears if there is a pending, active, inactive, or rejected request
• If the user does not have access, access can be granted automatically once the training is completed

Training required / only if access

• Same as above, but the button is only shown to users who already have access

Training displayed

• Button is always shown unless a training request is already in progress
• Works with or without access
• Ideal for optional training

Training displayed / only if access

• Same as above, but the button is only visible to users with access