Project

General

Profile

Actions

Improvement #29742

open

CBT Admin || User Access Control with Multi-Selection for Branch, Region, Region Unit, and Department

Added by Aysha Fida 5 months ago. Updated 3 months ago.

Status:
On hold
Priority:
Normal
Assignee:
Target version:
-
Start date:
11/11/2025
Due date:
% Done:

30%

Estimated time:
24:00 h
Spent time:
remarks:
DB Changes:
Keys & Permissions:
Areas Affected:
Files Changed:

Description

A Epic: Admin Permissions & Employee Access Management
USER STORY
For user with authority- a person who has the permissions,
I want to define user access permissions (branch, region, region unit, department) with multi-selection capability
So that roles and employees can have flexible and accurate access control across multiple organizational units.

DESCRIPTION (DETAILED)
PART 1: New Permission strip in Admin Settings
Suggested Strip Name: “User Access Control” .

Inside this Strip:
Add fields for assigning permissions:
  1. Access Multi Branch
  2. Acess Multi Region
  3. Acess Multi Region Unit
  4. Acess MultiDepartment

Admin can assign which branches/regions/region units/departments a particular role or user can access.
These permissions will drive visibility and access for users throughout the system (e.g., forms, approvals).

PART 2: Role Permission Integration
The roles created under Role Management should automatically inherit access based on the permissions configured in the new User Access Control tab.
Each role should only be able to perform actions or view data within the boundaries of the permissions given (Branch, Region, Region Unit, Department).
The User Access Control configuration determines:
Which Departments they can approve.
Which Regions/Branches their dashboard or reports show.
Which Employees they can view/manage.

Example:
If the “Regional Manager” role has access to Region: Middle East, they can:
View and approve requests only from Middle East branches.
See employees assigned to those regions.

PART 3: Multi-Selection in Employee Creation Form
Add multi-select dropdowns in the Employee Creation / Edit Form for:
Department
Region
Region Unit
Branch

Logic & Conditions:
If Region and Region Unit are manually created, then show multi-select option for both fields.
The available options in these dropdowns should be filtered based on the permission defined in the “User Access Control” tab.

Example Behavior:
Admin creates new employee “John Smith” (General Manager).
Selects multiple departments: HR, Finance, Operations.
Selects multiple branches: Kuwait Main, Dubai Head Office.
Based on the role assigned and access permission, John will have access to approve.

SCENARIOS & USE CASES

Scenario 1: General Manager Access
A General Manager is responsible for approvals across multiple departments.
Multi-selection allows assigning HR, Finance, and Operations departments during employee creation.
So John (GM) can approve requests across all departments he’s linked to.

Scenario 2: Temporary Delegation in Absence
If a Department Manager (e.g., HR Manager) is on leave, another manager can be assigned to handle HR approvals.
Through multi-selection, the temporary manager can be assigned additional department access (HR + their existing one) so work continues smoothly.

ACCEPTANCE CRITERIA

1 Tab Creation A new tab “User Access Control” appears under Admin Settings → Permission Category.
2 Acess Multi selection Fields Branch, Region, Region Unit, and Department fields
3 Permission Mapping Admin can assign multiple branches/regions/departments to roles.
4 Role Access Control Role permissions are restricted to the selected organizational units.
5 Employee Form Update Multi-select options for Branch, Region, Region Unit, Department are visible during employee creation.
6 Conditional Display Region & Region Unit multi-selection appear only if manually created.
7 Data Filtering Employees see/manage data only from assigned branches/regions/departments.
8 Approval Access Approvers (e.g., GM, Managers) can act on requests across assigned departments.
9 Delegation Support Admin can easily assign additional access in the employee form for temporary coverage.

EXAMPLE DATA FLOW
Admin → Access Mapping → Assign multiple departments to Role “General Manager”.
Employee “John” created with Role = General Manager → Multi-select (HR, Finance, Ops).
John logs in → System fetches his assigned departments → Approvals list shows only those.
If HR Manager is on leave → Admin adds HR department temporarily to another manager → That manager gains HR approval access until removed.

B * Add dropdown in dashboard*

For the above mentioned user,should be able see the dashboard based on region,region unit,branch,department also, for the permission that are given in user access control.

Actions #1

Updated by Arun S 5 months ago

  • Project changed from CBT Admin to 371
  • Category set to Functionality
  • Target version set to Version 1 - Initial Scope
Actions #2

Updated by Aysha Fida 5 months ago

  • Description updated (diff)
  • Assignee set to Shamini K N
Actions #3

Updated by Aysha Fida 5 months ago

  • Description updated (diff)
Actions #4

Updated by Aysha Fida 5 months ago

  • Description updated (diff)
Actions #5

Updated by Aysha Fida 5 months ago

  • Description updated (diff)
Actions #6

Updated by Shamini K N 5 months ago

  • Due date set to 11/12/2025
  • Status changed from New to Assigned
  • Start date changed from 11/07/2025 to 11/11/2025
  • Estimated time set to 16:00 h
Actions #7

Updated by Shamini K N 5 months ago

  • Status changed from Assigned to In Progress
Actions #8

Updated by Shamini K N 5 months ago

  • % Done changed from 0 to 30

Permissions added
Access to Multiple Department permissions implemented in the employee module
Code/stored procedure modification done based on multi-department access

Actions #9

Updated by Shamini K N 5 months ago

  • Status changed from In Progress to On hold
  • Estimated time changed from 16:00 h to 24:00 h

The Qgo CBT priority tasks need to be completed. This feature will be implemented at the product level.

Actions #10

Updated by Shamini K N 5 months ago

  • Due date deleted (11/12/2025)
Actions #11

Updated by Shamini K N 3 months ago

  • Project changed from 371 to CBT Admin
  • Category deleted (Functionality )
  • Target version deleted (Version 1 - Initial Scope)
Actions

Also available in: Atom PDF