This document outlines the step-by-step process for configuring role-based access in uKnowva using the Subadmin Modules and Sub Admin Access Rule features. Real-life use cases and ready-to-use configurations are also included.

Step 1: Configure Subadmin Modules

1. Log in with uKnowva Admin Access.
2. Navigate to the right-hand menu and click on Subadmin Modules.
3. Click on Add New.
4.  Fill in the following fields:

• Module Name: A user-friendly name (e.g., Attendance - Team Atten).
• Component Name: Select the internal module (e.g., HRM Lite, recruitment, kraandratings).
• View Name: A technical view identifier (e.g., attendance).
• Tasks: Comma-separated list of actions (e.g., employees,downloadattendancereport).
• Published: Set to Yes & Click Save.

Step 2: Determine View Name and Tasks from Menu Manager

1. Navigate to uKnowva Config > Menu Manager.
2. Locate the relevant menu item.
3. Look at the Menu Link:

• Extract View Name from view=XYZ.
• Extract Task Name from cmd=XYZ.taskname.
• Ignore any URL parameters after &.

Example 1:

index.php?option=com_workflowengine&view=workflowengine&cmd=workflowengine.myrequest

• View: workflowengine

• Task: myrequest

Example 2:

index.php?option=com_hrm&view=attendance&cmd=attendance.calendar

• View: attendance

• Task: calendar

Step 3: Assign Subadmin Access Rule

1.  Navigate to Sub Admin Access Rule from the right-hand menu.
2. Click Add.
3. Fill in the following fields:

• Admin Access Name: Give the rule a meaningful name.
• Admin Access Group / Users: Select target user group(s) or user(s).
• Exclude Groups/Users: Optionally exclude certain users.
• Modules: Choose the module configured in Step 1.
• Target Audience: Select All or Set as per profile field specific eg employees whose location is 'Mumbai Office'
• ePublished: Set to Yes & Save details.
  

Ready-to-Use Role-Based Configurations

The following configurations can be applied when you have multiple admins—such as location-wise HR—who need access to detailed information about their respective teams.

Notes:

• Always validate the view and task names using Menu Manager before configuration.
• Keep Subadmin Modules and Access Rules named consistently by location or role.
• Regularly review rules and modules to ensure they align with org structure changes.