diff --git a/docs/integration/vision/gift/introduction.md b/docs/integration/vision/gift/introduction.md
index 3a9ee5e..1c3e77e 100644
--- a/docs/integration/vision/gift/introduction.md
+++ b/docs/integration/vision/gift/introduction.md
@@ -4,7 +4,7 @@ sidebar_position: 1
# Introduction
-The Gifts feature, accessible through **Main Dashboard > Wallet > Gifts**, allows managers to create digital gifts. All users can then redeem these gifts using coins earned by completing missions.
+The Gifts feature, accessible through **Main Dashboard > Wallet > Gifts**, allows managers to create digital gifts that all users can redeem using coins earned from completing missions.
|||
|:--------------------------------|:--------------------------------|
diff --git a/docs/integration/vision/gift/manager.md b/docs/integration/vision/gift/manager.md
index 59938a0..b0a692d 100644
--- a/docs/integration/vision/gift/manager.md
+++ b/docs/integration/vision/gift/manager.md
@@ -32,7 +32,7 @@ After manager creates a gift, users will receive notification regarding the new
| **Redemption Validity Start Date** | The first date when the gift can be redeemed. | Required |
| **Redemption Validity End Date** | The last date when the gift can be redeemed. | Required |
| **Clear** | Clears all content on the current page. | - |
-| **Next** | Navigates to the previous page. | - |
+| **Next** | Navigates to the next page. | - |
3. Gift Redemption Criteria
@@ -41,8 +41,8 @@ After manager creates a gift, users will receive notification regarding the new
| Properties | Description | Note |
|:-----------------------------|:-----------------------------------------------------------------------------------|:--------:|
| **Redeem Coins** | To specify the amount of coins required to redeem the gift. | Required |
-| **Category** | To select a category to classify the gift, such as Uncategorised, Food & Beverages, Shopping, Service, Entertainment, Digital Goods, or Travel Accommodation. | Required |
-| **Available Quantity** | To specify the total number of units of the gift that are available for redemption. | Required |
+| **Category** | To classify the gift, such as Uncategorised, Food & Beverages, Shopping, Service, Entertainment, Digital Goods, or Travel Accommodation. | Required |
+| **Available Quantity** | To specify the total number of gift units available for redemption. | Required |
| **Max Allowable Redemption Per Employee** | To specify the maximum number of times a user can redeem the gift.| Required |
| **Attactment** | To upload an image associated with the gift, such as a product photo or promotional graphic, through the mobile's camera or gallery. | - |
| **Clear** | Clears all content on the current page. | - |
@@ -51,7 +51,7 @@ After manager creates a gift, users will receive notification regarding the new
## Gift Update
-1. Choose Gift - To update a gift, the manager can go to **More icon > Manage Gift** and select the gift want to be update.
+1. To update a gift, the manager can go to **More icon > Manage Gift** and select the gift to be updated.
|| |
|:------------------------------------|:-----------------------------------------------------|
@@ -85,20 +85,19 @@ After clicking **Issue**, select **Confirm** to complete issuing the gift.
### Check Issuance
-To check completed issuances, **toggle on Issued Gift**s to display the latest issued gift.
+To check completed issuances, **toggle on Issued Gifts** to display the latest issued gift.
|| |
|:------------------------------------|:-----------------------------------------------------|
## Manage Gift
-
### Gift Status
|Active Gifts|Inactive Gifts |
|:--------------------------------|:---------------------------------|
|||
-|Propertise|Description|
+|Properties|Description|
|:--------------------------------|:--------------------------------|
|**Inactive Gifts Switch - Toggle Off**|Displays all active gifts.|
|**Deactivate**|Deactivate all currently selected active gifts|
diff --git a/docs/integration/vision/gift/user.md b/docs/integration/vision/gift/user.md
index baabaac..207c2bb 100644
--- a/docs/integration/vision/gift/user.md
+++ b/docs/integration/vision/gift/user.md
@@ -10,26 +10,26 @@ These feature are available to both **manager** and **employee**.
:::
-## Gift Redeem
+## Gift Redemption
-1. Gift Filter Type
+**1. Gift Filter Type**
|Gift Category Filter Chip|Filter Drawer|
|:--------------------------------|:--------------------------------|
|||
-|Propertise|Description|
+|Properties|Description|
|:--------------------------------|:--------------------------------|
-|**Gift Category Filter Chip**|Displays all gifts that match any of the chosen categorie.|
+|**Gift Category Filter Chip**|Displays all gifts that match any of the selected categories.|
|**Clear**| Deselect all the selected filter option.|
-|**Shop By Price Filter**|Display gifts that match any of the chosen specific price ranges.|
+|**Shop By Price Filter**|Display gifts that match any of the selected specific price ranges.|
|**Sort by Featured**|Display the gifts bassed on popularity in descending order.|
|**Sort by Newest**|Display the most recently added gifts in descending order.|
-|**Sort by Price: High-to-Low**|Display gifts from expensive to cheap.|
-|**Sort by Price: Low-to-High**|Display gifts from cheap to expensive.|
+|**Sort by Price: High-to-Low**|Display gifts from most expensive to least expensive.|
+|**Sort by Price: Low-to-High**|Display gifts from to least expensive to most expensive.|
|**Reset**|Select all the filter options again.|
-2. Select gift - After selecting a gift, and a **bottom bar will appear**.
+**2. Select Gift**: After choosing a gift, a bottom bar will appear.
:::info[Note]
@@ -40,24 +40,24 @@ Once the gift has expired, it will no longer be displayed for redemption. The ma
|||
|:--------------------------------|:--------------------------------|
-|Propertise|Description|
+|Properties|Description|
|:--------------------------------|:--------------------------------|
|**Validity Duration**|The period during which the gift can be redeemed. The gift will not be available for redemption before or after this period.|
|**Terms and Conditions**|A clickable text that directs users to the page outlining the rules, requirements, guidelines, and limitations they must agree to in order to redeem the gift.|
|**Max Redeem**|The maximum quantity of a gift that a user is allowed to redeem. |
-|**Quantity Input Field**|A field that allow users to enter the desired quantity to redeem .It can be adjusted by either entering an amount in the text field or using the plus and minus buttons.|
+|**Quantity Input Field**|A field that allows users to enter the desired quantity to redeem. It can be adjusted by either entering a value in the text field or using the plus and minus buttons.|
|**Redeem**|A button to add the selected gift to the gift cart.|
-3. Confirm Redemption - After clicking **Redeem**, select **Confirm** to redeem the gift. If the redemption is successful, a success dialog will appear automatically.
+**3. Confirm Redemption**: After tapping **Redeem**, select **Confirm** to redeem the gift. If the redemption is successful, a success dialog will appear automatically.
|||
|:-----------------------------------|:-----------------------------------|
-4. View Redemption - To view redeemed gifts, users can go to **Cart icon> MyRedemption**. If a gift shows as **0/1 issued**, it means that **one redemption has been made**, but it **has not yet been issued**.
+**4. View Redemption**: To view redeemed gifts, users can go to **Cart icon > My Redemption**. If a gift displays **0/1 issued**, it means one redemption has been made but **has not yet been issued**.
:::info[Note]
-Users will need to wait for approval or issuance from the manager before the gift can be used.
+Users must wait for manager approval or issuance before the gift can be used.
:::
@@ -65,7 +65,7 @@ Users will need to wait for approval or issuance from the manager before the gif
|:-----------------------------------|:-----------------------------------|
## Redemption Log
-Redemption log lets users view a history of redeemed rewards, showing who redeemed each reward and when it was redeemed.
+The redemption log allows users to view the history of redeemed rewards, including who redeemed each reward and when it was redeemed.
To view the redemption log, users can go to **More icon> Redemption Log**.
diff --git a/docs/integration/vision/group.md b/docs/integration/vision/group.md
index 7d2e61b..a28282c 100644
--- a/docs/integration/vision/group.md
+++ b/docs/integration/vision/group.md
@@ -12,7 +12,7 @@ This feature is only available to **manager**.
## Introduction
-**Group** is a feature that allows manager to do grouping in advance. These groups can then be applied when creating a Target, Assignment or Upskill without requiring manager to select the members individually.
+**Group** is a feature that allows manager to do grouping in advance. These groups can then be applied when creating a *Target, Assignment or Upskill* without requiring manager to select the members individually.
## Manage Group
@@ -22,20 +22,22 @@ Manager can view all the created groups in **Main Dashboard | Manage Group**. In
### Add Group
-
+|  | ➜ |  |
+ |:---:|---|:---:|
-1. Tap **Add** to create a new group.
+1. Tap **Add icon** on the top right to create a new group.
2. Enter **Group Name**.
-3. Select **Group Members** and their **Roles**.
-4. Tap **Save** to save the group.
+3. Select participants as **Admin**, **Group Leader** and **Group Members**.
+4. Tap **Add** to save the group.
### Edit Group
-
+|  | ➜ |  |
+ |:---:|---|:---:|
-1. Tap on the **group card** that you want to edit. You'll see the previously saved Group Name, Group Members, and their Roles.
-3. Edit by changing either the **Group Name**, **Group Members**, or their **Roles**.
-4. Tap **Save** to save the changes.
+1. Tap on the **group card** that you want to edit. You will see the previously saved *Group Name*, *Admin*, *Group Leader*, and *Group Members*.
+3. Edit by changing either the **Group Name**, **Admin**, **Group Leader** and **Group Members**.
+4. Tap **Save** to save the changes, or **Cancel** to discard the changes.
### Delete Group
@@ -43,10 +45,11 @@ Manager can view all the created groups in **Main Dashboard | Manage Group**. In
1. Swipe **Left** on the group card that you want to delete. Tap **Delete**.
2. Confirm by tapping **Yes**.
+3. You can also delete a group when editing, on the top right **delete icon**.
## Apply Group
-Group can be applied when creating a [**Target**](task/manager_view/task_creation/target#step-3---add-members), [**Assignment (Step 3)**](task/manager_view/task_creation/assignment#step-3---add-members) or an [**Upskill (Step 4)**](upskill/manager_view/upskill-creation#step-4---participants-information).
+Group can be applied when creating a [**Target**](task/manager_view/task_creation/target#step-3---participants-information), [**Assignment (Step 3)**](task/manager_view/task_creation/assignment#step-3---participants-information) or an [**Upskill (Step 4)**](upskill/manager_view/upskill-creation#step-4---participants-information).
@@ -71,6 +74,6 @@ Example:
:::info[Note 2]
-When a group is applied to an **assignment, upskill, or individual target**, the **Team Leader** role of any member in that group will be **automatically removed**.
+When a group is applied to an **assignment, upskill, or individual target**, the **Group Leader** role of any member in that group will be **automatically removed**.
:::
\ No newline at end of file
diff --git a/docs/integration/vision/linking-to-account.md b/docs/integration/vision/linking-to-account.md
index ce67c52..576e088 100644
--- a/docs/integration/vision/linking-to-account.md
+++ b/docs/integration/vision/linking-to-account.md
@@ -6,7 +6,7 @@ sidebar_position: 10
## Introduction
-SQL Vision are linked to SQL Account to get the amount of sales target achieved by employees.
+SQL Vision is linked to SQL Account to get the amount of sales target achieved by employees.
## Requirement
@@ -49,7 +49,7 @@ The SQL Accounting Software must be open and logged in during the connection pro
6. Insert the company ID.
7. Click **Get OTP** .
-8. Insert the OTP Get from the step 7 into the OTP field.
+8. Insert the OTP obtained from the Step 7 into the OTP field.
9. Click **Get Token**.
10. Click **Next** to continue the following steps.
@@ -77,7 +77,7 @@ Suppose you’re managing a Sales Department and want to track Q1 sales targets:
1. For the mission **"Achieve Q1 Sales Target"**, assign the **"Invoice Based Strategy"** strategy.
-2. With this setup, managers can update sales progress daily in SQL Vision by using SQL Vision Sync tool by mapping to the right Strategy ID. Managers can view the updated progress daily in SQL Vision.
+2. With this setup, managers can update sales progress daily in SQL Vision using SQL Vision Sync tool by mapping it to the correct Strategy ID. Managers can then view the updated progress daily in SQL Vision.
:::
@@ -87,7 +87,7 @@ By default, SQL Vision automatically adds two pre-defined strategies to a newly
-If the system encounters an error and fails to create the pre-defined strategies, you can manually add them by navigating to the Company Configuration section. When this issue occurs, the application will display a dialog box prompting you to add the default strategies manually, as shown in the image below:
+If the system encounters an error and fails to create the pre-defined strategies, you can manually add them by navigating to the **Company Configuration** section. When this issue occurs, the application will display a dialog box prompting you to add the default strategies manually, as shown in the image below:
@@ -100,7 +100,7 @@ To add a new strategy, follow these steps:
1. Click the **add icon** to create a new strategy.
2. Enter the strategy name.
3. Click the **Add** button.
-4. Strategy added can be preview. Click **X** to remove it.
+4. Strategy added can be previewed. Click **X** to remove it.
5. Click **Save** to apply changes.
6. Click **Cancel** to discard the changes.
@@ -110,7 +110,7 @@ To edit an existing strategy, follow these steps:
-1. Click on the strategy you want like to edit.
+1. Click on the strategy you would like to edit.
2. Edit the strategy name.
3. Click the **Edit** button.
4. Click **Save** to apply changes.
diff --git a/docs/integration/vision/linking-to-payroll.md b/docs/integration/vision/linking-to-payroll.md
index cb6ce6b..d489330 100644
--- a/docs/integration/vision/linking-to-payroll.md
+++ b/docs/integration/vision/linking-to-payroll.md
@@ -6,7 +6,7 @@ sidebar_position: 11
## Introduction
-SQL Vision are linked with SQL Payroll to process all cash rewards earned by employees.
+SQL Vision is linked with SQL Payroll to process all cash rewards earned by employees.
## Requirement
@@ -39,6 +39,6 @@ All rewards will be classified as **Commission** by default. You can change the
:::warning[Warning]
- You are **allowed** to process the reward for specific employees if the expected payout month is **within or before** the payroll process month.
-- If you **choose not to process** particular reward, update the expected payout date for the employee in SQL Vision through **[Wallet | Manage Payout](wallet#manage-payoutentitlement-page)**.
+- If you **choose not to process** particular reward, update the expected payout date for the employee in SQL Vision through **[Wallet | Manage Payout](wallet#manage-payoutentitlement)**.
:::
diff --git a/docs/integration/vision/login.md b/docs/integration/vision/login.md
index c9e582d..47e65ae 100644
--- a/docs/integration/vision/login.md
+++ b/docs/integration/vision/login.md
@@ -17,7 +17,8 @@ sidebar_position: 1
-3. **Resend OTP** allows user to request again an One-Time Password(OTP)
+3. **Resend OTP** allows user to request again an One-Time Password(OTP)
+
4. Verification
diff --git a/docs/integration/vision/main-dashboard.md b/docs/integration/vision/main-dashboard.md
index a4fcd97..94922fc 100644
--- a/docs/integration/vision/main-dashboard.md
+++ b/docs/integration/vision/main-dashboard.md
@@ -8,16 +8,16 @@ sidebar_position: 2
### Task
-- Display all available quest and tasks assigned to the user.
+- Displays all available quests and tasks assigned to the user.
### Upskill
-- Display all available courses and those the user is currently enrolled in.
+- Displays all available courses and courses in which the user is currently enrolled.
### Gantt Chart
-- Display a visual timeline of tasks and deadlines, allowing the user to track progress across project.
+- Displays a visual timeline of tasks and deadlines, allowing the user to track progress across project.
### Wallet
-- Display cash and coins earned, transaction history and redeem gift.
+- Displays earned cash and coins, transaction history, and available rewards for redemption.
### Manage Task
- Allows user to create, edit and update tasks, track task progress and review completed tasks.
@@ -31,40 +31,50 @@ sidebar_position: 2
## Status Card
-- Displays the count of tasks where:
+- Displays the total number of tasks categorized by their current status:
- Green: Completed tasks
- Blue: Undue tasks
- Red: Overdue tasks
-- Clicking the status card navigates the user to the task list, and filter will be applied based on the status clicked.
+- **Navigation**: Selecting a status card redirects the user to the task list, with the tasks automatically filtered according to the selected status.
## Overdue Tasks
-- Displays up to 3 tasks that have passed thier deadlines.
+- Displays up to three tasks that have exceeded their deadlines, providing the user with a clear overview of the most urgent overdue items.
## Undue Tasks
-- Displays up to 3 tasks that are currently in progress and have not yet reached their deadlines.
+- Displays up to three tasks that are currently in progress and have not yet reached their deadlines, providing the user with a quick view of ongoing responsibilities.
## Earned Card
-- Allows the user to view the cash and coin rewards they are entitled to for the current month or the previous month.
+- Displays the cash and coin rewards earned by the user for the current or previous month, allowing easy tracking of monthly earnings.
## Account Setting
-### Personal Information
-- Displays the user's profile information in the company payroll system, organized into sections for general details, employment grouping and family information.
+### Profile
+- Displays the user's basic information.
+- **Statistics**: Shows the total cash and coin rewards earned by the user, along with the number of quests joined and courses registered.
+- **Completion**: Provides progress indicators for targets, assignments, and courses, displaying both numeric counts and percentage completion.
+- **Achievements**: Displays badges earned by the user for completing various activities, with an option to view all achievements.
+
+
+
+- The top-right button allows managers to search employees and view their details, but cash and points earned are not shown.
+
+|  | ➜ |  |
+ |:---:|---|:---:|
-
:::info NOTE
Details are **view-only** and **cannot be edited** or **modified** from the mobile application.
:::
### Company Configuration (Manager)
-- Allows managers to modify settings such as the closing period, estimated payout day and strategies.
-- For more details about strategy, see [**Linking to SQL Account | Strategy**](./linking-to-account.md#strategy).
+- Enables managers to view and modify company settings, including the closing period (days), estimated payout day, and payment strategies.
+- Managers can switch between Default and Customize strategies and use the search bar to quickly locate specific strategies.
+- For more details about strategy, refer to [**Linking to SQL Account | Strategy**](./linking-to-account.md#strategy).
:::warning NOTE
@@ -72,16 +82,16 @@ Details are **view-only** and **cannot be edited** or **modified** from the mobi
:::
### Switch Company
-- Displays a list of companies the user is enrolled in, allowing them to switch between different company accounts.
+- Shows all companies the user is associated with, allowing seamless switching between different company accounts.
### Help
-- Directs the user to the company website for support resources and guides.
+- Directs users to SQL Vision’s documentation page for support resources and user guides.
### Logout
-- Logs the user out of the application, ending the current session and returning them to the login screen.
+- Ends the current session, logging the user out of the application and returning them to the login screen.
## Log File Review
-- Enables the user to view and manage pending and approved log files for assignments that have not been finalised yet
\ No newline at end of file
+- Allows the user to view and manage pending and approved log files for assignments that have not been finalised yet.
\ No newline at end of file
diff --git a/docs/integration/vision/task/introduction.md b/docs/integration/vision/task/introduction.md
index bd503a0..07c30c3 100644
--- a/docs/integration/vision/task/introduction.md
+++ b/docs/integration/vision/task/introduction.md
@@ -7,10 +7,14 @@ sidebar_position: 1
There are 3 types of missions in task module: **Assignment**, **Target** and **Quest**.
- **Assignment:**
- An Assignment mission focuses on qualitative outcomes that require creativity and strategic thinking. These missions emphasize the quality of work and the process rather than measurable results. E.g. Idea brainstorm, Clothes design..
+ An Assignment mission focuses on qualitative outcomes that require creativity and strategic thinking. These missions emphasize the quality of work and the process rather than measurable results.
+
+ *Example: Marketing Strategy Planning, Company Logo design.*
- **Target:**
- A Target mission centers on quantitative outcomes with specific, measurable goals. The focus is on achieving clear, countable results. E.g. Sales Target, Total new users.
+ A Target mission centers on quantitative outcomes with specific, measurable goals. The focus is on achieving clear, countable results.
+
+ *Example: Sales Target, Input Data.*
- **Quest:**
- A Quest is used when you’re unsure who to assign a task to or want to invite all employees to participate.
+ A Quest is ideal when the participant is not predetermined or when you want to invite all employees to participate.
diff --git a/docs/integration/vision/task/manager_view/assignment.md b/docs/integration/vision/task/manager_view/assignment.md
index 13ba7a6..5e882ce 100644
--- a/docs/integration/vision/task/manager_view/assignment.md
+++ b/docs/integration/vision/task/manager_view/assignment.md
@@ -4,80 +4,84 @@ description: A brief guide on assignment
sidebar_position: 2
---
-Managers can view the assignment detail that are created such as title, description, start date, end date, consultant, rewards, and bonus criteria.
+Managers can view the assignment details that are created such as *title, description, start date, end date, admin, consultant, rewards, and bonus criteria.*
-| Undue/Overdue | Completed |
-|--------------------------------------------------------------|----------------------------------------------------------|
-|  | |
+| Undue/Overdue | Completed |
+| ---------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- |
+|  |  |
-## Undue & Overdue
+## Undue & Overdue
### Edit Assignment Detail
+
1. Press **Edit** in assignment detail
- - For more information, please refer [**Edit Task**](task_creation/task-edit)
+ - For more information, please refer [**Edit Task**](task_creation/task-edit)
### Employee Progress
+
1. Navigate to: **Progress** > **Employee Progress Card** (highlighted in red)
:::info Info
-**Progress** tab bar: Display the employee that are still havent reached **100%**.
+**Progress** tab: Shows employees who have not yet reached **100%** of the milestone.
-**Completed** tab bar: Display the employee that reached **100%**.
+**Completed** tab: Shows employees who have achieved **100%** of the milestone.
:::
-2. Display employee's assignment detail:
- - Total cash and coin(s) earned (**Highlighted in red**)
- - Log file submitted
- - Rewards earned
-
+2. Display employee's assignment details:
+ - Total cash and coin(s) earned (**Highlighted in red**)
+ - Log file submitted
+ - Rewards earned
-
### Log File Submission
+
1. Navigate to: **Log File** > **Log File Card** (highlighted in red)
- - Manager can view all unapproved log files submitted by the employees.
+ - Manager can view all unapproved log files submitted by the employees.
-2. Manager can view the log file details as shown.
- - Actions:
- - Override
- - Approve
+2. Manager can view the log file details as shown below.
+ - **Actions:**
+ - Override
+ - Approve
### Log File Override
+
Manager can override the log file's progress percentage by clicking **Save** button.
:::info Info
- Manager will not be able to override progress percentage that is **lower** than the previous progress percentage.
+Manager will not be able to override progress percentage that is **lower** than the previous progress percentage.
:::
### Employee Bonus Review
+
- After approving the log file, manager can view the bonus request submitted by the employee.
:::note Note
-- Bonus Review is only available when the log file submission is **100%**.
+- **Bonus Review** is only available when the log file submission is **100%**.
- The colored bonus card represents the bonus requested by the employee. (**highlighted in red**)
:::
-### Edit Employee Bonus
+### Edit Employee Bonus
+
1. Press **Edit** in bonus review page
- - Manager can edit the employee's bonus request.
- - Manager can choose the bonus criteria, and edit the amount.
+ - Manager can edit the employee's bonus request.
+ - Manager can choose the bonus criteria, and edit the amount.
:::note Note
@@ -88,16 +92,27 @@ Manager can override the log file's progress percentage by clicking **Save** but
+### Transfer Ownership
+
+- Only the creator will see the transfer ownership button in the app bar.
+- If ownership is transferred to someone who is not an admin, that person will automatically be promoted to admin.
+- Once ownership is transferred, the button will no longer be visible to you, as you are no longer the creator.
+- In the third diagram below, ownership has been transferred to Tan Jun Wei, making him the new creator. Although he was not initially an admin, he was automatically promoted to admin upon receiving ownership.
+
+
+
### Change Log
+
1. Press **History Icon** (highlighted in red)
- - details of who made edits and what changes were made.
+ - Displays details of who made edits and what changes were made.
### Finalise Assignment
+
1. Press **Finalise** in assignment detail page
- - To finalise assignment, all log file must be **approved**.
- - After finalising, consultant reward will be entitled.
+ - To finalise an assignment, all log files must be **approved**.
+ - After finalising, consultant rewards will be entitled.
:::danger Warning
@@ -105,39 +120,41 @@ Finalising assignment is an **irreversible** action.
:::
-
+
-## Completed
+## Completed
### Reward Info
+
1. Press **Info Icon** (highlighted in red)
-2. User can view the milestone and bonus rewards
+2. User can view the milestone and bonus rewards
:::info Info
- The code will matches with the code in the summary table.
+The code will match with the code in the summary table.
:::
### Employee Progress
+
1. Press **Employee Name** (highlighted in red)
-
### Employee Log File
-1. Navigate to: **Employee Name** (in summary table) > **View Log File**
+
+1. Navigate to: **Employee Name** (in summary table) > **View Log File**
### Tooltip Reward
-1. Click **Total Cash Amount** / **Total Coin Amount**
- - can view the earned amounts for the corresponding employee in the tooltip.
-
+1. Press **Total Cash Amount** / **Total Coin Amount**
+ - Displays the earned amounts for the corresponding employee in the tooltip.
+
diff --git a/docs/integration/vision/task/manager_view/quest.md b/docs/integration/vision/task/manager_view/quest.md
index 2369316..527f747 100644
--- a/docs/integration/vision/task/manager_view/quest.md
+++ b/docs/integration/vision/task/manager_view/quest.md
@@ -4,9 +4,9 @@ description: A brief guide on quest
sidebar_position: 4
---
-Quest detail will be same as the assignment or target details based on whether it's a target or assignment quest.
+Quest details are the same as the Assignment or Target details, depending on whether the Quest is an *Assignment-type* or *Target-type* mission.
-For more information, can refer as below:
+For more information, refer below:
- [**Target**](target.md)
- [**Assignment**](assignment.md)
@@ -19,16 +19,16 @@ For more information, can refer as below:
-2. Filter menu on right top allows the manager to filter the employee by branch, department, and HR group.
+2. Filter menu on right top allows the manager to filter employees by Branch, Department, and HR group.
| View | Filter |
|---------------------------------------------------------------------------|--------------------------------------------------------|
|  | |
-### Delete Request Employee
+### Delete Employee Request
1. Press **Delete**
- - allows manager to delete the request of employee for joining the quest
+ - Allows the manager to delete employee requests to join the Quest
-### Approve Request Employee
+### Approve Employee Request
1. Press **Approve**
- - allows manager to approve the request of employee for joining the quest
\ No newline at end of file
+ - Allows the manager to approve employee requests to join the Quest.
\ No newline at end of file
diff --git a/docs/integration/vision/task/manager_view/target.md b/docs/integration/vision/task/manager_view/target.md
index 0b3f38a..531cf3c 100644
--- a/docs/integration/vision/task/manager_view/target.md
+++ b/docs/integration/vision/task/manager_view/target.md
@@ -4,23 +4,33 @@ description: A brief guide on target
sidebar_position: 3
---
-Managers can view the target detail that are created such as title, task creator, description, start date, end date, strategy, rewards, and employee's progress.
+Managers can view the target details that are created such as *title, task creator, description, start date, end date, strategy, admin, rewards, and employee's progress*.
-| Individual | Team |
-|-------------------------------------------------------------|-------------------------------------------------|
-| | |
+| Individual | Team |
+| ---------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------- |
+|  |  |
+
+### Employee Progress
-### Employee Progress
1. Press **Employee Card** (highlighted in red)
-| Individual | Team |
-|--------------------------------------------------------|-------------------------------------------|
-|  | |
+| Individual | Team |
+| ---------------------------------------------------------------------------------- | ---------------------------------------------------------------------- |
+|  |  |
### Edit
+
1. Press **Edit**
- - For more information, please refer [**Edit Task**](task_creation/task-edit)
+ - For more information, please refer [**Edit Task**](task_creation/task-edit)
+
+
+
+### Transfer Ownership
+
+Please refer [**Transfer Ownership**](assignment/#transfer-ownership)
+
+### Change Log
-
\ No newline at end of file
+Please refer [**Change Log**](assignment/#change-log)
diff --git a/docs/integration/vision/task/manager_view/task_creation/assignment.md b/docs/integration/vision/task/manager_view/task_creation/assignment.md
index 5a2b1fb..fa2c28c 100644
--- a/docs/integration/vision/task/manager_view/task_creation/assignment.md
+++ b/docs/integration/vision/task/manager_view/task_creation/assignment.md
@@ -4,7 +4,7 @@ sidebar_position: 2
# Create Assignment
-Assignment is a qualitative mission (non-countable). E.g. Idea brainstorm, Clothes design.
+Assignment is a qualitative mission (uncountable). *E.g., Marketing Strategy Planning, Company Logo design*
:::info[Note]
@@ -20,27 +20,27 @@ This feature is only available to **manager**.
| Properties | Description | Note |
|:-------------------------|:-----------------------------------------------------------------------------------|:--------:|
| **Title** | The title of the mission. | Required |
-| **Description** | A detailed description of the mission. | Required |
+| **Description** | A detailed description of the mission. | - |
| **[Project/Job/Task](#projectjobtask)** | The category for the mission, indicating whether it relates to a project, job, or specific task. | - |
-| **Start Date** | The date when the mission begins. The start date must be today or a future date. | Required |
+| **Start Date** | The date when the mission begins. | Required |
| **End Date** | The date when the mission ends. The end date must be later than the start date. | Required |
| **Clear** | Clears all content on the current page. | - |
| **Next** | Navigates to the next page. | - |
### Project/Job/Task
-Select a **Project**, **Job**, and **Task** from the dropdown. If you leave any of these fields set to **(None)**, the Manager's Project, Job, and Task will be used in the SQL Payroll.
+Select a **Project**, **Job**, and **Task** from the dropdown menus. If any field is left as **(None)**, the **Manager's** corresponding Project, Job, and Task will be applied in SQL Payroll.
-## Step 2 - Milestone and Rewards
+## Step 2 - Rewards Information
| Properties | Description | Note |
|:----------------------------------------------------|:----------------------------------------------------------------------|:------------:|
| **[Milestone and Rewards](#milestone-and-rewards)** | Section for entering details about milestones and associated rewards. | At least one |
-| **[Consultant Rewards](#consultant-rewards)**| Section for selecting consultants and specifying their respective rewards.| Required |
+| **[Consultant Rewards](#consultant-rewards)**| Section for selecting consultants and specifying their respective rewards.| - |
| **[Payment By](#payment-by)** | Section for selecting the payment method and specifying the payout month. | Required |
| **[Bonus](#bonus)** | Section for entering additional bonus rewards. | - |
| **Clear** | Clears all content on the current page. | - |
@@ -54,8 +54,8 @@ Select a **Project**, **Job**, and **Task** from the dropdown. If you leave any
| Properties | Description |
|---------------------|-----------------------------------------------------------------------|
-| **Milestone (%)** | Text field to input the percentage of the milestone (e.g., 20%). |
-| **Description** | Text field to input the description of the milestone (e.g., the requirements to achieve the particular milestone). |
+| **Milestone (%)** | Text field to input the percentage of the milestone *(e.g., 20%)*. |
+| **Description** | Text field to input the description of the milestone *(e.g., the requirements to achieve the particular milestone)*. |
| **Rewards** | Text field to enter the rewards available to the achievers of the particular milestone. There are 2 types of rewards:
1. **Cash (RM):** Commission or allowance provided through the SQL Account on the payout date.
2. **Coins:** Digital coins that can be used to redeem gifts in SQL Vision via [**Gift**](../../../gift/introduction.md). |
| **Add** | Adds a new milestone along with its respective rewards. |
| **Delete** | Deletes a specific milestone and its associated rewards. |
@@ -64,9 +64,9 @@ Select a **Project**, **Job**, and **Task** from the dropdown. If you leave any
-**Consultants** are employees responsible for providing guidance on a particular mission. They do not complete the mission themselves.
+*Consultants* are employees who provide guidance on a mission but do not complete the mission themselves.
-To add a consultant click on  to navigates to the Select Consultant page. The selected consultants will be listed down in the Consultant Rewards section under the associated rewards.
+To add a consultant, click on  to navigate to the **Select Consultant** page. On the **Select Consultant** page, you can filter consultants by *Branch*, *Department*, or *HR Group*, and sort them by these criteria. After selecting the desired consultants, click *Apply*. The chosen consultants will appear in the **Consultant Rewards** section under the corresponding rewards.
@@ -74,7 +74,7 @@ To add a consultant click on . |
+| **Description** | Text field to enter a description for the bonus. *(e.g., extra points that you hope the employee can achieve, though it is not mandatory)* |
| **Rewards** | Text field to enter the rewards available to the achievers of the particular bonus. |
| **Add** | Adds a new bonus along with its respective rewards. |
-| **Delete** | Adds a new bonus along with its respective rewards. |
+| **Delete** | Deletes a new bonus along with its respective rewards. |
+
+## Step 3 - Participants Information
+### Participant Role
-## Step 3 - Add Members
+#### Admin
+ - **Admin** is authorized to **manage and edit** the task.
+ - Admin does not perform the task and therefore **is not entitled to any rewards**.
+ - By default, the creator will be added as Admin and cannot be removed by anyone. *(Employee with yellow crown, as shown in image below, is the creator.)*
-There are 4 combination of members that can be created in Assignment:
+#### Participant
+ - **Participant** is the employee responsible for performing the mission.
+ - They are eligible to receive the reward.
-1. **Normal member:**
- An employee who performs the mission without a specific management or advisory role.
+#### Consultant
+ - **Consultant** provide **guidance or advice** on the mission but do not perform the task.
+ - They are assigned in **[Step 2 - Rewards Information, Consultant Rewards section](#consultant-rewards)**.
-2. **Admin:**
- An employee authorized to manage the task but does not complete the mission themselves. Admin shall not be entitled to any reward.
+### Features
-3. **Consultant:**
- An employee who provides guidance on the mission without directly managing or completing it (e.g., an advisor).
+
-4. **Consultant and Admin:**
- An employee who both guides the mission and manages the task but does not complete the mission themselves. This employee will be entitled to consultant's reward.
+| Properties | Description |
+|:------------------------|:-------------------------------------------------------------------------|
+| **Apply Group** | Allow you to apply group. See more in [**group**](../../../group#apply-group). |
+| **Clear** | Clears all content on the current page. |
+| **Make Quest** | Converts your mission into a Quest. See more in [**quest**](quest). |
+| **Add Person Icon** | Add employees as the participant type. |
+| **Delete Icon** | Delete the particular employee. |
+| **Back** | Navigates to the previous page. |
+| **Create** | Creates the mission. |
-The *Normal Member* and *Admin* can be created in **[Add Members](#step-3---add-members)** in Step 3, on the other hand the *Consultant* and *Consultant and Admin* combination can be created in **[Consultant Reward](#consultant-rewards)** in Step 2.
+### Steps to add Participants
-
+
+
+1. Press on the **Add Person Icon** in the section for the participant role you want to add.
+2. Select participants.
+3. Press **Apply** to assign the selected employees to the participant role.
+4. Press **Cancel** to discard current changes.
+
+#### Side functions
| Properties | Description |
|:------------------------|:-------------------------------------------------------------------------|
| **Search** | Allows you to search for employees by their names. |
-| **[Filter](#filter)** | Allow you to filter and sort the employee list. |
-| **Group** | Allow you to apply group. See more in [**group**](../../../group#apply-group). |
+| **[Filter](assignment#filter)** | Allow you to filter and sort the employee list. |
| **Select All** | Allow you to select all employees at once. |
-| **Make Quest** | Converts your mission into a Quest. See more in [**quest**](quest). |
-| **Back** | Navigates to the previous page. |
-| **Create** | Creates the mission. |
#### Filter
-
-
-The employee list can be filtered and sort by:
+A filter is available in the Employee List when selecting participants. The list can be filtered and sorted by **Branch**, **Department**, and **HR Group**, as shown in the image below.
-- Branch
-- Department
-- HR Group
+
\ No newline at end of file
diff --git a/docs/integration/vision/task/manager_view/task_creation/duplication.md b/docs/integration/vision/task/manager_view/task_creation/duplication.md
index 72ec42e..b57d6e3 100644
--- a/docs/integration/vision/task/manager_view/task_creation/duplication.md
+++ b/docs/integration/vision/task/manager_view/task_creation/duplication.md
@@ -4,7 +4,7 @@ sidebar_position: 5
# Duplication
-Duplication allows managers to recreate a previously created task, including deleted missions, without needing to re-enter the mission details manually.
+Duplication allows managers to recreate a previously created task without needing to re-enter the mission details manually.
:::info[Note]
@@ -14,7 +14,7 @@ This feature is only available to **manager**.
## Mission Card
-The mission card displays key details of the mission, including the Title, Created Date, Duration, and Members. Pressing the card allows you to create a new mission with the same details duplicated.
+The mission card displays key details of the mission, including the Title, Created Date, Duration, and Members. Tapping the card allows you to create a new mission with the same details duplicated.
@@ -24,10 +24,7 @@ The mission card displays key details of the mission, including the Title, Creat
## Filter
-The filter button allow you to filter your recent mission. The duplicated mission can be filtered by Status and Type:
-
-**Status:**
-- Show only deleted
+The Filter button allows you to filter your recent missions. Duplicated missions can be filtered by **Type**:
**Type:**
- Assignment
@@ -35,10 +32,4 @@ The filter button allow you to filter your recent mission. The duplicated missio
- Quest Assignment
- Quest Target
-
-
-### Show only deleted mission
-
-By default, the duplication page in SQL Vision displays only missions that have not been deleted. If you need to search for deleted missions, you can do so by using the filter function. The filter function allows you to specifically display missions that have been marked as deleted.
-
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/docs/integration/vision/task/manager_view/task_creation/quest.md b/docs/integration/vision/task/manager_view/task_creation/quest.md
index 70e26a1..dc3d120 100644
--- a/docs/integration/vision/task/manager_view/task_creation/quest.md
+++ b/docs/integration/vision/task/manager_view/task_creation/quest.md
@@ -4,7 +4,7 @@ sidebar_position: 4
# Create Quest
-Quest is a mission that is visible and open for employees to join freely, based on their Branch, Department, and HR Group. To create quest, go to **Create New | Target/Assignment | Step 3 | Make Quest**.
+A Quest is a mission that is visible to employees and open for them to join freely, based on their Branch, Department, and HR Group.To create quest, go to **Create New | Target/Assignment | Step 3 | Make Quest**.
:::info[Note]
@@ -12,13 +12,12 @@ This feature is only available to **manager**.
:::
-
+
-| Properties | Description |
-|:--------------------------|:------------------------------------------------------------------------------|
-| **Maximum Pax** | The maximum number of people allowed to join the quest. |
+| Properties | Description |
+|:--------------------------|:----------------------------------------------------------------------------|
| **Join Permission** | Sets whether the quest requires manager approval to join. |
+| **Maximum Pax** | The maximum number of people allowed to join the quest. |
| **Quest Visible By** | Specifies which Branch, Department, or HR Group can view and join the quest. |
-| **Back to Normal Task** | Converts your mission into normal mission. See more in [**assignment**](assignment) and [**target**](target) |
| **Back** | Navigates to the previous page. |
| **Create** | Creates the quest. |
diff --git a/docs/integration/vision/task/manager_view/task_creation/target.md b/docs/integration/vision/task/manager_view/task_creation/target.md
index 6b343cf..1908e0d 100644
--- a/docs/integration/vision/task/manager_view/task_creation/target.md
+++ b/docs/integration/vision/task/manager_view/task_creation/target.md
@@ -4,7 +4,7 @@ sidebar_position: 3
# Create Target
-Target is a quantitative mission (countable data). E.g. Sales Target, Total new users.
+Target is a quantitative mission (countable data). E.g. Sales Target, Input Data.
:::info[Note]
@@ -12,29 +12,29 @@ This feature is only available to **manager**.
:::
-## Step 1 - Target Details
+## Step 1 - Target Information
| Properties | Description | Note |
|:-----------------------------|:-----------------------------------------------------------------------------------|:--------:|
| **Title** | The title of the mission. | Required |
-| **Description** | A detailed description of the mission. | Required |
-| **Start Date** | The date when the mission begins. The start date must be today or a future date. | Required |
+| **Description** | A detailed description of the mission. | - |
+| **Start Date** | The date when the mission begins. | Required |
| **End Date** | The date when the mission ends. The end date must be later than the start date. | Required |
| **Clear** | Clears all content on the current page. | - |
| **Next** | Navigates to the next page. | - |
-## Step 2 - Target and Rewards
+## Step 2 - Rewards Information
-
+
| Properties | Description | Note |
|:------------------------------------|:-----------------------------------------------------------------------------------------|:------------:|
| **[Grouping Type](#grouping-type)** | Section to select the target grouping type, either *Individual* or *Team*. | Required |
-| **[Strategy](#strategy)** | Section to select the target strategy, with options predefined in Company Configuration. | Required |
-| **[Condition](#condition)** | Section to select the target condition (e.g., *Between*, *More than*). | Required |
+| **[Strategy](#strategy)** | Section to select the target strategy, with options predefined in **Company Configuration**. | Required |
+| **[Condition](#condition)** | Section to select the target condition. *(e.g., Between, More than)* | Required |
| **[Target and Rewards](#target-and-rewards)**| Section to enter details about the targets and their associated rewards. | At least one |
| **[Payment By](#payment-by)** | Section to select the payment method and specify the payout month. | Required |
| **Clear** | Clears all content on the current page. | - |
@@ -48,13 +48,13 @@ This feature is only available to **manager**.
There are two types of **Grouping Types**:
1. **Individual:**
- - Selecting Individual means that the targets and rewards apply to each normal member added or who joins this target mission.
- - **Example:** if the target is 10,000 and the reward is 1%, all employees will have a target of 10,000 and a reward of 1%.
+ - Selecting Individual means that the targets and rewards **apply to each participant** added or who joins this target mission.
+ - **Example:** If the target is RM 10,000 and the reward is 1%, each participant will have a target of RM 10,000 and a reward of 1%.
2. **Team:**
- - Selecting Team means that the targets and rewards apply only to the team leader added to this target mission.
- - **Example:** if the target is RM 50,000 and the reward is 5%, the leader receives the reward only when the total target achieved by members exceeds RM 50,000.
+ - Selecting Team means that the targets and rewards apply **only to the Team Leader** assigned to this target mission.
+ - **Example:** If the target is RM 50,000 and the reward is 5%, the team leader receives the reward only when the combined target achieved by all team members exceeds RM 50,000.
:::info[Note]
@@ -62,7 +62,7 @@ Team option is not available for quests.
:::
-:::tip Tip to create a Team Target Mission
+:::tip Tips to create a Team Target Mission
To set up a team target, create two identical missions: one with the **Individual** setting and the other with the **Team** setting.
@@ -76,7 +76,7 @@ To set up a team target, create two identical missions: one with the **Individua
-**Strategy** refers to the formula that helps managers and the application determine which specific target a particular mission belongs to. This formula enables the application to accurately retrieve the target amount from the SQL Account. For more details, see [**Linking to SQL Account | Strategy**](../../../linking-to-account.md#strategy).
+**Strategy** refers to the formula that helps managers and the application determine which specific target a mission belongs to. This formula allows the application to accurately retrieve the target amount from the SQL Account. For more details, see [**Linking to SQL Account | Strategy**](../../../linking-to-account.md#strategy).
:::tip Example Scenario
@@ -84,7 +84,7 @@ Suppose you’re managing a Sales Department and want to track Q1 sales targets:
1. For the mission **"Achieve Q1 Sales Target"**, assign the **"Invoice Based Strategy"** strategy.
-2. With this setup, managers can update sales progress daily in SQL Vision by using SQL Vision Sync tool by mapping to the right Strategy ID. Managers can view the updated progress daily in SQL Vision.
+2. With this setup, managers can update sales progress daily in SQL Vision by using SQL Vision Sync tool, mapping it to the correct Strategy ID. Managers can then view the updated progress daily in SQL Vision.
:::
@@ -129,8 +129,8 @@ The "Less Than" condition is designed to grant rewards when an employee achieves
-1. If an employee have **2 return stock**, they will receive **RM3,000 & 10,000 coins** because their performance is **below 3**, which excludes the second target reward.
-2. If an employee have **4 return stock**, they will receive **RM1,000 & 5,000 coins** bacause their performance is **below 10 but above or equal 3**, therfore not qualify with the reward in Target 1.
+1. If an employee has **2 return stock**, they will receive **RM3,000 & 10,000 coins** because their performance is **below 3**, which excludes the second target reward.
+2. If an employee has **4 return stock**, they will receive **RM1,000 & 5,000 coins** bacause their performance is **below 10 but above or equal 3**, therfore not qualified for the reward in Target 1.
#### D. More Than and Equal
@@ -153,8 +153,8 @@ The "Less Than and Equal" condition is applied to reward employees who achieve r
-1. If an employee has **3** return stock, they will receive **RM3,000 & 10,000 coins** because their performance is **3 or less**, which excludes rewards for any higher targets.
-2. If an employee has **4** return stock, they will receive **RM1,000 & 5,000 coins** because their performance is **10 or less but above 3**, making them ineligible for Target 1's reward.
+1. If an employee has **3 return stock**, they will receive **RM3,000 & 10,000 coins** because their performance is **3 or less**, which excludes rewards for any higher targets.
+2. If an employee has **4 return stock**, they will receive **RM1,000 & 5,000 coins** because their performance is **10 or less but above 3**, making them ineligible for Target 1's reward.
### Target and Rewards
@@ -164,7 +164,7 @@ The "Less Than and Equal" condition is applied to reward employees who achieve r
| Properties | Description |
|-------------|----------------------------------------------------------------------------------------------------------|
| **Target** | Text field to input the target amount. (Note: Only the **Between** condition will have two text fields.) |
-| **Rewards** | Text field to enter the rewards available to the achievers of the particular target. There are 3 types of rewards:
1. **Percentage (%):** A percentage of the target amount awarded to the members (e.g., 2%).
2. **Cash (RM):** Commission or allowance provided through the SQL Account on the payout date.
3. **Coins:** Digital coins that can be used to redeem gifts in SQL Vision via [**Gift**](../../../gift/introduction.md). |
+| **Rewards** | Text field to enter the rewards available to the achievers of the particular target. There are 3 types of rewards:
1. **Percentage (%):** A percentage of the target amount awarded to the members *(e.g., 2%)*.
2. **Cash (RM):** Commission or allowance provided through the SQL Account on the payout date.
3. **Coins:** Digital coins that can be used to redeem gifts in SQL Vision via [**Gift**](../../../gift/introduction.md). |
| **Add** | Adds a new target along with its respective rewards. |
| **Delete** | Deletes a specific target and its associated rewards. |
@@ -181,40 +181,68 @@ The payment method applies only to **Cash**. All coins will be paid immediately
There are two types of payment methods:
1. **Payment Terms:**
- - The payout month, which will be X months after the entitled month.
- - E.g., if set to 3 months, the reward will be paid after 3 months from when the employee achieved and became entitled to the reward.
+ - The payout month, which occurs X months after the entitled month.
+
+ *E.g., If set to 3 months, the reward will be paid 3 months after the employee becomes entitled to it.*
2. **Settlement Month:**
- - The entitled cash will be collected until a specific month for payment, either inclusive or exclusive of that month.
- - **Inclusive Setting:** If inclusive with January and August, all rewards entitled from February to August will be paid in August, while rewards entitled from September to January will be paid in January.
- - **Exclusive Setting:** If exclusive with January and August, all rewards entitled from January to July will be paid in August, and rewards entitled from August to December will be paid in January.
+ - Entitled cash will be accumulated until a specific month for payout, which can be either inclusive or exclusive of that month.
+ - **Inclusive Setting:** *If January and August are set as inclusive months, rewards entitled from February to August will be paid in August, while rewards entitled from September to January will be paid in January.*
+ - **Exclusive Setting:** *If January and August are set as exclusive months, rewards entitled from January to July will be paid in August, and rewards entitled from August to December will be paid in January.*
-## Step 3 - Add Members
+## Step 3 - Participants Information
-There are 4 combination of members that can be created in Target:
+### Participant Role
+The participant role in **Team and Individual Target** are different and works differently:
-1. **Normal member:**
- An employee who performs the mission without a specific management or leadership role.
+#### Admin
+ - **Admin** is authorized to **manage and edit** the task.
+ - Admin does not perform the task and therefore **is not entitled to any rewards**.
+ - By default, the creator will be added as Admin and cannot be removed by anyone. *(Employee with yellow crown, as shown in image below, is the creator.)*
-2. **Admin:**
- An employee authorized to manage the task but does not complete the mission themselves. Admin shall not be entitled to any reward.
+#### Team Leader *(Team only)*
+ - The **Team Leader** is responsible for **leading the mission**.
+ - A **leader is required** in a team target.
+ - The leader does not contribute to the target directly, but is **entitled to rewards based on the combined performance of the Team Members**, as defined in **[Step 2 - Rewards Information](#step-2---rewards-information)**. See **[Grouping Type](#grouping-type)** for more details.
-3. **Team Leader:**
- An employee who leads the mission. *This role is visible only when Grouping Type is set to **Team**.*
+#### Team Members *(Team only)*
+ - **Team Members** are employees who **contribute their target achievements** toward the team goal.
+ - The **combined performance of all team memebers** determines whether the Team Leader qualifies for a reward.
+ - Rewards are **given only to Team Leader** if the total achievements meet the target set in **[Step 2 - Rewards Information](#step-2---rewards-information)**. See **[Grouping Type](#grouping-type)** for more details.
-4. **Team Leader and Admin:**
- An employee who both leads the mission and manages the task but does not complete the mission themselves. This employee will be entitled to team leader's reward. *This role is visible only when Grouping Type is set to **Team**.*
+#### Participant
+ - **Participant** is the employee responsible for performing the mission.
+ - They are eligible to receive the reward.
-All 4 combinations can be created in **[Add Members](#step-3---add-members)** in Step 3.
+### Features
-
+| Team Target | Individual Target |
+|:-----------:|:-----------------:|
+|  |  |
| Properties | Description |
|:------------------------|:-------------------------------------------------------------------------|
-| **Search** | Allows you to search for employees by their names. |
-| **[Filter](assignment#filter)** | Allow you to filter and sort the employee list. |
-| **Group** | Allow you to apply group. See more in [**group**](../../../group#apply-group). |
-| **Select All** | Allow you to select all employees at once. |
+| **Apply Group** | Allow you to apply group. See more in [**group**](../../../group#apply-group). |
+| **Clear** | Clears all content on the current page. |
| **Make Quest** | Converts your mission into a Quest. See more in [**quest**](quest). |
+| **Add Person Icon** | Add employees as the participant type. |
+| **Delete Icon** | Delete the particular employee. |
| **Back** | Navigates to the previous page. |
-| **Create** | Creates the mission. |
\ No newline at end of file
+| **Create** | Creates the mission. |
+
+### Steps to add Participants
+
+
+
+1. Press on the **Add Person Icon** in the section for the participant role you want to add.
+2. Select participants.
+3. Press **Apply** to assign the selected employees to the participant role.
+4. Press **Cancel** to discard current changes.
+
+#### Side functions
+
+| Properties | Description |
+|:------------------------|:-------------------------------------------------------------------------|
+| **Search** | Allows you to search for employees by their names. |
+| **[Filter](assignment#filter)** | Allow you to filter and sort the employee list. |
+| **Select All** | Allow you to select all employees at once. |
\ No newline at end of file
diff --git a/docs/integration/vision/task/manager_view/task_creation/task-creation.md b/docs/integration/vision/task/manager_view/task_creation/task-creation.md
index f67e986..e0b7627 100644
--- a/docs/integration/vision/task/manager_view/task_creation/task-creation.md
+++ b/docs/integration/vision/task/manager_view/task_creation/task-creation.md
@@ -15,13 +15,13 @@ To create a new mission, navigate to **Main Dashboard | Manage Task**. Click the
### Duplicate Existing
-In this section, you can view all previously created missions, including those that have been deleted.
+This section allows you to view and create a copy of an existing mission.
- [**Duplication**](duplication)
### Create New
-In this section, you can create a new mission from scratch, choosing either Assignment or Target.
+This section allows you to create a new mission from scratch, choosing between Assignment and Target types.
- [**Assignment**](assignment)
- [**Target**](target)
diff --git a/docs/integration/vision/task/manager_view/task_creation/task-edit.md b/docs/integration/vision/task/manager_view/task_creation/task-edit.md
index 1aa7017..63aa082 100644
--- a/docs/integration/vision/task/manager_view/task_creation/task-edit.md
+++ b/docs/integration/vision/task/manager_view/task_creation/task-edit.md
@@ -21,9 +21,9 @@ There are certain conditions for editing a mission, as stated in the table below
| Field | Affected Mission Type | Task Status | Description |
|:--------------------------|:---------------------:|:-----------:|:---------------------------------------------------|
| **Start Date** | Both | Ongoing | Start Date cannot be changed. |
-| **Members** | Both | Ongoing | The members added to the mission cannot be removed or have their roles changed. However, it is possible to add more members, but these additions cannot be modified later once updated. |
-| **Milestone and Rewards** | Assignment | Ongoing | If any member achieves a particular milestone, that milestone cannot be changed. However, the following milestones can still be edited. |
-| **Bonus** | Assignment | Ongoing | If any member achieves 100% of the milestone, the bonus cannot be changed. However, it is possible to add a new bonus, but it will also be unchangeable once updated. |
+| **Team Leader, Team Members, Participants** | Both | Ongoing | Roles that are initially assigned to a mission cannot be removed or changed. You can add more roles if needed, but once added, these new roles cannot be modified. |
+| **Milestone and Rewards** | Assignment | Ongoing | Milestones that have already been achieved by a member are locked and cannot be modified, while future milestones remain editable.|
+| **Bonus** | Assignment | Ongoing | Once a member achieves 100% of a milestone, the associated bonus cannot be changed. You can add a new bonus, but it will also become unchangeable once applied. |
| **Grouping Type, Strategy and Condition**| Target | Ongoing | Grouping type, strategy and condition cannot be changed after mission is ongoing. |
#### Non-editable Field
diff --git a/docs/integration/vision/task/user_view/assignment.md b/docs/integration/vision/task/user_view/assignment.md
index 0e9b022..2b267ca 100644
--- a/docs/integration/vision/task/user_view/assignment.md
+++ b/docs/integration/vision/task/user_view/assignment.md
@@ -4,7 +4,7 @@ description: A brief guide on assignment
sidebar_position: 1
---
-Users can view the assignment detail such as title, description, start date, end date, consultant, rewards, bonus criteria, and other progress.
+Users can view the assignment's details such as *title, description, start date, end date, consultant, rewards, bonus criteria, and other progress*.
:::info Info
@@ -22,20 +22,21 @@ The bonus will only be available when the log file's percentage reaches **100%**
### Milestone and Reward
-Users can view the reward for each milestone and are entitled to it once the task's completion percentage reaches the milestone percentage (after manager **approved** the submitted log file).
+Users can view the reward for each milestone and become entitled to it once the task’s completion percentage reaches the milestone, after the manager **approves** the submitted log file.
:::tip Tips
-- The percentage displayed in the chat bubble corresponds to the rewards section.
+- The percentage displayed in the chat bubble corresponds to the rewards section.
- The progress bar displays the user's completion percentage.
:::
-### Progress Tracker
+### Progress Tracker
+
1. Press **Progress Tracker**
- - user can view his/her submitted log file and milestone reward obtained.
+ - Allows users to view their submitted log files along with any milestone rewards earned.
@@ -47,19 +48,20 @@ Indicates the log file is in **Approved** status
-### Update Log File
+### Update Log File
+
1. Press **Update Log File**
- - Allows user to create a new log file, fill in the details, and submit it by clicking **Submit** button.
- - Users **must** fill in all the details.
- - Submitted log file cannot be **edit**.
- - Users are not be able to **submit** log file **before** manager **approve** the previous one.
+ - Allows user to create a new log file, fill in the details, and submit it by clicking **Submit** button.
+ - Users **must** fill in all the details.
+ - Submitted log file cannot be **edited**.
+ - Users are unable to **submit** log file **before** manager **approves** the previous one.
### Submission Bonus Request
-1. This form is only available when the log file submission is **100%**.
-2. Users are allowed to submit bonus request by choosing the bonus criteria and add on remark.
+1. This form is only available when the log file submission is **100%**.
+2. Users are allowed to submit bonus request by selecting the bonus criteria and add on remark.
:::warning Alert
@@ -68,3 +70,7 @@ Bonus request can only be submitted once.
:::
+
+### Change Log
+
+Please refer [**Change Log**](../manager_view/assignment/#change-log)
diff --git a/docs/integration/vision/task/user_view/quest.md b/docs/integration/vision/task/user_view/quest.md
index a9fc519..91e39f0 100644
--- a/docs/integration/vision/task/user_view/quest.md
+++ b/docs/integration/vision/task/user_view/quest.md
@@ -4,11 +4,9 @@ description: A brief guide on quest
sidebar_position: 3
---
-- Users can join available quests by clicking **Join Quest** button
-- Some quests require manager approval, which places the request in **Pending** status
-- Users can cancel a pending request by clicking **Cancel Join Quest**
-- Quests that don't require join permission will allow users to join directly.
-- After joining, users will be navigate to [**Target**](target.md) or [**Assignment**](assignment.md)
+- Open quests are available for all users to join and earn rewards, as they are not restricted to specific employees.
+- Quests can be **Target** or **Assignment**.
+- After successfully joining, users will be navigate to [**Target**](target.md) or [**Assignment**](assignment.md).
:::warning Alert
@@ -16,4 +14,18 @@ After joining, users **cannot** quit the task.
:::
-
+### Direct Join
+
+- Quests that **do not** require join permission from manager.
+- Users can join the quests directly by clicking the **Join Quest** button.
+
+ 
+
+### Requires Join Permission
+
+- Quests that require manager approval.
+- Users can request to join the quest by clicking the **Request To Join** button.
+- While awaiting manager approval, the request is placed in **Pending** status, as shown in the image below.
+- Users can cancel a pending request by clicking the **Cancel Join Quest**.
+
+
diff --git a/docs/integration/vision/task/user_view/target.md b/docs/integration/vision/task/user_view/target.md
index 6895d7e..a1afe1b 100644
--- a/docs/integration/vision/task/user_view/target.md
+++ b/docs/integration/vision/task/user_view/target.md
@@ -4,11 +4,11 @@ description: A brief guide on target
sidebar_position: 2
---
-Users can view the target detail such as title, task creator, description, start date, end date, strategy, rewards, and ranking.
+Users can view the target's details such as *title, task creator, description, start date, end date, strategy, rewards, and ranking*.
:::note Note
-Team task will only **visible** for team leader.
+Team task is only **visible** for team leader.
:::
@@ -18,10 +18,14 @@ Progress of the task will be calculated based on the target type.
**Individual**: Progress of the employee himself
-**Team**: Total progress of all members (include team leader)
+**Team**: Total progress of all members (including team leader)
:::
-| Individual | Team |
-|-----------------------------------------------------------|----------------------------------------------|
-|  | |
\ No newline at end of file
+| Individual | Team |
+| ------------------------------------------------------------------------------------- | ------------------------------------------------------------------------- |
+|  |  |
+
+### Change Log
+
+Please refer [**Change Log**](../manager_view/assignment/#change-log)
diff --git a/docs/integration/vision/upskill/introduction.md b/docs/integration/vision/upskill/introduction.md
index 9d4e7ea..17f1898 100644
--- a/docs/integration/vision/upskill/introduction.md
+++ b/docs/integration/vision/upskill/introduction.md
@@ -1,86 +1,117 @@
---
title: Introduction
-description: A brief explanation about Upskill
+description: A brief explanation about Upskill
sidebar_position: 1
---
# Introduction
-### Rewards Type
+Upskill is a module that allows employees to learn new skills by joining courses. **Managers** *can create courses, set rewards, edit course details, mark attendance, approve bonus requests, and finalise the course*. **Employees** can *view available courses, register for a course, request bonuses, and view the rewards they have earned throughout the course*.
+
+### Rewards Type
#### **Rewards by Completion**
- - Rewards are issued when participants achieve full attendance across all sessions (100% attendance).
- - Participants can view their session reward only after the all sessions has ended, as the reward depends on their overall attendance.
- :::info[Note]
- By default, a course with only one session is considered "reward by completion."
- :::
+- Rewards are issued when participants **achieve full attendance** across all sessions *(100% attendance)*.
+- Participants can view their session reward only after the all sessions has ended, as the reward depends on their overall attendance.
- :::danger[Warning]
- Participants will not receive any reward if they miss any session in a completion-based course.
- :::
+:::info[Note]
+By default, a course with only one session is considered **"Reward by Completion"**.
+:::
-
+:::danger[Warning]
+Participants will not receive any session reward if they missed any session in a completion-based course.
+:::
#### **Rewards by Session**
- - Rewards are issued once participants attend any session.
- - Participants can view their updated reward immediately after each session ended.
- :::info[Note]
- Session-based course requires at least two sessions.
- :::
+- Rewards are issued once participants **attend any session**.
+- Participants can view their updated reward immediately after each session ended.
-
+:::info[Note]
+Session-based course requires **at least two sessions**.
+:::
+
+### Course Role
+#### **Admin**
+- The **course creator** is automatically assigned as the first admin and cannot be removed.
+- Admin holds the **highest** level of **privileges** in the course.
+- They can perform all actions including *editing course details, managing participants, marking attendance, and approving bonus requests*.
+#### **Tutor**
+- The **lead instructor** of the course.
+- Each course can have **only one** tutor.
+- Tutors hold the second-highest level of privileges, after admins.
+- **Except for reward-related details** — such as tutor and assistant assignments, Step 3 reward settings, and admin roles, tutors can perform **same actions as admin**.
-
-### Course visibility
-- The diagram below illustrates how course visibility is set for branches, departments, and HR groups.
-
+:::info[Note]
+Tutors cannot edit reward-related course details or assign tutors, assistant tutors, or admins.
+:::
-#### **User Visibility**
-- Participants can view courses open to their own branch, department, and HR group.
-- However, participants can join courses from other branches, departments, or HR groups if a manager manually adds them to the course.
+#### **Assistant**
-#### **Manager Visibility**
-- Managers can only **manage** courses involving the **branch and department that are under their management area** which is set in payroll.
-- For **other branches and departments**, managers can only **view** the course information **without reward details**.
+- There can be **multiple** assistants in a course.
+- Assistants hold the **same level of privileges as tutor**.
+- Multiple assistant tiers can be created, each with different reward allocations.
-
+#### **Participant**
-| Properties
| Description
| Note
|
-|:-----------------------------|:-----------------------------------------------------------------------------------|:---------|
-| **Attendees** | To view **registered employees** of this course, categorized by department, branch, or HR group, with department set as the default filter.| Can click on employee to view their participant profile which includes summary of attendance and rewards earned in this course.
To know more about participant's profile, [click here](manager_view/upskill#participants-profile)
-| **Rewards** | To view the **total cash and coins spent** on this course, distributed among the tutor, assistants, and participants, along with detailed rewards earned by each participant. | To know more about rewards summary, [click here](manager_view/upskill#reward-summary) |
-| **Bonus** | To view, approve and edit bonus requests. | To know more about bonus requests, [click here](manager_view/upskill#bonus-requests) |
-| **Attendance** | To view and mark attendance. | To know more about attendance, [click here](manager_view/upskill#attendance)|
-| **Finalise/Edit** | To edit, manually complete or finalise course. | To know more about:
- Edit course, [click here](manager_view/upskill-creation#edit-course)
- Complete course, [click here](manager_view/upskill#complete-course)
- Finalise course, [click here](manager_view/upskill#finalise-course)|
+- Employees who have registered for the course.
+- Participants can view their attendance records, request bonuses, and track rewards earned.
+
+### Course Visibility
+- The dashboard contains two buttons: upskill and manage upskill.
+ **Upskill**: Displays courses where the employee is a **participant, tutor, or assistant**.
+ **Manage Upskill**: Displays courses where the employee is assigned as **admin**.
+ 
+:::info[Note]
+
+- Employees who are **not managers** cannot view **others’ upskill** or create courses.
+
+:::
+#### **User Visibility**
+- Participants can view courses open to exactly their own branch, department, and HR group.
+- However, participants still can join courses from other branches, departments, or HR groups if a manager manually adds them to the course.
+- The diagram below illustrates how course visibility is set for branches, departments, and HR groups.
+
+
+#### **Manager Visibility**
+- Employees can only manage courses where they are assigned as admin. To understand more about admin, [click here](#course-role)
+- Courses where they are not admins will appear under the **others' upskill view** where managers can only **view** the public course information **without reward details**.
+
+| Properties
| Description
| Note
|
+| :----------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Attendees** | To view **registered employees** of this course, categorized by department, branch, or HR group, with department set as the default filter. | Can tap on employee to view their participant profile which includes summary of attendance and rewards earned in this course.
To know more about participant's profile, [click here](manager_view/upskill#participants-profile) |
+| **Rewards** | To view the **total cash and coins spent** on this course, distributed among the tutor, assistants, and participants, along with detailed rewards earned by each participant. | To know more about rewards summary, [click here](manager_view/upskill#reward-summary) |
+| **Bonus** | To view, approve and edit bonus requests from participants. | To know more about bonus requests, [click here](manager_view/upskill#bonus-requests) |
+| **Attendance** | To view and mark attendance. | To know more about attendance, [click here](manager_view/upskill#attendance) |
+| **Edit/Complete/Finalise Button** | To edit, manually complete or finalise course *(depending on course status)*. | To know more about:
- Edit course, [click here](manager_view/upskill-creation#edit-course)
- Complete course, [click here](manager_view/upskill#complete-course)
- Finalise course, [click here](manager_view/upskill#finalise-course) |
-### Course status
-- There are **4 course status** in upskill module:
+### Course Status
+- There are **4 course statuses** in upskill module:
-| Status | Description |
-|:-------------------------------------|:-------------------------------------------|
-| **Upcoming** | Course not yet started. |
-| **Ongoing** | The first session has started.
The last session may have ended but the course remains ongoing until the manager manually complete it. |
-| **Completed** | Course is manually completed by manager.
[Complete course](manager_view/upskill#complete-course) |
-| **Finalised** | Course is manually finalised by manager.
[Finalise course](manager_view/upskill#finalise-course)|
+| Status | Description |
+| :------------ | :---------------------------------------------------------------------------------------------------------------------------------------- |
+| **Upcoming** | Course not yet started. |
+| **Ongoing** | The first session has started.
The last session may have ended but the course remains ongoing until the manager manually completes it. |
+| **Completed** | Course is manually completed by manager.
[Complete course](manager_view/upskill#complete-course) |
+| **Finalised** | Course is manually finalised by manager.
[Finalise course](manager_view/upskill#finalise-course) |
- Below shows the **course card** of different course status:
@@ -92,49 +123,46 @@ sidebar_position: 1
- Both users and managers can **perform different actions** depending on the course status:
#### **User Course Status**
+
-| Actions | Upcoming | Ongoing | Completed | Finalised | Cannot perform when|
-|:-------------------------------------|:--------:|:-------:|:---------:|:---------:|:--------------------------|
-| **Register** | ✓ | ✓ | | | Course is **full**.
**Last** session has **ended**. |
-| **Unregister** | ✓ | | | | Course is **private** as participant is added by manager.
-| **+ Request** | | | ✓ | | **Absent** from **all** sessions.
-| **Request status** | | | ✓ | ✓ | -
+| Actions | Upcoming | Ongoing | Completed | Finalised | Cannot perform when |
+| :---------------------------- | :------: | :-----: | :-------: | :-------: | :-------------------------------------------------------- |
+| **Register** | ✓ | ✓ | | | Course is **full**.
**Last** session has **ended**. |
+| **Unregister** | ✓ | | | | Course is **private** as participant is added by manager. |
+| **Request Bonus (+ Request)** | | | ✓ | | **Absent** from **all** sessions. |
+| **View Request Status** | | | ✓ | ✓ | - |
#### **Manager Course Status**
-| Actions | Upcoming | Ongoing | Completed | Finalised | Condition |
-|:----------------------------------------------|:--------:|:-------:|:---------:|:---------:|:------------------------------------|
-| **Attendees** - view attendees & participant's profile | ✓ | ✓ | ✓ | ✓ | |
-| **Rewards** - view rewards summary | ✓ | ✓ | ✓ | ✓ | Summary table only will be shown when the course is finalised. |
-| **Bonus** - approve bonus requests | | | ✓ | | - |
-| **Attendance** - mark attendance | | ✓ | ✓ | | The session must be started. |
-| **Edit** - edit course | ✓ | ✓ | | | - |
-| **Complete** - complete course | | ✓ | | | Last session must be ended. |
-| **Finalise** - finalise course | | | ✓ | | All bonus requests must be marked. |
+| Actions | Upcoming | Ongoing | Completed | Finalised | Condition |
+| :----------------------------------------------------- | :------: | :-----: | :-------: | :-------: | :------------------------------------------------------------- |
+| **Attendees** - view attendees & participant's profile | ✓ | ✓ | ✓ | ✓ | |
+| **Rewards** - view rewards summary | ✓ | ✓ | ✓ | ✓ | Summary table only will be shown when the course is finalised. |
+| **Bonus** - approve bonus requests | | | ✓ | | - |
+| **Attendance** - mark attendance | | ✓ | ✓ | | The session must be started. |
+| **Edit** - edit course | ✓ | ✓ | | | - |
+| **Complete** - complete course | | ✓ | | | Last session must be ended. |
+| **Finalise** - finalise course | | | ✓ | | All bonus requests must be marked. |
-### Course Privacy
+### Course Privacy
-#### **Public course**
-- A public course is visible to participants in specific branches, departments, or HR groups as set by the manager at [here](#course-visibility).
-- It allows eligible participants to register on their own.
+#### **Public course**
+
+- A public course is visible to participants in specific branches, departments, or HR groups as set by the manager [here](#course-visibility).
+- It allows eligible participants to register on their own.
#### **Private course**
-- A private course is not open for general registration.
-- Instead, participants are manually added by the manager.
-- Only those who are added to the course can view it in the course tab (registered or completed tab).
+
+- A private course is not open for general registration.
+- Instead, participants are manually added by the manager.
+- Only those who are added to the course can view it in the course tab *(registered or completed tab)*.
**Course card** of public and private course:
-
-:::info[Note]
-When manager creates a **private course**, the course visibility will be the branch and department that manager belongs to.
-The **visibility** of a private course will always be the same as the **creator's branch and department**, **regardless** of which manager **edits** the course.
-
-:::
diff --git a/docs/integration/vision/upskill/manager_view/upskill-creation.md b/docs/integration/vision/upskill/manager_view/upskill-creation.md
index 6f0768e..30f8bcf 100644
--- a/docs/integration/vision/upskill/manager_view/upskill-creation.md
+++ b/docs/integration/vision/upskill/manager_view/upskill-creation.md
@@ -5,23 +5,26 @@ sidebar_position: 1
---
# Upskill Creation
+
## Creation Steps
+
### Step 1 - Course Information
+
-| Properties
| Description
| Required | Note
|
-|:----------------------------------------------|:------------------------------------------|:--------:|:----|
-| **Title** | The title of the course. | ✓ | - |
-| **Description** | A detailed description of the course. | ✗ | - |
-| **Tutor** | The main tutor of the course. | ✓ | - |
-| **Assistant Tutor** | The assistant tutor for the course. | ✗ | - |
-| **Clear** | Clears all course information on the current page. | - | **Manager:**
Clears all course information.
**Tutor Assistants:**
Clears all excepts tutor and assistants information.|
-| **Next** | Navigate to the next page. | - | - |
+| Properties
| Description
| Required | Note
|
+| :----------------------------------- | :------------------------------------------------- | :------: | :-------------------------------------------------------------------------------------------------------------------------------------- |
+| **Title** | The title of the course. | ✓ | - |
+| **Description** | A detailed description of the course. | ✗ | - |
+| **Tutor** | The main tutor of the course. | ✓ | - |
+| **Assistant Tutor** | The assistant tutor for the course. | ✗ | - |
+| **Clear** | Clears all course information on the current page. | - | **Manager:**
Clears all course information.
**Tutor Assistants:**
Clears all excepts tutor and assistants information. |
+| **Next** | Navigate to the next page. | - | - |
#### Tutor
- **Tutor** is the employee responsible for giving lessons and providing guidance throughout the learning process in the course.
-- There will be only **one** lead tutor in every course.
+- There will be only **one** lead tutor in every course.
@@ -29,28 +32,18 @@ sidebar_position: 1
#### Assistant Tutor
- **Assistant Tutor** plays a role in supporting the lead tutor in completing the course smoothly.
-- There can be **multiple** assistant tutors in every course.
+- There can be **multiple** assistant tutors in every course.
-
-
-
-
-
-
-
-
-
-
-
+
### Step 2 - Sessions Information
| Properties
| Description
| Note
|
|:-------------------------------------|:--------------------------------------| :----------------------------- |
-| **Date Range** | Display the start date and end date of the course which is determined by first and last session's date. - |
-| **Rewards By Session / Completion** | Determine whether the reward is calculated **by session** or **by completion**.
**By Completion**
- Rewards are issued when participants achieve full attendance across all sessions (100% attendance).
**By Session**
- Rewards are issued once participants attend any session. | **On:**
Rewards calculate by session.
**Off:**
Rewards calculate by completion.
To know more about rewards type, [click here](../introduction#rewards-type)|
+| **Date Range** | Display the start date and end date of the course which is determined by first and last session's date. | -
+| **Rewards By Session / Completion** | Determine whether the reward is calculated **by session** or **by completion**.
**By Completion**
- Rewards are issued when participants achieve full attendance across all sessions *(100% attendance)*.
**By Session**
- Rewards are issued once participants attend any session. | **On:**
Rewards calculate by session.
**Off:**
Rewards calculate by completion.
To know more about rewards type, [click here](../introduction#rewards-type)|
| **Session (Dropdown)**| The details of each session of the course. | - |
| **Add** | Add more sessions to the course. | - |
| **Back** | Navigate back to the previous page. | - |
@@ -68,110 +61,61 @@ sidebar_position: 1
| **End Time** | The end time of the session. | ✓ | Cannot be earlier than start time |
| **Venue** | The venue of the session. | ✗ | - |
-
-
-
-
-
-
-
-
-
-
-
+
### Step 3 - Rewards Information
-| Properties
| Description
| Required | Note
|
-|:-------------------------------------|:------------------------------------------|:--------:|:----|
-| **Session Rewards** | **Completion-based course:** There is only **one** completion reward for the entire course.
**Session-based course:** There are **multiple** session rewards. Each session will have their respective session rewards. | ✗ | Default reward is "0". |
-| **Payment by** | Type of payment method for this course.
This payment method only applicable for cash only, coins will be paid immediately upon entitlement. | ✓ | Same concept as in task creation's payment by, [click here](../../task/manager_view/task_creation/assignment#payment-by) |
-| **Bonus Rewards** | Extra criterias that employee can achieve to earn more rewards. | ✗ | Default reward is "0".
If a value is specified in cash or coins, the bonus criteria must be provided.
Same concept as in task creation's bonus, [click here](../../task/manager_view/task_creation/assignment#bonus) |
-| **Clear** | Clears all rewards on the current page. | - | **Manager:**
Clears all rewards.
**Tutor Assistants:**
No clear button as they cannot edit rewards.|
-| **Back** | Navigate to the previous page. | - | - |
-| **Next** | Navigate to the next page. | - | - |
+| Properties
| Description
| Required | Note
|
+| :----------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | :------: | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Session Rewards** | **Completion-based course:** There is only **one** completion reward for the entire course.
**Session-based course:** There are **multiple** session rewards. Each session will have their respective session rewards. | ✗ | Default reward is "0". |
+| **Payment by** | Type of payment method for this course.
This payment method only applicable for cash only, coins will be paid immediately upon entitlement. | ✓ | Same concept as in task creation's payment by, [click here](../../task/manager_view/task_creation/assignment#payment-by) |
+| **Bonus Rewards** | Extra criterias that employee can achieve to earn more rewards. | ✗ | Default reward is "0".
If a value is specified in cash or coins, the bonus criteria must be provided.
Same concept as in task creation's bonus, [click here](../../task/manager_view/task_creation/assignment#bonus) |
+| **Clear** | Clears all rewards on the current page. | - | **Manager:**
Clears all rewards.
**Tutor Assistants:**
No clear button as they cannot edit rewards. |
+| **Back** | Navigate to the previous page. | - | - |
+| **Next** | Navigate to the next page. | - | - |
#### Session rewards
- **Completion-based course:** There is only **one** completion reward for the entire course.
-- **Session-based course:** There are **multiple** session rewards. Each session will have their respective session rewards.
+- **Session-based course:** There are **multiple** session rewards. Each session will have their respective session rewards.
-
-
-
-
-
-
-
-
-
+
### Step 4 - Participants Information
| Properties
| Description
| Note
|
|:-----------------------------|:-----------------------------------------------------------------------------------|:---------|
+| **Apply Group** | Apply groups with preset roles for both admin and participant. | To know more about group, [click here](../../group/#apply-group).
+| **Clear** | Clears all admin and participants on the current page. | Uneditable participants will not be cleared.
+| **Creator** | Creator of course will be the first admin and cannot be removed. | - |
+| **Add Admin** | Lead you to the select admin page. | To know more about admin, [ click here](../introduction#course-role).
+| **Remove Admin** | Remove selected admin. | The first admin (creator) cannot be removed.
| **Is Public** | Determine whether this course is public or private. | **On:**
Public course.
**Off:**
Private course.
To know more about public and private course, [ click here](../introduction#course-privacy).
-| **Filter Icon** | Filter and sort the employee list. | By branch, department & HR group. |
-| **Group Icon** | Apply group members. | To know more about group, [click here](../../group#apply-group).
-| **Select All** | Select all employees as participants. | Can press again to deselect all employees. |
-| **Available Slots** | The available slots left for this course (Number of selected participants / maximum pax). |As this is **private** course, so there is **no maximum pax**, hence the maximum pax is "-".|
-| **Selected Employees** (With tick) | All employees in the companies that **participate** in this course. | Click to **remove** employee from course.
Selected participants cannot be removed when the course has started (ongoing). |
-| **Unselected Employees** (Without tick) | All employees in the companies that **does not participate** in this course. |Click to **add** employee to course.|
+| **Available Slots** | The available slots left for this course *(number of selected participants / maximum pax)*. |As this is **private** course, so there is **no maximum pax**, hence the maximum pax is "-".|
+| **Add Participants** | Lead you to the select participants page. | To know more about participants, [ click here](../introduction#course-role).
+| **Editable Employees** | Currently selected employees that **participate** in this course. | - |
+| **Remove Participant** | Remove selected participant. | - |
+| **Uneditable Employees** | Previously selected participants that cannot be removed. | Only will have this section once the course has started (ongoing).
Once the course has started, only newly added employees is editable.|
| **Back** | Navigate back to the previous page. | - |
-| **Save** | Create or edit the course. | - |
-
-
-#### Is Public
-
-**Public course**
-- A public course is visible to participants in specific branches, departments, or HR groups as set by the manager.
-- It allows eligible **participants to register** on their own.
-
-**Private course**
-- A private course is not open for general registration.
-- Instead, participants are manually **added by the manager**.
-- Only those who are added to the course can view it in the course tab.
-
-:::info[Note]
-If the is public switch is on, the maximum pax, branch, department and HR group fields are required.
-:::
-
-:::tip
-If a course is public, the manager can manually add participants who do not belong to the specified branches, departments, or HR groups.
-:::
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+| **Create or Edit** | Create or edit the course. | - |
## Edit Course
-- The diagram below illustrates the **manager's** and **tutor assistants'** edit permissions based on the different course statuses.
+
+- The diagram below illustrates the **admin's** and **tutor assistants'** edit permissions based on the different course statuses.
- To know more about course status, [click here](../introduction#course-status).
:::info[Note]
Tutor and assistants cannot edit any rewards-related field.
:::
-#### **Manager:**
+#### **Manager:**
-#### **Tutor & Assistants:**
+#### **Tutor & Assistants:**
-
diff --git a/docs/integration/vision/upskill/manager_view/upskill.md b/docs/integration/vision/upskill/manager_view/upskill.md
index 8368ae2..25f7cc3 100644
--- a/docs/integration/vision/upskill/manager_view/upskill.md
+++ b/docs/integration/vision/upskill/manager_view/upskill.md
@@ -14,19 +14,20 @@ sidebar_position: 2
- **Completed tab**: Courses that is completed or finalised.
:::info[Note]
-- Manager can press the switch view button at the app bar to toggle between **manage upskill** (can manage) and **other branch & department** (view only).
+- Manager can tap on the switch view button at the app bar to toggle between **manage upskill** *(can manage)* and **others' upskill** *(view only)*.
- To know more about visibility, [click here](../introduction#course-visibility).
:::
-#### **Other Branch & Department**
-- Manager is not allowed to view the rewards can be earned for each course.
-- Manager can access the course detail by clicking on the course card, but the rewards will remain hidden.
-
+#### **Others' Upskill**
+- Manager is **not allowed to view the rewards** available for each course.
+- Manager is **unable to see private courses**, only public courses are accessible.
+- Manager can access the course detail by clicking on the course card, but the rewards will remain hidden.
+
:::info[Note]
-By default, finalized courses are hidden.
-To view finalized courses, open the filter and **tick** the **finalised** option.
+By default, finalized courses are hidden from the course list.\
+To view them, open the filter settings and **tick** the **Finalised** option. This will display all courses that have been marked as finalised.
:::
+### Transfer Ownership
+- Only the creator will see the **transfer ownership button** in the top-right corner of the app bar *(highlighted in red)*.
+- If the ownership is transferred to someone who is not an admin, that person will automatically be promoted to admin.
+- Once ownership is transferred, the button will no longer be visible to you, as you are no longer the creator.
+- In the third diagram below, ownership has been transferred to Ah Foo, making him the **new creator**. Although he was not originally an admin, he was automatically promoted to admin when he received ownership.
+
+
+
+### Change Log
+- The change log button *(history icon)* is located in the top-right corner of the app bar *(highlighted in red)*.
+- Only **admins, managers, tutors, and assistants** have access to view the change log.
+- The change log displays a record of *course edits, including who made the changes and the details provided by the editor*.
+
+
+
-
### Participant List
- The manager can view participant list by clicking on the **"Attendees"** button.
:::info[Note]
-- The attendees can be sorted by branch, department or HR group using the filter function.
-- By default, the attendees is sorted by department.
+- The attendees can be sorted by Branch, Department or HR group using the filter function.
+- By default, the attendees is sorted by Department.
:::
-
-
### Participant's profile
-- Participant's profile is the summary of attendance and reward (session and bonus reward) obtained by participants.
+- A participant’s profile provides a summary of their attendance and the rewards they have earned, including both session and bonus rewards.
-- **2 ways** to access participant's profile: Attendees & Rewards
+- **2 ways** to access participant's profile:
+ - Attendees
+ - Rewards
- Sample of participant's profile of **session-based** & **completion-based** course:
@@ -62,14 +77,12 @@ To view finalized courses, open the filter and **tick** the **finalised** option
:::info[Note]
-- A greyed-out reward means the participant did not entitle the reward.
+- A greyed-out reward indicates that the participant is not entitled to it.
- However, as long as the course has not been finalised, any changes made by the manager to a participant’s attendance or bonus reward will be reflected in their profile.
- The bonus request status is exactly the same as the course info page, [click here](../user-view#bonus-request-status) to know more.
:::
-
-
### Reward Summary
- The manager can view summary of reward by clicking on the **"Rewards"** button.
@@ -79,7 +92,7 @@ To view finalized courses, open the filter and **tick** the **finalised** option
|:-----------------------------|:-----------------------------------------------------------------------------------|:---------|
| **Total Spend** | To view the total expenses of the company for this course, including rewards allocated to tutors, assistants, and participants. | -
| **Expected Payout Date** | To view the expected payout date for this course. | The expected payout date is set in the creation, [click here](upskill-creation#step-3---rewards-information) to know more. |
-| **Tutor & assistant rewards** | To view the rewards of tutor and assistants. | - |
+| **Tutor & Assistant Rewards** | To view the rewards of tutor and assistants. | - |
| **Session / Completion reward** | To view the session reward entitled by participants.
**Completion-based reward**
- Represented by "C".
- For completion-based courses, there is always a single reward for session rewards, referred to as "C1".
**Session-based reward**
- Represented by "S".
- In this case, there are two sessions: "S1" represents the first session and "S2" represents the second session. | To know more about rewards type, [click here](../introduction#rewards-type)|
| **Bonus reward** | To view the bonus reward entitled by participants. | - |
| **Total reward** | To view the total rewards entitled by participants (session rewards + bonus rewards). | - |
@@ -89,25 +102,23 @@ To view finalized courses, open the filter and **tick** the **finalised** option
:::tip
- **Reward summary table** will only be shown after the course is **finalised**.
-- Manager can also click on the participants' name to access to their participant's profile
+- Manager can also click on the participants' name to access to the participant's profile
- To know more about participant's profile, [click here](#participants-profile).
:::
-
-
### Bonus requests
#### **View Bonus Requests**
- The manager can view bonus requested by the participants by clicking on the **"Bonus"** button.
- There are two statuses for bonus requests:
- - **Pending**: The request has not been approved by the manager and is awaiting approval..
+ - **Pending**: The request has not been approved by the manager and is awaiting approval.
- **Marked**: The request has been approved by the manager but can still be edited.
- The total amount for pending requests is 2 because the request has not yet been approved.
- **Remark** is the comment entered by participants to detail what they achieved in order to meet the bonus criteria.
- **Feedback** is the comments provided by the manager or tutor for the participants.
:::info[Note]
-The **amount** of bonus requested by participant may be **different** but will not **exceed** the original amount.
+The **amount** of bonus requested by participant may be **different** but will not **exceed** the original amount set.
:::
@@ -115,8 +126,8 @@ The **amount** of bonus requested by participant may be **different** but will n
#### **Enter Edit Mode**
- To approve or edit the bonus request, the manager needs to click on the **"Edit"** button.
-- Once in edit mode, the **expand all** will automatically ticked and all bonus requests will be expanded.
-- Manager will be able to view and edit the bonus request details of each participant.
+- Once in edit mode, the **Expand All** will be automatically ticked and all bonus requests will be expanded.
+- Manager is able to view and edit the bonus request details of each participant.
@@ -125,7 +136,7 @@ The **amount** of bonus requested by participant may be **different** but will n
- **Tick & Untick**: The manager can tick or untick the bonus criteria by tapping on the bonus criteria card or checkbox.
- **Edit value**: The manager can edit the value, but it **cannot exceed the original bonus amount** shown at the bottom right corner of the edit field.
- **Give feedback**: The manager can also leave feedback to evaluate the participants' performance.
-- **Approve**: The manager must press the approve button for each participant to confirm the edit.
+- **Approve**: The manager must tap on the **Approve** button for each participant to confirm the changes.
:::warning
@@ -137,11 +148,9 @@ The **amount** of bonus requested by participant may be **different** but will n
:::
-
-
### Attendance
-- The attendance must be marked manually.
-
+- The attendance must be marked manually.
+
#### **View Attendance**
- The manager or tutor can view attendance summary from the session card.
- Once the **session has started**, a **pen icon** will **appear** beside the attendance which indicates the attendance is **editable**.
@@ -157,18 +166,16 @@ The **amount** of bonus requested by participant may be **different** but will n
- Manager can edit the attendance anytime before finalising the course.
:::
:::tip
-- If the majority participants are present, the manager can select all participants in the "Absent" tab and check them in.
-- Then, in the "Checked-In" tab, manager can search for the absent participants and mark them as absent.
+- If the majority participants are present, the manager can select all participants in the **"Absent"** tab and check them in.
+- Then, in the **"Checked-In"** tab, manager can search for the absent participants and mark them as absent.
:::
-
-
### Complete Course
-- When all sessions of course has ended, the complete button will appear in the bottom bar of course info page for manager to manually complete the course.
-- Manager can also choose to edit course and add more sessions.
+- When all sessions of a course has ended, the complete button will appear in the bottom bar of course info page for manager to manually mark the course as **Completed**.
+- Manager can also choose to edit the course and add more sessions.
:::warning
Once the course is completed, the course details cannot be edited anymore.
@@ -177,23 +184,21 @@ Once the course is completed, the course details cannot be edited anymore.
:::tip
- Participants can only start to request bonus after course is completed.
- Bonus can only be approved after the course is completed.
-- To view more actions a manager can perform in "Completed" course, [click here](../introduction#manager-course-status)
+- To view more actions a manager can perform in a **"Completed"** course, [click here](../introduction#manager-course-status)
:::
-
-
### Finalise Course
- Finalising a course marks an end to the course.
:::info[Note]
-- All course rewards, including those for tutors, assistants, and participants, will be distributed once the course is finalised.
-- Coins are awarded immediately, while cash rewards are given based on the expected payout date.
+- All course rewards, including those for *tutors, assistants, and participants*, will be distributed once the course is finalised.
+- Coins are awarded immediately, while **cash rewards are given based on the expected payout date**.
:::
:::tip
-- Before finalising a course, the manager must mark all bonus requests.
+- Before finalising a course, the manager **must** mark all bonus requests.
- A reminder will be issued if any participants have not yet requested a bonus.
:::
diff --git a/docs/integration/vision/wallet.md b/docs/integration/vision/wallet.md
index cb9924c..67b74ba 100644
--- a/docs/integration/vision/wallet.md
+++ b/docs/integration/vision/wallet.md
@@ -4,93 +4,101 @@ sidebar_position: 7
# Wallet
## User View
-### Wallet home page
+### Wallet Home Page
+- Displays a card showing the amount of the upcoming payout.
+- Shows a leaderboard highlighting the top-earning employee.
+- Provides a quest list for employees to join.
+- Includes menu buttons with four modules:
+ - Payout
+ - Entitlement
+ - Coin Transaction
+ - Gifts
+
-- contains a card showing the amount of upcoming payout
-- a leaderboard displaying the top earning employee
-- a quest list for employees to join
-- menu buttons contains 4 modules:\
- -- payout\
- -- entitlement\
- -- coin transactions\
- -- gifts
-#### swiping left will show similar UI to above, displaying information in relation to coins
+
+- Swiping left shows a similar interface, but displaying information related to coins.\
+- Tap on the **"View All"** button to see the full list of the leaderboard.
-#### tap on "view all" button to see full list of the leaderboard
|  | ➜ |  |
|:---:|---|:---:|
-### Payout (based on payment date)
+### Payout (Based on Expected Payout Date)
+- Switch between Upcoming and History tabs to filter data.
+- View a bar chart visualising earnings.
+- See a monthly payout grid, with each month tappable to display a detailed pop-up.
+- In the History tab, an exclamation mark will appear for any unpaid payouts.
+
 
-- filter data by upcoming or history by switching tabs
-- barchart to visualise earnings
-- grid showing payout per month, able to tap into it for details pop up\
- |  | ➜ |  |
- |:---:|---|:---:|
-### Entitlement (based on achieved date)
-- barchart to visualise earnings
-- grid showing entitlement per month, able to tap into it for details pop up
+- If a payout has been officially paid, the **payment date** will be shown instead of the **entitled date**.
+- For payouts past the expected payout date, a **Paid** or **Unpaid** status will indicate whether the payment has been made.
- |  | ➜ |  |
- |:---:|---|:---:|
+|  | ➜ |  |
+|:---:|---|:-------------------------------------------------------------------------------:|
+
+### Entitlement (Based On Achieved Date)
+- View a bar chart visualising earnings.
+- See a monthly entitlement grid, with each month tappable to display a detailed pop-up.
+
+|  | ➜ |  |
+|:---:|---|:---:|
### Coin Transactions
-
-- graph to visualise coin earnings and spendings
-- list view to show logs of coin transactions
-- press on segmented buttons to filter data displayed
+- View a line chart visualising coin earnings and spendings.
+- Browse a list of coin transaction logs.
+- Use segmented buttons to filter the displayed data.
|  | ➜ |  |
|:---:|---|:---:|
-- use the dropdown button to sort the list\
+- Use the dropdown button to sort the transaction list\
## Manager View
-### Manage payout/entitlement page
-both payout and entitlement view have similar layout and function
+### Manage Payout/Entitlement
+Both **Payout** and **Entitlement** views share a similar layout and functionality.
- - press on icon to go to manage payout, which shows the company total payout/entitlement
+ - Tap the icon (highlighted in red) to navigate to **Manage Payout**, which displays the company’s total payout or entitlement.
|  | ➜ |  |
|:---:|---|:---:|
- - tapping the grid will now show a list of employee instead\
+ - Tapping an **Upcoming Payout card** in the grid will now display a list of employees.
+- In the **History Payout** tab, a red exclamation mark will appear next to an employee’s avatar if their payout remains unpaid past the expected payout date.\
- - tapping on a name will show payout/entitlement details of that employee\
- (**this view will differ when you are in payout history/entitlement view compared to upcoming payout view**)
- - **a) payout history/entitlement** \
+
+ - Tapping an employee’s name will display their payout or entitlement details.\
+ (*This view will differ depending on whether you are in the Payout History or Entitlement view, compared to the Upcoming Payout view.*)\
+ **A. Payout History/Entitlement** \
+- If a payout has been officially paid, the **payment date** will be shown instead of the **entitled date**.
+- For payouts past the expected payout date, a **Paid** or **Unpaid** status will indicate whether the payment has been made.
- - **b) upcoming payout** \
- as upcoming payout are not yet paid out, their payout date can be editited, so \
- there is an arrow button on the card which would open edit view
+ **B. Upcoming Payout**
+ - Since upcoming payouts have not yet been paid, their payout date can be edited. An arrow button on the card opens the edit view.
- | 1) tap on arrow button to open edit view | | 2) tap on the date to open date picker | | 3) use the date picker to choose a date |
+ | 1) Tap on arrow button to open edit view | | 2) Tap on the date to open the calendar | | 3) Use the calendar to select a new date |
|:---:|---|:---:|---|:---:|
|  | ➜ |  | ➜ | |
- | 4) after selecting, submit to save changes |||||
+ | **4) After selecting, tap on submit to save changes** |||||
|  |||||
- - you can search payout/entitlement info of a specific employee using "search employee button"
+ - Use the **Search Employee** button to find the payout or entitlement information of a specific employee.
|  | ➜ |  | ➜ | |
|:---:|---|:---:|---|:---:|
- - use the stat icon to compare the payout/entitlement history of up to 3 employees
+ - Use the **Stats icon** to compare the payout or entitlement history of up to three employees.
|  | ➜ |  | ➜ | |
|:---:|---|:---:|---|:---:|
- ### Manage coin transactions page
-
-
- - tap the top right icon and then select an employee from the list, then the coin transactions of that employee will be shown
+ ### Manage Coin Transactions
+ - Tap the **top-right icon**, select an employee from the list, and view that employee’s coin transactions.
|  | ➜ |  | ➜ | |
|:---:|---|:---:|---|:---:|
diff --git a/static/img/integration/vision/group/g-add-1.jpg b/static/img/integration/vision/group/g-add-1.jpg
new file mode 100644
index 0000000..c14522f
Binary files /dev/null and b/static/img/integration/vision/group/g-add-1.jpg differ
diff --git a/static/img/integration/vision/group/g-add-2.jpg b/static/img/integration/vision/group/g-add-2.jpg
new file mode 100644
index 0000000..cc01078
Binary files /dev/null and b/static/img/integration/vision/group/g-add-2.jpg differ
diff --git a/static/img/integration/vision/group/g-apply.png b/static/img/integration/vision/group/g-apply.png
index d863bab..9a4c66f 100644
Binary files a/static/img/integration/vision/group/g-apply.png and b/static/img/integration/vision/group/g-apply.png differ
diff --git a/static/img/integration/vision/group/g-edit-1.jpg b/static/img/integration/vision/group/g-edit-1.jpg
new file mode 100644
index 0000000..62636a7
Binary files /dev/null and b/static/img/integration/vision/group/g-edit-1.jpg differ
diff --git a/static/img/integration/vision/group/g-edit-2.jpg b/static/img/integration/vision/group/g-edit-2.jpg
new file mode 100644
index 0000000..6ccbf10
Binary files /dev/null and b/static/img/integration/vision/group/g-edit-2.jpg differ
diff --git a/static/img/integration/vision/main-dashboard/employeeDetails.jpg b/static/img/integration/vision/main-dashboard/employeeDetails.jpg
new file mode 100644
index 0000000..97a0f25
Binary files /dev/null and b/static/img/integration/vision/main-dashboard/employeeDetails.jpg differ
diff --git a/static/img/integration/vision/main-dashboard/personalInformation.jpg b/static/img/integration/vision/main-dashboard/personalInformation.jpg
new file mode 100644
index 0000000..bc0d5a1
Binary files /dev/null and b/static/img/integration/vision/main-dashboard/personalInformation.jpg differ
diff --git a/static/img/integration/vision/main-dashboard/personalInformation.png b/static/img/integration/vision/main-dashboard/personalInformation.png
deleted file mode 100644
index 7b6ccdc..0000000
Binary files a/static/img/integration/vision/main-dashboard/personalInformation.png and /dev/null differ
diff --git a/static/img/integration/vision/main-dashboard/searchEmployees.jpg b/static/img/integration/vision/main-dashboard/searchEmployees.jpg
new file mode 100644
index 0000000..d7c58fb
Binary files /dev/null and b/static/img/integration/vision/main-dashboard/searchEmployees.jpg differ
diff --git a/static/img/integration/vision/mi_creation/a-2.2.2.png b/static/img/integration/vision/mi_creation/a-2.2.2.png
index 4e3dca8..836f674 100644
Binary files a/static/img/integration/vision/mi_creation/a-2.2.2.png and b/static/img/integration/vision/mi_creation/a-2.2.2.png differ
diff --git a/static/img/integration/vision/mi_creation/d-2.png b/static/img/integration/vision/mi_creation/d-2.png
index 50ff0a2..476a9ec 100644
Binary files a/static/img/integration/vision/mi_creation/d-2.png and b/static/img/integration/vision/mi_creation/d-2.png differ
diff --git a/static/img/integration/vision/mi_creation/g-apply.png b/static/img/integration/vision/mi_creation/g-apply.png
new file mode 100644
index 0000000..9a4c66f
Binary files /dev/null and b/static/img/integration/vision/mi_creation/g-apply.png differ
diff --git a/static/img/integration/vision/mi_creation/participant-steps.png b/static/img/integration/vision/mi_creation/participant-steps.png
new file mode 100644
index 0000000..5cf6b61
Binary files /dev/null and b/static/img/integration/vision/mi_creation/participant-steps.png differ
diff --git a/static/img/integration/vision/mi_creation/participant-team.png b/static/img/integration/vision/mi_creation/participant-team.png
new file mode 100644
index 0000000..e651e3b
Binary files /dev/null and b/static/img/integration/vision/mi_creation/participant-team.png differ
diff --git a/static/img/integration/vision/mi_creation/participant.png b/static/img/integration/vision/mi_creation/participant.png
new file mode 100644
index 0000000..de71b79
Binary files /dev/null and b/static/img/integration/vision/mi_creation/participant.png differ
diff --git a/static/img/integration/vision/mi_creation/q.png b/static/img/integration/vision/mi_creation/q.png
deleted file mode 100644
index 4a2d390..0000000
Binary files a/static/img/integration/vision/mi_creation/q.png and /dev/null differ
diff --git a/static/img/integration/vision/mi_creation/quest.png b/static/img/integration/vision/mi_creation/quest.png
new file mode 100644
index 0000000..751d68e
Binary files /dev/null and b/static/img/integration/vision/mi_creation/quest.png differ
diff --git a/static/img/integration/vision/mi_creation/t-2.jpg b/static/img/integration/vision/mi_creation/t-2.jpg
new file mode 100644
index 0000000..042f05b
Binary files /dev/null and b/static/img/integration/vision/mi_creation/t-2.jpg differ
diff --git a/static/img/integration/vision/mi_creation/t-2.png b/static/img/integration/vision/mi_creation/t-2.png
deleted file mode 100644
index bc04804..0000000
Binary files a/static/img/integration/vision/mi_creation/t-2.png and /dev/null differ
diff --git a/static/img/integration/vision/mi_creation/t-3.png b/static/img/integration/vision/mi_creation/t-3.png
deleted file mode 100644
index 1ead821..0000000
Binary files a/static/img/integration/vision/mi_creation/t-3.png and /dev/null differ
diff --git a/static/img/integration/vision/task/asgmtReward.png b/static/img/integration/vision/task/asgmtReward.png
index b1ca26e..85f3063 100644
Binary files a/static/img/integration/vision/task/asgmtReward.png and b/static/img/integration/vision/task/asgmtReward.png differ
diff --git a/static/img/integration/vision/task/assignmentDetail.png b/static/img/integration/vision/task/assignmentDetail.png
index 6474b9a..bb50c7f 100644
Binary files a/static/img/integration/vision/task/assignmentDetail.png and b/static/img/integration/vision/task/assignmentDetail.png differ
diff --git a/static/img/integration/vision/task/changeLog.png b/static/img/integration/vision/task/changeLog.png
index 9cfb5ff..dad7426 100644
Binary files a/static/img/integration/vision/task/changeLog.png and b/static/img/integration/vision/task/changeLog.png differ
diff --git a/static/img/integration/vision/task/directJoin.png b/static/img/integration/vision/task/directJoin.png
new file mode 100644
index 0000000..43afaf4
Binary files /dev/null and b/static/img/integration/vision/task/directJoin.png differ
diff --git a/static/img/integration/vision/task/finaliseAsgmt.jpg b/static/img/integration/vision/task/finaliseAsgmt.jpg
new file mode 100644
index 0000000..ab938bd
Binary files /dev/null and b/static/img/integration/vision/task/finaliseAsgmt.jpg differ
diff --git a/static/img/integration/vision/task/finaliseAsgmt.png b/static/img/integration/vision/task/finaliseAsgmt.png
deleted file mode 100644
index c2ea3f6..0000000
Binary files a/static/img/integration/vision/task/finaliseAsgmt.png and /dev/null differ
diff --git a/static/img/integration/vision/task/individualTarget.png b/static/img/integration/vision/task/individualTarget.png
index 93ebc49..8bab16f 100644
Binary files a/static/img/integration/vision/task/individualTarget.png and b/static/img/integration/vision/task/individualTarget.png differ
diff --git a/static/img/integration/vision/task/mgrAssignmentDetail.png b/static/img/integration/vision/task/mgrAssignmentDetail.png
index af444df..048df74 100644
Binary files a/static/img/integration/vision/task/mgrAssignmentDetail.png and b/static/img/integration/vision/task/mgrAssignmentDetail.png differ
diff --git a/static/img/integration/vision/task/mgrCompleteAsgmt.png b/static/img/integration/vision/task/mgrCompleteAsgmt.png
index ba9d85c..0747102 100644
Binary files a/static/img/integration/vision/task/mgrCompleteAsgmt.png and b/static/img/integration/vision/task/mgrCompleteAsgmt.png differ
diff --git a/static/img/integration/vision/task/mgrIndividualTarget.png b/static/img/integration/vision/task/mgrIndividualTarget.png
index d928817..ecffd61 100644
Binary files a/static/img/integration/vision/task/mgrIndividualTarget.png and b/static/img/integration/vision/task/mgrIndividualTarget.png differ
diff --git a/static/img/integration/vision/task/mgrLogFile.png b/static/img/integration/vision/task/mgrLogFile.png
index bf7567e..f63c92a 100644
Binary files a/static/img/integration/vision/task/mgrLogFile.png and b/static/img/integration/vision/task/mgrLogFile.png differ
diff --git a/static/img/integration/vision/task/mgrProgress.png b/static/img/integration/vision/task/mgrProgress.png
index 9b9ed07..ed2b596 100644
Binary files a/static/img/integration/vision/task/mgrProgress.png and b/static/img/integration/vision/task/mgrProgress.png differ
diff --git a/static/img/integration/vision/task/mgrTeamTarget.png b/static/img/integration/vision/task/mgrTeamTarget.png
index ef45618..7392ecd 100644
Binary files a/static/img/integration/vision/task/mgrTeamTarget.png and b/static/img/integration/vision/task/mgrTeamTarget.png differ
diff --git a/static/img/integration/vision/task/mgr_transferOwnership.png b/static/img/integration/vision/task/mgr_transferOwnership.png
new file mode 100644
index 0000000..402a05e
Binary files /dev/null and b/static/img/integration/vision/task/mgr_transferOwnership.png differ
diff --git a/static/img/integration/vision/task/quest.png b/static/img/integration/vision/task/quest.png
deleted file mode 100644
index de510b2..0000000
Binary files a/static/img/integration/vision/task/quest.png and /dev/null differ
diff --git a/static/img/integration/vision/task/questJoinDirect.png b/static/img/integration/vision/task/questJoinDirect.png
index a194903..2896054 100644
Binary files a/static/img/integration/vision/task/questJoinDirect.png and b/static/img/integration/vision/task/questJoinDirect.png differ
diff --git a/static/img/integration/vision/task/questRequiredApprove.png b/static/img/integration/vision/task/questRequiredApprove.png
index dd68554..524f8c2 100644
Binary files a/static/img/integration/vision/task/questRequiredApprove.png and b/static/img/integration/vision/task/questRequiredApprove.png differ
diff --git a/static/img/integration/vision/task/requireJoinPermission.png b/static/img/integration/vision/task/requireJoinPermission.png
new file mode 100644
index 0000000..c52bac2
Binary files /dev/null and b/static/img/integration/vision/task/requireJoinPermission.png differ
diff --git a/static/img/integration/vision/task/teamTarget.png b/static/img/integration/vision/task/teamTarget.png
index 762d593..729a50e 100644
Binary files a/static/img/integration/vision/task/teamTarget.png and b/static/img/integration/vision/task/teamTarget.png differ
diff --git a/static/img/integration/vision/upskill/concept_coursePrivacy_privateCourse.png b/static/img/integration/vision/upskill/concept_coursePrivacy_privateCourse.png
deleted file mode 100644
index 834f68c..0000000
Binary files a/static/img/integration/vision/upskill/concept_coursePrivacy_privateCourse.png and /dev/null differ
diff --git a/static/img/integration/vision/upskill/concept_courseVisibility.png b/static/img/integration/vision/upskill/concept_courseVisibility.png
new file mode 100644
index 0000000..ef84fce
Binary files /dev/null and b/static/img/integration/vision/upskill/concept_courseVisibility.png differ
diff --git a/static/img/integration/vision/upskill/concept_courseVisibility_manageUpskillTab.png b/static/img/integration/vision/upskill/concept_courseVisibility_manageUpskillTab.png
new file mode 100644
index 0000000..6179ed2
Binary files /dev/null and b/static/img/integration/vision/upskill/concept_courseVisibility_manageUpskillTab.png differ
diff --git a/static/img/integration/vision/upskill/mgr_changeLog.png b/static/img/integration/vision/upskill/mgr_changeLog.png
new file mode 100644
index 0000000..742349b
Binary files /dev/null and b/static/img/integration/vision/upskill/mgr_changeLog.png differ
diff --git a/static/img/integration/vision/upskill/mgr_courseTab_othersUpskill.jpg b/static/img/integration/vision/upskill/mgr_courseTab_othersUpskill.jpg
new file mode 100644
index 0000000..096ceba
Binary files /dev/null and b/static/img/integration/vision/upskill/mgr_courseTab_othersUpskill.jpg differ
diff --git a/static/img/integration/vision/upskill/mgr_transferOwnership.png b/static/img/integration/vision/upskill/mgr_transferOwnership.png
new file mode 100644
index 0000000..7f82d78
Binary files /dev/null and b/static/img/integration/vision/upskill/mgr_transferOwnership.png differ
diff --git a/static/img/integration/vision/upskillCreation/step4_ParticipantInfo.png b/static/img/integration/vision/upskillCreation/step4_ParticipantInfo.png
index 62e4f99..fe0e740 100644
Binary files a/static/img/integration/vision/upskillCreation/step4_ParticipantInfo.png and b/static/img/integration/vision/upskillCreation/step4_ParticipantInfo.png differ
diff --git a/static/img/integration/vision/wallet/manager-payout-details.png b/static/img/integration/vision/wallet/manager-payout-details.png
index 0484181..4b19319 100644
Binary files a/static/img/integration/vision/wallet/manager-payout-details.png and b/static/img/integration/vision/wallet/manager-payout-details.png differ
diff --git a/static/img/integration/vision/wallet/manager-payout-emp-details.png b/static/img/integration/vision/wallet/manager-payout-emp-details.png
index 64e745a..20dc57d 100644
Binary files a/static/img/integration/vision/wallet/manager-payout-emp-details.png and b/static/img/integration/vision/wallet/manager-payout-emp-details.png differ
diff --git a/static/img/integration/vision/wallet/payout-details.png b/static/img/integration/vision/wallet/payout-details.png
index 32e25f6..ece64d5 100644
Binary files a/static/img/integration/vision/wallet/payout-details.png and b/static/img/integration/vision/wallet/payout-details.png differ