diff --git a/docs/integration/vision/_category_.json b/docs/integration/vision/_category_.json
new file mode 100644
index 0000000..3545c20
--- /dev/null
+++ b/docs/integration/vision/_category_.json
@@ -0,0 +1,8 @@
+{
+ "label": "SQL Vision",
+ "position": 4,
+ "link": {
+ "type": "generated-index",
+ "description": "SQL Vision related topics"
+ }
+}
diff --git a/docs/integration/vision/gift/_category_.json b/docs/integration/vision/gift/_category_.json
new file mode 100644
index 0000000..e0523fd
--- /dev/null
+++ b/docs/integration/vision/gift/_category_.json
@@ -0,0 +1,8 @@
+{
+ "label": "Gift",
+ "position": 8,
+ "link": {
+ "type": "generated-index",
+ "description": "Guidance to create Gift and redeem Gift in SQL Vision."
+ }
+ }
diff --git a/docs/integration/vision/gift/introduction.md b/docs/integration/vision/gift/introduction.md
new file mode 100644
index 0000000..50cd242
--- /dev/null
+++ b/docs/integration/vision/gift/introduction.md
@@ -0,0 +1,11 @@
+---
+sidebar_position: 1
+---
+
+# Gift 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
new file mode 100644
index 0000000..cd05448
--- /dev/null
+++ b/docs/integration/vision/gift/manager.md
@@ -0,0 +1,117 @@
+---
+sidebar_position: 3
+---
+
+# Manager
+:::info[Note]
+
+These feature is only available to **manager**.
+
+:::
+
+## Gift Creation
+:::info[Note]
+After a manager creates a gift, users receive a notification about the new gift.
+:::
+To add a new gift, managers can go to **More icon> Add Gift**.
+
+
+
+### 1. 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. | - |
+
+### 2. Gift Redeemption 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. | - |
+
+
+## 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.
+|| |
+|:------------------------------------|:-----------------------------------------------------|
+
+### 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]
+
+The **Active** status can only be set if the Redemption Validity End Date is **on or after** the the current date.
+
+:::
+
+|| |
+|:------------------------------------|:-----------------------------------------------------|
+
+## Gift Issue
+
+### 1. 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
+After clicking **Issue**, select **Confirm** to complete issuing the gift.
+|| |
+|:------------------------------------|:-----------------------------------------------------|
+
+### 3. Check Issuance
+
+To check completed issuances, **toggle on Issued Gift**s to display the latest issued gift.
+
+|| |
+|:------------------------------------|:-----------------------------------------------------|
+
+
+## Manage Gift
+
+### 1. Gift Status
+
+|Active Gifts|Inactive Gifts |
+|:--------------------------------|:---------------------------------|
+|||
+
+|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|
+
+### 2. 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**.
+
+|| |
+|:------------------------------------|:-----------------------------------------------------|
+
+
+
+
diff --git a/docs/integration/vision/gift/user.md b/docs/integration/vision/gift/user.md
new file mode 100644
index 0000000..011d5a6
--- /dev/null
+++ b/docs/integration/vision/gift/user.md
@@ -0,0 +1,75 @@
+---
+sidebar_position: 2
+---
+
+# User
+
+:::info[Note]
+
+These feature are available to both **manager** and **employee**.
+
+:::
+
+## Gift Redeem
+### 1. Gift Filter Type
+
+|Gift Category Filter Chip|Filter Drawer|
+|:--------------------------------|:--------------------------------|
+|||
+
+|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.
+:::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.
+
+:::
+
+|||
+|:--------------------------------|:--------------------------------|
+
+|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.|
+
+### 3. Confirm Redemption
+After clicking **Redeem**, select **Confirm** to confirm. 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**.
+
+:::info[Note]
+
+Users will need to wait for approval or issuance from the manager before the gift can be used.
+
+:::
+
+|||
+|:-----------------------------------|:-----------------------------------|
+
+## Redemption Log
+Redemption log lets users view a history of redeemed rewards, showing 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/linking-to-account.md b/docs/integration/vision/linking-to-account.md
new file mode 100644
index 0000000..9a8c253
--- /dev/null
+++ b/docs/integration/vision/linking-to-account.md
@@ -0,0 +1,137 @@
+---
+sidebar_position: 9
+---
+
+# Linking to SQL Account
+
+## Introduction
+
+SQL Vision are linked to SQL Account to get the amount of sales target achieved by employees.
+
+## Requirement
+
+- SQL Vision Sync
+- SQL Account
+- SQL Vision
+- Internet Access
+
+## Setup
+
+1. **Run SQLVisionSync-Setup.exe**
+
+2. Click **Next | Next | Next | Install**
+
+3. Click **Finish**
+
+## Connect SQL Account and SQL Vision with SQL Vision Sync
+
+
+
+1. Insert the SQL accounting DFC file into the corresponding field of SQL Vision Sync. You can find the SQL account DFC file in the path specified within the SQL Account Database of the SQL Accounting Software.
+
+
+
+2. Open the dropdown and select the database from the dropdown lsit.
+
+3. Insert the user name and password fields with the SQL Accounting Software user name and password.
+
+4. Click **Test Connection**.
+:::info[Hint]
+
+The SQL Accounting Software must be open and logged in during the connection process.
+
+:::
+
+5. Click **Next** to continue the following steps.
+
+
+
+
+6. Insert the company ID.
+7. Click **Get OTP** .
+8. Insert the OTP Get from the step 7 into the OTP field.
+9. Click **Get Token**.
+10. Click **Next** to continue the following steps.
+
+
+
+11. Select the last export date
+12. Click **Export Data**.
+13. Once the data is exported, the SQL Vision mobile app will sync and display the data retrieved from the SQL Accounting Software.
+
+:::info[Parameter for SQL Vision Sync]
+
+
+
+:::
+
+## 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.
+
+:::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.
+
+
+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.
+
+
+:::
+
+### 1.0 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:
+
+
+
+### 1.1 Creating or Editing a Strategy
+
+Coming Soon.
+
+
+
diff --git a/docs/integration/vision/linking-to-payroll.md b/docs/integration/vision/linking-to-payroll.md
new file mode 100644
index 0000000..9f2f7e1
--- /dev/null
+++ b/docs/integration/vision/linking-to-payroll.md
@@ -0,0 +1,44 @@
+---
+sidebar_position: 10
+---
+
+# Linking to SQL Payroll
+
+## Introduction
+
+SQL Vision are linked with SQL Payroll to process all cash rewards earned by employees.
+
+## Requirement
+
+- SQL Payroll
+- SQL Vision
+- Internet Access
+
+## Sync SQL Vision Data
+
+1. Click **Payroll** | **New Payroll**.
+
+
+
+2. By default, the software will select the current month and all employees for processing. Confirm the configuration and click **Process**.
+
+
+
+3. A list of employees with their entitled cash will be displayed for confirmation. Press **OK** to complete the process.
+
+
+
+:::info[note]
+
+By default, all rewards will be classified as **Commission**. You can change the payment method by updating the **Payout Code**.
+
+
+
+:::
+
+:::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)**.
+
+:::
diff --git a/docs/integration/vision/login.md b/docs/integration/vision/login.md
new file mode 100644
index 0000000..06205ba
--- /dev/null
+++ b/docs/integration/vision/login.md
@@ -0,0 +1,33 @@
+---
+sidebar_position: 1
+---
+
+# Login Page
+
+## 1. Login
+
+Enter the user company email address (**highlighed** in red)
+
+
+
+### 1.1 Submit Email
+
+- This button allows user to submit their email
+- 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)
+
+### 1.4 Verification
+
+- 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
new file mode 100644
index 0000000..d7556c9
--- /dev/null
+++ b/docs/integration/vision/main-dashboard.md
@@ -0,0 +1,80 @@
+---
+sidebar_position: 2
+---
+
+# Main Dashboard
+
+
+
+
+
+
+## 1. Quick Action Buttons
+### 1.1 Task:
+- Display all available quest and tasks assigned to the user.
+
+### 1.2 Gantt Chart:
+- Display a visual timeline of tasks and deadlines, allowing the user to track progress across project.
+
+### 1.3 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:
+- Allows user to create, edit and update tasks, track task progress and review completed tasks.
+
+### 1.6 Manage Upskill:
+- Allows user to create, edit and update courses, track course progress and review completed course.
+
+## 2. 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
+- Displays up to 3 tasks that have passed thier deadlines.
+
+## 4. Undue Tasks
+- Displays up to 3 tasks that are currently in progress and have not yet reached their deadlines.
+
+## 5. 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
+
+
+### 6.1 Personal Information
+- Displays the user's profile information in the company payroll system, organized into sections for general details, employment grouping and family information.
+
+
+:::info NOTE
+Details are **view-only** and **cannot be edited** or **modified** from the mobile application.
+:::
+
+### 6.2 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).
+
+
+:::warning NOTE
+*This function is accessible only to users with manager permissions.*
+:::
+
+### 6.3 Switch Company
+- Displays a list of companies the user is enrolled in, allowing them to switch between different company accounts.
+
+
+
+### 6.4 Help
+- Directs the user to the company website for support resources and guides.
+
+### 6.5 Logout
+- Logs the user out of the application, ending the current session and returning them to the login screen.
+
+## 7. 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
new file mode 100644
index 0000000..77b9bcc
--- /dev/null
+++ b/docs/integration/vision/task.md
@@ -0,0 +1,294 @@
+---
+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_creation/_category_.json b/docs/integration/vision/task_creation/_category_.json
new file mode 100644
index 0000000..884be59
--- /dev/null
+++ b/docs/integration/vision/task_creation/_category_.json
@@ -0,0 +1,8 @@
+{
+ "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
new file mode 100644
index 0000000..b730ef0
--- /dev/null
+++ b/docs/integration/vision/task_creation/assignment.md
@@ -0,0 +1,171 @@
+---
+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
new file mode 100644
index 0000000..adfcf11
--- /dev/null
+++ b/docs/integration/vision/task_creation/duplication.md
@@ -0,0 +1,52 @@
+---
+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
new file mode 100644
index 0000000..bbd314b
--- /dev/null
+++ b/docs/integration/vision/task_creation/quest.md
@@ -0,0 +1,24 @@
+---
+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/target.md b/docs/integration/vision/task_creation/target.md
new file mode 100644
index 0000000..ab9b58e
--- /dev/null
+++ b/docs/integration/vision/task_creation/target.md
@@ -0,0 +1,251 @@
+---
+sidebar_position: 3
+---
+
+# Target
+
+Target is a quantitative mission (countable data). E.g. Sales Target, Total new users.
+
+:::info[Note]
+
+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. | - |
+
+## 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
+
+
+
+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%.
+
+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.
+
+:::info[Note]
+
+Team option is not available for quests.
+
+:::
+
+:::tip Tip 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.
+
+1. Add the team leader to the Team target and their team members to both the Team and Individual targets.
+
+2. The team leader’s target will now reflect the collective achievements of the entire team and include a unique reward, while each member will have their own individual targets and rewards!
+
+:::
+
+### 2.2 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.
+
+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.3 Condition
+
+
+
+**Condition** specifies the criteria for calculating target rewards.
+
+#### A. Between
+
+The "Between" condition is designed to allocate rewards based on an employee’s achievement falling within a defined range. Specifically, rewards are granted when an employee's achievement meets the following criteria:
+
+- It is greater than the lower boundary (X amount).
+- It is less than or equal to the upper boundary (Y amount).
+
+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.
+
+#### B. More Than
+
+The "More Than" condition is used to grant rewards when an employee surpasses a specified target amount (X). The rewards are granted according to the below criteria:
+
+- 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).
+
+#### C. Less Than
+
+The "Less Than" condition is designed to grant rewards when an employee achieves a result below a specified target amount (X). This condition is typically applied in scenarios where lower values are preferable, such as reducing errors or minimizing return stock. The rewards are granted according to the below criteria:
+
+- 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.
+
+#### D. More Than and Equal
+
+The "More Than and Equal" condition grants rewards when an employee’s achievement meets or exceeds a specified target amount (X). The rewards are granted according to the below criteria:
+
+- 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.
+
+#### E. Less Than and Equal
+
+The "Less Than and Equal" condition is applied to reward employees who achieve results at or below a specified target amount (X). The rewards are granted according to the below criteria:
+
+- 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
+
+
+
+#### 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.
+
+#### 2.4.4 Delete
+ - Deletes a specific target and its associated rewards.
+
+### 2.5 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.
+
+## Step 3 - Add Members
+
+There are 4 combination of members that can be created in Target:
+
+1. **Normal member:**
+ An employee who performs the mission without a specific management or leadership 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. **Team Leader:**
+ An employee who leads the mission. *This role is visible only when Grouping Type is set to **Team**.*
+
+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**.*
+
+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
diff --git a/docs/integration/vision/task_creation/task-creation.md b/docs/integration/vision/task_creation/task-creation.md
new file mode 100644
index 0000000..41bea90
--- /dev/null
+++ b/docs/integration/vision/task_creation/task-creation.md
@@ -0,0 +1,44 @@
+---
+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/task_creation/task-edit.md b/docs/integration/vision/task_creation/task-edit.md
new file mode 100644
index 0000000..8ba8326
--- /dev/null
+++ b/docs/integration/vision/task_creation/task-edit.md
@@ -0,0 +1,33 @@
+---
+sidebar_position: 6
+---
+
+# Edit Task
+
+:::info[Note]
+
+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**.
+
+
+
+## Edit Permission
+
+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. |
+| **Grouping Type, Strategy and Condition**| Target | Ongoing | Grouping type, strategy and condition cannot be changed after mission is ongoing. |
+
+#### Non-editable Field
+
+To clearly identify the non-editable fields, they will be greyed out, as shown in the picture.
+
+
\ No newline at end of file
diff --git a/docs/integration/vision/upskill-creation.md b/docs/integration/vision/upskill-creation.md
new file mode 100644
index 0000000..293f0b7
--- /dev/null
+++ b/docs/integration/vision/upskill-creation.md
@@ -0,0 +1,173 @@
+---
+sidebar_position: 5
+---
+
+# Upskill Creation
+## 1. Creation Steps
+### Step 1 - Course Information
+
+
+| Properties
| Description
| Required | Note
|
+|:----------------------------------------------|:------------------------------------------|:--------:|:----|
+| **1.1 Title** | The title of the course. | ✓ | - |
+| **1.2 Description** | A detailed description of the course. | ✗ | - |
+| **1.3 Tutor** | The main tutor of the course. | ✓ | - |
+| **1.4 Assistant Tutor** | The assistant tutor for the course. | ✗ | - |
+| **1.5 Clear** | Clears all course information on the current page. | - | **Manager:**
Clears all course information.
**Tutor Assistants:**
Clears all excepts tutor and assistants information.|
+| **1.6 Next** | Navigate to the next page. | - | - |
+
+
+#### 1.3 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.
+
+
+
+
+
+#### 1.4 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.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+### Step 2 - Sessions Information
+
+| Properties
| Description
| Note
|
+|:-------------------------------------|:--------------------------------------| :----------------------------- |
+| **2.1 Start & End Date** | Display the start date and end date of the course which is determined by first and last session's date. | - |
+| **2.2 Rewards Type** | 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](./upskill.md#1-rewards-type)|
+| **2.3 Session Details**| The details of each session of the course. | - |
+| **2.4 Add Session** | Add more sessions to the course. | - |
+| **2.5 Back** | Navigate back to the previous page. | - |
+| **2.6 Next** | Navigate to the next page. | - |
+
+
+#### 2.3 Session Details
+
+| Properties
| Description
| Required
| Note
|
+|:--------------------------|:--------------------------------------|:-:|:------------------------------------|
+| **2.3.1 Title** | The title of the session. | ✓ | - |
+| **2.2.2 Description** | A detailed description of the session.| ✗ | - |
+| **2.3.2 Date** | The date of the session. | ✓ | - |
+| **2.3.4 Start Time** | The start time of the session. | ✓ | - |
+| **2.3.5 End Time** | The end time of the session. | ✓ | Cannot be earlier than start time |
+| **2.3.6 Venue** | The venue of the session. | ✗ | - |
+
+
+
+
+
+
+
+
+
+
+
+
+
+### Step 3 - Rewards Information
+
+
+| Properties
| Description
| Required | Note
|
+|:-------------------------------------|:------------------------------------------|:--------:|:----|
+| **3.1 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". |
+| **3.2 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_creation/assignment.md#23-payment-by) |
+| **3.3 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_creation/assignment.md#24-bonus) |
+| **3.4 Clear** | Clears all rewards on the current page. | - | **Manager:**
Clears all rewards.
**Tutor Assistants:**
No clear button as they cannot edit rewards.|
+| **3.5 Back** | Navigate to the previous page. | - | - |
+| **3.6 Next** | Navigate to the next page. | - | - |
+
+
+#### 3.1 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.
+
+
+
+
+
+
+
+
+
+
+
+
+
+### Step 4 - Participants Information
+
+| Properties
| Description
| Note
|
+|:-----------------------------|:-----------------------------------------------------------------------------------|:---------|
+| **4.1 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](upskill.md#4-course-privacy).
+| **4.2 Filter** | Filter and sort the employee list. | By branch, department & HR group. |
+| **4.3 Select All** | Select all employees as participants. | Can press again to deselect all employees. |
+| **4.4 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 "-".|
+| **4.5 Selected Employees** | 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). |
+| **4.6 Unselected Employees** | All employees in the companies that **does not participate** in this course. |Click to **add** employee to course.|
+| **4.7 Back** | Navigate back to the previous page. | - |
+| **4.8 Create or Edit** | Create or edit the course. | - |
+
+
+#### 4.1 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.
+:::
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+## 2. Edit Course
+- The diagram below illustrates the **manager's** and **tutor assistants'** edit permissions based on the different course statuses.
+- To know more about course status, [click here](./upskill.md#3-course-status).
+
+:::info[Note]
+Tutor and assistants cannot edit any rewards-related field.
+:::
+
+#### **Manager:**
+
+
+
+#### **Tutor & Assistants:**
+
+
+
diff --git a/docs/integration/vision/upskill.md b/docs/integration/vision/upskill.md
new file mode 100644
index 0000000..f1d77e8
--- /dev/null
+++ b/docs/integration/vision/upskill.md
@@ -0,0 +1,478 @@
+---
+sidebar_position: 6
+---
+
+# Upskill
+
+## Concept
+
+### 1. 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."
+ :::
+
+ :::danger[Warning]
+ Participants will not receive any reward if they miss 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.
+ :::
+
+
+
+
+
+
+
+
+
+
+### 2. Course visibility
+- The diagram below illustrates how course visibility is set for branches, departments, and HR groups.
+
+
+#### **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.
+
+#### **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**.
+
+
+
+| Properties
| Description
| Note
|
+|:-----------------------------|:-----------------------------------------------------------------------------------|:---------|
+| **2.1 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](#3-participants-profile)
+| **2.2 Rewards summary** | 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](#4-reward-summary) |
+| **2.3 Bonus requests** | To view, approve and edit bonus requests. | To know more about bonus requests, [click here](#5-bonus-requests) |
+| **2.4 Attendance** | To view and mark attendance. | To know more about attendance, [click here](#6-attendance)|
+| **2.5 Edit course or manage course status** | To edit, manually complete or finalise course. | To know more about:
- Edit course, [click here](upskill-creation.md#2-edit-course)
- Complete course, [click here](#7-complete-course)
- Finalise course, [click here](#8-finalise-course)|
+
+
+
+
+
+
+
+
+
+
+
+
+### 3. Course status
+- There are **4 course status** 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](#7-complete-course) |
+| **Finalised** | Course is manually finalised by manager.
[Finalise course](#8-finalise-course)|
+
+
+- Below shows the **course card** of different course status:
+
+
+
+
+
+- Both users and managers can **perform different actions** depending on the course status:
+
+#### **User Course Status**
+
+
+| Actions | Upcoming | Ongoing | Completed | Finalised | Cannot perform when|
+|:-------------------------------------|:--------:|:-------:|:---------:|:---------:|:--------------------------|
+| **3.1 Register** | ✓ | ✓ | | | Course is **full**.
**Last** session has **ended**. |
+| **3.2 Unregister** | ✓ | | | | Course is **private** as participant is added by manager.
+| **3.3 Request bonus** | | | ✓ | | **Absent** from **all** sessions.
+| **3.4 View bonus request status** | | | ✓ | ✓ | -
+
+
+#### **Manager Course Status**
+
+
+| Actions | Upcoming | Ongoing | Completed | Finalised | Condition |
+|:----------------------------------------------|:--------:|:-------:|:---------:|:---------:|:------------------------------------|
+| **3.5 View attendees & participant's profile** | ✓ | ✓ | ✓ | ✓ | |
+| **3.6 View rewards summary** | ✓ | ✓ | ✓ | ✓ | Summary table only will be shown when the course is finalised. |
+| **3.7 Approve bonus requests** | | | ✓ | | - |
+| **3.8 Mark attendance** | | ✓ | ✓ | | The session must be started. |
+| **3.9 Edit course** | ✓ | ✓ | | | - |
+| **3.9 Complete course** | | ✓ | | | Last session must be ended. |
+| **3.9 Finalise course** | | | ✓ | | All bonus requests must be marked. |
+
+
+### 4. 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](#2-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).
+
+
+**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.
+
+:::
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+## User View
+### 1. Course tab
+#### **Courses tab**
+- Course tab **displays joinable courses** that the employee has not yet registered for.
+- Employees can register for any course listed in this tab, as long as there are **available slots**.
+
+
+
+
+#### **Registered tab**
+- Contains two sub-tabs:
+ **Learner tab:** Displays upcoming or ongoing courses the employee has **registered** for.
+ **Tutor tab:** Displays upcoming or ongoing courses where the employee is **assigned as a tutor or assistant**.
+
+
+
+
+#### **Completed tab**
+- Contains two sub-tabs:
+ **Learner tab:** Displays completed or finalised courses the employee has **registered** for.
+ **Tutor tab:** Displays completed or finalised courses where the employee is **assigned as a tutor or assistant**.
+
+
+
+:::info[Note]
+By default, **finalized courses are hidden**.
+To view finalized courses, open the filter and **tick** the **finalised** option.
+:::
+
+
+
+
+### 2. Participant list
+- User can view participants that has registered to course with the **"..."** button.
+- 11/15 in the diagram belows indicates that there are 11 participants registered into the course with 15 available slots.
+
+:::tip
+Private course does not have a maximum participant limit.
+Therefore the registered participants value will be displayed as "11/-".
+:::
+
+
+
+
+
+
+### 3. Bonus request status
+- Users must **attend at least one session** to request for bonus.
+
+
+
+| Status | Description |
+|:-------------------------------------|:-------------------------------------------|
+| **Request** | - User can request for bonus.
- User can only request the bonus once and no further edit can be made. |
+| **Pending** | - The bonus is awaiting for manager approval.
- Greyed out indicates that user does not request for the bonus.
+| **Marked** | - The bonus request is marked by manager.
- Greyed out indicates that user does not entitle the bonus.|
+| **Unable to request** | User cannot request a bonus due to zero attendance. |
+| **No request** | - This status only will be shown once the course has finalised.
- Indicates that user does not request for any bonus.
+ |
+
+:::warning
+User can only request the bonus once and no further edit can be made.
+:::
+:::info[Note]
+- The **request button** will **remain available** until the user **submits a bonus request** or the **course is finalised**, as long as the bonus has not yet been requested.
+- Once the course is finalised, unrequested bonuses will no longer appear greyed out but will display a **"No request"** tag instead.
+:::
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+## Manager View
+### 1. Course tab
+
+#### **Manage Upskill**
+- **Upcoming tab**: Courses that not not yet started.
+- **Ongoing tab**: Courses start has started.
+- **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).
+- To know more about visibility, [click here](#2-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.
+
+
+:::info[Note]
+By default, finalized courses are hidden.
+To view finalized courses, open the filter and **tick** the **finalised** option.
+:::
+
+
+
+
+
+### 2. 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.
+:::
+
+
+
+
+
+
+### 3. Participant's profile
+- Participant's profile is the summary of attendance and reward (session and bonus reward) obtained by participants.
+
+- **2 ways** to access participant's profile: Attendees & Rewards
+
+
+- Sample of participant's profile of **session-based** & **completion-based** course:
+
+
+
+:::info[Note]
+- A greyed-out reward means the participant did not entitle the reward.
+- 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](#3-bonus-request-status) to know more.
+:::
+
+
+
+
+### 4. Reward Summary
+- The manager can view summary of reward by clicking on the **"Rewards"** button.
+
+
+
+| Properties
| Description
| Note
|
+|:-----------------------------|:-----------------------------------------------------------------------------------|:---------|
+| **3.1 Total Spend** | To view the total expenses of the company for this course, including rewards allocated to tutors, assistants, and participants. | -
+| **3.2 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.md#step-3---rewards-information) to know more. |
+| **3.3 Tutor & assistant rewards** | To view the rewards of tutor and assistants. | - |
+| **3.4 Session 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](#1-rewards-type)|
+| **3.5 Bonus reward** | To view the bonus reward entitled by participants. | - |
+| **3.6 Total reward** | To view the total rewards entitled by participants (session rewards + bonus rewards). | - |
+| **3.7 Fully Achieve** | Indicates that participants entitled full amount of the original reward. | Tap on the indicator to view the amount of cash and coins earned.
|
+| **3.8 Partially Achieve** | Indicates that participants entitled partial amount of the original reward. | Tap on the indicator to view the amount of cash and coins earned.
 |
+
+
+:::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
+- To know more about participant's profile, [click here](#2-participants-profile).
+:::
+
+
+
+
+### 5. 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..
+ - **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.
+:::
+
+
+
+
+#### **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.
+
+
+
+
+#### **Approve or Edit Bonus Requests**
+- **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.
+
+
+:::warning
+- If a participant's bonus request is edited but not yet approved, a confirmation window will appear to remind the manager to approve the edited request.
+ - **Yes**: Discard the unapproved request and save only the approved request.
+ - **Cancel**: Continue editing the request.
+
+
+:::
+
+
+
+
+### 6. Attendance
+- 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**.
+- If **session not yet started**, there is **no pen icon** which indicates attendance is not editable and is for **viewing** only.
+- "0/3" indicates that 0 participants are present out of a total of 3 participants.
+- The manager or tutor can click on the attendance to view details or mark attendance.
+
+
+
+#### **Mark Attendance**
+- A manager or tutor can only mark attendance once the session has started.
+:::info[Note]
+- 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.
+:::
+
+
+
+
+
+
+### 7. 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.
+
+:::warning
+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](#manager-course-status)
+:::
+
+
+
+
+
+### 8. 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.
+:::
+
+:::tip
+- 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.
+:::
+
+:::warning
+Once the course is finalised, the bonus request cannot be edited anymore.
+:::
+
\ No newline at end of file
diff --git a/docs/integration/vision/wallet.md b/docs/integration/vision/wallet.md
new file mode 100644
index 0000000..c7ec85a
--- /dev/null
+++ b/docs/integration/vision/wallet.md
@@ -0,0 +1,98 @@
+---
+sidebar_position: 7
+---
+
+# Wallet
+## User
+### 1 - Wallet home page
+
+- 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
+
+
+#### tap on "view all" button to see full list of the leaderboard
+|  | ➜ |  |
+|:---:|---|:---:|
+
+### 2 - Payout (based on payment date)
+ 
+- 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\
+
+ |  | ➜ |  |
+ |:---:|---|:---:|
+
+### 3 - Entitlement (based on achieved date)
+- barchart to visualise earnings
+- grid showing entitlement per month, able to tap into it for details pop up
+
+ |  | ➜ |  |
+ |:---:|---|:---:|
+
+### 4 - 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
+
+|  | ➜ |  |
+|:---:|---|:---:|
+
+- use the dropdown button to sort the list\
+
+
+
+## Manager
+### 1 - Manage payout/entitlement page
+both payout and entitlement view have similar layout and function
+
+ - press on icon to go to manage payout, which shows the company total payout/entitlement
+
+ |  | ➜ |  |
+ |:---:|---|:---:|
+
+ - tapping the grid will now show a list of employee instead\
+ 
+
+ - 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** \
+ 
+
+ - **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
+
+ | 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 |
+ |:---:|---|:---:|---|:---:|
+ |  | ➜ |  | ➜ | |
+ | 4) after selecting, submit to save changes |||||
+ |  |||||
+
+ - you can search payout/entitlement info of a specific employee using "search employee button"
+
+ |  | ➜ |  | ➜ | |
+|:---:|---|:---:|---|:---:|
+
+ - use the stat icon to compare the payout/entitlement history of up to 3 employees
+
+|  | ➜ |  | ➜ | |
+|:---:|---|:---:|---|:---:|
+
+ ### 2 - 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
+
+ |  | ➜ |  | ➜ | |
+|:---:|---|:---:|---|:---:|
+
+
diff --git a/static/img/integration/vision/account/export-data.png b/static/img/integration/vision/account/export-data.png
new file mode 100644
index 0000000..8a0634c
Binary files /dev/null and b/static/img/integration/vision/account/export-data.png differ
diff --git a/static/img/integration/vision/account/export-log-file.png b/static/img/integration/vision/account/export-log-file.png
new file mode 100644
index 0000000..f1a3636
Binary files /dev/null and b/static/img/integration/vision/account/export-log-file.png differ
diff --git a/static/img/integration/vision/account/get-otp-and-token.png b/static/img/integration/vision/account/get-otp-and-token.png
new file mode 100644
index 0000000..484fb8d
Binary files /dev/null and b/static/img/integration/vision/account/get-otp-and-token.png differ
diff --git a/static/img/integration/vision/account/location-DCF-file.png b/static/img/integration/vision/account/location-DCF-file.png
new file mode 100644
index 0000000..9b4117a
Binary files /dev/null and b/static/img/integration/vision/account/location-DCF-file.png differ
diff --git a/static/img/integration/vision/account/predefined-strategy-add.png b/static/img/integration/vision/account/predefined-strategy-add.png
new file mode 100644
index 0000000..fb2cf76
Binary files /dev/null and b/static/img/integration/vision/account/predefined-strategy-add.png differ
diff --git a/static/img/integration/vision/account/predefined-strategy.png b/static/img/integration/vision/account/predefined-strategy.png
new file mode 100644
index 0000000..fcc8669
Binary files /dev/null and b/static/img/integration/vision/account/predefined-strategy.png differ
diff --git a/static/img/integration/vision/account/strategy-add.png b/static/img/integration/vision/account/strategy-add.png
new file mode 100644
index 0000000..a775a5a
Binary files /dev/null and b/static/img/integration/vision/account/strategy-add.png differ
diff --git a/static/img/integration/vision/account/strategy-edit.png b/static/img/integration/vision/account/strategy-edit.png
new file mode 100644
index 0000000..4488d3f
Binary files /dev/null and b/static/img/integration/vision/account/strategy-edit.png differ
diff --git a/static/img/integration/vision/account/text-connection.png b/static/img/integration/vision/account/text-connection.png
new file mode 100644
index 0000000..3f01ed1
Binary files /dev/null and b/static/img/integration/vision/account/text-connection.png differ
diff --git a/static/img/integration/vision/gift/activationFailed.png b/static/img/integration/vision/gift/activationFailed.png
new file mode 100644
index 0000000..bfc0e2e
Binary files /dev/null and b/static/img/integration/vision/gift/activationFailed.png differ
diff --git a/static/img/integration/vision/gift/activeGift.png b/static/img/integration/vision/gift/activeGift.png
new file mode 100644
index 0000000..342283b
Binary files /dev/null and b/static/img/integration/vision/gift/activeGift.png differ
diff --git a/static/img/integration/vision/gift/addGiftStep1.png b/static/img/integration/vision/gift/addGiftStep1.png
new file mode 100644
index 0000000..4977f83
Binary files /dev/null and b/static/img/integration/vision/gift/addGiftStep1.png differ
diff --git a/static/img/integration/vision/gift/addGiftStep2.png b/static/img/integration/vision/gift/addGiftStep2.png
new file mode 100644
index 0000000..bdcd37b
Binary files /dev/null and b/static/img/integration/vision/gift/addGiftStep2.png differ
diff --git a/static/img/integration/vision/gift/checkIssuance.png b/static/img/integration/vision/gift/checkIssuance.png
new file mode 100644
index 0000000..f77b524
Binary files /dev/null and b/static/img/integration/vision/gift/checkIssuance.png differ
diff --git a/static/img/integration/vision/gift/chooseEditGift.png b/static/img/integration/vision/gift/chooseEditGift.png
new file mode 100644
index 0000000..0299571
Binary files /dev/null and b/static/img/integration/vision/gift/chooseEditGift.png differ
diff --git a/static/img/integration/vision/gift/chooseGift.png b/static/img/integration/vision/gift/chooseGift.png
new file mode 100644
index 0000000..f497ea6
Binary files /dev/null and b/static/img/integration/vision/gift/chooseGift.png differ
diff --git a/static/img/integration/vision/gift/chooseIssueGift.png b/static/img/integration/vision/gift/chooseIssueGift.png
new file mode 100644
index 0000000..d178700
Binary files /dev/null and b/static/img/integration/vision/gift/chooseIssueGift.png differ
diff --git a/static/img/integration/vision/gift/confirmRedeem.png b/static/img/integration/vision/gift/confirmRedeem.png
new file mode 100644
index 0000000..34713ac
Binary files /dev/null and b/static/img/integration/vision/gift/confirmRedeem.png differ
diff --git a/static/img/integration/vision/gift/doneIssuedGift.png b/static/img/integration/vision/gift/doneIssuedGift.png
new file mode 100644
index 0000000..dc14c08
Binary files /dev/null and b/static/img/integration/vision/gift/doneIssuedGift.png differ
diff --git a/static/img/integration/vision/gift/editGiftStep1.png b/static/img/integration/vision/gift/editGiftStep1.png
new file mode 100644
index 0000000..2897110
Binary files /dev/null and b/static/img/integration/vision/gift/editGiftStep1.png differ
diff --git a/static/img/integration/vision/gift/editGiftStep2.png b/static/img/integration/vision/gift/editGiftStep2.png
new file mode 100644
index 0000000..29e3445
Binary files /dev/null and b/static/img/integration/vision/gift/editGiftStep2.png differ
diff --git a/static/img/integration/vision/gift/expiredGift.png b/static/img/integration/vision/gift/expiredGift.png
new file mode 100644
index 0000000..a6e96c8
Binary files /dev/null and b/static/img/integration/vision/gift/expiredGift.png differ
diff --git a/static/img/integration/vision/gift/filterChip.png b/static/img/integration/vision/gift/filterChip.png
new file mode 100644
index 0000000..1c7510d
Binary files /dev/null and b/static/img/integration/vision/gift/filterChip.png differ
diff --git a/static/img/integration/vision/gift/filterDrawer.png b/static/img/integration/vision/gift/filterDrawer.png
new file mode 100644
index 0000000..cb298f5
Binary files /dev/null and b/static/img/integration/vision/gift/filterDrawer.png differ
diff --git a/static/img/integration/vision/gift/giftIntro1.png b/static/img/integration/vision/gift/giftIntro1.png
new file mode 100644
index 0000000..920c50b
Binary files /dev/null and b/static/img/integration/vision/gift/giftIntro1.png differ
diff --git a/static/img/integration/vision/gift/giftIntro2.png b/static/img/integration/vision/gift/giftIntro2.png
new file mode 100644
index 0000000..8a700e4
Binary files /dev/null and b/static/img/integration/vision/gift/giftIntro2.png differ
diff --git a/static/img/integration/vision/gift/goRedeemCart.png b/static/img/integration/vision/gift/goRedeemCart.png
new file mode 100644
index 0000000..e026303
Binary files /dev/null and b/static/img/integration/vision/gift/goRedeemCart.png differ
diff --git a/static/img/integration/vision/gift/gotoAddGift.png b/static/img/integration/vision/gift/gotoAddGift.png
new file mode 100644
index 0000000..8fac77a
Binary files /dev/null and b/static/img/integration/vision/gift/gotoAddGift.png differ
diff --git a/static/img/integration/vision/gift/gotoIssuedPage.png b/static/img/integration/vision/gift/gotoIssuedPage.png
new file mode 100644
index 0000000..0a2f55b
Binary files /dev/null and b/static/img/integration/vision/gift/gotoIssuedPage.png differ
diff --git a/static/img/integration/vision/gift/gotoManageGift.png b/static/img/integration/vision/gift/gotoManageGift.png
new file mode 100644
index 0000000..8c2be71
Binary files /dev/null and b/static/img/integration/vision/gift/gotoManageGift.png differ
diff --git a/static/img/integration/vision/gift/gotoManageRedemption.png b/static/img/integration/vision/gift/gotoManageRedemption.png
new file mode 100644
index 0000000..df39349
Binary files /dev/null and b/static/img/integration/vision/gift/gotoManageRedemption.png differ
diff --git a/static/img/integration/vision/gift/gotoRedemption.png b/static/img/integration/vision/gift/gotoRedemption.png
new file mode 100644
index 0000000..8d7216b
Binary files /dev/null and b/static/img/integration/vision/gift/gotoRedemption.png differ
diff --git a/static/img/integration/vision/gift/inactiveGift.png b/static/img/integration/vision/gift/inactiveGift.png
new file mode 100644
index 0000000..ed007cd
Binary files /dev/null and b/static/img/integration/vision/gift/inactiveGift.png differ
diff --git a/static/img/integration/vision/gift/issueConfirmation.png b/static/img/integration/vision/gift/issueConfirmation.png
new file mode 100644
index 0000000..b279d8e
Binary files /dev/null and b/static/img/integration/vision/gift/issueConfirmation.png differ
diff --git a/static/img/integration/vision/gift/myRedemption.png b/static/img/integration/vision/gift/myRedemption.png
new file mode 100644
index 0000000..f248e5c
Binary files /dev/null and b/static/img/integration/vision/gift/myRedemption.png differ
diff --git a/static/img/integration/vision/gift/redeemGift.png b/static/img/integration/vision/gift/redeemGift.png
new file mode 100644
index 0000000..832c2c0
Binary files /dev/null and b/static/img/integration/vision/gift/redeemGift.png differ
diff --git a/static/img/integration/vision/gift/redeemSuccess.png b/static/img/integration/vision/gift/redeemSuccess.png
new file mode 100644
index 0000000..24719b6
Binary files /dev/null and b/static/img/integration/vision/gift/redeemSuccess.png differ
diff --git a/static/img/integration/vision/gift/redemptionLog.png b/static/img/integration/vision/gift/redemptionLog.png
new file mode 100644
index 0000000..e02d6cc
Binary files /dev/null and b/static/img/integration/vision/gift/redemptionLog.png differ
diff --git a/static/img/integration/vision/login/email.png b/static/img/integration/vision/login/email.png
new file mode 100644
index 0000000..4d8989b
Binary files /dev/null and b/static/img/integration/vision/login/email.png differ
diff --git a/static/img/integration/vision/login/otp.png b/static/img/integration/vision/login/otp.png
new file mode 100644
index 0000000..a4637b5
Binary files /dev/null and b/static/img/integration/vision/login/otp.png differ
diff --git a/static/img/integration/vision/login/receiveOTP.png b/static/img/integration/vision/login/receiveOTP.png
new file mode 100644
index 0000000..32ed0f1
Binary files /dev/null and b/static/img/integration/vision/login/receiveOTP.png differ
diff --git a/static/img/integration/vision/login/vision.png b/static/img/integration/vision/login/vision.png
new file mode 100644
index 0000000..803b3c2
Binary files /dev/null and b/static/img/integration/vision/login/vision.png differ
diff --git a/static/img/integration/vision/main-dashboard/dashboardBottom.png b/static/img/integration/vision/main-dashboard/dashboardBottom.png
new file mode 100644
index 0000000..da3e599
Binary files /dev/null and b/static/img/integration/vision/main-dashboard/dashboardBottom.png differ
diff --git a/static/img/integration/vision/main-dashboard/dashboardButton.png b/static/img/integration/vision/main-dashboard/dashboardButton.png
new file mode 100644
index 0000000..19eb2ad
Binary files /dev/null and b/static/img/integration/vision/main-dashboard/dashboardButton.png differ
diff --git a/static/img/integration/vision/main-dashboard/dashboardHeader.png b/static/img/integration/vision/main-dashboard/dashboardHeader.png
new file mode 100644
index 0000000..b422c04
Binary files /dev/null and b/static/img/integration/vision/main-dashboard/dashboardHeader.png differ
diff --git a/static/img/integration/vision/main-dashboard/dashboardMiddle.png b/static/img/integration/vision/main-dashboard/dashboardMiddle.png
new file mode 100644
index 0000000..450fe03
Binary files /dev/null and b/static/img/integration/vision/main-dashboard/dashboardMiddle.png differ
diff --git a/static/img/integration/vision/main-dashboard/logFileReview.png b/static/img/integration/vision/main-dashboard/logFileReview.png
new file mode 100644
index 0000000..594ab59
Binary files /dev/null and b/static/img/integration/vision/main-dashboard/logFileReview.png differ
diff --git a/static/img/integration/vision/main-dashboard/personalInformation.png b/static/img/integration/vision/main-dashboard/personalInformation.png
new file mode 100644
index 0000000..7b6ccdc
Binary files /dev/null and b/static/img/integration/vision/main-dashboard/personalInformation.png differ
diff --git a/static/img/integration/vision/main-dashboard/switchCompany.png b/static/img/integration/vision/main-dashboard/switchCompany.png
new file mode 100644
index 0000000..b75a28d
Binary files /dev/null and b/static/img/integration/vision/main-dashboard/switchCompany.png differ
diff --git a/static/img/integration/vision/mi_creation/a-1.3.png b/static/img/integration/vision/mi_creation/a-1.3.png
new file mode 100644
index 0000000..ee13adf
Binary files /dev/null and b/static/img/integration/vision/mi_creation/a-1.3.png differ
diff --git a/static/img/integration/vision/mi_creation/a-1.png b/static/img/integration/vision/mi_creation/a-1.png
new file mode 100644
index 0000000..9387d93
Binary files /dev/null and b/static/img/integration/vision/mi_creation/a-1.png differ
diff --git a/static/img/integration/vision/mi_creation/a-2.1.png b/static/img/integration/vision/mi_creation/a-2.1.png
new file mode 100644
index 0000000..8ce8830
Binary files /dev/null and b/static/img/integration/vision/mi_creation/a-2.1.png 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
new file mode 100644
index 0000000..ce77319
Binary files /dev/null and b/static/img/integration/vision/mi_creation/a-2.2.2.png differ
diff --git a/static/img/integration/vision/mi_creation/a-2.2.png b/static/img/integration/vision/mi_creation/a-2.2.png
new file mode 100644
index 0000000..a3ac12b
Binary files /dev/null and b/static/img/integration/vision/mi_creation/a-2.2.png differ
diff --git a/static/img/integration/vision/mi_creation/a-2.3.png b/static/img/integration/vision/mi_creation/a-2.3.png
new file mode 100644
index 0000000..9ffc159
Binary files /dev/null and b/static/img/integration/vision/mi_creation/a-2.3.png differ
diff --git a/static/img/integration/vision/mi_creation/a-2.4.png b/static/img/integration/vision/mi_creation/a-2.4.png
new file mode 100644
index 0000000..2556528
Binary files /dev/null and b/static/img/integration/vision/mi_creation/a-2.4.png differ
diff --git a/static/img/integration/vision/mi_creation/a-2.png b/static/img/integration/vision/mi_creation/a-2.png
new file mode 100644
index 0000000..7717639
Binary files /dev/null and b/static/img/integration/vision/mi_creation/a-2.png differ
diff --git a/static/img/integration/vision/mi_creation/a-3.2.png b/static/img/integration/vision/mi_creation/a-3.2.png
new file mode 100644
index 0000000..1887060
Binary files /dev/null and b/static/img/integration/vision/mi_creation/a-3.2.png differ
diff --git a/static/img/integration/vision/mi_creation/a-3.png b/static/img/integration/vision/mi_creation/a-3.png
new file mode 100644
index 0000000..1d1cdfd
Binary files /dev/null and b/static/img/integration/vision/mi_creation/a-3.png differ
diff --git a/static/img/integration/vision/mi_creation/d-1.png b/static/img/integration/vision/mi_creation/d-1.png
new file mode 100644
index 0000000..2b08e75
Binary files /dev/null and b/static/img/integration/vision/mi_creation/d-1.png differ
diff --git a/static/img/integration/vision/mi_creation/d-2.1.png b/static/img/integration/vision/mi_creation/d-2.1.png
new file mode 100644
index 0000000..a7c06c3
Binary files /dev/null and b/static/img/integration/vision/mi_creation/d-2.1.png differ
diff --git a/static/img/integration/vision/mi_creation/d-2.png b/static/img/integration/vision/mi_creation/d-2.png
new file mode 100644
index 0000000..50ff0a2
Binary files /dev/null and b/static/img/integration/vision/mi_creation/d-2.png differ
diff --git a/static/img/integration/vision/mi_creation/d-3.png b/static/img/integration/vision/mi_creation/d-3.png
new file mode 100644
index 0000000..4f4f7f7
Binary files /dev/null and b/static/img/integration/vision/mi_creation/d-3.png differ
diff --git a/static/img/integration/vision/mi_creation/e-1.png b/static/img/integration/vision/mi_creation/e-1.png
new file mode 100644
index 0000000..043c008
Binary files /dev/null and b/static/img/integration/vision/mi_creation/e-1.png differ
diff --git a/static/img/integration/vision/mi_creation/e-payment.png b/static/img/integration/vision/mi_creation/e-payment.png
new file mode 100644
index 0000000..7545305
Binary files /dev/null and b/static/img/integration/vision/mi_creation/e-payment.png differ
diff --git a/static/img/integration/vision/mi_creation/i-1.png b/static/img/integration/vision/mi_creation/i-1.png
new file mode 100644
index 0000000..76e0418
Binary files /dev/null and b/static/img/integration/vision/mi_creation/i-1.png differ
diff --git a/static/img/integration/vision/mi_creation/i-2.png b/static/img/integration/vision/mi_creation/i-2.png
new file mode 100644
index 0000000..23d618f
Binary files /dev/null and b/static/img/integration/vision/mi_creation/i-2.png differ
diff --git a/static/img/integration/vision/mi_creation/i-3.png b/static/img/integration/vision/mi_creation/i-3.png
new file mode 100644
index 0000000..893564a
Binary files /dev/null and b/static/img/integration/vision/mi_creation/i-3.png differ
diff --git a/static/img/integration/vision/mi_creation/q.png b/static/img/integration/vision/mi_creation/q.png
new file mode 100644
index 0000000..2552c3f
Binary files /dev/null and b/static/img/integration/vision/mi_creation/q.png differ
diff --git a/static/img/integration/vision/mi_creation/t-1.png b/static/img/integration/vision/mi_creation/t-1.png
new file mode 100644
index 0000000..d2dbcea
Binary files /dev/null and b/static/img/integration/vision/mi_creation/t-1.png differ
diff --git a/static/img/integration/vision/mi_creation/t-2.1.png b/static/img/integration/vision/mi_creation/t-2.1.png
new file mode 100644
index 0000000..598dc07
Binary files /dev/null and b/static/img/integration/vision/mi_creation/t-2.1.png differ
diff --git a/static/img/integration/vision/mi_creation/t-2.2.png b/static/img/integration/vision/mi_creation/t-2.2.png
new file mode 100644
index 0000000..5090d6e
Binary files /dev/null and b/static/img/integration/vision/mi_creation/t-2.2.png differ
diff --git a/static/img/integration/vision/mi_creation/t-2.3-example.png b/static/img/integration/vision/mi_creation/t-2.3-example.png
new file mode 100644
index 0000000..a08ba71
Binary files /dev/null and b/static/img/integration/vision/mi_creation/t-2.3-example.png differ
diff --git a/static/img/integration/vision/mi_creation/t-2.3-example2.png b/static/img/integration/vision/mi_creation/t-2.3-example2.png
new file mode 100644
index 0000000..c31e9fb
Binary files /dev/null and b/static/img/integration/vision/mi_creation/t-2.3-example2.png differ
diff --git a/static/img/integration/vision/mi_creation/t-2.3-example3.png b/static/img/integration/vision/mi_creation/t-2.3-example3.png
new file mode 100644
index 0000000..44abd75
Binary files /dev/null and b/static/img/integration/vision/mi_creation/t-2.3-example3.png differ
diff --git a/static/img/integration/vision/mi_creation/t-2.3-example4.png b/static/img/integration/vision/mi_creation/t-2.3-example4.png
new file mode 100644
index 0000000..9f13261
Binary files /dev/null and b/static/img/integration/vision/mi_creation/t-2.3-example4.png differ
diff --git a/static/img/integration/vision/mi_creation/t-2.3-example5.png b/static/img/integration/vision/mi_creation/t-2.3-example5.png
new file mode 100644
index 0000000..e430a59
Binary files /dev/null and b/static/img/integration/vision/mi_creation/t-2.3-example5.png differ
diff --git a/static/img/integration/vision/mi_creation/t-2.3.png b/static/img/integration/vision/mi_creation/t-2.3.png
new file mode 100644
index 0000000..5d47824
Binary files /dev/null and b/static/img/integration/vision/mi_creation/t-2.3.png differ
diff --git a/static/img/integration/vision/mi_creation/t-2.4.png b/static/img/integration/vision/mi_creation/t-2.4.png
new file mode 100644
index 0000000..267119c
Binary files /dev/null and b/static/img/integration/vision/mi_creation/t-2.4.png differ
diff --git a/static/img/integration/vision/mi_creation/t-2.png b/static/img/integration/vision/mi_creation/t-2.png
new file mode 100644
index 0000000..b4505d7
Binary files /dev/null and b/static/img/integration/vision/mi_creation/t-2.png differ
diff --git a/static/img/integration/vision/mi_creation/t-3.png b/static/img/integration/vision/mi_creation/t-3.png
new file mode 100644
index 0000000..589a821
Binary files /dev/null and b/static/img/integration/vision/mi_creation/t-3.png differ
diff --git a/static/img/integration/vision/payroll/payroll-1.png b/static/img/integration/vision/payroll/payroll-1.png
new file mode 100644
index 0000000..82b449b
Binary files /dev/null and b/static/img/integration/vision/payroll/payroll-1.png differ
diff --git a/static/img/integration/vision/payroll/payroll-2.png b/static/img/integration/vision/payroll/payroll-2.png
new file mode 100644
index 0000000..5cf16d1
Binary files /dev/null and b/static/img/integration/vision/payroll/payroll-2.png differ
diff --git a/static/img/integration/vision/payroll/payroll-3.png b/static/img/integration/vision/payroll/payroll-3.png
new file mode 100644
index 0000000..f54f75e
Binary files /dev/null and b/static/img/integration/vision/payroll/payroll-3.png differ
diff --git a/static/img/integration/vision/payroll/payroll-info.png b/static/img/integration/vision/payroll/payroll-info.png
new file mode 100644
index 0000000..030244d
Binary files /dev/null and b/static/img/integration/vision/payroll/payroll-info.png differ
diff --git a/static/img/integration/vision/task/approve.png b/static/img/integration/vision/task/approve.png
new file mode 100644
index 0000000..13d634f
Binary files /dev/null and b/static/img/integration/vision/task/approve.png differ
diff --git a/static/img/integration/vision/task/assignmentDetail.png b/static/img/integration/vision/task/assignmentDetail.png
new file mode 100644
index 0000000..0cb355e
Binary files /dev/null and b/static/img/integration/vision/task/assignmentDetail.png differ
diff --git a/static/img/integration/vision/task/bonusReq.png b/static/img/integration/vision/task/bonusReq.png
new file mode 100644
index 0000000..b09191f
Binary files /dev/null and b/static/img/integration/vision/task/bonusReq.png differ
diff --git a/static/img/integration/vision/task/bonusReview.png b/static/img/integration/vision/task/bonusReview.png
new file mode 100644
index 0000000..589ba2e
Binary files /dev/null and b/static/img/integration/vision/task/bonusReview.png differ
diff --git a/static/img/integration/vision/task/changeLog.png b/static/img/integration/vision/task/changeLog.png
new file mode 100644
index 0000000..5803049
Binary files /dev/null and b/static/img/integration/vision/task/changeLog.png differ
diff --git a/static/img/integration/vision/task/editAsgmt.png b/static/img/integration/vision/task/editAsgmt.png
new file mode 100644
index 0000000..b981f34
Binary files /dev/null and b/static/img/integration/vision/task/editAsgmt.png differ
diff --git a/static/img/integration/vision/task/editBonus.png b/static/img/integration/vision/task/editBonus.png
new file mode 100644
index 0000000..939766f
Binary files /dev/null and b/static/img/integration/vision/task/editBonus.png differ
diff --git a/static/img/integration/vision/task/editTarget.png b/static/img/integration/vision/task/editTarget.png
new file mode 100644
index 0000000..afeaeb6
Binary files /dev/null and b/static/img/integration/vision/task/editTarget.png differ
diff --git a/static/img/integration/vision/task/filterEmp.png b/static/img/integration/vision/task/filterEmp.png
new file mode 100644
index 0000000..d12e06f
Binary files /dev/null and b/static/img/integration/vision/task/filterEmp.png differ
diff --git a/static/img/integration/vision/task/finalizeAsgmt.png b/static/img/integration/vision/task/finalizeAsgmt.png
new file mode 100644
index 0000000..c2ea3f6
Binary files /dev/null and b/static/img/integration/vision/task/finalizeAsgmt.png differ
diff --git a/static/img/integration/vision/task/individualEmp.png b/static/img/integration/vision/task/individualEmp.png
new file mode 100644
index 0000000..ba99e14
Binary files /dev/null and b/static/img/integration/vision/task/individualEmp.png differ
diff --git a/static/img/integration/vision/task/individualTarget.png b/static/img/integration/vision/task/individualTarget.png
new file mode 100644
index 0000000..93ebc49
Binary files /dev/null and b/static/img/integration/vision/task/individualTarget.png differ
diff --git a/static/img/integration/vision/task/logFile.png b/static/img/integration/vision/task/logFile.png
new file mode 100644
index 0000000..181af9d
Binary files /dev/null and b/static/img/integration/vision/task/logFile.png differ
diff --git a/static/img/integration/vision/task/logFileApproval.png b/static/img/integration/vision/task/logFileApproval.png
new file mode 100644
index 0000000..5144c14
Binary files /dev/null and b/static/img/integration/vision/task/logFileApproval.png differ
diff --git a/static/img/integration/vision/task/logFileOverride.png b/static/img/integration/vision/task/logFileOverride.png
new file mode 100644
index 0000000..7b385e9
Binary files /dev/null and b/static/img/integration/vision/task/logFileOverride.png differ
diff --git a/static/img/integration/vision/task/manageParticipant.png b/static/img/integration/vision/task/manageParticipant.png
new file mode 100644
index 0000000..f9594ad
Binary files /dev/null and b/static/img/integration/vision/task/manageParticipant.png differ
diff --git a/static/img/integration/vision/task/mgrAssignmentDetail.png b/static/img/integration/vision/task/mgrAssignmentDetail.png
new file mode 100644
index 0000000..e172cb8
Binary files /dev/null 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
new file mode 100644
index 0000000..db37022
Binary files /dev/null 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
new file mode 100644
index 0000000..30e466c
Binary files /dev/null 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
new file mode 100644
index 0000000..38c12b8
Binary files /dev/null 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
new file mode 100644
index 0000000..d4bd504
Binary files /dev/null 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
new file mode 100644
index 0000000..e4a54bc
Binary files /dev/null and b/static/img/integration/vision/task/mgrTeamTarget.png differ
diff --git a/static/img/integration/vision/task/mgrViewEmpAsgmt.png b/static/img/integration/vision/task/mgrViewEmpAsgmt.png
new file mode 100644
index 0000000..f38222e
Binary files /dev/null and b/static/img/integration/vision/task/mgrViewEmpAsgmt.png differ
diff --git a/static/img/integration/vision/task/mgrViewEmpCompleteAsmgt.png b/static/img/integration/vision/task/mgrViewEmpCompleteAsmgt.png
new file mode 100644
index 0000000..f2b3f9f
Binary files /dev/null and b/static/img/integration/vision/task/mgrViewEmpCompleteAsmgt.png differ
diff --git a/static/img/integration/vision/task/pending.png b/static/img/integration/vision/task/pending.png
new file mode 100644
index 0000000..3708ec4
Binary files /dev/null and b/static/img/integration/vision/task/pending.png differ
diff --git a/static/img/integration/vision/task/progressTracker.png b/static/img/integration/vision/task/progressTracker.png
new file mode 100644
index 0000000..d415093
Binary files /dev/null and b/static/img/integration/vision/task/progressTracker.png differ
diff --git a/static/img/integration/vision/task/quest.png b/static/img/integration/vision/task/quest.png
new file mode 100644
index 0000000..de510b2
Binary files /dev/null and b/static/img/integration/vision/task/quest.png differ
diff --git a/static/img/integration/vision/task/questJoinDirect.png b/static/img/integration/vision/task/questJoinDirect.png
new file mode 100644
index 0000000..a194903
Binary files /dev/null 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
new file mode 100644
index 0000000..b579163
Binary files /dev/null and b/static/img/integration/vision/task/questRequiredApprove.png differ
diff --git a/static/img/integration/vision/task/rewardDialog.png b/static/img/integration/vision/task/rewardDialog.png
new file mode 100644
index 0000000..358b6d4
Binary files /dev/null and b/static/img/integration/vision/task/rewardDialog.png differ
diff --git a/static/img/integration/vision/task/teamEmp.png b/static/img/integration/vision/task/teamEmp.png
new file mode 100644
index 0000000..8506214
Binary files /dev/null and b/static/img/integration/vision/task/teamEmp.png differ
diff --git a/static/img/integration/vision/task/teamTarget.png b/static/img/integration/vision/task/teamTarget.png
new file mode 100644
index 0000000..762d593
Binary files /dev/null and b/static/img/integration/vision/task/teamTarget.png differ
diff --git a/static/img/integration/vision/task/tooltipAsgmt.png b/static/img/integration/vision/task/tooltipAsgmt.png
new file mode 100644
index 0000000..cfc82e8
Binary files /dev/null and b/static/img/integration/vision/task/tooltipAsgmt.png differ
diff --git a/static/img/integration/vision/task/updateLogFile.png b/static/img/integration/vision/task/updateLogFile.png
new file mode 100644
index 0000000..ebf75b4
Binary files /dev/null and b/static/img/integration/vision/task/updateLogFile.png differ
diff --git a/static/img/integration/vision/upskill/concept_coursePrivacy_courseCard.png b/static/img/integration/vision/upskill/concept_coursePrivacy_courseCard.png
new file mode 100644
index 0000000..43db1fb
Binary files /dev/null and b/static/img/integration/vision/upskill/concept_coursePrivacy_courseCard.png differ
diff --git a/static/img/integration/vision/upskill/concept_coursePrivacy_privateCourse.png b/static/img/integration/vision/upskill/concept_coursePrivacy_privateCourse.png
new file mode 100644
index 0000000..834f68c
Binary files /dev/null and b/static/img/integration/vision/upskill/concept_coursePrivacy_privateCourse.png differ
diff --git a/static/img/integration/vision/upskill/concept_courseStatus_courseCard.png b/static/img/integration/vision/upskill/concept_courseStatus_courseCard.png
new file mode 100644
index 0000000..1da8609
Binary files /dev/null and b/static/img/integration/vision/upskill/concept_courseStatus_courseCard.png differ
diff --git a/static/img/integration/vision/upskill/concept_courseStatus_mgrAction.png b/static/img/integration/vision/upskill/concept_courseStatus_mgrAction.png
new file mode 100644
index 0000000..67a374b
Binary files /dev/null and b/static/img/integration/vision/upskill/concept_courseStatus_mgrAction.png differ
diff --git a/static/img/integration/vision/upskill/concept_courseStatus_userAction.png b/static/img/integration/vision/upskill/concept_courseStatus_userAction.png
new file mode 100644
index 0000000..b23a40a
Binary files /dev/null and b/static/img/integration/vision/upskill/concept_courseStatus_userAction.png differ
diff --git a/static/img/integration/vision/upskill/concept_courseVisibility_mgrManage&ViewCourse.png b/static/img/integration/vision/upskill/concept_courseVisibility_mgrManage&ViewCourse.png
new file mode 100644
index 0000000..276cbda
Binary files /dev/null and b/static/img/integration/vision/upskill/concept_courseVisibility_mgrManage&ViewCourse.png differ
diff --git a/static/img/integration/vision/upskill/concept_courseVisibility_setVisibility.png b/static/img/integration/vision/upskill/concept_courseVisibility_setVisibility.png
new file mode 100644
index 0000000..3733b3b
Binary files /dev/null and b/static/img/integration/vision/upskill/concept_courseVisibility_setVisibility.png differ
diff --git a/static/img/integration/vision/upskill/concept_managerCreatePrivateCourse.png b/static/img/integration/vision/upskill/concept_managerCreatePrivateCourse.png
new file mode 100644
index 0000000..2604be5
Binary files /dev/null and b/static/img/integration/vision/upskill/concept_managerCreatePrivateCourse.png differ
diff --git a/static/img/integration/vision/upskill/concept_publicPrivateCourseCard.png b/static/img/integration/vision/upskill/concept_publicPrivateCourseCard.png
new file mode 100644
index 0000000..ecde310
Binary files /dev/null and b/static/img/integration/vision/upskill/concept_publicPrivateCourseCard.png differ
diff --git a/static/img/integration/vision/upskill/concept_rewardType.png b/static/img/integration/vision/upskill/concept_rewardType.png
new file mode 100644
index 0000000..4a28fc6
Binary files /dev/null and b/static/img/integration/vision/upskill/concept_rewardType.png differ
diff --git a/static/img/integration/vision/upskill/mgr_attendance_markAttendance.png b/static/img/integration/vision/upskill/mgr_attendance_markAttendance.png
new file mode 100644
index 0000000..d758ea4
Binary files /dev/null and b/static/img/integration/vision/upskill/mgr_attendance_markAttendance.png differ
diff --git a/static/img/integration/vision/upskill/mgr_attendance_viewAttendance.png b/static/img/integration/vision/upskill/mgr_attendance_viewAttendance.png
new file mode 100644
index 0000000..e589c36
Binary files /dev/null and b/static/img/integration/vision/upskill/mgr_attendance_viewAttendance.png differ
diff --git a/static/img/integration/vision/upskill/mgr_bonusRequest_approveBonus.png b/static/img/integration/vision/upskill/mgr_bonusRequest_approveBonus.png
new file mode 100644
index 0000000..0c8cc4e
Binary files /dev/null and b/static/img/integration/vision/upskill/mgr_bonusRequest_approveBonus.png differ
diff --git a/static/img/integration/vision/upskill/mgr_bonusRequest_editMode.png b/static/img/integration/vision/upskill/mgr_bonusRequest_editMode.png
new file mode 100644
index 0000000..7f0348a
Binary files /dev/null and b/static/img/integration/vision/upskill/mgr_bonusRequest_editMode.png differ
diff --git a/static/img/integration/vision/upskill/mgr_bonusRequest_unapprovedBonusDialog.png b/static/img/integration/vision/upskill/mgr_bonusRequest_unapprovedBonusDialog.png
new file mode 100644
index 0000000..3d08ad0
Binary files /dev/null and b/static/img/integration/vision/upskill/mgr_bonusRequest_unapprovedBonusDialog.png differ
diff --git a/static/img/integration/vision/upskill/mgr_bonusRequest_viewBonusReq.png b/static/img/integration/vision/upskill/mgr_bonusRequest_viewBonusReq.png
new file mode 100644
index 0000000..0bf09c1
Binary files /dev/null and b/static/img/integration/vision/upskill/mgr_bonusRequest_viewBonusReq.png differ
diff --git a/static/img/integration/vision/upskill/mgr_completeCourse.png b/static/img/integration/vision/upskill/mgr_completeCourse.png
new file mode 100644
index 0000000..336e595
Binary files /dev/null and b/static/img/integration/vision/upskill/mgr_completeCourse.png differ
diff --git a/static/img/integration/vision/upskill/mgr_courseTab_deleteCourse.png b/static/img/integration/vision/upskill/mgr_courseTab_deleteCourse.png
new file mode 100644
index 0000000..016d64c
Binary files /dev/null and b/static/img/integration/vision/upskill/mgr_courseTab_deleteCourse.png differ
diff --git a/static/img/integration/vision/upskill/mgr_courseTab_manageUpskill.png b/static/img/integration/vision/upskill/mgr_courseTab_manageUpskill.png
new file mode 100644
index 0000000..a27967a
Binary files /dev/null and b/static/img/integration/vision/upskill/mgr_courseTab_manageUpskill.png differ
diff --git a/static/img/integration/vision/upskill/mgr_courseTab_otherBranch&Dept.png b/static/img/integration/vision/upskill/mgr_courseTab_otherBranch&Dept.png
new file mode 100644
index 0000000..4368063
Binary files /dev/null and b/static/img/integration/vision/upskill/mgr_courseTab_otherBranch&Dept.png differ
diff --git a/static/img/integration/vision/upskill/mgr_finaliseCourse.png b/static/img/integration/vision/upskill/mgr_finaliseCourse.png
new file mode 100644
index 0000000..be97705
Binary files /dev/null and b/static/img/integration/vision/upskill/mgr_finaliseCourse.png differ
diff --git a/static/img/integration/vision/upskill/mgr_participantList.png b/static/img/integration/vision/upskill/mgr_participantList.png
new file mode 100644
index 0000000..a7c8df2
Binary files /dev/null and b/static/img/integration/vision/upskill/mgr_participantList.png differ
diff --git a/static/img/integration/vision/upskill/mgr_participantProfile_sessionCompletion.png b/static/img/integration/vision/upskill/mgr_participantProfile_sessionCompletion.png
new file mode 100644
index 0000000..6d814b3
Binary files /dev/null and b/static/img/integration/vision/upskill/mgr_participantProfile_sessionCompletion.png differ
diff --git a/static/img/integration/vision/upskill/mgr_participantProfile_waysToAccess.png b/static/img/integration/vision/upskill/mgr_participantProfile_waysToAccess.png
new file mode 100644
index 0000000..4494f7f
Binary files /dev/null and b/static/img/integration/vision/upskill/mgr_participantProfile_waysToAccess.png differ
diff --git a/static/img/integration/vision/upskill/mgr_rewardSummary.png b/static/img/integration/vision/upskill/mgr_rewardSummary.png
new file mode 100644
index 0000000..0ec6e48
Binary files /dev/null and b/static/img/integration/vision/upskill/mgr_rewardSummary.png differ
diff --git a/static/img/integration/vision/upskill/mgr_rewardSummary_tapFullyIndicator.png b/static/img/integration/vision/upskill/mgr_rewardSummary_tapFullyIndicator.png
new file mode 100644
index 0000000..5163b00
Binary files /dev/null and b/static/img/integration/vision/upskill/mgr_rewardSummary_tapFullyIndicator.png differ
diff --git a/static/img/integration/vision/upskill/mgr_rewardSummary_tapPartialIndicator.png b/static/img/integration/vision/upskill/mgr_rewardSummary_tapPartialIndicator.png
new file mode 100644
index 0000000..adb0747
Binary files /dev/null and b/static/img/integration/vision/upskill/mgr_rewardSummary_tapPartialIndicator.png differ
diff --git a/static/img/integration/vision/upskill/payroll-info.png b/static/img/integration/vision/upskill/payroll-info.png
new file mode 100644
index 0000000..a5472e8
Binary files /dev/null and b/static/img/integration/vision/upskill/payroll-info.png differ
diff --git a/static/img/integration/vision/upskill/user_bonusReqStatus.png b/static/img/integration/vision/upskill/user_bonusReqStatus.png
new file mode 100644
index 0000000..9ed8904
Binary files /dev/null and b/static/img/integration/vision/upskill/user_bonusReqStatus.png differ
diff --git a/static/img/integration/vision/upskill/user_courseTab_completed.png b/static/img/integration/vision/upskill/user_courseTab_completed.png
new file mode 100644
index 0000000..1f8489c
Binary files /dev/null and b/static/img/integration/vision/upskill/user_courseTab_completed.png differ
diff --git a/static/img/integration/vision/upskill/user_courseTab_courses.png b/static/img/integration/vision/upskill/user_courseTab_courses.png
new file mode 100644
index 0000000..5a96850
Binary files /dev/null and b/static/img/integration/vision/upskill/user_courseTab_courses.png differ
diff --git a/static/img/integration/vision/upskill/user_courseTab_registered.png b/static/img/integration/vision/upskill/user_courseTab_registered.png
new file mode 100644
index 0000000..ba679e4
Binary files /dev/null and b/static/img/integration/vision/upskill/user_courseTab_registered.png differ
diff --git a/static/img/integration/vision/upskill/user_participantList.png b/static/img/integration/vision/upskill/user_participantList.png
new file mode 100644
index 0000000..8a8cca2
Binary files /dev/null and b/static/img/integration/vision/upskill/user_participantList.png differ
diff --git a/static/img/integration/vision/upskillCreation/editCourse_mgr.png b/static/img/integration/vision/upskillCreation/editCourse_mgr.png
new file mode 100644
index 0000000..0a6009b
Binary files /dev/null and b/static/img/integration/vision/upskillCreation/editCourse_mgr.png differ
diff --git a/static/img/integration/vision/upskillCreation/editCourse_tutorAsst.png b/static/img/integration/vision/upskillCreation/editCourse_tutorAsst.png
new file mode 100644
index 0000000..34489bb
Binary files /dev/null and b/static/img/integration/vision/upskillCreation/editCourse_tutorAsst.png differ
diff --git a/static/img/integration/vision/upskillCreation/payroll-3.png b/static/img/integration/vision/upskillCreation/payroll-3.png
new file mode 100644
index 0000000..04d0ea0
Binary files /dev/null and b/static/img/integration/vision/upskillCreation/payroll-3.png differ
diff --git a/static/img/integration/vision/upskillCreation/step1_addAssistant.png b/static/img/integration/vision/upskillCreation/step1_addAssistant.png
new file mode 100644
index 0000000..f5bd246
Binary files /dev/null and b/static/img/integration/vision/upskillCreation/step1_addAssistant.png differ
diff --git a/static/img/integration/vision/upskillCreation/step1_addMultipleTutor.png b/static/img/integration/vision/upskillCreation/step1_addMultipleTutor.png
new file mode 100644
index 0000000..bdbcead
Binary files /dev/null and b/static/img/integration/vision/upskillCreation/step1_addMultipleTutor.png differ
diff --git a/static/img/integration/vision/upskillCreation/step1_addTutor.png b/static/img/integration/vision/upskillCreation/step1_addTutor.png
new file mode 100644
index 0000000..8959349
Binary files /dev/null and b/static/img/integration/vision/upskillCreation/step1_addTutor.png differ
diff --git a/static/img/integration/vision/upskillCreation/step1_courseInfo.png b/static/img/integration/vision/upskillCreation/step1_courseInfo.png
new file mode 100644
index 0000000..669e832
Binary files /dev/null and b/static/img/integration/vision/upskillCreation/step1_courseInfo.png differ
diff --git a/static/img/integration/vision/upskillCreation/step2_sessionInfo.png b/static/img/integration/vision/upskillCreation/step2_sessionInfo.png
new file mode 100644
index 0000000..40666e4
Binary files /dev/null and b/static/img/integration/vision/upskillCreation/step2_sessionInfo.png differ
diff --git a/static/img/integration/vision/upskillCreation/step2_sessionInfoDetail.png b/static/img/integration/vision/upskillCreation/step2_sessionInfoDetail.png
new file mode 100644
index 0000000..397cf8c
Binary files /dev/null and b/static/img/integration/vision/upskillCreation/step2_sessionInfoDetail.png differ
diff --git a/static/img/integration/vision/upskillCreation/step3_rewardInfo.png b/static/img/integration/vision/upskillCreation/step3_rewardInfo.png
new file mode 100644
index 0000000..108b069
Binary files /dev/null and b/static/img/integration/vision/upskillCreation/step3_rewardInfo.png differ
diff --git a/static/img/integration/vision/upskillCreation/step3_sessionReward.png b/static/img/integration/vision/upskillCreation/step3_sessionReward.png
new file mode 100644
index 0000000..32d5a90
Binary files /dev/null and b/static/img/integration/vision/upskillCreation/step3_sessionReward.png differ
diff --git a/static/img/integration/vision/upskillCreation/step4_IsPublic.png b/static/img/integration/vision/upskillCreation/step4_IsPublic.png
new file mode 100644
index 0000000..c123c7b
Binary files /dev/null and b/static/img/integration/vision/upskillCreation/step4_IsPublic.png differ
diff --git a/static/img/integration/vision/upskillCreation/step4_ParticipantInfo.png b/static/img/integration/vision/upskillCreation/step4_ParticipantInfo.png
new file mode 100644
index 0000000..882df6a
Binary files /dev/null and b/static/img/integration/vision/upskillCreation/step4_ParticipantInfo.png differ
diff --git a/static/img/integration/vision/wallet/wallet1.png b/static/img/integration/vision/wallet/wallet1.png
new file mode 100644
index 0000000..5eb60c3
Binary files /dev/null and b/static/img/integration/vision/wallet/wallet1.png differ
diff --git a/static/img/integration/vision/wallet/wallet10.png b/static/img/integration/vision/wallet/wallet10.png
new file mode 100644
index 0000000..7df6f17
Binary files /dev/null and b/static/img/integration/vision/wallet/wallet10.png differ
diff --git a/static/img/integration/vision/wallet/wallet11.png b/static/img/integration/vision/wallet/wallet11.png
new file mode 100644
index 0000000..e50dd46
Binary files /dev/null and b/static/img/integration/vision/wallet/wallet11.png differ
diff --git a/static/img/integration/vision/wallet/wallet12.png b/static/img/integration/vision/wallet/wallet12.png
new file mode 100644
index 0000000..d710772
Binary files /dev/null and b/static/img/integration/vision/wallet/wallet12.png differ
diff --git a/static/img/integration/vision/wallet/wallet13.png b/static/img/integration/vision/wallet/wallet13.png
new file mode 100644
index 0000000..3213a3b
Binary files /dev/null and b/static/img/integration/vision/wallet/wallet13.png differ
diff --git a/static/img/integration/vision/wallet/wallet14.png b/static/img/integration/vision/wallet/wallet14.png
new file mode 100644
index 0000000..160c1f3
Binary files /dev/null and b/static/img/integration/vision/wallet/wallet14.png differ
diff --git a/static/img/integration/vision/wallet/wallet15.png b/static/img/integration/vision/wallet/wallet15.png
new file mode 100644
index 0000000..c434013
Binary files /dev/null and b/static/img/integration/vision/wallet/wallet15.png differ
diff --git a/static/img/integration/vision/wallet/wallet16.png b/static/img/integration/vision/wallet/wallet16.png
new file mode 100644
index 0000000..44680b6
Binary files /dev/null and b/static/img/integration/vision/wallet/wallet16.png differ
diff --git a/static/img/integration/vision/wallet/wallet17.png b/static/img/integration/vision/wallet/wallet17.png
new file mode 100644
index 0000000..bedd562
Binary files /dev/null and b/static/img/integration/vision/wallet/wallet17.png differ
diff --git a/static/img/integration/vision/wallet/wallet19.png b/static/img/integration/vision/wallet/wallet19.png
new file mode 100644
index 0000000..0060cc6
Binary files /dev/null and b/static/img/integration/vision/wallet/wallet19.png differ
diff --git a/static/img/integration/vision/wallet/wallet2.png b/static/img/integration/vision/wallet/wallet2.png
new file mode 100644
index 0000000..2d43412
Binary files /dev/null and b/static/img/integration/vision/wallet/wallet2.png differ
diff --git a/static/img/integration/vision/wallet/wallet20.png b/static/img/integration/vision/wallet/wallet20.png
new file mode 100644
index 0000000..f0f7e6b
Binary files /dev/null and b/static/img/integration/vision/wallet/wallet20.png differ
diff --git a/static/img/integration/vision/wallet/wallet21.png b/static/img/integration/vision/wallet/wallet21.png
new file mode 100644
index 0000000..e7559f6
Binary files /dev/null and b/static/img/integration/vision/wallet/wallet21.png differ
diff --git a/static/img/integration/vision/wallet/wallet22.png b/static/img/integration/vision/wallet/wallet22.png
new file mode 100644
index 0000000..a097d71
Binary files /dev/null and b/static/img/integration/vision/wallet/wallet22.png differ
diff --git a/static/img/integration/vision/wallet/wallet24.png b/static/img/integration/vision/wallet/wallet24.png
new file mode 100644
index 0000000..aaae3cb
Binary files /dev/null and b/static/img/integration/vision/wallet/wallet24.png differ
diff --git a/static/img/integration/vision/wallet/wallet25.png b/static/img/integration/vision/wallet/wallet25.png
new file mode 100644
index 0000000..e14892e
Binary files /dev/null and b/static/img/integration/vision/wallet/wallet25.png differ
diff --git a/static/img/integration/vision/wallet/wallet26.png b/static/img/integration/vision/wallet/wallet26.png
new file mode 100644
index 0000000..1e1900d
Binary files /dev/null and b/static/img/integration/vision/wallet/wallet26.png differ
diff --git a/static/img/integration/vision/wallet/wallet27.png b/static/img/integration/vision/wallet/wallet27.png
new file mode 100644
index 0000000..8517bf8
Binary files /dev/null and b/static/img/integration/vision/wallet/wallet27.png differ
diff --git a/static/img/integration/vision/wallet/wallet28.png b/static/img/integration/vision/wallet/wallet28.png
new file mode 100644
index 0000000..7637051
Binary files /dev/null and b/static/img/integration/vision/wallet/wallet28.png differ
diff --git a/static/img/integration/vision/wallet/wallet29.png b/static/img/integration/vision/wallet/wallet29.png
new file mode 100644
index 0000000..403cd33
Binary files /dev/null and b/static/img/integration/vision/wallet/wallet29.png differ
diff --git a/static/img/integration/vision/wallet/wallet3.png b/static/img/integration/vision/wallet/wallet3.png
new file mode 100644
index 0000000..3d4bf68
Binary files /dev/null and b/static/img/integration/vision/wallet/wallet3.png differ
diff --git a/static/img/integration/vision/wallet/wallet30.png b/static/img/integration/vision/wallet/wallet30.png
new file mode 100644
index 0000000..a236bf3
Binary files /dev/null and b/static/img/integration/vision/wallet/wallet30.png differ
diff --git a/static/img/integration/vision/wallet/wallet31.png b/static/img/integration/vision/wallet/wallet31.png
new file mode 100644
index 0000000..0669580
Binary files /dev/null and b/static/img/integration/vision/wallet/wallet31.png differ
diff --git a/static/img/integration/vision/wallet/wallet32.png b/static/img/integration/vision/wallet/wallet32.png
new file mode 100644
index 0000000..64dbcfb
Binary files /dev/null and b/static/img/integration/vision/wallet/wallet32.png differ
diff --git a/static/img/integration/vision/wallet/wallet33.png b/static/img/integration/vision/wallet/wallet33.png
new file mode 100644
index 0000000..15d7d9b
Binary files /dev/null and b/static/img/integration/vision/wallet/wallet33.png differ
diff --git a/static/img/integration/vision/wallet/wallet34.png b/static/img/integration/vision/wallet/wallet34.png
new file mode 100644
index 0000000..4aaf40f
Binary files /dev/null and b/static/img/integration/vision/wallet/wallet34.png differ
diff --git a/static/img/integration/vision/wallet/wallet35.png b/static/img/integration/vision/wallet/wallet35.png
new file mode 100644
index 0000000..18b34ce
Binary files /dev/null and b/static/img/integration/vision/wallet/wallet35.png differ
diff --git a/static/img/integration/vision/wallet/wallet4.png b/static/img/integration/vision/wallet/wallet4.png
new file mode 100644
index 0000000..9a9fcbc
Binary files /dev/null and b/static/img/integration/vision/wallet/wallet4.png differ
diff --git a/static/img/integration/vision/wallet/wallet5.png b/static/img/integration/vision/wallet/wallet5.png
new file mode 100644
index 0000000..19136cf
Binary files /dev/null and b/static/img/integration/vision/wallet/wallet5.png differ
diff --git a/static/img/integration/vision/wallet/wallet6.png b/static/img/integration/vision/wallet/wallet6.png
new file mode 100644
index 0000000..36c941e
Binary files /dev/null and b/static/img/integration/vision/wallet/wallet6.png differ
diff --git a/static/img/integration/vision/wallet/wallet7.png b/static/img/integration/vision/wallet/wallet7.png
new file mode 100644
index 0000000..7a63425
Binary files /dev/null and b/static/img/integration/vision/wallet/wallet7.png differ
diff --git a/static/img/integration/vision/wallet/wallet8.png b/static/img/integration/vision/wallet/wallet8.png
new file mode 100644
index 0000000..3021fde
Binary files /dev/null and b/static/img/integration/vision/wallet/wallet8.png differ
diff --git a/static/img/integration/vision/wallet/wallet9.png b/static/img/integration/vision/wallet/wallet9.png
new file mode 100644
index 0000000..fde6e02
Binary files /dev/null and b/static/img/integration/vision/wallet/wallet9.png differ