diff --git a/docs/integration/vision/gift/introduction.md b/docs/integration/vision/gift/introduction.md
index 50cd242..3a9ee5e 100644
--- a/docs/integration/vision/gift/introduction.md
+++ b/docs/integration/vision/gift/introduction.md
@@ -2,10 +2,9 @@
sidebar_position: 1
---
-# Gift Introduction
+# 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.
|||
|:--------------------------------|:--------------------------------|
-
diff --git a/docs/integration/vision/gift/manager.md b/docs/integration/vision/gift/manager.md
index cd05448..59938a0 100644
--- a/docs/integration/vision/gift/manager.md
+++ b/docs/integration/vision/gift/manager.md
@@ -1,63 +1,62 @@
---
-sidebar_position: 3
+sidebar_position: 2
---
-# Manager
+# Manager View
+
:::info[Note]
-These feature is only available to **manager**.
+These features are only available to **manager**.
:::
## Gift Creation
+
:::info[Note]
-After a manager creates a gift, users receive a notification about the new gift.
+After manager creates a gift, users will receive notification regarding the new gift.
:::
-To add a new gift, managers can go to **More icon> Add Gift**.
+
+1. To add a new gift, managers can go to **More icon> Add Gift**.

-### 1. Gift Redemption Details
+2. Gift Redemption Details

| Properties | Description | Note |
|:-----------------------------|:-----------------------------------------------------------------------------------|:--------:|
-| **1.0 Name** | The name of the gift. | Required |
-| **1.1 Description** | A detailed description of the gift. | Required |
-| **1.2 Terms & Conditions** | To specify the rules, requirements, guidelines, and limitations that the user must agree to in order to redeem the gift. | Required |
-| **1.3 Redemption Validity Start Date** | The first date when the gift can be redeemed. | Required |
-| **1.4 Redemption Validity End Date** | The last date when the gift can be redeemed. | Required |
-| **1.5 Clear** | Clears all content on the current page. | - |
-| **1.6 Next** | Navigates to the previous page. | - |
+| **Name** | The name of the gift. | Required |
+| **Description** | A detailed description of the gift. | Required |
+| **Terms & Conditions** | To specify the rules, requirements, guidelines, and limitations that the user must agree to in order to redeem the gift. | Required |
+| **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. | - |
-### 2. Gift Redeemption Criteria
+3. Gift Redemption Criteria

| Properties | Description | Note |
|:-----------------------------|:-----------------------------------------------------------------------------------|:--------:|
-| **2.0 Redeem Coins** | To specify the amount of coins required to redeem the gift. | Required |
-| **2.1 Category** | To select a category to classify the gift, such as Uncategorised, Food & Beverages, Shopping, Service, Entertainment, Digital Goods, or Travel Accommodation. | Required |
-| **2.2 Available Quantity** | To specify the total number of units of the gift that are available for redemption. | Required |
-| **2.3 Max Allowable Redemption Per Employee** | To specify the maximum number of times a user can redeem the gift.| Required |
-| **2.4 Attactment** | To upload an image associated with the gift, such as a product photo or promotional graphic, through the mobile's camera or gallery. | - |
-| **2.5 Clear** | Clears all content on the current page. | - |
-| **2.6 Back** | Navigates to the previous page. | - |
-| **2.7 Create** | To submit and create the new gift entry after filling in all required details. | - |
-
+| **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 |
+| **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. | - |
+| **Back** | Navigates to the previous page. | - |
+| **Create** | To submit and create the new gift entry after filling in all required details. | - |
## 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. Choose Gift
-
-To update a gift, the manager can go to **More icon > Manage Gift** and select the gift want to be update.
|| |
|:------------------------------------|:-----------------------------------------------------|
-### 2. Update Gift Details
-In step 2 of edit mode, the user can update the gift's status using the **"Set as Active"** field.
+2. Update Gift Details - In step 2 of edit mode, the user can update the gift's status using the **"Set as Active"** field.
:::info[Note]
@@ -68,31 +67,32 @@ The **Active** status can only be set if the Redemption Validity End Date is **o
|| |
|:------------------------------------|:-----------------------------------------------------|
-## Gift Issue
+## Gift Issue
-### 1. Choose Gift Issuance Request
+### Choose Gift Issuance Request
The gift can only be issued after the user has redeemed it. To issue a gift, the manager can go to **More icon > Manage Redemption** and select a gift issuance request.
|| |
|:------------------------------------|:-----------------------------------------------------|
-### 2. Confirm Issuance
+### Confirm Issuance
+
After clicking **Issue**, select **Confirm** to complete issuing the gift.
+
|| |
|:------------------------------------|:-----------------------------------------------------|
-### 3. Check Issuance
+### Check Issuance
To check completed issuances, **toggle on Issued Gift**s to display the latest issued gift.
|| |
|:------------------------------------|:-----------------------------------------------------|
-
## Manage Gift
-### 1. Gift Status
+### Gift Status
|Active Gifts|Inactive Gifts |
|:--------------------------------|:---------------------------------|
@@ -100,18 +100,14 @@ To check completed issuances, **toggle on Issued Gift**s to display the latest i
|Propertise|Description|
|:--------------------------------|:--------------------------------|
-|**1.0 Inactive Gifts Switch - Toggle Off**|Displays all active gifts.|
-|**1.1 Deactivate**|Deactivate all currently selected active gifts|
-|**1.2 Inactive Gifts Switch - Toggle On**|Displays all inactive gifts.|
-|**1.3 Active**|Activate all currently selected inactive gifts|
+|**Inactive Gifts Switch - Toggle Off**|Displays all active gifts.|
+|**Deactivate**|Deactivate all currently selected active gifts|
+|**Inactive Gifts Switch - Toggle On**|Displays all inactive gifts.|
+|**Active**|Activate all currently selected inactive gifts|
-### 2. Expired Gift
+### Expired Gift
-The activation will **fail** if the gift has expired. To activate the gift, the manager must [**update**](#2-update-gift-details) its **Redemption Validity End Date**.
+The activation will **fail** if the gift has expired. To activate the gift, the manager must [**update**](#gift-update) its **Redemption Validity End Date**.
|| |
|:------------------------------------|:-----------------------------------------------------|
-
-
-
-
diff --git a/docs/integration/vision/gift/user.md b/docs/integration/vision/gift/user.md
index 011d5a6..baabaac 100644
--- a/docs/integration/vision/gift/user.md
+++ b/docs/integration/vision/gift/user.md
@@ -1,8 +1,8 @@
---
-sidebar_position: 2
+sidebar_position: 3
---
-# User
+# User View
:::info[Note]
@@ -11,7 +11,8 @@ These feature are available to both **manager** and **employee**.
:::
## Gift Redeem
-### 1. Gift Filter Type
+
+1. Gift Filter Type
|Gift Category Filter Chip|Filter Drawer|
|:--------------------------------|:--------------------------------|
@@ -19,21 +20,20 @@ These feature are available to both **manager** and **employee**.
|Propertise|Description|
|:--------------------------------|:--------------------------------|
-|**1.0 Gift Category Filter Chip**|Displays all gifts that match any of the chosen categorie.|
-|**1.1 Clear**| Deselect all the selected filter option.|
-|**1.2 Shop By Price Filter**|Display gifts that match any of the chosen specific price ranges.|
-|**1.3 Sort by Featured**|Display the gifts bassed on popularity in descending order.|
-|**1.4 Sort by Newest**|Display the most recently added gifts in descending order.|
-|**1.5 Sort by Price: High-to-Low**|Display gifts from expensive to cheap.|
-|**1.6 Sort by Price: Low-to-High**|Display gifts from cheap to expensive.|
-|**1.7 Reset**|Select all the filter options again.|
-
-
-### 2. Choose gift
-Choose a gift, and a bottom bar will appear.
+|**Gift Category Filter Chip**|Displays all gifts that match any of the chosen categorie.|
+|**Clear**| Deselect all the selected filter option.|
+|**Shop By Price Filter**|Display gifts that match any of the chosen 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.|
+|**Reset**|Select all the filter options again.|
+
+2. Select gift - After selecting a gift, and a **bottom bar will appear**.
+
:::info[Note]
-Once the gift has expired, it will no longer be displayed for redemption. The manager will need to [**update**](../gift/manager.md#2-update-gift-details) the redemption validity end date to reactivate the gift for future redemptions.
+Once the gift has expired, it will no longer be displayed for redemption. The manager will need to [**update**](../gift/manager.md#gift-update) the redemption validity end date to reactivate the gift for future redemptions.
:::
@@ -42,20 +42,18 @@ Once the gift has expired, it will no longer be displayed for redemption. The ma
|Propertise|Description|
|:--------------------------------|:--------------------------------|
-|**1.0 Validity Duration**|The period during which the gift can be redeemed. The gift will not be available for redemption before or after this period.|
-|**1.1 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.|
-|**1.2 Max Redeem**|The maximum quantity of a gift that a user is allowed to redeem. |
-|**1.3 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.|
-|**1.4 Redeem**|A button to add the selected gift to the gift cart.|
+|**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.|
+|**Redeem**|A button to add the selected gift to the gift cart.|
-### 3. Confirm Redemption
-After clicking **Redeem**, select **Confirm** to confirm. If the redemption is successful, a success dialog will appear automatically.
+3. Confirm Redemption - After clicking **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> MyRedemption**. If a gift shows as **0/1 issued**, it means that **one redemption has been made**, but it **has not yet been issued**.
:::info[Note]
diff --git a/docs/integration/vision/group.md b/docs/integration/vision/group.md
new file mode 100644
index 0000000..7d2e61b
--- /dev/null
+++ b/docs/integration/vision/group.md
@@ -0,0 +1,76 @@
+---
+sidebar_position: 9
+---
+
+# Group
+
+:::info[Note]
+
+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.
+
+## Manage Group
+
+Manager can view all the created groups in **Main Dashboard | Manage Group**. In this page, manager can **search**, **add**, **edit** and **delete** group.
+
+
+
+### Add Group
+
+
+
+1. Tap **Add** to create a new group.
+2. Enter **Group Name**.
+3. Select **Group Members** and their **Roles**.
+4. Tap **Save** 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.
+
+### Delete Group
+
+
+
+1. Swipe **Left** on the group card that you want to delete. Tap **Delete**.
+2. Confirm by tapping **Yes**.
+
+## 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).
+
+
+
+1. Tap **Group** icon.
+2. Select the group that you want to apply. You can select multiple groups.
+3. Tap **Apply**. You will see the selected groups members appear in the list.
+
+
+:::info[Note 1]
+
+When multiple groups are selected, the Roles of duplicated Group Members will be applied according to the **last selected group**.
+
+Example:
+
+- **Group A:** Member A (No Role)
+- **Group B:** Member A (Admin)
+
+1. **Selecting A then B** → Member A becomes **Admin**.
+2. **Selecting B then A** → Member A becomes **No Role**."
+
+:::
+
+:::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**.
+
+:::
\ 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 9a8c253..ce67c52 100644
--- a/docs/integration/vision/linking-to-account.md
+++ b/docs/integration/vision/linking-to-account.md
@@ -1,5 +1,5 @@
---
-sidebar_position: 9
+sidebar_position: 10
---
# Linking to SQL Account
@@ -31,7 +31,7 @@ SQL Vision are linked to SQL Account to get the amount of sales target achieved

-2. Open the dropdown and select the database from the dropdown lsit.
+2. Open the dropdown and select the database from the dropdown list.
3. Insert the user name and password fields with the SQL Accounting Software user name and password.
@@ -67,71 +67,52 @@ The SQL Accounting Software must be open and logged in during the connection pro
## Strategy
-The **Strategy** is a formula that helps managers and the application categorize specific targets for each mission. This setup allows the application to accurately retrieve the target amounts associated with a mission from the SQL Account system.
+The **Strategy** is a formula that helps managers and the application categorize specific targets for each mission. This setup allows the application to accurately retrieve the target amounts associated with a mission from the SQL Account system.
+
+To view the strategy, go to **Main Dashboard | Side Bar | Company Configuration**
:::tip Example Scenario
-
Suppose you’re managing a Sales Department and want to track Q1 sales targets:
-
-
-1. **Assign Strategy to Mission**
- For the mission **"Achieve Q1 Sales Target"**, assign the **"Invoice Based Strategy"** strategy.
-
+1. For the mission **"Achieve Q1 Sales Target"**, assign the **"Invoice Based Strategy"** strategy.
-2. **Automated Target Tracking**
- With this setup, the application will automatically retrieve and update the sales progress daily, based on employee achievements recorded in SQL Account. Managers can view this 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 by mapping to the right Strategy ID. Managers can view the updated progress daily in SQL Vision.
:::
-### 1.0 Pre-defined Strategy
+### Pre-defined Strategy
By default, SQL Vision automatically adds two pre-defined strategies to a newly created company, 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, SQL Vision 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:

-### 1.1 Creating or Editing a Strategy
-
-Coming Soon.
-
-
+1. Click on the strategy you want like to edit.
+2. Edit the strategy name.
+3. Click the **Edit** button.
+4. Click **Save** to apply changes.
+5. Click **Cancel** to discard the changes.
diff --git a/docs/integration/vision/linking-to-payroll.md b/docs/integration/vision/linking-to-payroll.md
index 9f2f7e1..0482233 100644
--- a/docs/integration/vision/linking-to-payroll.md
+++ b/docs/integration/vision/linking-to-payroll.md
@@ -1,5 +1,5 @@
---
-sidebar_position: 10
+sidebar_position: 11
---
# Linking to SQL Payroll
@@ -30,7 +30,7 @@ SQL Vision are linked with SQL Payroll to process all cash rewards earned by emp
:::info[note]
-By default, all rewards will be classified as **Commission**. You can change the payment method by updating the **Payout Code**.
+All rewards will be classified as **Commission** by default. You can change the payment method by updating the **Payout Code**.

@@ -38,7 +38,7 @@ By default, all rewards will be classified as **Commission**. You can change the
:::warning[Warning]
-You are **not 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.md#1---manage-payoutentitlement-page)**.
+- 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.md#1---manage-payoutentitlement-page)**.
:::
diff --git a/docs/integration/vision/login.md b/docs/integration/vision/login.md
index 06205ba..c9e582d 100644
--- a/docs/integration/vision/login.md
+++ b/docs/integration/vision/login.md
@@ -1,33 +1,28 @@
---
+title: Login
+description: A brief guide on logging into the SQL VISION mobile application
sidebar_position: 1
---
-# Login Page
+# Login
-## 1. Login
-
-Enter the user company email address (**highlighed** in red)
+1. Enter the user company email address

-### 1.1 Submit Email
+2. Submit email
-- This button allows user to submit their email
-- Wait to receive an email that include an One-Time Password(OTP)
+ 1. Press **Next**
+ 2. Wait to receive an email that include an One-Time Password(OTP)

-### 1.2 Enter OTP
-
-Enter the OTP (**highlighed** in red)
-
-
-
-### 1.3 Resend OTP
-
-This text button allows user to request again an One-Time Password(OTP)
+3. **Resend OTP** allows user to request again an One-Time Password(OTP)
+
-### 1.4 Verification
+4. Verification
+ 1. Enter the received OTP
+ 2. Press **Log In** to submit the OTP for verification
+ 3. After verification, the user is ready to start using the application
-- This button allows user to submit the OTP for verification
-- After verification, the user is ready to start using the application
+ 
diff --git a/docs/integration/vision/main-dashboard.md b/docs/integration/vision/main-dashboard.md
index d7556c9..a4fcd97 100644
--- a/docs/integration/vision/main-dashboard.md
+++ b/docs/integration/vision/main-dashboard.md
@@ -4,50 +4,57 @@ sidebar_position: 2
# Main Dashboard
+## Quick Action Buttons

-
-
-
-## 1. Quick Action Buttons
-### 1.1 Task:
+### Task
- Display all available quest and tasks assigned to the user.
-### 1.2 Gantt Chart:
+### Upskill
+- Display all available courses and those the user is currently enrolled in.
+
+### Gantt Chart
- Display a visual timeline of tasks and deadlines, allowing the user to track progress across project.
-### 1.3 Wallet:
+### Wallet
- Display cash and coins earned, transaction history and redeem gift.
-### 1.4 Upskill:
-- Display all available courses and those the user is currently enrolled in.
-
-### 1.5 Manage Task:
+### Manage Task
- Allows user to create, edit and update tasks, track task progress and review completed tasks.
-### 1.6 Manage Upskill:
+### Manage Upskill
- Allows user to create, edit and update courses, track course progress and review completed course.
-## 2. Status Card
+### Manage Group
+- Allows user to view, create, edit and delete groups.
+
+## Status Card
+
+
- Displays the count of tasks where:
- 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.
-## 3. Overdue Tasks
+## Overdue Tasks
+
+
- Displays up to 3 tasks that have passed thier deadlines.
-## 4. Undue Tasks
+## Undue Tasks
+
+
- Displays up to 3 tasks that are currently in progress and have not yet reached their deadlines.
-## 5. Earned Card
+## Earned Card
+
- Allows the user to view the cash and coin rewards they are entitled to for the current month or the previous month.
-## 6. Account Setting
+## Account Setting

-### 6.1 Personal Information
+### Personal Information
- Displays the user's profile information in the company payroll system, organized into sections for general details, employment grouping and family information.

@@ -55,7 +62,7 @@ sidebar_position: 2
Details are **view-only** and **cannot be edited** or **modified** from the mobile application.
:::
-### 6.2 Company Configuration (Manager)
+### 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).
@@ -64,17 +71,17 @@ Details are **view-only** and **cannot be edited** or **modified** from the mobi
*This function is accessible only to users with manager permissions.*
:::
-### 6.3 Switch Company
+### Switch Company
- Displays a list of companies the user is enrolled in, allowing them to switch between different company accounts.

-### 6.4 Help
+### Help
- Directs the user to the company website for support resources and guides.
-### 6.5 Logout
+### Logout
- Logs the user out of the application, ending the current session and returning them to the login screen.
-## 7. Log File Review
+## 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
diff --git a/docs/integration/vision/task.md b/docs/integration/vision/task.md
deleted file mode 100644
index 77b9bcc..0000000
--- a/docs/integration/vision/task.md
+++ /dev/null
@@ -1,294 +0,0 @@
----
-sidebar_position: 4
----
-
-# Task
-
-## User View
- User view is for employees who will accomplish the task.
-
-### 1. Target
- Users can view the target detail such as title, task creator, description, start date, end date, strategy, rewards, and ranking.
-
- :::note Note
-
- Team task will only **visible** for team leader.
-
- :::
-
- :::info Info
-
- 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)
-
- :::
-
- | Individual | Team |
- |-----------------------------------------------------------|----------------------------------------------|
- |  | |
-
-### 2. Assignment
- Users can view the assignment detail such as title, description, start date, end date, consultant, rewards, bonus criteria, and other progress.
-
- :::info Info
-
- **Consultant**: responsible for providing expert guidance to the user in completing the task.
-
- :::
-
- :::note Note
-
- The bonus will only be available when the log file's percentage reaches **100%**.
-
- :::
-
- 
-
-### 2.1 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).
-
- :::tip Tips
-
- - The percentage displayed in the chat bubble corresponds to the rewards section.
- - The progress bar displays the user's completion percentage.
-
- :::
-
-### 2.2 Progress Tracker
-
- - This button allows user to view his submitted log file and milestone reward obtained.
-
- 
- Indicates the log file is in **Pending** status
-
- 
- Indicates the log file is in **Approved** status
-
- - The rewards are entitled once the **approved** log file percentage is achieved.
-
- 
-
-### 2.3 Update Log File
- This button 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.
-
- 
-
-### 2.4 Submission Bonus Request
- Users are allowed to submit bonus request by choosing the bonus criteria and add on remark.
-
- :::note Note
-
- This form is only available when the log file submission is **100%**.
-
- :::
-
-
- :::warning Alert
-
- Bonus request can only be submitted once.
-
- :::
-
- 
-
-### 3. Quest
- - 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**](#1-target) or [**Assignment**](#2-assignment)
-
- :::warning Alert
-
- After joining, users **cannot** quit the task.
-
- :::
-
- 
-
-## Manager View
- Manager view is for users who will assigned the task to employee.
-
-### 1. Target (Manager)
- 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.
-
- | Individual | Team |
- |-------------------------------------------------------------|-------------------------------------------------|
- | | |
-
-### 1.1 Employee Progress Card
- This button allows the manager to view employee's target info
-
- | Individual | Team |
- |--------------------------------------------------------|-------------------------------------------|
- |  | |
-
-### 1.2 Edit
- This button allows the manager to edit the target details.
-
- For more information, please refer [**Edit Task**](task_creation/task-edit.md)
-
- 
-
-### 2. Assignment (Manager)
- Managers can view the assignment detail that are created such as title, description, start date, end date, consultant, rewards, and bonus criteria.
-
- | Undue/Overdue | Completed |
- |--------------------------------------------------------------|----------------------------------------------------------|
- |  | |
-
-### 2.1 Progress
- This button allows manager to view the progress of each employee.
-
- :::note Note
-
- **Progress** tab bar: Display the employee that are still havent reached **100%**.
-
- **Completed** tab bar: Display the employee that reached **100%**.
-
- :::
-
- 
-
-### 2.2 Log File
- This button allows the manager to view all unapproved log files submitted by employees.
-
- 
-
-### 2.3 Edit
- This button allows the manager to edit the assignment details.
-
- For more information, please refer [**Edit Task**](task_creation/task-edit.md)
-
- 
-
-### 2.4 Finalize
- - This button allows the manager to finalize assignment.
-
- - To finalize assignment, all log file should be **approve**.
-
- - After finalizing, consultant reward will be entitled.
-
- :::danger Warning
-
- Finalizing assignment is an **irreversible** action.
-
- :::
-
- 
-
-### 2.5 Employee Progress Card
- - This button allows manager to view employee's assignment info.
-
- - (**Highlighted in red**) The total cash and coin(s) earned by the employee in this assignment.
-
- 
-
-### 2.6 Log File Card
- This button allows the manager to view the log file details submitted by employee.
-
- 
-
-### 2.7 Log File Override
- This button allows the manager to 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.
- :::
-
- 
-
-### 2.8 Approve Log File
- - This button allows the manager to approve the employee's log file.
-
- - After approving, manager can view the bonus request submitted by the employee.
-
- :::note Note
-
- - 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**)
-
- :::
-
-
-
-### 2.9 Edit Bonus
- - This button allows the manager to edit the bonus request from the employee.
-
- - Managers can choose the bonus criteria, and edit the amount.
-
- :::note Note
-
- - Edit amount cannot **exceed** the maximum amount as shown.
- - Manager can **edit** maximum amount in the [**Edit**](#23-edit) section.
-
- :::
-
- 
-
-### 2.10 Reward Info
- This info button allows user to view the milestone and bonus rewards in the dialog.
-
- :::info Info
- The code will matches with the code in the summary table.
- :::
-
- 
-
-### 2.11 Employee
- Managers can click the employee's name to view the employee's assignment info.
-
- 
-
-### 2.12 Tooltip Reward
- Managers can click the total cash and coins to view the earned amounts for the corresponding employee in the tooltip.
-
- :::info Info
- The code will matches with the code in the summary table.
- :::
-
- 
-
-### 2.13 Employee Log File
- This button allows the manager to view all the log file submitted by the employee.
-
- 
-
-### 2.14 Change Log
- This button allows the manager to view the mission's change log, including details of who made edits and what changes were made.
-
- 
-
-### 3. Quest (Manager)
- Quest detail will be same as the assignment or target details based on whether it's a target or assignment quest.
-
- For more information, can refer as below:
- - [**Target**](#1-target-manager)
- - [**Assignment**](#2-assignment-manager)
-
- | Approval Required | No Approval Required |
- |---------------------------------------------------------------------------|----------------------------------------------------------------|
- |  | |
-
-### 3.1 Manage Participant
- - Filter menu on right top allows the manager to filter the employee by branch, department, and HR group.
-
- | View | Filter |
- |---------------------------------------------------------------------------|--------------------------------------------------------|
- |  | |
-
-### 3.2 Delete Request Employee
- This button allows manager to delete the request of employee for joining the quest
-
-### 3.3 Approve Request Employee
- This button allows manager to approve the request of employee for joining the quest
\ No newline at end of file
diff --git a/docs/integration/vision/task/_category_.json b/docs/integration/vision/task/_category_.json
new file mode 100644
index 0000000..b7ab81f
--- /dev/null
+++ b/docs/integration/vision/task/_category_.json
@@ -0,0 +1,8 @@
+{
+ "label": "Task",
+ "position": 3,
+ "link": {
+ "type": "generated-index",
+ "description": "Guidance to Task Module in SQL Vision."
+ }
+ }
\ No newline at end of file
diff --git a/docs/integration/vision/task/introduction.md b/docs/integration/vision/task/introduction.md
new file mode 100644
index 0000000..bd503a0
--- /dev/null
+++ b/docs/integration/vision/task/introduction.md
@@ -0,0 +1,16 @@
+---
+sidebar_position: 1
+---
+
+# Introduction
+
+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..
+
+- **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.
+
+- **Quest:**
+ A Quest is used when you’re unsure who to assign a task to or want to invite all employees to participate.
diff --git a/docs/integration/vision/task/manager_view/_category_.json b/docs/integration/vision/task/manager_view/_category_.json
new file mode 100644
index 0000000..56ff9d6
--- /dev/null
+++ b/docs/integration/vision/task/manager_view/_category_.json
@@ -0,0 +1,8 @@
+{
+ "label": "Manager View",
+ "position": 3,
+ "link": {
+ "type": "generated-index",
+ "description": "Manager view is for users who will assigned the task to employee. "
+ }
+}
\ No newline at end of file
diff --git a/docs/integration/vision/task/manager_view/assignment.md b/docs/integration/vision/task/manager_view/assignment.md
new file mode 100644
index 0000000..89dc15b
--- /dev/null
+++ b/docs/integration/vision/task/manager_view/assignment.md
@@ -0,0 +1,143 @@
+---
+title: Assignment
+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.
+
+| Undue/Overdue | Completed |
+|--------------------------------------------------------------|----------------------------------------------------------|
+|  | |
+
+## Undue & Overdue
+
+### Edit Assignment Detail
+1. Press **Edit** in assignment detail
+ - 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%**.
+
+**Completed** tab bar: Display the employee that reached **100%**.
+
+:::
+
+2. Display employee's assignment detail:
+ - 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.
+
+
+
+2. Manager can view the log file details as shown.
+ - 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.
+:::
+
+
+
+### 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%**.
+- The colored bonus card represents the bonus requested by the employee. (**highlighted in red**)
+
+:::
+
+
+
+### 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.
+
+:::note Note
+
+- Edit amount cannot **exceed** the maximum amount as shown.
+- Manager can **edit** maximum amount in the [**Edit**](#23-edit) section.
+
+:::
+
+
+
+### Change Log
+1. Press **History Icon** (highlighted in red)
+ - 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.
+
+:::danger Warning
+
+Finalising assignment is an **irreversible** action.
+
+:::
+
+
+
+## Completed
+
+### Reward Info
+1. Press **Info Icon** (highlighted in red)
+
+
+
+2. User can view the milestone and bonus rewards
+
+
+
+:::info Info
+ The code will matches 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**
+
+
+
+### Tooltip Reward
+1. Click **Total Cash Amount** / **Total Coin Amount**
+ - can view 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
new file mode 100644
index 0000000..2369316
--- /dev/null
+++ b/docs/integration/vision/task/manager_view/quest.md
@@ -0,0 +1,34 @@
+---
+title: Quest
+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.
+
+For more information, can refer as below:
+- [**Target**](target.md)
+- [**Assignment**](assignment.md)
+
+| Approval Required | No Approval Required |
+|---------------------------------------------------------------------------|----------------------------------------------------------------|
+|  | |
+
+### Manage Participant
+1. Press **Add People Icon** (highlighted in red)
+
+
+
+2. Filter menu on right top allows the manager to filter the employee by branch, department, and HR group.
+
+| View | Filter |
+|---------------------------------------------------------------------------|--------------------------------------------------------|
+|  | |
+
+### Delete Request Employee
+1. Press **Delete**
+ - allows manager to delete the request of employee for joining the quest
+
+### Approve Request Employee
+1. Press **Approve**
+ - allows manager to approve the request of employee for joining 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
new file mode 100644
index 0000000..0b3f38a
--- /dev/null
+++ b/docs/integration/vision/task/manager_view/target.md
@@ -0,0 +1,26 @@
+---
+title: Target
+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.
+
+| Individual | Team |
+|-------------------------------------------------------------|-------------------------------------------------|
+| | |
+
+### Employee Progress
+1. Press **Employee Card** (highlighted in red)
+
+
+
+| Individual | Team |
+|--------------------------------------------------------|-------------------------------------------|
+|  | |
+
+### Edit
+1. Press **Edit**
+ - For more information, please refer [**Edit Task**](task_creation/task-edit)
+
+
\ No newline at end of file
diff --git a/docs/integration/vision/task/manager_view/task_creation/_category_.json b/docs/integration/vision/task/manager_view/task_creation/_category_.json
new file mode 100644
index 0000000..a56878a
--- /dev/null
+++ b/docs/integration/vision/task/manager_view/task_creation/_category_.json
@@ -0,0 +1,8 @@
+{
+ "label": "Task Creation",
+ "position": 1,
+ "link": {
+ "type": "generated-index",
+ "description": "Guidance to create and edit Assignment and Target mission in SQL Vision."
+ }
+ }
\ No newline at end of file
diff --git a/docs/integration/vision/task/manager_view/task_creation/assignment.md b/docs/integration/vision/task/manager_view/task_creation/assignment.md
new file mode 100644
index 0000000..5a2b1fb
--- /dev/null
+++ b/docs/integration/vision/task/manager_view/task_creation/assignment.md
@@ -0,0 +1,144 @@
+---
+sidebar_position: 2
+---
+
+# Create Assignment
+
+Assignment is a qualitative mission (non-countable). E.g. Idea brainstorm, Clothes design.
+
+:::info[Note]
+
+This feature is only available to **manager**.
+
+:::
+
+## Step 1 - Assignment Information
+
+
+
+
+| Properties | Description | Note |
+|:-------------------------|:-----------------------------------------------------------------------------------|:--------:|
+| **Title** | The title of the mission. | Required |
+| **Description** | A detailed description of the mission. | Required |
+| **[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 |
+| **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.
+
+
+
+## Step 2 - Milestone and Rewards
+
+
+
+| 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 |
+| **[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. | - |
+| **Back** | Navigates to the previous page. | - |
+| **Next** | Navigates to the next page. | - |
+
+### Milestone and Rewards
+
+
+
+
+| 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). |
+| **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. |
+
+### Consultant Rewards
+
+
+
+**Consultants** are employees responsible for providing guidance on a particular mission. They 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.
+
+
+
+### Payment By
+
+:::info[Note]
+
+The payment method applies only to **Cash**. All coins will be paid immediately upon entitlement.
+
+:::
+
+
+
+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.
+
+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.
+
+### Bonus
+
+
+
+| Properties | Description |
+|---------------|-------------------------------------------------------------------------------------|
+| **Description** | Text field to input a description of 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. |
+
+
+## Step 3 - Add Members
+
+There are 4 combination of members that can be created in Assignment:
+
+1. **Normal member:**
+ An employee who performs the mission without a specific management or advisory role.
+
+2. **Admin:**
+ An employee authorized to manage the task but does not complete the mission themselves. Admin shall not be entitled to any reward.
+
+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.
+
+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.
+
+
+
+| 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). |
+| **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:
+
+- Branch
+- Department
+- HR Group
diff --git a/docs/integration/vision/task/manager_view/task_creation/duplication.md b/docs/integration/vision/task/manager_view/task_creation/duplication.md
new file mode 100644
index 0000000..72ec42e
--- /dev/null
+++ b/docs/integration/vision/task/manager_view/task_creation/duplication.md
@@ -0,0 +1,44 @@
+---
+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.
+
+:::info[Note]
+
+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.
+
+
+
+-  representing as **Target**
+-  representing as **Assignment**
+-  representing as **Quest**
+
+## 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
+
+**Type:**
+- Assignment
+- Target
+- 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
diff --git a/docs/integration/vision/task/manager_view/task_creation/quest.md b/docs/integration/vision/task/manager_view/task_creation/quest.md
new file mode 100644
index 0000000..70e26a1
--- /dev/null
+++ b/docs/integration/vision/task/manager_view/task_creation/quest.md
@@ -0,0 +1,24 @@
+---
+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**.
+
+:::info[Note]
+
+This feature is only available to **manager**.
+
+:::
+
+
+
+| Properties | Description |
+|:--------------------------|:------------------------------------------------------------------------------|
+| **Maximum Pax** | The maximum number of people allowed to join the quest. |
+| **Join Permission** | Sets whether the quest requires manager approval to join. |
+| **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_creation/target.md b/docs/integration/vision/task/manager_view/task_creation/target.md
similarity index 58%
rename from docs/integration/vision/task_creation/target.md
rename to docs/integration/vision/task/manager_view/task_creation/target.md
index ab9b58e..6b343cf 100644
--- a/docs/integration/vision/task_creation/target.md
+++ b/docs/integration/vision/task/manager_view/task_creation/target.md
@@ -2,7 +2,7 @@
sidebar_position: 3
---
-# Target
+# Create Target
Target is a quantitative mission (countable data). E.g. Sales Target, Total new users.
@@ -14,35 +14,36 @@ This feature is only available to **manager**.
## Step 1 - Target Details
-
+
| Properties | Description | Note |
|:-----------------------------|:-----------------------------------------------------------------------------------|:--------:|
-| **1.1 Title** | The title of the mission. | Required |
-| **1.2 Description** | A detailed description of the mission. | Required |
-| **1.3 Start Date** | The date when the mission begins. The start date must be today or a future date. | Required |
-| **1.4 End Date** | The date when the mission ends. The end date must be later than the start date. | Required |
-| **1.5 Clear** | Clears all content on the current page. | - |
-| **1.6 Next** | Navigates to the next page. | - |
+| **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 |
+| **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
-
+
-| Properties | Description | Note |
-|:-------------------------------------------|:-----------------------------------------------------------------------------------------|:------------:|
-| **[2.1 Grouping Type](#21-grouping-type)** | Section to select the target grouping type, either *Individual* or *Team*. | Required |
-| **[2.2 Strategy](#22-strategy)** | Section to select the target strategy, with options predefined in Company Configuration. | Required |
-| **[2.3 Condition](#23-condition)** | Section to select the target condition, such as *Between* or *More than*. | Required |
-| **[2.4 Target and Rewards](#24-target-and-rewards)**| Section to enter details about the targets and their associated rewards. | At least one |
-| **[2.5 Payment By](#25-payment-by)** | Section to select the payment method and specify the payout month. | Required |
-| **2.6 Clear** | Clears all content on the current page. | - |
-| **2.7 Back** | Navigates to the previous page. | - |
-| **2.8 Next** | Navigates to the next page. | - |
-### 2.1 Grouping Type
+| 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 |
+| **[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. | - |
+| **Back** | Navigates to the previous page. | - |
+| **Next** | Navigates to the next page. | - |
-
+### Grouping Type
+
+
There are two types of **Grouping Types**:
@@ -71,27 +72,25 @@ To set up a team target, create two identical missions: one with the **Individua
:::
-### 2.2 Strategy
+### Strategy
-
+
-**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 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).
:::tip Example Scenario
Suppose you’re managing a Sales Department and want to track Q1 sales targets:
-1. **Assign Strategy to Mission**
- For the mission **"Achieve Q1 Sales Target"**, assign the **"Invoice Based Strategy"** strategy.
+1. For the mission **"Achieve Q1 Sales Target"**, assign the **"Invoice Based Strategy"** strategy.
-2. **Automated Target Tracking**
- With this setup, the application will automatically retrieve and update the sales progress daily, based on employee achievements recorded in SQL Account. Managers can view this 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 by mapping to the right Strategy ID. Managers can view the updated progress daily in SQL Vision.
:::
-### 2.3 Condition
+### Condition
-
+
**Condition** specifies the criteria for calculating target rewards.
@@ -104,9 +103,7 @@ The "Between" condition is designed to allocate rewards based on an employee’s
It is essential to ensure the upper limit (Y) of one target matches the lower limit (X) of the subsequent target to ensure continuity and avoid gaps.
-Example:
-
-
+
1. If an employee achieves **RM15,000**, the employee will fall in **Target 1** and receive **2%** reward.
2. If an employee achieves **RM25,000**, the employee will fall in **Target 2** and receive **3%** reward.
@@ -118,9 +115,7 @@ The "More Than" condition is used to grant rewards when an employee surpasses a
- Each reward is granted only **once**, regardless of how far the employee's achievement exceeds the target.
- Achieving a higher target **excludes rewards for lower targets**, ensuring that only the highest applicable reward is granted.
-Example:
-
-
+
1. If an employee achieves **RM15,000**, they will receive **2%** reward because their achievement **exceeds RM10,000 but does not surpass RM20,000**.
2. If an employee achieves **RM25,000**, they will receive **3%** reward because their achievement **exceeds RM20,000**, which excludes the reward for the lower target (2% Reward).
@@ -132,9 +127,7 @@ The "Less Than" condition is designed to grant rewards when an employee achieves
- Each reward is granted only **once**, based on the smallest qualifying target achieved.
- Achieving a lower target amount **excludes rewards for higher targets**.
-Example:
-
-
+
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.
@@ -146,9 +139,7 @@ The "More Than and Equal" condition grants rewards when an employee’s achievem
- Each reward is granted only **once**, corresponding to the highest applicable target achieved.
- Achieving a higher target automatically **excludes rewards for lower targets**.
-Example:
-
-
+
1. If an employee achieves **5 new customers**, they will receive **RM1,000 & 5,000 coins** because their achievement is **5 or more customers** but does not meet the next threshold of 10 or more customers.
2. If an employee achieves **12 new customers**, they will receive **RM3,000 and 10,000 coins** because their achievement is **10 or more customers**, which excludes first target rewards.
@@ -160,37 +151,24 @@ The "Less Than and Equal" condition is applied to reward employees who achieve r
- Each reward is granted only **once**, based on the smallest qualifying target achieved.
- Achieving a smaller target automatically **excludes rewards for higher targets**.
-Example:
-
-
+
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.
-### 2.4 Target and Rewards
-
-
+### Target and Rewards
-#### 2.4.1 Target
- - Text field to input the target amount. (Note: Only the **Between** condition will have two text fields.)
+
-#### 2.4.2 Reward
- - Text field to enter the rewards available to the achievers of the particular target.
- - There are 3 types of rewards:
- - **Percentage (%):**
- A percentage of the target amount awarded to the members (e.g., 2%).
- - **Cash (RM):**
- Commission or allowance provided through the SQL Account on the payout date.
- - **Coins:**
- Digital coins that can be used to redeem gifts in SQL Vision via [**Gift**](../gift/introduction.md).
-#### 2.4.3 Add
- - Adds a new target along with its respective rewards.
+| 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). |
+| **Add** | Adds a new target along with its respective rewards. |
+| **Delete** | Deletes a specific target and its associated rewards. |
-#### 2.4.4 Delete
- - Deletes a specific target and its associated rewards.
-
-### 2.5 Payment By
+### Payment By
:::info[Note]
@@ -198,7 +176,7 @@ The payment method applies only to **Cash**. All coins will be paid immediately
:::
-
+
There are two types of payment methods:
@@ -229,23 +207,14 @@ There are 4 combination of members that can be created in Target:
All 4 combinations can be created in **[Add Members](#step-3---add-members)** in Step 3.
-
-
-| Properties | Description |
-|:----------------------------|:-------------------------------------------------------------------------|
-| **3.1 Search** | Allows you to search for employees by their names. |
-| **[3.2 Filter](#32-filter)**| Allow you to filter and sort the employee list. |
-| **3.3 Select All** | Allow you to select all employees at once. |
-| **3.4 Make Quest** | Converts your mission into a Quest. See more in [**quest**](quest). |
-| **3.5 Back** | Navigates to the previous page. |
-| **3.6 Create** | Creates the mission. |
-
-#### 3.2 Filter
-
-
-
-The employee list can be filtered and sort by:
-
-- Branch
-- Department
-- HR Group
\ No newline at end of file
+
+
+| 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. |
+| **Make Quest** | Converts your mission into a Quest. See more in [**quest**](quest). |
+| **Back** | Navigates to the previous page. |
+| **Create** | Creates the mission. |
\ 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
new file mode 100644
index 0000000..f67e986
--- /dev/null
+++ b/docs/integration/vision/task/manager_view/task_creation/task-creation.md
@@ -0,0 +1,30 @@
+---
+sidebar_position: 1
+---
+
+# Create a Mission
+
+:::info[Note]
+This feature is only available to **manager**.
+:::
+
+To create a new mission, navigate to **Main Dashboard | Manage Task**. Click the **Add Button** located at the bottom right corner of the app.
+
+
+
+
+### Duplicate Existing
+
+In this section, you can view all previously created missions, including those that have been deleted.
+
+- [**Duplication**](duplication)
+
+### Create New
+
+In this section, you can create a new mission from scratch, choosing either Assignment or Target.
+
+- [**Assignment**](assignment)
+- [**Target**](target)
+
+
+
diff --git a/docs/integration/vision/task_creation/task-edit.md b/docs/integration/vision/task/manager_view/task_creation/task-edit.md
similarity index 80%
rename from docs/integration/vision/task_creation/task-edit.md
rename to docs/integration/vision/task/manager_view/task_creation/task-edit.md
index 8ba8326..1aa7017 100644
--- a/docs/integration/vision/task_creation/task-edit.md
+++ b/docs/integration/vision/task/manager_view/task_creation/task-edit.md
@@ -10,9 +10,9 @@ This feature is only available to **manager** and **admin**.
:::
-To edit a mission, go to **Main Dashboard > Manage Task > press on a mission card > press Edit Button**.
+To edit a mission, go to **Main Dashboard | Manage Task | press on a mission card | press Edit Button**.
-
+
## Edit Permission
@@ -28,6 +28,6 @@ There are certain conditions for editing a mission, as stated in the table below
#### Non-editable Field
-To clearly identify the non-editable fields, they will be greyed out, as shown in the picture.
+The non-editable fields will be greyed out as shown in the picture below.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/docs/integration/vision/task/user_view/_category_.json b/docs/integration/vision/task/user_view/_category_.json
new file mode 100644
index 0000000..ab01e6a
--- /dev/null
+++ b/docs/integration/vision/task/user_view/_category_.json
@@ -0,0 +1,8 @@
+{
+ "label": "User View",
+ "position": 4,
+ "link": {
+ "type": "generated-index",
+ "description": "User view is for employees who will accomplish the task."
+ }
+ }
\ No newline at end of file
diff --git a/docs/integration/vision/task/user_view/assignment.md b/docs/integration/vision/task/user_view/assignment.md
new file mode 100644
index 0000000..0e9b022
--- /dev/null
+++ b/docs/integration/vision/task/user_view/assignment.md
@@ -0,0 +1,70 @@
+---
+title: Assignment
+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.
+
+:::info Info
+
+**Consultant**: responsible for providing expert guidance to the user in completing the task.
+
+:::
+
+:::note Note
+
+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).
+
+
+
+:::tip Tips
+
+- The percentage displayed in the chat bubble corresponds to the rewards section.
+- The progress bar displays the user's completion percentage.
+
+:::
+
+### Progress Tracker
+1. Press **Progress Tracker**
+ - user can view his/her submitted log file and milestone reward obtained.
+
+
+
+
+Indicates the log file is in **Pending** status
+
+
+Indicates the log file is in **Approved** status
+
+
+
+### 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.
+
+
+
+### 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.
+
+
+:::warning Alert
+
+Bonus request can only be submitted once.
+
+:::
+
+
diff --git a/docs/integration/vision/task/user_view/quest.md b/docs/integration/vision/task/user_view/quest.md
new file mode 100644
index 0000000..a9fc519
--- /dev/null
+++ b/docs/integration/vision/task/user_view/quest.md
@@ -0,0 +1,19 @@
+---
+title: Quest
+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)
+
+:::warning Alert
+
+After joining, users **cannot** quit the task.
+
+:::
+
+
diff --git a/docs/integration/vision/task/user_view/target.md b/docs/integration/vision/task/user_view/target.md
new file mode 100644
index 0000000..6895d7e
--- /dev/null
+++ b/docs/integration/vision/task/user_view/target.md
@@ -0,0 +1,27 @@
+---
+title: Target
+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.
+
+:::note Note
+
+Team task will only **visible** for team leader.
+
+:::
+
+:::info Info
+
+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)
+
+:::
+
+| Individual | Team |
+|-----------------------------------------------------------|----------------------------------------------|
+|  | |
\ No newline at end of file
diff --git a/docs/integration/vision/task_creation/_category_.json b/docs/integration/vision/task_creation/_category_.json
deleted file mode 100644
index 884be59..0000000
--- a/docs/integration/vision/task_creation/_category_.json
+++ /dev/null
@@ -1,8 +0,0 @@
-{
- "label": "Task Creation/Edit",
- "position": 3,
- "link": {
- "type": "generated-index",
- "description": "Guidance to create Assignment and Target mission in SQL Vision."
- }
- }
\ No newline at end of file
diff --git a/docs/integration/vision/task_creation/assignment.md b/docs/integration/vision/task_creation/assignment.md
deleted file mode 100644
index b730ef0..0000000
--- a/docs/integration/vision/task_creation/assignment.md
+++ /dev/null
@@ -1,171 +0,0 @@
----
-sidebar_position: 2
----
-
-# Assignment
-
-Assignment is a qualitative mission (non-countable). E.g. Idea brainstorm, Clothes design.
-
-:::info[Note]
-
-This feature is only available to **manager**.
-
-:::
-
-## Step 1 - Assignment Details
-
-
-
-
-| Properties | Description | Note |
-|:-----------------------------|:-----------------------------------------------------------------------------------|:--------:|
-| **1.1 Title** | The title of the mission. | Required |
-| **1.2 Description** | A detailed description of the mission. | Required |
-| **[1.3 Project/Job/Task](#13-projectjobtask)** | The category for the mission, indicating whether it relates to a project, job, or specific task. | - |
-| **1.4 Start Date** | The date when the mission begins. The start date must be today or a future date. | Required |
-| **1.5 End Date** | The date when the mission ends. The end date must be later than the start date. | Required |
-| **1.6 Clear** | Clears all content on the current page. | - |
-| **1.7 Next** | Navigates to the next page. | - |
-
-### 1.3 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.
-
-
-
-## Step 2 - Milestone and Rewards
-
-
-
-| Properties | Description | Note |
-|:----------------------------------------------------|:--------------------------------------------------------------------------|:------------:|
-| **[2.1 Milestone and Rewards](#21-milestone-and-rewards)** | Section for entering details about milestones and associated rewards. | At least one |
-| **[2.2 Consultant Rewards](#22-consultant-rewards)**| Section for selecting consultants and specifying their respective rewards.| Required |
-| **[2.3 Payment By](#23-payment-by)** | Section for selecting the payment method and specifying the payout month. | Required |
-| **[2.4 Bonus](#24-bonus)** | Section for entering additional bonus rewards. | - |
-| **2.5 Clear** | Clears all content on the current page. | - |
-| **2.6 Back** | Navigates to the previous page. | - |
-| **2.7 Next** | Navigates to the next page. | - |
-
-### 2.1 Milestone and Rewards
-
-
-
-#### 2.1.1 Milestones X
- - Text field to input the percentage of the milestone (e.g., 20%, 100%).
-
-#### 2.1.2 Description
- - Text field to input the description of the milestone (e.g., the requirements to achieve the particular milestone).
-
-#### 2.1.3 Rewards
- - Text field to enter the rewards available to the achievers of the particular milestone.
- - There are 2 types of rewards:
- - **Cash (RM):**
- Commission or allowance provided through the SQL Account on the payout date.
- - **Coins:**
- Digital coins that can be used to redeem gifts in SQL Vision via [**Gift**](../gift/introduction.md).
-
-#### 2.1.4 Add
- - Adds a new milestone along with its respective rewards.
-
-#### 2.1.5 Delete
- - Deletes a specific milestone and its associated rewards.
-
-### 2.2 Consultant Rewards
-
-**Consultants** are employees responsible for providing guidance on a particular mission. They do not complete the mission themselves.
-
-
-
-#### 2.2.1 Consultants
- - A list of consultants associated with the specific rewards.
-
-#### 2.2.2 Add Consultant
- - Button to add a consultant, which navigates to the Select Consultant page.
-
- 
-
- - Press on an employee to designate them as a consultant.
- - To make a consultant an Admin as well, long-press on the employee to view a pop-up menu and select Add Admin.
-
-#### 2.2.3 Add
- - Adds a new consultant reward.
-
-#### 2.2.4 Delete
- - Deletes a specific reward along with its associated consultants.
-
-### 2.3 Payment By
-
-:::info[Note]
-
-The payment method applies only to **Cash**. All coins will be paid immediately upon entitlement.
-
-:::
-
-
-
-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.
-
-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.
-
-### 2.4 Bonus
-
-
-
-#### 2.4.1 Description
- - Text field to input a description of the bonus (e.g., extra points that you hope the employee can achieve, though it is not mandatory).
-
-#### 2.4.2 Rewards
- - Text field to enter the rewards available to the achievers of the particular bonus.
-
-#### 2.4.3 Add
- - Adds a new bonus along with its respective rewards.
-
-#### 2.4.4 Delete
- - Deletes a specific bonus and its associated rewards.
-
-## Step 3 - Add Members
-
-There are 4 combination of members that can be created in Assignment:
-
-1. **Normal member:**
- An employee who performs the mission without a specific management or advisory role.
-
-2. **Admin:**
- An employee authorized to manage the task but does not complete the mission themselves. Admin shall not be entitled to any reward.
-
-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.
-
-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](#22-consultant-rewards)** in Step 2.
-
-
-
-| Properties | Description |
-|:----------------------------|:-------------------------------------------------------------------------|
-| **3.1 Search** | Allows you to search for employees by their names. |
-| **[3.2 Filter](#32-filter)**| Allow you to filter and sort the employee list. |
-| **3.3 Select All** | Allow you to select all employees at once. |
-| **3.4 Make Quest** | Converts your mission into a Quest. See more in [**quest**](quest.md). |
-| **3.5 Back** | Navigates to the previous page. |
-| **3.6 Create** | Creates the mission. |
-
-#### 3.2 Filter
-
-
-
-The employee list can be filtered and sort by:
-
-- Branch
-- Department
-- HR Group
diff --git a/docs/integration/vision/task_creation/duplication.md b/docs/integration/vision/task_creation/duplication.md
deleted file mode 100644
index adfcf11..0000000
--- a/docs/integration/vision/task_creation/duplication.md
+++ /dev/null
@@ -1,52 +0,0 @@
----
-sidebar_position: 5
----
-
-# Duplication
-
-:::info[Note]
-
-This feature is only available to **manager**.
-
-:::
-
-
-
-## 1. **Back Button**
-
-This button will direct you back to [**Manage Task**](../task.md) page.
-
-## 2. **Filter**
-
-This button allow you to filter your recent mission. The duplicated mission can be filtered by Status and Type:
-
-**Status:**
-- Show only deleted
-
-**Type:**
-- Assignment
-- Target
-- Quest Assignment
-- Quest Target
-
-
-
-### 2.1 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.
-
-
-
-## 3. **Search**
-
-The search allow you to search for your desired mission according to the mission title.
-
-## 4. **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.
-
-
-
-- `1` Icon representing as **Target**
-- `2` Icon representing as **Assignment**
-- `3` Badge representing as **Quest**
\ No newline at end of file
diff --git a/docs/integration/vision/task_creation/quest.md b/docs/integration/vision/task_creation/quest.md
deleted file mode 100644
index bbd314b..0000000
--- a/docs/integration/vision/task_creation/quest.md
+++ /dev/null
@@ -1,24 +0,0 @@
----
-sidebar_position: 4
----
-
-# 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**.
-
-:::info[Note]
-
-This feature is only available to **manager**.
-
-:::
-
-
-
-| Properties | Description |
-|:--------------------------|:------------------------------------------------------------------------------|
-| **1 Maximum Pax** | The maximum number of people allowed to join the quest. |
-| **2 Join Permission** | Sets whether the quest requires manager approval to join. |
-| **3 Quest Visible By** | Specifies which Branch, Department, or HR Group can view and join the quest. |
-| **4 Back to Normal Task** | Converts your mission into normal mission. See more in [**assignment**](assignment) and [**target**](target) |
-| **5 Back** | Navigates to the previous page. |
-| **6 Create** | Creates the quest. |
diff --git a/docs/integration/vision/task_creation/task-creation.md b/docs/integration/vision/task_creation/task-creation.md
deleted file mode 100644
index 41bea90..0000000
--- a/docs/integration/vision/task_creation/task-creation.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-sidebar_position: 1
----
-
-# Introduction
-
-:::info[Note]
-This feature is only available to **managers**.
-:::
-
-The Task Creation feature allows managers to create new missions for employees. There are two types of missions: **Assignment** and **Target**.
-
-- **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..
-
-- **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.
-
-- **Quest:**
- A Quest is used when you’re unsure who to assign a task to or want to invite all employees to participate.
-
-
-## Create a Mission
-
-To create a new mission, navigate to **Main Dashboard > Manage Task**. Click the **Add Button** located at the bottom right corner of the app.
-
-
-
-
-### 1. Duplicate Existing Mission
-
-In this section, you can view all previously created missions, including those that have been deleted.
-
-- [**Duplication**](duplication)
-
-### 2. Create New Mission
-
-In this section, you can create a new mission from scratch, choosing either Assignment or Target.
-
-- [**Assignment**](assignment)
-- [**Target**](target)
-
-
-
diff --git a/docs/integration/vision/upskill-creation.md b/docs/integration/vision/upskill-creation.md
deleted file mode 100644
index 293f0b7..0000000
--- a/docs/integration/vision/upskill-creation.md
+++ /dev/null
@@ -1,173 +0,0 @@
----
-sidebar_position: 5
----
-
-# Upskill Creation
-## 1. Creation Steps
-### Step 1 - Course Information
-
-
-|