diff --git a/images/eploy/assess-bcs/eploy_activate_workflow.png b/images/eploy/assess-bcs/eploy_activate_workflow.png
new file mode 100644
index 00000000..3e027415
Binary files /dev/null and b/images/eploy/assess-bcs/eploy_activate_workflow.png differ
diff --git a/images/eploy/assess-bcs/eploy_add_integration_stage.png b/images/eploy/assess-bcs/eploy_add_integration_stage.png
new file mode 100644
index 00000000..decb2dd7
Binary files /dev/null and b/images/eploy/assess-bcs/eploy_add_integration_stage.png differ
diff --git a/images/eploy/assess-bcs/eploy_add_integration_stage_hub.png b/images/eploy/assess-bcs/eploy_add_integration_stage_hub.png
new file mode 100644
index 00000000..5f438ea2
Binary files /dev/null and b/images/eploy/assess-bcs/eploy_add_integration_stage_hub.png differ
diff --git a/images/eploy/assess-bcs/eploy_add_or_edit_stage_form.png b/images/eploy/assess-bcs/eploy_add_or_edit_stage_form.png
new file mode 100644
index 00000000..ed9bdfa7
Binary files /dev/null and b/images/eploy/assess-bcs/eploy_add_or_edit_stage_form.png differ
diff --git a/images/eploy/assess-bcs/eploy_add_stage_button.png b/images/eploy/assess-bcs/eploy_add_stage_button.png
new file mode 100644
index 00000000..e49c874f
Binary files /dev/null and b/images/eploy/assess-bcs/eploy_add_stage_button.png differ
diff --git a/images/eploy/assess-bcs/eploy_add_webhook.png b/images/eploy/assess-bcs/eploy_add_webhook.png
new file mode 100644
index 00000000..07733888
Binary files /dev/null and b/images/eploy/assess-bcs/eploy_add_webhook.png differ
diff --git a/images/eploy/assess-bcs/eploy_bc_assess_config_form.png b/images/eploy/assess-bcs/eploy_bc_assess_config_form.png
new file mode 100644
index 00000000..47b41147
Binary files /dev/null and b/images/eploy/assess-bcs/eploy_bc_assess_config_form.png differ
diff --git a/images/eploy/assess-bcs/eploy_bc_assess_enable_1.png b/images/eploy/assess-bcs/eploy_bc_assess_enable_1.png
new file mode 100644
index 00000000..55f28a4c
Binary files /dev/null and b/images/eploy/assess-bcs/eploy_bc_assess_enable_1.png differ
diff --git a/images/eploy/assess-bcs/eploy_bc_assess_process_flow_diagram_4.png b/images/eploy/assess-bcs/eploy_bc_assess_process_flow_diagram_4.png
new file mode 100644
index 00000000..b71b8293
Binary files /dev/null and b/images/eploy/assess-bcs/eploy_bc_assess_process_flow_diagram_4.png differ
diff --git a/images/eploy/assess-bcs/eploy_bc_assess_process_sequence_diagram_7.png b/images/eploy/assess-bcs/eploy_bc_assess_process_sequence_diagram_7.png
new file mode 100644
index 00000000..40031209
Binary files /dev/null and b/images/eploy/assess-bcs/eploy_bc_assess_process_sequence_diagram_7.png differ
diff --git a/images/eploy/assess-bcs/eploy_bc_move_candidate_integration_stage.png b/images/eploy/assess-bcs/eploy_bc_move_candidate_integration_stage.png
new file mode 100644
index 00000000..ff6998b3
Binary files /dev/null and b/images/eploy/assess-bcs/eploy_bc_move_candidate_integration_stage.png differ
diff --git a/images/eploy/assess-bcs/eploy_bc_on_update_result_of_bc_on_ui.png b/images/eploy/assess-bcs/eploy_bc_on_update_result_of_bc_on_ui.png
new file mode 100644
index 00000000..c6623372
Binary files /dev/null and b/images/eploy/assess-bcs/eploy_bc_on_update_result_of_bc_on_ui.png differ
diff --git a/images/eploy/assess-bcs/eploy_bc_on_update_result_of_bc_on_ui_6.png b/images/eploy/assess-bcs/eploy_bc_on_update_result_of_bc_on_ui_6.png
new file mode 100644
index 00000000..fe7fb1e2
Binary files /dev/null and b/images/eploy/assess-bcs/eploy_bc_on_update_result_of_bc_on_ui_6.png differ
diff --git a/images/eploy/assess-bcs/eploy_bc_sent_to_the_candidate_as_visible_package_name_on_ui.png b/images/eploy/assess-bcs/eploy_bc_sent_to_the_candidate_as_visible_package_name_on_ui.png
new file mode 100644
index 00000000..29c4fd96
Binary files /dev/null and b/images/eploy/assess-bcs/eploy_bc_sent_to_the_candidate_as_visible_package_name_on_ui.png differ
diff --git a/images/eploy/assess-bcs/eploy_bc_sent_to_the_candidate_as_visible_package_name_on_ui_5.png b/images/eploy/assess-bcs/eploy_bc_sent_to_the_candidate_as_visible_package_name_on_ui_5.png
new file mode 100644
index 00000000..90f382df
Binary files /dev/null and b/images/eploy/assess-bcs/eploy_bc_sent_to_the_candidate_as_visible_package_name_on_ui_5.png differ
diff --git a/images/eploy/assess-bcs/eploy_candidate_created_and_apply_to_vacancy.png b/images/eploy/assess-bcs/eploy_candidate_created_and_apply_to_vacancy.png
new file mode 100644
index 00000000..79e50895
Binary files /dev/null and b/images/eploy/assess-bcs/eploy_candidate_created_and_apply_to_vacancy.png differ
diff --git a/images/eploy/assess-bcs/eploy_candidate_in_pipeline.png b/images/eploy/assess-bcs/eploy_candidate_in_pipeline.png
new file mode 100644
index 00000000..11635c28
Binary files /dev/null and b/images/eploy/assess-bcs/eploy_candidate_in_pipeline.png differ
diff --git a/images/eploy/assess-bcs/eploy_candidate_in_pipeline_hub.png b/images/eploy/assess-bcs/eploy_candidate_in_pipeline_hub.png
new file mode 100644
index 00000000..f7becd77
Binary files /dev/null and b/images/eploy/assess-bcs/eploy_candidate_in_pipeline_hub.png differ
diff --git a/images/eploy/assess-bcs/eploy_create_application_form.png b/images/eploy/assess-bcs/eploy_create_application_form.png
new file mode 100644
index 00000000..a643a73e
Binary files /dev/null and b/images/eploy/assess-bcs/eploy_create_application_form.png differ
diff --git a/images/eploy/assess-bcs/eploy_create_candidate_form.png b/images/eploy/assess-bcs/eploy_create_candidate_form.png
new file mode 100644
index 00000000..0847a907
Binary files /dev/null and b/images/eploy/assess-bcs/eploy_create_candidate_form.png differ
diff --git a/images/eploy/assess-bcs/eploy_create_recruitment_workflow_form.png b/images/eploy/assess-bcs/eploy_create_recruitment_workflow_form.png
new file mode 100644
index 00000000..7552689c
Binary files /dev/null and b/images/eploy/assess-bcs/eploy_create_recruitment_workflow_form.png differ
diff --git a/images/eploy/assess-bcs/eploy_create_vacancy.png b/images/eploy/assess-bcs/eploy_create_vacancy.png
new file mode 100644
index 00000000..a8c897df
Binary files /dev/null and b/images/eploy/assess-bcs/eploy_create_vacancy.png differ
diff --git a/images/eploy/assess-bcs/eploy_created_vacancy_page.png b/images/eploy/assess-bcs/eploy_created_vacancy_page.png
new file mode 100644
index 00000000..c3279ac4
Binary files /dev/null and b/images/eploy/assess-bcs/eploy_created_vacancy_page.png differ
diff --git a/images/eploy/assess-bcs/eploy_edit_additional_details.png b/images/eploy/assess-bcs/eploy_edit_additional_details.png
new file mode 100644
index 00000000..c5d93e6d
Binary files /dev/null and b/images/eploy/assess-bcs/eploy_edit_additional_details.png differ
diff --git a/images/eploy/assess-bcs/eploy_marketplace.png b/images/eploy/assess-bcs/eploy_marketplace.png
new file mode 100644
index 00000000..e7107c93
Binary files /dev/null and b/images/eploy/assess-bcs/eploy_marketplace.png differ
diff --git a/images/eploy/assess-bcs/eploy_marketplace_request_form.png b/images/eploy/assess-bcs/eploy_marketplace_request_form.png
new file mode 100644
index 00000000..084ff374
Binary files /dev/null and b/images/eploy/assess-bcs/eploy_marketplace_request_form.png differ
diff --git a/images/eploy/assess-bcs/eploy_navigate_to_additional_details_page_of_vacancy.png b/images/eploy/assess-bcs/eploy_navigate_to_additional_details_page_of_vacancy.png
new file mode 100644
index 00000000..9f099dfc
Binary files /dev/null and b/images/eploy/assess-bcs/eploy_navigate_to_additional_details_page_of_vacancy.png differ
diff --git a/images/eploy/assess-bcs/eploy_navigate_to_candidates.png b/images/eploy/assess-bcs/eploy_navigate_to_candidates.png
new file mode 100644
index 00000000..a4dc0911
Binary files /dev/null and b/images/eploy/assess-bcs/eploy_navigate_to_candidates.png differ
diff --git a/images/eploy/assess-bcs/eploy_navigate_to_recruitment_workflow.png b/images/eploy/assess-bcs/eploy_navigate_to_recruitment_workflow.png
new file mode 100644
index 00000000..f667db7b
Binary files /dev/null and b/images/eploy/assess-bcs/eploy_navigate_to_recruitment_workflow.png differ
diff --git a/images/eploy/assess-bcs/eploy_navigate_to_vacancy_pipeline.png b/images/eploy/assess-bcs/eploy_navigate_to_vacancy_pipeline.png
new file mode 100644
index 00000000..73fc1e07
Binary files /dev/null and b/images/eploy/assess-bcs/eploy_navigate_to_vacancy_pipeline.png differ
diff --git a/images/eploy/assess-bcs/eploy_new_recruitment_workflow.png b/images/eploy/assess-bcs/eploy_new_recruitment_workflow.png
new file mode 100644
index 00000000..1406e7b2
Binary files /dev/null and b/images/eploy/assess-bcs/eploy_new_recruitment_workflow.png differ
diff --git a/images/eploy/assess-bcs/eploy_selected_bc_visible_on_vacnacy_page.png b/images/eploy/assess-bcs/eploy_selected_bc_visible_on_vacnacy_page.png
new file mode 100644
index 00000000..eb1c055e
Binary files /dev/null and b/images/eploy/assess-bcs/eploy_selected_bc_visible_on_vacnacy_page.png differ
diff --git a/images/eploy/assess-bcs/eploy_stage_appear_in_the_workflow.png b/images/eploy/assess-bcs/eploy_stage_appear_in_the_workflow.png
new file mode 100644
index 00000000..da3d3491
Binary files /dev/null and b/images/eploy/assess-bcs/eploy_stage_appear_in_the_workflow.png differ
diff --git a/images/eploy/assess-bcs/eploy_stage_appear_in_the_workflow_hub.png b/images/eploy/assess-bcs/eploy_stage_appear_in_the_workflow_hub.png
new file mode 100644
index 00000000..85df8c18
Binary files /dev/null and b/images/eploy/assess-bcs/eploy_stage_appear_in_the_workflow_hub.png differ
diff --git a/images/eploy/assess-bcs/eploy_vacancy_navigation.png b/images/eploy/assess-bcs/eploy_vacancy_navigation.png
new file mode 100644
index 00000000..2e2f421f
Binary files /dev/null and b/images/eploy/assess-bcs/eploy_vacancy_navigation.png differ
diff --git a/images/eploy/assess-bcs/eploy_vacancy_stage_appears.png b/images/eploy/assess-bcs/eploy_vacancy_stage_appears.png
new file mode 100644
index 00000000..3a9913ad
Binary files /dev/null and b/images/eploy/assess-bcs/eploy_vacancy_stage_appears.png differ
diff --git a/images/eploy/assess-bcs/eploy_vacancy_stage_appears_hub.png b/images/eploy/assess-bcs/eploy_vacancy_stage_appears_hub.png
new file mode 100644
index 00000000..ee5beef2
Binary files /dev/null and b/images/eploy/assess-bcs/eploy_vacancy_stage_appears_hub.png differ
diff --git a/images/eploy/assess-bcs/eploy_webhook_event.png b/images/eploy/assess-bcs/eploy_webhook_event.png
new file mode 100644
index 00000000..5ff6c81f
Binary files /dev/null and b/images/eploy/assess-bcs/eploy_webhook_event.png differ
diff --git a/images/eploy/assess-bcs/eploy_workflow_add_stage.png b/images/eploy/assess-bcs/eploy_workflow_add_stage.png
new file mode 100644
index 00000000..bfa60f60
Binary files /dev/null and b/images/eploy/assess-bcs/eploy_workflow_add_stage.png differ
diff --git a/images/eploy/assess-bcs/eploy_workflow_stage_added.png b/images/eploy/assess-bcs/eploy_workflow_stage_added.png
new file mode 100644
index 00000000..5cbc7643
Binary files /dev/null and b/images/eploy/assess-bcs/eploy_workflow_stage_added.png differ
diff --git a/images/eploy/assess-bcs/eploy_workflow_visible_in_grid.png b/images/eploy/assess-bcs/eploy_workflow_visible_in_grid.png
new file mode 100644
index 00000000..6f08cfc7
Binary files /dev/null and b/images/eploy/assess-bcs/eploy_workflow_visible_in_grid.png differ
diff --git a/integration-configuration-concepts/ats/eploy-background-check.mdx b/integration-configuration-concepts/ats/eploy-background-check.mdx
index 7838221f..aad681f1 100644
--- a/integration-configuration-concepts/ats/eploy-background-check.mdx
+++ b/integration-configuration-concepts/ats/eploy-background-check.mdx
@@ -9,180 +9,190 @@ import IntegrationFooter from "/snippets/integration-footer.mdx";
This guidance assumes that you have admin privileges for your Eploy account.
-
- Please reach out to your integration partner to add an integration stage to the recruitment workflow. Once you move the candidate to that integration stage, the background check will be triggered.
-
- To configure further in Eploy for background checks, please follow the steps outlined below.
-
-
-## Add a custom option for background check packages
-
-
-
- Navigate to the _Custom Fields_ page by selecting _Customize Fields_ from the _Admin_ menu
-
-
-
-
- Navigate to the _User Option Types_ tab and click the `New` button to create a new custom option in Eploy
-
-
-
-
- Enter the title as `Background Checks` and then click the `Save` button
-
- Please use the name `Background Checks`, as this is necessary to ensure that you receive notifications from Eploy.
-
-
-
-
-
- The newly created `Background Checks` option will be visible in the _User Option Types_ grid
-
-
-
-
-
-
-
-## Add a custom field within the vacancy group
-
-
-
- Navigate to the _Custom Fields_ page by selecting _Customise Fields_ from the _Admin_ menu
-
-
-
-
- Navigate to the _Fields_ tab and click the `New` > `Input Field` button to create a new input field in Eploy
-
-
-
-
- Select the field values according to the instructions below:
-
- Please ensure you select the same values as suggested to receive Eploy notifications.
-
-
- - **Field Group:** Select `Additional Details (Vacancies)`
- - **Field Type:** Select `Input - Drop-down`
- - **Display Format:** Select `Hierarchy List Searchable`
- - **Option Type:** Select `Background Checks` (As you have created in above [step](#add-a-custom-option-for-background-check-packages))
- - **Insert Below:** You can select any value here, it will determine where the field appears in the form
- - **Active:** Ensure this field is marked as active
- - **Field Label:** Select `Background Checks`
- - **Help Description:** You may include any relevant description
-
- Click the `Save` button
-
-
-
-
- The newly created `Background Checks` field will be visible in the _Fields_ grid
-
-
-
-
-
-
-
-## Add background check packages
-
-
- You can ask your integration partner to add the background check packages, or you can follow the steps outlined below to add them manually.
-
-
-
-
- Navigate to the _Drop Down Lists_ page located in the _Admin_ menu
-
-
-
-
- Select `Background Checks` and click the `New` button to create a new package in Eploy
-
-
-
-
- Enter the following field values:
-
- - **Description:** This will be the label displayed in the dropdown list.
- - **Reference:** This can be any string and will not appear in the dropdown list.
-
- Click the `Save` button.
-
-
-
-
- The newly created background check package will be visible in the grid
-
-
-
-
-
-
-
-## Configure the background check package for the vacancy
-
-
-
- Go to the _Additional Details_ page for specific job vacancies created within the Recruitment Workflow that includes the background check integration stage.
-
-
-
-
- Edit Additional Details, to select the background check package,
-
-
-
-
- The selected background check package will be displayed on the _Additional Details_ page
-
-
-
-
-
+
+## Enable the Partner's Integration App in your Eploy account
+
+To enable the Eploy Technology Partner app and make it available as a stage within a Recruitment Workflow, go to the [Eploy Marketplace](https://www.eploy.com/product/eploy-marketplace).
+
+ 
+
+
+Click the partner's app in the Marketplace that you want to enable. It will direct you to the [Integrate your Eploy with Partner form](https://www.eploy.com/partner/technology-partners).
+Fill out the form to initiate your request to enable the integration app.
+
+ 
+
+
+Once the partner's app is enabled, it appears in the **Stages** dropdown when creating or editing Recruitment Workflows.
+
+
+ Visit the [Add a Recruitment Workflow](#add-a-recruitment-workflow) section to verify if the partner's integration app is enabled and visible in the Stages dropdown.
+
+
+
+## Add a Recruitment Workflow
+
+Navigate to the _Recruitment Workflow_ page from the _Admin_ menu.
+
+ 
+
+
+Click the `+ New` button to create a new workflow.
+
+ 
+
+
+Fill out the necessary fields in the _Create Recruitment Workflow_ form as per the requirements, and click `Save`.
+
+ 
+
+
+Scroll down and click the `Add` button to add stages in the workflow.
+
+ 
+
+
+You can choose various stages as per the requirements and select the partner's integration app stage from the Stages dropdown to trigger the background check notification.
+
+For the partner's integration app stage, select the following values:
+- **Stage Name:** Select the partner's integration app name.
+
+
+ If your partner's integration app is enabled, it'll appear in the **Stages** dropdown such as `Your Integration Stage`, else contact Eploy support to enable the integration app.
+
+
+- **Stage Type:** Select `Actions`.
+- **Action Type:** Select the partner's integration app name.
+
+You may configure other settings as per the requirements and click `Save` to add this stage to the workflow.
+
+ 
+
+
+After saving, the stage appears in the workflow.
+
+ 
+
+
+Ensure the workflow is set to `Active` to be visible when creating a vacancy.
+
+ 
+
+
+The newly created workflow appears in the _Recruitment Workflow_ grid.
+
+ 
+
+
+
+## Create a Vacancy in the Workflow
+
+Navigate to the _Vacancy_ page via `+` button in the top menu.
+
+ 
+
+
+Fill out the vacancy form by choosing the **Recruitment Workflow** that includes the partner's integration app stage you added earlier. You can also configure other fields as per the requirements and click `Save`.
+
+ 
+
+
+You will be directed to the vacancy page after saving.
+
+ 
+
+
+You can see the partner's integration app stage in the vacancy's talent pipeline by navigating to `Work on Vacancy` > `Go to Pipeline`.
+
+ 
+
+
+The stage appears in the vacancy's talent pipeline.
+
+ 
+
+
+
+## Select a Background Check package to associate with the vacancy
+
+Navigate to the _Additional Details_ page of the vacancy to select and associate the background check package.
+
+ 
+
+
+Edit the _Additional Details_, select the background check package from the `Background Checks` dropdown, and `Save` the changes.
+
+ 
+
+
+The selected background check package will appear on the _Additional Details_ page.
+
+ 
+
+
+
+## Create a Candidate and add as an applicant to the vacancy
+
+Navigate to the _Candidate_ page via `+` button in the top menu.
+
+ 
+
+
+Fill out the necessary details in the **Create Candidate** form and `Save`.
+
+ 
+
+
+You will be directed to the candidate's profile page after saving, where you can initiate the candidate's application by clicking `Application` under the `+` button menu.
+
+ 
+
+
+Select the **Vacancy** and **Stage**, and then `Save` to add the candidate as an applicant to the vacancy.
+
+ 
+
+
+You can see the candidate added as an applicant to the vacancy by navigating to the vacancy's talent pipeline.
+
+ 
+
+
+The candidate appears in the **Stage** you selected when creating the application.
+
+ 
+
+
+You can move the candidate's application to the partner's integration app stage to trigger the background check.
## Move the candidate within the pipeline
-
-
- To navigate to the _Pipeline_ page, click on the `Go to Pipeline` option located under the `Work on Vacancy` dropdown menu on the vacancy page
-
-
-
+To navigate to the _Pipeline_ page, click on the `Go to Pipeline` option located under the `Work on Vacancy` dropdown menu on the vacancy page
+
+
+
- Move the candidate to the integration stage to initiate the background check invitation
-
-
-
-
-
+Move the candidate to the integration stage to initiate the background check invitation
+
+
+
## To view the sent background check invitation
-
-
- Navigate to the _Pipeline_ page and click on the candidate to check the sent background check invitation
-
-
-
-
-
+Navigate to the _Pipeline_ page and click on the candidate to check the sent background check invitation
+
+
+
## To view the updated result of the background check
-
-
- Go to the _Pipeline_ page and click on the candidate to view the updated result of the background check
-
-
-
-
-
+Go to the _Pipeline_ page and click on the candidate to view the updated result of the background check
+
+
+