Description:

Currently, we have the CHANGE_SELECTED_EMPLOYEE permission, which is used in the site header to allow users to switch between employees and view their details. However, reusing this permission for other cases (like selecting employees when creating projects, teams, or tasks) could lead to unintended side effects.

To solve this, we propose adding a new global permission:

🔹 New Permission: `SELECT_EMPLOYEE`

Purpose: Allows an employee to select other employees only during specific processes (e.g., creating a project, team, task, or expense).
Restriction: This permission does not allow changing the currently selected employee in the site header.

🔸 Existing Permission: `CHANGE_SELECTED_EMPLOYEE`

Purpose: Allows switching between employees in the site header to view details of another employee.
Scope: Affects the global selection context in the application.
Why it can't be reused: Using it for general employee selection would allow unintended modifications to the global employee context.

Implementation Plan:

Introduce the new SELECT_EMPLOYEE permission.
Ensure it is checked in relevant processes (project/team/task creation, etc.).
Keep CHANGE_SELECTED_EMPLOYEE strictly for employee switching in the site header.
Review all areas where employee selection logic is used to avoid conflicts.

[Enhancement] Introduce SELECT_EMPLOYEE Permission for Controlled Employee Selection #8835

Company

Community

Support

Connect