# Conditional Logic Dropdown Not Listing All Blocks
Source: https://docs.talview.com/admin/configurations/forms/diagnostics/conditional-logic-dropdown-not-listing-all-blocks
While setting up **Conditional Logic** in Talview Forms, you may notice that **some blocks are not appearing** in the dropdowns for selecting the trigger or target block. This prevents the logic from being configured properly.
## ✅ Common Issues and Fixes
| **What Might Be Wrong** | **What You Can Do** |
| :--------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| The trigger block is not a valid type | Only **Dropdown**, **Radio Button**, or **Checkbox** blocks can be used as trigger blocks. Use one of these input types to trigger logic. |
| Trigger or target block is **not named** | Both the **trigger** block and the **target** block must be assigned a **name** in their settings. Unnamed blocks will not appear in the dropdowns. |
| A block is already used as a trigger | Blocks that are already being used as a **trigger in another logic** cannot be reused as a **target**, and vice versa. Remove the existing usage if needed. |
## 🌐 Final Check: Making It Work
To resolve the issue:
* Use a **radio, checkbox, or dropdown** block as the trigger
* Ensure **both trigger and target blocks are named**
* Make sure the target block is **not already being used as a trigger**
Then:
* Open the Conditional Logic settings
* Select the named trigger block from the dropdown
* Set the show/hide conditions for the named target block
### Additional Tips
* The **trigger** block is the one that users interact with (e.g., a dropdown), and the **target** block is the one shown/hidden based on that selection.
* All blocks, regardless of type, can be used as **targets** — as long as they are named and not already being used as triggers.
* Conditional Logic **will not work** between unnamed blocks or blocks already linked in reverse roles.
# Created Field Not Visible in Form Preview
Source: https://docs.talview.com/admin/configurations/forms/diagnostics/created-field-not-visible-in-form-preview
If you’ve added a field in the Talview Form Builder but it’s missing when you preview the form, it could be due to one of the reasons below.
## ✅ Common Reasons and Fixes
| **What Might Be Wrong** | **What You Can Do** |
| :---------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| The field is set to “Hidden” | Click on the field in the builder and **check if "Hide field" is enabled** under "More Options". If yes, disable it to make the field visible in preview. |
| Builder session expired due to inactivity | If you stepped away for long, the session might have expired **without warning**, and your recent changes weren’t saved. Refresh the page and **check if the field still exists** in the builder. |
| Field is part of conditional logic | If the field is configured to **only show based on a trigger**, ensure the right condition is met in the preview. |
| Browser cache or preview glitch | Try **refreshing the preview**, or open the preview in an **incognito window** to rule out local caching issues. |
# Embedded Image Link Not Rendering in Form
Source: https://docs.talview.com/admin/configurations/forms/diagnostics/embedded-image-link-not-rendering-in-form
You’ve added an image link to a form block in Talview’s Form Builder, but it’s not showing up in the preview. This article helps you identify and fix the issue.
## ✅ Common Causes and Fixes
| **What Might Be Wrong** | **What You Can Do** |
| :---------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------ |
| Image is hosted on a **restricted or private server** | Use a publicly accessible image hosting platform like **Imgur**, **Dropbox (public share)**, or **Google Drive with link sharing enabled**. |
| Link is broken or outdated | Test the URL in a separate browser tab. If it doesn’t load the image, use a new working link. |
| Link contains unnecessary URL parameters | Clean up the URL — remove tracking parameters or redirects that might block image loading. |
| Pasted in wrong field | Confirm that the image link is pasted in the **Image URL field** under the block’s configuration settings. |
## 🌐 Final Check
* Go to **Form Preview**
* If the image still doesn’t load, try the same link in an **incognito tab** to ensure it's publicly accessible
## Best Practices for Embedding
* Use **HTTPS links** to ensure security and compatibility
* Host your images on platforms that **don’t expire links**
* Prefer **lightweight images** to avoid slow rendering
# Form Layout Stuck in Single-Column View
Source: https://docs.talview.com/admin/configurations/forms/diagnostics/form-layout-stuck-in-single-column-view
If your form appears in a single-column view even after selecting different layout types in the Form Builder, it may not be an issue with the layout configuration itself —but rather a misunderstanding of how layout preview works.
## ✅ Common Issues and Fixes
| **What Might Be Wrong** | **What You Can Do** |
| :------------------------------------------------------------------- | :----------------------------------------------------------------------------------------------------------------------- |
| All blocks are set to **Layout 1 – Monogrid** | Use the **Layout** dropdown in each block's settings and change to Layout 2 or Layout 3 as needed. |
| You’re expecting layout changes to reflect inside the builder canvas | Layouts **only reflect in the Preview screen**, not in the builder canvas. Click **Preview Form** to view actual layout. |
## 🌐 Final Check: Layout Visibility
Once you’ve selected Layout 2 or 3 for multiple blocks:
* Click **Preview Form**
* Check if blocks are displayed side-by-side or in multiple columns
* If not, revisit each block’s layout setting
### Additional Tips
* Start assigning Layout 2 or Layout 3 from the **second block onward** — the first block is always set to Layout 1 by default.
* Make sure you’ve clicked **Save** after selecting layout options.
* Use the **Preview Form** option regularly while building to confirm layout changes are applied as expected.
# Forms Application Missing from Platform Dashboard
Source: https://docs.talview.com/admin/configurations/forms/diagnostics/forms-application-missing-from-platform-dashboard
If you’re unable to see the **Forms** application on your Talview dashboard, it’s likely due to permission restrictions or plan limitations. Use the checklist below to identify and resolve the issue.
## ✅ Common Causes and Fixes
| **What Might Be Wrong** | **What You Should Do** |
| :---------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------- |
| **Forms is not included in your organization’s plan** | Contact your internal Talview Admin or reach out to **Talview Support** to confirm whether the **Forms** module is enabled for your account. |
| **You don’t have permission to access Forms** | Only users with Admin role can access and create Forms. Ask another Admin to verify your role and **assign you the admin role**. |
| **Platform dashboard didn’t load completely** | Try **refreshing the page**, clearing your browser cache, or opening in an **incognito window**. |
| **You recently got access to Forms** | If access was just enabled, try logging out and back in, or **wait a few minutes** for the change to reflect. |
| **Logged into the wrong account** | Double-check if you’re logged into the correct **organization workspace**. Logout and re-login if needed. |
# Talview Form Features
Source: https://docs.talview.com/admin/configurations/forms/feature-page/talview-form-features
> This document provides an overview of all available features in the Talview Form Builder, covering input types, formatting options, field configuration, and layout controls.
***
## 1. Input Collection Features
These are the core building blocks for capturing information from your users.
| Feature | Description |
| :------------------ | :----------------------------------------------------------------------------- |
| **Short Text** | Captures single-line input such as names, titles, or short identifiers |
| **Long Text** | Captures multi-line input for detailed descriptions, comments, or explanations |
| **Multiple Choice** | Allows users to select one option from a predefined list |
| **Checkbox** | Allows users to select multiple options from a predefined list |
| **Dropdown** | Provides a collapsible list of options for single selection |
| **Number** | Accepts numeric-only input to ensure numerical data accuracy |
| **Email** | Captures email addresses in a structured format |
| **Phone Number** | Captures contact numbers using a dedicated phone input field |
| **Date** | Allows users to select a date through a calendar interface |
| **File Upload** | Enables users to attach documents or files within the form |
| **Photo Capture** | Allows users to capture and upload images directly from their devicec |
***
## 2. Content & Formatting Features
Use these blocks to add context, instructions, and structure to your form content.
| Feature | Description |
| :---------------- | :--------------------------------------------------------------------------- |
| **Quote Block** | Displays highlighted text to emphasize important information or instructions |
| **Bullet List** | Presents information in an unordered list format |
| **Numbered List** | Displays content in a sequentially numbered format |
| **Check List** | Creates an interactive checklist where items can be marked as completed |
| **Toggle List** | Creates expandable and collapsible sections to manage long content |
| **Code Block** | Displays formatted code with syntax highlighting for technical content |
***
## 3. Hierarchical Structuring Features
Organise your form into clear, collapsible sections using heading-based toggles.
| Feature | Description |
| :------------------------ | :---------------------------------------------------------------------- |
| **Toggle Heading 1 (H1)** | Creates a top-level collapsible section for organising major form areas |
| **Toggle Heading 2 (H2)** | Creates a secondary collapsible section within main sections |
| **Toggle Heading 3 (H3)** | Creates subsection-level collapsible groupings within sections |
***
## 4. Media Embedding Features
Enrich your forms with visual and video content to guide users effectively.
| Feature | Description |
| :-------------- | :------------------------------------------------------------------------------- |
| **Video Block** | Embeds video content within the form for instructional or informational purposes |
| **Image Block** | Embeds images within the form to provide visual context or references |
***
## 5. Structural Grouping Features
Logically group related fields together to improve form flow and readability.
| Feature | Description |
| :---------------------- | :----------------------------------------------------------- |
| **Section Group Start** | Marks the beginning of a logically grouped section of fields |
| **Section Group End** | Marks the end of a logically grouped section of fields |
***
## 6. Advanced Features
Take your forms further with intelligent, dynamic behaviour.
| Feature | Description |
| :-------------------- | :---------------------------------------------------------------------------- |
| **Conditional Logic** | Controls the dynamic visibility of fields or sections based on user responses |
***
## 7. Field Configuration Features
Fine-tune how each field behaves, appears, and validates input.
| Feature | Description |
| :------------------- | :--------------------------------------------------------------------------- |
| **Field Identifier** | Defines the internal reference name used for backend mapping or integrations |
| **Label** | Defines the visible name displayed to users for the field |
| **Required** | Marks a field as mandatory before form submission |
| **Disable Field** | Makes a field visible but non-editable |
| **Updatable Field** | Controls whether a field can be edited after submission |
| **Tooltip** | Provides contextual helper information for users interacting with a field |
| **Placeholder** | Displays example text inside the field before user input |
| **Default Value** | Pre-populates a field with a predefined value |
| **Minimum Length** | Sets the minimum number of characters allowed for input |
| **Maximum Length** | Sets the maximum number of characters allowed for input |
| **Regex Validation** | Applies pattern-based validation rules for advanced input control |
***
## 8. Layout & Design Features
Control the visual arrangement and management of fields within your form.
| Feature | Description |
| :------------------------------------ | :------------------------------------------------------------------- |
| **Column Layout (1 / 2 / 3 Columns)** | Controls how fields are arranged horizontally within the form layout |
| **Row Span** | Determines how much vertical grid space a field occupies |
| **Delete** | Removes a field from the form |
| **Hide** | Temporarily hides a field without deleting it |
| **Duplicate** | Creates a copy of an existing field with the same configuration |
***
## Form embedded in different applications
### 1. Candidate form on the CX application (Web)
### 2. Candidate form on CX application (Mobile view)
### **3. Candidate form on the attend-ng application (Web)**
### **4. Evaluation form on Workflow tools application**
### **5. Evaluation form on workflow tools application (Mobile view)**
### 6. Evaluation form on the Recruit web application
### 7. Evaluation form on the Recruit (Mobile view)
***
# Getting Started with Integrations
Source: https://docs.talview.com/admin/configurations/integrations/getting-started
Set up and manage integrations with your ATS, LMS, SSO, Calendar, Assessments, and Payments to streamline your hiring and certification workflows.
Connect your ATS (e.g., Workday, Greenhouse, SuccessFactors) to seamlessly manage candidate data and hiring workflows.
Integrate your LMS (e.g., Moodle, Canvas, Cornerstone) to deliver training, exams, and certifications at scale.
Enable secure SSO with Google or Azure AD for seamless access across your organization.
Sync with Google or Microsoft calendars to schedule, reschedule, and manage interviews.
Connect assessment providers (e.g., HackerEarth, Imocha, Inspera) to conduct coding, cognitive, and psychometric tests.
Enable secure candidate payments with providers like Stripe, Lemon Squeezy, and Cleverbridge.
# How to attempt a proctored canvas classic quiz
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/candidate/canvas/canvas-attempt-classic-quiz
Once the proctored quiz has been configured and made available, test takers can follow these steps to attempt the quiz.
Note: In order to get the password required to start the proctored quiz, ensure the Proview Proctoring extension is installed. You can get it from [here](https://chromewebstore.google.com/detail/proview-proctoring/doblkllolfingbjkbmelgiepdggnbmhi).
**1. Accessing the quiz**
* Log into Canvas LMS.
* Go to the course where the proctored quiz is available.
* From the quiz list, select the proctored quiz you need to attempt.
* Click on the quiz name to see the quiz description and instructions.
**2. Live proctored quiz requirement**
* If the quiz is live proctored, a side panel will open with a message informing you that you need to book a slot before starting the quiz.
* Click on the **Manage Booking** button. This will load a calendar in the same side panel where you can view available dates and times.
* Select a date and time slot that works for you and click **Confirm**.
* You will see an acknowledgement message confirming your booking.
* After booking, click the close icon at the top right to return to the quiz description page.
You can only start the quiz 30 minutes before your scheduled time.
**3. Starting the quiz**
* The quiz is password-protected, and the password will be injected automatically. Simply click on the **Start Quiz** button.
If the Proview browser extension has not been installed, an error message will appear, containing instructions and a link to install the extension.
* Once installed, acknowledge the web page’s prompt and refresh the screen.
* The code will then get injected to access the quiz.
* **Proctoring Pre-Flight Checks**: An iframe will load, and the proctoring pre-flight checks will begin.
* Once you successfully pass all pre-flight checks, the quiz questions will appear, and proctoring will begin in the background.
**4. Completing the quiz**
* Attempt all of the quiz questions and then click on **Submit Quiz.**
* Click on the **Stop Proctoring** button at the top right of the screen.
* A confirmation message will pop up, click **OK**. Ensure you have attempted all the questions before confirming to end the proctoring.
* Optionally, provide feedback on the proctoring experience.
* After stopping proctoring, you will be redirected back to the Canvas LMS home page.
# How to attempt a proctored new quiz
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/candidate/canvas/canvas-attempt-new-quiz
Once the proctored quiz has been configured and made available, test takers can follow these steps to attempt the quiz.
Note: In order to get the password required to start the proctored quiz, ensure the Proview Proctoring extension is installed. You can get it from [here](https://chromewebstore.google.com/detail/proview-proctoring/doblkllolfingbjkbmelgiepdggnbmhi).
**1. Accessing the quiz**
* Log into Canvas LMS.
* Go to the course where the proctored quiz is available.
* From the quiz list, select the proctored quiz you need to attempt.
* Click on the quiz name to see the quiz description and instructions.
**2. Live proctored quiz requirement**
* If the quiz is live proctored, a side panel will open with a message informing you that you need to book a slot before starting the quiz.
* Click on the **Manage Booking** button. This will load a calendar in the same side panel where you can view available dates and times.
* Select a date and time slot that works for you and click **Confirm**.
* You will see an acknowledgement message confirming your booking.
* After booking, click the close icon at the top right to return to the quiz description page.
You can only start the quiz 30 minutes before your scheduled time.
**3. Starting the quiz**
* Click on the **Start Quiz** button.
* **Proctoring Pre-Flight Checks**: An iframe will load, and the proctoring pre-flight checks will begin.
* Once you successfully pass all pre-flight checks, the quiz questions will appear, and proctoring will begin in the background.
**4. Completing the quiz**
* Attempt all of the quiz questions and then click on **Submit Quiz.**
* Click on the **Stop Proctoring** button at the top right of the screen.
* A confirmation message will pop up, click **OK**. Ensure you have attempted all the questions before confirming to end the proctoring.
* Optionally, provide feedback on the proctoring experience.
* After stopping proctoring, you will be redirected back to the home page.
# How to attempt a proctored quiz
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/candidate/cornerstone/csod-attempt-proctored-quiz
Once the proctored quiz has been configured and made available, test takers can follow these steps to attempt it.
Note: In order to attempt the proctored quiz, ensure the Proview Proctoring extension is installed. You can get it from [here](https://chromewebstore.google.com/detail/proview-proctoring/doblkllolfingbjkbmelgiepdggnbmhi)
**1. Accessing the quiz**
* Navigate to [this URL](https://pages.talview.com/proview/csod/test/), and click on **Launch Proview.**
* Enter the course LOID and user ID.
* Next, enter the following details.
**2. Completing the lesson**
* Attempt all of the lesson questions and then click on **Submit.**
* Click on the **Stop Proctoring** button at the top right of the screen.
* A confirmation message will pop up, click **OK**. Ensure you have attempted all the questions before confirming to end the proctoring.
* Optionally, provide feedback on the proctoring experience.
* After stopping proctoring, you will be redirected back to the home page.
# How to attempt a proctored quiz
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/candidate/d2l-brightspace/d2l-attempt-proctored-quiz
Once the proctored quiz has been configured and made available, test takers can follow these steps to attempt the quiz.
In order to get the password required to start the proctored quiz, ensure the Proview Proctoring extension is installed. You can get it from [here](https://chromewebstore.google.com/detail/proview-proctoring/doblkllolfingbjkbmelgiepdggnbmhi)
**1. Accessing the Quiz**
* Log into D2L Brightspace LMS.
* Go to the course where the proctored quiz is available.
* From the quiz list, select the proctored quiz you need to attempt.
* Click on the quiz name to see the quiz description and candidate instructions.
**2. Starting the Quiz**
* The quiz is password-protected, and the password will be injected automatically. Simply click on the **Start Quiz** button.
* **Proctoring Pre-Flight Checks**: An iframe will load, and the proctoring pre-flight checks will begin.
* Once you successfully pass all pre-flight checks, the quiz questions will appear, and proctoring will begin in the background.
**3. Completing the Quiz**
* Attempt all of the quiz questions and then click on **Submit Quiz.**
* Click on the **Stop Proctoring** button at the top right of the screen.
* A confirmation message will pop up, click **OK**. Ensure you have attempted all the questions before confirming to end the proctoring.
* Optionally, provide feedback on the proctoring experience.
* After stopping proctoring, you will be redirected back to the D2L LMS home page.
# How to attempt a proctored test
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/candidate/docebo/docebo-attempt-proctored-test
Once the proctored test has been configured and made available, test takers can follow these steps to attempt it.
Note: In order to start proctored test, ensure the Proview Proctoring extension is installed. You can get it from [here](https://chromewebstore.google.com/detail/proview-proctoring/doblkllolfingbjkbmelgiepdggnbmhi).
## Steps
**1. Accessing the test**
* Log into Docebo LMS.
* Go to the course where the proctored test is available.
* Expand the side panel and from the list, select the proctored test you need to attempt.
**2. Completing the test**
* Upon clicking the test, preflight checks will load.
* Once preflight checks are passed, then proctoring is loaded in another tab, while exam is in another.
* Attempt all of the lesson questions and then click on **Submit.**
* Click on the **Stop Proctoring** button at the top right of the screen.
* A confirmation message will pop up, click **Stop Proctoring**. Ensure you have attempted all the questions before confirming to end the proctoring.
* Optionally, provide feedback on the proctoring experience.
* After stopping proctoring, you will be redirected back to the home page
## Demo video
# How to attempt a proctored quiz
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/candidate/moodle/moodle-attempt-quiz
Follow these steps to access and view the playback of each student's quiz session attempt.
**1. Access the proctored quiz**
* Use your student credentials to log into Moodle LMS.
* Click on the **My Courses** tab in the navigation panel.
* Click on the desired course to expand its topics, then click on the proctored quiz you want to attempt.
**2. Starting the proctored quiz**
* Click on the **Attempt Quiz** button. This will initiate the proctoring pre-flight checks.
* The system will run through a series of checks to ensure everything is set up correctly for proctoring. Once you've successfully passed these checks, the quiz questions will appear, with proctoring running in the background.
**3. Completing the Quiz**
* Attempt all the questions in the quiz.
* Once you have answered all the questions, click on the **Finish Attempt** button.
* Review the attempt summary to ensure you have answered all questions to your satisfaction.
**4. Submitting the Quiz**
* Click on the **Submit All and Finish** button. A confirmation pop-up message will appear.
* Click on **Submit All and Finish** again in the pop-up to confirm your submission.
**5. Ending the Proctoring Session**
* Click on the **Finish Review** button to end the proctoring session.
* You may choose to provide feedback on your proctoring experience.
* Once done, you will be redirected back to the quiz page.
By following these steps, you will be able to successfully complete your proctored exam in Moodle LMS.
# Candidate Guide - Attempt a Proctored Quiz
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/candidate/moodle_4.5/candidate-guide-attempt-a-proctored-quiz
This guide covers how to attempt a proctored quiz within Moodle 4.5 LMS.
***
### Supported Browsers and Operating Systems
Keep your browser and OS updated to one of the supported versions below to avoid any issues during proctoring sessions.
**Supported Browsers** (latest 3 versions only):
* [Google Chrome](https://www.google.com/chrome/?brand=OPNX\&ds_kid=43700053265395784\&gclid=efe458afb020140252e33e0704417f10\&gclsrc=3p.ds&\&msclkid=efe458afb020140252e33e0704417f10\&utm_source=bing\&utm_medium=cpc\&utm_campaign=1707332%20%7C%20Chrome%20Win11%20%7C%20DR%20%7C%20ESS01%20%7C%20APAC%20%7C%20IN%20%7C%20en%20%7C%20Desk%20%7C%20SEM%20%7C%20BKWS%20-%20EXA%20%7C%20Txt%20%7C%20Bing\&utm_term=install%20chrome\&utm_content=Desk%20%7C%20BKWS%20-%20EXA%20%7C%20Txt_Install\&gclid=efe458afb020140252e33e0704417f10\&gclsrc=3p.ds)
* [Microsoft Edge](https://www.microsoft.com/en-us/edge/download?form=MA13FJ)
**Supported Operating Systems:**
* **Windows Devices**: Windows 10 and Windows 11
* **Apple Devices**: macOS Sonoma (14.6.1), macOS Ventura (13.6.9), macOS Monterey (12.7.6).
***
### Steps to Attempt a Proctored Quiz
1. Navigate to the relevant course and click on the proctored quiz you want to attempt.
2. Click the **Attempt Quiz** button to begin.
3. Complete all onboarding checks as prompted.
4. Once onboarding is successfully completed, the quiz questions will appear with proctoring running in the background.
5. Answer all questions, then click **Finish Attempt**, followed by **Submit All and Finish**.
6. In the confirmation modal, click **Submit and Finish** again to confirm your submission.
7. Click the **Finish Review** button to formally end the proctoring session and complete the quiz.
**Important:** You must click **Finish Review** to end proctoring and mark the session as complete. If this step is skipped, the proctoring session will remain active and appear as "in progress".
**Demo video:**
# How to attempt a proctored quiz
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/candidate/moodle_4.5/moodle_4.5-attempt-proctored-quiz
Once the proctored quiz has been configured and made available, test takers can follow these steps to attempt the quiz.
In order to start the proctored quiz, ensure the Proview Proctoring extension is installed. You can get it from [here](https://chromewebstore.google.com/detail/proview-proctoring/doblkllolfingbjkbmelgiepdggnbmhi).
## Steps
**1. Accessing the quiz**
* Log into Moodle LMS.
* Go to the course where the proctored quiz is available.
* From the quiz list, select the proctored quiz you need to attempt.
* Click on the quiz name to see the quiz description and instructions.
**2. Starting the quiz**
* Click on the **Start Quiz** button.
* **Proctoring Pre-Flight Checks**: An iframe will load, and the proctoring pre-flight checks will begin.
* Once you successfully pass all pre-flight checks, the quiz questions will appear, and proctoring will begin in the background.
**3. Completing the quiz & ending proctoring**
* Attempt all of the quiz questions and then click on the **Submit all and Finish** button.
* Optionally, provide feedback on the proctoring experience.
## Demo video
# How to attempt a proctored Caveon exam
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/candidate/skilljar/skilljar-attempt-caveon
This guide provides a step-by-step process for students on how to attempt a proctored Caveon exam within Skilljar LMS.
**1. Access the quiz**
* Open your web browser and enter the test domain URL provided by your course administrator.
* Append the specific course ID to the URL if required. This will direct you to the correct course page.
**2. Register or Sign In**
* If you are a new user, you need to **register** for an account. Follow the registration prompts and provide the necessary information to create your account.
* If you already have an account, simply **sign in** using your valid credentials (username and password).
**3. Start the quiz**
* After logging in, click on the **“Start”** button to begin the quiz.
**4. Proctoring Pre-Flight Checks**
* Clicking on **“Start”** will initiate the **proctoring pre-flight checks**. This step ensures that all necessary proctoring measures are in place before you begin the quiz.
**5. Take the Quiz**
* Proceed to answer all the questions as per the instructions provided in the quiz.
* Click on **Yes** in the confirmation messages to submit the quiz.
* Click on **End Lesson** button to end the proctoring, you will then be directed back to course home page.
# How to attempt a proctored LTI lesson
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/candidate/skilljar/skilljar-attempt-lti-lesson
This guide provides a step-by-step process for students on how to attempt an LTI lesson within Skilljar LMS.
**1. Access the quiz**
* Open your web browser and enter the test domain URL provided by your course administrator.
* Append the specific course ID to the URL if required. This will direct you to the correct course page.
**2. Register or Sign In**
* If you are a new user, you need to **register** for an account. Follow the registration prompts and provide the necessary information to create your account.
* If you already have an account, simply **sign in** using your valid credentials (username and password).
**3. Start the quiz**
* After logging in, click on the **“Start”** button to begin the quiz.
**4. Take the quiz**
* Proceed to answer all the questions as per the instructions provided in the quiz.
* Click on **Submit All Answers** to submit the quiz.
* Optionally, you can provide feedback on the test experience, once done click **Submit**.
* Close the browser window and return to the course page.
# How to attempt a proctored quiz
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/candidate/skilljar/skilljar-attempt-quiz
This guide provides a step-by-step process for students on how to attempt a proctored native quiz within Skilljar LMS.
**1. Access the quiz**
* Open your web browser and enter the test domain URL.
* Append the specific course ID to the URL if required. This will direct you to the correct course page.
**2. Register or Sign In**
* If you are a new user, you need to **register** for an account. Follow the registration prompts and provide the necessary information to create your account.
* If you already have an account, simply **sign in** using your valid credentials (username and password).
**3. Start the quiz**
* After logging in, click on the **“Start”** button to begin the quiz.
**4. Proctoring Pre-Flight Checks**
* Clicking on **“Start”** will initiate the **proctoring pre-flight checks**. This step ensures that all necessary proctoring measures are in place before you begin the quiz.
**5. Take the Quiz**
* Once you have successfully passed the pre-flight checks, the quiz questions will appear.
* Proceed to answer all the questions as per the instructions provided in the quiz.
# How to attempt a proctored lesson
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/candidate/thinkific/thinkific-attempt-proctored-lesson
Once the proctored lesson has been configured and made available, test takers can follow these steps to attempt the lesson.
In order to start the proctored quiz, ensure the Proview Proctoring extension is installed. You can get it from [here](https://chromewebstore.google.com/detail/proview-proctoring/doblkllolfingbjkbmelgiepdggnbmhi)
**1. Accessing the lesson**
* Log into Thinkific LMS.
* Go to the course where the proctored lesson is available.
* From the lesson list, select the proctored lesson you need to attempt.
* Click on the lesson name to see the lesson description and instructions.
**2. Starting the lesson**
* If the Proview browser extension has not been installed, an error message will appear, containing instructions and a link to install the extension.
* Once installed, acknowledge the web page’s prompt and refresh the screen.
**3. Completing the lesson**
* Attempt all of the lesson questions and then click on **Submit.**
* Click on the **Stop Proctoring** button at the top right of the screen.
* A confirmation message will pop up, click **OK**.
* Ensure you have attempted all the questions before confirming to end the proctoring.
* Optionally, provide feedback on the proctoring experience.
* After stopping proctoring, you will be redirected back to the home page.
# How to attempt a proctored SCORM package
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/candidate/totara/attempt-proctored-scorm-package
Once the proctored SCORM package has been configured and made available, test takers can follow these steps to attempt it.
In order to start proctored test, ensure the Proview Proctoring extension is installed. You can get it from [here](https://chromewebstore.google.com/detail/proview-proctoring/doblkllolfingbjkbmelgiepdggnbmhi).
## Steps
**1. Launch the SCORM package**
* Log in to your **Totara LMS** account.
* Navigate to the course that contains the proctored SCORM package, & click **Start.**
**2. Begin pre-flight checks**
* Click **Begin** to start the **Proctoring Pre-Flight Checks**.
* Once all checks are passed, you will automatically proceed to the SCORM package.
**3. Attempt the SCORM test**
* Complete all items in the SCORM package as usual.
* When finished, click **Stop Proctoring** at the top right of the screen.
**4. End the proctoring session**
* A confirmation message will appear.
* Review the message carefully and click **OK** to confirm and end your proctoring session.
## Demo video
# Blackboard Ultra - Installation Guide
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/client-admin/blackboard/blackboard-ultra-installation-guide
Talview provides LTI1.3 for integration with Blackboard. Follow these steps to install and configure the LTI Tool.
## **Introduction**
The Proview plugin, developed by Talview Inc., integrates the "Proview" proctoring solution into Blackboard Ultra LMS. Proview LTI Tool is designed to deliver a secure, seamless, and efficient proctoring experience directly through your web browser. This tool provides robust exam integrity measures and unparalleled convenience, setting a new standard in online proctoring. This tool continuously evolves with frequent feature enhancements.
This user guide will help system administrators add Proview LTI tool Blackboard Ultra LMS.
## Capabilities
* **Seamless and User-Friendly Integration**: Proview integrates effortlessly with Blackboard Ultra(LMS), ensuring a smooth setup process. The tool is easy to install and use, eliminating the need for complex software installations and making it accessible to a wide range of users.
* **Versatile and Flexible**: Proview is compatible with major web browsers, providing a consistent user experience across different devices and operating systems.
* **Live Remote Proctoring :** Live Remote Proctoring offers an end-to-end platform that supports holding multiple low to high-stakes online exams concurrently monitored by live proctors. The proctors help in authenticating test takers, monitoring exams, intervening, raising flags, terminating exams, and more.
* **Automated Proctoring:** Through advanced video & audio analytics, the Proview system monitors the feeds for any suspicious activity. It ensures candidate focuses on test screen during the test and checks for suspicious objects in video and background voice activity to red flag the test.
* **Record & Review:** This fully automated, AI-enabled application authenticates test takers, tracks, and records their behaviors, and flags critical events. After the exam concludes, our highly trained proctors, or those provided by you, can quickly review and confirm any event flags before certifying the validity of the exam and authenticity of test takers.
## Supported Browsers and Operating Systems
**Note:** Ensure to keep your browser and OS updated to one of these supported versions to prevent any potential issues during proctoring sessions.
Proview Proctoring solutions are supported on the following browsers:
* [Google Chrome](https://www.google.com/chrome/?brand=OPNX\&ds_kid=43700053265395784\&gclid=efe458afb020140252e33e0704417f10\&gclsrc=3p.ds&\&msclkid=efe458afb020140252e33e0704417f10\&utm_source=bing\&utm_medium=cpc\&utm_campaign=1707332%20%7C%20Chrome%20Win11%20%7C%20DR%20%7C%20ESS01%20%7C%20APAC%20%7C%20IN%20%7C%20en%20%7C%20Desk%20%7C%20SEM%20%7C%20BKWS%20-%20EXA%20%7C%20Txt%20%7C%20Bing\&utm_term=install%20chrome\&utm_content=Desk%20%7C%20BKWS%20-%20EXA%20%7C%20Txt_Install\&gclid=efe458afb020140252e33e0704417f10\&gclsrc=3p.ds) (latest 3 versions only)
* [Microsoft Edge](https://www.microsoft.com/en-us/edge/download?form=MA13FJ) (latest 3 versions only)
* [Mozilla Firefox](https://www.mozilla.org/en-US/firefox/new/) (latest 3 versions only)
Proview Proctoring solutions are supported on the following operating systems:
* **Windows Devices**: Windows 10 and Windows 11
* **Apple Devices**: macOS Sonoma
## Pre-requisites
* Client Blackboard instance is of type “Blackboard Ultra”.
* Users who perform configuration require admin tool access.
## Steps
### **1. Access admin tools**
* Log in to your LMS instance with a user having “System Administrator” Role.
* Select Admin from left side panel.
### **2. Add Proview LTI Tool Provider**
* In the administrator panel select “Integrations → LTI Tool Providers → Register LTI1.3/Advantage Tool”
* Add the client-id provided by Talview (`fe404e30-2b49-4155-aa08-02db995a2333` for development environment) and click “Submit to proceed”.
* Copy the default deployment ID and share it with Talview to complete the configuration.
* Change the “Tool Status” to “Approved” for enabling the tool, also grant the tool user data access.
### **3. Add Proview REST API Integration**
* In the administrator panel select “Integrations → REST API Integrations → Create Integration”
* Add the “Application ID” provided by Talview (`fe404e30-2b49-4155-aa08-02db995a2333` for development environment).
* Add a user as Learn User (You can create a new Integration User if Required).
* Allow End User Access
* Authorise to act as user
## Limitations
1. This LTI Tool is only supported on Blackboard Ultra and **not** supported on Blackboard Original.
2. If the tool is removed from the LTI Tool Providers list and re-added, the deployment ID will change and will have to be re-shared with Talview.
# Canvas LMS - Installation Guide
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/client-admin/canvas/canvas-installation-guide
Follow these steps to install and configure the Proview proctoring in Canvas LMS.
## **Introduction**
The Proview extension, developed by Talview Inc., integrates the "Proview" proctoring solution into Canvas LMS. Proview Proctoring Browser Extension is designed to deliver a secure, seamless, and efficient proctoring experience directly through your web browser. This cutting-edge extension provides robust exam integrity measures and unparalleled convenience, setting a new standard in online proctoring. This extension continuously evolves with frequent feature enhancements.
## Capabilities
* **Seamless and User-Friendly Integration**: Proview integrates effortlessly with canvas Learning Management System (LMS), ensuring a smooth setup process. The browser-based extension is easy to install and use, eliminating the need for complex software installations and making it accessible to a wide range of users.
* **Versatile and Flexible**: Proview is compatible with major web browsers, providing a consistent user experience across different devices and operating systems.
* **Live Remote Proctoring :** Live Remote Proctoring offers an end-to-end platform that supports holding multiple low to high-stakes online exams concurrently monitored by live proctors. The proctors help in authenticating test takers, monitoring exams, intervening, raising flags, terminating exams, and more.
* **Automated Proctoring:** Through advanced video & audio analytics, the Proview system monitors the feeds for any suspicious activity. It ensures candidate focuses on test screen during the test and checks for suspicious objects in video and background voice activity to red flag the test.
* **Record & Review:** This fully automated, AI-enabled application authenticates test takers, tracks, and records their behaviors, and flags critical events. After the exam concludes, our highly trained proctors, or those provided by you, can quickly review and confirm any event flags before certifying the validity of the exam and authenticity of test takers.
## Supported Browsers and Operating Systems
**Note:** Ensure to keep your browser and OS updated to one of these supported versions to prevent any potential issues during proctoring sessions.
Proview Proctoring solutions are supported on the following browsers:
* [Google Chrome](https://www.google.com/chrome/?brand=OPNX\&ds_kid=43700053265395784\&gclid=efe458afb020140252e33e0704417f10\&gclsrc=3p.ds&\&msclkid=efe458afb020140252e33e0704417f10\&utm_source=bing\&utm_medium=cpc\&utm_campaign=1707332%20%7C%20Chrome%20Win11%20%7C%20DR%20%7C%20ESS01%20%7C%20APAC%20%7C%20IN%20%7C%20en%20%7C%20Desk%20%7C%20SEM%20%7C%20BKWS%20-%20EXA%20%7C%20Txt%20%7C%20Bing\&utm_term=install%20chrome\&utm_content=Desk%20%7C%20BKWS%20-%20EXA%20%7C%20Txt_Install\&gclid=efe458afb020140252e33e0704417f10\&gclsrc=3p.ds) (latest 3 versions only)
* [Microsoft Edge](https://www.microsoft.com/en-us/edge/download?form=MA13FJ) (latest 3 versions only)
* [Mozilla Firefox](https://www.mozilla.org/en-US/firefox/new/) (latest 3 versions only)
Proview Proctoring solutions are supported on the following operating systems:
* **Windows Devices**: Windows 10 and Windows 11
* **Apple Devices**: macOS Sonoma
## Steps
### **Generate a New Developer Key**
1. **Navigate to the Developer Keys Section**:
* Log in to your Canvas LMS as an admin.
* From the side panel, navigate to **Admin** → **Your Account**.
* Select **Developer Keys** from the menu.
2. **Create a New API Key**:
* Click on **+ Developer Key** and select **API Key** from the dropdown.
* Fill out the required fields:
* **Name**: Enter a descriptive name for the key.
* **Email**: Enter your contact email.
* **Redirect URI**: Input `https://lms-connector.proview.io`.
* **Scopes**: Add the following scopes:
1. Expand the “**Enrollments**” section and select the following scope:
* **url:GET|/api/v1/courses/:course\_id/enrollments**
* This scope is required to retrieve enrollment data for a course
2. Expand the “**Quiz Submissions”** section and select the following scope:
* **url:GET|/api/v1/courses/:course\_id/quizzes/:quiz\_id/submissions**
* This scope is required to get submission data for classic quizzes, crucial for handling multiple attempts in AI and Record & Review sessions
3. Expand the “**Submissions”** section and select the following scope:
* **url:GET|/api/v1/courses/:course\_id/assignments/:assignment\_id/submissions/:user\_id**
* This scope is used to get submission data for new quizzes, essential for managing multiple attempts in AI and Record & Review sessions
4. Expand the “**Courses**” section and select the following scope:
* **url:GET|/url|/api/v1/courses/:id**
* This scope is used to get course details, as well as retrieving the total number of students enrolled
3. **Save and Enable the Developer Key**:
* After adding the scopes, click **Save**.
* You will receive the **Client ID** and **Client Secret**.
* Click **Show Key** to view the **Client Secret**.
!\[Cn5] Pn]\(/images/cn5].png)
* Make sure to **Enable** the state for the key by sliding the toggle to active state.
### **Authenticate the Integration**
1. **Prepare the Authentication URL**:
* Use the following URL format to authenticate:
```
https://your_lms_url/login/oauth2/auth?client_id=your_client_id&response_type=code&redirect_uri=https://lms-connector.proview.io&scope=url:GET|/api/v1/courses/:course_id/enrollments%20url:GET|/api/v1/courses/:course_id/quizzes/:quiz_id/submissions%20url:GET|/api/v1/courses/:course_id/assignments/:assignment_id/submissions/:user_id%20url:GET|/api/v1/courses/:id
```
* Replace `your_lms_url` with your actual Canvas LMS URL and `your_client_id` with the **Client ID** you generated.
**Example**:
```
https://talview.instructure.com/login/oauth2/auth?client_id=193880000000000216&response_type=code&redirect_uri=https://lms-connector.proview.io&scope=url:GET|/api/v1/courses/:course_id/enrollments%20url:GET|/api/v1/courses/:course_id/quizzes/:quiz_id/submissions%20url:GET|/api/v1/courses/:course_id/assignments/:assignment_id/submissions/:user_id%20url:GET|/api/v1/courses/:id
```
2. **Authenticate the Application**:
* Copy the prepared URL, paste it into your browser, and press enter.
* Log in to Canvas LMS and authorize the application.
* Upon successful authorization, a code will be appended to the URL in your browser.
3. **Generate the UUID**
* Log in to the Canvas LMS as an admin.
* Enter the following URL in your browser, replacing `your-instance-url` with your Canvas LMS instance URL:
* [https://your-instance-url/api/v1/audit/authentication/users/self](https://your-instance-url/api/v1/audit/authentication/users/self)
* For eg: [https://talview.instructure.com/api/v1/audit/authentication/users/self](https://talview.instructure.com/api/v1/audit/authentication/users/self)
* Copy the **UUID** of the account where you want to enable proctoring.
4. **Share the Required Details:**
* Copy the authorization code from the URL.
* Share the following details with Talview:
* **LMS URL**
* **Authorization Code**
* **Client ID**
* **Client Secret**
* **Account UUID**
* The whitelisting process will take about one hour
By following these steps, you will successfully set up the Proview Proctoring extension for your Canvas LMS, enabling a secure and efficient proctoring environment for your online assessments.
### Add a validation script to ensure browser extension installation
To ensure that test-takers have installed the Proview browser extension, follow these steps to add a validation script to Canvas LMS.
1. **Create the validation script:**
Create a file named `proview-browser-extension-validator.js` with the following code:
```javascript theme={null}
$(document).ready(async function () {
const url = window.location.href;
if (isValidCourseAssignmentUrl(url)) {
try {
const extension_id = 'doblkllolfingbjkbmelgiepdggnbmhi';
const { courseId, assignmentId } = parseCourseAssignmentIds(url);
const cmid = `${courseId}_${assignmentId}`;
const appId = await getAppId(courseId);
const apiResponse = await fetchProctoringStatus(cmid, appId);
if (!apiResponse.success) {
console.log('API did not respond successfully, allowing the quiz to load normally.');
return;
}
const proctoringEnabled = apiResponse.proctoringEnabled;
const tsbEnabled = apiResponse.tsbEnabled;
const isExtensionInstalled = await checkExtension(extension_id);
const userAgent = window.navigator.userAgent;
const isProviewBrowser = userAgent.includes('Proview-SB') || userAgent.includes('TalviewBrowser');
if ((proctoringEnabled || tsbEnabled) && !isExtensionInstalled && !isProviewBrowser) {
displayExtensionAlert();
}
} catch (error) {
console.error('Silent error, but proceeding without disruption:', error);
}
}
});
const isValidCourseAssignmentUrl = (url) =>
url.includes('courses') &&
url.includes('assignments') &&
!(url.includes('edit') || url.includes('new'));
const parseCourseAssignmentIds = (url) => {
const courseId = url.split('/courses/')[1].split('/')[0];
const assignmentId = url.split('/assignments/')[1].split('/')[0];
return { courseId, assignmentId };
};
const getAppId = async (courseId) => {
const baseUrl = window.location.href.split('/courses')[0];
const courseInfo = await fetchJson(`${baseUrl}/api/v1/courses/${courseId}`);
const accountId = courseInfo.root_account_id;
const userData = await fetchJson(`${baseUrl}/api/v1/audit/authentication/users/self`);
const accounts = userData.linked.accounts;
const account = accounts.find((acc) => acc.id === accountId);
return account.uuid;
};
const fetchJson = async (url) => {
const response = await fetch(url);
return response.json();
};
const fetchProctoringStatus = async (cmid, appId) => {
const proviewApiUrl = 'https://lms-connector.proview.io';
const getQuizInfoUrl = `${proviewApiUrl}/quiz?course_module_id=${cmid}`;
const config = {
headers: {
'Content-Type': 'application/json',
'app-id': appId,
}
};
try {
const response = await fetch(getQuizInfoUrl, config);
if (!response.ok) {
if (response.status === 404) {
console.log(`Quiz not found for cmid: ${cmid}`);
return { success: false };
}
return { success: false };
}
const quizInfo = await response.json();
return {
success: true,
proctoringEnabled: quizInfo?.data?.proctoring_enabled ?? false,
tsbEnabled: quizInfo?.data?.tsb_enabled ?? false
};
} catch (error) {
console.error('Error fetching proctoring/SB status:', error);
return { success: false };
}
};
const checkExtension = async (extension_id) => {
try {
const response = await fetch(`chrome-extension://${extension_id}/manifest.json`);
return response.ok;
} catch (error) {
return false;
}
};
const displayExtensionAlert = () => {
const courseUrl = window.location.href.split('/assignments')[0];
document.body.innerHTML = '';
const div = document.createElement('div');
const alertDiv = document.createElement('div');
alertDiv.innerHTML = `
Action Required: Install the Proview Browser Extension
To access your exam, you need to install the Proview browser extension.
Steps to Install
Click here to install the Proview browser extension.
`;
alertDiv.style.backgroundColor = '#f8d7da';
alertDiv.style.color = '#171717';
alertDiv.style.padding = '20px';
alertDiv.style.borderRadius = '5px';
div.style.position = 'absolute';
div.style.top = '50%';
div.style.left = '50%';
div.style.transform = 'translate(-50%, -50%)';
div.appendChild(alertDiv);
document.body.appendChild(div);
};
```
# Cornerstone LMS - Installation Guide
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/client-admin/cornerstone/cornerstone-installation-guide
Follow these steps to complete the installation and configuration of the Proview Proctoring extension on Cornerstone LMS through the LMS Dashboard. This enables authentication without sharing admin credentials.
## **Introduction**
The Proview extension, developed by Talview Inc., integrates the "Proview" proctoring solution into Cornerstone LMS. Proview Proctoring Browser Extension is designed to deliver a secure, seamless, and efficient proctoring experience directly through your web browser. This cutting-edge extension provides robust exam integrity measures and unparalleled convenience, setting a new standard in online proctoring. This extension continuously evolves with frequent feature enhancements.
## Capabilities
* **Seamless and User-Friendly Integration**: Proview integrates effortlessly with Cornerstone Learning Management System (LMS), ensuring a smooth setup process. The browser-based extension is easy to install and use, eliminating the need for complex software installations and making it accessible to a wide range of users.
* **Versatile and Flexible**: Proview is compatible with major web browsers, providing a consistent user experience across different devices and operating systems.
* **Recorded Proctoring:** Through advanced video & audio analytics, the Proview system monitors the feeds for any suspicious activity. It ensures candidate focuses on test screen during the test and checks for suspicious objects in video and background voice activity to red flag the test.
* **Record & Review:** This fully automated, AI-enabled application authenticates test takers, tracks, and records their behaviors, and flags critical events. After the exam concludes, our highly trained proctors, or those provided by you, can quickly review and confirm any event flags before certifying the validity of the exam and authenticity of test takers.
## Supported Browsers and Operating Systems
**Note:** Ensure to keep your browser and OS updated to one of these supported versions to prevent any potential issues during proctoring sessions.
Proview Proctoring solutions are supported on the following browsers:
* [Google Chrome](https://www.google.com/chrome/?brand=OPNX\&ds_kid=43700053265395784\&gclid=efe458afb020140252e33e0704417f10\&gclsrc=3p.ds&\&msclkid=efe458afb020140252e33e0704417f10\&utm_source=bing\&utm_medium=cpc\&utm_campaign=1707332%20%7C%20Chrome%20Win11%20%7C%20DR%20%7C%20ESS01%20%7C%20APAC%20%7C%20IN%20%7C%20en%20%7C%20Desk%20%7C%20SEM%20%7C%20BKWS%20-%20EXA%20%7C%20Txt%20%7C%20Bing\&utm_term=install%20chrome\&utm_content=Desk%20%7C%20BKWS%20-%20EXA%20%7C%20Txt_Install\&gclid=efe458afb020140252e33e0704417f10\&gclsrc=3p.ds) (latest 3 versions only)
* [Microsoft Edge](https://www.microsoft.com/en-us/edge/download?form=MA13FJ) (latest 3 versions only)
* [Mozilla Firefox](https://www.mozilla.org/en-US/firefox/new/) (latest 3 versions only)
Proview Proctoring solutions are supported on the following operating systems:
* **Windows Devices**: Windows 10 and Windows 11
* **Apple Devices**: macOS Sonoma
## Steps
### **1. Access LMS Dashboard**
* Log in to your LMS Dashboard.
* Click on the **“LMS Configuration”** option located at the top right of the screen.
* A pop-up will appear. Click on **“Cornerstone”** as the LMS option.
### 2. Authenticate
* Fill in the following fields, and then click on Verify butto
* **Name**
* **Proview Admin Username**
* **Password**
* **URL**
* Once verified successfully, click on the **Update Configuration** button, a confirmation message will appear as a browser pop up.
* Click on the **Verify** button to validate the credentials.
# D2L Brightspace LMS - Installation Guide
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/client-admin/d2l-brightspace/d2l-installation-guide
Follow these steps to install and configure the Proview Proctoring extension.
## **Introduction**
The Proview extension, developed by Talview Inc., integrates the "Proview" proctoring solution into D2L LMS. Proview Proctoring Browser Extension is designed to deliver a secure, seamless, and efficient proctoring experience directly through your web browser. This cutting-edge extension provides robust exam integrity measures and unparalleled convenience, setting a new standard in online proctoring. This extension continuously evolves with frequent feature enhancements.
## Capabilities
* **Seamless and User-Friendly Integration**: Proview integrates effortlessly with D2L Brightspace Learning Management System (LMS), ensuring a smooth setup process. The browser-based extension is easy to install and use, eliminating the need for complex software installations and making it accessible to a wide range of users.
* **Versatile and Flexible**: Proview is compatible with major web browsers, providing a consistent user experience across different devices and operating systems.
* **Live Remote Proctoring :** Live Remote Proctoring offers an end-to-end platform that supports holding multiple low to high-stakes online exams concurrently monitored by live proctors. The proctors help in authenticating test takers, monitoring exams, intervening, raising flags, terminating exams, and more.
* **Automated Proctoring:** Through advanced video & audio analytics, the Proview system monitors the feeds for any suspicious activity. It ensures candidate focuses on test screen during the test and checks for suspicious objects in video and background voice activity to red flag the test.
* **Record & Review:** This fully automated, AI-enabled application authenticates test takers, tracks, and records their behaviors, and flags critical events. After the exam concludes, our highly trained proctors, or those provided by you, can quickly review and confirm any event flags before certifying the validity of the exam and authenticity of test takers.
## Supported Browsers and Operating Systems
**Note:** Ensure to keep your browser and OS updated to one of these supported versions to prevent any potential issues during proctoring sessions.
Proview Proctoring solutions are supported on the following browsers:
* [Google Chrome](https://www.google.com/chrome/?brand=OPNX\&ds_kid=43700053265395784\&gclid=efe458afb020140252e33e0704417f10\&gclsrc=3p.ds&\&msclkid=efe458afb020140252e33e0704417f10\&utm_source=bing\&utm_medium=cpc\&utm_campaign=1707332%20%7C%20Chrome%20Win11%20%7C%20DR%20%7C%20ESS01%20%7C%20APAC%20%7C%20IN%20%7C%20en%20%7C%20Desk%20%7C%20SEM%20%7C%20BKWS%20-%20EXA%20%7C%20Txt%20%7C%20Bing\&utm_term=install%20chrome\&utm_content=Desk%20%7C%20BKWS%20-%20EXA%20%7C%20Txt_Install\&gclid=efe458afb020140252e33e0704417f10\&gclsrc=3p.ds) (latest 3 versions only)
* [Microsoft Edge](https://www.microsoft.com/en-us/edge/download?form=MA13FJ) (latest 3 versions only)
* [Mozilla Firefox](https://www.mozilla.org/en-US/firefox/new/) (latest 3 versions only)
Proview Proctoring solutions are supported on the following operating systems:
* **Windows Devices**: Windows 10 and Windows 11
* **Apple Devices**: macOS Sonoma
## Steps
### **1. Access admin tools**
* Log in to your LMS instance.
* Look to the right of the screen and click on the admin tools icon.
### **2. Manage extensibility**
* From the list of options presented, click on **Manage Extensibility**.
### **3. Register the app**
* Within the Manage Extensibility page, click on the **OAuth2.0** navigation tab. It's imperative to set up your OAuth and share the credentials with Talview.
* Click on the **Register an App** button.
### **4. Fill out application details**
* **Application Name**: Enter **Proview Proctoring** as the name of the application.
* **Redirect URI**: Enter [https://console.eu.proview.io/dashboard/lms/configure/brightspace](https://console.eu.proview.io/dashboard/lms/configure/brightspace) in the field
* **Scope**: Enter the following scopes, separated by space:
* `enrollment:orgunit:read`
* `quizzing:attempts:read`
* The `enrollment:orgunit:read` scope is necessary for syncing enrollment data to schedule live proctored exams.
* The `quizzing:attempts:read` scope is needed to map each new quiz attempt to Proview for AI and Record & Review exams.
* **Access Token Lifetime:** Provide the access token’s lifetime validity in seconds.
* **Description**: Enter a brief description of the application.
### **5. Additional enablement**
* **Prompt for User Content**: Check this statement.
* **Enable Refresh Tokens**: Check this statement.
* **Non-commercial Developer Agreement**: Check the statement to accept the agreement.
### **6. Finalize registration**
* Click on the **Register** button to complete the registration process.
* You have now completed registering the application, and will be displayed within **OAuth 2.0 Apps List**
### **7. Share admin credentials for that instance**
* Provide Talview with the admin credentials (username and password) along with the LMS URL.
* Talview needs the URL to whitelist it, ensuring the Proview Proctoring extension becomes compatible for the users.
* The whitelisting process will take about one hour
By following these steps, you will successfully set up the Proview Proctoring extension for your LMS, ensuring a secure and efficient proctoring environment for your online assessments.
# D2L Brightspace LMS - Self Onboarding Guide
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/client-admin/d2l-brightspace/d2l-self-onboarding-guide
Follow these steps to complete the installation and configuration of the Proview Proctoring extension on D2L LMS through the LMS Dashboard. This enables authentication without sharing admin credentials.
### **1. Access LMS Dashboard**
* Log in to your LMS Dashboard.
* Click on the **“LMS Configuration”** option located at the top right of the screen.
### **2. Select LMS for Configuration**
* A pop-up will appear. Choose **“Brightspace”** from the list of available LMS options.
### **3. Generate Refresh Token**
* On the Brightspace configuration screen, click the **“Generate Refresh Token”** button at the top right of the screen.
* A form will appear prompting you to enter integration details. Provide the following information:
* **Client ID**
* **Redirect URI**
* **Scope**
* **Client Secret**
### **4. Authenticate and Generate Token**
* After filling in the required details, click on the **“Generate Refresh Token”** button.
* You will be redirected to the D2L LMS login page.
* Log in with your credentials.
### **5. Return to Brightspace Configuration**
* After successful login, you will be redirected back to the Brightspace configuration screen in the LMS Dashboard.
### **6. Complete Configuration**
* The **“Refresh Token”** and **“App ID”** fields will be automatically populated.
* Fill in the remaining fields:
* **LMS URL**
* **Proview Admin Username**
* **Proview Admin Password**
* Once all fields are complete, click on the **“Update Configuration”** button.
* The refresh token is securely stored in our database.
The refresh token may not always be valid for the instance after updates made to the browser extension. In such instances, it is recommended to generated the refresh token again and update the configuration.
# Docebo LMS - Installation Guide
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/client-admin/docebo/docebo-installation-guide
Follow these steps to complete the installation and configuration of the Proview Proctoring extension on Docebo LMS through the LMS Dashboard. This enables authentication without sharing admin credentials.
## **Introduction**
The Proview extension, developed by Talview Inc., integrates the "Proview" proctoring solution into Docebo LMS. Proview Proctoring Browser Extension is designed to deliver a secure, seamless, and efficient proctoring experience directly through your web browser. This cutting-edge extension provides robust exam integrity measures and unparalleled convenience, setting a new standard in online proctoring. This extension continuously evolves with frequent feature enhancements.
## Capabilities
* **Seamless and User-Friendly Integration**: Proview integrates effortlessly with Docebo Learning Management System (LMS), ensuring a smooth setup process. The browser-based extension is easy to install and use, eliminating the need for complex software installations and making it accessible to a wide range of users.
* **Versatile and Flexible**: Proview is compatible with major web browsers, providing a consistent user experience across different devices and operating systems.
* **Recorded Proctoring:** Through advanced video & audio analytics, the Proview system monitors the feeds for any suspicious activity. It ensures candidate focuses on test screen during the test and checks for suspicious objects in video and background voice activity to red flag the test.
* **Record & Review:** This fully automated, AI-enabled application authenticates test takers, tracks, and records their behaviors, and flags critical events. After the exam concludes, our highly trained proctors, or those provided by you, can quickly review and confirm any event flags before certifying the validity of the exam and authenticity of test takers.
## Supported Browsers and Operating Systems
**Note:** Ensure to keep your browser and OS updated to one of these supported versions to prevent any potential issues during proctoring sessions.
Proview Proctoring solutions are supported on the following browsers:
* [Google Chrome](https://www.google.com/chrome/?brand=OPNX\&ds_kid=43700053265395784\&gclid=efe458afb020140252e33e0704417f10\&gclsrc=3p.ds&\&msclkid=efe458afb020140252e33e0704417f10\&utm_source=bing\&utm_medium=cpc\&utm_campaign=1707332%20%7C%20Chrome%20Win11%20%7C%20DR%20%7C%20ESS01%20%7C%20APAC%20%7C%20IN%20%7C%20en%20%7C%20Desk%20%7C%20SEM%20%7C%20BKWS%20-%20EXA%20%7C%20Txt%20%7C%20Bing\&utm_term=install%20chrome\&utm_content=Desk%20%7C%20BKWS%20-%20EXA%20%7C%20Txt_Install\&gclid=efe458afb020140252e33e0704417f10\&gclsrc=3p.ds) (latest 3 versions only)
* [Microsoft Edge](https://www.microsoft.com/en-us/edge/download?form=MA13FJ) (latest 3 versions only)
* [Mozilla Firefox](https://www.mozilla.org/en-US/firefox/new/) (latest 3 versions only)
Proview Proctoring solutions are supported on the following operating systems:
* **Windows Devices**: Windows 10 and Windows 11
* **Apple Devices**: macOS Sonoma
## Steps
### **1. Access LMS Dashboard**
* Log in to your LMS Dashboard.
* Click on the **“LMS Configuration”** option located at the top right of the screen.
* A pop-up will appear. Click on **“Docebo”** as the LMS option.
### 2. Authenticate
* Fill in the following fields, and then click on Verify button
* **Name**
* **Proview Admin Username**
* **Password**
* **URL**
* Once verified successfully, click on the **Update Configuration** button, a confirmation message will appear as a browser pop up.
# Moodle LMS - Backend Installation Guide
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/client-admin/moodle/moodle-backend-installation-guide
Installing the quizaccess_proctor and local_proview plugins in Moodle from backend.
**This is not a method supported by product to install the plugins**
## **Introduction**
Talview's proctoring solutions for Moodle LMS include two essential plugins: the Quiz Access Proctor plugin and the Local Proview plugin. These plugins work together to enhance the security and integrity of online quizzes by integrating advanced proctoring features directly into Moodle's quiz module.
The [**Quiz Access Proctor plugin**](https://github.com/talview/moodle-quizaccess_proctor/releases/tag/v1.5.0-Quiz_Access_Proctor) allows educators to apply specific proctoring settings to their quizzes, ensuring a controlled testing environment. With this plugin, different types of proctoring can be configured, and Talview's Secure Browser can be utilized to prevent unauthorized access and maintain exam integrity. **Install the “quiz access proctor” plugin first**
Complementing this, the [**Local Proview plugin**](https://github.com/talview/moodle-local_proview/releases/tag/v3.3.9-local-proview) injects the necessary Proview JavaScript into Moodle quizzes. It ensures that the proctoring session is initiated correctly when a quiz starts and manages integration aspects such as fetching session playback URLs for post-exam review. This comprehensive approach allows for seamless monitoring and reviewing of proctored sessions, enhancing the overall assessment process. **Install the “local proview” plugin second**
\[[*****These plugins are free to download, but a subscription is needed to fully use it. For any query on the subscription, please contact Talview Sales Team or technical support, you can reach out to Talview Tech Support.*****](https://talview.freshdesk.com/en/support/home)]\([https://www.talview.com/contact?hsCtaTracking=6b06eef3-21df-4508-826e-0c77f9922d17%7Cede73d3b-fccd-45f2-abfa-73d38e575dec](https://www.talview.com/contact?hsCtaTracking=6b06eef3-21df-4508-826e-0c77f9922d17%7Cede73d3b-fccd-45f2-abfa-73d38e575dec))
### **Step 1: Prepare and Configure Moodle Data Directory**
**Verify** and **Create** `dataroot`**Directory**
1. **Check Current Setting:**
```
sudo nano /var/www/html/moodle/config.php
```
2. **Ensure This Line Exists:**
```
$CFG->dataroot = '/var/moodledata';
```
3. **Create Directory if Missing:**
```
sudo mkdir -p /var/moodledata
```
4. **Set Correct Permissions:**
```
sudo chown -R www-data:www-data /var/moodledata
sudo chmod -R 770 /var/moodledata
```
5. **Restart Apache:**
```
sudo systemctl restart apache2
```
***
### **Step 2: Upload and Extract Plugin Files**
**Upload** and **Extract** `quizaccess_proctor`**Plugin:**
1. **Navigate to the Moodle Root Directory:**
```
cd /var/www/html/moodle
```
2. **Extract Plugin:**
```
sudo unzip quizaccess_proctor.zip -d /var/www/html/moodle/mod/quiz/accessrule/
```
3. **Rename the Extracted Directory:**
```
sudo mv /var/www/html/moodle/mod/quiz/accessrule/moodle-quizaccess_proctor-1.5.0-Quiz_Access_Proctor /var/www/html/moodle/mod/quiz/accessrule/proctor
```
4. **Set Correct Permissions:**
```
sudo chown -R www-data:www-data /var/www/html/moodle/mod/quiz/accessrule/proctor
sudo chmod -R 755 /var/www/html/moodle/mod/quiz/accessrule/proctor
```
**Upload** and **Extract**`local_proview`**Plugin:**
1. **Extract Plugin:**
```
sudo unzip local_proview.zip -d /var/www/html/moodle/local/
```
2. **Rename the Extracted Directory:**
```
sudo mv /var/www/html/moodle/local/moodle-local_proview-3.3.8-local-proview /var/www/html/moodle/local/proview
```
3. **Set Correct Permissions:**
```
sudo chown -R www-data:www-data /var/www/html/moodle/local/proview
sudo chmod -R 755 /var/www/html/moodle/local/proview
```
***
### **Step 3: Purge Cache and Restart Services**
1. **Purge Moodle Cache:**
```
sudo php /var/www/html/moodle/admin/cli/purge_caches.php
```
2. **Restart Apache Web Server:**
```
sudo systemctl restart apache2
```
***
### **Step 4: Install Composer Dependencies**
**1. Enable Permissions:**
```
sudo chown -R ubuntu:www-data /var/www/html/moodle
sudo chmod -R 775 /var/www/html/moodle
```
**2. Run Composer Installation:**
1. **Navigate to Plugin Directory:**
```
cd /var/www/html/moodle/mod/quiz/accessrule/proctor
```
2. **Create Missing Directories if Needed:**
```
mkdir -p vendor
```
3. **Run Composer:**
```
sudo composer install
```
4. **Verify**`autoload.php`**Exists:**
```
ls /var/www/html/moodle/mod/quiz/accessrule/proctor/vendor/autoload.php
```
**3. Reset Correct Permissions (Best Practice):**
```
sudo chown -R www-data:www-data /var/www/html/moodle
sudo chmod -R 755 /var/www/html/moodle
```
***
### **Step 5: Final Cleanup and Verification**
1. **Purge Moodle Cache Again:**
```
sudo php /var/www/html/moodle/admin/cli/purge_caches.php
```
2. **Restart Apache:**
```
sudo systemctl restart apache2
```
3. **Verify Moodle Installation:**
* Log in to Moodle.
* Go to **Site Administration > Plugins > Plugins Overview**.
* Verify that both plugins (`quizaccess_proctor` and `local_proview`) are listed without errors.
***
### **Verification Checklist:**
* **File Check:** Ensure both plugins have correct permissions.
* **Moodle Interface:** Verify plugins appear in **Plugins Overview.**
* **Database Check:** Run the following command to ensure plugins are in the database:
```
sudo mysql -u root -p
USE moodle;
SELECT * FROM mdl_config_plugins WHERE plugin IN ('quizaccess_proctor', 'local_proview');
```
By following these steps, you should be able to successfully install and configure both plugins on Moodle without encountering `autoload.php` or permission-related errors.
***
## Uninstalling the plugins from backend
To **completely remove the plugins** from your Moodle instance located at `/var/www/html/moodle`, follow these steps:
***
### **Step 1: Remove Plugin Files**
1. **Navigate to the Moodle Root Directory:**
```
cd /var/www/html/moodle
```
2. **Delete the Plugin Directories:**
* For **Quiz Access Proctor**:
```
sudo rm -rf /var/www/html/moodle/mod/quiz/accessrule/proctor
```
* For **Local Proview**:
```
sudo rm -rf /var/www/html/moodle/local/proview
```
3. **Verify Directories are Clean:**
```
ls /var/www/html/moodle/mod/quiz/accessrule
ls /var/www/html/moodle/local
```
***
### **Step 2: Database Cleanup**
1. **Log in to MySQL:**
```
sudo mysql -u root -p
```
2. **Select the Moodle Database:**
```
USE moodle;
```
3. **Check and Drop Plugin-Related Tables:**
```
SHOW TABLES LIKE '%proctor%';
SHOW TABLES LIKE '%proview%';
```
4. **Delete Tables (If Found):**
```
DROP TABLE IF EXISTS mdl_quizaccess_proctor;
DROP TABLE IF EXISTS mdl_local_proview;
```
5. **Remove Plugin Configurations:**
```
DELETE FROM mdl_config_plugins WHERE plugin IN ('quizaccess_proctor', 'local_proview');
```
6. **Check for Role Assignments (Optional):**
```
SELECT * FROM mdl_role_assignments WHERE roleid IN (
SELECT id FROM mdl_role WHERE shortname IN ('proctor', 'proview')
);
```
7. **Delete Role Assignments (If Found):**
```
DELETE FROM mdl_role_assignments WHERE roleid IN (
SELECT id FROM mdl_role WHERE shortname IN ('proctor', 'proview')
);
```
8. **Exit MySQL:**
```
EXIT;
```
***
### **Step 3: Clear Cache and Reset Permissions**
1. **Purge Moodle Cache:**
```
sudo php /var/www/html/moodle/admin/cli/purge_caches.php
```
2. **Reset Moodle Directory Permissions:**
```
sudo chown -R www-data:www-data /var/www/html/moodle
sudo chmod -R 755 /var/www/html/moodle
```
***
### **Step 4: Restart Services**
1. **Restart Apache Web Server:**
```
sudo systemctl restart apache2
```
***
### **Step 5: Verify Plugin Removal**
1. **Log in to Moodle Admin.**
2. Go to **Site Administration > Plugins > Plugins Overview.**
3. Ensure that **Quiz Access Proctor** and **Local Proview** are **not listed**.
***
These steps will **completely remove** the plugins from both the **filesystem** and **database**.
## Process to Insert Missing Quiz Records into `mdl_quizaccess_proctor`
### 1. SQL to Identify Missing Records
This query identifies quizzes in mdl\_quiz that do not have a corresponding entry in mdl\_quizaccess\_proctor.
```
SELECT q.id AS quizid, q.course AS courseid, cm.id AS cmid
FROM mdl_quiz q
LEFT JOIN mdl_course_modules cm ON cm.instance = q.id AND cm.module = (
SELECT id FROM mdl_modules WHERE name = 'quiz'
)
LEFT JOIN mdl_quizaccess_proctor p ON q.id = p.quizid
WHERE p.quizid IS NULL;
```
### 2. SQL to Insert Missing Records
To insert missing records with default values, use the following query.
```
INSERT INTO mdl_quizaccess_proctor (
quizid, cmid, proctortype, tsbenabled, usermodified, timecreated, timemodified,
reference_link, instructions, blacklisted_softwares_win, blacklisted_softwares_mac,
sb_kiosk_mode, sb_content_protection
)
SELECT
q.id AS quizid,
cm.id AS cmid,
'noproctor' AS proctortype,
0 AS tsbenabled,
2 AS usermodified,
UNIX_TIMESTAMP() AS timecreated,
0 AS timemodified,
'' AS reference_link,
'' AS instructions,
'' AS blacklisted_softwares_win,
'' AS blacklisted_softwares_mac,
0 AS sb_kiosk_mode,
0 AS sb_content_protection
FROM
mdl_quiz q
LEFT JOIN
mdl_course_modules cm ON cm.instance = q.id AND cm.module = (
SELECT id FROM mdl_modules WHERE name = 'quiz'
)
LEFT JOIN
mdl_quizaccess_proctor p ON q.id = p.quizid
WHERE
p.quizid IS NULL;
```
### 3. Verification
After running the query, verify no quizzes are missing
```
SELECT q.id AS missing_quizid
FROM mdl_quiz q
LEFT JOIN mdl_quizaccess_proctor p ON q.id = p.quizid
WHERE p.quizid IS NULL;
```
# Moodle LMS -Installation Guide
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/client-admin/moodle/moodle-installation-guide
Follow these steps to install and configure the two moodle plugins on to your instance.
## **Introduction**
Talview's proctoring solutions for Moodle LMS include two essential plugins: the Quiz Access Proctor plugin and the Local Proview plugin. These plugins work together to enhance the security and integrity of online quizzes by integrating advanced proctoring features directly into Moodle's quiz module.
The **Quiz Access Proctor plugin** allows educators to apply specific proctoring settings to their quizzes, ensuring a controlled testing environment. With this plugin, different types of proctoring can be configured, and Talview's Secure Browser can be utilized to prevent unauthorized access and maintain exam integrity. **Install the “quiz access proctor” plugin first**
Complementing this, the **Local Proview plugin** injects the necessary Proview JavaScript into Moodle quizzes. It ensures that the proctoring session is initiated correctly when a quiz starts and manages integration aspects such as fetching session playback URLs for post-exam review. This comprehensive approach allows for seamless monitoring and reviewing of proctored sessions, enhancing the overall assessment process. **Install the “local proview” plugin second**
\[[*****These plugins are free to download, but a subscription is needed to fully use it. For any query on the subscription, please contact Talview Sales Team or technical support, you can reach out to Talview Tech Support.*****](https://talview.freshdesk.com/en/support/home)]\([https://www.talview.com/contact?hsCtaTracking=6b06eef3-21df-4508-826e-0c77f9922d17%7Cede73d3b-fccd-45f2-abfa-73d38e575dec](https://www.talview.com/contact?hsCtaTracking=6b06eef3-21df-4508-826e-0c77f9922d17%7Cede73d3b-fccd-45f2-abfa-73d38e575dec))
## Capabilities
* **Versatile and Flexible**: Proview is compatible with major web browsers, providing a consistent user experience across different devices and operating systems.
* **Live Remote Proctoring :** Live Remote Proctoring offers an end-to-end platform that supports holding multiple low to high-stakes online exams concurrently monitored by live proctors. The proctors help in authenticating test takers, monitoring exams, intervening, raising flags, terminating exams, and more.
* **Automated AI Proctoring:** Through advanced video & audio analytics, the Proview system monitors the feeds for any suspicious activity. It ensures candidate focuses on test screen during the test and checks for suspicious objects in video and background voice activity to red flag the test.
* **Record & Review:** This fully automated, AI-enabled application authenticates test takers, tracks, and records their behaviors, and flags critical events. After the exam concludes, our highly trained proctors, or those provided by you, can quickly review and confirm any event flags before certifying the validity of the exam and authenticity of test takers.
## Steps - **Quiz Access Proctor Plugin**
Install the “quiz access proctor” plugin first
### **1. Accessing site administration**
* Log in to Moodle as an admin. In the admin view, go to **Site Administration**.
### **2. Installing the plugin**
* Click on **Plugins** in the Site Administration menu.
* Choose **Install Plugin** from the plugin options.
### **3. Downloading and uploading the plugin**
* Download the latest plugin from [https://github.com/talview/moodle-quizaccess\_proctor/releases/tag/v1.5.0-Quiz\_Access\_Proctor](https://github.com/talview/moodle-quizaccess_proctor/releases/tag/v1.5.0-Quiz_Access_Proctor)
* Use the **File Picker** option to upload the downloaded plugin zip file. Once uploaded, click on **Install Plugin from ZIP file**.
### **4. Validating and continuing installation**
* You will see a message stating "Validation successful, installation can continue". Click on the **Continue** button.
* Next, click on **Upgrade Moodle database now** button.
* Next, click on **Continue** button.
### **5. Configuring the plugin settings**
On the plugin settings page:
* **Enable configurations**: Enable configurations for the plugin by selecting the checkbox (Default Enabled).
* **Enter callback URL**:
* For Europe: `https://moodle-proview-api.talview.com`
* For Australia: `https://moodle-proview-api.talview.nz`
* **Input Authentication Details**:
* **Username**: Enter the username provided by Talview for authenticating the callbacks.
* **Password**: Provide the password provided by Talview for authenticating the callbacks.
* **Save Changes**: Once all configurations are finalized, click on the **Save Changes** button.
## Steps - **Local Proview Plugin**
Install the “local proview” plugin second
### **1. Accessing site administration**
* Log in to Moodle as an admin. In the admin view, go to **Site Administration**.
### **2. Installing the plugin**
* Click on **Plugins** in the Site Administration menu.
* Choose **Install Plugin** from the plugin options.
### **3. Downloading and uploading the plugin**
* Download the latest plugin from [https://github.com/talview/moodle-local\_proview/releases/tag/v3.3.11-local-proview](https://github.com/talview/moodle-local_proview/releases/tag/v3.3.11-local-proview)
* Use the **File Picker** option to upload the downloaded plugin zip file. Once uploaded, click on **Install Plugin from ZIP file**.
### **4. Validating and continuing installation**
* You will see a message stating "Validation successful, installation can continue". Click on the **Continue** button.
* Next, click on **Upgrade Moodle database now** button.
* Next, click on **Continue** button.
### **5. Configuring the Plugin Settings**
On the plugin settings page:
* **Enable Proview**: Check the checkbox to enable Proview (Default Disabled).
* **Enter Proctor Token**: Input the Proctor Token provided by Talview (subscription-based).
* **Enter CDN URL**: Input the CDN URL provided by Talview (subscription-based).
* **Enter Account Name**: Input the Account Name provided by Talview.
* **Update Root Directory**:
* **Root Directory Configuration**: Update the `root_dir` to match the root directory of your Moodle installation.
* **Examples**:
* If you access Moodle using a URL like `https://example.domain.com/`, the root directory is `/` and no additional configuration is required.
* If you access Moodle using a URL like `https://example.domain.com/moodle/`, the root directory is `/moodle/` and must be configured accordingly in the `root_dir` field during the Proview installation process.
* **Enter Proview Playback URL**: Input the Proview Playback URL provided by Talview, : [console.au.proview.io/embedded](http://console.au.proview.io/embedded)
### **6. Completing the Installation**
* **Save Changes**: Once all configurations are finalized, click on the **Save Changes** button.
## Steps - Create Moodle Web Service Token
Creating Web Service Token for Talview to synchronize quiz attendee data for Live Proctoring use case we need access to Moodle API.
### **1. Accessing site administration**
* Log in to Moodle as an admin. In the admin view, go to **Site Administration**.
### **2. Create External Service**
* Access “Server” tab
* Navigate to “Web Services” and select “External Services”
* Click on “Add” service to provide name and short name.
* Upon clicking the “Add Service”, it will prompt to add function. click on “Add Function”
* Search the function name `core_enrol_get_enrolled_users `and select it
* Upon adding the screen will look something like
### **3. Create WSToken**
* Navigate to Server (Tab) > Web Services > Manage tokens
* Click on “Create token” button
* Select user who have admin access and Select service that we created in earlier ([Create external web service](/10c3461472f380af8fede190455e2cff?pvs=25#1b53461472f38072893dd53c0305add6)).
* Click “Save changes” to obtain token
### 4. Sharing Token and URL with Talview
Use direct email or secure mode to share following information
* Token
* Moodle URL
## Assumptions
Before proceeding with the installation of Talview's proctoring plugins for Moodle LMS, we assume the following:
1. **Active Moodle Environment**: You have access to your Moodle platform with administrator rights. Talview Plugin is currently supported only on Moodle versions 3.9, 4.0, 4.1, 4.2
2. **Talview Subscription**: You have a valid subscription to Talview Proview services. If needed, contact the [Talview Sales Team](https://www.talview.com/contact?hsCtaTracking=6b06eef3-21df-4508-826e-0c77f9922d17%7Cede73d3b-fccd-45f2-abfa-73d38e575dec) or [Talview Tech Support](https://talview.freshdesk.com/en/support/home).
3. **Compatible Browser**: Testers will use a compatible web browser for the proctored quizzes.
4. **Domain Whitelisting**: Your Moodle domain is authorized and whitelisted to use Talview’s Proctoring Services. This security measure ensures that only approved domains can interact with the service.
5. **Instructor Awareness**: Course administrators have informed all course instructors about the necessity of installing the Proview extension. Without this extension, instructors cannot configure proctoring settings for quizzes, which might lead to confusion or incomplete proctoring setups.
Ensure your server and Moodle environment meet the necessary technical requirements for the plugins. Talview utilizes recorded alerts and configured stake to compute the Proview index, based on the candidate's behavior involving their browser, camera, and microphone. For comprehensive information on Talview's Proview flags, please consult the [Proctoring v7-Plus Events/Flags Details](/6fc4b8a03d774654a95b66f76f02a3f9?pvs=25) documentation.
# Moodle LMS - Self Onboarding Guide
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/client-admin/moodle/moodle-self-onboarding-guide
Administrators using Moodle LMS can now follow these steps to complete & authenticate their installation from the LMS dashboard without having to sharing their admin credentials.
### **1. Access LMS Dashboard**
* Log in to your LMS Dashboard.
* Click on the **“LMS Configuration”** option located at the top right of the screen.
* A pop-up will appear. Click on **“Moodle”** as the LMS option.
### 2. Authenticate
* Fill in the following fields, and then click on Verify button
* **Name**
* **Web Service Function**
* **Web Service Token**
* **Web Service URL**
* Once the fields are filled, click on Verify button. In the modal, enter a valid course ID.
* Upon successful verification, click on the **Update Configuration** button.
# Moodle 4.5 LMS - Installation Guide (Moodle Plugin Integration)
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/client-admin/moodle_4.5/moodle-4-5-lms-installation-guide-moodle-plugin-integration
## Introduction
Talview's Proview proctoring solution for Moodle 4.5 LMS is delivered through a single plugin that integrates advanced proctoring features directly into Moodle's quiz module. The plugin enables subject coordinators to configure proctoring settings for quizzes, enforce secure browser environments, and review session recordings — all from within Moodle.
> **Note:** The plugin is free to download, but a subscription is required to fully use it. For subscription enquiries, contact the [Talview Sales Team](https://www.talview.com/contact) or reach out to [Talview Tech Support](https://talview.freshdesk.com/en/support/home).
***
## Prerequisites
Before proceeding with the installation, ensure the following:
* You have administrator access to your Moodle 4.5 LMS instance.
* You have your Talview-provided **admin username**, **admin password**, **account name**, and **root directory** details on hand.
* **Moodle Web Service URL**
* **Moodle Web Service Token (wstoken)**
* This token is generated by the Moodle admin.
* It will be used to authenticate Proview’s requests to Moodle.
***
### Steps to create WSToken
* Navigate to Server (Tab) > Web Services > Manage tokens
* Click on “Create token” button
* Select user who have admin access and select service that we created earlier.
* Access “Server” tab
* Navigate to “Web Services” and select “External Services”
* Click on “Add” service to provide name and short name.
* Upon clicking the “Add Service”, it will prompt to add function. click on “Add Function”
* Search the function name `core_enrol_get_enrolled_users` and select it
* Upon adding the screen will look something like
* Once the service is created, select it from the dropdown.
* Click “Save changes” to obtain token
***
## Installation Steps
### Download the plugin
Download the plugin’s zip file from [this URL](https://github.com/talview/moodle-quizaccess_v7_proview/releases/tag/v0.1.6).
Save the zip file to a known location on your system.
### Log in to Moodle and navigate to plugin installation
1. Log in to Moodle LMS using your administrator credentials.
2. Click on **Site Administration** in the navigation menu.
3. Click on the **Plugins** tab.
4. Click on **Install Plugins**.
***
### Upload and install the plugin
1. In the **Install Plugin from ZIP File** section, either:
* Use the **File Picker** to browse and select the downloaded zip file from your system, or
* Drag and drop the zip file directly into the file picker area.
2. Click **Install Plugin from ZIP File** to proceed.
3. Click **Continue** to complete the installation.
### Configure Proview proctoring settings
1. From the **Plugins** page, click on **Talview Proview Proctoring**.
2. On the settings page, fill in the following fields:
| Field | Value |
| :--------------------------- | :---------------------------------------------- |
| **CDN URL (Europe)** | `https://cdn.proview.io/client/init.js` |
| **CDN URL (Australia)** | `https://cdn-proview.talview.nz/client/init.js` |
| **Account Name** | Your organization's Proview account name |
| **Admin URL (Europe)** | `https://console.eu.proview.io/embedded` |
| **Admin URL (Australia)** | `https://console.au.proview.io/embedded` |
| **Admin Username** | Provided by Talview |
| **Admin Password** | Provided by Talview |
| **Root Directory** | Your organisation's configured root directory |
| **Callback URL (Europe)** | `https://lms-connector.proview.io` |
| **Callback URL (Australia)** | `https://lms-connector.talview.nz` |
> **Note:** Use only the CDN URL and Callback URL applicable to your region.
Once all fields are filled in, click **Save Changes**.
The Proview proctoring plugin is now installed and configured on your Moodle 4.5 LMS instance. Subject coordinators can now begin configuring proctoring for their quizzes.
***
## Assumptions
Before proceeding with the installation of Talview's proctoring plugins for Moodle LMS, we assume the following:
1. **Active Moodle Environment**: You have access to your Moodle platform with administrator rights. Talview Plugin is currently supported only on Moodle versions 4.0, 4.1, 4.2, 4.5
2. **Talview Subscription**: You have a valid subscription to Talview Proview services. If needed, contact the [Talview Sales Team](https://www.talview.com/contact?hsCtaTracking=6b06eef3-21df-4508-826e-0c77f9922d17%7Cede73d3b-fccd-45f2-abfa-73d38e575dec) or [Talview Tech Support](https://talview.freshdesk.com/en/support/home).
3. **Compatible Browser**: Testers will use a compatible web browser for the proctored quizzes.
Ensure your server and Moodle environment meet the necessary technical requirements for the plugins. Talview utilizes recorded alerts and configured stake to compute the Proview index, based on the candidate's behavior involving their browser, camera, and microphone. For comprehensive information on Talview's Proview flags, please consult the [Proctoring v7-Plus Events/Flags Details](https://www.notion.so/Proctoring-v7-Plus-Events-Flags-Details-6fc4b8a03d774654a95b66f76f02a3f9?pvs=21) documentation.
# Moodle LMS 4.5 - Installation Guide
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/client-admin/moodle_4.5/moodle_4.5-installation-guide
## **Introduction**
The Proview extension, developed by Talview Inc., integrates the "Proview" proctoring solution into Moodle LMS. Proview Proctoring Browser Extension is designed to deliver a secure, seamless, and efficient proctoring experience directly through your web browser. This cutting-edge extension provides robust exam integrity measures and unparalleled convenience, setting a new standard in online proctoring. This extension continuously evolves with frequent feature enhancements.
***
## Capabilities
* **Versatile and Flexible**: Proview is compatible with major web browsers, providing a consistent user experience across different devices and operating systems.
* **Live Remote Proctoring :** Live Remote Proctoring offers an end-to-end platform that supports holding multiple low to high-stakes online exams concurrently monitored by live proctors. The proctors help in authenticating test takers, monitoring exams, intervening, raising flags, terminating exams, and more.
* **Automated AI Proctoring:** Through advanced video & audio analytics, the Proview system monitors the feeds for any suspicious activity. It ensures candidate focuses on test screen during the test and checks for suspicious objects in video and background voice activity to red flag the test.
* **Record & Review:** This fully automated, AI-enabled application authenticates test takers, tracks, and records their behaviors, and flags critical events. After the exam concludes, our highly trained proctors, or those provided by you, can quickly review and confirm any event flags before certifying the validity of the exam and authenticity of test takers.
## **Prerequisites**
Before starting the integration, ensure the following details are provided:
1. **Moodle Web Service URL**
2. **Moodle Web Service Token (wstoken)**
* This token is generated by the Moodle admin.
* It will be used to authenticate Proview’s requests to Moodle.
## **Steps to create WSToken**
* Navigate to Server (Tab) > Web Services > Manage tokens
* Click on “Create token” button
* Select user who have admin access and Select service that we created in earlier ([Create external web service](/10c3461472f380af8fede190455e2cff?pvs=25#1b53461472f38072893dd53c0305add6)).
* Click “Save changes” to obtain token
## Add custom script to end proctoring upon quiz submission
To ensure proctoring ends upon click of quiz submission, add the following code snippet.
1. Navigate to Site Administration from the home page.
2. Click on the Appearance tab.
3. Click on Additional HTML.
4. Add this code snippet in the last field, and then click on Save changes.
```javascript theme={null}
```
**Tutorial video**
# Thinkific LMS - Installation Guide
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/client-admin/thinkific/thinkific-installation-guide
Follow these steps to complete the installation and configuration of the Proview Proctoring extension on Thinkific LMS through the LMS Dashboard. This enables authentication without sharing admin credentials.
## **Introduction**
The Proview extension, developed by Talview Inc., integrates the "Proview" proctoring solution into Thinkific LMS. Proview Proctoring Browser Extension is designed to deliver a secure, seamless, and efficient proctoring experience directly through your web browser. This cutting-edge extension provides robust exam integrity measures and unparalleled convenience, setting a new standard in online proctoring. This extension continuously evolves with frequent feature enhancements.
## Capabilities
* **Seamless and User-Friendly Integration**: Proview integrates effortlessly with Thinkific Learning Management System (LMS), ensuring a smooth setup process. The browser-based extension is easy to install and use, eliminating the need for complex software installations and making it accessible to a wide range of users.
* **Versatile and Flexible**: Proview is compatible with major web browsers, providing a consistent user experience across different devices and operating systems.
* **Recorded Proctoring:** Through advanced video & audio analytics, the Proview system monitors the feeds for any suspicious activity. It ensures candidate focuses on test screen during the test and checks for suspicious objects in video and background voice activity to red flag the test.
* **Record & Review:** This fully automated, AI-enabled application authenticates test takers, tracks, and records their behaviors, and flags critical events. After the exam concludes, our highly trained proctors, or those provided by you, can quickly review and confirm any event flags before certifying the validity of the exam and authenticity of test takers.
## Supported Browsers and Operating Systems
**Note:** Ensure to keep your browser and OS updated to one of these supported versions to prevent any potential issues during proctoring sessions.
Proview Proctoring solutions are supported on the following browsers:
* [Google Chrome](https://www.google.com/chrome/?brand=OPNX\&ds_kid=43700053265395784\&gclid=efe458afb020140252e33e0704417f10\&gclsrc=3p.ds&\&msclkid=efe458afb020140252e33e0704417f10\&utm_source=bing\&utm_medium=cpc\&utm_campaign=1707332%20%7C%20Chrome%20Win11%20%7C%20DR%20%7C%20ESS01%20%7C%20APAC%20%7C%20IN%20%7C%20en%20%7C%20Desk%20%7C%20SEM%20%7C%20BKWS%20-%20EXA%20%7C%20Txt%20%7C%20Bing\&utm_term=install%20chrome\&utm_content=Desk%20%7C%20BKWS%20-%20EXA%20%7C%20Txt_Install\&gclid=efe458afb020140252e33e0704417f10\&gclsrc=3p.ds) (latest 3 versions only)
* [Microsoft Edge](https://www.microsoft.com/en-us/edge/download?form=MA13FJ) (latest 3 versions only)
* [Mozilla Firefox](https://www.mozilla.org/en-US/firefox/new/) (latest 3 versions only)
Proview Proctoring solutions are supported on the following operating systems:
* **Windows Devices**: Windows 10 and Windows 11
* **Apple Devices**: macOS Sonoma
## Steps
### **1. Access LMS Dashboard**
* Log in to your LMS Dashboard.
* Click on the **“LMS Configuration”** option located at the top right of the screen.
* A pop-up will appear. Click on **“Thinkific”** as the LMS option.
### 2. Authenticate
* Fill in the following fields, and then click on Verify button
* **Name**
* **Proview Admin Username**
* **Password**
* **URL**
* Once verified successfully, click on the **Update Configuration** button, a confirmation message will appear as a browser pop up.
# How to configure proctoring for a quiz
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/instructor/blackboard/blackboard-ultra-configure-proctoring
Follow these steps to ensure a secure and proctored exam environment for your students.
## **Introduction**
Proview is a robust proctoring solution that integrates seamlessly with Blackboard Ultra, providing a secure and reliable exam environment for students. With features such as real-time monitoring, identity verification, and behavioral analysis, Proview ensures the integrity of online assessments.
This user guide will help course administrators configure Proview proctoring settings for quizzes within Blackboard Ultra LMS.
## Capabilities
* **Live Remote Proctoring :** Live Remote Proctoring offers an end-to-end platform that supports holding multiple low to high-stakes online exams concurrently monitored by live proctors. The proctors help in authenticating test takers, monitoring exams, intervening, raising flags, terminating exams, and more.
* **Automated Proctoring:** Through advanced video & audio analytics, the Proview system monitors the feeds for any suspicious activity. It ensures candidate focuses on test screen during the test and checks for suspicious objects in video and background voice activity to red flag the test.
* **Record & Review:** This fully automated, AI-enabled application authenticates test takers, tracks, and records their behaviors, and flags critical events. After the exam concludes, our highly trained proctors, or those provided by you, can quickly review and confirm any event flags before certifying the validity of the exam and authenticity of test takers.
## Supported Browsers and Operating Systems
**Note:** Ensure to keep your browser and OS updated to one of these supported versions to prevent any potential issues during proctoring sessions.
Proview Proctoring solutions are supported on the following browsers:
* [Google Chrome](https://www.google.com/chrome/?brand=OPNX\&ds_kid=43700053265395784\&gclid=efe458afb020140252e33e0704417f10\&gclsrc=3p.ds&\&msclkid=efe458afb020140252e33e0704417f10\&utm_source=bing\&utm_medium=cpc\&utm_campaign=1707332%20%7C%20Chrome%20Win11%20%7C%20DR%20%7C%20ESS01%20%7C%20APAC%20%7C%20IN%20%7C%20en%20%7C%20Desk%20%7C%20SEM%20%7C%20BKWS%20-%20EXA%20%7C%20Txt%20%7C%20Bing\&utm_term=install%20chrome\&utm_content=Desk%20%7C%20BKWS%20-%20EXA%20%7C%20Txt_Install\&gclid=efe458afb020140252e33e0704417f10\&gclsrc=3p.ds) (latest 3 versions only)
* [Microsoft Edge](https://www.microsoft.com/en-us/edge/download?form=MA13FJ) (latest 3 versions only)
* [Mozilla Firefox](https://www.mozilla.org/en-US/firefox/new/) (latest 3 versions only)
Proview Proctoring solutions are supported on the following operating systems:
* **Windows Devices**: Windows 10 and Windows 11
* **Apple Devices**: macOS Sonoma
## Steps
**1. Accessing the Quiz Settings**
* **Navigate to the Course**: Log into Blackboard Ultra LMS and go to the course where you want to configure proctoring settings.
* **Open the Quiz Page**: Select the quiz you want to enable proctoring for.
**2. Enabling Proview Proctoring**
* **Open Settings**:
* On the right side of the quiz page, locate the **Settings** option.
* Click on **Settings**. This will open a side panel with various configuration options.
* **Configure Proctoring Settings**:
* Scroll to the bottom of the side panel and under **Assessment Security**, click on **Configure Proctoring Settings**.
* **Turn On Proctoring**:
* You will see a **Turn On Proctoring** toggle, click it.
* **Save Initial Settings**:
* Click on **Save**. This action will enable additional proctoring settings to be configured.
**3. Configuring Additional Proctoring Settings**
* **Select Proctoring Token**:
* After turning on proctoring, the course and test ID gets auto populated and a new set of options will appear.
* Choose the appropriate **Proctoring Token** from the dropdown menu.
* **Select Proctoring Type**:
* From the dropdown menu, select the **Proctoring Type** that best fits your exam requirements.
* **Enter Instructions**:
* In the provided text box, enter the **Candidate Instructions** and **Proctor Instructions**. Ensure these instructions are clear and detailed to avoid any confusion during the exam.
**4. Finalizing the Configuration**
* **Submit Settings**:
* Once all settings are configured and instructions are entered, click on **Submit**.
* A confirmation message will appear indicating the successful updating of the proctoring settings.
* **Save and Finalize**:
* Close the additional proctoring settings view.
* Click on the **Save** button again to ensure all settings are properly saved and activated.
## Assumptions
* The course administrator has the necessary permissions to configure quiz settings within Blackboard Ultra LMS.
* Proview proctoring has been installed on the Blackboard Ultra account of the course admin.
* The administrator is familiar with basic navigation and operations within Blackboard Ultra LMS.
## Limitations
* **Proctoring in Separate Tab**: Proctoring is conducted in a separate tab from the quiz. If the student closes the proctoring tab, they can still continue the exam in the quiz tab, compromising the integrity of the proctoring process.
* **Communication Challenges**: Students need to switch tabs to communicate with the proctor. If the proctor sends a message in the chat, the student might not see it while on the quiz tab, leading to missed communications. Effective communication may need to be maintained through calls with the proctor.
* **iPad not supported**: Proview proctoring is not supported on iPad devices. Test takers attempting to take a proctored session on any web browser on their iPad will not be able to do so.
# How to configure proctoring for a classic quiz
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/instructor/canvas/canvas-configure-proctoring-classic-quiz
Follow these steps to ensure a secure and proctored exam environment for your students.
## Supported Browsers and Operating Systems
Ensure to keep your browser and OS updated to one of these supported versions to prevent any potential issues during proctoring sessions.
Proview Proctoring solutions are supported on the following browsers:
* [Google Chrome](https://www.google.com/chrome/?brand=OPNX\&ds_kid=43700053265395784\&gclid=efe458afb020140252e33e0704417f10\&gclsrc=3p.ds&\&msclkid=efe458afb020140252e33e0704417f10\&utm_source=bing\&utm_medium=cpc\&utm_campaign=1707332%20%7C%20Chrome%20Win11%20%7C%20DR%20%7C%20ESS01%20%7C%20APAC%20%7C%20IN%20%7C%20en%20%7C%20Desk%20%7C%20SEM%20%7C%20BKWS%20-%20EXA%20%7C%20Txt%20%7C%20Bing\&utm_term=install%20chrome\&utm_content=Desk%20%7C%20BKWS%20-%20EXA%20%7C%20Txt_Install\&gclid=efe458afb020140252e33e0704417f10\&gclsrc=3p.ds) (latest 3 versions only)
* [Microsoft Edge](https://www.microsoft.com/en-us/edge/download?form=MA13FJ) (latest 3 versions only)
* [Mozilla Firefox](https://www.mozilla.org/en-US/firefox/new/) (latest 3 versions only)
Proview Proctoring solutions are supported on the following operating systems:
* **Windows Devices**: Windows 10 and Windows 11
* **Apple Devices**: macOS Sonoma
## Steps
Ensure that the Proview browser extension is installed before starting. You can get it from [here](https://chromewebstore.google.com/detail/proview-proctoring/doblkllolfingbjkbmelgiepdggnbmhi).
**1. Go to quiz configuration**
* In the desired course, click on quiz type - New Quiz to access the quiz configurations page.
**2. Access proctoring options**
* On the right side of the quiz configuration page, click the "Proview Proctoring" icon to open a side panel.
* The panel has two tabs: **Proctoring Configurations** and **Playback View**. The Proctoring Configurations tab is open by default.
**3. Specify mandatory fields**
* For the **Live Proctoring Requirements** section, specify the **opening time**, **closing time**, and **time limit**.
**Setting quiz open date**: Ensure that the quiz's opening time is set at least **48 hours** from the current date and time to allow the proctoring service provider sufficient time to allocate resources for the proctoring session.
* For Classic Quizzes, also set the **quiz password (access code)**.
* Fields not set will show “**Not Set**”, and the "Save" button will be disabled.
* Once the quiz title, time attributes are correctly set, they will turn green and display “**Correctly Set**”.
* Until these mandatory fields are configured, the proctoring and secure browser options will not appear.
* You can also set different open and close times for students at an individual level
Since proctoring is enabled for this quiz, a message will appear to inform students that the test is proctored, and password protected. They will need to install the [Proview browser extension](https://pages.talview.com/proview-extension/) to obtain the password.
* Click on **Copy Text** to copy the message.
* Paste the copied text into the **Description Box**.
**4. Configure proctoring options**
* Return to the quiz and click the "Proview Proctoring" icon.
* Now, the proctoring options will appear. Choose the **organization**, **Proview token**, and **proctoring type** from their respective dropdown menus.
**5. Enter proctor and candidate instructions**
* Fill in specific instructions for the proctor and candidates in their respective text fields.
**6. Save final configurations**
* After completing the configurations, click the **Save** button.
## Assumptions
* The course administrator has the necessary permissions to configure quiz settings within Canvas LMS.
* The Proview browser extension is installed on the computers of all students who will be taking the exam. Or instruction is provided as part of Quiz descriptions to install the Proview browser extension
* The administrator has the Proview Browser extension installed and is familiar with basic navigation and operations within the Canvas LMS platform.
* **Special Access Arrangements**: Students requiring special access arrangements need a separate quiz created for them. They cannot be enrolled in the same quiz as regular students since proctors will not receive prior details about any special accommodations (e.g., additional time allowances). Therefore, it's necessary to create a separate quiz for students with special requirements and set the appropriate quiz attributes accordingly.
## Limitations
* **Extension requirement for instructors**: If the Proview proctoring extension is not installed, the quiz proctoring settings section will not appear. While the course admin is aware of this requirement, instructors may not be. Therefore, it is the responsibility of the course admin to inform all instructors within the organization to install the Proview extension on their systems to enable proctoring settings.
* **Manual proctoring termination**: A **stop proctoring** button is required because proctoring cannot be stopped automatically as the exam is loaded in an iframe.
* **iPad not supported**: Proview proctoring is not supported on iPad devices. Test takers attempting to take a proctored session on any web browser on their iPad will not be able to do so.
* **Chatbot support removed**: The chatbot (freshchat) support feature has been removed, which means candidates can no longer use the chatbot to communicate with the support team. However, a link to chat with Talview Technical Support will be present.
* **Loading screen triggered by extension**: With the Proview extension installed, any interaction with an quiz/assessment-related activity will trigger the extension, even if the user is not engaging with proctoring. This results in a loading screen temporarily appearing for a few seconds before the user can see Canvas. This is treated as expected behavior, and users may choose to disable the extension when not using proctoring.
# How to configure proctoring for a new quiz
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/instructor/canvas/canvas-configure-proctoring-new-quiz
Follow these steps to ensure a secure and proctored exam environment for your students.
## Supported Browsers and Operating Systems
Ensure to keep your browser and OS updated to one of these supported versions to prevent any potential issues during proctoring sessions.
Proview Proctoring solutions are supported on the following browsers:
* [Google Chrome](https://www.google.com/chrome/?brand=OPNX\&ds_kid=43700053265395784\&gclid=efe458afb020140252e33e0704417f10\&gclsrc=3p.ds&\&msclkid=efe458afb020140252e33e0704417f10\&utm_source=bing\&utm_medium=cpc\&utm_campaign=1707332%20%7C%20Chrome%20Win11%20%7C%20DR%20%7C%20ESS01%20%7C%20APAC%20%7C%20IN%20%7C%20en%20%7C%20Desk%20%7C%20SEM%20%7C%20BKWS%20-%20EXA%20%7C%20Txt%20%7C%20Bing\&utm_term=install%20chrome\&utm_content=Desk%20%7C%20BKWS%20-%20EXA%20%7C%20Txt_Install\&gclid=efe458afb020140252e33e0704417f10\&gclsrc=3p.ds) (latest 3 versions only)
* [Microsoft Edge](https://www.microsoft.com/en-us/edge/download?form=MA13FJ) (latest 3 versions only)
* [Mozilla Firefox](https://www.mozilla.org/en-US/firefox/new/) (latest 3 versions only)
Proview Proctoring solutions are supported on the following operating systems:
* **Windows Devices**: Windows 10 and Windows 11
* **Apple Devices**: macOS Sonoma
## Steps
Ensure that the Proview browser extension is installed before starting. You can get it from [here](https://chromewebstore.google.com/detail/proview-proctoring/doblkllolfingbjkbmelgiepdggnbmhi).
**1. Navigate to quiz configuration**
* In the desired course, click on quiz type - New Quiz to access the quiz configurations page.
**2. Access proctoring options**
* On the right side of the quiz configuration page, click the "Proview Proctoring" icon to open a side panel.
* The panel has two tabs: **Proctoring Configurations** and **Playback View**. The Proctoring Configurations tab is open by default.
**3. Specify mandatory fields**
* For the **Live Proctoring Requirements** section, specify the **opening time**, **closing time**, and **time limit**.
**Setting quiz open date**: Ensure that the quiz's opening time is set at least **48 hours** from the current date and time to allow the proctoring service provider sufficient time to allocate resources for the proctoring session.
* Fields not set will show “**Not Set**”, and the "Save" button will be disabled.
* Once the quiz title, time attributes are correctly set, they will turn green and display “**Correctly Set**”.
* Until these mandatory fields are configured, the proctoring and secure browser options will not appear.
* You can also set different open and close times for students at an individual level.
Since proctoring is enabled for this quiz, a message will appear to inform students that the test is proctored, and password protected. They will need to install the [Proview browser extension](https://chromewebstore.google.com/detail/proview-proctoring/doblkllolfingbjkbmelgiepdggnbmhi) to obtain the password.
* Click on **Copy Text** to copy the message.
* Paste the copied text into the **Description Box**.
**4. Configure proctoring options**
* Return to the quiz and click the "Proview Proctoring" icon.
* Now, the proctoring options will appear. Choose the **organization**, **Proview token**, and **proctoring type** from their respective dropdown menus.
**5. Enter proctor and candidate instructions**
* Fill in specific instructions for the proctor and candidates in their respective text fields.
**6. Save final configurations**
* After completing the configurations, click the **Save** button.
## Assumptions
* The course administrator has the necessary permissions to configure quiz settings within Canvas LMS.
* The Proview browser extension is installed on the computers of all students who will be taking the exam. Or instruction is provided as part of Quiz descriptions to install the Proview browser extension
* The administrator has the Proview Browser extension installed and is familiar with basic navigation and operations within the Canvas LMS platform.
* **Special Access Arrangements**: Students requiring special access arrangements need a separate quiz created for them. They cannot be enrolled in the same quiz as regular students since proctors will not receive prior details about any special accommodations (e.g., additional time allowances). Therefore, it's necessary to create a separate quiz for students with special requirements and set the appropriate quiz attributes accordingly.
## Limitations
* **Extension requirement for instructors**: If the Proview proctoring extension is not installed, the quiz proctoring settings section will not appear. While the course admin is aware of this requirement, instructors may not be. Therefore, it is the responsibility of the course admin to inform all instructors within the organization to install the Proview extension on their systems to enable proctoring settings.
* **Manual proctoring termination**: A **stop proctoring** button is required because proctoring cannot be stopped automatically as the exam is loaded in an iframe.
* **iPad not supported**: Proview proctoring is not supported on iPad devices. Test takers attempting to take a proctored session on any web browser on their iPad will not be able to do so.
* **Chatbot support removed**: The chatbot (freshchat) support feature has been removed, which means candidates can no longer use the chatbot to communicate with the support team. However, a link to chat with Talview Technical Support will be present.
* **Loading screen triggered by extension**: With the Proview extension installed, any interaction with a quiz/assessment-related activity will trigger the extension, even if the user is not engaging with proctoring. This results in a loading screen temporarily appearing for a few seconds before the user can see Canvas. This is treated as expected behavior, and users may choose to disable the extension when not using proctoring.
# How to configure self scheduling for a quiz
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/instructor/canvas/canvas-self-scheduling
Follow these steps to configure self scheduling for your classic quiz, by which students will be required to book a slot before they can attempt it.
## Steps
Ensure that the Proview browser extension is installed before starting. You can get it from [here](https://chromewebstore.google.com/detail/proview-proctoring/doblkllolfingbjkbmelgiepdggnbmhi).
**1. Navigate to quiz configuration**
* In the desired course, click on quiz type - Classic/New Quiz to access the quiz configurations page.
**2. Access proctoring options**
* On the right side of the quiz configuration page, click the "Proview Proctoring" icon to open a side panel.
* The panel has two tabs: **Proctoring Configurations** and **Playback View**. The Proctoring Configurations tab is open by default.
**3. Specify mandatory fields**
* For the **Live Proctoring Requirements** section, specify the **opening time**, **closing time**, and **time limit**.
**Setting quiz open date**: Ensure that the quiz's opening time is set at least **48 hours** from the current date and time to allow the proctoring service provider sufficient time to allocate resources for the proctoring session.
* For Classic Quizzes, also set the **quiz password (access code)**.
* Fields not set will show “**Not Set**”, and the "Save" button will be disabled.
* Once the quiz title, time attributes are correctly set, they will turn green and display “**Correctly Set**”.
* Until these mandatory fields are configured, the proctoring and secure browser options will not appear.
* You can also set different open and close times for students at an individual level
Since proctoring is enabled for this quiz, a message will appear to inform students that the test is proctored, and password protected. They will need to install the [Proview browser extension](https://pages.talview.com/proview-extension/) to obtain the password.
* Click on **Copy Text** to copy the message.
* Paste the copied text into the **Description Box**.
**4. Configure proctoring options**
* Return to the quiz and click the "Proview Proctoring" icon.
* Now, the proctoring options will appear. Choose the **organization**, **Proview token**, and **proctoring type** from their respective dropdown menus.
**5. Select scheduling type**
* Select **Live Proctoring**, then a scheduling dropdown will appear. Choose the **scheduling type** from the available options.
\*\*6. Select a proctor \*\*
* Click the **Add Proctor** button.
* A list of available proctors will appear. Select a proctor from the list by clicking on their email ID.
* Next, click the **>>** button to confirm your selection. The selected proctor's email will appear in the **Selected Proctor** column.
The candidate will be able to book a slot based on this proctor's availability.
\*\*7. Enroll as a proctor \*\*
* Click the **Add Proctor** button.
* At the bottom of the list, click the **Enroll as a Proctor** button.
* Fill in the required fields: **Email**, **Password**, and **Confirm Password**.
* Click **Submit**. You will see a confirmation message indicating that your proctor account has been successfully created.
* Your email will now be listed as a proctor available for selection.
# How to view recording of a proctored classic quiz
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/instructor/canvas/canvas-view-classic-quiz-playback
Follow these steps to access and view the playback of each student's quiz session attempt.
**1. Access the quiz playback view**
* Go to the quiz configuration page and click the **Proview Proctoring** icon.
* Switch to the **Playback View** tab.
**2. View student sessions**
* The list of students that have completed their proctored quiz will appear.
* Search can be performed by the attributes- User ID, Full name, Email, Rating
* The Proview Index rating (high/medium/low) is visible in the Proview playback list, allowing quick identification and review high-risk sessions.
**3. Playback session recording**
* Click on the session attempt “**link**” to open the playback view.
* Review the recording and generated alerts for the session.
This functionality allows you to ensure the integrity of the proctored sessions and review any incidents or irregularities during the student's attempt.
# How to view recording of a proctored new quiz
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/instructor/canvas/canvas-view-playback-new-quiz
Follow these steps to access and view the playback of each student's quiz session attempt.
**1. Access the quiz playback view**
* Go to the quiz configuration page and click the **Proview Proctoring** icon.
* Switch to the **Playback View** tab.
**2. View student sessions**
* The list of students that have completed their proctored quiz will appear.
* Search can be performed by the attributes- User ID, Full name, Email, Rating
* The Proview Index rating (high/medium/low) is visible in the Proview playback list, allowing quick identification and review high-risk sessions.
**3. Playback session recording**
* Click on the session attempt “**link**” to open the playback view.
* Review the recording and generated alerts for the session.
This functionality allows you to ensure the integrity of the proctored sessions and review any incidents or irregularities during the student's attempt.
# Configure proctoring for a quiz
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/instructor/cornerstone/csod-configure-proctoring-for-a-quiz
Follow these steps to ensure a secure and proctored exam environment for your students.
Note: Ensure that the Proview browser extension is installed before starting. You can get it from [here](https://chromewebstore.google.com/detail/proview-proctoring/doblkllolfingbjkbmelgiepdggnbmhi)
## Supported Browsers and Operating Systems
**Note:** Ensure to keep your browser and OS updated to one of these supported versions to prevent any potential issues during proctoring sessions.
Proview Proctoring solutions are supported on the following browsers:
* [Google Chrome](https://www.google.com/chrome/?brand=OPNX\&ds_kid=43700053265395784\&gclid=efe458afb020140252e33e0704417f10\&gclsrc=3p.ds&\&msclkid=efe458afb020140252e33e0704417f10\&utm_source=bing\&utm_medium=cpc\&utm_campaign=1707332%20%7C%20Chrome%20Win11%20%7C%20DR%20%7C%20ESS01%20%7C%20APAC%20%7C%20IN%20%7C%20en%20%7C%20Desk%20%7C%20SEM%20%7C%20BKWS%20-%20EXA%20%7C%20Txt%20%7C%20Bing\&utm_term=install%20chrome\&utm_content=Desk%20%7C%20BKWS%20-%20EXA%20%7C%20Txt_Install\&gclid=efe458afb020140252e33e0704417f10\&gclsrc=3p.ds) (latest 3 versions only)
* [Microsoft Edge](https://www.microsoft.com/en-us/edge/download?form=MA13FJ) (latest 3 versions only)
* [Mozilla Firefox](https://www.mozilla.org/en-US/firefox/new/) (latest 3 versions only)
Proview Proctoring solutions are supported on the following operating systems:
* **Windows Devices**: Windows 10 and Windows 11
* **Apple Devices**: macOS Sonoma
## Steps
**1. Go to the set up**
* Open [this URL](https://pages.talview.com/proview/csod/test/) in a web browser.
* Click on **Configure Quiz.**
* Enter the curriculum LOID, and click Submit. The LOID acts as a session UUID.
**2. Access proview side panel**
* On the right side of the page, click the "Proview Proctoring" icon to open a side panel.
* The panel has two tabs: **Proctoring Configurations** and **Playback View**. The Proctoring Configurations tab is open by default.
**3. Configure proctoring**
* Choose the proview token and proctoring type from the respective dropdowns.
* Fill in specific instructions for the proctor and candidates in their respective text fields.
**4. Save final configurations**
* After completing the configurations, click the **Save** button.
Your Proview proctoring settings are now configured for the selected lesson in Cornerstone LMS.
## Assumptions
* The course administrator has the necessary permissions to configure lesson settings within Cornerstone LMS.
* The Proview browser extension is installed on the computers of all students who will be taking the exam. Or instruction is provided as part of lesson descriptions to install the Proview browser extension
* The administrator has the Proview Browser extension installed and is familiar with basic navigation and operations within the Cornerstone LMS platform.
***
## Limitations
* **Extension requirement for instructors**: If the Proview proctoring extension is not installed, the quiz proctoring settings section will not appear. While the course admin is aware of this requirement, instructors may not be. Therefore, it is the responsibility of the course admin to inform all instructors within the organization to install the Proview extension on their systems to enable proctoring settings.
* **Manual proctoring termination**: A **stop proctoring** button is required because proctoring cannot be stopped automatically as the exam is loaded in an iframe.
* **iPad not supported**: Proview proctoring is not supported on iPad devices. Test takers attempting to take a proctored session on any web browser on their iPad will not be able to do so.
* **Chatbot support removed**: The chatbot (freshchat) support feature has been removed, which means candidates can no longer use the chatbot to communicate with the support team. However, a link to chat with Talview Technical Support will be present.
* **Proctoring in separate tab**: Proctoring is conducted in a separate tab from the quiz. If the student closes the proctoring tab, they can still continue the exam in the quiz tab, compromising the integrity of the proctoring process.
* **Secure browser availability:** SB and its features like screen protection & app blacklisting are not available for configuration yet.
# How to view a proctored session's recording
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/instructor/cornerstone/csod-view-session-playback
Follow these steps to access and view the playback of each student's session attempt:
**1. Access the quiz playback view**
* Return to the quiz configuration page and click the **Proview Proctoring** icon.
* Switch to the **Playback View** tab.
**2. View student sessions**
* The list of students that have completed their proctored lesson will appear.
* Search can be performed by the attributes- User ID, Full name, Email, Rating
* The Proview Index rating (high/medium/low) is visible in the Proview playback list, allowing quick identification and review high-risk sessions.
**3. Playback session recording**
* Click on the session attempt “**link**” to open the playback view.
* Review the recording and generated alerts for the session.
This functionality allows you to ensure the integrity of the proctored sessions and review any incidents or irregularities during the student's attempt.
# How to configure proctoring for a quiz
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/instructor/d2l-brightspace/d2l-configure-proctoring
Follow these steps to ensure a secure and proctored exam environment for your students.
Note: Ensure that the Proview browser extension is installed before starting. You can get it from [here](https://chromewebstore.google.com/detail/proview-proctoring/doblkllolfingbjkbmelgiepdggnbmhi).
## Steps
**1. Go to the quiz configuration**
* In the desired course, click on quiz type - New Quiz to access the quiz configurations page.
**2. Access proctoring options**
* On the right side of the quiz configuration page, click the "Proview Proctoring" icon to open a side panel.
* The panel has two tabs: **Proctoring Configurations** and **Playback View**. The Proctoring Configurations tab is open by default.
**3. Specify mandatory fields**
* **Locate password field**:
* Look to the right of the page and find the **Availability Dates & Conditions** section.
* Scroll to the bottom of this section to find the **Password** field.
* **Enter password**:
* Enter a secure password for the exam. This password is necessary for proctoring to be enforced.
* Fields not set will show “**Not Set**”, and the "Save" button will be disabled.
* Once the quiz title, time attributes are correctly set, they will turn green and display “**Correctly Set**”.
* Until these mandatory fields are configured, the proctoring and secure browser options will not appear.
Since proctoring is enabled for this quiz, a message will appear to inform students that the test is proctored and password protected. They will need to install the [Proview browser extension](https://chromewebstore.google.com/detail/proview-proctoring/doblkllolfingbjkbmelgiepdggnbmhi) to obtain the password.
* Click on **Copy Text** to copy the message.
* Paste the copied text into the **Description Box**.
**4. Configure proctoring options**
* Return to the quiz and click the "Proview Proctoring" icon.
* Now, the proctoring options will appear. Choose the **organization**, **Proview token**, and **proctoring type** from their respective dropdown menus.
**5. Enter proctor and candidate instructions**
* Fill in specific instructions for the proctor and candidates in their respective text fields.
**6. Save final configurations**
* After completing the configurations, click the **Save and Close** button.
## Assumptions
* The course administrator has the necessary permissions to configure quiz settings within D2L LMS.
* The Proview browser extension is installed on the computers of all students who will be taking the exam. Or instruction is provided as part of Quiz descriptions to install the Proview browser extension
* The administrator has the Proview Browser extension installed and is familiar with basic navigation and operations within the D2L LMS platform.
* **Special Access Arrangements**: Students requiring special access arrangements need a separate quiz created for them. They cannot be enrolled in the same quiz as regular students since proctors will not receive prior details about any special accommodations (e.g., additional time allowances). Therefore, it's necessary to create a separate quiz for students with special requirements and set the appropriate quiz attributes accordingly.
## Limitations
* **Extension requirement for instructors**: If the Proview proctoring extension is not installed, the quiz proctoring settings section will not appear. While the course admin is aware of this requirement, instructors may not be. Therefore, it is the responsibility of the course admin to inform all instructors within the organization to install the Proview extension on their systems to enable proctoring settings.
* **Manual proctoring termination**: A **stop proctoring** button is required because proctoring cannot be stopped automatically as the exam is loaded in an iframe. If a candidate in an AI-proctored or record-and-review session submits and closes the exam without clicking the **stop proctoring** button, the session will continue to appear as "in progress," potentially causing confusion and administrative issues.
* **iPad not supported**: Proview proctoring is not supported on iPad devices. Test takers attempting to take a proctored session on any web browser on their iPad will not be able to do so.
* **Chatbot support removed**: The chatbot (freshchat) support feature has been removed, which means candidates can no longer use the chatbot to communicate with the support team. However, a link to chat with Talview Technical Support will be present.
* **Browser extension region limitation:** The Proview browser extension currently supports only the EU region.
* **Validation for quiz open/close times on individual student assignments:** Different open and close times cannot be set for students at an individual level
# How to view a proctored quiz's recording
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/instructor/d2l-brightspace/d2l-view-playback
Follow these steps to access and view the playback of each student's quiz session attempt.
**1. Access the quiz playback view**
* Navigate to the quiz configuration page and click the **Proview Proctoring** icon.
* Switch to the **Playback View** tab.
**2. View student sessions**
* The list of students that have completed their proctored quiz will appear.
* Search can be performed by the attributes- User ID, Full name, Email, Rating
* The Proview Index rating (high/medium/low) is visible in the Proview playback list, allowing quick identification and review high-risk sessions.
**3. Playback session recording**
* Click on the session attempt “**link**” to open the playback view.
* Review the recording and generated alerts for the session
This functionality allows you to ensure the integrity of the proctored sessions and review any incidents or irregularities during the student's attempt.
# How to configure proctoring for a test
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/instructor/docebo/docebo-configure-proctoring-for-test
Follow these steps to ensure a secure and proctored exam environment for your students.
Note: Ensure that the Proview browser extension is installed before starting. You can get it from [**here**](https://chromewebstore.google.com/detail/proview-proctoring/doblkllolfingbjkbmelgiepdggnbmhi)**.**
## Steps
**1. Go to training materials**
* From the Docebo admin dashboard, click on **Course Management**.
* Select the desired course from the list.
* Go to the **Training Materials** tab.
* Look to the bottom and click the **Proview Proctoring** icon to open a side panel.
**2. Select a test**
* In the side panel, search for or select a **test-type** training material.
* Once selected, the panel will show two tabs: **Proctoring Configurations** and **Playback View**.
* The **Proctoring Configurations** tab is open by default.
**3. Configure proctoring options**
* Select a **Proview token** and a **Proctoring Type** from the dropdown menus.
* Enter instructions for the proctor and candidate in their respective text fields.
**4. Save final configurations**
* After completing the configurations, click the **Save** button.
## Assumptions
* The course administrator has the necessary permissions to configure lesson settings within Docebo LMS.
* The Proview browser extension is installed on the computers of all students who will be taking the exam. Or instruction is provided as part of lesson descriptions to install the Proview browser extension
* The administrator has the Proview Browser extension installed and is familiar with basic navigation and operations within the Docebo LMS platform.
## Limitations
* **Extension requirement for instructors**: If the Proview proctoring extension is not installed, the quiz proctoring settings section will not appear. While the course admin is aware of this requirement, instructors may not be. Therefore, it is the responsibility of the course admin to inform all instructors within the organization to install the Proview extension on their systems to enable proctoring settings.
* **Manual proctoring termination**: A **stop proctoring** button is required because proctoring cannot be stopped automatically as the exam is loaded in an iframe.
* **iPad not supported**: Proview proctoring is not supported on iPad devices. Test takers attempting to take a proctored session on any web browser on their iPad will not be able to do so.
* **Chatbot support removed**: The chatbot (freshchat) support feature has been removed, which means candidates can no longer use the chatbot to communicate with the support team. However, a link to chat with Talview Technical Support will be present.
* **Proctoring in separate tab**: Proctoring is conducted in a separate tab from the quiz. If the student closes the proctoring tab, they can still continue the exam in the quiz tab, compromising the integrity of the proctoring process.
* **Secure browser availability:** SB and its features like screen protection & app blacklisting are not available for configuration yet.
# How to view a proctored test's recording
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/instructor/docebo/docebo-view-playback
Follow these steps to access and view the playback of each student's test attempt.
**1. Access the test playback view**
* Navigate to the test configuration page and click the **Proview Proctoring** icon.
* Switch to the **Playback View** tab.
**2. View student sessions**
* The list of students that have completed their proctored test will appear.
* Search can be performed by the attributes- User ID, Full name, Email, Rating
* The Proview Index rating (high/medium/low) is visible in the Proview playback list, allowing quick identification and review high-risk sessions.
**3. Playback session recording**
* Click on the session attempt “**link**” to open the playback view.
* Review the recording and generated alerts for the session.
This functionality allows you to ensure the integrity of the proctored sessions and review any incidents or irregularities during the student's attempt.
# How to configure proctoring for a quiz
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/instructor/moodle/moodle-configure-proctoring
Follow these steps to configure proctoring settings for a quiz as a course admin in Moodle LMS.
**1. Access the desired quiz**
* Use your administrator credentials to log into Moodle LMS.
* Click on the **My Courses** tab in the navigation panel.
* Click on the desired course to expand its topics. Then, click on the quiz you want to configure proctoring for.
**2. Access proctoring settings**
* In the quiz page view, click on the **Settings** tab.
* Scroll past the various configuration settings until you find the **Proview Proctoring Settings** toggle. Click on this toggle to expand the proctoring section.
**3. Configure proctoring**
* From the dropdown, choose the appropriate proctoring type that suits your quiz requirements. Choose ‘No Proctoring’ if you choose to not proctor the session.
* Enter any specific instructions and reference links in their respective boxes. These will be made available to the test taker during the quiz.
**4. Set a password for the quiz:**
* Click to expand the "**Restrictions on Attempts**" section
* In the **Password** field, type in a secure password for the quiz, then press Enter to save the changes.
**5. Finalizing configuration**
* Once you have finalized all the configurations, click the **Save and return to course** button to apply the changes.
Your Proview proctoring settings are now configured for the selected quiz in Moodle LMS.
## Assumptions
* The course administrator has the necessary permissions to configure quiz settings within Moodle LMS.
* Proview proctoring has been installed on the moodle account of the course admin.
* The administrator is familiar with basic navigation and operations within Moodle LMS.
* It is assumed that the test taker will launch Proview proctored assessment in a single browser tab. Launching it in multiple tabs can potentially affect the assessment’s smooth operation with redirection issues.
## Limitations
* **Short delay in proctoring pre-flight checks**: When a student clicks on the "attempt quiz" button, the proctoring pre-flight screens should ideally appear immediately. However, currently, the student can view the first question briefly before the pre-flight screens load. This could compromise exam integrity and lead to content leakage. To mitigate this risk, it is recommended to password-protect proctored quizzes, ensuring that the quiz cannot be accessed without proper authorization, thus preventing the initial question from being visible.
* **Pre-flight checks impact on live proctored assessment’s time**: The proctoring pre-flight checks reduce the actual quiz time available to students. To combat this issue, it is suggested to add an additional 30 minutes to the quiz close time. This adjustment ensures that the pre-flight checks do not eat into the quiz duration, providing students with the full allotted time to complete the quiz.
* **iPad not supported**: Proview proctoring is not supported on iPad devices. Test takers attempting to take a proctored session on any web browser on their iPad will not be able to do so.
# How to view recording of a proctored quiz
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/instructor/moodle/moodle-view-playback
Follow these steps to access and view the playback of each student's quiz session attempt.
**1. Access the desired quiz**
* Use your administrator credentials to log into Moodle LMS.
* Click on the **My Courses** tab in the navigation panel. From the list of available courses, click on the course where you want to view student attempts for a quiz.
* Click on the desired course to expand its topics. Click on the quiz for which you want to view student attempts.
**2. Viewing student session playback**
* Click on the **Results** tab.
* Scroll to the bottom of the page to find the table containing all information on test taker attempts.
* In the **Proview URL** column, you'll find the links to view the Proview session recordings.
* Click on the **Proctor Link** corresponding to the student whose session playback you want to view.
* Upon clicking the link, a modal will open where you can view the proview session recording as well as all alerts generated during the session.
By following these steps, you can effectively view the playback of each student's proctored quiz session, ensuring that the integrity of the examination process is maintained.
# Instructor Guide - Configure Proctoring for a Quiz
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/instructor/moodle_4.5/instructor-guide-configure-proctoring-for-a-quiz
### Introduction
The Proview plugin, developed by Talview Inc., integrates the Proview proctoring solution into Moodle 4.5 LMS. It is designed to deliver a secure, seamless, and efficient proctoring experience directly through your web browser. This plugin continuously evolves with frequent feature enhancements.
This guide covers how to configure proctoring for quizzes within Moodle 4.5 LMS.
***
### Capabilities
Proview offers the following proctoring capabilities through Moodle 4.5 LMS:
* **Cross-platform compatibility**: Proview works across major web browsers and operating systems, ensuring a consistent experience for all users regardless of their device.
* **Live remote proctoring**: Supports concurrent monitoring of multiple online exams by live proctors, who handle candidate verification, active monitoring, flagging, intervention, and exam termination when necessary.
* **AI-powered recorded proctoring**: Uses advanced video and audio analytics to monitor candidate behavior, detect suspicious activity, verify screen focus, identify restricted objects, and flag background audio in real time.
* **Record and review**: Automatically records and flags candidate behavior during the exam. After the exam, trained proctors can review flagged events to certify exam validity and test taker authenticity.
***
### Supported Browsers and Operating Systems
Keep your browser and OS updated to one of the supported versions below to avoid any issues during proctoring sessions.
**Supported Browsers** (latest 3 versions only):
* [Google Chrome](https://www.google.com/chrome/?brand=OPNX\&ds_kid=43700053265395784\&gclid=efe458afb020140252e33e0704417f10\&gclsrc=3p.ds&\&msclkid=efe458afb020140252e33e0704417f10\&utm_source=bing\&utm_medium=cpc\&utm_campaign=1707332%20%7C%20Chrome%20Win11%20%7C%20DR%20%7C%20ESS01%20%7C%20APAC%20%7C%20IN%20%7C%20en%20%7C%20Desk%20%7C%20SEM%20%7C%20BKWS%20-%20EXA%20%7C%20Txt%20%7C%20Bing\&utm_term=install%20chrome\&utm_content=Desk%20%7C%20BKWS%20-%20EXA%20%7C%20Txt_Install\&gclid=efe458afb020140252e33e0704417f10\&gclsrc=3p.ds)
* [Microsoft Edge](https://www.microsoft.com/en-us/edge/download?form=MA13FJ)
**Supported Operating Systems:**
* **Windows Devices**: Windows 10 and Windows 11
* **Apple Devices**: macOS Sonoma (14.6.1), macOS Ventura (13.6.9), macOS Monterey (12.7.6).
***
### **Enable proctoring for a quiz**
**Access the quiz**
1. Log in to Moodle LMS using credentials that have quiz creation and configuration permissions.
2. Navigate to the relevant course and open the quiz you want to configure proctoring for.
**Configure proctoring settings**
1. From the quiz page, click the **Settings** tab.
2. Scroll down and expand the **Proctored Exams** section.
3. From the dropdown, select a **Proview token**.
4. From the next dropdown, select the **proctoring type** appropriate for your quiz requirements.
5. Optionally, enter any specific instructions for the **proctor** and/or the **candidate** in their respective fields.
6. Optionally, enable password injection if you have specified password for the quiz and want it to be auto injected on the candidate’s side.
7. If you want students to take the exam in a more secure, restricted environment, check the **Secure Browser** checkbox. You can then enable additional secure browser configurations using the options that appear.
| Configurations | Parameter | Default value | Example value | Description |
| :--------------------- | :--------------------------------------------------------------- | :------------ | :--------------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------- |
| Enforce SB | is\_secure\_browser | FALSE | `true` | Mandate the use of Secure Browser in a session by setting the value to TRUE. |
| Kiosk Mode | is\_minimize | FALSE | `true` | Kiosk mode is a full screen mode which blocks the user to switch between two different applications or windows. |
| Blacklist applications | blacklisted\_softwares\_windows blacklisted\_softwares\_mac | Empty | `[` `"teams",` `"lenovo vantage"` `]` | Block any applications that are restricted for the user the use for the period the session is running on secure browser. |
| Theft protection | is\_record\_screen | FALSE | `false` | Block any applications to record the user’s screen or take any screenshots, ensuring the content in the exam is not leaked. |
8. Click **Save and display** to finalize your proctoring settings.
**Demo video:**
***
### Assumptions
* The instructor has the necessary permissions to configure quiz settings within Moodle 4.5 LMS.
* Proview proctoring has been installed and configured on the institution's Moodle account.
# Instructor Guide - View Session Recordings
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/instructor/moodle_4.5/instructor-guide-view-session-recordings
### **Introduction**
The Proview plugin, developed by Talview Inc., integrates the Proview proctoring solution into Moodle 4.5 LMS. It is designed to deliver a secure, seamless, and efficient proctoring experience directly through your web browser. This plugin continuously evolves with frequent feature enhancements.
This guide covers how to view session recordings within Moodle 4.5 LMS.
***
### Capabilities
Proview offers the following proctoring capabilities through Moodle 4.5 LMS:
* **Cross-platform compatibility**: Proview works across major web browsers and operating systems, ensuring a consistent experience for all users regardless of their device.
* **Live remote proctoring**: Supports concurrent monitoring of multiple online exams by live proctors, who handle candidate verification, active monitoring, flagging, intervention, and exam termination when necessary.
* **AI-powered recorded proctoring**: Uses advanced video and audio analytics to monitor candidate behavior, detect suspicious activity, verify screen focus, identify restricted objects, and flag background audio in real time.
* **Record and review**: Automatically records and flags candidate behavior during the exam. After the exam, trained proctors can review flagged events to certify exam validity and test taker authenticity.
***
### Supported Browsers and Operating Systems
Keep your browser and OS updated to one of the supported versions below to avoid any issues during proctoring sessions.
**Supported Browsers** (latest 3 versions only):
* [Google Chrome](https://www.google.com/chrome/?brand=OPNX\&ds_kid=43700053265395784\&gclid=efe458afb020140252e33e0704417f10\&gclsrc=3p.ds&\&msclkid=efe458afb020140252e33e0704417f10\&utm_source=bing\&utm_medium=cpc\&utm_campaign=1707332%20%7C%20Chrome%20Win11%20%7C%20DR%20%7C%20ESS01%20%7C%20APAC%20%7C%20IN%20%7C%20en%20%7C%20Desk%20%7C%20SEM%20%7C%20BKWS%20-%20EXA%20%7C%20Txt%20%7C%20Bing\&utm_term=install%20chrome\&utm_content=Desk%20%7C%20BKWS%20-%20EXA%20%7C%20Txt_Install\&gclid=efe458afb020140252e33e0704417f10\&gclsrc=3p.ds)
* [Microsoft Edge](https://www.microsoft.com/en-us/edge/download?form=MA13FJ)
**Supported Operating Systems:**
* **Windows Devices**: Windows 10 and Windows 11
* **Apple Devices**: macOS Sonoma (14.6.1), macOS Ventura (13.6.9), macOS Monterey (12.7.6).
***
### Review Session Recordings
1. Navigate to the relevant course and open the proctored quiz whose recordings you want to review.
2. Click the **Proview Recordings** button on the quiz page.
3. A table will appear with the following details for each attempt:
* Candidate name and ID
* Candidate email
* Attempt count
* Proview index rating
* Recording link
4. Click the **View Recording** link for the candidate whose session you want to review.
5. A modal will open displaying all stream recordings and any alerts raised during the session.
6. Once done, click the **X** button to exit the playback.
**Demo video:**
***
### Assumptions
* The instructor has the necessary permissions to configure quiz settings within Moodle 4.5 LMS.
* Proview proctoring has been installed and configured on the institution's Moodle account.
# How to configure proctoring for a quiz
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/instructor/moodle_4.5/moodle_4.5-configure-proctoring
Follow these steps to ensure a secure and proctored exam environment for your students.
Note: Ensure that the Proview browser extension is installed before starting. You can get it from [**here**](https://chromewebstore.google.com/detail/proview-proctoring/doblkllolfingbjkbmelgiepdggnbmhi)**.**
## Steps
**1. Access the desired quiz**
* Use your administrator credentials to log into Moodle LMS.
* Click on the **My Courses** tab in the navigation panel. From the list of available courses, click on the course where you want to configure the quiz proctoring settings.
* Click on the desired course to expand its topics. Then, click on the quiz you want to configure proctoring for.
**2. Access proctoring settings**
* In the quiz page view, click on the **Settings** tab.
* On the right side of this page quiz, click the "Proview Proctoring" icon to open a side panel.
* The panel has two tabs: **Proctoring Configurations** and **Playback View**. The Proctoring Configurations tab is open by default.
**3. Configure proctoring**
* Choose the **organization**, **Proview token**, and **proctoring type** from their respective dropdown menus.
* For **Live Proctoring Requirements**, specify the **opening time**, **closing time**.
Since proctoring is enabled for this quiz, a message will appear to inform students that the test is proctored, and password protected. They will need to install the [Proview browser extension](https://chromewebstore.google.com/detail/proview-proctoring/doblkllolfingbjkbmelgiepdggnbmhi) to obtain the password.
* Click on **Copy Text** to copy the message.
* Paste the copied text into the **Description Box**.
* Fill in specific instructions for the proctor and candidates in their respective text fields.
**4. Set a Password for the Quiz (mandatory)**
* Click to expand the "**Restrictions on Attempts**" section
* In the **Password** field, type in a secure password for the quiz, then press Enter to save the changes.
**5. Save final configurations**
* After completing the configurations, click the **Save** button.
Your Proview proctoring settings are now configured for the selected quiz in Moodle LMS.
## Demo video
## Assumptions
* The course administrator has the necessary permissions to configure quiz settings within Moodle LMS.
* The Proview browser extension is installed on the computers of all students who will be taking the exam. Or instruction is provided as part of Quiz descriptions to install the Proview browser extension
* The administrator has the Proview Browser extension installed and is familiar with basic navigation and operations within the Moodle LMS platform.
## Limitations
* **Extension requirement for instructors**: If the Proview proctoring extension is not installed, the quiz proctoring settings section will not appear. While the course admin is aware of this requirement, instructors may not be. Therefore, it is the responsibility of the course admin to inform all instructors within the organization to install the Proview extension on their systems to enable proctoring settings.
* **Manual proctoring termination**: A **stop proctoring** button is required because proctoring cannot be stopped automatically as the exam is loaded in an iframe.
* **iPad not supported**: Proview proctoring is not supported on iPad devices. Test takers attempting to take a proctored session on any web browser on their iPad will not be able to do so.
* **Chatbot support removed**: The chatbot (freshchat) support feature has been removed, which means candidates can no longer use the chatbot to communicate with the support team. However, a link to chat with Talview Technical Support will be present.
# How to view recording of a proctored quiz
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/instructor/moodle_4.5/moodle_4.5-view-playback
Follow these steps to access and view the playback of each student's quiz session attempt.
**1. Access the quiz playback view**
* Go to the quiz settings page and click the **Proview Proctoring** icon.
* Switch to the **Playback View** tab.
**2. View student sessions**
* The list of students that have completed their proctored quiz will appear.
* Search can be performed by the attributes- User ID, Full name, Email, Rating
* The Proview Index rating (high/medium/low) is visible in the Proview playback list, allowing quick identification and review high-risk sessions.
**3. Playback session recording**
* Click on the session attempt “**link**” to open the playback view.
* Review the recording and generated alerts for the session.
This functionality allows you to ensure the integrity of the proctored sessions and review any incidents or irregularities during the student's attempt.
## Demo video
# How to configure proctoring for a Caveon exam
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/instructor/skilljar/skilljar-configure-proctoring-caveon
This guide will walk you through the steps to configure a proctored Caveon exam in Skilljar LMS using the Talview theme.
## Supported Browsers and Operating Systems
**Note:** Ensure to keep your browser and OS updated to one of these supported versions to prevent any potential issues during proctoring sessions.
Proview Proctoring solutions are supported on the following browsers:
* [Google Chrome](https://www.google.com/chrome/?brand=OPNX\&ds_kid=43700053265395784\&gclid=efe458afb020140252e33e0704417f10\&gclsrc=3p.ds&\&msclkid=efe458afb020140252e33e0704417f10\&utm_source=bing\&utm_medium=cpc\&utm_campaign=1707332%20%7C%20Chrome%20Win11%20%7C%20DR%20%7C%20ESS01%20%7C%20APAC%20%7C%20IN%20%7C%20en%20%7C%20Desk%20%7C%20SEM%20%7C%20BKWS%20-%20EXA%20%7C%20Txt%20%7C%20Bing\&utm_term=install%20chrome\&utm_content=Desk%20%7C%20BKWS%20-%20EXA%20%7C%20Txt_Install\&gclid=efe458afb020140252e33e0704417f10\&gclsrc=3p.ds) (latest 3 versions only)
* [Microsoft Edge](https://www.microsoft.com/en-us/edge/download?form=MA13FJ) (latest 3 versions only)
* [Mozilla Firefox](https://www.mozilla.org/en-US/firefox/new/) (latest 3 versions only)
Proview Proctoring solutions are supported on the following operating systems:
* **Windows Devices**: Windows 10 and Windows 11
* **Apple Devices**: macOS Sonoma
## Score Porting and Proview Index Logic
* Once the test-taker completes a proctored session and stops proctoring on Skilljar, the test score gets ported resulting in lesson completion. Based on the score, the test-taker is assigned a Proview index of either ‘High’, ‘Medium’ or ‘Low’.
* The criteria for the allocation of the Proview index are configurable as per the requirement. The passing limit to be considered ‘Passed’ can be defined by the user. However, test-takers with a ‘Low’ Proview index are considered ‘Failed’ even if their score is above the passing limit.
* For example, a test-taker to be failed despite scoring more than the passing marks in case of a ‘Low’ Proview Index (more than excusable number of violations).
## Steps
**1. Log in and access the Talview theme**
* Use your administrator credentials to log into the Skilljar LMS platform.
* In the left-side navigation panel, click on the **“Theming”** tab.
* Under **“Theming”**, select the **“Themes”** option.
* From the list of available themes, click on the **“Talview Theme”** option to access its settings.
**2. Add global code snippet for proctoring**
* Scroll down the Talview Theme settings page until you reach the **“Code Snippets”** section.
* Click to expand the **“Global Code Snippet”** field.
* Paste the appropriate [code snippet provided](https://www.notion.so/Amplitude-SkillJar-Integration-with-Caveon-Proview-and-TSB-72b86cac5aef44578f6a59abbeb931d5?pvs=21) by Talview into this field.
* Insert the unique token for your account within the snippet where required.
* After ensuring the code snippet and token are correctly placed, click on the **“Save”** button to apply the changes.
**3. Navigate to course management**
* In the left-side navigation menu, click on the **“Course Management”** tab.
* Select **“Courses”** to view the list of all courses on the platform.
* Click on the desired course or create a new one for which you want to configure a proctored Caveon exam.
**4. Add a proctored quiz to the course**
* Within the selected course, navigate to the **“Curriculum”** tab.
* Click on the **“New Lesson”** button to create a new lesson for the course.
* From the lesson type options, choose **“Caveon Exam”**.
**5. Finalize the quiz configuration**
* Provide a name for the exam lesson.
* **Configure proctoring for specific quizzes**
* Add the proctoring tag directly in the quiz title, such as `ai_proctored` or `rr_proctored`.
* Optionally, provide the exam stake by adding the tags into quiz title: `_ls` (low stake), `_ms` (medium stake), or `_hs` (high stake).
* **Configure proctoring for multiple quizzes**
* Scroll to the bottom of the course view page.
* In the **Tags** field, enter the proctoring tag, such as `ai_proctored` or `rr_proctored`.
* Optionally, provide the exam stake by adding the tags into the course title: `_ls` (low stake), `_ms` (medium stake), or `_hs` (high stake).
If stake tag is not specified (low, medium, or high) within the quiz or course title, the system will default to configuring the proctored stake to a **medium stake**.
* From the dropdown menu, select the appropriate integration.
* Next, enter the Caveon Exam ID and content in their respective fields.
* Once all details are finalized, click on the **“Save Lesson”** button.
**6. Publish the course**
* After saving the lesson, click on the **“Manage Course”** button.
* Next, click on the **“Publish Course”** button to make the course live.
* From the dropdown menu, select the appropriate domain for the course publication.
* [https://talview-test-domain.skilljar.com/](https://talview-test-domain.skilljar.com/)
* Scroll to the bottom of the page and click the **“Save”** button to finalize the publication process.
# How to configure proctoring for an LTI lesson
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/instructor/skilljar/skilljar-configure-proctoring-lti-lesson
This guide will walk you through the steps to configure an LTI lesson in Skilljar LMS.
## Supported Browsers and Operating Systems
**Note:** Ensure to keep your browser and OS updated to one of these supported versions to prevent any potential issues during proctoring sessions.
Proview Proctoring solutions are supported on the following browsers:
* [Google Chrome](https://www.google.com/chrome/?brand=OPNX\&ds_kid=43700053265395784\&gclid=efe458afb020140252e33e0704417f10\&gclsrc=3p.ds&\&msclkid=efe458afb020140252e33e0704417f10\&utm_source=bing\&utm_medium=cpc\&utm_campaign=1707332%20%7C%20Chrome%20Win11%20%7C%20DR%20%7C%20ESS01%20%7C%20APAC%20%7C%20IN%20%7C%20en%20%7C%20Desk%20%7C%20SEM%20%7C%20BKWS%20-%20EXA%20%7C%20Txt%20%7C%20Bing\&utm_term=install%20chrome\&utm_content=Desk%20%7C%20BKWS%20-%20EXA%20%7C%20Txt_Install\&gclid=efe458afb020140252e33e0704417f10\&gclsrc=3p.ds) (latest 3 versions only)
* [Microsoft Edge](https://www.microsoft.com/en-us/edge/download?form=MA13FJ) (latest 3 versions only)
* [Mozilla Firefox](https://www.mozilla.org/en-US/firefox/new/) (latest 3 versions only)
Proview Proctoring solutions are supported on the following operating systems:
* **Windows Devices**: Windows 10 and Windows 11
* **Apple Devices**: macOS Sonoma
## Score Porting and Proview Index Logic
* Once the test-taker completes a proctored session and stops proctoring on Skilljar, the test score gets ported resulting in lesson completion. Based on the score, the test-taker is assigned a Proview index of either ‘High’, ‘Medium’ or ‘Low’.
* The criteria for the allocation of the Proview index are configurable as per the requirement. The passing limit to be considered ‘Passed’ can be defined by the user. However, test-takers with a ‘Low’ Proview index are considered ‘Failed’ even if their score is above the passing limit.
* For example, a test-taker to be failed despite scoring more than the passing marks in case of a ‘Low’ Proview Index (more than excusable number of violations).
## Steps
**1. Log in and access the Course Management**
* Use your administrator credentials to log into the Skilljar LMS platform.
* In the left-side navigation menu, click on the **“Course Management”** tab.
* Select **“Courses”** to view the list of all courses on the platform.
* Click on the desired course or create a new one for which you want to configure an LTI Lesson.
**2. Add the lesson to the course**
* Within the selected course, navigate to the **“Curriculum”** tab.
* Click on the **“New Lesson”** button to create a new lesson for the course.
* From the lesson type options, choose **“LTI 1.1 Lesson”**.
**3. Finalize the quiz configuration**
* Provide a name for the exam lesson.
* From the dropdown menu, select the appropriate integration.
* Next, enter the **LTI Launch URL** in the respective field.
* Check mark the option **Complete lesson based on LTI Basic Response Outcome Response** and subsequently also check mark the option **Use Basic Outcome Response as Lesson Score.**
* Once all details are finalized, click on the **“Save Lesson”** button.
**4. Publish the course**
* After saving the lesson, click on the **“Manage Course”** button.
* Next, click on the **“Publish Course”** button to make the course live.
* From the dropdown menu, select the appropriate domain for the course publication.
* [https://talview-test-domain.skilljar.com/](https://talview-test-domain.skilljar.com/)
* Scroll to the bottom of the page and click the **“Save”** button to finalize the publication process.
# How to configure proctoring for a quiz
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/instructor/skilljar/skilljar-configure-proctoring-quiz
This guide will walk you through the steps to configure a proctored native quiz in Skilljar LMS using the Talview theme.
## Supported Browsers and Operating Systems
**Note:** Ensure to keep your browser and OS updated to one of these supported versions to prevent any potential issues during proctoring sessions.
Proview Proctoring solutions are supported on the following browsers:
* [Google Chrome](https://www.google.com/chrome/?brand=OPNX\&ds_kid=43700053265395784\&gclid=efe458afb020140252e33e0704417f10\&gclsrc=3p.ds&\&msclkid=efe458afb020140252e33e0704417f10\&utm_source=bing\&utm_medium=cpc\&utm_campaign=1707332%20%7C%20Chrome%20Win11%20%7C%20DR%20%7C%20ESS01%20%7C%20APAC%20%7C%20IN%20%7C%20en%20%7C%20Desk%20%7C%20SEM%20%7C%20BKWS%20-%20EXA%20%7C%20Txt%20%7C%20Bing\&utm_term=install%20chrome\&utm_content=Desk%20%7C%20BKWS%20-%20EXA%20%7C%20Txt_Install\&gclid=efe458afb020140252e33e0704417f10\&gclsrc=3p.ds) (latest 3 versions only)
* [Microsoft Edge](https://www.microsoft.com/en-us/edge/download?form=MA13FJ) (latest 3 versions only)
* [Mozilla Firefox](https://www.mozilla.org/en-US/firefox/new/) (latest 3 versions only)
Proview Proctoring solutions are supported on the following operating systems:
* **Windows Devices**: Windows 10 and Windows 11
* **Apple Devices**: macOS Sonoma
## Score Porting and Proview Index Logic
* Once the test-taker completes a proctored session and stops proctoring on Skilljar, the test score gets ported resulting in lesson completion. Based on the score, the test-taker is assigned a Proview index of either ‘High’, ‘Medium’ or ‘Low’.
* The criteria for the allocation of the Proview index are configurable as per the requirement. The passing limit to be considered ‘Passed’ can be defined by the user. However, test-takers with a ‘Low’ Proview index are considered ‘Failed’ even if their score is above the passing limit.
* For example, a test-taker to be failed despite scoring more than the passing marks in case of a ‘Low’ Proview Index (more than excusable number of violations).
## Steps
**1. Log in and access the Talview theme**
* Use your administrator credentials to log into the Skilljar LMS platform.
* In the left-side navigation panel, click on the **“Theming”** tab.
* Under **“Theming”**, select the **“Themes”** option.
* From the list of available themes, click on the **“Talview Theme”** option to access its settings.
**2. Add global code snippet for proctoring**
* Scroll down the Talview Theme settings page until you reach the **“Code Snippets”** section.
* Click to expand the **“Global Code Snippet”** field.
* Paste the appropriate [code snippet provided](https://www.notion.so/Shopify-SkillJar-Quiz-Integration-with-Proview-Embedded-5231e774c3cb47cb9192321da12d4946?pvs=21) by Talview into this field.
* Insert the unique token for your account within the snippet where required.
* After ensuring the code snippet and token are correctly placed, click on the **“Save”** button to apply the changes.
**3. Navigate to course management**
* In the left-side navigation menu, click on the **“Course Management”** tab.
* Select **“Courses”** to view the list of all courses on the platform.
* Click on the desired course or create a new one for which you want to configure proctored quiz.
**4. Add a proctored quiz to the course**
* Within the selected course, navigate to the **“Curriculum”** tab.
* Click on the **“New Lesson”** button to create a new lesson for the course.
* From the lesson type options, choose **“Quiz”**.
* You can either create a new quiz or select an existing quiz for this lesson.
**5. Finalize the quiz configuration**
* Provide a name for the quiz lesson.
* Once all details are finalized, click on the **“Save Lesson”** button.
* **Configure proctoring for specific quizzes**
* Add the proctoring tag directly in the quiz title, such as `ai_proctored` or `rr_proctored`.
* Optionally, provide the exam stake by adding the tags into quiz title: `_ls` (low stake), `_ms` (medium stake), or `_hs` (high stake).
* **Configure proctoring for multiple quizzes**
* Scroll to the bottom of the course view page.
* In the **Tags** field, enter the proctoring tag, such as `ai_proctored` or `rr_proctored`.
* Optionally, provide the exam stake by adding the tags into the course title: `_ls` (low stake), `_ms` (medium stake), or `_hs` (high stake).
If stake tag is not specified (low, medium, or high) within the quiz or course title, the system will default to configuring the proctored stake to a **medium stake**.
**6. Publish the course**
* After saving the lesson, click on the **“Manage Course”** button.
* Next, click on the **“Publish Course”** button to make the course live.
* From the dropdown menu, select the appropriate domain for the course publication.
* [https://talview-test-domain.skilljar.com/](https://talview-test-domain.skilljar.com/)
* Scroll to the bottom of the page and click the **“Save”** button to finalize the publication process.
# How to configure proctoring for a lesson
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/instructor/thinkific/thinkific-configure-proctoring-for-a-lesson
Follow these steps to ensure a secure and proctored exam environment for your students.
Note: Ensure that the Proview browser extension is installed before starting. You can get it from [**here**](https://chromewebstore.google.com/detail/proview-proctoring/doblkllolfingbjkbmelgiepdggnbmhi)**.**
## Steps
**1. Navigate to lesson configuration**
* In the desired course, click on a lesson
**2. Access proctoring options**
* On the right side of the lesson configuration page, click the "Proview Proctoring" icon to open a side panel.
* The panel has two tabs: **Proctoring Configurations** and **Playback View**. The Proctoring Configurations tab is open by default.
**3. Enter proctor and candidate instructions**
* Fill in specific instructions for the proctor and candidates in their respective text fields.
**4. Save final configurations**
* After completing the configurations, click the **Save** button.
## Assumptions
* The course administrator has the necessary permissions to configure lesson settings within Thinkific LMS.
* The Proview browser extension is installed on the computers of all students who will be taking the exam. Or instruction is provided as part of lesson descriptions to install the Proview browser extension
* The administrator has the Proview Browser extension installed and is familiar with basic navigation and operations within the Thinkific LMS platform.
## Limitations
* **Extension requirement for instructors**: If the Proview proctoring extension is not installed, the quiz proctoring settings section will not appear. While the course admin is aware of this requirement, instructors may not be. Therefore, it is the responsibility of the course admin to inform all instructors within the organization to install the Proview extension on their systems to enable proctoring settings.
* **Manual proctoring termination**: A **stop proctoring** button is required because proctoring cannot be stopped automatically as the exam is loaded in an iframe.
* **iPad not supported**: Proview proctoring is not supported on iPad devices. Test takers attempting to take a proctored session on any web browser on their iPad will not be able to do so.
* **Chatbot support removed**: The chatbot (freshchat) support feature has been removed, which means candidates can no longer use the chatbot to communicate with the support team. However, a link to chat with Talview Technical Support will be present.
* **Proctoring in separate tab**: Proctoring is conducted in a separate tab from the quiz. If the student closes the proctoring tab, they can still continue the exam in the quiz tab, compromising the integrity of the proctoring process.
* **Secure browser availability:** SB and its features like screen protection & app blacklisting are not available for configuration yet.
* **Multi attempt tracking unavailable:** Currently, Thinkific LMS restricts students to only one attempt for a quiz.
# How to view a proctored lesson's recording
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/instructor/thinkific/thinkific-view-session-playback
Follow these steps to access and view the playback of each student's lesson session attempt.
**1. Access the lesson playback view**
* Go to the lesson configuration page and click the **Proview Proctoring** icon.
* Switch to the **Playback View** tab.
**2. View student sessions**
* The list of students that have completed their proctored lesson will appear.
* Search can be performed by the attributes- User ID, Full name, Email, Rating
* The Proview Index rating (high/medium/low) is visible in the Proview playback list, allowing quick identification and review high-risk sessions.
**3. Playback session recording**
* Click on the session attempt “**link**” to open the playback view.
* Review the recording and generated alerts for the session.
# Configure proctoring for a SCORM package
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/instructor/totara/configure-proctoring-scorm-package
Follow these steps to ensure a secure and proctored SCORM package environment for your students.
Note: Ensure that the Proview browser extension is installed before starting. You can get it from [here](https://chromewebstore.google.com/detail/proview-proctoring/doblkllolfingbjkbmelgiepdggnbmhi)
### **Introduction**
The Proview extension, developed by Talview Inc., integrates the "Proview" proctoring solution into Totara LMS. Proview Proctoring Browser Extension is designed to deliver a secure, seamless, and efficient proctoring experience directly through your web browser. This cutting-edge extension provides robust SCORM package integrity measures and unparalleled convenience, setting a new standard in online proctoring. This extension continuously evolves with frequent feature enhancements.
### Capabilities
* **Seamless and user-friendly integration**: Proview integrates effortlessly Totara LMS, ensuring a smooth setup process. The browser-based extension is easy to install and use, eliminating the need for complex software installations and making it accessible to a wide range of users.
* **Recorded proctoring:** Through advanced video & audio analytics, the Proview system monitors the feeds for any suspicious activity. It ensures candidate focuses on test screen during the test and checks for suspicious objects in video and background voice activity to red flag the test.
* **Record & Review:** This fully automated, AI-enabled application authenticates test takers, tracks, and records their behaviors, and flags critical events. After the SCORM package concludes, our highly trained proctors, or those provided by you, can quickly review and confirm any event flags before certifying the validity of the SCORM package and authenticity of test takers.
### Supported Browsers and Operating Systems
**Note:** Ensure to keep your browser and OS updated to one of these supported versions to prevent any potential issues during proctoring sessions.
Proview Proctoring solutions are supported on the following browsers:
* [Google Chrome](https://www.google.com/chrome/?brand=OPNX\&ds_kid=43700053265395784\&gclid=efe458afb020140252e33e0704417f10\&gclsrc=3p.ds&\&msclkid=efe458afb020140252e33e0704417f10\&utm_source=bing\&utm_medium=cpc\&utm_campaign=1707332%20%7C%20Chrome%20Win11%20%7C%20DR%20%7C%20ESS01%20%7C%20APAC%20%7C%20IN%20%7C%20en%20%7C%20Desk%20%7C%20SEM%20%7C%20BKWS%20-%20EXA%20%7C%20Txt%20%7C%20Bing\&utm_term=install%20chrome\&utm_content=Desk%20%7C%20BKWS%20-%20EXA%20%7C%20Txt_Install\&gclid=efe458afb020140252e33e0704417f10\&gclsrc=3p.ds) (latest 3 versions only)
* [Microsoft Edge](https://www.microsoft.com/en-us/edge/download?form=MA13FJ) (latest 3 versions only)
* [Mozilla Firefox](https://www.mozilla.org/en-US/firefox/new/) (latest 3 versions only)
Proview Proctoring solutions are supported on the following operating systems:
* **Windows Devices**: Windows 10 and Windows 11
* **Apple Devices**: macOS Sonoma
### Steps
**1. Open the desired course**
* Log in to your **Totara LMS** account.
* Navigate to the course where the **SCORM package** is available.
* Enable **Editing Mode**.
**2. Access the SCORM package**
* Locate the SCORM package you want to configure for and click it.
**3. Access Proview Proctoring panel**
* Once the SCORM package settings page loads, click the **Proview Proctoring** icon.
* The **Proctoring Configuration Panel** will appear on the right-hand side.
**4. Configure proctoring options**
* Select the **Proview Token** and the desired **Proctoring Type** from the dropdown menus.
* Optionally, enter **Candidate Instructions** in the respective field.
**6. Save final configurations**
* After finalizing all configurations, click the **Save** button.
* The SCORM package is now configured for **Proview Proctoring**.
### Assumptions
* The course administrator has the necessary permissions to configure SCORM package settings within Totara LMS.
* The Proview browser extension is installed on the computers of all students who will be taking the SCORM package. Or instruction is provided as part of SCORM package descriptions to install the Proview browser extension
* The administrator has the Proview Browser extension installed and is familiar with basic navigation and operations within the Totara LMS platform.
### Limitations
* **Extension requirement for instructors**: If the Proview proctoring extension is not installed, the SCORM package proctoring settings section will not appear. While the course admin is aware of this requirement, instructors may not be. Therefore, it is the responsibility of the course admin to inform all instructors within the organization to install the Proview extension on their systems to enable proctoring settings.
* **Manual proctoring termination**: A **stop proctoring** button is required because proctoring cannot be stopped automatically as the SCORM package is loaded in an iframe.
* **iPad not supported**: Proview proctoring is not supported on iPad devices. Test takers attempting to take a proctored session on any web browser on their iPad will not be able to do so.
* **Chatbot support removed**: The chatbot (freshchat) support feature has been removed, which means candidates can no longer use the chatbot to communicate with the support team. However, a link to chat with Talview Technical Support will be present.
* **Secure browser availability:** SB and its features like screen protection & app blacklisting are not available for configuration yet.
# Access session recording
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/instructor/totara/view-playback-scorm-package
Follow these steps to access and view the playback of each student's SCORM package session attempt.
**1. Open the desired course**
* Log in to your **Totara LMS** account.
* Navigate to the course where the **SCORM package** is available.
* Enable **Editing Mode**.
**2. Access the SCORM package**
* Locate the SCORM package you want to view the recording of, and click it.
**3. Access Playback View**
* Once the SCORM package settings page loads, click the **Proview Proctoring** icon.
* The **Proctoring Configuration Panel** will appear on the right-hand side.
* Switch to the **Playback View** tab.
**4. View student sessions**
* The list of students that have completed their proctored SCORM package will appear.
* Search can be performed by the attributes- User ID, Full name, Email, Rating
* The Proview Index rating (high/medium/low) is visible in the Proview playback list, allowing quick identification and review high-risk sessions.
**5. Playback session recording**
* Click on the session attempt “**link**” to open the playback view.
* Review the recording and generated alerts for the session.
This functionality allows you to ensure the integrity of the proctored sessions and review any incidents or irregularities during the student's attempt.
# Getting Started with LMS Integrations
Source: https://docs.talview.com/admin/configurations/integrations/lms-integrations/lms-getting-started
Set up and manage Learning Management System (LMS) integrations to streamline training and assessments with Talview.
Connect Talview with Canvas to deliver assessments and sync results seamlessly.
Integrate with Cornerstone to streamline training workflows and learner assessments.
Enable assessments and reporting directly inside Brightspace for smooth learner management.
Connect Talview with Docebo to manage training modules, assessments, and learner analytics.
Add Talview assessments to Moodle courses and track learner performance with ease.
Updated integration guide for Moodle 4.5, ensuring compatibility with the latest features.
Deliver skill-based training with Talview assessments inside Skilljar’s learning paths.
Combine Talview’s assessments with Thinkific courses to evaluate learner progress effectively.
# Talview + Lemon Squeezy Integration
Source: https://docs.talview.com/admin/configurations/integrations/payments/lemon-squeezy-integration
## Feature Document
## 1. Overview
Talview integrates with **Lemon Squeezy**, a Merchant of Record (MoR) platform, to simplify payments and tax compliance for exams, assessments, and certification bookings. With this integration: Candidates can pay seamlessly using Lemon Squeezy’s checkout. Talview automatically tracks payment status and updates candidate bookings. Global tax compliance (VAT, GST, sales tax) is handled by Lemon Squeezy.
## 2. How the Integration Works
### a. Booking & Payment Flow
1. **Candidate Books an Exam** → Candidate selects exam slot on Talview.
2. **Payment via Lemon Squeezy** → Candidate is directed to a Lemon Squeezy checkout page.
3. **Transaction Completion** → Lemon Squeezy processes payment, applies taxes, and confirms success or failure.
4. \*\*Talview Updates Booking: \*\*
* If **Payment Successful** → Candidate booking is confirmed.
* If **Payment Failed** → Lemon Squeezy keeps the candidate on their portal on immediate failure and candidate can reattempt by changing payment method.
* If **Payment Pending** → Booking stays on hold for 15 mins. If the payment confirmation is not sent by Lemon Squeezy within 15 mins, we cancel the booking.
### b. Taxes & Compliance
* Lemon Squeezy automatically detects candidate’s location and applies correct VAT/GST/sales tax. Tax receipts and invoices are shared directly with candidates.
* Tax receipts and invoices are shared directly with candidates.
## 3. Supported Countries & Payment Methods
### Countries Supported for Purchases
Lemon Squeezy allows purchases from almost all countries globally, **except** the following restricted list:
**Unsupported countries include** [(Lemon Squeezy Docs)](https://docs.lemonsqueezy.com/help/getting-started/supported-countries#unsupported-countries-for-purchases):
* Central African Republic
* Cuba
* Democratic People’s Republic of Korea
* Democratic Republic of the Congo
* Eritrea
* Guinea-Bissau
* Iran
* Iraq
* Lebanon
* Libya
* Mali
* North Korea
* Russian Federation
* Somalia
* South Sudan
* Sudan
* Syrian Arab Republic
* Yemen
## 4. Available Payment Methods by Country
Below are the supported methods, available today
* **Credit & Debit Cards:** Visa, Mastercard, American Express, Discover, Diners Club, JCB, and China UnionPay - accepted globally. ([Lemon Squeezy Docs](https://docs.lemonsqueezy.com/help/checkout/payment-methods?utm_source=chatgpt.com))
* **PayPal:** Available broadly, with global coverage.
\*\*In Talview Roadmap: \*\*
* \*\*Digital Wallets: \*\*
* Apple Pay (Safari only)
* Google Pay (Chrome only)
* Amazon Pay
* **Bank Debits:** Such as ACH; region-specific availability.
# Talview + Cleverbridge Integration
Source: https://docs.talview.com/admin/configurations/integrations/payments/talview-cleverbridge-integration
## **Overview**
Talview integrates with **Cleverbridge**, a Merchant of Record (MoR) platform, to simplify global exam payment collection and ensure tax compliance for exams, assessments, and certification bookings.
With this integration:
* Candidates can complete payments securely using Cleverbridge’s hosted checkout.
* Talview automatically tracks and updates candidate booking and payment status.
* Global tax handling (VAT, GST, Sales Tax) is managed by Cleverbridge in compliance with local laws.
***
## **1. How the Integration Works**
### **a. Booking & Payment Flow**
1. **Candidate Books an Exam**
→ Candidate selects a slot on Talview.
> *The sequence is configurable within Talview. Customers can choose whether candidates book their e slot before payment or after completing payment, based on their preferred workflow.*
1. **Redirect to Cleverbridge Checkout**
→ Candidate is redirected to Cleverbridge’s hosted checkout page.
→ Pricing, taxes, and localization (currency, language) are automatically handled.
2. **Payment Processing**
→ Cleverbridge processes the payment using the candidate’s selected payment method.
→ Taxes are calculated and applied automatically.
3. **Transaction Completion**
* **If Payment Successful** → Talview marks the payment status as *Confirmed* and automatically sends an invoice to the candidate.
* **If Payment Failed** → Cleverbridge redirects the candidate back to Talview. The candidate’s slot remains reserved for a limited period, during which they can retry the payment.
* **If Payment Pending** → Payments may remain in a *Pending* state for up to 24 hours. Transactions that require additional authorization or review are held until Cleverbridge completes verification and shares the final status with Talview.
4. **Status Sync to Talview**
→ Cleverbridge sends real-time webhooks to Talview’s backend for:
* Payment success
* Payment failure
* Partial refund/complete refund or chargeback events
### **b. Taxes & Compliance**
* Cleverbridge determines the buyer’s tax location automatically via billing address and IP.
* The correct **VAT/GST/Sales Tax** is applied per jurisdiction.
* Talview receives payment confirmation data but not tax filing data (handled by Cleverbridge as MoR).
***
## **2. Supported Countries & Payment Methods**
### **a. Supported Countries**
Cleverbridge supports transactions in most countries globally, excluding regions restricted under international sanctions or export control laws.
### **b. Supported Payment Methods**
Cleverbridge supports multiple payment options globally, with localized availability:
* **Credit/Debit Cards** – Visa, Mastercard, American Express, Discover, JCB, Diners Club
* **PayPal** – Available globally
***
## **3. Refunds and Disputes**
* Refunds are initiated through Cleverbridge’s dashboard or API.
* Talview can trigger a full or partial refund event via API if a candidate cancels an exam within allowed policy timelines.
* Cleverbridge processes the refund to the original payment method and updates Talview via webhook.
* Chargebacks or disputes raised by customers are handled directly by Cleverbridge.
***
## **4. Data Flow and Integration Points**
| **Event** | **Source System** | **Destination System** | **Data Passed** | **Purpose** |
| :-------------------- | :---------------- | :--------------------- | :------------------------------------------------------- | :------------------------ |
| Exam Booking | Talview | Cleverbridge | Talview Transaction ID, Product/Exam ID, Price, Currency | Initiate checkout |
| Payment Completion | Cleverbridge | Talview | Transaction ID, Status, Amount, Tax details | Confirm booking |
| Refund Initiation | Talview | Cleverbridge | Transaction ID, refund amount | Trigger refund |
| Refund/Dispute Update | Cleverbridge | Talview | Status, Amount, Reason | Update transaction record |
## **In Talview Roadmap**
* **Digital Wallets** - Apple Pay, Google Pay, etc.
* Enhanced reporting in Talview Dashboard for **Revenue & Tax breakdown**
# Talview + Stripe Integration
Source: https://docs.talview.com/admin/configurations/integrations/payments/talview-stripe-integration
## **Overview**
Talview integrates with **Stripe**, a leading global payment platform, to enable smooth and secure payment collection for exams, assessments, and certifications.
With this integration:
* Candidates can pay seamlessly through Stripe’s hosted checkout.
* Talview automatically tracks payment status and updates candidate bookings.
* Stripe enables **local-currency payments** for candidates, while **Talview receives settlements in USD**.
***
## 1. How the Integration Works
### a. Booking & Payment Flow
1. **Candidate Books an Exam** → Candidate selects the exam slot on Talview.
2. **Payment via Stripe Checkout** → Candidate is redirected to a Stripe-hosted checkout page.
3. **Transaction Completion**
* **Payment Successful** → Stripe confirms the payment; Talview marks the booking as *confirmed*.
* **Payment Failed** → Candidate can retry payment with another method on the same page.
4. **Talview Updates Booking** → Stripe web hooks send real-time payment status updates to Talview.
### **b. Taxes & Compliance**
* Stripe does **not** act as Merchant of Record.
* Stripe can **display prices inclusive of tax** (for clarity to candidates), but **tax calculation and remittance** remain Talview’s responsibility.
* Automated tax calculation or remittance is **not enabled** in this setup; tax-related configurations depend on the organization’s internal setup.
***
## **2. Supported Countries & Payment Methods**
### **Countries Supported**
Stripe supports transactions from **190 + countries**, with localized payment and currency options (subject to regional regulations).
### **Payment Methods**
* **Credit & Debit Cards:** Visa, Mastercard, American Express, Discover, JCB, UnionPay
* **Wallets:** Paypal
***
## **3. Key Benefits**
✅ **Global reach with local currency support** - candidates can pay in their own currency while reconciliation happens in USD.
✅ **Higher payment success rates** due to Stripe’s optimized routing and regional processing.
✅ **Frictionless checkout** on both desktop and mobile.
✅ **Real-time status sync** between Stripe and Talview.
✅ **Transparent pricing** - Talview can send prices inclusive of tax to Stripe for display.
# Standard Talview Authentication
Source: https://docs.talview.com/admin/configurations/integrations/workflow-integrations/authentication/standard-talview-authentication
Every API request to Talview needs to be authenticated by passing the `access_token` received with the response of the below-mentioned login API.
**Request header definition:**
| Method | POST |
| :----------- | :------------------------------------------------- |
| **Host** | [https://api.talview.com](https://api.talview.com) |
| Route | /api/rest/auth\_user\_login |
| Content type | application/json |
**Request payload definition:**
| Attribute | Data Type | Mandatory | Description |
| :--------- | :-------- | :-------- | :----------------------------------------------------------------------------------- |
| username | String | Yes | API username that will be shared by Talview |
| password | String | Yes | API password that will be shared by Talview |
| tenant\_id | Integer | Yes | Tenant identifier for each of the organization on Talview, will be shared by Talview |
**Sample request payload:**
```text theme={null}
{
"username": "username@talview.com",
"password": "secure_password",
"tenant_id": 1
}
```
**Sample response payload:**
1. Success response: HTTP status code - 201
```text theme={null}
{
"auth_user_login": {
"success": true,
"error_message": null,
"data": {
"access_token": "<:jwt_token:>",
"expires_in": 1715077045,
"refresh_token": "<:refresh_token:>"
}
}
}
```
2. Error Response: HTTP status code - 401
```text theme={null}
{
"error": "Wrong username/password"
}
```
**Sample CURL request:**
```bash theme={null}
curl --request POST \\
--url https://supergraph.talview.com/api/rest/auth_user_login \\
--data '{
"username": "username@talview.com",
"password": "secure_password",
"tenant_id": 1
}'
```
# Talview Workflow Callback Integration Flow
Source: https://docs.talview.com/admin/configurations/integrations/workflow-integrations/workflow-api-endpoints/callback
Talview Standard Assessment Workflow Callback Api provides mechanism for sending assessment reports,scores,video playback url's and etc.
### Prerequisites
1. Please follow Workflow Schedule OR Workflow Invite page inviting candidates to assessments on Talview.
## Callback Integrations Steps
1. Callback Url can be setup in our system.
2. Once Callback Url endpoint is setup in our system, we will trigger data in below standard structure to \ system.
**Request payload definition: Standard**
| Attribute | Mandatory | Data Type | Description |
| :-------------------------------- | :-------- | :-------- | :----------------------------------------------------------------------------------------------------------------------------------- |
| report\_url | no | String | Candidate Assessment report url based on the standard skills setup in our system. Its a signed url which has a expiration time. |
| playback\_url | no | String | Playback url of Assessment Async video or Interview recorded video |
| overall\_score | no | Number | Overall score of candidate in async mcq section of assessment |
| candidate\_reference\_id | no | String | Candidate’s ID in External System |
| workflow\_reference\_id | no | String | Talview Workflow ID |
| workflow\_step\_reference\_id | no | String | WorkflowStep ID from external client system |
| workflow\_id | no | String | Talview Workflow ID |
| candidate\_id | no | Number | Talview Candidate ID |
| workflow\_candidate\_step\_status | yes | String | Step status of the candidate |
| workflow\_step\_id | no | Number | Talview Workflow step id |
**Sample response payload:**
1. Success response: HTTP status code - 2xx
2. Error response: HTTP status code - 4xx
**Sample CURL request:**
```bash theme={null}
curl --request POST \
--url https://abc.com/callback/report \
--data '{
"report_url": "AWS signed url",
"playback_url": "https://wt.talview.com/workflow/{{workflow_id}}/invite/{{workflow_candidate_step_id}}",
"overall_score": 35,
"candidate_reference_id": "CAN-291",
"workflow_reference_id": "ASS-31",
"workflow_step_reference_id": "ASS-1A-31"
}'
```
# Talview Workflow Invite Flow
Source: https://docs.talview.com/admin/configurations/integrations/workflow-integrations/workflow-api-endpoints/workflow-invite
To integrate with Talview WFT (Workflow Tools) Assessment, please follow the steps below.
## Assessment Invite Technical Steps
### 1. Authentication
* Use this [guide](../Authentication) to generate an **`access_token`**.
* The token generated will go in `Authorization` header for all API calls.
### 2. Assessment Invite API
Every assessment invitation sent to Talview, must follow the below payload structure.
**Request header definition**
| Method | POST |
| :----------- | :------------------------------------------------- |
| **Host** | [https://api.talview.com](https://api.talview.com) |
| Route | /api/rest/external/assessment/invite |
| Content type | application/json |
**Request payload definition: Standard**
| Attribute | Mandatory | Data Type | Description |
| :---------------------------- | :-------- | :--------- | :------------------------------------------------------------------------------------------------------------------------- |
| candidate\_email | yes | String | Candidate’s email address |
| candidate\_first\_name | no | String | Candidate's first name |
| candidate\_last\_name | no | String | Candidate's last name |
| candidate\_reference\_id | no | String | Candidate’s ID in the external system |
| workflow\_step\_id | yes | Number | Workflow\_step\_id in Talview System (maps to the exact step in the workflow where the candidate needs to be invited) |
| workflow\_step\_reference\_id | no | String | Workflow Step ID in the external system *(Note: Either workflow\_step\_id or step\_reference\_id is manadatory)* |
| callback\_url | no | String | URL of the external service to be used for sending the reports, scores, playback video, etc. |
| is\_notify | no | Boolean | Whether the candidate needs to be notified or not |
| valid\_till | no | TimeStampz | Assessment window duration in ISO 8601 format: yyyy-MM-dd'T'HH:mm:ss.SSSZ |
**Sample response payload:**
1. Success response: HTTP status code - 201
```json theme={null}
{
"workflow" : {
"id" : 12,
"external_id" : "12-1A",
"workflow_name": "Java Techincal"
},
"candidate": { "external_id": 2932, "email": "abc@xyz.com" },
"step" : {
"id": 29103,
"external_id": "2032-201",
"type": "ASSESSMENT",
"workflow_id": 3
},
"valid_till": "2025-10-03T17:00:00+00:00",
"attend_url": "https://cx.talview.com/..."
}
```
2. Error response: HTTP status code - 422
```json theme={null}
{
"errors": [{
"field": "valid_till",
"message": "valid till can not be in past"
}]
}
```
3. Error response: HTTP status code - 400
```json theme={null}
{
"errors": [{
"field": "callback_url",
"message": "Callback Url can not be blank"
}]
}
```
**Sample CURL request:**
```bash theme={null}
curl --request POST \\
--url https://api.talview.com/external/assessment/invite \\
--header 'Authorization: Bearer <:access_token:>' \\
--data '{
"valid_till": "2024-06-08T08:30:00.000Z",
"candidate_first_name": "candidate",
"candidate_last_name" : "name",
"candidate_email": "candidate@email.com",
"candidate_reference_id": "CAN_LAT_10045",
"workflow_step_id": 10394,
"workflow_step_reference_id": "AD-1",
"is_notify": true,
"callback_url" : "https://.com/scores"
}'
```
# Standard Schedule Integration Flow
Source: https://docs.talview.com/admin/configurations/integrations/workflow-integrations/workflow-api-endpoints/workflow-schedule
To schedule a interview in Talview Workflow Tools (WFT) application,please follow the below steps.
### Prerequisites
1. An workflow with Technical Round needs to be pre configured.
## Interview Schedule Technical Steps
### 1. Authentication
* Use this [guide](../Authentication) to generate an **`access_token`**.
* The token generated will go in `Authorization` header for all API calls.
### 2. Schedule API
Every invitation send to Talview System, must follow below the payload structure.
**Request header definition:**
| Method | POST |
| :----------- | :------------------------------------------------- |
| **Host** | [https://api.talview.com](https://api.talview.com) |
| Route | /api/rest/external/workflow/schedule |
| Content type | application/json |
**Request payload definition: Standard**
| Attribute | Mandatory | Data Type | Description |
| :---------------------------- | :-------- | :-------------- | :----------------------------------------------------------------------------------------------------------------------------------------- |
| organizer\_email | yes | String | Organizer of interview email address |
| interviewers | yes | Array of String | Array of emails of the interviewers |
| candidate\_email | yes | String | Candidate's email address |
| candidate\_reference\_id | yes | String | Candidate's ID in External System |
| timezone | no | String | The timezone to be used for the schedule |
| candidate\_name | no | String | Candidate's name (first + last ) name |
| start\_time | yes | timestampz | Start time of the interview. ISO 8601 format: yyyy-MM-dd'T'HH:mm:ss.SSSZ |
| status | yes | String | Status to manage schedule: Possible values: 1. SCHEDULE 2. CANCEL 3. UPDATE |
| callback\_url | yes | String | Url of External Service to be used for sending the reports,scores,playbacy video,etc.. |
| duration | yes | Number | Duration of interview in minutes Possible values: 30 \| 45 \| 60 \| 90 \| 120, default: 30 |
| meeting\_id | no | Number | Meeting\_id in Talview System (*Used when doing CANCEL/UPDATE actions)* |
| workflow\_step\_id | yes | String | Talview Workflow ID |
| workflow\_step\_reference\_id | no | String | WorkflowStep ID from external client system ( *Note : Need to send either workflow\_reference\_id or workflow\_step\_reference\_id )* |
**Sample response payload:**
1. Success response: HTTP status code - 201
```json theme={null}
{
"meeting_id": 1293,
"candidate": { "external_id": 2932, "email": "abc@xyz.com" },
"meeting_status" : "SCHEDULED"
}
```
2. Error response: HTTP status code - 422
```json theme={null}
{
"errors": [{
"field": "start_time",
"message": "Start time cannot be in the past"
}]
}
```
3. Error response: HTTP status code - 400
```json theme={null}
{
"errors": [{
"field": "start_time",
"message": "Start time cannot be blank"
}]
}
```
**Sample CURL request:**
```bash theme={null}
curl --request POST \
--url https://api.talview.com/api/rest/external/workflow/schedule \
--header 'Authorization: Bearer <:access_token:>' \
--data '{
"status": "SCHEDULE",
"meeting_id": null,
"workflow_step_id": "39121",
"start_time": "2024-06-08T08:30:00.000Z",
"duration": 30,
"timezone": "Asia/Kolkata",
"candidate_name": "candidate name",
"candidate_email": "candidate@email.com",
"candidate_reference_id": "CAN_LAT_10045",
"interviewers": ["inerviewer1@email.com", "inerviewer2@email.com"],
"organizer_email": "organizer@email.com",
"workflow_step_reference_id" : "LA-1-1",
"callback_url" : "https://.com/scores"
}'
```
# Why are my changes not being saved?
Source: https://docs.talview.com/admin/forms/diagnostics/why-are-my-changes-not-being-saved
If your edits are disappearing after leaving the Form Editor or fields are no longer visible when you reopen the form in Talview, it's usually a connection or session issue. The Form Editor auto-saves your changes as you work, so a save failure typically means something interrupted that process. In this article, you'll find the most common causes and how to resolve them.
### **🔎 Troubleshooting common issues**
| **What Might Be Wrong** | **How to Fix It** |
| :-------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------- |
| Your internet connection dropped while editing. | Check your connection. Once back online, refresh the page, queued changes should sync. |
| Your browser session timed out after being idle too long. | Log out and log back in, then reopen the form from the Forms list. |
| You closed the tab or navigated away before auto-save could complete. | Wait a few seconds after making changes before leaving the editor. |
| A temporary server error prevented the save. | Refresh the page and check if your changes are still on the canvas. If not, re-apply them and wait before navigating away. |
| Multiple users are editing the same form at the same time. | Ensure only one person edits a form at a time. Refresh the page to load the most recent version. |
**Additional Tips**
* Auto-save works in the background as you make changes, there's no manual save button.
* If you frequently experience save issues, try switching to a recommended browser such as Chrome, Edge, or Firefox.
* Clear your browser cache if the issue continues after trying the steps above.
* If the problem persists across sessions and browsers, contact your administrator for further assistance.
# Why are previously created forms missing from the list?
Source: https://docs.talview.com/admin/forms/diagnostics/why-are-previously-created-forms-missing-from-the-list
If forms you've previously created are not appearing in the Forms list on Talview's Admin platform, it doesn't necessarily mean they've been deleted. This usually happens when the list is being narrowed by an active search query, filter, or pagination setting. In this article, you'll find the most common causes and how to resolve them.
***
### 🔎 Troubleshooting common issues
| **What might be wrong** | **How to fix it** |
| :---------------------------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| A search query is still active in the search bar | Check the **Search** bar at the top right of the Forms list. If there's text in it, clear it to return to the full list. |
| Filters are applied and hiding some forms | Check whether a *filter tag* is showing below the header (for example, "Status Includes any Draft"). Click **Clear all** at the top right to remove all active filters. |
| You're on the wrong page | 1. Check the pagination controls at the bottom of the table. 2. You may be on page 2 or 3 while the form you're looking for is on a different page. 3. Navigate between pages or increase the **Rows per page** to display more forms at once. |
| The Rows per page setting is too low | 1. If Rows per page is set to 5 or 10, some forms may be hidden on later pages. 2. Click the **Rows per page** dropdown and select a higher number to see more forms on a single page. |
| Your account can only see forms you have permission to view | 1. Depending on your organisation's configuration, you may only see forms you created or forms within your permission scope. 2. Contact your organisation admin to confirm whether form visibility is restricted to your account. |
**Additional Tips**
Before assuming a form is missing, try clearing the search bar, removing all filters, and setting Rows per page to the highest option. This gives you the complete, unfiltered view of all forms in your organisation.
# Why can't I add or edit fields in the Form Editor?
Source: https://docs.talview.com/admin/forms/diagnostics/why-cant-i-add-or-edit-fields-in-the-form-editor
If fields aren't inserting, the “**/”** menu isn't appearing, or the Form Editor seems frozen while you're building a form in Talview, it's usually caused by a browser issue or a session-related problem. In this article, you'll find the most common causes and how to get the editor working again.
#### 🔎 Troubleshooting common issues
| **What Might Be Wrong** | **How to Fix It** |
| :-------------------------------------------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| The “**/”** command menu isn't appearing when you type on the canvas. | Click directly on the canvas to make sure it's in focus, then type “**/”**. If it still doesn't appear, refresh the page with `Ctrl + Shift + R` (Windows) or `Command + Shift + R` (Mac). |
| A field was selected from the block picker but didn't insert on the canvas. | Refresh the page and try again. Make sure you're clicking on an empty area of the canvas before selecting a field from the block picker. |
| The editor appears frozen and no clicks or edits are registering. | Your browser tab may have become unresponsive. Refresh the page, or close and reopen the tab. If the issue continues, close other heavy tabs or applications to free up memory. |
| Your changes aren't being saved, or fields revert after adding them. | This could be a network issue. Check your internet connection and refresh the page. Your previously auto-saved content should still be intact. |
| Your browser session has expired or timed out. | Log out and log back in, then reopen the form from the Forms list. |
| A browser extension is interfering with the editor. | Try opening the Form Editor in an incognito or private browsing window. If the editor works there, disable extensions one by one to identify the conflict. |
**Additional Tips**
* Chrome, Edge, and Firefox are the recommended browsers for the Form Editor. If you're using a different browser, try switching.
* Clear your browser cache if the editor continues to behave unexpectedly after trying the steps above.
* Your form content is auto saved, so refreshing or reopening the form won't cause you to lose your work.
* If the issue persists across browsers and devices, contact your administrator for further assistance.
# Why can't I copy the form link from the publish modal?
Source: https://docs.talview.com/admin/forms/diagnostics/why-cant-i-copy-the-form-link-from-the-publish-modal
If you published a form in Talview and the copy button next to the share link isn't working, it's usually a browser permission issue. In this article, you'll find the most common causes and how to resolve them.
#### 🔎 Troubleshooting common issues
| **What Might Be Wrong** | **How to Fix It** |
| :------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Your browser is blocking clipboard access for the platform. | When prompted, click **Allow** on the clipboard permission popup. If you dismissed it earlier, go to your browser's site settings and enable clipboard access for the platform. |
| You're using a browser that doesn't fully support the clipboard API. | Switch to a recommended browser such as Chrome, Edge, or Firefox and try again. |
| A browser extension is interfering with the copy action. | Try copying the link in an incognito or private browsing window. If it works there, disable extensions one by one to find the conflict. |
| The copy button was clicked but no confirmation appeared. | The link may have copied successfully without a visible toast. Try pasting (`Ctrl + V` or `Command + V`) to confirm. |
| As a fallback, you can copy the link manually. | Click inside the URL field in the **Share Link** section, select the full link using `Ctrl + A` (Windows) or `Command + A` (Mac), then copy it with `Ctrl + C` or `Command + C`. |
**Additional Tips**
* The shareable link is unique to each form and remains the same after publishing.
* For an alternative way to share the form, you can use the QR code from the same modal.
# Why can't the Admin see the forms section in the navigation bar?
Source: https://docs.talview.com/admin/forms/diagnostics/why-cant-the-admin-see-the-forms-section-in-the-navigation-bar
If you can't find the **Forms** entry in the side navigation on Talview's Admin platform, you won't be able to access the Form Builder to create or manage forms. This typically happens due to account access level or role configuration. In this article, you'll find the most common causes and how to resolve them.
***
### 🔎 Troubleshooting common issues
| **What might be wrong** | **How to fix it** |
| :------------------------------------------------------------------------ | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Your account doesn't have admin-level access | 1. The Form Builder is available to Tenant Admins and Platform Admins only. 2. Other roles such as Recruiter don't see the **Forms** entry. 3. Confirm your role with your organisation admin and request an upgrade to admin access if needed. |
| The side navigation is showing limited options based on your access level | 1. The side navigation displays different sections based on your access level. 2. If you see sections like Workflow list view instead of User Management and Forms, your account is configured as a Recruiter, not an Admin. 3. Contact your organisation admin to verify. |
| Your session has expired | 1. An expired session can sometimes cause navigation items to disappear. 2. Refresh the page or log out and log back in to restore a fresh session. |
| Browser cache is showing an outdated version of the navigation | 1. Your browser may be loading a cached version of the page. 2. Press `Ctrl + Shift + R` (Windows) or `Command + Shift + R` (Mac) to do a hard reload. |
**Additional Tips**
If you've confirmed your account has admin access and you still can't see **Forms** in the navigation, contact your organisation admin to check whether the Form Builder feature is enabled for your tenant.
# Why did the form fail to publish?
Source: https://docs.talview.com/admin/forms/diagnostics/why-did-the-form-fail-to-publish
If you clicked **Publish form** in the Talview Form Editor and the form didn't go live, it could be due to a validation issue, a network error, or an incomplete form setup. In this article, you'll find the most common reasons for a failed publish and how to resolve them.
#### 🔎 Troubleshooting common issues
| **What Might Be Wrong** | **How to Fix It** |
| :------------------------------------------------------------------------------------------------------------------ | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| The form canvas is empty, or all fields were removed before publishing. | Add at least one field to the canvas using the “**/”** command or the block picker. The form can't be published without content. |
| One or more fields have validation errors (for example, a required label is missing, or a dropdown has no options). | Review each field on the canvas and check for any error indicators or highlighted fields. Fix the flagged issues and try publishing again. |
| A network error interrupted the publish action. | Check your internet connection and try again. Refresh the page with `Ctrl + Shift + R` (Windows) or `Command + Shift + R` (Mac), then click **Publish form** again. |
| The platform encountered a temporary server error. | Wait a few minutes and try publishing again. If the error persists, try logging out and logging back in before retrying. |
| Your browser session has expired or timed out. | Refresh the page or log out and log back in. Reopen the form from the Forms list and try publishing again. Your changes should still be saved due to auto-save. |
**Additional Tips**
* If you see a specific error message when publishing, note it down, it can help identify the root cause faster.
* Your form content is auto saved as you work, so you won't lose your changes even if the publish action fails.
* Try using a different browser such as Chrome, Edge, or Firefox if the issue persists.
* If none of the above steps resolve the issue, contact your administrator for further assistance.
# Why did the form not get created after clicking "+ New Form"?
Source: https://docs.talview.com/admin/forms/diagnostics/why-did-the-form-not-get-created-after-clicking-new-form
If you clicked **+ New Form**, entered a form name, selected a form type, and clicked **Create Form** but the form wasn't created on Talview's Admin platform, you won't be able to start building. This can happen due to network issues, missing required fields, or a temporary error.
In this article, you'll find the most common causes and how to resolve them.
***
### 🔎 Troubleshooting common issues
| **What might be wrong** | **How to fix it** |
| :----------------------------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| The form name field was left empty | The **Form name** field is required. Go back and enter a name for your form before clicking **Create Form**. |
| Your internet connection dropped during form creation | Check your internet connection. If it's unstable, switch to a stable network, click **Cancel**, and start the form creation process again from `+ New Form`. |
| A temporary server error prevented the form from being saved | Wait a few minutes and try again. Click **Cancel** to return to the Forms list, then click `+ New Form` and repeat the steps. |
| Your session expired while you were on the creation screen | If you were on the creation screen for a while without taking action, your session may have expired. Log out, log back in, and try creating the form again. |
| Your browser is loading a cached version of the page | Press `Ctrl + Shift + R (Windows)` or` Command + Shift + R (Mac`) to do a hard reload, then try creating the form again. |
**Additional Tips**
* After clicking **Create Form**, wait for the Form Editor to fully load before taking any other action. Navigating away too quickly may interrupt the creation process.
* If the issue persists after trying all the steps above, contact your organisation admin.
# Why is my Form title not saving?
Source: https://docs.talview.com/admin/forms/diagnostics/why-is-my-form-title-not-saving
If you set a title for your form in the Talview Form Editor but it reverts to the default placeholder when you reopen the form, it usually means the title didn't save properly. In this article, you'll find the most common causes and how to resolve them.
#### 🔎 Troubleshooting common issues
| **What Might Be Wrong** | **How to Fix It** |
| :-------------------------------------------------------------------- | :--------------------------------------------------------------------------------------- |
| You navigated away or closed the tab before auto-save could complete. | After entering or editing the title, wait a few seconds before leaving the editor. |
| Your internet connection dropped while the title was being saved. | Check your connection, refresh the page, and re-enter the title. |
| The title exceeds the allowed character limit. | Shorten the title and check if it saves successfully. |
| Your browser session expired while the editor was open. | Log out and log back in, reopen the form, and set the title again. |
| A temporary server error prevented the save. | Refresh the page and re-enter the title. If the issue persists, try a different browser. |
**Additional Tips**
* The form title auto-saves in the background, similar to other changes in the editor. There is no manual save button.
* If you leave the title blank, the form retains the default placeholder text.
* Try using a recommended browser such as Chrome, Edge, or Firefox if the issue continues.
* If the problem persists across sessions, contact your administrator for further assistance.
# Why is the Form Editor not loading after I created a form?
Source: https://docs.talview.com/admin/forms/diagnostics/why-is-the-form-editor-not-loading-after-i-created-a-form
If you successfully created a form but the Form Editor shows a blank canvas, an unresponsive screen, or doesn't load at all on Talview's Admin platform, you won't be able to start adding fields to your form. This can happen due to browser issues, network interruptions, or a temporary loading error.
In this article, you'll find the most common causes and how to resolve them.
***
### 🔎 Troubleshooting common issues
| **What might be wrong** | **How to fix it** |
| :--------------------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| The editor didn't fully load after form creation | Press `Ctrl + Shift + R (Windows)` or `Command + Shift + R (Mac)` to do a hard reload. This forces the browser to fetch the latest version of the page. |
| Your internet connection dropped during the transition from creation to the editor | Check your internet connection. If it's unstable, switch to a stable network, go back to the Forms list, find your newly created form, and click on it to reopen the editor. |
| Your browser is outdated or not compatible | The Form Editor works best on the latest versions of **Chrome**, **Edge**, or **Firefox**. Update your browser or switch to a supported one. |
| Browser cache or stored data is interfering with the editor | Clear your browser cache and cookies, then log back in and open the form from the Forms list. |
| Browser extensions are blocking the editor from loading | 1. Try opening the Admin platform in an incognito or private browsing window. If the editor loads there, a browser extension may be interfering. 2. Disable extensions one by one to identify the cause. |
| Your session expired during the creation process | 1. Log out, log back in, and open the form from the Forms list. 2. The form should have been saved even if the editor didn't load. |
**Additional Tips**
* Even if the editor didn't load after creation, the form is usually saved. Go back to the Forms list and check whether the form appears in the table. If it does, click on it to open the editor.
* If the editor still doesn't load after trying all the steps above, contact your organisation admin or raise a support request.
# Why is the form preview not displaying correctly?
Source: https://docs.talview.com/admin/forms/diagnostics/why-is-the-form-preview-not-displaying-correctly
If the form preview on Talview's Admin platform shows a blank page, a broken layout, or fields that aren't rendering properly, you won't be able to verify how the form looks before publishing. This can happen due to browser issues, cached data, or differences between the web and mobile preview.
In this article, you'll find the common causes and steps to get your form preview displaying correctly.
***
### 🔎 Troubleshooting common issues
| **What might be wrong** | **How to fix it** |
| :------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Your browser is loading a cached version of the preview | Press `Ctrl + Shift + R (Windows)` or `Command + Shift + R (Mac)` to do a hard reload, then click **Preview** again. |
| Your browser is outdated or not compatible | The preview works best on the latest versions of **Chrome**, **Edge**, or **Firefox**. Update your browser or switch to a supported one. |
| The form has unsaved changes | Go back to the editor by clicking **Back to editor**, wait for the **✓ Saved** indicator to appear in the header, and then click **Preview** again. |
| The layout looks different in mobile view compared to web view | 1. This is expected. The mobile view simulates a narrower screen, so fields stack vertically and the form container is smaller. 2. Toggle the **Mobile view** tab to return to the web view and compare. |
| Browser extensions are interfering with the preview | 1. Open the Admin platform in an incognito or private browsing window and try previewing again. 2. If it works there, a browser extension may be the cause. Disable extensions one by one to identify it. |
| A temporary loading error caused the preview to break | Click **Back to editor** to return to the Form Editor, then click **Preview** again to reload the preview. |
**Additional Tips**
* Always check both the web view and mobile view before publishing. Some layout issues only appear in one view and not the other.
* If the preview continues to display incorrectly after trying all the steps above, contact your organisation admin or raise a support request.
# Why is the Forms list not loading?
Source: https://docs.talview.com/admin/forms/diagnostics/why-is-the-forms-list-not-loading
If the Forms list page shows a blank screen, a spinner that doesn't stop, or an error message after clicking **Forms** in the side navigation on Talview's Admin platform, you won't be able to view or manage your forms.
In this article, you'll find the most common causes and how to resolve them.
***
### 🔎 Troubleshooting common issues
| **What might be wrong** | **How to fix it** |
| :----------------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Your internet connection is unstable or disconnected | 1. Check your internet connection. 2. Try loading another page to confirm. If the connection is weak, switch to a stable network and try again. |
| Your session has expired | Log out and log back in to the Admin platform. This refreshes your session and reloads the page. |
| Your browser is loading a cached version of the page | Press `Ctrl + Shift + R (Windows)` or `Command + Shift + R (Mac)` to do a hard reload. This clears the cached version and fetches the latest page. |
| Your browser is not compatible or is outdated | 1. The Admin platform works best on the latest versions of **Chrome**, **Edge**, or **Firefox**. 2. Update your browser or switch to a supported one. |
| Your account doesn't have the correct access level | 1. The Forms list is available to Tenant Admins and Platform Admins only. 2. If your account doesn't have admin access, the page may not load. 3. Confirm your access level with your organisation admin. |
| A temporary server issue is preventing the page from loading | 1. Wait a few minutes and try again. 2. If the issue persists, contact your organisation admin or raise a support request. |
**Additional Tips**
If you see a specific error message on the page, note it down before trying the fixes above. It can help your admin or support team identify the issue faster.
# Why is the Preview button disabled?
Source: https://docs.talview.com/admin/forms/diagnostics/why-is-the-preview-button-disabled
If the **Preview** button at the top right of the Form Editor appears disabled and you can't click it on Talview's Admin platform, this is usually because the form doesn't have any content yet. In this article, you'll learn why this happens and how to enable it.
***
### 🔎 Troubleshooting common issues
| What might be wrong | **How to fix it** |
| ------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| The form canvas is empty | 1. The Preview button is intentionally disabled when the form has no content. 2. Add at least one field to the canvas (type / to see available commands), and the button will become active. |
| You added content but the button is still disabled | 1. The change may not have been saved yet. 2. Click somewhere else on the canvas and wait for the **✓ Saved** indicator to appear in the header. 3. Then try clicking **Preview** again. |
| A temporary loading issue is preventing the button from activating | Press `Ctrl + Shift + R `(Windows) or `Command + Shift + R `(Mac) to do a hard reload. Reopen the form from the Forms list and check if the button is now active. |
**Additional Tips**
The **Preview** button only becomes active once the form has at least one field or block of content on the canvas. This is by design to prevent previewing an empty form.
# Why is the Publish button disabled?
Source: https://docs.talview.com/admin/forms/diagnostics/why-is-the-publish-button-disabled
If the **Publish form** button appears grayed out or unclickable while you're working in the Talview Form Editor, it can be confusing, especially when you're ready to make your form live. This usually happens because certain conditions haven't been met yet. In this article, you'll find the most common reasons why this occurs and how to resolve it so you can publish your form successfully.
### 🔎 Troubleshooting common issues
| **What Might Be Wrong** | **How to Fix It** |
| :---------------------------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| The form canvas is empty with no fields or blocks added. | Add at least one field using the “ **/”** command or the block picker on the left panel. The **Publish form** button activates once a field is present. |
| All previously added fields were deleted from the canvas. | Re-add at least one field to the canvas. The button re-enables automatically. |
| The form was newly created, and the canvas is still blank. | This is expected. Start adding fields and the button will activate with the first field added. |
| The page hasn't fully loaded or there's a temporary glitch. | Refresh the page with `Ctrl + Shift + R` (Windows) or `Command + Shift + R` (Mac). If the button is still disabled, close and reopen the form from the Forms list. |
**Additional Tips**
* The **Publish form** button is intentionally disabled for empty forms to prevent accidentally publishing a blank form to respondents.
* You don't need to save manually after adding fields, your changes are auto-saved as you work.
* If the button remains disabled even after adding fields and refreshing the page, try using a different browser such as Chrome, Edge, or Firefox.
# How to create a form using a template
Source: https://docs.talview.com/admin/forms/how-tos/how-to-create-a-form-using-a-template
Instead of building a form from scratch, you can use a pre-built template in Talview to get started quickly. Templates come with fields already set up based on the form type you select. In this article, you will learn how to choose a template, insert it, and customise the form to your needs.
#### Step-by-step guide
1. **Open a new form**
Create a new form to open the Form Editor. On the canvas, you will see two options: **Start from scratch** and **Use a template**.
2. **Click Use a template**
Click the icon next to **Use a template**. A **Types Of Forms** modal opens, listing all available form types on the left side.
3. **Choose a form type**
Select a form type from the list (for example, **Pre-Registration**). When you select a type, a description and a preview of the template appear on the right side of the modal. This helps you understand what fields the template includes before inserting it.
4. **Insert the template**
Click **Insert** at the bottom right of the modal. The template is applied to your form, and the canvas now shows the pre-built fields for the selected type.
> For example, a Pre-Registration template includes fields like Full Name, Email Address, Phone Number, and Department.
5. **Customise the form**
You can now add, remove, or rearrange fields on the canvas to match your requirements. Use the “**/”** command or the block picker to add new fields.
6. **Publish or save as a draft**
Once you're done, click **Publish form** at the top right to make the form live. If you want to keep it as a draft and continue working on it later, click the back arrow next to the form name to return to the Forms list. Your changes are auto-saved.
**Additional Tips**
* You can rework on a published form at any time. Find the form in the Forms list, open it, make your changes, and click **Publish form** again. The **Last updated by** column in the Forms list reflects who last made changes.
* Each form type template comes with a default set of fields tailored to that use case.
* If you want to switch to a different template after adding one, the existing fields on the canvas may be replaced. Make sure you've selected the correct type before clicking **Insert**.
# How to create a new form
Source: https://docs.talview.com/admin/forms/how-tos/how-to-create-a-new-form
The Form Builder lets you create new forms directly from the Forms list. In this article, you'll learn how to start a new form by naming it, selecting a form type, and landing in the Form Editor.
### Before you begin
* You need to be on the Forms list page. If you're not sure how to get there, see *How to navigate to the Forms section*.
***
### Step-by-step guide
**1. Click + New Form**
At the top right of the Forms list, click the **+ New Form** button. A new page opens with a form card where you set up your form.
**2. Enter a form name**
In the **Form name** field, type a name for your form (for example, "Candidate Onboarding Form"). Choose something descriptive so it's easy to identify in the Forms list later.
**3. Select a form type**
Under **Form type**, select one of the two options:
* **Candidate registration form**: for collecting information from candidates.
* **Panel evaluation form**: for capturing structured feedback from evaluators and interviewers.
> For help choosing, refer to *What is the difference between a Registration form and an Evaluation form?*
**4. Click Create Form**
* Once you've entered a name and selected a form type, click the **Create Form** button.
* If you change your mind, click **Cancel** to return to the Forms list without creating a form.
**5. Start building in the Form Editor**
The Form Editor opens with a blank canvas. Your form name appears in the header at the top left. The canvas shows a placeholder that says "Enter text or type '/' for commands", which is where you start adding fields and content to your form.
> From here, you can start building your form. For next steps, refer to *How to add fields to a form*.
**Additional Tips**
The **Publish Form** button is disabled when the form is empty. You need to add at least one field before you can publish.
# How to edit a form after it has been created
Source: https://docs.talview.com/admin/forms/how-tos/how-to-edit-a-form-after-it-has-been-created
After creating a form, you can open it at any time to make changes to its fields or settings. In this article, you'll learn how to open an existing form from the Forms list, make edits in the Form Editor, and confirm your changes are saved.
***
### Step-by-step guide
**1. Find the form you want to edit**
In the Forms list, locate the form you want to edit. You can scroll through the table, use the **Search** bar, or apply **Filters** to find it.
**2. Click on the form**
Click on the form's name in the table. The Form Editor opens with the form's existing content on the canvas.
**3. Make your changes**
Add, edit, or remove fields as needed. You can also update the form's appearance or settings. As you work, the save indicator in the header shows **"Saving..."** and then **"✓ Saved"** to confirm your changes are saved automatically.
**4. Publish or continue editing**
If your form is still in **Draft** and you're ready to make it live, click the **Publish Form** button at the top right. You'll be automatically taken back to the *Forms list* and the form's status will change to **Published**.
> For more details, refer to *How to publish a form*.
If you're not ready to publish yet, you can continue editing or return to the Forms list. Your changes are already saved.
**5. Return to the Forms list**
When you're done, click the **←** (back arrow) at the top left corner next to the form title. You're taken back to the Forms list, and the form's **Updated On** and **Updated By** columns reflect your latest changes.
**Additional Tips**
* You can edit both Draft and Published forms. If you edit a Published form, your changes are saved and reflected immediately to respondents.
* You don't need to manually save. The editor auto-saves as you work. Wait for the **✓ Saved** indicator before leaving the editor to make sure your latest changes are captured.
# How to filter the Forms list
Source: https://docs.talview.com/admin/forms/how-tos/how-to-filter-the-forms-list
The Forms list provides filters that let you narrow down the table by status or form type. In this article, you'll learn how to open the filter panel, apply filters, and clear them.
### Step-by-step guide
**1. Open the filter panel**
At the top right of the Forms list, click the **Filters** icon (next to the search bar). A dropdown panel opens with two filter categories: **Status** and **Type**.
**2. Filter by Status**
Click **Status** to expand the options. You'll see checkboxes for:
* **Published**: shows only forms that are live and accessible to respondents.
* **Draft**: shows only forms that are still being worked on.
* **Archived**: shows only forms that have been archived and are no longer active.
Select one or both checkboxes. The list updates to show only the forms that match your selection. A filter tag appears below the header showing the applied filter (for example, "Status Includes any Published, Draft").
**3. Filter by Type**
Click **Type** to expand the options. You'll see a checkbox for each available form type. Select one or more checkboxes to narrow the list.
> For a full list and description of each form type, refer *Understanding form types*.
**4. Clear filters**
When filters are active, you can clear them in two ways:
* Click the “**X”** on a filter tag to remove that specific filter.
* Click **Clear all** at the top right to remove all applied filters at once.
**Additional Tips**
You can use filters and the search bar together. For example, filter by **Published** under Status and then search for a specific form name to narrow the results further.
# How to navigate to the Forms section
Source: https://docs.talview.com/admin/forms/how-tos/how-to-navigate-to-the-forms-section
The Forms section is where you view, create, and manage all your forms. In this article, you'll learn how to reach the Forms section from the side navigation and what to expect when the page loads.
### Before you begin
* You need an admin account (Tenant Admin or Platform Admin) with access to the Form Builder.
* If you don't see **Forms** in the side navigation, check with your organisation admin to confirm your access level.
***
### Step-by-step guide
**1. Log in to the Admin platform**
Log in to the Admin platform with your credentials.
**2. Click Forms in the side navigation**
In the left side navigation panel, click **Forms**. The Forms list page loads, showing all the forms that have been created in your organisation.
**3. What the page shows on load**
The Forms list page displays all the forms in your organisation in a table. The table includes the following columns: *Form Name, Type, Status, Responses, Updated On,* and *Updated By.*
***
### Key elements on the Forms list page
Along with the table, the Forms list page includes:
* **Search bar** (top right): lets you find a specific form by name or form ID.
* **Filters icon** (top right, next to Search): lets you narrow the list by Status or Type.
* **+ New Form button** (top right): lets you create a new form.
* **Pagination controls** (bottom): lets you move between pages and set the number of rows displayed per page.
**Note:** To understand what each column means and how to interpret the values, see *How to read the Forms list table*.
# How to preview a form in web and mobile view
Source: https://docs.talview.com/admin/forms/how-tos/how-to-preview-a-form-in-web-and-mobile-view
Before publishing a form, you can preview it to see how it will appear to respondents on a desktop browser and on a mobile device. The preview opens in web view by default and lets you switch to mobile view using tabs. In this article, you'll learn how to open the preview, switch between web and mobile views, and what to check in each.
***
### Step-by-step guide
**1. Click Preview**
Inside the Form Editor, click **Preview** at the top right. The **Preview Web** page opens, showing your form in web view by default.
**2. Review the web view**
The web view displays your form as it will appear to respondents on a desktop browser. Check that:
* All fields are visible and in the correct order.
* Field labels and placeholder text are accurate.
* Required fields are marked with an asterisk (\*).
* The overall layout and spacing look as expected.
**3. Switch to mobile view**
Click the **Mobile View** tab at the top center of the page. The header changes to **Preview Mobile** and the form is displayed inside a narrower container that simulates a mobile screen. Check that:
* All fields stack correctly and are readable on a narrower screen.
* Field widths adjust properly.
* Buttons are large enough to tap.
* The form does not require horizontal scrolling.
**4. Switch back to web view**
Click the **Web View** tab to return to the desktop preview.
**5. Return to the editor**
Click the back arrow next to **Preview Web** or **Preview Mobile** to return to the Form Editor.
**Additional Tips**
* You can preview your form at any point while building it, not just when it's finished. Previewing periodically as you add fields helps catch layout issues early.
* Many respondents will fill in your form on a mobile device. Always check the mobile view before publishing.
* The **Publish form** button is also accessible from the preview page, so you can publish directly after reviewing.
# How to publish a form
Source: https://docs.talview.com/admin/forms/how-tos/how-to-publish-a-form
When you create a form, it starts with a **Draft** status. It stays in Draft regardless of what changes you make in the Form Editor, until you explicitly publish it. Publishing makes the form live and accessible to respondents. In this article, you'll learn when the Publish button becomes active and how to publish a form.
### Before you begin
* You need to have a form open in the Form Editor with at least one field added. The **Publish Form** button is disabled when the canvas is empty.
***
### Step-by-step guide
You can publish a form in two ways: right after creating it, or by opening a Draft form from the Forms list at a later time. The publish step is the same in both cases.
#### **A. Publishing a form right after creating it**
**1. Create a new form**
Click **+ New Form** from the Forms list, enter a form name, select a form type, and click **Create Form**. The Form Editor opens with a blank canvas.
**2. Build your form**
Add the fields you need and check that the form looks as expected. Preview the form in both web and mobile view to verify the layout.
**3. Click Publish Form**
At the top right of the Form Editor, click the **Publish Form** button. A loading spinner appears on the button while the form is being published.
**4. Confirm the form is published**
Once publishing is complete, you're automatically taken back to the Forms list. The form's status in the **Status** column now shows **Published** in green.
#### **B. Publishing a Draft form later**
**1. Open the form from the Forms list**
Locate the Draft form you want to publish and click on it. The Form Editor opens with the form’s existing content.
Check that all the fields you need are added and the form looks as expected. Make any changes if needed. Your edits are auto-saved as you work.
**3. Click Publish Form**
At the top right of the Form Editor, click the **Publish Form** button. A loading spinner appears while the form is being published.
**4. Confirm the form is published**
You're automatically taken back to the Forms list. The form's status now shows **Published** in green.
**Additional Tips**
Publishing a form makes it immediately accessible to respondents. Make sure all fields and content are final before you publish.
# How to read the Forms list table
Source: https://docs.talview.com/admin/forms/how-tos/how-to-read-the-forms-list-table
The Forms list table gives you an overview of all the forms in your organisation. Each row represents a form, and the columns show key details about it at a glance. In this article, you'll learn what each column in the table means, how to interpret the values shown, and how the table is organised.
***
### What does each column show
**Form Name**
Displays the name of the form along with its form ID. The form name is what you set when you create the form, and the ID is assigned automatically. The form ID is unique and doesn't change, so you can use it to quickly identify a specific form even if multiple forms have similar names.
**Type**
Shows the form type, based on the type selected when the form was created (for example, Evaluation Form or Survey). For a full list and description of each form type.
**Status**
Shows the current state of the form:
* **Draft**: the form is still being worked on and hasn't been published yet. Forms in Draft are not accessible to respondents.
* **Published**: the form is live and accessible to respondents through its shared link or QR code.
* **Archived**: the form has been published before but is no longer needed and has been archived. Archived forms are no longer accessible to respondents.
**Responses**
The total number of responses that have been submitted for the form. A form with 0 responses either hasn't received any submissions yet or is still in Draft and hasn't been shared with respondents.
**Updated On**
The date when the form was last modified (for example, Wed, Jun 10, 2026). This helps you identify which forms have been recently worked on and which haven't been touched in a while.
**Updated By**
The name and email address of the user who last made changes to the form. This is useful when multiple admins are working on forms and you need to know who last edited a particular form.
***
### How the table is organised
The table displays a set number of rows per page. You can see the current page number, total pages, and the rows per page setting at the bottom of the table. Use the pagination controls to move between pages if your organisation has more forms than a single page can display.
Each row also has a menu on the right side that gives you quick access to actions for that form. The actions available from this menu are covered in their respective articles.
***
# How to search for a form
Source: https://docs.talview.com/admin/forms/how-tos/how-to-search-for-a-form
When your Forms list grows, you can use the search bar to quickly find a specific form instead of scrolling through the table. In this article, you'll learn how to search for a form by its name or form ID.
### Before you begin
* You need to be on the Forms list page. If you're not sure how to get there, see [*How to navigate to the Forms*](https://docs.talview.com/admin/forms/how-tos/how-to-navigate-to-the-forms-section) section.
***
### Step-by-step guide
**1. Click the Search bar**
At the top right of the Forms list, click the **Search** bar.
**2. Type your search term**
Enter the form name or form ID (for example, "Registration Form" or "FORM-677"). The list narrows down in real-time as you type, showing only the forms that match your search term.
**3. View the results**
The table updates to display only the matching forms. If no forms match your search term, the page displays a **"No forms yet"** message.
> **Note**: To clear the search and return to the full list, remove the text from the search bar.
**Additional Tips**
You can also find a form by scrolling through the *Forms list* and using the pagination controls at the bottom of the table.
# How to use pagination in the Forms list
Source: https://docs.talview.com/admin/forms/how-tos/how-to-use-pagination-in-the-forms-list
When your Forms list has more forms than a single page can display, the pagination controls at the bottom of the table let you move between pages and adjust how many forms are shown per page. In this article, you'll learn how to use the pagination controls to navigate the Forms list.
***
### Step-by-step guide
**1. Navigate between pages**
* At the bottom of the Forms list, you'll see the pagination controls. These show the current page number and the total number of pages (for example, Page 1 - 3).
* Use the left (**\<**) and right (**>**) arrows to move to the previous or next page.
**2. Go to a specific page**
Click the page number field, type the page number you want to go to, and press Enter. The table updates to display the forms on that page.
**3. Change rows per page**
* Click the **Rows per page** dropdown at the bottom right of the table.
* Select from the available options: **5**, **10**, **15**, **25**, or the total number of forms in your list.
* The table adjusts to display the selected number of rows per page, and the total number of pages updates accordingly.
***
**Additional Tips**
If you need to scan all your forms at once, select the highest option in the **Rows per page** dropdown to display everything on a single page.
# How to view who created or last updated a Form
Source: https://docs.talview.com/admin/forms/how-tos/how-to-view-who-created-or-last-updated-a-form
The Forms list table includes details about who created each form and who last made changes to it. In this article, you'll learn where to find this information and how to read it.
#### Step-by-step guide
**1. Open the Forms list**
Open the **Forms** section. The Forms list table loads with all available forms.
**2. Locate the Created by column**
The **Created by** column shows the name and profile picture of the user who originally created the form, along with the date it was created (for example, 23 Dec 2025).
**3. Locate the Last updated by column**
The **Last updated by** column shows the name and profile picture of the user who most recently made changes to the form, along with the date of that update (for example, 10 Mar 2026).
> **Note**: If no one has edited the form since it was created, this column shows the same user and date as **Created by**.
**Additional Tips**
* If a user doesn't have a profile picture, a colored initial avatar is shown instead (for example, "MC" for Michael Chen).
* These columns are helpful when multiple admins work on forms and you need to identify who last touched a specific form.
# Understanding Form Status Indicators
Source: https://docs.talview.com/admin/forms/how-tos/understanding-form-status-indicators
Every form in the Forms list has a status that tells you where it is in its lifecycle. In this article, you'll learn what each status means, how to identify them in the list, and how a form's status affects its availability to respondents.
***
### What are the form statuses?
**Draft**
A form in Draft status is still being worked on. It hasn't been published, so it's not accessible to respondents. You can continue editing the form, adding fields, and customising its appearance.
Use Draft when you're still building the form or want to make changes before making it available.
**Published**
A form in Published status is live and accessible to respondents through its shared link or QR code. Published is shown in green text in the Status column. Once a form is published, responses start getting collected as respondents fill it in.
Use Published when the form is ready and you want respondents to start submitting their information or feedback.
**Archived**
A form in Archived status has been taken out of active use. Archived forms are no longer accessible to respondents, but their responses are still preserved. Archiving a form doesn't delete it or its data.
Use Archived when you no longer need a form to be active but want to keep it and its responses for reference.
***
### How does status affect form availability?
| Status | Visible to respondents | Accepts responses | Editable by admin |
| :------------ | :--------------------- | :---------------- | :---------------- |
| **Draft** | No | No | Yes |
| **Published** | Yes | Yes | Yes |
| **Archived** | No | No | Yes |
***
# Understanding Form types
Source: https://docs.talview.com/admin/forms/how-tos/understanding-form-types
When you create a form in the Form Builder, you select a form type that determines the purpose and behaviour of the form. The Form Builder supports nine form types; each designed for a different stage of your hiring or organisational workflow.
In this article, you'll learn what each form type is used for and how to choose the right one.
***
### Available Form types:
* **Pre-Registration**: capture candidate interest and basic details before the official registration process opens.
* **Event Registration**: collect attendee information and confirm participation for an upcoming event or session.
* **Candidate Application**: gather candidate profile, background, and job-application details for a specific role.
* **Evaluation Form**: rate and record structured feedback on a candidate's performance against defined criteria.
* **Assessment Form**: capture scores and observations from a skills-based or knowledge-based assessment.
* **Post-Assessment Feedback**: collect candidate or evaluator feedback on the assessment experience after completion.
* **Survey**: gather general opinions, ratings, or insights from a target audience on a specific topic.
* **Enterprise Workflow Form**: configure multi-step forms to support internal enterprise processes and approvals.
* **Custom**: build a form from scratch with fully customisable fields to suit any unique requirement.
***
### When to use each form type -
| Stage | Form types |
| :------------------------------------ | :---------------------------------------------------------- |
| **Before an assessment or interview** | Pre-Registration, Event Registration, Candidate Application |
| **During or after an assessment** | Evaluation Form, Assessment Form |
| **After the assessment is complete** | Post-Assessment Feedback, Survey |
| **Internal or custom workflows** | Enterprise Workflow Form, Custom |
You select the form type when you create a form. Choose the type that matches the stage of your workflow.
**Additional Tips**
If none of the predefined types fit your needs, select **Custom** to build a form from scratch with fully customisable fields.
# Understanding the difference between Registration and Evaluation forms
Source: https://docs.talview.com/admin/forms/how-tos/understanding-the-difference-between-registration-and-evaluation-forms
When you create a form in the Form Builder, you choose one of two form types: Registration or Evaluation. Each type is designed for a different audience and purpose. In this article, you'll learn what each form type is used for, how they differ, and how to choose the right one.
***
### What is a Registration form?
A Registration form is designed to be filled in by candidates. Use it when you need to collect information such as name, contact details, qualifications, documents, or any other details before an assessment or event. When a candidate opens a published Registration form, they see the form fields along with a submit button to send their responses.
### What is an Evaluation form?
An Evaluation form is designed to be filled in by evaluators and interviewers. Use it when you need them to score candidates and record structured feedback during or after an interview. Unlike Registration forms, Evaluation forms don't display a submit button to the respondent since it is there in the parent platform.
### How do they differ?
| Comparison | Registration form | Evaluation form |
| :---------------- | :----------------------------------------------------------------- | :----------------------------------------------------- |
| **Filled in by** | Candidates | Evaluators and interviewers |
| **Purpose** | Collect candidate information before an assessment or event | Capture structured feedback and scoring on a candidate |
| **Submit button** | Displayed on the form | Not displayed |
| **Typical use** | Drive registration, pre-assessment details, candidate applications | Interview feedback, assessment scoring |
### How to choose the right form type?
Ask yourself who will be filling in the form:
* If it's **candidates** submitting their own information, choose **Registration**.
* If it's **evaluators or interviewers** recording feedback on a candidate, choose **Evaluation**.
You select the form type when you first create a form. This choice can't be changed later, so it's worth deciding before you start building.
# What is a Form Builder and who can access it
Source: https://docs.talview.com/admin/forms/how-tos/what-is-a-form-builder-and-who-can-access-it
The Form Builder lets you create forms that collect information from candidates or capture structured feedback from evaluators during your hiring process. In this article, you'll learn what the Form Builder is, what types of forms you can create, where it fits in your workflow, and who can access it.
***
### What is a Form Builder?
The Form Builder is where you create and manage forms for your hiring workflows. You build forms by adding fields onto a canvas, customise the appearance to match your organisation's branding, and publish them when they're ready. Published forms can be shared directly with candidates or evaluators or attached to a hiring workflow so they appear as a step in the process.
### What types of forms can you create?
The Form Builder supports two form types:
* **Candidate registration form**: designed for candidates. Use it when you need to collect information such as name, contact details, qualifications, or documents before an assessment or event.
* **Panel evaluation form**: designed for evaluators and interviewers. Use it when you need them to score candidates and record structured feedback during or after an interview.
You choose the form type when you create a form. This choice determines how the form behaves once it's published. For a detailed comparison, see *What is the difference between a Registration form and an Evaluation form?*
### Where does the Form Builder fit in your workflow?
A typical flow looks like this: you create a form, add the fields you need, preview it to check how it looks on web and mobile, and publish it. Once published, you either share the form's link or QR code directly, or attach it to a hiring workflow so candidates or evaluators reach it as a step in the process. As responses come in, you can review them from the form's response list.
### Who can access the Form Builder?
The Form Builder is available to Tenant Admins and Platform Admins. When you log in to the application, the side navigation shows different sections based on your access level. If your account has admin access, you'll see **Forms** in the side navigation, which is where you access the Form Builder.
Recruiters and other roles don't see the **Forms** entry, so form creation and response management are limited to admins. If you're an admin and don't see **Forms** in the side navigation, check with your organisation admin to confirm your account has the correct access level.
# Why can't I log in with my password?
Source: https://docs.talview.com/admin/login-and-access/diagnostics/Why-cant-I-log-in-with-my-password
Logging in to Talview with your password may fail for a number of reasons, such as an unrecognized email address, an incorrect password, or a browser issue. This can prevent you from accessing your account and getting started. In this article, you will find the most common causes and fixes to get back in quickly.
***
### 🔎 Troubleshooting common issues
| **What Might Be Wrong** | **How to Fix It** |
| :---------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| You're not on the **Login** tab | Make sure the **Login** tab is selected before entering your email address. |
| You're entering the wrong email address | Check for typos or extra spaces and re-enter your registered email address. |
| Your verification code has expired | Verification codes are time sensitive. Return to the login page and request a new one. |
| You didn't receive the verification code | Check your spam or junk folder. If it's not there, wait for the resend timer to expire and click **Resend code**. |
| You're selecting the wrong account | If multiple accounts are linked to your email, make sure you're selecting the right one on the **Pick an account** screen. |
| You're entering the wrong password | Passwords are case-sensitive, re-enter yours carefully. Check that *Caps Lock* isn't on before retyping. If you've forgotten it, click **Forgot password?** to [reset your password.](https://docs.talview.com/admin/login-and-access/how-tos/how-to-reset-your-password) |
| Your account is locked after multiple failed attempts | Contact your administrator to regain access. |
| Your browser is causing issues | Clear your browser cache and cookies. Try logging in on a different browser. |
**Additional tips**
Use **Chrome**, **Edge**, or **Firefox** for the best login experience.
* If none of the steps above resolve your issue, reach out to your administrator for further assistance.
# Why am I not able to access Talview on my browser?
Source: https://docs.talview.com/admin/login-and-access/diagnostics/why-am-i-not-able-to-access-talview-on-my-browser
If you're unable to open or access Talview on your browser, it could be due to an unsupported browser, network issues, or browser settings blocking the platform. This can prevent you from logging in and getting started. In this article, you will find the most common causes and fixes to access the platform successfully.
***
### 🔎 Troubleshooting common issues
| **What Might Be Wrong** | **How to Fix It** |
| :----------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| You're using an unsupported browser | Use a supported browser - **Chrome**, **Edge**, or **Firefox** are recommended for the best experience. |
| Your browser is outdated | Update your browser to the latest version and try again. |
| Your browser cache or cookies are causing issues | **Google Chrome:** Go to `Settings > Privacy and security > Clear browsing data`. Select *Cookies and other site data* and *Cached images and files*, then click *Clear data*. **Microsoft Edge:** Go to `Settings > Privacy, search, and services > Clear browsing data > Choose what to clear`. Select *Cookies and other site data* and *Cached images and files*, then click *Clear now*. **Mozilla Firefox:** Go to `Settings > Privacy & Security > Cookies and Site Data > Clear Data`. Select both options and click *Clear*. Reload the page after clearing. |
| Browser extensions are blocking the platform | Disable browser extensions, particularly ad blockers or security extensions and try again. |
| Your internet connection is unstable | Check your connection and try again once it's stable. |
| Your organization's network is blocking access | Check with your IT team to ensure Talview isn't being blocked by your organization's firewall or network settings. |
| The login URL is incorrect | Make sure you're using the correct login URL shared by your organization. Check your onboarding email if you're unsure. |
**Additional tips**
* Try opening the platform in an incognito or private browsing window to rule out extension or cache issues.
* If the issue persists, contact your administrator or reach out to Talview support for further assistance.
# Why can't I log in with SSO?
Source: https://docs.talview.com/admin/login-and-access/diagnostics/why-cant-i-log-in-with-sso
If you're unable to log in to Talview using *SSO (Single Sign-On)*, it could be due to an unrecognized email address, a missing SSO configuration, or a browser issue. This can prevent you from accessing your account using your company credentials. In this article, you will find the most common causes and fixes to complete your SSO login successfully.
***
### 🔎 Troubleshooting common issues
| **What Might Be Wrong** | **How to Fix It** |
| :-------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| You're not on the **Login** tab | Make sure the **Login** tab is selected before entering your email address. |
| You're using a personal email address | SSO only works with your official company email address. Re-enter your company email and click **Continue**. |
| You didn't receive the verification code | Check your spam or junk folder. If it's not there, wait for the resend timer to expire and click **Resend code**. |
| Your verification code has expired | Verification codes are time sensitive. Return to the login page and request a new one. |
| You're selecting the wrong account | If multiple accounts are linked to your email, make sure you select the right one on the **Pick an account** screen. If you're unsure, check with your administrator. |
| The **Login with SSO** button isn't appearing | SSO may not be enabled for your account. Contact your administrator to enable it. |
| Your browser is causing issues | Clear your browser cache and cookies. Try logging in on a different browser. |
**Additional tips**
* If **Login with SSO** isn't available, your administrator may have enabled password login instead. Try [logging in with your password](https://docs.talview.com/admin/login-and-access/how-tos/how-to-log-in-with-a-password).
* Use **Chrome**, **Edge**, or **Firefox** for the best experience.
* If the issue persists, contact your administrator for further assistance.
# Why can't I reset my password?
Source: https://docs.talview.com/admin/login-and-access/diagnostics/why-cant-i-reset-my-password
If you're unable to reset your password on Talview, it's usually due to an issue with your email address or the magic link. This can prevent you from regaining access to your account. In this article, you will find the most common causes and fixes to complete your password reset successfully.
***
### 🔎 Troubleshooting common issues
| **What Might Be Wrong** | **How to Fix It** |
| :-------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------- |
| You're entering the wrong email address | Make sure you're entering your registered email address. Check for typos or extra spaces. |
| You're selecting the wrong account | If multiple accounts are linked to your email, make sure you select the right one on the **Pick an account** screen before clicking ***Forgot password?*** |
| You didn't receive the magic link | - Check your spam or junk folder. - If it's not there, wait for the resend timer to expire and click **Resend code** to request a new magic link. |
| The magic link has expired | Magic links are time-sensitive. Return to the login page and repeat the process to request a new one. |
| Your browser is causing issues | - Clear your browser cache and cookies. - Try opening the magic link on a different browser. |
**Additional tips**
* Once your password is reset, log in using your new password via [How to log in with a password](https://docs.talview.com/admin/login-and-access/how-tos/how-to-log-in-with-a-password).
* If the issue persists, contact your administrator for further assistance.
# Why can't I sign up?
Source: https://docs.talview.com/admin/login-and-access/diagnostics/why-cant-i-sign-up
If you're having trouble signing up on Talview, it could be due to an unrecognised email address, an expired verification code, or a browser issue. This can prevent you from creating your account and getting started. In this article, you will find the most common causes and fixes to complete your sign-up successfully.
***
### 🔎 Troubleshooting common issues
| **What Might Be Wrong** | **How to Fix It** |
| :------------------------------------------------ | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| You're not on the **Sign-Up** tab | Make sure the **Sign-Up** tab is selected before entering your details. |
| You're entering an invalid email address | Check for typos or extra spaces and re-enter a valid email address. |
| You didn't receive the verification code | Check your spam or junk folder for an email from Talview. If it's not there, wait for the resend timer to expire and click **Resend code** to request a new one. If the issue persists, check with your IT team to ensure emails from Talview aren't being blocked by your organisation's email filters. |
| Your verification code has expired | Verification codes are time sensitive. Return to the sign-up page and request a new one. |
| An account already exists with your email address | An account may already be registered with your email. Try [logging in with your password](https://www.notion.so/talview/link) or [resetting your password](https://www.notion.so/talview/link) instead. |
| Your browser is causing issues | - Clear your browser cache and cookies. - Try signing up on a different browser. |
**Additional tips**
* Use **Chrome**, **Edge**, or **Firefox** for the best experience.
* If the issue persists, contact your administrator for further assistance.
# Why has my session expired?
Source: https://docs.talview.com/admin/login-and-access/diagnostics/why-has-my-session-expired
On Talview, your session remains active until you log out. If you're seeing a session expired message or have been logged out unexpectedly, it's likely due to a browser issue rather than a platform timeout. In this article, you will find the most common causes and fixes to restore your session quickly.
### 🔎 Troubleshooting common issues
| **What Might Be Wrong** | **How to Fix It** |
| :-------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Your browser cookies were cleared or expired | Log back in. Avoid clearing cookies while actively using the platform. |
| You're using multiple browser tabs or windows | Close any duplicate tabs and log in again from a single tab. |
| Your browser is causing issues | Clear your cache and cookies on **Google Chrome**, **Microsoft Edge**, or **Mozilla Firefox** (recommended browsers) and reload the page. Try logging in on a different browser. |
| You're on an unstable internet connection | Check your connection and log back in once it's stable. |
**Additional tips**
* Use **Chrome**, **Edge**, or **Firefox** for the best experience.
* If you're being logged out frequently, check with your IT team, your organization's network or security settings may be affecting your browser session.
* If the issue persists, contact your administrator for further assistance.
# Why is SSO not working for my organization?
Source: https://docs.talview.com/admin/login-and-access/diagnostics/why-is-sso-not-working-for-my-organization
If *SSO (Single Sign-On)* isn't working for your organization on Talview, it's likely due to a configuration issue or a mismatch between your email and your organization's SSO setup. This can prevent your entire team from logging in using company credentials. In this article, you will find the most common causes and fixes to get SSO working for your organization.
***
### 🔎 Troubleshooting common issues
| **What Might Be Wrong** | **How to Fix It** |
| :----------------------------------------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------- |
| SSO hasn't been enabled for your organization | Contact your administrator to confirm SSO is enabled for your organization's account. |
| SSO hasn't been enabled for specific users | SSO may be enabled at the organization level but not for individual accounts. Your administrator can enable it for the affected users. |
| Users are logging in with a personal email address | SSO only works with official company email addresses. Make sure all users are entering their company email address on the login page. |
| The **Login with SSO** button isn't appearing | • Confirm SSO is enabled for your organization. • Clear the browser cache and cookies and try again. • Try a different browser. |
| Your organization's *identity provider (IdP)* configuration has an error | Contact your IT team to verify that the IdP configuration is correctly set up and synced with Talview. |
**Additional tips**
* If SSO is unavailable, your administrator can enable password login as an alternative. Refer to [How to log in with a password](https://docs.talview.com/admin/login-and-access/how-tos/how-to-log-in-with-a-password).
* If the issue affects multiple users across your organization, escalate to your IT team or contact Talview support for assistance.
# Why isn't my password reset email arriving?
Source: https://docs.talview.com/admin/login-and-access/diagnostics/why-isnt-my-password-reset-email-arriving
When you request a password reset on Talview, a magic link is sent to your registered email address. If you haven't received it, a few things could be preventing it from reaching your inbox. In this article, you will find the most common causes and fixes to receive your magic link and complete your password reset.
***
### 🔎 Troubleshooting common issues
| **What Might Be Wrong** | **How to Fix It** |
| :------------------------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------- |
| The email is in your spam or junk folder | Check your spam or junk folder for an email from Talview. Mark it as "Not spam" to ensure future emails land in your inbox. |
| You entered the wrong email address | Return to the login page and restart the process using your correct registered email address. |
| You selected the wrong account | If multiple accounts are linked to your email, make sure you select the right one on the **Pick an account** screen before clicking ***Forgot password?*** |
| The magic link has expired | Magic links are time sensitive. If the link has expired, return to the login page and request a new one. |
| The resend timer hasn't expired yet | Wait for the resend timer to expire, then click **Resend code** to request a new magic link. |
| Your organization's email filters are blocking the email | Check with your IT team or administrator to ensure emails from Talview aren't being blocked by your organization's email filters. |
**Additional tips**
* Once you receive the magic link, click it promptly before it expires.
* If the issue persists, contact your administrator for further assistance.
# Why isn't my verification email arriving?
Source: https://docs.talview.com/admin/login-and-access/diagnostics/why-isnt-my-verification-email-arriving
When you sign up on Talview, a verification code is sent to your registered email address to confirm your identity. If it hasn't arrived, a few things could be preventing it from reaching your inbox. In this article, you will find the most common causes and fixes to receive your verification code and complete your sign-up.
***
### 🔎 Troubleshooting common issues
| **What Might Be Wrong** | **How to Fix It** |
| :------------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------- |
| The email is in your spam or junk folder | Check your spam or junk folder for an email from Talview. Mark it as "Not spam" to ensure future emails land in your inbox. |
| You entered the wrong email address | Return to the sign-up page and restart the process using your correct email address. |
| The verification code has expired | Verification codes are time sensitive. Wait for the resend timer to expire and click **Resend code** to request a new one. |
| The resend timer hasn't expired yet | Wait for the resend timer to expire before clicking **Resend code**. |
| Your organization's email filters are blocking the email | Check with your IT team or administrator to ensure emails from Talview aren't being blocked by your organisation's email filters. |
**Additional tips**
* Once you receive the verification code, enter it promptly before it expires.
* If the issue persists, contact your administrator for further assistance.
# Login And Access FAQs
Source: https://docs.talview.com/admin/login-and-access/faqs/login-and-access-faqs
### Introduction
This FAQ explains how users can sign up for and log in to Talview using their organization's configured authentication method, either *Single Sign-On (SSO)* or username/password.
It also covers password resets, supported browsers, session handling, and troubleshooting common login issues.
Use this guide to understand each step of the login flow and how to resolve common access-related problems.
***
### 1. Sign-up FAQs
**Q1. How do I sign up for Talview?**
1. Go to the Talview platform website and click **Sign up**.
2. Fill in your **Full name**, **Work email**, **Company name**, and **Role/Job title**.
3. Click **Get started** to submit the form.
4. A confirmation screen appears, and a member of the Talview team will reach out via your work email, typically within 1-2 business days.
**Q2. Can I sign up using a personal email address?**
No. Only official work email addresses are accepted. Personal email addresses (e.g., Gmail, Yahoo) aren't supported and will prevent your account from being activated.
**Q3. What happens after I submit the sign-up form?**
* A confirmation screen appears immediately after submission.
* A Talview team member will review your details and reach out via your work email to guide you through account setup and activation.
***
### 2. Understanding the login flow
**Q4. How do I log in to Talview?**
1. Go to your organisation's Talview login page.
2. Make sure the **Login** tab is selected.
3. Enter your work email address and click **Continue**.
4. If multiple accounts are linked to your email, select the correct one on the **Pick an account** screen.
5. Choose your login method: **Login with SSO** or enter your **password**.
**Q5. What browsers are supported for Talview login?**
Talview works best on:
* **Google Chrome** (recommended)
* **Microsoft Edge** (latest version)
* **Mozilla Firefox** (latest version)
Safari is supported on macOS. Always keep your browser updated for the best performance and security.
**Q6. I can't find my login URL.**
Check your onboarding email or contact your platform administrator for the direct login link.
***
### 3. Password login FAQs
**Q7. How do I log in using my password?**
1. On your organisation's Talview login page, enter your work email and click **Continue**.
2. If prompted, select your account from the **Pick an account** screen.
3. Enter your password and click **Login**.
**Q8. My password is correct, but I still can't log in.**
* Make sure **Caps Lock** is off.
* Clear your browser cache and re-enter your credentials.
* Try a different browser.
If the issue continues, contact your administrator.
**Q9. How do I reset my password?**
1. On the login page, enter your email and click **Continue**.
2. If prompted, select your account from the **Pick an account** screen.
3. On the password screen, click **Forgot password?**
4. A magic link is sent to your registered email. Click **Open Gmail** or **Open Outlook** to access it directly.
Tip: Can't find the email? Check your spam or junk folder. If it's not there, wait for the resend timer and click **Resend code** to request a new magic link.
**Q10. My account is locked. What should I do?**
After multiple failed login attempts, your account may be temporarily locked. Contact your administrator to regain access.
***
### 4. SSO login FAQs
**Q11. What is SSO and how does it work in Talview?**
*SSO (Single Sign-On)* lets you log in using your organisation's existing credentials. After entering your email, click **Login with SSO** and you'll be redirected to your corporate login page (e.g., Microsoft, Okta, Google). Once authenticated, you're redirected back to your account automatically.
**Q12. How do I log in using SSO?**
1. Go to your organisation's Talview login page and make sure the **Login** tab is selected.
2. Enter your company email address and click **Continue**.
3. If prompted, select your account from the **Pick an account** screen.
4. Click **Login with SSO** to authenticate using your company credentials.
**Q13. The "Login with SSO" button isn't appearing.**
Your administrator may need to enable SSO for your account. If your organisation also supports password login, you can use that as an alternative in the meantime.
**Q14. I'm seeing an "Invalid SSO token" or "Authentication failed" error.**
* Clear your browser cookies and try again.
* Confirm you're using your official work email associated with your SSO account.
* If the issue persists, contact your IT administrator to verify your SSO configuration.
**Q15. I can log in via SSO in one browser but not another.**
This is usually caused by cached credentials or session cookies. Try:
* Logging out of all active sessions.
* Clearing your cache and cookies.
* Logging in again using your organisation's Talview URL.
**Q16. Why am I redirected to the wrong login page or tenant?**
Make sure you're using your organisation's unique Talview URL (e.g., `abc.talview.com`). Using the wrong URL may cause authentication errors.
**Q17. My SSO works for other systems but not Talview.**
Your account may not be mapped to the Talview application group in your *identity provider (IdP)*. Ask your IT or Tenant Admin to confirm your account is assigned to the correct group.
**Q18. Can I use SSO from a personal device or outside the office network?**
Yes, if your organisation allows external SSO access. You'll still authenticate through your company's login page, subject to your IT policy (e.g., MFA or VPN requirements). If SSO is restricted to internal networks, contact your IT administrator for remote access permissions.
***
### 5. MFA, security, and session management
**Q19. Does Talview require MFA?**
Yes, if enabled by your organisation. After SSO login, you may be prompted to authenticate using an **Authenticator App**, **SMS**, or **Email OTP** as a secondary step.
**Q20. I didn't receive my MFA prompt or OTP.**
* Make sure your registered email or device is active.
* Check your spam or junk folder for OTP emails.
* If you're using an authenticator app, make sure it's synced correctly.
If the issue persists, contact your IT administrator to verify your MFA setup.
**Q21. Can I log in from multiple devices at the same time?**
You can log in from multiple devices, but only one active session per device type is supported. Logging in elsewhere may automatically sign out your previous session for security reasons.
***
### 6. Access and troubleshooting
**Q22. I logged in but don't see my workflows, tasks, or assignments.**
Your role may not have been assigned yet. Contact your Tenant Admin to confirm your role and permissions.
**Q23. The login page doesn't load or shows a blank screen.**
* Clear your browser cache and cookies.
* Make sure you're using a supported browser (Chrome, Edge, or Firefox).
* Disable your VPN or check your network connection.
If the issue persists, contact your administrator for further assistance.
**Q24. I'm stuck in a login loop. It keeps asking for my email again.**
This usually happens when session cookies are blocked or expired.
* Clear your browser cookies and try again.
* Make sure your browser allows redirects and third-party cookies.
If using SSO, confirm your organisation's login URL is correct.
***
# How to log in with a password
Source: https://docs.talview.com/admin/login-and-access/how-tos/how-to-log-in-with-a-password
Logging in to Talview with your password gives you quick access to your account using your registered email address. In this article, you will learn how to log in to Talview using your email address and password.
***
### Before you begin
Make sure you have:
* A registered Talview account
* Your registered email address
* Your account password
***
### Step-by-step guide
**Step 1: Go to the login page**
Open your browser (*Google Chrome, Microsoft Edge, or Mozilla Firefox*) and go to the Talview login page shared by your organization.
> Can't find your login URL? Check your onboarding email or reach out to your platform administrator.
**Step 2: Enter your email address**
1. Make sure the **Login** tab is selected.
2. Click the **Email** field and enter your registered email address.
3. Click **Continue**. Talview will verify your email and move you to the next step.
**Step 3: Enter the verification code**
1. An 8-digit verification code will be sent to your registered email address.
2. Open your inbox, copy the code, and enter it on the login page.
**Step 4: Select your account**
If multiple accounts are linked to your email, a screen appears for you to **Pick an account**. Select the account you'd like to log in with.
**Step 5: Enter your password**
1. Your email address will appear pre-filled with a *green checkmark*, confirming it was recognized.
2. Click the **Password** and enter your password.
> If you've forgotten your password, Click on **Forgot Password?** to receive a reset link to your registered email address.
**Step 6: Click Login**
Click **Login** to complete the process and access your dashboard.
> If your account is locked after multiple failed attempts, contact your administrator to regain access.
**Additional tips**
If you don't receive the verification code, check your spam or junk folder. Verification codes are time-sensitive, enter it promptly before it expires. If it has expired, return to the login page and request a new one.
# How to log in with SSO
Source: https://docs.talview.com/admin/login-and-access/how-tos/how-to-log-in-with-sso
Talview supports *Single Sign-On (SSO)*, allowing you to log in using your company credentials. In this article, you will learn how to log in to Talview using SSO.
***
### Before you begin
Make sure you have:
* An active Talview account
* Your official company email address - personal email addresses aren't supported for SSO login
* SSO enabled for your organisation - if you're unsure, check with your administrator
***
### Step-by-step guide
**Step 1: Go to the login page**
Open your browser (*Google Chrome, Microsoft Edge, or Mozilla Firefox*) and go to the Talview login page shared by your organization.
> Make sure the **Login** tab is selected.
**Step 2: Enter your email address**
Click the **Email** field, enter your company email address, and click **Continue**.
**Step 3: Enter the verification code**
Enter the verification code sent to your email address.
> The next time you log in from the same device and browser, you won't be prompted for a verification code.
**Step 4: Select your account**
If a **Pick an account** screen appears, select the account that matches your workspace. If you're unsure which to select, check with your administrator before proceeding.
**Step 5: Click Login with SSO**
Confirm your email address is pre-filled correctly, then click **Login with SSO** to authenticate using your company credentials.
**Additional tips**
If the **Login with SSO** button doesn't appear, your administrator may need to enable SSO for your account. You can also click **Login with password** if your administrator has enabled that option.
# How to reset your password
Source: https://docs.talview.com/admin/login-and-access/how-tos/how-to-reset-your-password
If you've forgotten your password, Talview lets you reset it quickly using a magic link sent to your registered email address. In this article, you will learn how to reset your password on Talview.
***
### Step-by-step guide
**Step 1: Go to the login page**
Open your browser and go to the Talview login page shared by your organization.
**Step 2: Enter your email address**
Click the **Email** field, enter your registered email address, and click **Continue**.
**Step 3: Select your account**
If your email is linked to multiple accounts, a **Pick an account** screen appears. Select the account you'd like to log in with.
**Step 4: Click Forgot password**
On the password entry screen, click **Forgot password?** to start the reset process.
**Step 5: Check your inbox for a magic link**
Talview sends a magic link to your registered email address.
Click **Open Gmail** or **Open Outlook** to access your inbox directly.
**Additional tips**
Can't find the email? Check your spam or junk folder. If it's not there, wait for the resend timer to expire and click **Resend code** to request a new magic link.
# How to sign up on Talview
Source: https://docs.talview.com/admin/login-and-access/how-tos/how-to-sign-up-on-talview
This article guide walks you through filling out the sign-up form to request access to the platform.
***
### Before You Begin
Make sure you have the following information ready before you start:
* Your full name
* A valid work email address
* Your company name
* Your role or job title (e.g., Recruiter, Talent Head, HR Ops, Product, IT)
***
### Steps to Sign Up
**Step 1: Navigate to the Sign-Up Page**
Go to the platform website and click **Sign up** at the top of the page.
The sign-up form will load with fields for your details.
**Step 2: Enter Your Full Name**
In the **Full name** field, type your first and last name.
This personalises your account on the platform.
**Step 3: Enter Your Work Email Address**
In the **Work email** field, enter your official company email address.
This email will be used to contact you and link your account.
> **Note:** Use your official work email address. Personal email addresses (e.g., Gmail, Yahoo) are not accepted and will prevent your account from being activated.
**Step 4: Provide Your Company Name**
Enter the name of your organisation in the **Company name** field.
**Step 5: Specify Your Role or Job Title**
In the **Role / Job Title** field, enter your position within your organisation.
This helps the team tailor your platform experience.
**Step 6: Submit the Form**
Once all fields are filled in, click **Get started**.
By submitting, you agree to the platform's [Terms and Conditions](https://www.notion.so/Login-Access-3183461472f3803196e3cdbd25891b8a?pvs=21) and [Privacy Policy](https://www.notion.so/Login-Access-3183461472f3803196e3cdbd25891b8a?pvs=21).
**Step 7: Confirmation**
After submitting, a confirmation screen will appear letting you know your request has been received. An expert from the team will contact you shortly to help you get started.
**Additional Tips**
Check your work email inbox (and spam/junk folder) for the activation message from the team.
# Account & Access
Source: https://docs.talview.com/candidates/assessments/ae/account-and-access
Common questions about logging in, invite links, and access to Talview as a candidate.
***
**Q: How do I log in to Talview?**
A: You don’t need to create an account yourself. You’ll receive a unique link from your recruiter or exam coordinator via email or SMS. Click the link to access your test or interview, and use the same email to which your invitation was sent to login.
***
**Q: I haven’t received my invite link. What should I do?**
A: Check your spam or promotions folder. If you still don’t see the invite, contact your recruiter or exam coordinator to resend it.
***
**Q: Can I use the same login link on multiple devices?**
A: No, your link is unique and tied to your session. Use it only once, on one device, to avoid access issues.
***
**Q: What if I get logged out during a test or interview?**
A: Reopen the original link from your invite to rejoin. If you continue to face issues, contact support or your recruiter.
***
**Q: Do I need to create a password?**
A: No, Talview uses secure one-click access via unique links. No separate password setup is required.
# Why can’t I confirm that my assessment responses were submitted?
Source: https://docs.talview.com/candidates/assessments/ae/diagnostics/why-cant-i-confirm-that-my-assessment-responses-were-submitted
After you complete an assessment, **Talview** displays a confirmation message indicating that your responses were submitted successfully. This checklist helps you verify your submission status and understand what to do if you did not see a confirmation.
### 🔎 Troubleshooting Common Issues
| **What Might Be Wrong** | **How to Fix It** |
| :---------------------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **No confirmation message appeared** | After clicking the final **submit button**, you should see a confirmation screen with a message such as: `"Your responses have been submitted successfully"`. Take a screenshot of this confirmation for your records. |
| **Network interrupted during submission** | If you notice network issues during the assessment, check your internet connection stability before clicking the final submit button. Wait for a stable connection, then **submit.** If you've already experienced a disruption, refresh the page to see if your progress was saved before attempting to resubmit. |
| **Unsure if submission went through** | Reach out to the hiring organization or Talview support with your assessment details (assessment name, date, and approximate completion time). They can verify whether your responses were received in their system. |
| **Link shows the Thank You page again when reopened** | Assessment links are single use. Once submitted, reopening the link always shows Thank You, this is expected, not an error. If this happened before you finished, contact the hiring organization to resend your invite. A completed link cannot be reissued. |
**Additional Tips:**
* Always screenshot the final confirmation screen as proof of submission
* Use recommended browsers (Chrome, Firefox, Edge) to minimize technical issues
* Ensure stable internet connection throughout the assessment—avoid submitting during connectivity problems
* If restarting an assessment, clear your browser cache first to load the current version
# Why is my face not being detected?
Source: https://docs.talview.com/candidates/assessments/ae/diagnostics/why-is-my-face-not-being-detected
During an assessment, **Talview** uses facial recognition to verify your identity through your camera. If you see a “Face not detected” message, this checklist helps you resolve common lighting, positioning, and camera-related issues.
## 🔎 Troubleshooting Common Issues
| **What might be wrong** | **How to fix it** |
| ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Poor lighting conditions | Position yourself in a well-lit area with light shining on your face from the front. Use natural light or add a lamp behind your screen pointed toward you. Avoid overhead-only lights that create shadows under your eyes or nose. |
| Backlighting creates shadows | Never sit with your back to windows or bright light sources, this makes your face appear dark. Turn your setup so the light faces you directly, not from behind. |
| Camera positioned incorrectly | Place your webcam at eye level and center your face in the frame. Maintain an arm's length distance so your full face is clearly visible without excessive zoom. Adjust the angle to avoid looking up or down. |
| Face obstructed or covered | Remove hats, sunglasses, masks, scarves, or anything covering your face (unless required for religious or medical reasons). Ensure your entire face from forehead to chin is visible. |
| Glasses causing glare | Adjust your position or tilt your glasses slightly to minimize reflections from lighting sources. If glare persists, try repositioning your light source or camera angle. |
| Multiple faces in frame | Ensure you're alone in the camera view, no other people, photos, or posters with faces should be visible. Only your face should appear in the frame. |
| Camera hardware issues | Test your webcam in another application (like your device's camera app) to confirm it's working. Clean the lens with a soft cloth to remove dust or smudges. Close other apps using the camera (Skype, Zoom, Teams). |
| Neutral background missing | Use a plain, well-lit background (white or neutral colors work best). Avoid busy patterns, bright colors, or cluttered areas that might confuse the detection system. |
**Additional Troubleshooting Tips**
* [**Test your webcam**](https://video-diagnostics.talview.org/) functionality by opening any video application to confirm the camera is working properly
* Clean the webcam lens, as dust or smudges can blur the image and affect detection
* Close all applications that might be using the camera, such as Skype, Zoom, or Teams, as they can interfere with the assessment platform
* Ensure adequate lighting in the room for optimal video quality
* If using an external camera, ensure it is properly connected to your computer with cables securely plugged in
# How to follow Assessment do’s and don’ts on Talview
Source: https://docs.talview.com/candidates/assessments/ae/how-to/how-to-follow-assessment-dos-and-donts-on-talview
Talview's Assessment module offers multiple formats including **Objective Assessments, Coding Assessments, Asynchronous Video Assessments, and proctored exams** to evaluate candidate skills effectively.
Follow these guidelines to complete each type successfully while adhering to platform rules.
***
### 1. Objective Assessments
Objective Assessments feature multiple-choice questions (MCQ or MCA) with timers and auto-submit functions.
**Dos:**
* Read instructions carefully and select one answer for MCQ or all applicable options for MCA questions.
* Monitor the visible countdown timer for total time or per-section limits to pace responses evenly.
* Use the **"Hide timer"** feature in your assessment to reduce distractions and maintain focus.
**Don'ts:**
* Attempt to pause or restart once started, as most must finish in one sitting.
* Switch devices or tabs, which may end the session prematurely.
* Ignore auto-submit at time expiry, as it prevents re-access.
***
### 2. Coding Assessments
Coding Assessments like Code-Solo support over 80 languages with built-in editors for writing, testing, and validating against test cases.
**Dos:**
* Select your preferred language early, then use auto-completion, syntax highlighting, and test runners to verify code.
* Test against visible and edge cases before submitting to ensure passes contribute to scores.
* Monitor the **timer** closely. When the time expires, your assessment will be **Auto submitted**.
* Submit only after confirming all tests pass consistently in a stable environment.
**Don'ts:**
* Rely solely on visible tests, as hidden ones determine final scores.
* Switch languages mid-assessment or use unapproved external tools.
***
### 3. Asynchronous Video Assessments
Asynchronous Video Assessments present one video question at a time for timed recording.
**Dos:**
* Take advantage of the **practice session** to become comfortable with the platform and its features before the actual assessment.
* Prepare a structured response during think time, speaking clearly to the camera with eye contact.
* Use the countdown to adjust posture, restate the question briefly, and pace within the progress bar.
* Stay natural, using off-screen bullet notes without reading verbatim.
**Don'ts:**
* Refresh, close the window, or stop mid-recording unless instructed, risking session end.
* Rush or exceed time by ignoring the timer; summarize key points if needed.
* Use scripts or face away from the camera during delivery.
***
### 4. Proctoring and General Guidelines
Proctored assessments across types include **facial recognition, ID verification,** **environment scans** and **secondary camera setup.**
**Dos:**
* Join 5-10 minutes early on Chrome or Edge with stable 2 Mbps+ internet in a quiet, lit space.
* Complete **360-degree room scan**s via secondary camera and maintain professional body language.
* Clear cache, disable VPNs/adblockers, and close bandwidth-heavy apps before starting.
**Don'ts:**
* Use public Wi-Fi, mobile hotspots without verification, or locations with distractions.
* Switch tabs, share screens without permission, or leave the workstation during monitoring.
* Attempts rejoin without checking progress save, contact support for issues instead.
**Additional Tips**
* Test your setup using practice session or system diagnostics before starting to confirm camera, mic, and internet stability.
* Keep a stable wired connection over Wi-Fi when possible, aiming for 2 Mbps upload/download speeds to prevent disruptions.
* Position in a well-lit room facing a plain wall, avoiding reflections or clutter that could trigger proctoring flags.
* Note the exact assessment link and start time; arrive 10 minutes early but do not refresh if minor delays occur.
* Focus on **time management**, prioritize high value questions first and flag others for review.
# How to navigate between questions during an Objective assessment
Source: https://docs.talview.com/candidates/assessments/ae/how-to/how-to-navigate-between-questions-during-an-objective-assessment
This article provides a comprehensive guide for candidates to navigate between questions during an **Objective Assessment** (With and without skip) using Talview’s Workflow Tools.
***
### Step-by-Step Guide
#### Navigate between questions without skips
In assessments where skips are not allowed, you must choose an answer before moving to another question.
* Select your preferred option for the current question.
* You can also click the question number from the navigation panel.
#### Navigate between questions with skips
In assessments where skips are enabled, you can move freely between questions even if some are unanswered.
* Use the question numbers on the navigation panel to move forward or backward at any time.
* You can scroll down after viewing or answering the current question to automatically reach the next one.
#### Use Mark for review
The “Mark for review” option helps you flag questions you want to revisit before submitting.
* On any question, click the icon to **Mark for review**; the question’s number in the navigation panel changes to blue.
* You can continue to scroll down or click other question numbers to move ahead; marked questions remain flagged until you return and unmark them or submit the test.
***
### What happens when you click “Submit”?
When you click *Submit*, a confirmation pop-up appears summarizing your assessment status before final submission.
* The pop-up shows how many questions you have not answered and how many you have marked for review and then asks if you want to review your answers again.
* Click **“Yes, Review”** to go back to the test and use the navigation panel or scroll to revisit unanswered or marked questions.
* Click **“No, Finish”** if you are confident about your responses and want to submit the assessment; after this, you typically cannot change your answers.
**Additional Tips:**
* Keep an eye on the question counter and timer so you can pace yourself and avoid rushing through the last few questions.
* Use **Mark for review** strategically for questions you are unsure about, and plan time near the end to revisit them.
* Avoid refreshing the browser or using the back button, as this can interrupt your test session or cause you to lose progress.
* If the page appears to freeze while scrolling or switching questions, wait a few seconds before clicking again to prevent accidental multiple actions.
# How to record a great video response (tips and best practices)
Source: https://docs.talview.com/candidates/assessments/ae/how-to/how-to-record-a-great-video-response-tips-and-best-practices
Tips for recording a great video response during your Talview Asynchronous Assessment include preparing your answer, setting up a distraction‑free environment, and speaking clearly and confidently to the camera. Following these simple steps helps you make a strong impression even without a live interviewer present.
***
### Understand the assessment format
* You will see one question at a time and will have limited time to think and then record your answer, so read the on‑screen instructions carefully before you start.
* Some questions may allow only one attempt and a fixed response duration, so keep an eye on the timer and aim to finish a few seconds early.
***
### Get your environment ready
* Choose a quiet, well‑lit space where you are unlikely to be interrupted and keep your background clean and professional.
* Avoid strong backlight from windows; position the light source in front of you so your face is clearly visible in the video.
***
### Check your device, camera, and mic
* Use a stable internet connection and ensure your device is plugged in or sufficiently charged before you begin the assessment.
* During the system check or practice question, confirm that your camera frames your head and shoulders and that your microphone captures your voice clearly without distortion.
***
### Plan your answers briefly
* Before you hit record, quickly structure your response with a short intro, 2–3 key points, and a brief closing sentence so your answer is focused.
* If practice or retakes are allowed, use one attempt to get comfortable with the timing and refine how you present your main points.
> **Note:** Take advantage of the **practice session** to become comfortable with the platform and its features before the actual assessment.
***
### Present yourself professionally
* Dress in neat, work‑appropriate clothing and sit upright, looking into the camera to simulate eye contact with the evaluator.
* Speak a little slower than normal conversation, articulate your words clearly, and avoid filler words or long pauses to keep your response easy to follow.
***
### Body language and on‑screen behavior
* Keep your movements minimal by sitting still, avoiding fidgeting, and keeping your hands away from your face so the focus stays on what you are saying.
* Maintain a neutral, friendly facial expression and nod occasionally to show engagement without exaggerating gestures.
***
### During the countdown and recording
* Use the countdown to sit still, adjust your posture, and ensure your eyes are level with the camera so you appear composed and ready.
* Quickly mentally rehearse the **question text** again during the countdown.
* Start with a calm, confident opening line (for example, restating the core of the question in your own words) to set up a clear direction for your answer.
* If you lose your train of thought, pause briefly, take a breath, and continue rather than stopping the recording; a short pause is acceptable, but long silences are not.
If something goes wrong
* If you face technical issues (for example, your camera or mic stops working), stop and follow on‑screen troubleshooting steps.
* Do not refresh or close the browser unless the instructions specifically recommend it; doing so may end your current question or session depending on the test configuration.
# How to run and test your code before submitting
Source: https://docs.talview.com/candidates/assessments/ae/how-to/how-to-run-and-test-your-code-before-submitting
Talview's coding editor in assessments like Code-Solo provides built-in tools to execute and validate your code against test cases prior to final submission, helping ensure accuracy and passing scores.
In this article, learn the step-by-step process to test effectively during your coding assessment.
***
### Steps to Run and Test Code
1. Read the question carefully and select your preferred programming language from the supported options (over 80 languages like Python, Java, JavaScript), then write your code into the editor.
2. Click the `"Run"` button to execute against visible and hidden test cases—green checks indicate passes; red flags show failures with error details.
3. Review console output, error messages, or failed test inputs to identify issues like syntax errors or logic flaws.
4. Edit your code accordingly and re-run iteratively until all cases pass consistently.
5. Click on **Submit**, only after confirming no remaining errors.
**Additional Tips:**
* Regularly run your code after small changes to quickly identify and fix bugs without losing track of errors.
* Pay attention to error messages and console output; they help locate issues like syntax mistakes or logical errors.
* Avoid copying code from external sources during the test to prevent plagiarism flags.
# How to submit your answers at the end of an Objective assessment
Source: https://docs.talview.com/candidates/assessments/ae/how-to/how-to-submit-your-answers-at-the-end-of-an-objective-assessment
In this article, you will learn how to submit your answers at the end of an **Objective (MCQ) Assessment** using Talview’s Platform.
***
### Step-by-Step Guide
Once you have answered all the questions in your Objective Assessment, follow the steps below to complete your test successfully.
**Step 1: Click on Submit**
* After you finish reviewing your answers, click the **Submit** button at the bottom of the screen.
* Once you confirm, your responses will be recorded and you will not be able to make any further changes.
> **Note:** To answer the questions, ***select one option*** for single-answer multiple choice questions (MCQ) and **select all applicable options** for MCA questions before clicking Submit.
**Step 2: Provide feedback**
* After submitting the assessment, **provide feedback** on the session.
* You will receive a **confirmation of your submission** on the screen.
**Additional Tips:**
* Ensure a stable internet connection during submission to avoid interruptions or delays in score generation.
* Before clicking Submit, double-check that all your answers are complete and saved, as you will not be able to change them after submission.
* If the submission page seems to hang or freeze, avoid refreshing immediately; wait a minute or two to allow the system to process your answers.
# How to take a Long form Assessment on Web
Source: https://docs.talview.com/candidates/assessments/ae/how-to/how-to-take-a-long-form-assessment-on-web
This article provides a comprehensive guide for candidates on how to take a **proctored Longform assessment online using Talview’s proctoring platform.** Proctored assessments ensure the integrity of the test by monitoring candidates during their assessments.
***
### What is a Longform Assessment?
A Longform Assessment is a comprehensive evaluation that requires candidates to respond to a series of open-ended questions or problems, allowing for deeper engagement and critical thinking. Unlike traditional multiple-choice tests, Longform Assessments often require candidates to **write essays, solve complex problems, or present arguments on specific topics.**
***
### Prerequisites
Before starting the assessment, ensure that you meet the following requirements:
* A **stable** internet connection.
* A device (computer or laptop) with a **webcam and microphone.**
* Google Chrome or Firefox browser installed and updated.
* A quiet, well-lit space **free from distractions.**
***
### Steps to take a Proctored Longform Assessment (Web)
**Step 1: Access the Assessment Link**
* You will receive a mail with a link to access the assessment.
* Click on this link, this will redirect you to the **Talview assessment portal.**
* Enter your mail id and enter the **confirmation code**, sent to your email.
**Step 2: System Requirements Check**
Before starting the assessment, perform a **system check:**
* Talview will prompt you to verify that your device meets the necessary requirements.
* Ensure your webcam and microphone are enabled and functioning, as these will be used during the proctoring process.
* Follow any prompts to resolve issues if your device does not meet the requirements.
**Step 3: Read the Instructions**
* Prior to commencing the assessment, read all provided instructions carefully.
* Familiarize yourself with the assessment format, timing, and any guidelines related to proctoring.
> **Prepare for the Proctored Environment:**
>
> 1. Make sure no unauthorized materials are present in your surroundings.
> 2. Clear your desk of any items that could be considered as aids during the test.
> 3. You may be asked to show your environment via your webcam.
**Step 4: Begin the Assessment**
* Once your identity is verified, and the camera, microphone and environment checks are complete, you can **start your assessment.**
* Follow the on-screen **instructions** carefully and attend to your assessment.
**Step 5: Submit the Assessment and Feedback**
* After completing the assessment, **provide feedback** on the session, then **submit your test.**
* You will receive a **confirmation of your submission** on the screen.
**Troubleshooting Common Issues**
In case of any technical difficulties or issues during the assessment,
* Check your internet connection.
* Refresh the page or relaunch your browser.
* Restart your device if necessary.
* If you continue to have problems, contact Talview's technical support using the support options provided within the portal.
# How to take a Proctored Objective Assessment on Web
Source: https://docs.talview.com/candidates/assessments/ae/how-to/how-to-take-a-proctored-objective-assessment-on-web
This article provides a comprehensive guide for candidates preparing to take a **proctored objective assessment using Talview's platform.**
Proctored assessments are designed to maintain the integrity of the testing process, ensuring that candidates complete their assessments honestly and fairly.
***
### What is an Objective Assessment?
An objective assessment can include **multiple-choice questions, true/false questions, and fill-in-the-blank formats.** The primary goal of an objective assessment is to ensure fairness and impartiality in evaluating candidates, as the scoring is based solely on the correctness of the responses.
***
### Prerequisites
Before beginning your assessment, ensure you have the following:
* A **stable** internet connection.
* A computer or laptop with a **working webcam and microphone.**
* Supported web browser (Google Chrome is recommended).
* A **quiet, well-lit environment** free from distractions.
* A **valid** ID card for identity verification.
***
### Steps to take a Proctored Objective Assessment (Web)
**Step 1: Access the Assessment Link**
* You will receive an email with a link to access the assessment.
* Click on this link, this will redirect you to the **Talview assessment portal.**
* Enter the **confirmation code** sent to your email.
**Step 2: Identity Verification**
* Open **Talview assessment portal** and **log in** using your credentials.
* You will need to verify your identity. This typically involves:
* Taking a **photo of yourself.**
* Taking a **photo of your ID.**
**Step 3: Camera, Microphone and Environment Check**
* The system will check if your **webcam and microphone** are functioning correctly. Make sure that:
* Your camera is clear, capturing your face.
* Your microphone is working, allowing for audio input.
* Enable **Secondary device**
* Make sure your Test environment is clear and ready for the **Environment check**
**Step 4: Begin the Assessment**
* Once your identity is verified, and the camera and microphone checks are complete, you can **start your assessment.**
* Read the instructions provided before starting and familiarize yourself with the format of the questions.
> **Prepare for the Proctored Environment:**
>
> 1. Make sure no unauthorized materials are present in your surroundings.
> 2. Clear your desk of any items that could be considered as aids during the test.
> 3. You may be asked to show your environment via your webcam.
**Step 5: During the Assessment**
* Ensure your environment remains quiet and free from distractions during the test.
* Follow the on-screen instructions carefully.
**Step 6: Submit the Assessment**
* After completing the assessment, **provide feedback** on the session, then **submit your test.**
* You will receive a **confirmation of your submission** on the screen.
**Troubleshooting Common Issues:**
* **Technical Issues**: If you encounter crashes or errors during the assessment, try refreshing your browser or restarting your computer. Ensure your internet connection is stable.
* **Audio/Video Problems**: If your webcam or microphone does not work, check that it is properly connected and that you have granted the browser permission to access these devices.
* **ID Verification Issues**: If you have trouble with the identity verification process, ensure your ID is clear and legible.
# How to take an Asynchronous Assessment on Web
Source: https://docs.talview.com/candidates/assessments/ae/how-to/how-to-take-an-asynchronous-assessment-on-web
With the Talview platform, candidates can complete their assessments at their convenience while showcasing their skills and abilities effectively.
This article provides a step-by-step guide for candidates on how to take an**Asynchronous assessment on the web using Talview.**
***
### What is an Asynchronous Assessment?
An **asynchronous assessment**, often referred to as a recorded assessment, is a type of an assessment where candidates answer questions without being in real-time interaction with the recruiter or assessment facilitator. This format allows candidates to record their responses at their convenience, as they can access the questions whenever they choose, within a specified timeframe.
***
### Prerequisites
Before starting the assessment, ensure that you have:
* A **stable** internet connection.
* A computer or laptop with a **webcam and microphone.**
* Access to the **assessment link** provided by the recruiter or employer.
* A **compatible** web browser (Chrome and Firefox is recommended).
***
### Steps to take an Asynchronous Assessment (Web)
**Step 1: Access the Assessment Link**
* You will receive a mail with a link to access the assessment.
* Click on this link, this will redirect you to the **Talview assessment portal.**
* Enter the email id to which the invitation was sent and enter the **confirmation code**, sent to your email.
**Step 2: Read the Instructions**
* Prior to commencing the assessment, read all provided instructions carefully.
* Familiarize yourself with the assessment format, timing, and any guidelines.
**Step 3: Start the Assessment**
* Take the **Practice recording**, to understand how the actual response recording works. Here, your **microphone and camera** capability will be checked.
* Once you’re done practicing, you can **proceed** to start the assessment.
**Step 4: Record Your Video Responses**
* **Start recording** your video responses to the questions asked.
* Speak clearly and maintain eye contact with the camera to engage.
* Once you're done with your response, Click on **Stop recording.**
* Click **Retake** to record your response again, if you want to improve your answer.
**Step 5: Feedback and Assessment submission**
* After **submitting** the assessment, provide **feedback** based on your experience.
**Troubleshooting Common Issues:**
In case of any technical difficulties or issues during the assessment,
* Check your internet connection.
* Refresh the page or relaunch your browser.
* Restart your device if necessary.
* If you continue to have problems, contact Talview's technical support using the support options provided within the portal.
# How We Protect Your Data
Source: https://docs.talview.com/candidates/assessments/ae/how-to/how-we-protect-your-data
When you take an assessment through Talview, protecting your personal data and privacy is a top priority. You entrust us with sensitive information such as **your identity details, biometric data, video and audio recordings, and your responses** during the assessment.
This article explains how we securely handle and protect your data throughout the assessment process, ensuring compliance with strict global data privacy standards and using advanced security technologies. Understanding **how your data is protected** can help you feel confident and secure as you complete your assessment with us.
***
### **Data Collected During Your Assessment**
Your data is safeguarded through end-to-end encryption, strict access controls, and compliance with global privacy laws like GDPR, CCPA, and others.
We collect specific information to ensure assessment integrity, including *your name, email, phone, face capture, voice samples, surroundings and behavioral data*. Device details like *IP address, browser type, and location* may also be gathered automatically via cookies for analytics, but non-personal aggregate data is used only to improve services. No unique identifiers like UDID or MAC addresses are captured, and you consent to collection each time you access the platform via clear notices in the Privacy Policy and Teams.
### Security Measures and Access Controls
Access to your data follows role-based permissions with periodic reviews, audits, and automatic revocation upon role changes or employee termination. A Data Security Committee oversees policies, while external vendors conduct vulnerability and penetration testing every six months. Physical and hardware security includes safeguards against loss or unauthorized use, with Data Protection Impact Assessments (DPIA) for high-risk processing.
### Compliance and Regional Data Handling
Talview complies with GDPR (EU data hosted in EU servers), CCPA, LGPD, PDPA, PIPEDA, COPPA for minors, and pursues ISO 27001/SOC2 audits. Biometric and behavioral data is retained only as needed (default 6 months per SLA) then securely deleted by overwriting. For EU/EEA users, processing includes consent-based decisions with human oversight on AI flags
### Understanding AI and Automated Processes
We use advanced AI technologies for proctoring, identity verification through face-photo ID matching and biometric authentication, and behavioral analysis to maintain assessment integrity. These AI systems process your facial recognition, voice patterns, and behavioral biometrics like keystrokes and movements to detect potential fraud while prioritizing your privacy with minimal data retention and end-to-end encryption.
All AI-driven flags and decisions receive human oversight by trained proctors, with ongoing bias detection, fairness metrics, third-party audits, and accommodations to ensure equitable and transparent evaluations.
### **How We Protect Your Video and Audio Data**
During your assessment, we encrypt all video and audio streams using end-to-end protocols to securely transmit them and prevent any interception during live or recorded proctoring sessions. We store these recordings only for the duration specified by the recruiting organization typically per service level agreements before automatically deleting them securely to minimize data retention. Access remains strictly limited to authorized proctors or reviewers involved in integrity checks, with role-based controls ensuring no unnecessary exposure.
### **Protecting Your Data on Different Devices and Networks**
Whether using a personal device, public computer, or any supported browser for your assessment, we secure all data transmissions with high-grade SSL/TLS protocols and end-to-end encryption to protect against interception. Our platform stores no personal data locally on your device beyond the active session, clearing temporary files upon completion to avoid persistence. Built-in mechanisms prevent unauthorized caching, browser data leakage, or local storage of sensitive information like biometrics or recordings.
### **Data After Your Assessment**
After you complete your assessment, we retain your personal data only for as long as it is needed for evaluation, compliance, and audit purposes, or as required by law and our agreement with the recruiting organization. Once this period ends, your data is securely deleted or anonymized so it can no longer be linked back to you.
If you are in a region covered by GDPR or similar regulations, you may have the right to request deletion of your personal data (the “right to be forgotten”). To exercise this, you can raise a request with the recruiting organization, who will work with us to review and process the deletion in line with applicable legal and contractual requirements.
***
### Our Commitment to Your Privacy and Security
We understand that trust is essential when sharing your personal data during assessments. That is why we are dedicated to maintaining the highest standards of data protection, transparency, and ethical AI use. Our security protocols and compliance measures evolve continuously to address emerging risks and regulatory changes. If you ever have questions or concerns about how your data is managed or wish to exercise your privacy rights, you can contact your recruiting organization.
Your privacy and security are our utmost priority throughout your entire assessment experience.
# Understanding the Timer and Auto-Submit in an Objective assessment
Source: https://docs.talview.com/candidates/assessments/ae/how-to/understanding-the-timer-and-auto-submit-in-an-objective-assessment
In this article, you will learn about the **timer** and **auto-submit** features in Objective Assessment. This helps you manage your time and complete the assessment smoothly without needing to manually submit.
***
### Step-by-Step Guide
### Timer Display Toggle
* You may see a timer during your objective assessment which shows how much time is remaining.
* Timer display can be toggled to **hide the timer** from your view depending on the test settings configured by the administrators or examiners. Use this feature to avoid getting overwhelmed by constantly watching the countdown.
* Hiding the timer means the candidate will not visually see the countdown but the time limit for the assessment still runs in the background.
> **Note:** When there’s **last 10 secs left** to finish the assessment, the color of the timer turns to red automatically.
### Auto-Submit on Timer End
* When the timer reaches zero, the assessment is **auto-submitted** immediately.
* Auto-submission ensures all answers that the candidate provided up to that point are saved and submitted for evaluation, preventing loss of work if the candidate runs out of time.
* This feature is critical in timed assessments to maintain the integrity of the exam and fairness for all candidates by strictly enforcing time limits.
**Additional Tips:**
* Always keep track of the time yourself even if the timer is hidden, so you can pace your answers effectively.
* Ensure a stable internet connection to avoid disruptions that may affect auto-submission at the timer end.
* Avoid waiting until the last moments to answer questions; the auto-submit triggers promptly as soon as time runs out.
* If possible, practice with timed sample tests to get comfortable managing your time within the set limits.
# System Requirements
Source: https://docs.talview.com/candidates/assessments/ae/system-requirements
Frequently asked questions about supported browsers, devices, and internet requirements for candidates.
***
**Q: Which browsers are supported?**
A: The latest versions of Google Chrome, Mozilla Firefox, and Microsoft Edge are recommended. Safari is supported for Mac users for only interviews. Internet Explorer is not supported.
***
**Q: Can I use a mobile device for my test or interview?**
A: Yes, most assessments and interviews can be taken on mobile. However, for the best experience (especially coding or essay tests), we recommend a laptop or desktop.
***
**Q: Can I take the test on my office laptop?**
A: Sometimes, corporate firewalls or security restrictions block access. If you face issues, switch to a personal laptop or mobile device.
***
**Q: My device shows as unsupported. What should I do?**
A: Ensure your operating system and browser are updated to the latest version. If the issue persists, try a different supported device.
***
**Q: What are the minimum internet requirements?**
A: A stable connection with at least 1 Mbps upload and download speed is required. For video interviews, 2 Mbps or higher is recommended.
***
**Q: Can I use a VPN or proxy during my test?**
A: No, VPNs and proxies may interfere with access. Disable them before starting your session.
# Taking an Assessment
Source: https://docs.talview.com/candidates/assessments/ae/taking-assessments
Frequently asked questions for candidates about taking assessments, covering pre-assessment, during, and post-assessment scenarios.
***
### Pre-Assessment
**Q: How do I access my assessment?**
A: You’ll receive an email with a unique link. Click the launch link to open your assessment in your browser.
***
**Q: Can I use my phone for an assessment?**
A: Yes, but we recommend using a laptop or desktop for the best experience, especially if your test involves coding or written responses.
***
**Q: What browsers or devices can I use?**
A: Assessments work best on the latest versions of Chrome, Firefox, or Edge. Safari is supported for Mac users.
***
**Q: Can I take the assessment from any location?**
A: Yes, but choose a quiet, well-lit space where you won’t be interrupted. Some assessments may require a private room for proctoring.
***
### During the Assessment
**Q: Can I pause or restart my assessment?**
A: No, once started, most assessments must be completed in one sitting. If your test allows breaks, instructions will appear on your screen.
***
**Q: What should I do if I accidentally close the window?**
A: In most cases, you can rejoin using the same link, and your progress will be saved. If you can’t rejoin, contact support or your recruiter immediately.
***
**Q: My video or audio isn’t working. What should I do?**
A: Follow the steps below:
* Check that your browser has permission to use your camera and microphone.
* Close other apps using your camera (Zoom, Teams, Meet).
* Refresh and rejoin.
***
**Q: Can I switch devices mid-assessment?**
A: No, assessments are designed to be taken on a single device. Switching may cause your test to end.
***
**Q: What happens if I lose internet connection?**
A: The system will try to reconnect automatically. If you’re unable to continue, contact support with your test link and time.
***
### Post-Assessment
**Q: How do I know my assessment was submitted successfully?**
A: You’ll see a submission confirmation message once the test is completed. If you don’t, reach out to support.
***
**Q: Can I retake an assessment if I faced technical issues?**
A: Retakes are allowed only if approved by your recruiter or test administrator. Contact them directly for guidance.
***
**Q: When will I receive my results?**
A: Results are shared by your recruiter or exam coordinator. Timelines vary depending on the organization’s evaluation process.
***
**Q: Will I get a copy of my assessment responses?**
A: No, responses are stored securely and only accessible to authorized recruiters or coordinators.
# How to resolve Verification code errors?
Source: https://docs.talview.com/candidates/assessments/diagnostics/how-to-resolve-verification-code-errors
Attendees receive an email from Talview containing a test link and a unique verification code to access their assessment. After clicking the link and entering the code, they proceed to complete the onboarding steps before starting their test.
This article helps attendees resolve issues when their verification code is invalid or not accepted during the login process.
## 🔎Troubleshooting Common Issues
| **What might be wrong** | **How to fix it** |
| :-------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Verification code entered incorrectly** | Copy and paste the code directly from the email instead of typing it manually. Ensure there are no extra spaces before or after the code. The code is case-sensitive, so match the exact capitalization shown in the email. |
| **Verification code has expired** | Verification codes are typically valid for a limited time. If your code has expired, look for a "Resend Code" option on the login page, or contact your test organizer to send a new invitation link. |
| **Using an old or previous verification code** | If you received multiple emails from Talview, ensure you're using the code from the most recent email. Previous codes become invalid once a new one is generated. |
| **Email link and verification code are mismatched** | Always use the verification code that came in the same email as the link you clicked. If you clicked a link from one email but used a code from another, the system will reject it. |
| **Browser cache or cookies interfering** | Clear your browser cache and cookies, then restart your browser. Try accessing the test link again in a private/incognito window to rule out stored data conflicts. |
| **Copy-paste formatting issues** | If copying the code, paste it into a plain text editor (like Notepad) first, then copy it again before pasting into the verification field. This removes any hidden formatting characters. |
### **Additional Tips:**
* Check your spam or junk folder if you haven't received the verification code email, as automated messages sometimes get filtered.
* Avoid refreshing the login page multiple times after entering the code, as this may trigger security blocks.
* If you're using a mobile device, switch to a desktop or laptop browser if the issue persists, as some mobile browsers may not handle the verification properly.
* Make sure you're accessing the link from the same device where you opened the email, especially if your organization has device-specific security policies.
* Contact your test administrator immediately if none of these solutions work, and provide them with the exact error message you're seeing.
# What to do if I receive a warning during a proctored test?
Source: https://docs.talview.com/candidates/assessments/diagnostics/what-to-do-if-i-receive-a-warning-during-a-proctored-test
Receiving a warning during your proctored test can be stressful, but understanding why warnings appear and how to respond appropriately will help you complete your assessment successfully.
Warnings are automated alerts triggered by the proctoring system when it detects behavior that may violate test rules. This article explains common warning scenarios and provides clear steps to address them.
### Understanding Proctoring Warnings
Talview's AI-powered proctoring monitors your test session to ensure a fair testing environment. The system may issue warnings for actions such as:
* Looking away from the screen
* Presence of other people in the test environment
* Moving away from camera view
* Attempting to switch tabs or applications
* Covering or blocking your webcam
* Background noise or voices
* Using unauthorized materials or devices
Most warnings are precautionary and give you a chance to correct your behavior before any serious action is taken. If you think the warning is falsely shown, let the proctor know in the chat and continue with your exam.
### 🔎 Warning shown? Here’s what to check for:
| **What Might Be Wrong** | **How to Fix It** |
| :-------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Face not detected** | Adjust your seating position so your face is clearly visible and centered in the camera frame. Ensure adequate lighting falls on your face from the front, not from behind. Avoid wearing accessories that obscure your face. |
| **Multiple faces detected** | Ensure you are alone in the room during the test. Ask others to leave the testing area. If someone inadvertently enters, acknowledge the warning and immediately ensure they leave the frame. |
| **Looking away from screen** | Keep your eyes focused on the test screen. Avoid looking around the room, at notes unless allowed in the exam rules. |
| **Tab switching or application access** | Do not switch browser tabs, open new applications, or access other programs during the test. Close all unnecessary applications before starting. Use only the test interface provided. |
| **Audio anomaly detected** | Silence your phone/secondary camera and other devices. Ensure you are in a quiet environment. |
| **Webcam blocked or covered** | Check that nothing is obstructing your webcam. Remove any stickers, tape, or objects covering the camera. Ensure your camera lens is clean and unobstructed. |
| **Prohibited object detected** | Remove all unauthorized materials from your testing area, including phones, tablets, notes, books, or additional monitors. |
| **Person left the frame** | Remain seated at your workstation throughout the test. If you must briefly adjust your position, do so quickly and return to a clearly visible position in the camera frame. |
**Best Practices**
Following these guidelines will help you maintain a warning-free test session:
* Set up your testing environment according to the pre-test requirements checklist
* Position yourself centrally in the camera frame with good front-facing lighting
* Clear your desk of all materials except those explicitly permitted by the test administrator
* Silence all devices and close unnecessary applications before beginning
* Remain focused on the test screen throughout your session
* Keep your hands visible and avoid excessive movement
* Stay in your seat for the duration of the test
If you receive multiple warnings, the session may be flagged for review or end. Take each warning seriously and correct the behavior immediately.
# How to verify your identity as part of your exam enrollment
Source: https://docs.talview.com/candidates/assessments/enrolling-for-an-exam/how-tos/how-to-verify-your-identity-as-part-of-your-exam-enrollment
As part of enrolling for an exam, you may be asked to verify your identity by submitting a photo ID and a face capture, if this step has been enabled by your exam coordinator. Talview uses these details to confirm your identity throughout your exam journey. In this article, you will learn how to submit your ID and face capture during enrollment.
***
#### Before You Begin
Make sure you have:
* Entered your basic enrollment details (Full Name, Country of Residence, and Age).
* A desktop with a working camera.
* A valid government-issued photo ID (such as a Driver License, Passport) on hand.
* If you're an underage candidate, completed the parent or legal guardian consent and verification steps first - these steps only appear for underage candidates and must be finished before you can submit your own ID and face capture. Underage candidates require consent from a parent or legal guardian before they can enroll. Refer: *How to complete parent or legal guardian consent and ID verification during enrollment* to learn more.
***
#### Step-by-Step Guide
**1. Provide your ID details**
* Select the **Country** that issued your ID.
* Select the **Subdivision(state/province)** where your ID was issued from the searchable dropdown.
* Select the **type of ID** you'll be submitting - for example, Driver License, Passport.
* Select **Capture** next to your chosen ID type.
**2. Capture your ID**
* Once camera access is allowed, position the front of your ID within the on-screen frame, making sure all edges are visible and there's no glare, then select **Capture**.
* Depending on the type of ID, you may also be prompted to capture the back of your ID in the same way.
* On the review screen, confirm the image(s) are clear and select **Submit**, or retake if needed.
**3. Capture your face**
* Position your face within the on-screen frame, following the on-screen instructions - look straight at the camera, ensure good lighting, and avoid covering your face or wearing hats or sunglasses.
* Select **Capture**.
* On the review screen, confirm the image is clear and select **Submit**, or retake it if needed.
**4. Confirmation**
* Once your face capture is submitted, a confirmation screen lets you know your details have been submitted successfully.
* You'll also receive a confirmation email at your registered email address with further details about your exam, including the date, time, and any additional instructions you may need before your exam.
* If any of your submitted details need to be reviewed manually, you may be contacted separately before you receive final confirmation.
***
**Additional Tips**
* If the candidate is below 18, the parental consent and verification steps always come first, the candidate's own ID and face capture only happens after the parent or guardian has completed their part.
* Make sure your ID is fully visible with no cropped corners before submitting, a blurry or partial capture may need to be retaken.
# Attendee FAQs - Attendee Proctoring Onboarding
Source: https://docs.talview.com/candidates/assessments/faqs/attendee-faqs-attendee-proctoring-onboarding
### **Introduction**
Attendee Proctoring Onboarding is the pre-assessment verification process that ensures a secure and fair testing environment.
This FAQ is specifically for **Attendees (candidates/test takers)** who are required to complete identity verification, system checks, secure browser setup, and environment validation before starting the assessments.
***
### **1. Before You Begin**
**Q1. What is Attendee Proctoring Onboarding?**
Attendee Proctoring Onboarding is a mandatory pre-exam process that verifies:
* Your device compatibility
* Your camera and microphone access
* Your identity (ID verification and facial capture)
* Your testing environment (if required)
* Secure Browser installation (for certain assessments)
You must complete onboarding successfully before you begin your exam.
**Q2. How can I check if my device and browser are compatible?**
Before your scheduled exam:
* Ensure you are using a supported browser:
* Google Chrome (recommended)
* Microsoft Edge
* Update your browser to the latest version.
* Test your:
* Camera
* Microphone
* Internet connection
For optimal performance, close unnecessary tabs and background applications before starting.
**Q3. What devices can I use for the assessment?**
You can typically use:
* **Desktop or Laptop (Recommended)** – Windows or macOS
* **Supported browsers** – Chrome or Edge and other chromium based browsers (latest versions)
Mobile devices are not recommended unless explicitly permitted by your organization.
**Q4. What are the minimum system requirements?**
| Requirement | Minimum |
| :---------- | :----------------------- |
| RAM | 4GB |
| Processor | Dual-core 2 GHz |
| Webcam | Functional camera |
| Microphone | Required |
| Internet | 1 Mbps upload & download |
For optimal performance, use a desktop or laptop.
**Q5. Can I use a mobile phone or tablet for onboarding?**
Mobile devices are not recommended unless explicitly permitted. Most proctored assessments require a laptop or desktop.
**Q6. How early should I start the onboarding process?**
You should begin onboarding at least **15–20 minutes before** your scheduled exam time. This allows sufficient time for system checks, Secure Browser updates (if required), and identity verification.
**Q7. What should I keep ready before starting onboarding?**
* Government-issued photo ID
* Stable internet connection
* Fully charged laptop (or connected power source)
* Quiet, well-lit room
* Administrator access to install Secure Browser (if Secure Browser is required)
**Q8. Can I use a public or office network?**
Yes, but ensure:
* The network does not block camera or screen recording permissions
* Firewall restrictions do not prevent Secure Browser installation
* Bandwidth is stable
> **Note**: If using a corporate network, check with IT in advance.
**Q9. Can I change devices after starting onboarding?**
If you face technical issues during onboarding, you may switch to another supported device and restart the process.
However, after completing onboarding, you should continue the exam on the **same device**, as changing devices may require re-verification.
***
### **2. Secure Browser**
**Q1. What is a Secure Browser?**
A Secure Browser is a controlled testing browser used to ensure exam integrity. It restricts certain system and browser functions during the assessment. It creates a secure testing environment to prevent unauthorized activity.
**Q2. How do I install the Secure Browser?**
Some assessments require a **Secure Browser** for enhanced exam security.
To install:
**For Windows:**
* Download TSB from the **Microsoft Store** or the official Talview download link provided in your assessment email.
* Right-click the installer and select **“Run as Administrator.”**
* Follow the on-screen instructions to complete the installation.
* When prompted, grant permissions for:
* Camera
* Microphone
* Screen Recording
**For macOS:**
* Download the **.dmg file** from Talview’s official download page.
* Open the .**dmg file**.
* Drag the Talview Secure Browser application into your **Applications** folder.
* Launch the application.
* Allow permissions for:
* Camera
* Microphone
* Screen Recording
> **NOTE:**
>
> * Administrator privileges are required to install TSB.
> * Launch TSB **15–20 minutes before your scheduled test** to allow time for updates and system checks.
**Q3. Why is Secure Browser required?**
The Secure Browser helps maintain a fair and secure assessment environment by preventing unauthorized actions and monitoring system activity during the exam.
**Q4. What if Secure Browser fails to launch?**
* Restart your device
* Reinstall the Secure Browser
* Ensure administrator access
* Temporarily disable antivirus (if blocking installation)
> **Note**: Uninstall any previous versions before you install the latest version of Secure browser.
**Q5. Can I use other applications while using the Secure Browser?**
No. The Secure Browser restricts access to other applications and system functions during the assessment.
**Q6. Do I need to uninstall the Secure Browser after the exam?**
You can keep the Secure Browser installed if you have upcoming assessments scheduled. If you do not have any future exams, you may uninstall it from your system settings.
**Q7. Will Secure Browser access my personal files?**
No. The Secure Browser does not access personal files. It only restricts system functionality during the assessment session.
***
### 3. Verification Process
**Q1. Why is my verification taking longer than expected?**
Verification may take longer if additional checks are being completed or if multiple test takers are being verified at the same time.
Delays or retries can also occur due to:
* Slow internet connection
* Poor lighting
* Blurry ID or facial image
> **Note**: Please remain on the page and avoid refreshing repeatedly while the process completes.
**Q2. My exam time has started, but I’m stuck on the verification page. What should I do?**
If your exam time has started and verification is still in progress:
* **Stay on the verification page** and do not close the window.
* Avoid repeated refresh attempts.
* If the delay continues after your scheduled start time, use the **chat option to contact the proctor** and inform them that verification is pending.
> **Note**: Do not exit the session unless instructed by the proctor or support.
**Q3. What happens if my verification fails?**
If verification fails:
* Reattempt facial capture or ID upload carefully.
* Ensure proper lighting and camera positioning.
* Follow on-screen instructions.
**Q4. What documents are accepted for ID verification?**
Typically accepted documents include:
* Government-issued ID card
* Passport
* Driver’s License
> **Note:** If explicitly mentioned in your assessment instructions, a **College/Institution ID** may also be accepted. Refer to your assessment instructions for exact requirements.
**Q5. What should I do if my face is not detected during verification?**
* Improve lighting
* Remove hats or face coverings
* Sit directly facing the camera
* Ensure your face is centered in the frame
**Q6. What is a 360° Environment Check?**
You may be asked to rotate your camera briefly to show your surroundings. This confirms that no unauthorized materials or individuals are present.
**Q7. What happens if my ID gets rejected during verification?**
If your ID is rejected, you **cannot proceed with the exam** until a valid and clear ID is submitted. The system expects a high-quality image where all required details (photo, name, expiry date, etc.) are clearly visible. You will be prompted to **retake and resubmit your ID** with a clearer image.
**Q8. Why am I asked to show my surroundings?**
This ensures:
* No unauthorized materials are present
* No other individuals are assisting you
* The environment meets exam integrity standards
***
### **5. During the Exam**
**Q1. Am I allowed to take a break during the exam?**
Break permissions depend on how your organization has configured the assessment.
* If breaks are allowed, you will see a **Pause/Break** option.
* If breaks are not allowed:
* Leaving the screen may trigger proctoring alerts.
* The session may be flagged.
* Your exam may be automatically submitted or terminated.
> **Note**: Always read the instructions carefully before you begin your exam.
**Q2. My internet connection is stable, but my screen is frozen. How can I fix this?**
If your screen freezes:
* Wait a few seconds to see if it resumes.
* Close unnecessary background applications.
* Refresh the page once.
* Restart the Secure Browser if required.
* Rejoin using the original assessment link.
> **Note**: Avoid repeated refresh attempts, as this may disrupt the session.
**Q3. What should I do if I accidentally close the exam window?**
If you accidentally close:
* Reopen the original assessment link immediately.
* Log back in using your registered credentials.
* Continue the assessment (if allowed by configuration).
> **Note**: If you cannot resume, contact support right away.
**Q4. What actions can trigger proctoring alerts?**
* Switching browser tabs
* Opening other applications
* Leaving the camera frame
* Disconnecting camera or microphone
* Connecting additional devices
> **Note**: These alerts may be reviewed by Alvy (AI Proctoring Agent) or a human proctor.
**Q5. What happens if I lose internet connection during the exam?**
* Reconnect immediately
* Reopen the original exam link
* Resume the assessment (if allowed)
Prolonged disconnection may be flagged.
**Q6. What happens if I leave the camera frame briefly?**
Leaving the camera view may trigger a proctoring alert. Repeated or prolonged absence can lead to review or escalation.
**Q7. What happens if someone enters the room during my exam?**
If another person enters the room, it may trigger a **warning or proctoring flag**.
Depending on your exam setup:
* You may receive an **on-screen warning**, or
* The incident may be **flagged for review** by a proctor or exam administrator.
To avoid issues, you must ask the other person to leave the exam environment and take the exam **alone in a private room**.
**Q8. How do I change the language in a proctored assessment?**
To change the language, go to the top-right corner of the onboarding page and click on the language icon. A small menu will appear where you can select your preferred language. Currently, the available language options are English and Spanish.
**Q9. Am I allowed to drink water during the exam?**
Yes, you are allowed to drink water during the exam. Preferably use a transparent water bottle with no content or written materials. Just make sure you remain visible in the camera view while doing so.
**Q10. What happens if I get disconnected during the exam?**
If you experience a disconnection, rejoin immediately using the provided session link and resume from where you left off. To minimize disruptions, we recommend using a stable wired connection if possible, closing unnecessary apps, keeping your device charged, and avoiding network changes mid-session. If you need further guidance, report to the proctor via chat.
**Q11. Can I connect my charger to the laptop during the exam?**
Yes, you can connect your charger to your laptop during the exam. In fact, we recommend keeping your device plugged in throughout the session to avoid any disruptions caused by a low battery or unexpected shutdown. Just make sure that plugging in the charger doesn't cause you to move out of the camera's view or create prolonged movement away from the screen, as this could trigger a flag.
**Q12. What should I do if I get flagged during the exam?**
If you receive a flag during the exam, don't panic. First, try reaching out to the proctor via the chat option to understand what triggered the flag and get guidance. If you believe the flag was raised in error and you haven't violated any rules, simply continue with your exam as normal. Flags are reviewed after the session, and any unintentional triggers are taken into account during the review process. The most important thing is to stay calm, keep your focus, and complete the exam.
***
### **6. Device Permissions**
**Q1. What permissions do I need to allow?**
You must allow:
* **Camera access** – for facial verification and proctoring
* **Microphone access** – for monitoring (if required)
* **Screen access** – for secure assessments
* **Secure Browser permissions** (if applicable)
When prompted by your browser, click **“Allow”**.
**Q2. What if I accidentally denied camera or microphone permissions?**
If you denied permissions:
* Click the **lock icon** in the browser address bar.
* Go to **Site Settings**.
* Set Camera and Microphone to **Allow**.
* Refresh the page.
Complete this before proceeding with verification.
**Q3. Why is screen recording permission required?**
Screen recording permission is required to monitor on-screen activity during the assessment. This helps maintain exam integrity and may be used for session review or auditing, if required by your organization’s proctoring configuration.
**Q4. What if my operating system blocks screen recording permission?**
*On macOS*:
* Go to **System Settings → Privacy & Security → Screen Recording**
* Enable access for **Talview Secure Browser**
* Restart the browser
*On Windows:*
Ensure required permissions (camera, microphone, screen recording)are granted during installation.
***
### **7. Troubleshooting & Support**
**Q1. How can I raise a support ticket?**
To contact support:
* Click the [**Help/Support**](https://talview.freshdesk.com/support/tickets/new) option on the onboarding or assessment page.
* Provide:
* Your registered email ID
* Assessment name
* Detailed description of the issue
* Screenshots (if available)
* Submit the request.
> **Note**: You may also use the support contact information provided in your invitation email.
**Q2. I received a browser or OS compatibility error. What should I do?**
If you see a compatibility error:
* Switch to Chrome, Edge, or Firefox (latest version).
* Update your browser.
* Use a supported operating system.
* Try a different laptop or desktop device.
If you do not have access to a supported device, inform your administrator immediately.
**Q3. What should I do if I continue to face technical issues?**
If troubleshooting does not resolve the issue:
* Contact support immediately.
* Stay logged in until advised otherwise.
* Capture screenshots (if possible).
> **Note**: Early reporting helps minimize disruption and protects your assessment attempt.
**Q4. Will my exam time be compensated if I face technical issues?**
Time adjustments depend on your organization’s policy. Always report issues immediately to ensure they are documented.
**Q5. Can I reschedule my exam due to technical issues?**
Rescheduling is subject to your organization’s policy. Contact your administrator or recruiter for clarification.
***
# Candidate Assessment FAQs
Source: https://docs.talview.com/candidates/assessments/faqs/candidate-assessment-faqs
### Introduction
The **Talview Candidate Platform** helps candidates participate in various evaluation formats - from objective tests and coding challenges to video interviews and AI-led assessments - in a secure, fair, and user-friendly environment.
This FAQ is designed to guide you through the **complete assessment experience**, including how to prepare, what to expect during your test or interview, and how your data is handled. It also covers important topics like **technical readiness**, **proctoring permissions**, **privacy and security**, and **where to get help** if you face any issues during your assessment.
***
### **1. Before You Begin**
**Q1. What technical requirements should I check before starting my assessment?**
Before starting, make sure your setup meets the following requirements:
* **Device:** Laptop or desktop (recommended); mobile access only if the assessment supports it.
* **Browser:** Latest version of **Google Chrome** (preferred), Microsoft Edge, or Firefox.
* **Internet:** Minimum **2 Mbps** stable connectivity.
* **Hardware:** Functioning **camera**, **microphone**, and **speakers/headphones**.
* **Permissions:** Allow access to your camera, microphone, and screen (if requested).
* **Environment:** Quiet, well-lit space with minimal background noise.
💡 *Tip:* You can run a **System Test** from your test invite email to ensure your device meets these requirements.
**Q2. What Are the Different Types of Assessments Talview Supports?**
The different forms of the assessments you can take on Talview include:
* Asynchronous/Automated Video Assessments
* Multiple Choice Video Assessments
* Essay Video Assessments
* Code Video Assessments
* Live Interviews
**Q3. What Are the Pre-Assessment Steps on Talview?**
Before attending your interview, there are a few important points to keep in mind:
1. Test your equipment: Ensure that your microphone and camera are working properly. It's crucial to have functioning audio and video for a smooth interview experience.
2. Check your internet connectivity and speed: Make sure you have a stable internet connection with a minimum speed of 256 Kbps for attending Automated/Asynchronous Video Interviews, Multiple-Choice Video Assessments, Essay Video Assessments, or Code Video Assessments. For Live Interviews, a minimum speed of 1 Mbps is required.
3. Prepare your surroundings: Find a clean and quiet space where you can sit comfortably during the interview. Creating a professional environment will help you make a positive impression.
4. Review the assessment invitation: Take the time to thoroughly read the assessment invitation email. Additionally, it's highly recommended to participate in any practice assessments provided beforehand. Completing the assessment in advance can help you avoid any last-minute technical issues.
Remember, during the interview, try to maintain eye contact by looking into the camera. This will help you establish a stronger connection with the interviewer.
**Q4. Is There a Practice Assessment Option Available on Talview?**
Absolutely! Talview offers a practice video assessment for all proctored video assessments. Upon receiving the invitation email, you can access the practice assessment page using the provided link. This page includes sample questions to familiarize yourself with the assessment process. However, please note that practice assessments are not available for Live Interviews.
**Q5. System Requirements and Tips for a Smooth Talview Experience**
To ensure a seamless experience while attending assessments or interviews on Talview, please follow these steps:
1. **Internet Connection**: Make sure you have an active internet connection with a minimum speed of 256 Kbps for video assessments and 1 Mbps for Live Interviews.
2. **Device Check**: Before starting the assessment, check the functionality of your equipment. If you're using a smartphone, ensure that the front camera is working properly. For laptop or desktop users, verify that the webcam, microphone, and speakers/headphones are in good working condition.
3. **Audio Quality:** If attending the assessment on a laptop or desktop, it is recommended to use a high-quality external microphone. However, the built-in microphone on your laptop can also be used. If using a mobile phone, avoid using the phone's built-in microphone.
4. **Mobile Application:** The Talview mobile application supports Automated/Asynchronous Video Interviews and Multiple-Choice Video Assessments. If you receive a "Not Supported" message or are instructed to write an essay, code test, VEPT, or Versant assessment, please use a laptop or desktop computer.
5. **Supported Browsers:** Talview is compatible with the **latest versions** of Google Chrome, Mozilla Firefox, and Microsoft Edge. Ensure you are using one of these browsers for the best performance.
6. **Practice and Preparation:** Take advantage of the practice assessment and watch the candidate process flow videos provided by Talview. These resources will familiarize you with the assessment format and ensure you are well-prepared.
By following these guidelines, you can optimize your Talview experience and minimize the chances of encountering technical issues during your assessment or interview.
***
### **2. Assessment Experience**
**Q1. Received an Email/SMS for an Assessment on Talview? Not Sure What to Expect?**
If you have received an email from \<[no-reply@org-name.com](mailto:no-reply@org-name.com)> or an SMS pertaining to online assessments or a Live Interview, it signifies the initiation of the interview process for the position you have applied for with the company. It is essential to engage in this process to proceed further in the hiring procedure. Talview serves as an advanced online platform for conducting video-proctored online assessments and live interviews. Renowned employers, educational institutions, training agencies, and more rely on Talview to carry out assessments and interviews for talent acquisition, learning exams, certifications, and other related purposes.
**Q2. What happens if I accidentally close the test window?**
If you close the browser or tab during your assessment:
* Your progress is **auto saved** up to the last completed question or section.
* You can **reopen the test link** and continue as long as the allotted time remains.
* For time-bound or single-attempt tests (like Objective, Coding or Ivy interviews), contact your **recruiter or test administrator** if the session closes unexpectedly.
* If you already reached the **Thank You page**, the assessment is marked complete and the link can't be reused. Contact your **recruiter** for a new invite.
***
**Q3. Will the timer stop if I get disconnected or lose internet?**
No. The timer **continues to run** even if you lose connectivity.
You can resume from where you left off after reconnecting, provided your test time hasn’t expired.
Make sure you use a **stable, uninterrupted internet connection** for the duration of the test.
***
**Q4. Can I take breaks during the test or interview?**
Most assessments are designed to be taken **in one sitting**.
If you need a short break, complete your current section first. The timer will **continue running** even while you’re away.
For longer written or coding assessments, check your **instructions** — some recruiters may allow section-wise breaks.
**Q5. What are the different types of assessments I may encounter on Talview?**
1. **Objective Assessments (MCQ/MCA):**
Multiple-choice or multiple-answer questions with a time limit per question or overall section.
Responses auto-save as you progress.
2. **Asynchronous (Async) Interviews:**
You’ll record video or audio answers to pre-set questions. Each question has a **time limit and allows retries** (as defined by the recruiter).
3. **Ivy AI Interviews:**
Conducted by **Ivy**, Talview’s virtual interviewer, who interacts using **voice**. Your responses are analyzed for communication skills.
4. **Long-Form / Written Assessments:**
Require detailed written responses, essays, or case studies. You can type directly in the editor or upload files in supported formats.
5. **Code Solo (Coding Assessments):**
Real-time coding tasks using supported programming languages. The in-built compiler auto-saves progress.
You can run test cases before submission.
**Q6. What file formats are supported for uploads (case studies or long answers)?**
Supported formats include:
* **Documents:** PDF, DOC, DOCX, PPT
* **Spreadsheets:** XLS, XLSX
* **Images:** JPG, PNG
* **Text files:** TXT
Maximum upload size: **10 MB per file**.
Always check the on-screen instructions for accepted file types.
**Q7. What should I do if my file upload fails?**
If your upload doesn’t complete:
* Check your **internet connection**.
* Ensure the file meets the **format and size limits**.
* Rename the file (avoid special characters).
If the issue continues, refresh the page and try again.
If the problem persists, contact **Talview Support** using the **Help** option in your test window.
**Q8. How does the AI interviewer (Ivy) work?**
**Ivy**, Talview’s AI-powered interviewer, conducts interactive interviews using **voice**.
* Ivy records your responses and evaluates key communication traits like fluency, tone, and relevance.
* It ensures fairness by asking identical questions to all candidates.
* Your recordings and insights are securely shared only with **authorized recruiters and evaluators**.
**Q9. How do I know if my assessment or interview submission was successful?**
You’ll see a **confirmation message** once your responses are submitted.
For asynchronous or written tests, you may also receive an **email confirmation**.
If you’re unsure, reopen your test link - if it shows **“Completed”**, your submission was successful.
**Q10. Can I retake my assessment if something goes wrong?**
Retakes are **not automatic**.
If you face technical issues (power loss, browser crash, etc.), contact your **recruiter or test administrator** immediately.
They can review your logs and reassign the test if permitted.
**Q11. What devices and browsers are supported for Talview assessments?**
You can take assessments on:
* **Desktop/Laptop:** Chrome (recommended), Edge, or Firefox (latest versions)
* **Mobile (if allowed):** Chrome or Safari
Ensure your device has a **working camera, microphone, and stable internet** before beginning.
**Q12. What Should I Do If I Face a Technical Issue During an Assessment or Interview on Talview?**
If you encounter any technical issues during an assessment or interview on Talview, we provide multiple channels to assist you:
Level 1: Detailed [FAQs](https://talview.freshdesk.com/en/support/solutions) - You can find comprehensive answers to common technical queries on our platform.
Level 2: Talview's Technical [Superbot](https://talview.freshdesk.com/en/support/home) (Chatbot) - Our intelligent chatbot is designed to address specific technical concerns and provide instant support.
Level 3: [Ticketing Support](https://talview.freshdesk.com/en/support/tickets/new) - If you require personalized assistance, you can raise a support ticket through our ticketing system. Our dedicated support team will promptly address your concerns.
Level 4: [Phone Support](https://talview.freshdesk.com/en/support/solutions/articles/11000103432-talview-tech-support-phone-numbers) - For urgent technical issues, you can reach out to us directly through our phone support line.
For more information and access to our candidate technical support resources, please visit our Candidate Technical Support Page. We are committed to ensuring a seamless experience for all users on Talview.
***
### **3. Proctoring & Permissions**
**Q1. Is my video or audio being recorded during the assessment?**
Yes, if the assessment is **proctored** or involves an **AI/Async interview**, your **camera, microphone, and/or screen** may be recorded for integrity verification.
Recording starts only after you **grant permission**.
This helps recruiters validate identity and prevent unfair practices.
**Q2. Why am I being asked to allow camera, microphone, or screen access?**
These permissions are used only for:
* **Identity verification** and test monitoring
* **Proctoring** (to ensure fairness and compliance)
Talview **never accesses personal data or files** outside the test environment.
**Q2. What happens if I deny camera or microphone access?**
* For **Objective or Written assessments**: You may proceed if proctoring isn’t mandatory.
* For **Async or Ivy interviews**: Camera/microphone access is **required** to continue.
* For **Proctored tests**: Denying access will **block the test start**.
If you have privacy or hardware concerns, contact your recruiter for alternate arrangements.
***
### **4. Data Sharing, Privacy & Security**
**Q1. What information is shared with the recruiter or employer?**
Recruiters and evaluators can view:
* Your **assessment responses**, scores, and recordings
* **AI evaluation reports** (if configured)
* **Proctoring footage** (video/audio/screen)
* Your **personally identifiable information (PII)** — name, email, candidate ID, and test logs
This data is shared **solely for hiring and evaluation** within your organization’s workflow.
**Q2. How is my data protected on Talview?**
Talview adheres to **global data privacy standards** such as **GDPR**, **SOC 2**, and **ISO 27001**.
Your data is:
* **Encrypted at rest and in transit**
* Accessible only to **authorized users**
* Automatically **deleted after the retention period** defined by your organization
Talview does **not sell, share, or reuse** candidate data for any purpose outside recruitment.
**Q3. Are accommodations available for candidates with disabilities or special needs?**
Yes. Talview and participating organizations support **reasonable accommodations**.
If you require extra time, assistive technology, or a specific setup, inform your **recruiter in advance**.
They can configure your assessment with the appropriate support or alternative arrangements.
**Q4. Can I request deletion of my data before the retention period ends?**
Yes. You can raise a **data deletion request** through your recruiter or email [**privacy@talview.com**](mailto:privacy@talview.com).
Your request will be processed in accordance with your organization’s data policy and legal requirements.
***
### **5. Troubleshooting & Support**
**Q1. My test isn’t loading, or I can’t start it - what should I do?**
Try these steps:
1. Refresh the page or relaunch your browser.
2. Check your camera/microphone permissions.
3. Confirm your internet stability.
4. Use Chrome or Edge on desktop/laptop.
If it still doesn’t load, contact **Talview Support** via the **Help** option on your test page.
**Q2. I was disconnected during a live or Ivy AI interview. Can I rejoin?**
Yes, if the session is still active. Reopen your **interview link** to rejoin.
If the session has ended, contact your **recruiter** to reschedule or continue from a new slot.
**Q3**. **What Can I Expect After the Assessment or Interview? How Will I Be Notified of the Next Steps?**
After completing the assessment or interview, the recruiter from the employer will be responsible for communicating the status and next steps to you. The recruiter will provide you with the necessary updates and information.
Please note that Talview does not have access to your assessment or interview results. Therefore, we kindly request that you refrain from contacting the Talview team regarding the assessment or interview results.
# How to attempt a Coding Assessment?
Source: https://docs.talview.com/candidates/assessments/how-to/how-to-attempt-a-coding-assessment
Talview coding assessments enables candidates to demonstrate programming skills through secure, proctored online tests with support for over 80 languages via integrated editors like Code-Solo and Code-Pair.
This article provides a step-by-step guide for candidates on attemping a **Coding assessment.**
***
### What is a Coding Assessment?
Coding assessments evaluates problem-solving and coding proficiency using browser-based editors with real-time execution, autoscoring, and proctoring for integrity. Formats include solo timed challenges or collaborative pair sessions, featuring syntax highlighting, test case runners, and plagiarism checks.
* **Code-Solo:** A tool designed to evaluate candidates' coding skills in a real-world development setting by providing auto-scored tasks and test cases. It serves as a valuable resource for screening candidates in the initial stages of the hiring process.
* **Code-Pair:** Offers collaborative live coding interviews with integrated audio and video calling capabilities. It provides a platform to evaluate coding skills in real-time during live interviews.
***
### Prerequisites
Before starting the assessment, ensure that you have:
* A **stable** internet connection.
* A computer or laptop with a **webcam and microphone**.
* Access to the **assessment link** provided by the recruiter.
* A **compatible** web browser (Chrome or Edge is recommended).
***
### Steps to Take a Coding Assessment
**1. Access the Assessment Link**
* You will receive an invitation email with an assessment link to access the coding assessment.
* View your assessment details and click on “**Start Assessment”**, which will redirect you to the **Talview candidate portal**.
* Enter the exact same email address to which the invite was sent to you, to receive your one-time confirmation code (OTP).
* Click **Request OTP** to receive your unique confirmation code in your inbox.
* Enter the *8-digit confirmation code*, sent to your email to continue your assessment.
**2. Grant Permissions**
> **Note:** If you are asked to give consent or capture photo then proceed with these steps.
* Agree to our *Terms & Conditions and Privacy Policy* to keep your experience secure.
* Consent to face capture and session recording, ensuring assessment integrity.
* Click **Continue** to proceed after accepting required.
**3. Face Capture**
* Position your face and hold steady to **Capture** your photo for a secure face verification.
**4. Start the Assessment**
* Read the Assessment instructions carefully and click **Proceed.**
* Read the question carefully and answer, select your programming language (e.g., Python, Java) and review the problem statement, inputs, outputs, and constraints.
* Then click on **Run** to test outputs - Green for pass, red for fail and debug errors iteratively.
**5. Assessment Submission and Feedback**
* Once all tests pass, click on **Submit**; confirm to finalize your assessment.
* Provide *feedback* by rating your assessment experience and click on **Submit.**
**Additional Tips:**
* Ensure your device is fully charged or plugged in to avoid interruptions during the test.
* Close all unnecessary applications and browser tabs to optimize your system's performance and prevent distractions.
* Use headphones if in a noisy environment to stay focused and avoid background noise being picked up by the microphone.
* Avoid switching tabs or windows during the assessment to prevent proctoring flags and potential disqualification.
* Read each problem statement carefully before coding and plan your approach to manage time effectively.
# What to expect after completing your assessment?
Source: https://docs.talview.com/candidates/assessments/how-to/what-to-expect-after-completing-your-assessment
This article outlines the standard process candidates experience post-assessment submission, ensuring transparency on confirmation, results, and next steps.
***
### Submission Confirmation
Upon submitting your assessment, the Talview platform immediately displays a confirmation screen, verifying that your responses have been successfully recorded and sent to the evaluators. If no confirmation appears due to technical issues, contact your recruiter or Talview support immediately to verify status.
***
### Results Processing
The hiring team or exam organizer will review your submission, and they may share an overall update or outcome with you if their process allows it.
If you’d like feedback, reach out to your recruiter or the contact person who invited you to take the assessment.
***
### Response Access
Your assessment responses remain securely stored and are not provided to candidates; only aggregated performance insights may be shared through your recruiter. For feedback, reach out to the hiring team post-evaluation.
***
### Next Steps and Communication
Monitor your email for updates on interview scheduling or status notifications. Recruiters handle all follow-ups, so ensure your contact details are correct. If no communication arrives within the expected timeline, politely follow up with your point of contact.
**Additional Tips:**
* Keep an eye on your email (including spam/junk) for any communication from the recruiter or exam organizer after your assessment.
* Do not uninstall the Talview app or clear important browser data until your process is complete, in case a retake or additional verification is requested.
* Make a note of the date and time you completed the assessment so you can reference it when following up with the recruiter.
* If you faced technical issues during the test, document them (screenshots, error messages, time of occurrence) and share them promptly with your recruiter or support.
* Avoid discussing specific questions or test content publicly or with other candidates, as this may violate the assessment’s integrity and terms.
# Who to contact if you don’t receive a status update?
Source: https://docs.talview.com/candidates/assessments/how-to/who-to-contact-if-you-dont-receive-a-status-update
After completing your Talview Assessment, you may expect a status update from the organization within a specified timeframe, such as 3-7 business days. If no update arrives via email, delays can stem from internal review processes, high candidate volumes, or workflow configurations set by your recruiter.
This article details the steps for candidates to resolve missing status updates efficiently, while respecting organizational review processes.
***
### Check Your Assessment Status
Check your inbox, spam, and junk folders for automated notifications, which often include your assessment ID, submission confirmation, and expected next steps. Status delays commonly arise from high candidate volumes, internal evaluation queues managed by the organization, or customized workflow settings.
***
### Contact Your Recruiter or Hiring Manager
Your recruiter or hiring manager remain the primary point of contact, as they are in control of the status notifications.
* Use the email address provided in your initial assessment invitation.
* Reference your full name, assessment ID, and completion date in the subject line, e.g., "Status Update Request - Assessment ID \[ID] - \[Your Name]".
* Politely request an update and mention the expected timeline if communicated.
***
### Talview Support for Technical Issues
Contact Talview support only for platform specific problems, such as login failures or confirmation discrepancies and **not for status inquiries**.
* For assistance, submit a support ticket at ([https://talview.freshdesk.com/support/tickets/new](https://talview.freshdesk.com/support/tickets/new)) and include your assessment details.
* Use the in-app *"Contact Support"* feature if available during your session.
**Best Practices for Follow-Ups**
* Wait at least 3-5 business days after completion before following up, unless a specific timeline was provided in your invitation. Send emails during standard business hours (e.g., 9 AM - 5 PM in the recruiter's time zone.
* If no reply after 10 business days, escalate politely to the hiring manager (if contact info available) or check the company's careers page for alternative support.
# Why we use Proctoring and how it works
Source: https://docs.talview.com/candidates/assessments/how-to/why-we-use-proctoring-and-how-it-works
Remote assessments have become essential for hiring and certification processes. **Talview’s Assessment module** uses proctoring technology to ensure these exams are conducted fairly, securely, and with integrity.
This article explains why proctoring is important, how it works, and what candidates can expect during the assessments.
***
### Why we use Proctoring in Assessments?
Proctoring helps **maintain the integrity of the assessment process** by verifying the candidate's identity and monitoring the exam environment to prevent cheating or any unauthorized activity. This is crucial because remote assessments are vulnerable to dishonest behaviors such as **impersonation, use of unauthorized devices, or accessing external help**.
By using advanced proctoring technology, we create a secure and trusted testing environment where candidates can showcase their true abilities without concerns of unfair advantage by others. Proctoring also helps clients and organizations who use Talview assessments to trust the results, enabling them to make informed decisions during hiring or certification processes. It brings the reliability of in-person exams to remote assessments, offering convenience without compromising on exam security.
***
### How Does Proctoring Work?
Our proctoring system combines artificial intelligence (AI) and, where needed, live human oversight to monitor assessments comprehensively.
Here is how it works from a candidate’s perspective:
**✔️Identity Verification**
Before starting the exam, candidates must verify their identity using facial recognition and other security checks. This ensures the person taking the assessment is the registered candidate and prevents impersonation.
**✔️Secure Exam Environment**
When the exam begins, a secure browser environment is activated that restricts the candidate’s ability to switch tabs, open other applications, or copy and paste content. This browser lockdown protects exam content and prevents access to unauthorized resources.
**✔️Real-Time Monitoring**
*AI*-powered algorithms, including our patented **AI Proctoring Agent, Alvy;** continuously analyze video, audio, and screen activity to detect suspicious behaviors such as off-screen glances, whispering, multiple faces in frame, background voices, or browser window changes.
The system flags anomalies like *unusual eye movements, device tampering, or unauthorized software access in real-time for review*. This multi-modal monitoring ensures exam integrity by identifying patterns of potential cheating without relying solely on rigid rules.
**✔️Environment Checks**
Candidates may be asked to perform environment scans like showing their workspace or doing a **360-degree room scan** to ensure no prohibited materials or devices are present.
**✔️Flagging and Intervention**
If the AI detects any irregularities, it automatically flags these for review.
In setups with **live proctoring**, human proctors can observe the candidate throughout and intervene immediately if they spot any issues.
**✔️Record & Review Option**
In some cases, exams are recorded in full to allow thorough post-exam review (Playback session) by proctors or clients. This ensures all suspicions are carefully checked before finalizing results.
***
### Understanding Proctoring Flags
Our proctoring system may sometimes raise “flags” during your assessment when it notices something unusual in your test environment. These flags simply mark moments for review to help keep the exam fair and consistent for all candidates.
*Common flags include:*
* Multiple faces detected in the camera view, suggesting possible assistance from others
* Frequent looking away from the screen or extended absence from the webcam view
* Background noises or conversations detected during the exam
* Attempts to switch browser tabs or use unauthorized applications
* Sudden changes in lighting or environment, which may indicate suspicious activity
It’s important to understand that a flag does not automatically mean misconduct. Flags are signals for review, and all flagged sessions are carefully analyzed by proctors or AI systems before any final decisions are made.
Candidates are encouraged to remain calm, follow all instructions, and maintain exam discipline to minimize the chances of being flagged. This transparent process helps create a trustworthy and fair exam environment for everyone.
**Preparing for Your Proctored Assessment**
Proper preparation ensures a smooth and successful proctored experience. Review these steps to set up your environment and system in advance:
* Test your webcam, microphone, and internet connection before you begin your assessment.
* Choose a quiet, private room with consistent lighting and no prohibited items like notes or extra devices.
* Close all unnecessary applications and disable notifications to avoid accidental tab switches.
* Have your government issued ID ready for identity verification at the start.
* Charge your device and use a stable power source to prevent interruptions.
Following these guidelines reduces technical issues and flags, allowing you to focus on performing your best during the assessment.
# Why am I being asked to provide a photo ID?
Source: https://docs.talview.com/candidates/assessments/proctoring/diagnostics/why-am-I-being-asked-to-provide-a-photo-id
During onboarding or before starting an exam or interview, Talview may require a photo ID for identity verification. Having an accepted photo ID ready helps prevent delays, verification failures, or interruptions during your session.
Read below to understand which photo IDs are accepted, what to do if you don’t have one, and how to prepare your ID correctly.
## ✅Accepted Types of Photo ID
The following photo IDs are commonly accepted for verification. Acceptance may vary based on your exam or interview sponsor.
| Type of ID | Description |
| :----------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Government-issued Photo ID** | Includes passports, national identity cards, voter IDs, PAN cards, Aadhaar cards (India), and driver’s licenses that display your photo and name. |
| **Student ID Card** | Issued by an educational institution and must clearly show your name, photo, and identifying details. |
| **Residency Card** | Permanent or temporary residency cards that clearly display your identity information. |
| **Employee ID Card** | Employer-issued ID that includes your name and photograph. |
| **Military ID** | Photo identification issued to active or retired military personnel. |
> **Note:** Government-issued photo IDs are the most widely accepted and recommended for faster verification.
## 🛠Common Troubleshooting Steps
| What might be wrong | **What to Do** |
| :------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------- |
| **Lost or Misplaced ID** | Contact your **exam administrator** immediately. They may allow a temporary or alternative ID, or guide you on rescheduling your session. |
| **Expired ID** | Renew your ID before the exam if possible. Some organizers may temporarily accept expired IDs with proof of renewal—confirm this first. |
| **Never Had a Photo ID** | You’ll need to obtain one before your exam. Most organizations accept only verified government-issued IDs. |
| **Name Mismatch (ID vs Registration)** | Inform your recruiter or Talview Support before the exam and provide supporting proof (e.g., name change document). |
## 🪪Before You Submit Your ID
Make sure your photo ID:
* Is valid and not expired.
* Clearly displays your photo, full name, and ID number.
* Matches the name used during exam or interview registration.
* Is original and undamaged (digital copies or screenshots may not be accepted).
# Why is my verification code not showing up?
Source: https://docs.talview.com/candidates/assessments/proctoring/diagnostics/why-is-my-verification-code-not-showing-up
When you register for a test through Talview, you'll receive an email containing both a test link and a verification code. This code is required to access your test and complete the onboarding process. If you don't see the verification code in your email, this guide will help you resolve the issue.
This article helps attendees troubleshoot and resolve issues when verification codes fail to appear during the onboarding process.
## 🔎 Troubleshooting Common Issues
| **What Might Be Wrong** | **How to Fix It** |
| :-------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------- |
| The email hasn't arrived yet | Wait 5-10 minutes and check your inbox again. Email delivery can be delayed depending on network or provider conditions. |
| Email is in spam/junk/promotions folder | Search your spam, junk, or promotions folder for emails from Talview. |
| Checking the wrong email address | Confirm you are checking the email address you used to register for the test. If you have multiple accounts, check each one. |
| Email was deleted accidentally | Check your trash or deleted items folder for Talview emails. Restore the email if found or request a new code from your administrator if not. |
| Verification code expired | Verification codes can expire if not used promptly. Contact your test administrator to request a fresh code if needed. |
| Inbox is full or restricted | Make sure your inbox isn’t over its storage limit or restricted from receiving new emails. Clear space if needed and ask for the email to be resent. |
**Additional Tips:**
* Try accessing your email from a different device or browser if the email isn't loading properly
* Screenshot or copy the verification code immediately when you receive it for easy reference
* Contact your test administrator promptly if you don't receive the email within 15 minutes of registration
# Why is the QR code not scanning?
Source: https://docs.talview.com/candidates/assessments/proctoring/diagnostics/why-is-the-qr-code-not-scanning
During attendee onboarding, you may need to scan a QR code displayed on your **laptop or desktop** (primary device), to connect your **mobile phone** as a secondary camera.
This article helps attendees resolve QR code scanning issues when setting up their secondary device.
## 🔎 Troubleshooting Common Issues
| What might be wrong | How to fix it |
| :------------------------------------------- | :---------------------------------------------------------------------------------------- |
| Mobile camera lens is dirty or smudged | Clean the camera lens using a soft, lint-free cloth to remove dust or fingerprints. |
| Primary device screen brightness is too low | Increase the brightness on your laptop or desktop so the QR code is clearly visible. |
| Poor lighting in your environment | Ensure the room is well lit so your mobile camera can capture the QR code clearly. |
| QR scanning is disabled in the camera app | Open your phone’s camera settings and enable the QR code scanning option. |
| Mobile camera is not focusing | Hold your phone steady about 6–8 inches from the screen and allow it to auto-focus. |
| Another app is using the mobile camera | Close background apps that may be accessing the camera (for example, video calling apps). |
| QR code is blurred or obstructed | Make sure the QR code is fully visible, unobstructed, and the screen is not damaged. |
| Device does not support built-in QR scanning | Install a trusted third-party QR code scanner app from your app store. |
**Additional Tips:**
* Restart your mobile device if the issue persists, as this can resolve temporary software glitches affecting the camera functionality.
* Use landscape mode when positioning your phone after scanning to provide a wider viewing angle for the secondary camera feed.
* If the issue continues after troubleshooting, try switching to a different mobile device and attempt the QR code scan again to determine if the problem is device specific.
# How to Install Talview Secure Browser on Mac
Source: https://docs.talview.com/candidates/assessments/proctoring/how-to/how-to-install-talview-secure-browser-on-mac
The **Talview Secure Browser (TSB)** provides a secure, controlled environment for online assessments by restricting access to unauthorized applications and ensuring test integrity. If the Secure Browser isn’t installed properly, candidates may face issues launching or attending exams. This guide explains how to download, install, and troubleshoot TSB on macOS devices.
## Where to Download
You can download the official Talview Secure Browser from the following source:
🔗 [Download Secure Browser for macOS (.dmg)](https://pages.talview.com/securebrowser/)
* Ensure you download the macOS `.dmg` version.
* TSB is also available for Windows via the Windows Store if supported in your region.
* Avoid using third-party or copied installers.
**Secure Browser Availability**
* Supported OS: Windows, macOS
* Not supported on Linux — Linux users must use standard browser-based assessments (non-SB mode).
## How to Install the Secure Browser
1. Download the `.dmg` file from the official Talview link.
2. Open the `.dmg` file and drag the Talview Secure Browser into your Applications folder.
3. Launch the Secure Browser and allow any permission prompts for **Camera, Microphone, and Screen Recording**.
4. Open your assessment link (from your email) within the Secure Browser to start the test.
If your device is organization-managed, coordinate with your IT team to allow installation and permissions.
Admin privileges are required to install or auto-update the Secure Browser.
## Granting Device Permissions (macOS)
The Secure Browser requires permission to access **Camera, Microphone, and Screen Recording**.
1. Open **System Settings → Privacy & Security → Camera / Microphone / Screen Recording**.
2. Turn On access for **Talview Secure Browser**.
3. Restart the browser and reattempt the test.
Failure to grant permissions will prevent exams from launching successfully.
## Device and Network Prerequisites
### Minimum System Requirements for Mac
| Component | Minimum Requirement | Recommended Specification |
| :--------------- | :------------------------------------- | :----------------------------------- |
| Operating System | macOS 12.6.7+ | Latest macOS build |
| RAM | 4 GB (2 GB free) | 8 GB (4 GB free) |
| Processor | Apple M1 2.0 GHz+ | Apple M1+ 2.5 GHz+ |
| Graphics | 512 MB internal | 1 GB internal / 1.5 GB external |
| Disk Space | 10 GB free | 20 GB free |
| Camera & Mic | HD webcam (15fps, 320×240), microphone | Full HD webcam, noise-cancelling mic |
| CPU Idle Usage | Below 30% before launch | Below 15% for smooth proctoring |
| Power Backup | Recommended | UPS for extended live proctoring |
### Network & Bandwidth Requirements
| Use Case | Low Bandwidth Mode | Minimum Requirement | Recommended Requirement |
| :------------------------- | :----------------- | :------------------ | :---------------------- |
| Recorded / Live Proctoring | Lesser FPS | 200 Kbps | 5 Mbps |
| Secondary Camera (if used) | — | 200 Kbps | 5 Mbps |
| Latency | — | — | \< 80ms |
| Jitter | — | — | \< 20ms |
| Packet Loss | — | — | 0% |
| Connection Type | Wi-Fi acceptable | Wi-Fi acceptable | Ethernet preferred |
> Disable VPNs and background downloads.
## How to Exit the Secure Browser
After submitting your test:
* **macOS:** Press Command (⌘) + Q to exit the Secure Browser.
If you run into issues and need to close the Secure Browser, you can reopen the assessment using the same code you received in the email.
## Common Error States and How to Resolve
| Issue / Error Message | Possible Cause | Resolution |
| :------------------------------ | :------------------------------------------- | :-------------------------------------------------- |
| Installer won’t open | Gatekeeper blocking app | Right-click → Open, confirm prompt |
| SB crashes mid-test | High CPU/RAM usage, background apps | Close unnecessary apps, restart system, relaunch SB |
| Blank Screen / Launch Failure | Poor network, VPN, blocked ports | Use Ethernet, disable VPN, retry |
| Update Required | Outdated Secure Browser | Click “Update” when prompted |
| Restricted Software Detected | Unsupported apps (Zoom, OBS, screen capture) | Close blacklisted apps and relaunch SB |
| Multiple Monitors Detected | More than one display connected | Disconnect extra monitors, restart SB |
| Screen Recording Detected | Active screen capture / recording tool | Close recording tools, restart SB |
| SB won’t install on managed Mac | Admin lockout or group policy | Use personal device or contact IT team |
## Best Practices for Smooth Assessments
* Restart your Mac and close unnecessary apps (Zoom, Teams, browsers) before launching SB.
* Use a wired (Ethernet) connection for stable video streaming.
* Secure Browser checks for updates automatically at each launch.
* To ensure a smooth process, make sure to check [Pre-Requisites for Online Assessment : Support Center](https://talview.freshdesk.com/support/solutions/articles/11000129948-pre-requisites-for-online-assessments) before your session.
* Candidates should launch SB at least **15–20 minutes** before the scheduled test time.
By ensuring your device meets all prerequisites and following the above installation and troubleshooting steps, you can avoid last-minute technical issues and have a seamless testing experience on **Talview Secure Browser for macOS**.
# How to Install Talview Secure Browser on Windows
Source: https://docs.talview.com/candidates/assessments/proctoring/how-to/how-to-install-talview-secure-browser-on-windows
The **Talview Secure Browser (TSB)** provides a controlled, secure environment for online assessments by restricting access to unauthorized applications and ensuring test integrity.
If the Secure Browser isn’t installed properly, candidates may face issues launching or attending exams. This guide explains how to download, install, and troubleshoot TSB on **Windows devices**.
## **Where to Download**
* Secure Browser is available through the **Windows Store.**\
Ensure you download the official Talview Secure Browser here:
🔗 [**Talview Secure Browser – Microsoft Store**](https://apps.microsoft.com/detail/9ncq0q33kl48?hl=en-US\&gl=IN)
* **Installation Steps (Windows Store):**
1. Click **Download** on the Microsoft Store page.
2. Once the download completes, a file will be generated in your default download location.
3. **Double-click** the downloaded file to launch the installer.
4. Follow the on-screen instructions to complete **installation.**
If the app is not available in the Windows Store, you can download the `.exe` installer from the official Talview link:
🔗 [**Download Secure Browser (.exe) for Windows**](https://pages.talview.com/securebrowser/index.html)
Always ensure you download the version specific to Windows and avoid third-party or copied installers to prevent errors or security issues.
**Secure Browser Availability**
* Supported OS: Windows, macOS
* **Not supported on Linux** - Linux users must use standard browser-based assessments (non-SB mode).
## How to Install the Secure Browser
1. Download the official Talview Secure Browser from Windows Store.
2. Right-click the downloaded installer → select **“Run as Administrator**.”
3. Follow the on-screen instructions to complete setup.
4. Once installed, the Talview Secure Browser icon will appear on your Desktop or Start Menu.
5. Launch the Secure Browser and allow any permission prompts for Camera, Microphone, and Screen Recording.
6. Open your **assessment link** (from your email) within the Secure Browser to start the test.
If your device is organization-managed, coordinate with your IT team to allow installation and permissions.
**Admin privileges** are required to install or auto-update the Secure Browser.
### **Granting Device Permissions (Windows)**
* The Secure Browser requires permission to access Camera, Microphone, and Screen Recording.
Failure to grant permissions will prevent exams from launching successfully.
## **Device and Network Prerequisites**
### **Minimum System Requirements for Windows**
| **Component** | **Minimum Requirement** | **Recommended Specification** |
| :------------------- | :---------------------------------------- | :----------------------------------- |
| **Operating System** | Windows 10 or 11 | Latest Windows 11 build |
| **RAM** | 4 GB (2 GB free) | 8 GB (4 GB free) |
| **Processor** | Intel Core i3 (10th Gen+) or AMD Ryzen 3 | Intel i7+ or Ryzen 5+ |
| **Graphics** | 512 MB internal GPU | 1 GB dedicated GPU |
| **Disk Space** | 10 GB free | 20 GB free |
| **Free CPU Cores** | 2 cores available | 3–4 cores available |
| **Camera & Mic** | HD webcam (15fps, 320×240) and microphone | Full HD webcam, noise-cancelling mic |
| **CPU Idle Usage** | Below 30% before launch | Below 15% for smooth proctoring |
### **Network & Bandwidth Requirements for Windows**
| **Use Case** | **Low Bandwidth Mode (Lesser FPS)** | **Minimum Requirement** | **Recommended Requirement** |
| :----------------------------- | :---------------------------------- | :---------------------- | :-------------------------- |
| **Recorded / Live Proctoring** | 200 Kbps | 512 Kbps | 5 Mbps |
| **Secondary Camera (if used)** | 200 Kbps | 512 Kbps | 5 Mbps |
| **Latency** | — | \< 150ms | \< 80ms |
| **Jitter** | — | \< 30ms | \< 20ms |
| **Packet Loss** | — | \< 1% | 0% |
| **Connection Type** | Wi-Fi acceptable | Wi-Fi acceptable | Ethernet preferred |
> Disable VPNs and background downloads.
## **How to Exit the Secure Browser**
After submitting your test:
* Click the **‘Quit’ (Power) icon** in the bottom-right corner, o
* Press **Ctrl + Q** on your keyboard.
This will safely close the Secure Browser and end your session.
## **Common Error States and How to Resolve**
| **Issue / Error Message** | **Possible Cause** | **Resolution** |
| :---------------------------------------------- | :-------------------------------------------- | :----------------------------------------------------------------------------------------------------------------------- |
| **Installer doesn’t open** | Installer blocked by Windows Defender | Right-click installer → **Run as Administrator** |
| **Installation blocked by antivirus/firewall** | Security software interference | Temporarily disable firewall via **Control Panel → System and Security → Windows Defender Firewall → Turn off firewall** |
| **Update Required** | Outdated Secure Browser | Click **“Update”** when prompted to install latest version |
| **Resolution for Restricted Software Detected** | Unsupported apps (e.g., Zoom, OBS) running | Close blacklisted apps and relaunch Secure Browser. Disable setting to run applications in background |
| **Multiple Monitors Detected** | More than one display connected | Disconnect extra monitors and restart browser |
| **Screen Recording Detected** | Recording or screenshot tool active | Close screen recording software and restart Secure Browser |
| **Blank Screen / Launch Failure** | Poor network or blocked ports | Restart router, disable VPNs, retry with Ethernet |
| **SB crashes mid-test** | Insufficient resources or restricted software | Restart device, close apps, ensure at least **2 GB free RAM** |
| **SB won’t install on school/work laptop** | Admin lockout or group policy | Use **personal device** or contact your IT team |
> 🆘 **Still stuck?**
>
> Re-download TSB from the official link, restart your computer, and relaunch the exam.
>
> If issues persist, Contact [Talview Support](https://certification.talview.com/support/tickets/new) with a screenshot and your registered email ID.
## **Best Practices for Smooth Assessments**
* Restart your system and close unnecessary apps (Zoom, Teams, browsers) before launching Secure Browser.
* Use a **wired (Ethernet)** connection for stable video streaming.
* Checks for updates automatically at every launch.
* Download and install the latest version before the test begins.
* To ensure a smooth process, make sure to check [Pre-Requisites for Online Assessment : Support Center](https://talview.freshdesk.com/support/solutions/articles/11000129948-pre-requisites-for-online-assessments) before your session.
* Candidates should launch SB at least 15–20 minutes before their scheduled test time.
By ensuring your device meets all prerequisites and following the above installation and troubleshooting steps, you can avoid last-minute technical issues and have a seamless testing experience on Talview Secure Browser for Windows.
# Welcome, Candidates & Learners 👋
Source: https://docs.talview.com/candidates/getting-started
Find everything you need to successfully take interviews and exams on Talview here below
Step-by-step guide to start and complete your online proctored exam.
Install and launch the Secure Browser to take your exam without issues.
Instructions to join your scheduled interview, including audio/video setup.
How to pay for, schedule, and confirm your exam slot.
***
### System Compatibility
Check whether your computer, browser, and internet setup are ready for Talview
***
# Candidate did not join the session - what to do?
Source: https://docs.talview.com/candidates/interviews/diagnostics/candidate-did-not-join-the-session-what-to-do
If the interview screen shows as that the **candidate didn’t join your scheduled session**, it means the participant has not accessed the interview or assessment platform. This can cause delays or interruptions. Here’s how to troubleshoot and resolve the issue.
## Troubleshooting Common Issues
| What Might Be Wrong? | What You Can Do |
| :------------------------------------------------------------------ | :---------------------------------------------------------------------------------------------------------------------------------------- |
| The candidate may have technical difficulties joining the session. | Ask them to restart their device and try joining again. Confirm they are using the compatible browser. |
| Candidate facing network connectivity problems | Confirm they have a stable internet connection. Suggest switching to another network if possible. |
| The session started before the candidate was ready or logged in | Wait a few minutes for the candidate to join. Communicate via phone or email to confirm their status. |
| Incorrect or expired invite link or session credentials | Verify and resend the correct invite link and credentials. Double-check the candidate’s email address. |
| Scheduled time or time zone confusion | Confirm the session time and time zone with the candidate. Reschedule if needed. |
| Candidate’s device or browser security settings blocking access | Ask them to disable firewall, VPN, or restrictive browser settings temporarily. Ensure permissions for webcam and microphone are granted. |
| Email ID used to send invite is incorrect | Double-check the invite was sent to the correct email ID and resend if needed. |
| Candidate has hardware issues like webcam or microphone malfunction | Suggest they test their hardware or try joining from a different device. |
## Checklist before the exam
* Allow a short waiting window for candidates to resolve last-minute issues.
* Follow your organization’s guidelines for no-shows or rescheduling.
* Always use recommended devices, browsers, and a strong internet connection.
***
## Additional Troubleshooting Steps
* Confirm the candidate received the correct invite link and session details.
* Ensure their system meets Talview’s technical requirements.
* Ask them to clear browser cache and cookies.
* Suggest disabling VPNs or proxy servers temporarily.
* Ask them to restart their device before joining.
* If the issue persists, reschedule in coordination with Talview support.
# Candidate Interview Link Not Working or Expired- Troubleshooting Guide
Source: https://docs.talview.com/candidates/interviews/diagnostics/candidate-interview-link-not-working-or-expired-troubleshooting-guide
If you are unable to access your interview because the link provided is not working or shows as expired, this guide will help you understand common reasons and how to resolve the issue quickly.
## Troubleshooting Issues
| **Possible Reasons** | **How to Fix It** |
| :------------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------- |
| Interview link has expired | Check the scheduled date/time of your interview. Contact your recruiter to request a renewed link. |
| Incorrect or wrong link received | Verify that the link you received matches the latest invitation. Ask your recruiter to resend the correct link if needed. |
| Account locked or login failure | If you’re locked out after multiple failed login attempts, wait a few minutes before retrying. |
| Use “Forgot Password” to reset credentials if necessary. | |
| Unsupported or outdated browser/device | Use an updated browser (Chrome or Edge recommended). Try joining from another device (laptop preferred). |
| Network restrictions such as VPN/firewall | Disable VPNs or proxies. Update firewall/antivirus settings to allow the interview platform. |
| Platform downtime or technical issues | Check with your recruiter or Talview support if the issue persists for multiple candidates, or if there is scheduled maintenance. |
## Checklist Before the Interview
Make sure you:
* Have the correct and latest interview link from your recruiter.
* Join within the scheduled date and time.
* Use an updated and supported browser.
* Ensure a stable internet connection (avoid VPNs or proxies).
* Allow the interview platform through your firewall/antivirus.
* Test on an alternative browser or device if required.
## Additional Troubleshooting
1. Clear your browser cache and cookies.
2. Open the link in **incognito/private mode**.
3. Restart your device and try again.
4. Verify your device’s **date and time settings** are correct.
5. Disable interfering extensions (e.g., ad blockers).
# CodeJam Not Working in Talview Live Interview - How to Fix?
Source: https://docs.talview.com/candidates/interviews/diagnostics/codejam-not-working-in-talview-live-interview-steps-to-fix
Talview’s **CodeJam** in Interview Rooms enables real-time coding collaboration between candidates and interviewers. At times, participants may face technical issues that disrupt the flow. This guide outlines common problems, causes, and solutions to help both interviewers and candidates quickly resolve them.
## Common Issues and Fixes
| What might be wrong | What to do? |
| :------------------------------- | :-------------------------------------------------------------------------------------------------------- |
| CodeJam icon/button not visible | Refresh the page. Clear cache or try incognito mode. |
| Code won’t run | Confirm Code execution is enabled, and choose a supported programming language, Check internet stability. |
| Collaboration lags/sync issues | Switch to a stable/wired connection. Close bandwidth-heavy apps, Refresh CodeJam to resync. |
| Can’t switch back to video | Use “Exit CodeJam” button or Refresh the page. |
| Video/audio freezes while coding | Close unused apps/tabs and ensure device meets system requirements. |
## Additional Troubleshooting Tips
* Browser Compatibility: For best results, use desktop/laptop with updated Chrome, Firefox, or Edge. Mobile devices may have limited functionality.
* Stable Internet: A reliable high-speed connection ensures smooth code execution and collaboration.
* Permissions Matter: Interviewers activate CodeJam and control candidate permissions. Communicate if you can’t edit or execute code.
* Refresh First: Many interface glitches or sync errors can be resolved by refreshing the page.
* Device Readiness: Restart your system before the session to clear temporary glitches.
## Best Practices to Prevent Issues
* Join the session 5–10 minutes early to test CodeJam functionality.
* Close background apps that use heavy bandwidth (e.g., streaming, downloads).
* Use a wired internet connection when possible.
* Test your mic, webcam, and system performance in advance.
## Need Help?
If issues persist after following these steps, contact **Talview Support** for live assistance:
Talview’s support team will help troubleshoot platform-specific problems and ensure your session runs smoothly.
# Evaluator Didn’t Join the Session : What to do ?
Source: https://docs.talview.com/candidates/interviews/diagnostics/evaluator-did-not-join-the-session-what-to-do
If you see a message that the **evaluator didn’t join your scheduled session**, it means the interviewer or proctor has not accessed the platform. This may cause delays in starting your interview or assessment. Here’s what you can do.
## Troubleshooting Common Issues
| What Might Be Wrong? | What You Can Do |
| :---------------------------------------------------------------------- | :-------------------------------------------------------------------------------------------------- |
| The evaluator may be facing technical difficulties joining the session. | Wait a few minutes and stay logged in. The evaluator may rejoin after restarting their device. |
| Evaluator has network connectivity problems | Allow some time for them to resolve it. Stay on the platform so you don’t miss when they join. |
| The session started before the evaluator was ready or logged in | Stay connected and check for updates from the recruiter. |
| Incorrect or expired invite link or session credentials | Contact your recruiter or Talview coordinator to confirm the correct session details. |
| Scheduled time or time zone confusion | Double-check the scheduled session time and your time zone. Reach out to your recruiter if unclear. |
| Evaluator’s device or browser security settings blocking access | The evaluator may be fixing this; wait for their confirmation. |
| Evaluator joined a different session | Stay logged in while the issue is clarified by your recruiter. |
| Evaluator has hardware issues like webcam or microphone malfunction | Wait while they troubleshoot, and keep communication open with the recruiter. |
## Things to Keep in Mind
* Arrive on time and stay patient while the evaluator joins.
* Follow instructions from your recruiter or Talview coordinator.
* Maintain readiness with a working device, browser, and stable internet connection.
## Additional Troubleshooting Steps
* Confirm your invite link and session details are correct.
* Keep your system ready and meet all technical requirements.
* Stay connected to the platform for updates.
* Reach out to your recruiter if the evaluator doesn’t join after waiting.
* If the session cannot continue, your recruiter will help reschedule.
# Fix live interviews (Interview rooms) from crashing or freezing
Source: https://docs.talview.com/candidates/interviews/diagnostics/how-to-fix-live-interviews-from-crashing-or-freezing
We know how frustrating it can be when the Live interview (Interview Rooms) freezes or crashes during your session. Don’t worry—this guide will help you quickly identify what might be causing the issue and get you back to a smooth, hassle-free interview experience.
## Troubleshooting Common Issues
| What causes the issue ? | **How to Fix It ?** |
| :-------------------------------------------- | :-------------------------------------------------------------------------------------------------- |
| Unstable or slow internet | Connect to a stable, high-speed Wi-Fi network. |
| Outdated or unsupported browser | Use the latest version of Google Chrome or Mozilla Firefox for the best experience. |
| Too many open apps or tabs | Close all non-essential apps and tabs. A quick restart before your session can improve performance. |
| Browser cache or cookies interfering | Clear your browser cache and cookies, then reload the Interview Room page. |
| Heavy background software running | Pause or exit apps like video editors, streaming services, or development tools. |
| Browser extensions blocking features | Disable any unnecessary extensions (e.g., ad blockers or security add-ons) during the interview. |
| VPN, proxy, or firewall causing interruptions | Turn off VPNs and use a direct, unrestricted network for a smoother experience. |
## A Quick Checklist before the exam
Before you begin the session, make sure you have:
* The latest version of **Google Chrome** or **Mozilla Firefox**
* A stable internet connection (strong Wi-Fi recommended)
* A device that meets minimum requirements
* Closed any unnecessary apps and browser tabs
* Allowed camera, microphone, and screen sharing permissions for the Interview Room
**Additional Troubleshooting Steps:** If freezing or crashing continues:
1. Restart your computer to clear temporary glitches.
2. Try joining from a different device to see if the issue is device-specific.
3. Switch to a **wired internet connection** for better reliability.
4. Reinstall your browser to rule out corrupted settings.
5. Monitor CPU and memory usage on your device and close any high-resource programs.
6. Temporarily disable VPNs, firewalls, or antivirus software and test again.
7. Make sure both your Operating System and browser are fully up to date.
# Interview Invite Link Not Opening or showing expired
Source: https://docs.talview.com/candidates/interviews/diagnostics/interview-invite-link-not-opening-or-showing-expired
Live Interview invite link may fail to open or show as expired due to link validity limits, account mismatches, browser issues, or network restrictions. This checklist helps you quickly identify the cause and take the right steps to access your interview without delay.
## 🔎 Troubleshooting Common Issues
| What might be wrong | How to fix it |
| :--------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------- |
| Interview link has expired | Contact your recruiter and request a new interview link or to reschedule the interview. |
| Link opened from the wrong email account | Log out of all email accounts and sign in using the same email address that received the interview invite. Then open the link again. |
| Link already used or session timed out | Refresh the page once and retry. If the link still fails, request a fresh invite from the recruiter. |
| Unsupported or outdated browser | Use the latest version of Chrome, Edge, or Firefox. Avoid opening the link from in-app browsers (Gmail, Outlook, WhatsApp). |
| Browser cache or cookie conflict | Clear browser cache and cookies, then reopen the link. Alternatively, open the link in an Incognito or Private window. |
| Network, VPN, or firewall restrictions | Turn off VPNs or proxies if allowed. Switch to a home Wi-Fi network or mobile hotspot and retry. |
| Security software blocking the link | Temporarily disable strict antivirus or browser security extensions, then reopen the link. |
### **Additional tips:**
* Always open the interview link directly from the original email instead of copying it across devices or apps.
* Avoid bookmarking the interview link, as it may expire or become invalid.
* Do not share your interview link with others, as this can invalidate the session.
* If the link opens but does not load fully, refresh once and wait a few seconds before retrying.
* Keep your recruiter’s contact details handy in case you need immediate assistance.
# Interview Room Features Not Working – Browser/Network Fixes
Source: https://docs.talview.com/candidates/interviews/diagnostics/interview-room-features-not-working-browser-network-fixes
If some features in the Talview Interview Room (such as audio, video, chat, or screen sharing) are not working properly, the issue is often related to your browser or network settings. This guide will help you troubleshoot and fix common problems to ensure a smooth interview experience.
## Troubleshooting Issues
| **Possible Reasons** | **How to Fix It** |
| :---------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Using an unsupported or outdated browser | Use a supported, and updated browser such as the latest version of Google Chrome, Edge, or Safari. |
| Browser cache or cookies causing conflicts | Clear your browser cache and cookies via your browser’s privacy settings to fix loading or functionality issues. |
| Browser permissions (camera/mic/screen sharing) blocked or denied | Ensure camera, microphone, and screen sharing permissions are enabled in your browser. Click the **lock icon** near the URL bar to check and allow permissions. |
| Browser extensions interfering with interview room features | Temporarily disable browser extensions like ad blockers or privacy tools and reload the interview room page. |
| Unstable or restricted network connection | Use a stable, direct internet connection. Avoid VPNs, proxies, or networks with strict firewall settings that may block video/audio or signaling ports. |
| Firewall or antivirus software blocking connections | Configure your firewall or antivirus to allow interview room URLs. Add exceptions if necessary. |
| Testing in a corrupted browser session | Restart your browser/device or try opening the interview room in **Incognito/Private mode** to rule out session issues. |
## Additional Troubleshooting
1. Restart your computer and relaunch the interview room.
2. Clear your browser’s cache and cookies.
3. Test in an incognito/private window to bypass extensions or cached data.
4. Close all other applications that might use your camera or microphone.
5. Switch to a wired internet connection if you’re on Wi-Fi.
6. Ensure no VPN or proxy is running during the interview.
## Need More Help?
If you’ve tried all the above steps and still face issues, please contact support with:
* Contact Talview Support for personalized assistance and can raise a ticket at [https://talview.freshdesk.com/support/tickets/new](https://talview.freshdesk.com/support/tickets/new)
Our team will help you resolve the issue.
# Network Requirements for Clear VoIP Calls in Live Interview
Source: https://docs.talview.com/candidates/interviews/diagnostics/network-requirements-for-clear-voip-calls-in-live-interviews
A stable internet connection is essential for clear and uninterrupted VoIP (Voice over Internet Protocol) calls in Talview. Interviewers can initiate calls to candidates directly from the interview landing page, ensuring prompt and seamless communication.
### Minimum and Recommended Bandwidth
| **Type** | **Minimum Requirement** | **Recommended Requirement** |
| :----------------- | :---------------------- | :-------------------------- |
| **Upload Speed** | 2 Mbps | 5 Mbps |
| **Download Speed** | 2 Mbps | 5 Mbps |
Tip: For the best results in Talview interviews, ensure at least 5 Mbps bandwidth and minimal latency for clear audio and zero lag.
### How to Check Your Network Speed
Before starting your interview or assessment, test your connection using Talview’s speed test tool:
👉 [Run Speed Test](https://speed.talview.com/)
### Steps:
1. Click **Start Test** to begin.
2. Wait for the test to finish — it automatically measures **download**, **upload**, and **latency**.
3. Compare your results with the values in the **Recommended Network Metrics** table below.
Tip: Run the test on the same device and browser you’ll use for the interview.
### Recommended Network Metrics
| **Parameter** | **Recommended Value** | **What It Means** |
| :----------------- | :-------------------- | :--------------------------------------------------------------------- |
| **Ping (Latency)** | ≤ 50 ms | Measures response time; lower values mean less delay during calls. |
| **Jitter** | ≤ 30 ms | Indicates connection stability; lower jitter ensures consistent audio. |
| **Download Speed** | ≥ 5 Mbps | Ensures you can receive real-time audio and video smoothly. |
| **Upload Speed** | ≥ 5 Mbps | Ensures your audio is transmitted clearly to others. |
### Tips for Best Performance
* Use a wired Ethernet connection instead of Wi-Fi for better stability.
* Close unused applications or browser tabs that consume bandwidth.
* Test from the same device and location where you’ll attend the session.
* Keep a mobile hotspot backup ready in case of network fluctuations.
A reliable network is key to maintaining clear, delay-free VoIP communication during interviews and assessments. By ensuring your internet meets these requirements, you can enjoy a professional, uninterrupted experience on the Talview platform.
# Resolving Audio, Video, and Screen Sharing Issues: Troubleshooting Guide for Evaluators
Source: https://docs.talview.com/candidates/interviews/diagnostics/resolving-audio-video-screen-sharing-issues-during-interview-troubleshooting-guide
Talview Interview Rooms provide a secure platform for seamless remote interviewing. However, audio, video, or screen sharing issues may occur due to browser, device, or network settings.
This guide helps evaluators quickly diagnose and resolve such issues.
## Troubleshooting Common Issues
| **What might be wrong?** | **What to do ?** |
| :------------------------------- | :--------------------------------------------------------------------------------------------------------------------- |
| Microphone not detected or muted | Check your microphone is connected, unmuted, and selected in **system settings** and Talview. Adjust volume levels. |
| Browser permissions blocked | Click the lock icon near the URL bar and allow access to microphone, camera, and screen sharing. |
| Camera already in use | Close other applications (Zoom, Teams, Skype) using your webcam before joining Talview. |
| Wrong device selected | In Talview settings, select the correct **microphone/camera** from the dropdown. |
| Poor lighting or position | Ensure good lighting and proper webcam placement for clear video. |
| Outdated or unsupported browser | Use the latest version of Chrome or Edge. |
| Cache/cookie conflicts | Clear your browser cache and cookies, or try Incognito/Private mode. |
| Screen share not starting | When prompted, grant permission and choose the correct window/screen. Make sure your OS/browser allows screen sharing. |
| Low internet bandwidth | Move closer to Wi-Fi, or switch to a wired Ethernet connection for stable video/audio and screen sharing. |
| Security/firewall restrictions | Ensure firewall/antivirus isn’t blocking Talview. Add interview URLs to the allow list if needed. |
## Additional Troubleshooting
1. Restart your browser or computer and rejoin the interview.
2. Close all other apps that may use your camera, mic, or bandwidth.
3. Try joining from an Incognito/Private window to bypass extensions.
4. Switch to another supported browser or device if issues continue.
5. Check and apply any pending system or browser updates.
## Checklist Before the Interview
Make sure that:
* Microphone and camera are connected, unmuted, and selected correctly.
* Browser permissions for audio/video/screen sharing are allowed.
* You’re using the latest browser.
* Your internet connection is stable.
* Other apps using the camera/mic are closed.
* You tested your setup 10 minutes before the interview.
## Need More Help?
If issues persist:
* Contact Talview Support for personalized assistance and can raise a ticket at [https://talview.freshdesk.com/support/tickets/new](https://talview.freshdesk.com/support/tickets/new)
Our team will help you resolve the issue.
# Session Ended Abruptly - A Quick Troubleshooting Guide
Source: https://docs.talview.com/candidates/interviews/diagnostics/session-ended-abruptly-a-quick-troubleshooting-guide
If you see a **“Session ended abruptly”** error message in middle of the test, it means your test ended unexpectedly. This can happen due to a system conflict, loss of connectivity, or a policy violation detected by the platform.
Session termination can interrupt your progress and may prevent you from completing your assessment on time — but in most cases, it can be resolved quickly.
## Common Troubleshooting Steps
| **What Might Be Wrong** | **What You Can Do** |
| :--------------------------------------- | :------------------------------------------------------------------------------------ |
| Loss of internet connection mid-session | Reconnect to a stable network and refresh the page. Avoid using mobile hotspots. |
| Switched tabs or minimized the browser | Don’t open new tabs, switch apps, or minimize the test window during your session. |
| System crashed, restarted, or froze | Restart your device and rejoin the session using the original test link. |
| Camera/mic was disabled or blocked | Make sure camera and microphone permissions are always enabled during the test. |
| Page got refreshed or test window closed | Accidental reloads or closing the browser tab can interrupt the test. |
## Additional Troubleshooting Steps
* Close all other apps or tabs to avoid *system conflicts.*
* Reopen your original test link to attempt rejoining.
* Clear your **browser cache** if errors persist.
* Run the system check to ensure everything works well.
If your session does not allow automatic rejoining, Talview will log the error and notify the recruiter/assessment provider.
## Checklist before the Live Interview
* The latest version of Chrome, Edge, or Safari is being used.
* Camera, microphone, and screen-sharing permissions are granted.
* Internet connection is stable (preferably wired).
* Unnecessary extensions or VPNs are disabled.
* Interview date, time, and time zone are confirmed.
* Joined at least 5–10 minutes early to test the setup.
## Need More Help?
* If you’ve tried all the above steps and still experience any issue, contact Talview support for further assistance.
* Or you can raise a [support ticket](https://talview.freshdesk.com/support/tickets/new).
Our team will help you resolve your issue.
# System Requirements for a Smooth Interview Experience
Source: https://docs.talview.com/candidates/interviews/diagnostics/system-requirements-for-a-smooth-interview-experience
To have a seamless and disruption-free interview, it is important to ensure that your system, browser, and internet connection meet the required standards. Below are the detailed requirements for both web and mobile platforms.
## Web Interview Requirements
### Hardware:
* **RAM:** Minimum 4GB; Recommended 8GB for smooth performance.
* **Processor:** At least a dual-core processor (x86-64 compatible) at 2 GHz, such as Intel® Core™ i3, AMD Ryzen™ 3, or Apple M1. For best results, use a quad-core processor at 2.5 GHz or higher (e.g., Intel® Core™ i5, AMD Ryzen™ 5).
* **Graphics:** 512MB internal / 1GB external graphics memory required; 1GB internal / 1.5GB external recommended.
* **Multimedia Support:**
* Functional sound card
* Inbuilt or external microphone
* Webcam capable of at least 15fps with 320x240 resolution in color (HD webcam recommended for clarity).
### Software:
* **Operating System:** Windows 10 and above, Linux (officially supported), or macOS 12.7.2 and above.
* **Browser:** Latest versions of Google Chrome, Microsoft Edge, or Mozilla Firefox (support extends to the latest - 3 versions).
## Mobile Interview Requirements
For candidates attending interviews via the mobile app:
* **Operating System:** Minimum Android 8.0 (Oreo) or iOS 13; recommended Android 12 or iOS 15 and above.
* **RAM:** At least 3GB; 4GB or higher is preferred.
* **Storage:** Ensure at least 200MB of free space (500MB recommended).
* **Camera:** Rear or front camera with minimum 5MP; front-facing 8MP+ recommended for video assessments.
* **Audio:** Inbuilt microphone and speaker; a noise-cancelling headset is recommended for better clarity.
## Bandwidth Requirement
* **Minimum:** 1 Mbps upload and 1 Mbps download.
* **Recommended:** 2 Mbps upload and 2 Mbps download.
A stable internet connection is crucial to avoid lags or disconnections during the session.
## Quick Troubleshooting Guide
If you face issues during your interview, try the following steps:
| **What Might Be Wrong** | **What To Do** | |
| :---------------------------------------------- | :-------------------------------------------------------------------------------------------------- | :- |
| Outdated browser or system resources overloaded | Update your browser, clear cache/cookies, and close unnecessary applications | |
| Webcam or microphone not working/detected | Test webcam and mic before the session, grant permissions in browser/app, use a headset for clarity | |
| Lagging video/audio or frequent disconnections | Run a speed test, ensure stable connection, use wired internet or sit close to Wi-Fi router | |
| Device shutting down or slowing during session | Restart your device before the interview and keep it plugged into power | |
Following these guidelines will help you create the right setup for a smooth and professional interview experience.
***
# Unable to Join Your Talview Interview? Troubleshooting Guide for Evaluators.
Source: https://docs.talview.com/candidates/interviews/diagnostics/unable-to-join-talview-live-interview-troubleshooting-guide-for-evaluators
Talview Interview Rooms are designed for seamless access, but technical or scheduling issues may occasionally prevent evaluators from joining. This guide will help you identify and resolve the most common problems so you can join interviews smoothly.
## Troubleshooting Issues
| **Possible Reason** | **How to Fix It** |
| :------------------------------------------------ | :-------------------------------------------------------------------------------------------------------------------------------------------- |
| Incorrect or incomplete interview link | Always use the secure link provided in your email or Talview notification. Avoid copying partial links. |
| Unsupported or outdated browser | Use the **latest version** of Google Chrome, Microsoft Edge, or Safari. |
| Browser cache/cookies causing conflicts | Clear your browser cache and cookies, then rejoin. |
| Permissions not allowed (camera/mic/screen share) | Click the **lock icon** in your browser’s URL bar and allow access to camera, microphone, and screen sharing. |
| Extensions interfering with join process | Disable extensions like ad blockers or VPN plug-ins and reload the page. |
| Internet connection unstable or restricted | Use a stable, high-speed connection. Prefer wired Ethernet over Wi-Fi. Avoid VPNs, proxies, or corporate networks with strict firewalls. |
| Audio/video devices in use by other apps | Close other tools like Zoom or Teams that may already be using your camera/mic. |
| Time zone or scheduling mismatch | Double-check the **date, time, and time zone** of the scheduled interview. Join only within the allotted time window. |
| Stuck on “Waiting for others” screen | Verify whether the candidate or other evaluators have joined. Refresh the page or rejoin if the screen persists. |
| Authentication or access denied | Confirm you are logged in with the **authorized account**. Ensure you have the correct role/permissions to join. |
## Additional Troubleshooting
1. Restart your browser or computer.
2. Test in Incognito/Private mode to rule out extension conflicts.
3. Run Talview’s built-in device check before joining.
4. Ensure your organization’s firewall or antivirus allows Talview interview URLs.
5. Try a different supported browser or device if issues continue.
6. Contact your recruiting coordinator if the issue is related to scheduling or permissions.
## Checklist Before the Interview
Make sure that :
* The latest version of Chrome, Edge, or Safari is being used.
* Camera, microphone, and screen-sharing permissions are granted.
* Internet connection is stable (preferably wired).
* Unnecessary extensions or VPNs are disabled.
* Interview date, time, and time zone are confirmed.
* Joined at least 5–10 minutes early to test the setup.
## Need More Help?
If you’ve tried the above and still can’t join:
* Contact Talview Support for personalized assistance and can raise a ticket at [https://talview.freshdesk.com/support/tickets/new](https://talview.freshdesk.com/support/tickets/new)
Our team will help you resolve the issue.
# Why am I facing browser compatibility issues during my Live interview?
Source: https://docs.talview.com/candidates/interviews/diagnostics/why-am-i-facing-browser-compatibility-issues-during-my-live-interview
If you face browser compatibility issues while joining an interview or assessment on **Talview**, this checklist helps you identify common causes and apply quick fixes to resolve them.
### 🔎 **Troubleshooting Common Issues**
| What might be wrong | How to fix it |
| :---------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Browser is outdated or unsupported | Update to the latest version of **Google Chrome**, **Microsoft Edge**, or **Mozilla Firefox**. On macOS, use the latest **Safari** version for interviews only. |
| Operating system version is incompatible | Upgrade to **Windows 10 or later**, or one of the **latest three macOS versions**. |
| Camera, microphone, or screen permissions are blocked | Allow access in browser settings and reload the page. Close other apps using the camera or mic. |
| Browser extensions interfering | Disable ad blockers, VPNs, privacy tools, or screen-recording extensions, then restart the browser. |
| Secure browser does not launch | Reinstall the secure browser and add it to antivirus or firewall exceptions. Run as Administrator on Windows. |
| Unsupported device warning | Switch to a **desktop or laptop** with a supported browser. Use the **mobile app** only if instructed. |
### **Additional tips:**
* Restart your browser after changing any permissions.
* Avoid joining from incognito or private mode unless specifically instructed.
* Complete a system check well before your scheduled interview.
# Why am I facing network interruptions during my live interview?
Source: https://docs.talview.com/candidates/interviews/diagnostics/why-am-i-facing-network-interruptions-during-my-live-interview
If your Live interviews disconnects or becomes unstable due to network issues, this checklist covers the most common causes and helps you restore connectivity quickly.
### 🔎 **Troubleshooting Common Issues**
| What might be wrong | How to fix it |
| :-------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------- |
| Internet connection is slow or unstable | Restart your modem or router and reconnect. Use a wired (LAN) connection if available and run a speed test before rejoining. |
| Too many devices using the same network | Disconnect other devices from Wi-Fi and pause downloads, streaming, or cloud backups. |
| VPN or proxy is enabled | Turn off any VPN or proxy services and connect using a direct home network or mobile hotspot. |
| Office or campus network restrictions | Switch to a personal network or mobile hotspot if video or audio traffic is blocked. |
| Browser or device is outdated | Update your browser (Chrome or Edge recommended) and operating system. Try joining from another device if the issue persists. |
| Background apps consuming bandwidth | Close unnecessary apps, browser tabs, and resource-heavy software. |
| Network changed during the interview | Stay on one stable network and avoid switching between Wi-Fi and mobile data. |
| Sudden disconnection occurred | Rejoin the interview immediately. Restart your device if reconnection does not happen automatically. |
### **Additional tips:**
* Test your internet connection at least 10 minutes before the interview.
* Keep a mobile hotspot ready as a backup.
* Sit closer to your router to improve Wi-Fi signal strength.
# Why can’t I hear the interviewer during my live interview?
Source: https://docs.talview.com/candidates/interviews/diagnostics/why-cant-i-hear-the-interviewer-during-my-live-interview
If you cannot hear the interviewer during your session, this checklist helps you identify and resolve common audio, browser, and network issues in **Talview**.
### 🔎 **Troubleshooting Common Issues**
| What might be wrong | How to fix it |
| :------------------------------------ | :------------------------------------------------------------------------------------------------------------------------------------- |
| Incorrect speaker or headset selected | Open your system sound settings and select the correct output device. If using Bluetooth, confirm the headset is connected and active. |
| Volume muted or too low | Increase system volume and check headset controls. Ensure the speaker is not muted at the device level. |
| Browser audio permission blocked | Click the browser lock icon and allow audio access, then reload the interview room. |
| Interview tab muted | Right-click the browser tab and ensure it is not muted. |
| Another application using audio | Close apps like Zoom, Teams, or Meet that may be controlling audio output. |
| Network blocking audio | Switch to a different network or mobile hotspot. Disable VPNs if allowed. |
| Faulty speaker or headset | Test audio on another website or app. Try using a different headset or device. |
### **Additional tips:**
* Use wired headphones to avoid Bluetooth connectivity issues.
* Join the interview a few minutes early to test audio.
* Avoid shared or restricted networks during the interview.
# Why can’t I join the interview after accepting the invitation?
Source: https://docs.talview.com/candidates/interviews/diagnostics/why-cant-i-join-the-interview-after-accepting-the-invitation
If you accepted the Live interview invitation but are unable to join at the scheduled time, this checklist helps you identify common technical, timing, or access-related issues and understand what to do next in **Talview**.
### 🔎 **Troubleshooting Common Issues**
| What might be wrong | How to fix it |
| :--------------------------------------- | :------------------------------------------------------------------------------------------------------------------- |
| Technical issues with device or internet | Check your internet connection, restart your browser or device, and try joining the interview again. |
| Incorrect or expired interview link | Reopen the invitation email or message and ensure you are using the most recent interview link shared with you. |
| Browser compatibility issues | Use a supported browser such as Chrome, Edge, Firefox, or Safari, and make sure it is updated to the latest version. |
| Time zone confusion | Verify the interview time and time zone mentioned in the invitation and confirm it matches your local time. |
| VPN or network restrictions | Disconnect VPN or proxy services and try joining from a different network if possible. |
### **Additional tips:**
* Try joining the interview 5–10 minutes early to avoid last-minute issues.
* Close other applications or browser tabs before joining.
* Keep your email or messages open in case updated instructions are shared.
# Why can’t I share my screen during my interview?
Source: https://docs.talview.com/candidates/interviews/diagnostics/why-cant-i-share-my-screen-during-my-interview
Screen sharing issues during live interviews in **Talview** usually occur due to browser limitations, permission blocks, network restrictions, or device compatibility problems, and this checklist helps you identify and fix them.
### 🔎 **Troubleshooting Common Issues**
| What might be wrong | How to fix it |
| :-------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------- |
| Screen sharing button is not responding | Update to the latest version of Google Chrome, Microsoft Edge, or Mozilla Firefox. Restart the browser after updating. |
| Browser is blocking screen-sharing permission | Click the lock icon near the address bar, allow screen sharing or desktop capture, then refresh or rejoin the interview. |
| Browser extensions interfering | Disable ad blockers, VPNs, or security extensions. Try Incognito or Private Mode if extensions cannot be disabled. |
| Multiple monitors or display scaling issues | Use the primary display and set display scaling to 100%. Try sharing a specific window or browser tab if full screen fails. |
| Network instability | Switch to a stable Wi-Fi or wired connection. Turn off VPNs or proxies. |
| Browser cache or session issue | Clear browser cache and cookies, restart the browser, and rejoin the interview. |
| Outdated operating system or drivers | Update your operating system and graphics drivers to the latest supported versions. |
### **Additional tips:**
* Test screen sharing before the interview using the system check.
* Close applications that use screen recording or video conferencing.
* Avoid switching networks during the interview.
# Why can’t I switch my camera or microphone during a live interview?
Source: https://docs.talview.com/candidates/interviews/diagnostics/why-cant-i-switch-my-camera-or-microphone-during-a-live-interview
During a Live interview, candidates may need to switch audio or video devices, for example, changing from a built-in microphone to a headset or selecting a different camera. If device switching does not work, it is usually due to browser permission restrictions, device conflicts, or system-level limitations.
This article helps candidates identify the cause and resolve the issue quickly.
### 🔎 **Troubleshooting Common Issues**
| What might be wrong? | What to do |
| :---------------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------- |
| New device not detected by the browser | Connect the camera or microphone **before** opening the interview link. Refresh the interview room to re-detect devices. |
| Camera or microphone permissions blocked | Click the `lock icon` in the browser address bar and set camera and microphone permissions to `Allow`, then reload the page. |
| Device in use by another application | Close Zoom, Teams, Meet, Discord, or any app using audio/video devices before retrying. |
| Unsupported or outdated browser | Use the latest version of Chrome, Edge, or Firefox. Avoid in-app or embedded browsers. |
| Device switch option unresponsive mid-interview | Keep the interview tab active and avoid switching tabs while changing devices. |
| OS-level permission restrictions | Check system privacy settings and ensure the browser is allowed to access camera and microphone. |
### **Additional Tips:**
* Keep backup devices (wired headset or alternate webcam) ready.
* Avoid Bluetooth devices with low battery, as they may disconnect unexpectedly.
* If switching fails mid-interview, inform the interviewer via chat before refreshing the page.
# Why do I hear my own voice echo during the Live interview?
Source: https://docs.talview.com/candidates/interviews/diagnostics/why-do-i-hear-my-own-voice-echo-during-the-live-interview
If you hear your own voice repeating or delayed during the Live interview, this checklist helps you identify and fix common speaker, microphone, and device configuration issues.
### 🔎 **Troubleshooting Common Issues**
| What might be wrong | How to fix it |
| :--------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------- |
| Speaker sound feeding into microphone | Switch to wired or wireless headphones immediately. If headphones are unavailable, lower your speaker volume. |
| Incorrect microphone or speaker selected | Open system sound settings and select the correct microphone and speaker. Confirm the same selection inside the interview session. |
| Microphone sensitivity too high | Reduce microphone input volume in system settings. Keep the microphone close to your mouth and away from speakers. |
| Echo cancellation disabled | Enable echo cancellation or noise suppression in your system or browser audio settings, if available. |
| Multiple devices capturing audio | Ensure only one device is being used for audio. Mute, disconnect, or move away from other nearby devices. |
### **Additional tips:**
* Sit in a smaller, enclosed room to reduce sound reflections.
* Choose carpeted or furnished spaces instead of empty rooms.
* Turn off fans, close windows, and minimize background noise sources.
# Why is my live interview loading slowly or crashing?
Source: https://docs.talview.com/candidates/interviews/diagnostics/why-is-my-live-interview-loading-slowly-or-crashing
If your Live interview takes too long to load, freezes, or crashes after joining, the issue is typically caused by network instability, browser or device limitations, or background applications consuming system resources.
This article helps you identify the cause and apply quick fixes so you can join and continue your interview smoothly.
## 🔍Troubleshooting Common Issues
| What might be wrong? | What to do |
| :-------------------------------------------- | :-------------------------------------------------------------------------------------------------------- |
| Slow or unstable internet connection | Switch to a strong Wi-Fi or wired connection. Move closer to the router and pause downloads or streaming. |
| Unsupported or outdated browser | Use the latest version of Chrome, Edge, or Firefox. Avoid in-app browsers. |
| Corrupted cache or browser data | Clear browser cache and cookies, then reload the interview link. |
| Device overloaded with background apps | Close unnecessary tabs, apps, and background programs before joining. |
| VPN, proxy, or security software interference | Disable VPN or proxy services temporarily. Ensure antivirus software is not blocking the interview page. |
| Camera or microphone conflicts | Close Zoom, Teams, Meet, or any app using audio/video devices before joining. |
| Low device memory or performance limits | Restart your device and rejoin the interview using only essential applications. |
### **Additional Tips:**
* Join the interview 10–15 minutes early to complete system checks.
* Keep only one browser tab open for the interview.
* Avoid switching networks or devices during the session.
* If the interview crashes, rejoin using the same link and inform the interviewer via chat or email.
# Why is my Live interview not loading?
Source: https://docs.talview.com/candidates/interviews/diagnostics/why-is-my-live-interview-not-loading
If your Live interview does not load or remains stuck on a loading screen, this checklist helps you quickly identify and resolve common browser, device, and network issues.
### 🔎 **Troubleshooting Common Issues**
| What might be wrong | How to fix it |
| :------------------------------------ | :------------------------------------------------------------------------------------------------------------------- |
| Unsupported or outdated browser | Update your browser to the latest version or switch to a supported browser such as Chrome, Edge, Firefox, or Safari. |
| Corrupted browser cache or cookies | Clear cache and cookies from your browser settings, then reload the interview page. |
| Required browser permissions blocked | Click the lock icon in the address bar, allow camera and microphone access, and refresh the page. |
| Browser extensions interfering | Disable extensions temporarily or open the interview in Incognito/Private mode. |
| VPN or network restrictions | Turn off VPN or proxy services and switch to a personal or home network if possible. |
| Too many applications running | Close unused apps and browser tabs, then restart the browser or device. |
| Antivirus or firewall blocking access | Temporarily allow the interview URL through security software if it is safe to do so. |
### **Additional tips:**
* Join the interview a few minutes early to verify the page loads correctly.
* Use a stable internet connection with consistent speed.
* Avoid refreshing the page repeatedly while it is loading.
# Why is my video lagging or freezing during the interview?
Source: https://docs.talview.com/candidates/interviews/diagnostics/why-is-my-video-lagging-or-freezing-during-the-interview
If your video freezes, lags, or becomes choppy during the Live interview, this checklist helps you identify and resolve common network, browser, and device performance issues.
### 🔎 **Troubleshooting Common Issues**
| What might be wrong | How to fix it |
| :----------------------------------- | :------------------------------------------------------------------------------------------------------------- |
| Unstable or slow internet connection | Switch to a wired LAN connection or strong Wi-Fi, move closer to the router, and pause downloads or streaming. |
| Browser-related issues | Update your browser to the latest version, clear cache, and try joining in Incognito or Private mode. |
| Device performance overload | Close all non-essential applications and tabs, then restart your device before rejoining. |
| VPN, firewall, or proxy interference | Turn off VPN or proxy services if allowed, and switch to an unrestricted network. |
| Camera or app conflicts | Close video apps such as Zoom, Teams, or Meet, then rejoin the interview session. |
### **Additional tips:**
* Run a network speed test and ensure latency stays below 100 ms.
* Update your webcam drivers or try using a different device.
* Refresh the interview tab only after completing the fixes above.
# Why is the camera not detected during live interviews?
Source: https://docs.talview.com/candidates/interviews/diagnostics/why-is-the-camera-not-detected-during-live-interviews
If your camera is not detected while joining a live interview on **Talview**, this checklist helps you identify common causes and apply quick fixes to restore camera access.
### 🔎 **Troubleshooting Common Issues**
| What might be wrong | How to fix it |
| :-------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------- |
| Camera is disconnected or not powered | Ensure your built-in or external camera is connected and turned on. If using a webcam, reconnect it or try a different USB port. |
| Browser camera permission is blocked | Click the lock icon in the browser address bar, open site settings, set Camera to Allow, and reload the page. |
| System-level camera access is disabled | Open camera privacy settings on your system and allow camera access for your browser (Chrome, Edge, or Firefox). |
| Incorrect camera selected | If multiple cameras are available, select the correct one in the device selector before joining the interview. Disable unused devices if needed. |
| Another application is using the camera | Close apps like Zoom, Teams, Meet, or Skype, and close any browser tabs using the camera. Restart the browser afterward. |
| Browser or operating system is outdated | Update your browser to the latest version and ensure your operating system is up to date. |
| Physical blockage or poor lighting | Remove any webcam covers, clean the lens, and ensure your face is well-lit without strong backlighting. |
| Cache, extensions, or session conflict | Clear browser cache and cookies, disable ad-blockers or privacy extensions, or try Incognito/Private mode. |
| Network or firewall restrictions | Switch to a home network or mobile hotspot, turn off VPNs, and avoid restrictive corporate networks if possible. |
### **Additional tips:**
* Test your camera using an online webcam checker before joining the interview.
* Restart your system if the camera remains undetected after browser fixes.
# Why is the chat not working during my live interview?
Source: https://docs.talview.com/candidates/interviews/diagnostics/why-is-the-chat-not-working-during-my-live-interview
Chat is used during live interviews to coordinate with the interviewer. If chat messages are not sending, loading, or updating correctly, it is usually caused by browser issues, network instability, or device performance problems. This guide helps you fix common chat issues quickly so you can continue your interview smoothly.
### 🔎 **Troubleshooting Common Issues**
| What might be wrong | How to fix it |
| :-------------------------------------- | :-------------------------------------------------------------------------------------------------------------------- |
| Chat messages not sending or receiving | Check your internet connection and ensure it is stable. Switch to a strong Wi-Fi network or mobile hotspot if needed. |
| Chat loads partially or freezes | Refresh the interview page. Close unused browser tabs and background applications, then rejoin the interview. |
| Messages appear delayed or out of order | Ensure your network connection is stable. Avoid switching networks during the interview. |
| Chat window does not open | Use the latest version of Chrome, Edge, or Firefox. Disable browser extensions and try Incognito/Private mode. |
| Browser-related issues | Clear browser cache and cookies, restart the browser, and rejoin the interview. |
### **Additional Tips**
* Avoid using VPNs or proxies during the interview.
* Restart your device before rejoining if the issue continues.
* Inform the interviewer via audio/video if chat is temporarily unavailable.
# Why is the Whiteboard not working during my Live interview?
Source: https://docs.talview.com/candidates/interviews/diagnostics/why-is-the-whiteboard-not-working-during-my-live-interview
If the Whiteboard fails to load, freeze, or not sync properly during your session in **Talview**, this guide helps you troubleshoot common issues and restore functionality quickly.
### 🔎 **Troubleshooting Common Issues**
| What might be wrong | How to fix it |
| :--------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Whiteboard does not load | Use the latest version of Chrome, Firefox, or Edge. Restart the browser and rejoin the interview. |
| Whiteboard syncs slowly or not at all | Ensure a stable internet connection. Close background apps consuming bandwidth. Run a speed test. Switch to a wired connection if possible. |
| Changes are not visible to others | Refresh the page. Clear browser cache and cookies. Rejoin the interview session. |
| Toolbar or controls not responsive | Enable JavaScript in browser settings. Disable ad-blockers or privacy extensions. Try Incognito/Private mode. Switch to a supported browser. |
| Whiteboard freezes or content disappears | Close unused tabs and applications. Ensure your device meets minimum system requirements. Restart the browser or device. Save or screenshot important content manually. |
### **Additional tips:**
* Whiteboard works best on a **desktop browser**; mobile support may be limited.
* Ensure your internet connection is stable and fast for smooth syncing.
* Rejoin the session promptly if any freezes occur to avoid losing progress.
# Why should I clear my browser cache and cookies before joining a live interview?
Source: https://docs.talview.com/candidates/interviews/diagnostics/why-should-i-clear-my-browser-cache-and-cookies-before-joining-a-live-interview
Browser cache and cookies store temporary data that can sometimes conflict with the Live interviews, leading to issues such as slow loading, device detection errors, or session instability. Clearing this data helps ensure the interview loads correctly and runs smoothly.
This article explains when and how candidates should clear browser cache and cookies to improve interview stability.
***
## **When clearing cache and cookies helps?**
* Interview page does not load fully or gets stuck on a loading screen
* Camera or microphone is not detected correctly
* Audio or video freezes intermittently
* Chat messages fail to send or update
* Errors appear after rejoining an interview
## **How to clear cache and cookies? (Quick Steps)**
> Use Chrome, Edge, or Firefox for best results.
1. Open browser settings.
2. Go to **Privacy & Security**.
3. Select **Clear browsing data**.
4. Choose **Cookies and cached images/files**.
5. Clear data for **All time**.
6. Close and reopen the browser.
7. Rejoin the interview using the same invite link.
***
### Additional Tips
* Clear cache at least once before your Live interview.
* Use a single browser profile when joining the interview.
* Avoid Incognito mode unless advised by support.
* Restart your device after clearing cache for best results.
# FAQs – Interviews
Source: https://docs.talview.com/candidates/interviews/faq-candidate
Frequently asked questions for candidates about interviews, covering pre-interview, during, and post-interview scenarios.
***
### Pre-Interview
**Q: How do I join my interview?**
A: You’ll receive an email or SMS with a unique link. Simply click the link 10 minutes before the scheduled time for online interviews.
***
**Q: Can I use my phone for the interview?**
A: Yes, mobile browsers are supported, but we recommend using a laptop for the best experience.
***
**Q: What if I can’t join from my office laptop?**
A: Some corporate devices have restrictions. Try switching to a personal laptop or mobile device.
***
### During the Interview
**Q: My interviewer hasn’t joined yet. What should I do?**
A: Stay on the interview page — interviewers may be running late. If they don’t join within 15 minutes, contact your recruiter.
***
**Q: My audio or video isn’t working. What should I check?**
A: Follow the steps below:
* Ensure your browser has permission to use your camera and mic.
* Close any other apps (Zoom, Teams, Meet) that may be using your camera.
* Refresh the page and rejoin.
***
**Q: Can I reschedule my interview?**
A: Rescheduling depends on the recruiter’s policy. In case of any request, reach out directly to your recruiter.
***
### Post-Interview
**Q: Will I get a copy of my interview recording?**
A: No, recordings are only accessible to recruiters and hiring managers. You’ll be notified by your recruiter about next steps.
***
**Q: How do I know my interview was completed successfully?**
A: Once the interview ends, your session is automatically saved. You’ll see a confirmation message before exiting.
***
**Q: Who should I contact if I face issues after the interview?**
A: You should be able to self-resolve the issues following the steps mentioned during your interview. Reach out to your recruiter in case you have additional queries — include your interview link, time, and error details for faster resolution.
# FAQs - Live Interview
Source: https://docs.talview.com/candidates/interviews/faqs/faqs-live-interviews
### **Introduction**
Talview’s Live Interviews are designed to deliver a seamless and professional interview experience by combining real-time video communication with advanced security measures to ensure a fair, transparent, and fraud-free environment.
This FAQ is designed to guide you through the **complete interview experience,** including how to prepare, what to expect during your interview. It also covers important topics like **technical readiness**, **privacy and security**, and **where to get help** if you face any issues during your live interview.
***
### **1. Before You Begin**
**Q1. What is a Live interview experience?**
Live interviews are a secure, browser-based video interview experience that enables real-time, interactive interviews. Unlike traditional phone or video calls, the platform includes specialized collaboration tools such as *live coding environments, whiteboarding,* and *screen sharing* designed to thoroughly assess your skills and fit for the role. The platform also incorporates advanced security features including *facial recognition* and *environment monitoring* to maintain interview integrity.
**Q2. How do I access my interview?**
**Step 1:** Check your email inbox for an invitation from your recruiter or hiring organization. The email will contain a unique interview link and your scheduled date and time.
**Step 2:** Click the "Join Interview" link provided in the invitation email.
**Step 3:** Your browser will open the *Live Interview platform*. You may be asked to enter verification information or credentials.
**Step 4:** Allow access to your camera and microphone when prompted by your browser.
> **NOTE:** The entire process is browser-based, no downloads or installations are required. You can access the interview from any device with a supported web browser.
**Q3. What devices can I use to join?**
A Live Interview is compatible with:
* **Computers -** Desktop or laptop (Windows, macOS, or Linux)
* **Mobile Devices -** Smartphone or tablet (iOS or Android)
* **Browsers** - Google Chrome, Microsoft Edge, or Mozilla Firefox (latest versions recommended)
We recommend using a **desktop or laptop computer** for the best experience, as it provides better video quality, stable positioning, and full access to all collaboration tools. If you must use a mobile device, ensure it has a strong internet connection and sufficient battery charge for the full interview duration.
**Q4. What technical requirements do I need to meet?**
To ensure a smooth interview experience, your device should meet these minimum specifications:
| Requirement | Minimum | Recommended |
| :------------------ | :----------------------------------- | :------------------------------------ |
| **RAM** | 4GB | 8GB |
| **Processor** | Dual core at 2 GHz or faster | Quad-core at 2.5 GHz or faster |
| **Graphics Memory** | 512MB internal / 1GB external | 1GB internal / 1.5GB external |
| **Webcam** | 15 fps minimum, 320x240 aspect ratio | Higher resolution with 30 fps |
| **Microphone** | Built-in or external | External quality microphone preferred |
| **Sound Card** | Required | Dedicated sound card preferred |
| **Internet Speed** | 1 Mbps upload / 1 Mbps download | 2 Mbps upload / 2 Mbps download |
> **NOTE:** If your device doesn't meet these specifications, you may experience lag, video freezing, or audio dropouts. Contact your recruiter if you have concerns about your device's compatibility
**Q5. What internet connection do I need?**
A **stable, high-speed internet connection** is critical for a successful interview. Here are the requirements: **Minimum Speed:** 1 Mbps upload and 1 Mbps download **Recommended Speed:** 2 Mbps upload and 2 Mbps download **Connection Type:** Wired (Ethernet cable) or private Wi-Fi network is preferred. Avoid public Wi-Fi networks (cafes, libraries, hotels), as they are often unreliable and may have bandwidth restrictions.
**Before Your Interview**
* [**Run a speed test**](https://speed.talview.com/) at to confirm your internet speed
* Close bandwidth-heavy applications (video streaming, downloads, software updates)
* Ask other household members to pause their internet usage during your interview
* If using Wi-Fi, position your device close to the router for a stronger signal
* Have a backup internet connection ready (such as mobile hotspot) in case your primary connection fails
**Pro Tip:** Join your interview 5–10 minutes early to test your connection, camera, and microphone.
**Q6. How should I prepare my environment before the interview?**
Choose a quiet, well-lit, and private space where you will not be disturbed. Make sure:
* Your background is tidy and professional
* Your face is clearly visible (avoid sitting with a bright light directly behind you)
* You inform people around you not to interrupt during the scheduled time
* You silence mobile notifications and close distracting apps or tabs
**Q7. Will I need to verify my identity or show my face?**
Yes. Live Interviews are often used with identity verification features. You may be asked to:
* Turn on your camera so your face can be captured
* Keep your face visible throughout the interview
> **NOTE:** Always follow the on-screen instructions carefully for any verification steps.
**Q8. Do I need to install any software or plugins?**
In most cases, no installation is required. Live Interviews run directly in your browser. You only need to:
* Use a supported browser
* Allow camera and microphone access when prompted
* Ensure no restrictive plugins or extensions are blocking media access
**Q9. How early should I join my Live Interview?**
It is recommended to join at least 10 minutes before the scheduled time. This gives you enough time to:
* Complete the pre-join lobby checks (camera, mic, audio).
* Adjust your lighting and background.
* Resolve any basic technical issues before the interviewer joins.
***
### **2. Interview Experience**
**Q1. What happens when I click on a Live Interview link?**
When you click the link, you will be taken to a pre-join screen or onboarding page. There, you may be asked to:
* Allow access to your camera and microphone
* Check your audio and video preview
* Review any instructions shared by the recruiter or platform
Once everything looks good, you can click to join the live interview room.
**Q2. Will I see who is in the interview room?**
You will generally see the number of participants in the interview, but you may not see full detailed information about each participant as interviewers do. This design keeps the interface simpler for you and reduces distractions.
**Q3. Can I share my screen during the interview?**
Yes, if your interviewers request it. You will see a **“Share”** option in the interface. When you select it, your browser will ask you to choose:
* A specific window
* A tab
* Or your entire screen
> **NOTE:** Always close any personal or sensitive content before sharing.
**Q4. What is “CodeJam” in the interview room?**
A collaborative code editor where you and your interviewer can write, edit, and test code in real-time.
**How It Work:**
1. Your interviewer will share a coding problem or prompt
2. You'll write code in the shared editor while your interviewer watches and listens
3. You can explain your thought process as you code
4. Your code can be executed and tested immediately, with results visible to both you and your interviewer
5. Your interviewer can provide feedback or ask follow-up questions about your approach
**Q5. What is “Whiteboard” in the interview room?**
A digital whiteboard tool allows you to draw, write, and erase content to visually explain ideas.
**How It Works:**
1. A blank whiteboard will appear on your screen
2. Use your mouse, keyboard, or stylus (if using a tablet) to draw, write, or sketch
3. You can illustrate concepts, create diagrams, draw flowcharts, or solve math problems
4. Your interviewer can see everything you draw in real-time
5. You can erase and modify your drawings as needed
**Q6. Can I chat with the interviewer during the session?**
Yes. There is a chat panel where you can send text messages to all participants. This is helpful if:
* You have brief clarifying questions
* You are facing minor audio issues
* You want to share a link or quick text response if requested
Use chat professionally and only for interview related communication.
**Q7. Can I change between light and dark themes?**
Live Interviews usually allow you to switch between **light and dark** themes for comfort. You can find a theme toggle on the interface, which will change how the application looks without affecting the interview.
**Q8. Can I see my own video while talking?**
Yes, you will usually see a small preview of your own video feed along with the interviewer’s video. This helps you ensure that your face is visible, your lighting is good, and your camera angle is appropriate.
**Q9. What happens if the interviewer is late to join?**
If you join on time and do not see the interviewer immediately, stay in the room for at least **10 minutes**. They may be joining from another meeting or dealing with delays. If no one joins after that, follow the instructions from your recruiter (for example, replying to the interview email or contacting support).
**Q10. Will I be notified when the interview is about to end?**
The interviewer may receive internal time-based notifications to help manage the session, which are not visible to you as a candidate. It is still a good practice to manage your time during answers and stay aware of the interview duration.
**Q11. Can I provide feedback about my interview experience?**
Yes. At the end of the session, you will see an option to rate your experience or share feedback about the interview and platform. This helps us and the hiring organization to improve future experiences.
**Q12. What should I do if I make a mistake or misunderstand a question?**
Treat the session like an in-person interview:
* Calmly ask for clarification if needed
* Acknowledge the misunderstanding briefly
* Correct your answer or approach Interviewers understand that virtual settings can be stressful; they are typically more interested in your overall capability and communication than perfection.
**Q13. What is a Secondary Camera?**
A **Secondary Camera** is an additional device, usually your **mobile phone**, is used during some interviews to provide an extra camera view of your surroundings. This helps ensure a **fair and secure interview environment**.
Key points to know:
* Your **main interview continues on your primary device** (laptop or desktop)
* The secondary camera is typically positioned to show your workspace or room
* This feature is enabled only if required by the hiring organization
* Clear on-screen instructions are provided to help you connect the secondary device
The secondary camera is used only for interview integrity and does not affect how your answers are evaluated.
**Q14. Will the secondary camera record audio or interrupt my interview?**
No. The secondary camera:
* Is used primarily for **visual monitoring**, not for conversation
* Does **not replace your main camera or microphone**
* Runs in parallel without interrupting the interview flow
You should continue speaking and interacting with the interviewer as usual through your primary device.
**Q15. What should I do if I face issues connecting the secondary camera?**
If you have trouble connecting your secondary device:
* Follow the on-screen instructions carefully
* Ensure your mobile device has a stable internet connection and sufficient battery
* Allow camera permissions when prompted
If the issue persists:
* Inform the interviewer via chat
* Continue the interview as instructed
Technical difficulties with the secondary camera are common and **will not automatically disqualify you**. The interviewer or recruiting team will guide next steps if needed.
**Q16. What is a 360° environment check?**
A **360° environment check** is a brief process where you may be asked to show your surroundings using your camera. This helps confirm that:
* You are in a private space
* No unauthorized materials or people are present
* The interview environment meets integrity requirements
This check is usually done **at the beginning of the interview** and takes less than a minute.
**Q17. How do I complete a 360° environment check?**
If prompted:
* Follow the interviewer’s or platform’s instructions
* Slowly rotate your camera or device to show the room
* Return the camera to its normal position once completed
Try to remain calm and natural, this is a standard step and part of the interview process.
**Q18. Will the 360° check or secondary camera affect my performance evaluation?**
No. These features are designed to:
* Maintain a fair and secure interview process
* Apply equally to all candidates for the same role
Your evaluation is based on your **skills, experience, communication, and responses**, not on the use of monitoring tools.
***
### **3. Device Permissions**
**Q1. Why do I give permission to access to my camera and microphone?**
A Live Interview uses your camera and microphone, so you can be seen and heard during the interview, and so that identity verification can be completed if required. Without granting these permissions, you may not be able to join or fully participate in the session.
**Q2. How do I allow camera and microphone access in my browser?**
When you first join the interview room, your browser will display a pop‑up requesting permission. To allow access:
* In **Chrome/Edge/Firefox**, click `“Allow”` when asked for camera and microphone access
* If you previously **blocked access**, click the`lock icon` next to the URL, go to `“Site settings,”` and set Camera and Microphone to `“Allow,”` then refresh the page
Always test this well before the scheduled start time.
**Q3. What if my camera is not being detected?**
If your camera is not detected:
* Make sure no other apps (like Zoom, Teams, or Skype) are using the camera
* Check your system’s privacy settings to ensure the browser has camera access
* Try unplugging and reconnecting your external webcam
* Switch to a different USB port if using an external device
* Refresh the browser or restart it and try joining again
**Q4. What if my microphone is not working?**
If your microphone does not work:
* Confirm that the correct microphone is selected in device settings
* Check your operating system’s sound settings to ensure the mic is enabled and not muted
* If using a headset, ensure it is properly plugged in or paired via Bluetooth
* Close other applications that may be using the microphone
* Refresh the page after making changes
**Q5. Can I switch devices (camera or microphone) during the interview?**
Yes, you can usually switch devices from within the meeting via the “Device Settings” option. There you can select a different camera, microphone, or speaker device. Make the change during a natural pause and confirm with the interviewer that they can still see and hear you.
***
### **4. Troubleshooting & Support**
**Q1. What should I do if the interview link does not open?**
If clicking the link does nothing or shows an error:
* Copy and paste the link directly into the address bar of a supported browser
* Check that you have a stable internet connection
* Make sure there are no typos in the link
* Try another supported browser (Chrome, Edge, or Firefox)
If the issue persists, contact your recruiter or the support channel mentioned in your invitation email.
**Q2. What if I am disconnected in the middle of the interview?**
If you get disconnected:
* Reconnect to your internet (or switch to a more stable connection)
* Reopen the same interview link and rejoin the room
* Inform the interviewer, once you’re back, that you temporarily lost connection
> **NOTE:** Do this as quickly as possible so that the session can continue smoothly.
**Q3. What can I do if my video is freezing or lagging?**
Video freezing is often due to network speed or congestion. Try:
* Closing all non-essential tabs and background apps
* Moving closer to your Wi‑Fi router or switching to a wired connection
**Q4. My face is not detected, or I receive a “Face not detected” message. What should I do?**
If the system cannot detect your face:
* Ensure your camera is turned on and not covered
* Sit directly in front of the camera, with your entire face clearly visible
* Improve lighting so your face is not in shadow
* Avoid sitting too far from the camera
Once your face is clearly visible, the message should resolve automatically or upon retry.
**Q5. What if I am asked to verify my identity and it fails?**
If an identity verification step fails:
* Ensure your face is clearly visible and matches your earlier photo or ID
* Remove hats, sunglasses, or anything that obscures your face
* Hold any ID document steady and within frame, if requested
* Retry the process patiently, following on‑screen instructions
**Q6. I cannot hear the interviewer, but they can hear me. What should I check?**
If you cannot hear the interviewer:
* Check that your speakers or headset are correctly selected in device settings
* Verify that your system volume and browser tab volume are not muted
* Test audio using another website or music/video app
* If needed, disconnect and reconnect your audio device
Use chat to inform the interviewer while you fix the issue.
**Q7. The interviewer cannot hear me. How do I fix this quickly?**
If the interviewer cannot hear you:
* Ensure that your microphone is not muted in platform
* Confirm that the correct microphone is selected in device settings
* Check your system’s audio input settings
* Try unplugging and reconnecting your headset or microphone
**Q8. How can I make sure my device is ready before the actual interview?**
To prepare your device:
* Restart your computer or mobile device before the interview time
* Close non-essential applications
* Run the [Speed test](https://speed.talview.com/) and [**Video diagnostics test**](/candidates/system-diagnostics/run-diagnostics)
* Check your internet speed and stability
* Join the interview link 10 minutes early to complete all checks
**Q9. I received an error saying my browser or OS is not supported. What now?**
If you see a compatibility error:
* Switch to a supported browser (Chrome, Edge, or Firefox)
* Update your browser to the latest version
* Use a device with a supported operating system (Windows 10+, macOS 12.7.2+, supported Linux)
If you cannot access a supported device, inform your recruiter as early as possible.
**Q10. What happens if the interviewer doesn’t join?**
If the interviewer fails to join within 5 minutes of the start time, the system flags it as a **potential no-show** and alerts the recruiter.
# Candidates Using CodeJam During Talview Live Interviews
Source: https://docs.talview.com/candidates/interviews/how-to/candidates-using-codejam-during-talview-live-interviews
**CodeJam** in Talview Interview Rooms provides candidates with a collaborative coding space for live technical assessments during interviews. This guide explains how candidates can access and work with CodeJam during their interview.
## Prerequisites
* Active Talview interview session invitation or link
* Stable internet connection
* Supported browser and device suitable for coding tasks
## Steps to Use CodeJam
1. **Join the Interview Session**
* Access the interview using your Talview link or via your dashboard.
2. **Activate CodeJam**
* The interviewer initiates CodeJam.
* The coding panel will open automatically alongside the interview window.
3. **Start Coding**
* Begin solving the given problems.
* Use features such as **language selection**, **syntax highlighting**, and other features and tools.
4. **Finish Coding**
* When you complete the task, or when the interviewer closes CodeJam, the screen will return to the main video/audio interview view.
## Tips for Candidates
* Check which programming languages are supported before the interview
* Think aloud and explain your approach while coding to help interviewers understand your reasoning
* Stay calm, and communicate clearly if you face technical issues
## Supported Browsers and Devices
* **Browsers:** Latest versions of Chrome, Firefox, and Microsoft Edge
* **Devices:** Desktop or laptop recommended (mobile devices have limited functionality)
# Candidates Using Whiteboard During Talview Live Interviews
Source: https://docs.talview.com/candidates/interviews/how-to/candidates-using-whiteboard-during-talview-live-interviews
The Whiteboard feature in Talview Interview Rooms provides candidates with a collaborative space to visually present ideas, solve problems, or respond to tasks during an interview. This article guides candidates on how to access and use the Whiteboard during an interview session.
## Prerequisites
Before using the Whiteboard, make sure:
* You have an **active Talview interview session** link or dashboard access.
* Your interviewer has enabled the **Whiteboard feature** during the session.
* You have a **stable internet connection** for smooth real-time updates.
## Steps to Use the Whiteboard
1. **Join the Interview Room**
* Enter your Talview interview session using the provided link or via the Talview dashboard.
2. **Locate the Whiteboard Feature**
* The Whiteboard is usually initiated by the interviewer.
* Once activated, you will see the Whiteboard window option at the bottom left of the screen.
3. **Interact with the Whiteboard**
* Use the available toolbar options to draw, write, or highlight your responses.
* Your input will be visible to the interviewer in real time.
4. **Switch Back to Video Mode**
* To exit the Whiteboard and return to the main video interview screen, click the provided option in the toolbar.
## Tips for Effective Use of Whiteboard in Talview
* **Prepare in Advance:** Familiarize yourself with the Whiteboard tools before the interview.
* **Communicate Clearly:** Explain your drawings or notes out loud to ensure clarity.
* **Use Colors and Shapes:** To highlight important points and organize your thoughts visually.
* **Maintain Interview Flow:** Switch back to video/audio smoothly to maintain conversational engagement.
**Tip for Candidates:** Use the Whiteboard to demonstrate problem-solving steps, diagrams, or brainstorming ideas to make your responses clearer and more engaging.
Switching to the Whiteboard in Talview Interview Rooms enhances collaboration, assessment, and communication during interviews.
By following the steps outlined above, candidates can efficiently use this tool to create a dynamic and interactive interview experience.
# Dos and Don’ts Before Your Talview Interview Starts
Source: https://docs.talview.com/candidates/interviews/how-to/dos-and-donts-before-your-talview-interview-starts
Preparing well before your Talview interview helps you make a strong first impression and ensures a smooth experience. Since Talview’s AI-powered platform comes with built-in checks, security measures, and a virtual interview room, your readiness should cover both technical setup and personal presentation.
## Dos Before Your Talview Interview
### 1. Run a System Check Before Your Interview
* Run Talview’s system check a day or two before the interview. Confirm your internet speed (at least 2 Mbps), webcam, microphone, and speakers are working.
* Join the interview room 5–10 minutes early to test your device and browser.
* Use an updated browser (Google Chrome or Microsoft Edge).
* Disable VPNs and ad blockers.
* Have an alternate device, charger, or internet option (like a mobile hotspot) available in case of technical issues.
### 2. Choose a Quiet, Professional Space
* Sit in a quiet, well-lit area with a clean background and minimal distractions.
* Avoid backlighting or harsh shadows that obscure your face.
### 3. Dress Appropriately
* Wear professional attire, just as you would for an in-person interview. Business casual or formal attire is recommended depending on the role.
### 4. Keep ID Ready
* Have your valid ID for identity verification.
### 5. Follow Talview’s On-Screen Instructions
* Be prepared for a 360-degree environment scan or secondary camera using your mobile device, if prompted.
* Stay on camera and avoid switching tabs or multitasking during the session.
### 6. Maintain Positive Body Language
* Look directly at the webcam, sit upright, and use natural gestures.
* Smile and engage actively to help interviewers connect with you.
## Don’ts Before Your Talview Interview
### 1. Don’t Leave Tech Setup to the Last Minute
* Avoid relying on unstable internet connections or public Wi-Fi.
* Don’t install updates or make major system changes right before the interview.
### 2. Don’t Overlook Your Environment
* Skip noisy or cluttered spaces, distracting virtual backgrounds, or dim lighting.
### 3. Don’t Multitask
* Avoid looking away often or switching screens—your engagement is monitored.
### 4. Don’t Forget to Silence Devices
* Turn off notifications on your phone, computer, and other devices to stay focused.
### 5. Don’t Panic if Something Goes Wrong
* If you face technical issues, stay calm. Try rejoining, restarting your browser, or contacting Talview support.
Proper preparation not only helps you adapt smoothly to Talview’s platform but also highlights your professionalism and focus.
With the platform’s advanced tools and your readiness, you can give your best performance and concentrate on what matters most—showcasing your skills.
***
# Face capture & Authentication Before Talview Live Interviews
Source: https://docs.talview.com/candidates/interviews/how-to/face-capture-and-authentication-before-talview-live-interview
Before starting an interview, candidates are required to complete **face capture**. These checks ensure security, fairness, and trust in the recruitment process by verifying that the right candidate is participating. Unlike passwords or PINs, face are unique, making them powerful tools for identity assurance.
## Key Benefits of Face Authentication
| **Benefit** | **Why It Matters** |
| :----------------------------------------- | :------------------------------------------------------------------------------------------------------- |
| **Enhanced security and fraud prevention** | Face biometrics are unique and difficult to replicate, preventing impersonation and unauthorized access. |
| **Accurate identity verification** | Matches the candidate’s face in real time, ensuring the verified individual participates. |
| **Seamless and convenient experience** | Removes the need for passwords or PINs, allowing quick and simple authentication. |
| **Remote and contactless authentication** | Enables secure verification without physical presence, ideal for remote interviews. |
| **Automated fraud detection** | Detects spoofing attempts such as photos or deepfakes using liveness checks. |
| **Compliance and trust** | Aligns with global data privacy standards, ensuring transparency and fairness. |
| **Ongoing monitoring** | Periodically verifies that the same person remains active during the session. |
## Candidate Tips for Smooth Authentication
* Choose a well lit space to make sure your face is clearly visible.
* Keep a valid photo ID handy.
* Follow on screen instructions to complete the verification steps carefully before proceeding.
# How candidates can stop the recording during the interview?
Source: https://docs.talview.com/candidates/interviews/how-to/how-candidates-can-stop-the-recording-during-the-interview
During a live interview in the Platform, candidates have full control over whether their session is recorded. It clearly displays the recording status and allows candidates to stop recording at any time by withdrawing their consent for regions where recording is optional.
This feature ensures transparency, privacy, and comfort throughout the interview experience.
## Steps to Stop the Interview Recording
### Check the Recording Indicator
* A **red recording indicator** appears at the top of the screen when the interview is being recorded.
* You’ll also see the message: *“This interview is being recorded.”*
### Opt Out of Recording
* Click on the **red recording indicator** or the text displayed below it.
* A **consent prompt** appears with two options:
* **I consent**
* **I don’t want to be recorded**
* Select **“I don’t want to be recorded”** to withdraw your consent.
* The recording stops immediately, and the indicator changes from red to white.
### Confirm the Change
* Once you opt out, the indicator turns **white** and displays the message:
*“This interview is not being recorded.”*
* In some cases, you may also see a message stating:
*“Recording is disabled by policy.”*
### **Notes**
* Stopping the recording applies only to the current interview session.
* Interviewers and system administrators are automatically notified when you change your recording consent.
* Recording cannot be resumed during the same interview once you’ve opted out.
**Tip:** If you’re unsure about recording policies for your interview, you can check with your recruiter or interviewer in advance. This ensures a smooth experience during your Talview interview session.
***
***
***
# How to Control Your Camera and Microphone in Live Interviews?
Source: https://docs.talview.com/candidates/interviews/how-to/how-to-control-your-camera-and-microphone-in-live-interviews
Live Interviews in the platform give you full control over your camera and microphone both **before entering** the interview and **during the live session**. This helps you verify your device setup, avoid interruptions, and comply with interviewer guidelines.
***
## Before Joining the Interview
When you enter the Interview Lobby, you will see the audio and video preview screen. Here, you can check your setup and adjust your device controls.
You can:
* **Turn On/Off Camera:** Click the **Camera** icon to enable or disable your video before joining.
* **Mute/Unmute Microphone:** Click the **Mic** icon to mute or unmute your audio.
## Steps to Set Up Before Joining
1. Open your interview link to reach the Interview Lobby.
2. If prompted, allow your browser to access the camera and microphone.
3. Use the Camera icon to turn your video on or off.
4. Use the Mic icon to mute or unmute your audio.
5. Confirm that your video and audio preview is working correctly.
***
## During the Live Interview
Once you join the interview room, the camera and microphone controls will be visible on the toolbar.
You can:
* Click to mute or unmute your microphone at any time.
* Click to turn your video on or off as needed.
### Steps During the Live Interview
1. Once in the interview room, locate the toolbar at the bottom of the screen.
2. Click the Mic button at any time to mute or unmute.
3. Click the Camera button to switch your video on or off.
4. Your changes apply instantly, without interrupting the call.
Your changes apply instantly, allowing you to adjust without interrupting the conversation.
## **Important Note**
Most interviewers require candidates to:
* Keep Camera On throughout the interview for verification and engagement.
* Keep the Microphone Unmuted unless specifically instructed to mute.
Follow the interviewer’s instructions to avoid any disruption during the session.
***
***
# How to End the Live Interviews?
Source: https://docs.talview.com/candidates/interviews/how-to/how-to-end-the-live-interviews
This article explains how candidates can properly **end a live interview session** on the platform.
Following these steps ensures a smooth departure from the session and helps you complete any required post-interview actions, including feedback submission.
***
## When You Should End the Interview
You may end or exit the interview when:
* The interview is completed, and no further interaction is needed.
* One party does not join, or the session is interrupted.
* You must exit due to technical issues or unexpected situations.
***
## Steps to End the Interview
### **1. Locate the ‘Leave’ Button**
On most devices, the Leave button appears as:
* A **red** phone/disconnect icon
* Positioned at the **bottom center** of the interview interface
### **2. Click the ‘Leave’ Button**
* Click the red button once.
* You will immediately exit the interview session.
### **3. Complete the Feedback Form**
* After exiting, the platform automatically redirects you to the **Feedback Page**.
* Fill out the feedback form as prompted.
* Feedback helps improve the platform experience.
### **Best Practices**
* Confirm that all discussions and assessments are complete.
* Avoid closing the browser tab abruptly, always use the **Leave** button for a proper exit.
* Close the tab after submiting the feedbackform.
# How to join a live talview interview on mobile?
Source: https://docs.talview.com/candidates/interviews/how-to/how-to-join-a-live-talview-interview-on-mobile
**Talview Interview Rooms** is a secure, proctored platform that allows candidates to join live interviews directly from their mobile devices. This guide explains how to access your interview, prepare your mobile setup, and join the session smoothly without technical interruptions.
## Video Guide
Watch the walkthrough below to understand the joining process on mobile:
### 1. Access Your Interview Invitation
* Check your email inbox for the interview invitation sent by the recruiter or hiring team.
* Open the email on your mobile device.
* Tap the **Join Interview** link provided in the invitation.
> No separate login is required. The link takes you directly to your interview session.
### 2. Prepare Your Mobile Setup
Before joining the interview, ensure your device and environment meet the following requirements:
| **Preparation Area** | **Best Practices** |
| :---------------------- | :--------------------------------------------------------------------------------------------------- |
| **Device** | Use a smartphone or tablet with a working camera and microphone. |
| **Internet Connection** | Ensure a stable internet or Wi-Fi connection with at least **2 Mbps** upload and download speed. |
| **Camera & Microphone** | Allow camera and microphone permissions when prompted; ensure clear video framing and audible sound. |
| **Audio Devices** | Use wired or Bluetooth earphones for clearer audio and reduced echo. |
| **Battery** | Fully charge your device or keep it connected to a power source throughout the interview. |
| **Environment** | Sit in a quiet, well-lit space with minimal background noise or movement. |
| **Background Apps** | Close all unnecessary apps to improve performance and avoid interruptions. |
### 3. Join the Live Interview
* Tap the **Join Interview** link from your email.
* When prompted, allow access to your **camera** and **microphone**.
* Complete the short audio and video check to verify your setup.
* Once verified, tap **Join Interview** to enter the live session.
You will be connected to the interviewer once the session begins.
### Candidate Checklist Before Joining
Before tapping **Join Interview**, confirm the following:
* The interview **date, time, and time zone** are correct.
* Your internet connection is stable.
* Your device has sufficient battery or is plugged in.
* All background apps are closed and notifications are disabled (enable *Do Not Disturb* mode).
* Audio and video checks are completed successfully.
* Your workspace is clean, quiet, and free from distractions.
***
# How to manage recording settings in a Live Interview?
Source: https://docs.talview.com/candidates/interviews/how-to/how-to-manage-recording-settings-in-a-live-interview
This article explains how candidates can manage, allow, or stop recording during a Live Interview on the Talview Platform. You can control your recording preferences at any time, and the platform displays a clear indicator showing whether recording is active.
***
## Prerequisites
* You must be logged in and inside the **Live Interview Room**.
* Your browser permissions for camera and microphone must be enabled.
***
## Video Guide
### **Recording Indicator**
When recording is active, you will see:
* A **red recording indicator** at the top.
* A message: **“This interview is being recorded. I don’t want to be recorded.”**
When recording is inactive:
* The indicator turns **white**.
* Message updates to: **“This interview is not being recorded.”**
***
### **Steps to Opt Out of Recording**
1. Click **“I don’t want to be recorded.”**
2. The system immediately stops the recording.
3. The indicator turns white to confirm that recording is no longer active.
***
### **Steps to Enable Recording Again**
You can re-enable recording in two ways:
**Option 1: Direct Consent**
1. When a consent prompt appears, click **“I consent.”**
**Option 2: Respond to Interviewer Request**
1. The interviewer clicks **“Request consent.”**
2. A prompt appears on your screen.
3. Click **“I consent”** to allow recording.
Once enabled, the indicator turns red with the message: **“This interview is being recorded.”**
### **Additional Notes**
* You may change your recording preference at any time.
* Once you decline recording, the interviewer cannot resume recording unless you provide consent.
* Recording behavior may differ depending on regional compliance requirements.
# How to Submit Feedback and Rating after a Live Interview?
Source: https://docs.talview.com/candidates/interviews/how-to/how-to-submit-feedback-and-rating-after-a-live-interview
Talview allows candidates to submit **feedback and ratings** after completing a live interview, giving them an opportunity to share their experience and help improve the interview process for future participants.
***
## What does Feedback include?
* **Post-interview survey:** A short feedback form displayed after the interview ends.
* **Experience ratings:** Rate key aspects such as:
* Audio and video quality
* Ease of joining and using the platform
* Clarity of instructions
* Overall interview experience
* **Optional comments:** Share suggestions, issues faced, or positive feedback in your own words.
***
## How to Submit a Feedback?
1. Complete your live interview session.
2. Once the interview ends, a **feedback prompt** appears automatically.
3. Rate the listed experience parameters.
4. Add comments if you wish (optional).
5. Submit the feedback form.
Your responses are saved securely and do not affect your interview outcome.
***
## **Why Your Feedback Matters?**
* Helps improve the interview experience for future candidates
* Highlights technical or usability issues encountered during the session
* Ensures candidate perspectives are heard and valued
* Supports continuous platform and process improvements
### **Best Practice**
Submit feedback immediately after the interview while the experience is still fresh.
# How to switch between Light and Dark themes during a Live Interview?
Source: https://docs.talview.com/candidates/interviews/how-to/how-to-switch-between-light-and-dark-themes-during-a-live-interview
Talview allows candidates to switch between **Light**, **Dark**, and **System Default** themes at any time during a live interview to improve visibility, comfort, and accessibility based on personal preference or lighting conditions.
***
## **Steps to Change the Theme**
You can update your theme directly from the live interview interface.
1. During the live interview, click the **More** menu at the bottom of the screen.
2. Select **Device Settings**.
3. Navigate to the **Theme** section.
4. Choose one of the following options:
* **Light** – Best for bright or well-lit environments.
* **Dark** – Reduces glare and is suitable for low-light conditions.
* **System Default** – Matches your device’s current theme setting
*(This may appear visually similar to Light mode depending on your system.)*
5. The selected theme is applied **instantly** without interrupting the interview.
### **Why Switching Themes Helps?**
* Improves on-screen visibility in different lighting environments
* Reduces eye strain during longer interviews
* Enhances accessibility for users sensitive to brightness or contrast
* Allows a more comfortable, personalized interview experience
# Joining a Live Interview in Talview Interview Rooms
Source: https://docs.talview.com/candidates/interviews/how-to/joining-a-live-interview-in-talview-interview-rooms
**Talview Interview Rooms** is a secure, proctored online interview platform designed to provide a smooth experience for candidates. This guide explains how to join an interview session step by step, along with preparation tips and troubleshooting.
## Step 1: Access Your Invitation
* Open the invitation email from your recruiter.
* Click the **Join Interview** link provided in the email.
## Step 2: Prepare Your Setup
| Preparation | Best Practices |
| :------------------------------------------ | :-------------------------------------------------------------------------------------------------- |
| Device | Desktop, laptop or mobile device. |
| (Google Chrome or other supported browsers) | |
| Internet | Stable connection (min. 2 Mbps upload/download) |
| Webcam & Microphone | Test that both are functional and clear |
| Environment | Quiet, well-lit, distraction-free; remove unauthorized materials or people |
| Environment Scan | Interviews may prompt you to pan your workspace; ensure your surroundings are professional and tidy |
## Step 3: Join the Interview
* Click the interview link to open the Talview live Interview in your browser.
* Enter the verification code or credentials if prompted.
* Allow access to your camera and microphone when prompted.
## Candidate Checklist Before Joining
* Confirm date, time, and time zone.
* Test internet speed and connected devices.
* Close unnecessary apps and browser tabs.
* Disable VPNs/proxy servers to avoid connectivity conflicts.
# Pre-Join Lobby for Candidate-Web
Source: https://docs.talview.com/candidates/interviews/how-to/pre-join-lobby-for-candidate-web
The Pre-Join Lobby allows candidates to prepare for the interview and adjust all required settings before entering the session.
### **Steps**
1. Upon entering the Pre-Join Lobby, allow access to your microphone and camera.
Note: If your **browser or system permissions** for camera and microphone are not enabled, you will not be able to join the meeting.
Please follow the steps in [Allowing Hardware Permissions](https://www.notion.so/Allowing-Hardware-permissions-527fd096e82b4646826e2779d12421de?pvs=21) to grant necessary access.
2. Choose your preferred **video and audio devices** for the meeting.
3. Configure your **camera and microphone settings :** you can mute or unmute your mic and turn your camera on or off before joining the session.
4. You may remain in the Pre-Join Lobby or enter the meeting and wait there until the interviewer joins.
5. The lobby displays the **number of participants** already in the meeting.
6. When you're ready for the interview, click on '**Join Interview'** to start the session.
# Sharing Screen during a live Interview in Talview Interview Rooms
Source: https://docs.talview.com/candidates/interviews/how-to/sharing-screen-during-a-live-interview-in-talview-interview-rooms
**Talview Interview Rooms** provide a secure and interactive space for interviews and assessments. While features like **CodeJam** (for coding tasks) and **Whiteboard** (for visual problem-solving) are available within the platform, you may also be asked to **share your screen** when presenting assignments, portfolios, or project work.
This guide explains when and how to share your screen effectively.
## When Do You Need to Share Your Screen?
You may be asked to share your screen in situations such as:
* Presenting a **portfolio** or project work.
* Walking through a **case study or assignment**.
* Delivering a **PowerPoint or document-based presentation**.
* Demonstrating **external tools or workflows** not supported within Talview’s built-in features.
## Step-by-Step Guide to Screen Sharing
1. **Join the Interview Session**
* Click the **Join Interview** link from your invitation.
* Allow access to your **camera and microphone**.
2. **Locate the Screen Share Option**
* In the Talview Interview Room, click the **Share Screen** button.
3. **Choose What to Share**
You will see three options:
* **Entire Screen** – Shares everything on your desktop (use only if required).
* **Window** – Shares one application window (e.g., PowerPoint, PDF viewer).
* **Browser Tab** – Shares a single tab (useful for online portfolios or web-based content).
4. **Confirm Sharing**
* Click **Share** to begin.
* Your interviewer(s) will now see the selected content.
5. **Stop Sharing**
* Once finished, click **Stop Sharing** from the control bar.
## Candidate Checklist Before Sharing
* Close unrelated tabs, apps, or private documents.
* Keep only the **presentation/assignment materials** open.
* Turn off desktop notifications (emails, messages, pop-ups).
* Test your presentation file or web link in advance.
* Use Google Chrome (latest version) for best performance.
# Understanding 360° Room View in Talview Live Interview
Source: https://docs.talview.com/candidates/interviews/how-to/understanding-360-degree-room-view-in-talview-live-interview
Talview Live Interviews uses an advanced proctoring feature like **360° Room View** to ensure a secure and fair interview environment. This guide explains what it is, why it is required, how to complete it smoothly, and the role of a **secondary device** during the process.
## What is 360° Room View?
The **360° Room View** is an environment scan feature designed to ensure that your interview space is free from unauthorized materials or additional people.
* You may be prompted to use either your **primary device camera (laptop/desktop webcam)** or a **secondary device (smartphone or tablet)** to complete the room scan.
* The system guides you to capture your desk, walls, ceiling, and surrounding areas.
* When a secondary device is required, it provides greater flexibility and a wider viewing angle to ensure complete room coverage.
* This process assures the interviewer and organization that the environment is distraction-free and compliant with interview policies.
## Step-by-Step Setup
| Step | 360° Room View |
| :--- | :------------------------------------------------------------------------------------------------ |
| 1 | Follow the on-screen instructions when prompted. |
| 2 | If instructed, connect your **secondary device** by scanning the QR code displayed on the screen. |
| 3 | Use your primary or secondary device camera to slowly pan around the room. |
| 4 | Ensure all sides of the room, desk, and workspace are clearly visible. |
| 5 | Confirm the scan is complete when the system prompts. |
## Candidate Checklist
* Keep your interview space clean and free of unauthorized items.
* Have a **secondary device (smartphone or tablet)** ready with a working camera and stable internet connection.
* Ensure the secondary device is fully charged before starting.
* Complete the environment scan before the interview begins.
**Tip:** Ensure your workspace is well-lit and tidy before starting the scan to avoid retakes or delays.
# What to Expect as a candidate before attending a Talview Live Interview
Source: https://docs.talview.com/candidates/interviews/how-to/what-to-expect-as-a-candidate-before-attending-a-talview-live-interview
Talview’s Live Interview Rooms provide candidates with a seamless, high-quality video interview experience that closely replicates an in-person meeting. You’ll interact with your interviewer in real time and may use features such as screen sharing, a virtual whiteboard, or CodeJam for coding exercises. Interviews can also be recorded (with your permission) for review.
To ensure fairness and security, Talview uses AI-powered facial recognition, ID verification, environment scanning, and secondary camera monitoring.
This article will walk you through **how to prepare, what to expect, and how to troubleshoot common issues**.
***
## Candidate Flow - Demo
## Preparation Checklist – Before the Interview
| Step | Details |
| :------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Login Early** | Join your interview room 5–10 minutes before scheduled time to test internet, camera, and microphone. |
| **Stable Internet** | Use a reliable and fast network connection (prefer wired or private Wi-Fi, avoid public Wi-Fi). Pause all bandwidth-heavy applications (downloads, streaming). Aim for 2 Mbps or higher. |
| **Supported Browser** | Use an up-to-date browser, preferably Google Chrome or Microsoft Edge. Disable VPN, ad-blockers, and clear cache before starting. |
| **Prepare Environment** | Select a quiet, well-lit, distraction-free location. Face natural light or use soft artificial light. Ensure no shadows or backlighting. Keep your background tidy and professional. |
| **Professional experience** | Dress professionally. Position your camera/frame so you are centered and clearly visible. |
| **Cross-Platform Compatibility** | Talview’s platform supports multiple devices and operating systems including Windows, macOS, Android, and iOS. Ensure your device is compatible and updated for the best experience. |
***
## During the Interview – What to Expect
* You will undergo **AI-powered facial recognition** and be asked to present a valid ID to confirm your identity.
* Some interviews require an **environment / room scan** via a secondary device: scan a QR code, then slowly record a 360° view of your room to ensure a secure and standardized interview setting.
* The front camera of your smartphone or tablet, is used as a **secondary camera** feed to continuously monitor the candidate during the session. This will provide an additional angle for interviewers, allowing them to have a wider view of your test environment.
### Interview Conduct
* Maintain eye contact by looking directly into the camera.
* Exhibit positive body language: sit up straight, smile, and be attentive.
* Listen carefully; pause briefly to gather your thoughts before responding.
* Don’t try switching tabs as you will be monitored throughout the session.
* Clarify questions politely if unclear.
### Tools You May Use
* **CodeJam** – To type, edit, and test code live in a collaborative editor. Explain your thought process as you code
* **Whiteboard** – Allows you to draw, write, highlight, or erase to visually explain ideas.
* **Screen Sharing** – You can initiate screen sharing to walk interviewers through projects, workflows, or creative work directly.
### Types of Questions
* **Competency-Based:** Focused on your skills, experience, and achievements.
* **Behavioral:** Questions about how you handled specific past situations.
* **Situational:** Hypothetical scenarios related to the job role.
***
## Post Interview
* Reflect on your performance to identify areas for improvement.
* Contact your recruiter to request feedback if available.
* Keep your device ready in case of any follow-up or technical support needs.
***
**Additional Tips for a Smooth Interview Experience:**
* **Join Early:** Gives you time to troubleshoot any last-minute technical issues.
* **Use a compatible Device:** Ensure your computer or device meets system requirements and supports Talview’s platform.
* **Stay Engaged:** Show enthusiasm for the role by actively listening and asking thoughtful questions about the team or company culture.
* **Communicate Technical Issues:** If issues occur, inform your recruiter or Talview’s 24/7 customer support for assistance.
# Why might an interviewer call you during the interview?
Source: https://docs.talview.com/candidates/interviews/how-to/why-might-an-interviewer-call-you-during-the-interview
During Live Interviews, interviewers may use **VoIP (Voice over Internet Protocol) calls** to contact candidates directly when they are unable to join the interview on time, face login issues, or are marked as no-shows. This helps ensure timely communication and avoids unnecessary interview delays.
Unlike in-platform calls, VoIP calls are placed to the **phone number you registered**, and they may appear as an **international call** on your mobile screen. These calls are used only to help interviewers quickly connect with you and guide you into the interview.
***
## **When Might You Receive a Phone Call?**
You may receive a phone call from the interviewer if:
* You have not joined the interview at the scheduled time
* You are marked as *Late* or *No-Show*
* You are facing login or access issues
* The interviewer needs to confirm your availability or help you join the session
***
### **What Happens During the Call?**
**1. Interviewer Initiates the Call**
* If you have not joined the interview on time, the interviewer can trigger a VoIP call directly from the platform.
* The system automatically dials your **registered phone number**.
**2. Incoming Call on Your Phone**
* You receive an **incoming call on your personal mobile device**.
* The call typically appears on the caller ID.
**3. Answering the Call**
* Candidates can **answer the call** as they would a regular phone call.
* Once connected, they can speak directly with the interviewer.
* The interviewer may confirm attendance, share instructions, or help the candidate join the ongoing session.
**4. During the Call**
* Candidates can **answer the call** as they would a regular phone call.
* Once connected, they can speak directly with the interviewer.
* The interviewer may confirm attendance, share instructions, or help the candidate join the ongoing session.
**5. Post-call process**
* After the call, the interviewer can update the candidate’s status (e.g., *Joined Late*, *Unable to Reach*, or *Rescheduled*).
* Follow-up communication or interview continuation happens within the platform as usual.
### **Best Practices for Candidates**
* Ensure your registered phone number is correct and active.
* Keep your mobile device nearby and unmuted during the scheduled interview time.
* Answer promptly to avoid being marked as a no-show.
* Maintain a stable mobile network for uninterrupted communication.
If you do not receive the call, check your mobile network, and ensure you’re not in airplane mode. The interviewer may attempt again within a few minutes.
***
# Ivy AI does not respond during an AI-powered interview
Source: https://docs.talview.com/candidates/ivy-ai-interview/diagnostics/ivy-ai-does-not-respond-during-an-ai-powered-interview
When you're attending an AI-powered interview and Ivy AI stops responding or doesn't respond to your answers, this can disrupt your experience. This usually happens due to microphone permissions, browser compatibility, or connectivity issues.
This article helps you troubleshoot common technical issues that prevent AI interaction.
## 🔎 Troubleshooting Common Issues
| **What might be wrong** | **How to fix it** |
| :------------------------------------------ | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Microphone permissions are blocked** | 1.Check your browser's address bar for a microphone icon. 2.Click and select `Allow`to grant microphone access. 3.Refresh the page and resume your interview. |
| **Browser is not compatible** | Use **Google Chrome (recommended) or Microsoft Edge.** Avoid Safari, Firefox, or mobile browsers as they may not fully support AI interview features. |
| **Microphone is muted or disconnected** | Check your system settings to ensure your microphone isn't muted. If using an external microphone, verify it's properly connected and selected as the default input device. |
| **Your response was too long or off topic** | Keep your answers focused and within the suggested time limit. **Ivy AI** may pause if responses exceed processing capacity or don't align with the question. |
| **Poor internet connection** | [Test your connection speed](https://speed.talview.com/). You need at least 2 Mbps for stable AI interaction. Move closer to your router or switch to a wired connection if possible. |
| **Background noise is interfering** | Move to a quiet location. Background noise or multiple voices can prevent **Ivy AI** from processing your responses correctly. |
| **Browser cache is causing conflicts** | Clear your browser cache and cookies, then restart your browser. Navigate back to your interview link to continue. |
| **Pop-up blockers are enabled** | Disable pop-up blockers for the Talview domain. Some AI interview features require pop-ups to function properly. |
| **Multiple browser tabs are open** | Close unnecessary tabs and applications. Having too many tabs open can slow down your browser and affect AI processing. |
**Additional Tips:**
* Speak clearly and at a moderate pace to help **Ivy AI** process your responses
* Wait a few seconds after **Ivy AI** asks a question before responding
* Avoid interrupting **Ivy AI** while it's speaking or processing
* Check if your antivirus or firewall is blocking the interview platform
* Try restarting your computer if issues persist after trying other solutions
# Mic Troubleshooting - Ivy (AI Interviewer) cannot hear me
Source: https://docs.talview.com/candidates/ivy-ai-interview/diagnostics/mic-troubleshooting-ivy-ai-interviewer-cannot-hear-me
If **Ivy AI (AI Interviewer)** isn't responding to your answers during your interview, the issue is usually related to microphone permissions, device settings, or conflicting applications.
Follow this guide to resolve microphone related issues and ensure Ivy can hear you clearly.
## 🔎 Troubleshooting Common Issues
| **What Might Be Wrong** | **How to Fix It** |
| :------------------------------------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Browser permissions for microphone are blocked or denied** | Click the **lock icon** in your browser's address bar and set microphone access to **"Allow"** or **"Always allow on this site."** When prompted during the interview, select **"Allow"** for microphone access. |
| **Microphone is not detected, muted, or has low volume** | Check that your microphone is connected, unmuted, and set to an appropriate volume level in your system settings. Adjust the input volume to ensure your voice can be detected. |
| **Wrong microphone device is selected** | In settings during the *environment check*, select the correct microphone from the dropdown menu. Verify in your system settings that the right device is set as the default input. |
| **Other applications are using your microphone** | Fully close apps like **Zoom, Microsoft Teams, Skype, OBS, or other video conferencing and recording tools**. Restart your browser after closing these applications. |
| **Operating system privacy settings are blocking microphone access** | **On Windows**: `Go to Settings > Privacy > Microphone > Allow access for apps and browser`. **On Mac**: `Go to System Settings > Privacy & Security > Microphone > Allow access` for Chrome or Safari. |
| Browser is outdated or unsupported | Use the latest version of **Google Chrome or Microsoft Edge** for optimal compatibility with Talview Assessment and Ivy AI. Update your browser if using an older version. |
| Hardware access is disabled at system level | Ensure **Camera access** and **Microphone access toggles** are turned **ON** in your system settings (Windows Settings or Mac System Settings). |
## 🗣️How to Prompt Ivy to Speak or Respond
If you've verified your microphone is working but Ivy still isn't responding, try these steps to prompt interaction:
✔️**Speak clearly and wait for Ivy to process your response**
After you finish answering, pause for 2-3 seconds to allow Ivy to process your answer before expecting a follow-up question.
✔️**Answer the question completely before pausing**
Ivy is designed to detect when you've finished speaking and will ask follow-up questions based on your response. Ensure you provide a complete answer rather than short phrases, as this helps Ivy understand your response and generate appropriate follow-ups.
✔️**Speak at a normal conversational pace**
Ivy AI is built to simulate human-like interactions and real-time conversations. Speak naturally at a moderate pace, not too fast or too slow, to help Ivy accurately capture and interpret your responses.
✔️**Avoid long silences during your answers**
If you pause for too long while speaking, Ivy may interpret this as the end of your response and move on to the next question. Keep your answers flowing without extended pauses to maintain conversation continuity.
✔️**If Ivy doesn't respond after your answer, repeat your response**
If Ivy doesn't acknowledge your answer or ask a follow-up question after a reasonable wait (5-10 seconds), try repeating your response clearly and slightly louder to ensure its captured.
**Additional Tips:**
* Complete the **system readiness check** and **environment check** before starting your interview to verify all hardware is working properly
* Speak loudly and continuously while testing your microphone during the setup process
* Position your microphone appropriately (6-8 inches from your mouth) to capture your audio clearly throughout the test
* Use a wired headset instead of Bluetooth devices to avoid connectivity delays or audio quality issues
* Ensure all devices you plan to use are plugged in, switched on, and fully charged before logging in to Talview
* Ensure no physical mute button on your headset, keyboard, or device is activated
* Check and securely reconnect your microphone cable if using an external device. Avoid using damaged wires
* [**Test your microphone**](https://webcammictest.com/) before the interview begins
# Video not recording in an asynchronous video response - Troubleshooting
Source: https://docs.talview.com/candidates/ivy-ai-interview/diagnostics/video-not-recording-in-an-asynchronous-video-responses-troubleshooting
If you're attempting to record video responses for your Asychronous assessment but the recording isn't working, this article will help you identify and resolve the issue.
This article helps you diagnose why your video isn't recording during asynchronous assessment.
## 🔎 Troubleshooting Common Issues
| **What might be wrong** | **How to fix it** |
| :----------------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Camera permissions not granted** | Click the camera icon in your browser's address bar Select **"Allow"** for both camera and microphone access Refresh the page and try recording again |
| **Browser doesn't support video recording** | Use the latest version of **Chrome, Firefox, or Edge** Avoid using Internet Explorer or outdated browser versions Update your current browser to the latest version Clear your browser cache and cookies, then reload the assessment |
| **Camera already in use by another application** | Close all other applications using your camera `(Zoom, Skype, Teams, etc.)` Check your system tray for background apps that might be using the camera Restart your browser after closing other applications If on Windows, open Task Manager and end any camera-related processes |
| **Camera hardware malfunction** | Try using a different camera if available |
| **Insufficient storage or memory** | Free up at least 2GB of storage space on your device Close unnecessary browser tabs and applications Clear your browser's cache and temporary files Restart your browser to free up memory |
| **Network connectivity interrupting recording** | Test your internet speed (minimum 2 Mbps upload speed recommended) Connect to a more stable network or use a wired connection Move closer to your Wi-Fi router Try recording during off-peak hours for better connectivity |
**Additional Tips:**
* Test your camera before starting the assessment by clicking the camera test option
* Record a practice response to ensure everything works before answering actual questions
* Ensure good lighting so the camera can properly capture your video
* Keep your face clearly visible and centered in the frame during recording
* If you're using a laptop, connect it to a power source to prevent performance issues
* Disable browser extensions that might interfere with camera access (ad blockers, privacy tools)
* Try using incognito or private browsing mode to rule out extension conflicts
# Candidate FAQs - Ivy interviews
Source: https://docs.talview.com/candidates/ivy-ai-interview/faqs/candidate-faqs-ivy-interviews
## Introduction
Talview's Ivy Interview is an AI interviewer designed to conduct human-like, structured interviews at scale. Ivy replicates the intelligence, empathy, and diligence of a top recruiter by listening to candidate responses in real-time, asking dynamic follow-up questions, and evaluating both verbal and non-verbal cues.
This AI-powered interviewing agent enables candidates to complete interviews at their convenience, eliminating scheduling bottlenecks while maintaining consistency, fairness, and objectivity throughout the evaluation process.
This FAQ is designed to guide you through the **complete interview experience,** including how to prepare, what to expect during your interview. It also covers important topics like **technical readiness**, **privacy and security**, and **where to get help** if you face any issues during your assessment.
***
## 1. Before You Begin
**Q1. What is Talview's Ivy Interview?**
Ivy is an AI-powered interviewing agent that conducts structured, interactive interviews similar to live human interviews. It engages with candidates and asks follow-up questions based on responses, and evaluates communication skills, problem-solving abilities, and critical thinking.
**Q2. What are the system requirements for Ivy Interview?**
For web-based interviews, you need Windows 10 or above, macOS 12.7.2 or above. Use the latest versions of Google Chrome, Microsoft Edge, or Mozilla Firefox. Your device should have at least 4GB RAM (8GB recommended), a dual-core processor at 2 GHz, and a webcam capable of at least 15fps.
**Q3. Do I need to install any special software?**
Most Ivy Interviews are conducted through your web browser without additional software installation.
***
## 2. Interview Experience
**Q4. What to expect during an Ivy (AI) interview**
* When you join an Ivy interview, you will interact with an AI interviewer that conducts a natural, conversational experience similar to live interviews.
* Ivy will ask you structured, role-specific questions and listen to your responses in real-time. Based on what you share, Ivy will ask relevant follow-up questions to explore your experience, competencies, and skills more deeply.
* The AI evaluates both your verbal responses and non-verbal cues, such as body language and communication style, to provide a comprehensive assessment.
* Throughout the session, you can engage with Ivy at your own pace in an asynchronous format, meaning you complete the interview at your convenience without scheduling constraints.
* After the interview, Ivy automatically generates a detailed report with transcripts and scoring metrics that the hiring team reviews.
**Q5. Will Ivy ask me follow-up questions?**
Yes, Ivy uses advanced natural language processing to adapt the conversation flow based on your responses. When you mention relevant experience, Ivy automatically asks follow-up questions to gather more detailed information, creating a personalized interview experience.
**Q6. How does Ivy evaluate my performance?**
Ivy captures and analyzes both verbal responses and non-verbal cues to provide a comprehensive evaluation of your potential. The AI uses a proprietary conversation engine that ensures a structured and standardized interview process, assessing you on consistent criteria including communication skills, problem-solving, and critical thinking.
**Q7. Is the Ivy Interview fair and unbiased?**
Yes, Ivy's structured format eliminates biases often present in traditional interviews. Every candidate is assessed using the same standardized questions and objective scoring criteria, ensuring consistency and fairness throughout the evaluation process.
**Q8. How long does an Ivy Interview take?**
The duration varies depending on the role and questions configured by the hiring organization. However, there is a *timer* where you can track your interview duration. Since Ivy is an on-demand interviewing agent, you can complete the interview at your convenience without time zone constraints.
**Q9. What happens if I accidentally close the Ivy interview?**
* If you accidentally close the browser window or tab during your Ivy interview, you should attempt to rejoin the session immediately using the original interview link provided in your invitation email.
* Depending on how your interview was configured by the hiring organization, you may be able to resume where you left off or restart the session.
* If you experience technical difficulties or cannot rejoin, contact your recruiting coordinator or the support contact provided in your interview invitation as soon as possible to explain the situation and request assistance. They can help determine whether you can continue the interview or need to reschedule.
**Q10. How to know if your interview submission is complete?**
* After you finish answering all questions in your Ivy interview, you will typically receive an on-screen confirmation message indicating that your interview has been successfully submitted.
* This confirmation ensures that your responses have been captured and that Ivy has generated the evaluation report for the hiring team.
* If you have concerns about submission status, contact your recruiting coordinator immediately with details about your session to verify that your interview was received.
***
## 3. Device Permissions
**Q11. Why does Ivy Interview need access to my camera and microphone?**
Ivy requires camera and microphone access to conduct interactive, real-time interviews where it can listen to your responses and observe non-verbal cues. These permissions are essential for the AI to capture verbal responses and interpret visual signals, providing a comprehensive evaluation similar to live interviews.
**Q12. What should I do if my camera or microphone is blocked?**
If your device or browser security settings are blocking access, temporarily disable firewall, VPN, or restrictive browser settings. Ensure permissions for webcam and microphone are granted in both your device settings and browser settings. You may need to restart your browser after making changes.
**Q13. Can I test my camera and microphone before the interview?**
Yes, you should test your [**camera and microphone**](/candidates/system-diagnostics/run-diagnostics) before joining your interview. This allows you to verify that your camera and microphone are functioning properly and that permissions are correctly configured.
***
## 3. Device Permissions
**Q14. How does Talview protect my privacy during Ivy Interviews?**
Talview follows strict data protection regulations including GDPR and local laws to ensure candidate privacy and data security. The platform employs encryption for data in transit and at rest, secure access controls, and regular security audits.
**Q15. What data does Ivy collect during interviews?**
Ivy collects data such as facial recognition information, screen activity, responses, and behavioral cues necessary to conduct the interview evaluation. [**Talview's Privacy Policy**](https://www.talview.com/en/privacy-and-security) clearly shows candidates what data is collected and why, and you must provide consent before starting the interview process.
**Q16. How long is my interview data stored?**
Talview keeps biometric and behavioral data only for a limited duration as required by the specific use case, deleting it automatically afterward unless required for compliance purposes. Talview does not let your information linger unnecessarily, reducing privacy risks.
**Q17. Can I opt out of data collection?**
Talview provides transparency about data collection and allows candidates to understand what's happening during their interview. You can review the Privacy Policy before starting your session. However, certain data collection is necessary to conduct the AI interview evaluation.
***
## 4. Troubleshooting & Support
**Q18. What should I do if I cannot join my Ivy Interview?**
First, confirm you received the correct invite link and session details. Check your spam folder. Ensure your system meets Talview's technical requirements and that you are using a compatible browser. Clear your browser cache, restart your device, and try joining again.
**Q19. What if I'm experiencing network connectivity problems?**
Confirm you have a stable internet connection with at least 1-2 Mbps upload and [**Run a Speed Test**](https://speed.talview.com/). If possible, switch to a different network or move closer to your Wi-Fi router. Disable VPNs or proxies that may interfere with connectivity.
**Q20. What should I do if Ivy AI does not respond during my interview?**
If Ivy stops responding, check your internet connection stability first. Try refreshing your browser or testing in Incognito/Private mode to rule out extension conflicts. Ensure your microphone is working properly and that Ivy can hear your responses clearly
**Q21. My camera or microphone is not working during the interview. What should I do?**
[**Test your hardware**](/candidates/system-diagnostics/run-diagnostics) to ensure your camera and microphone are functioning properly. Check that you have granted camera and microphone permissions in both your browser and device settings. Try using a different device if hardware issues persist.
**Q22. Should I try a different browser if I'm having problems?**
Yes, if you encounter persistent issues, try switching to a different supported browser such as *Google Chrome, Microsoft Edge, or Mozilla Firefox*. Testing in Incognito or Private mode can also help identify if browser extensions are causing conflicts.
# Access Your Ivy Assessment Link
Source: https://docs.talview.com/candidates/ivy-ai-interview/how-to/access-your-ivy-assessment-link
Candidates invited to take an **Ivy assessment (AI Interviewer) on Talview** receive an email notification containing their unique assessment link. This article provides step-by-step guidance to help you locate, access, and begin your Ivy Assessment.
## Step-by-step Guide:
Once an Ivy assessment is scheduled, you'll receive an email invitation with the assessment details.
### **To access and attend your Ivy assessment:**
* Open the assessment invitation email.
* Review the assessment name, date, duration, and candidate information.
* Click the **Start Assessment** button in the email.
* You'll be taken directly to the Ivy assessment interface.
**Additional Tips:**
* Check your spam or promotions folder regularly.
* Bookmark the assessment link in your browser or save the email in a dedicated folder so you can quickly locate it when you are ready to take the test.
* Before clicking the assessment link, read all instructions provided in the email regarding test duration, permitted tools, and technical requirements.
* Ensure your device, browser, webcam, and internet connection meet the technical requirements before starting the assessment.
* [**Running a system check**](https://webcammictest.com/) ahead of time prevents technical disruptions that could impact your performance.
* Assessment links are typically time-sensitive and may expire after a specific deadline mentioned in the email. Plan your schedule to complete the test well before the expiration date to avoid missing the opportunity.
**Avoid sharing your assessment link**. Your unique assessment link is assigned exclusively to you and should not be shared with anyone else. Using someone else to complete the assessment or allowing others to access your link violates integrity policies and can result in disqualification.
# Attend an Ivy AI Assessment (Step-by-Step)
Source: https://docs.talview.com/candidates/ivy-ai-interview/how-to/attend-an-ivy-ai-assessment-step-by-step
With the Talview platform, candidates can complete their **Ivy AI interviews** while engaging in natural, two-way conversations that showcase their skills and abilities effectively.
This article provides a step-by-step guide for candidates on how to take an **Ivy AI assessment on the web/mobile using Talview.**
***
## What is an Ivy AI Assessment?
An **Ivy AI assessment** is an AI-powered interview where you engage in a natural, two-way conversation with *Ivy, Talview's virtual interviewer*. Ivy asks questions, listens to your responses in real time, asks follow-up questions based on your answers, and evaluates your communication skills and competencies. This allows you to complete your interview at your convenience, without the need for scheduling with a human interviewer.
***
## Prerequisites
Before starting the assessment, ensure that you have:
* A **stable** internet connection.
* A computer or laptop with a **webcam and microphone**.
* Access to the **assessment link** provided by the recruiter.
* A **compatible** web browser (Chrome or Edge is recommended).
***
## Steps to Take an Ivy AI Assessment
### Step 1: Access the Assessment Link
* You will receive an invitation email with an assessment link to access the Ivy AI assessment.
* View your assessment details and click on “**Start Assessment”**, which will redirect you to the **Talview sign in portal**.
* Enter the exact same email address to which the invite was sent to you, to receive your one-time confirmation code (OTP).
* Click **Request OTP** to receive your unique confirmation code in your inbox.
* Enter the *8-digit confirmation code*, sent to your email to continue your assessment.
### Step 2: Grant Permissions
* Agree to our *Terms & Conditions and Privacy Policy* to keep your experience secure.
* Consent to face capture and session recording, ensuring assessment integrity.
* Click **Continue** to proceed after accepting required policies.
### Step 3: Face Capture
* Position your face and hold steady to **Capture** your photo for a secure face verification.
### Step 4: Start the Assessment
* Read the Assessment instructions carefully and click **Proceed.**
* Before you begin the assessment,
* Make sure your *camera* and *microphone* is **turned ON.**
* Click on **Reduce;** to reduce mic noise (This ensures your voice stays clear and professional).
* Once you're ready with the hardware setup, Click **Join** to begin your Ivy AI Assessment.
### Step 5: Engage in Conversation with Ivy
* Ivy will ask you questions one by one in a conversational manner.
* **Speak clearly and naturally**, maintaining eye contact with the camera.
* Ivy will listen to your responses and may ask **follow-up questions** based on what you say to explore your experience more deeply.
* After you finish answering, mute the mic for *2-3 seconds* to allow Ivy to process your answer before expecting a follow-up question
* Your **camera and microphone must remain on** throughout the interview so Ivy can analyze your verbal responses and non-verbal cues.
### Step 6: Assessment Submission and Feedback
* Click **End session** with a single click when your interview is complete.
* Provide *feedback* by rating your assessment experience and click on **Submit.**
***
## What Happens Next?
* Ivy generates a detailed report that includes your responses, competency scores, and behavioral insights.
* The hiring team reviews Ivy's evaluation to make informed decisions about your candidacy.
* You will be notified about next steps via email.
### **Quick Tips for Success**
* Stay calm and confident; Ivy assesses your communication as well as your answers.
* Mute and unmute as needed to manage brief interruptions without affecting your assessment.
* Ensure all technical and environmental requirements are met beforehand so you can concentrate fully on responding to Ivy's questions.
# Device and browser compatibility for Ivy
Source: https://docs.talview.com/candidates/ivy-ai-interview/how-to/device-and-browser-compatibility-for-ivy
**Talview's AI-powered interviewer, Ivy** conducts human-like interviews with real-time follow-ups and visual cue interpretation. To ensure a smooth interview experience with **Ivy**, your device and browser must meet the following technical requirements.
## Supported Browsers
For web-based Ivy AI assessments, use the latest versions of the following browsers:
* **Google Chrome** (recommended)
* **Microsoft Edge**
* **Mozilla Firefox**
Browser support extends to the latest three versions of each supported browser. Ensure your browser is updated before starting your interview with Ivy.
## Supported Devices
You can complete your Ivy AI Assessments on multiple device types:
* **Desktop or Laptop**: Recommended for the best interview experience with Ivy's real-time follow-up questions and visual assessment capabilities
* **Mobile Devices**: Available through the Talview mobile app for Android and iOS
## Operating System Requirements
### For Web Interviews
Your device must run one of the following operating systems:
* **Windows**: Version 10 and above
* **macOS**: Version 12.7.2 and above
### For Mobile Interviews
If you are attending your Ivy AI Assessment via the mobile app:
* **Android**: Minimum version 8.0; Android 12 or above recommended
* **iOS**: Minimum version 13; iOS 15 or above recommended
## Hardware Requirements
### For Web Interviews
To ensure Ivy can effectively conduct your interview with real-time listening and observation capabilities, your device should meet these specifications:
* **RAM**: Minimum 4GB; 8GB recommended for smooth performance
* **Processor**: At least a dual-core processor (x86-64 compatible) at 2 GHz, such as Intel Core i3, AMD Ryzen 3, or Apple M1
* **Graphics**: 512MB internal or 1GB external graphics memory required; 1GB internal or 1.5GB external recommended
* **Camera**: Webcam capable of at least 15fps with 320x240 resolution in color; HD webcam recommended for clarity since Ivy interprets visual cues during the interview
* **Microphone**: Inbuilt or external microphone required for verbal responses
* **Sound Card**: Functional sound card to hear Ivy's questions clearly
### For Mobile Interviews
If using the mobile app for your Ivy AI interview:
* **RAM**: At least 3GB; 4GB or higher preferred
* **Storage**: Minimum 200MB of free space; 500MB recommended
* **Camera**: Rear or front camera with minimum 5MP; front-facing 8MP or higher recommended for video assessments
* **Audio**: Inbuilt microphone and speaker; a noise-cancelling headset is recommended for better clarity during your conversation with Ivy
## Internet Requirements
A stable internet connection is essential for your Ivy AI interview, as Ivy listens in real-time and asks follow-up questions based on your responses:
* **Minimum**: 1 Mbps upload and 1 Mbps download
* **Recommended**: 2 Mbps upload and 2 Mbps download
A stable connection is crucial to avoid lags or disconnections during your interview session with Ivy.
## Browser Permissions
Before starting your Ivy AI interview, ensure you grant the following permissions in your browser:
* **Camera access**: Required for Ivy to observe visual cues and verify your identity
* **Microphone access**: Required for verbal interaction with Ivy
* **Pop-ups**: Enable pop-ups for the Talview domain
Refresh the page after granting permissions to ensure they take effect.
### **Additional Recommendations**
* **Close competing applications**: Before your interview, close applications that may use your camera or microphone, such as *Skype, Zoom, or messaging apps*
* **Test your setup**: Log in a few minutes early to [**verify**](/candidates/system-diagnostics/run-diagnostics) your camera, microphone, and internet connection are working properly
* **Use a personal device if possible**: Corporate firewalls or security restrictions on office devices may interfere with access to the platform
# Improving audio quality during Ivy interviews
Source: https://docs.talview.com/candidates/ivy-ai-interview/how-to/improving-audio-quality-during-ivy-interviews
Clear audio is essential for a successful Ivy Assessment, as it ensures your responses are captured accurately and helps create a smooth interaction experience. This article provides practical steps to improve audio quality during your Ivy interview.
## Use a High-Quality Microphone
### External Microphone
If you are attending your Ivy Assessment on a laptop or desktop, it is recommended to use a high-quality external microphone for the best audio capture. External microphones typically provide clearer sound than built-in options.
### Built-In Microphone
If an external microphone is not available, the built-in microphone on your device will work. However, ensure it is functioning properly before your interview begins.
## Test Your Audio Before the Interview
### Check Microphone Functionality
Before your scheduled Ivy interview, [**test your microphone**](https://webcammictest.com/) to verify it is detected and working properly. Most browsers allow you to test audio input during the permission setup process.
### Grant Browser Permissions
Ensure your browser has permission to access your microphone. Click the secure/lock icon in your browser's address bar and allow microphone access for the Talview site.
### System Settings
Verify that your microphone is selected as the default audio input device in your operating system's sound settings.
## Choose a Quiet Environment
### Minimize Background Noise
Select a quiet location for your Ivy interview where background noise is minimal. Ambient sounds, conversations, or other audio distractions can interfere with the clarity of your responses.
### Close Doors and Windows
Close doors and windows to reduce external noise from traffic, construction, or other sources that might be picked up by your microphone.
### Inform Others
Let household members or colleagues know you are taking an assessment, so they avoid interrupting or creating noise nearby.
## Close Competing Applications
Before starting your Ivy interview, close any applications that might use your microphone or audio resources:
* Video conferencing apps like Zoom, Skype, or Microsoft Teams
* Messaging apps with voice features such as WhatsApp or Slack
* Music or video streaming services
* Voice assistants or recording software
These applications can interfere with microphone access and reduce audio quality during your interview.
## Position Your Microphone Correctly
### Maintain Proper Distance
Speak at a comfortable distance from your microphone—typically 6 to 12 inches away for external microphones. Speaking too close can cause distortion, while speaking too far may make your voice sound faint.
### Avoid Obstructions
Ensure nothing is blocking your microphone, such as clothing, hair, or objects on your desk.
### Face Your Device
If using a built-in microphone on a laptop or desktop, position yourself directly in front of the device and speak toward the microphone.
### Final Checklist
Before starting your Ivy interview, complete this audio quality checklist:
* Test your microphone and verify it is working
* Grant microphone permissions in your browser or app
* Use a high-quality external microphone or noise-cancelling headset
* Choose a quiet environment with minimal background noise
* Close all competing applications that use audio resources
* Position yourself at the correct distance from your microphone
* Verify your internet connection is stable
* Keep your device plugged into power to avoid interruptions
# Network test checklist before starting Ivy
Source: https://docs.talview.com/candidates/ivy-ai-interview/how-to/network-test-checklist-before-starting-ivy
Before you begin your Ivy assessment on Talview's platform, it is essential to verify that your internet connection meets the minimum requirements for a smooth experience. This checklist will guide you through the network testing process to ensure you are ready.
***
## Run the Talview Network Speed Test
### Access the Speed Test
Visit the Talview Speed Test at [**https://speed.talview.com**](https://speed.talview.com**) to check your internet connection. This test is designed to measure the network speed between your device and Talview's servers.
### Start the Test
Click the **Start** button on the testing tool to begin checking your internet connection. Wait while the system analyzes your network performance.
## Understanding Your Test Results
After the test finishes, you will see results in four key areas:
### Ping (Latency)
Ping shows how fast data travels from your device to the server and back. A lower ping means a quicker connection, which is important for a smooth assessment experience.
* **Recommended**: 50ms or lower
* **Warning threshold**: 30ms
### Jitter
Jitter tells you how stable your connection is. Lower jitter means fewer interruptions during your online assessment, helping to ensure better performance.
* **Recommended**: 30ms or lower
### Download Speed
Download speed shows how quickly you can receive data from the internet. Ensure this speed is high enough for general online activities and video streaming.
* **Minimum**: 5 Mbps
* **Recommended**: 5 Mbps or higher for smooth video and real-time interaction
### Upload Speed
Upload speed shows how fast you can send data to the internet. Check that this speed is adequate for interactive tasks and data sharing during your assessment.
* **Minimum**: 5 Mbps
* **Recommended**: 5 Mbps or higher
## What the Network Test Checks
When you click **Start**, Talview's system automatically tests the following:
* **Connectivity**: Verifies that your device is online and able to connect to Talview's servers
* **Bandwidth**: Checks if your internet speed is sufficient for video streaming and real-time interaction
* **Latency**: Measures how quickly data travels between your device and Talview's servers
## Troubleshooting Failed or Warning Results
If your test shows a warning or failure, follow these steps to improve your connection:
* **Use a wired connection** instead of Wi-Fi if available
* **Close apps and tabs** that use the internet heavily, such as Zoom, Netflix, or YouTube
* **Avoid VPNs**, as they may increase latency
* **Restart your modem or router** before retrying the check
* **Sit closer to your Wi-Fi router** if you are on wireless
* **Avoid public networks** for better security and stability
* **Ensure no background apps** are consuming data if using a mobile hotspot
### Understanding Specific Errors
* **Connectivity fails**: You are not connected to a stable internet source
* **Bandwidth is low**: You may experience frozen video or delayed audio due to a congested or limited-speed network
* **Latency is high**: You may face choppy video or audio echo due to data delays
## When to Retest
Click **Retest** if:
* You have made any network changes, such as switching to mobile data or a different Wi-Fi network
* You closed apps or restarted your router
* Your initial test showed a warning or failure
### **Additional Network Checklist**
Before starting your Ivy assessment, complete these additional checks:
* **Run the system check** at least 15 minutes before your scheduled assessment
* **Do not switch devices or networks** once you have started the session
* **Avoid corporate or restricted Wi-Fi networks**, as these may have firewalls or limitations that could disrupt your assessment
* **Use a personal device** if possible to avoid security settings and firewalls from employer-provided devices
* **Ensure camera and microphone permissions** are allowed in your browser
# Candidate FAQs - Scheduling & Payments
Source: https://docs.talview.com/candidates/scheduling-payments/candidate-faqs-scheduling-and-payments
## 1. General Scheduling FAQs
**Q1. How do I schedule my exam on Talview?**
You can schedule your exam by clicking the exam link shared by your test provider, selecting an available slot from the calendar, and confirming your booking (payment may be required depending on the exam).
**Q2. Do I need to create a Talview account to book an exam?**
In most cases, no separate account creation is required. You must use the same email ID throughout the booking and exam process.
**Q3. Why am I unable to see any available exam slots?**
Slots may be fully booked, the booking window may not be open yet, or it may have already closed. Try refreshing later or contact your test provider.
**Q4. Can I choose my preferred date and time for the exam?**
Yes, you can select from the available slots shown on the scheduling calendar.
**Q5. Can I schedule the exam on a mobile device?**
Slot booking and payment can be done on supported mobile browsers.
***
## 2. Payment-Related FAQs
**Q6. Is payment mandatory to schedule an exam?**
This depends on the exam provider. Some exams require payment before confirming a slot, while others are free or prepaid.
**Q7. What payment methods are supported on Talview?**
Talview supports major credit and debit cards, PayPal, and Apple Pay (region and device dependent).
**Q8. Are UPI, net banking, Google Pay, or wallets supported?**
No. UPI, net banking, Google Pay, wallets, cash, bank transfers, or cryptocurrency are not currently supported.
**Q9. Is my payment information secure?**
Yes. Talview uses secure, compliant payment gateways to process transactions.
**Q10. Will I receive a confirmation after payment?**
Yes. You will receive a payment confirmation and exam booking email once the payment is successful.
***
## 3. Booking Confirmation & Visibility FAQs
**Q11. I completed payment, but my exam slot is not showing. What should I do?**
Wait a few minutes and refresh the page. Ensure you are logged in with the same email used for booking. If it still doesn’t appear, check your email for confirmation.
**Q12. My payment was debited, but the exam slot is not booked.**
This may be due to a temporary sync delay. Do not retry payment immediately. If the slot is still not confirmed after some time, contact support with payment details.
**Q13. I did not receive any booking confirmation email.**
Check your spam/junk folder and verify the email ID you used during booking.
**Q14. Can I book multiple slots for the same exam?**
It entirely depends on the exam provider. If they allow, then you can go ahead.
***
## 4. Payment Failure & Retry FAQs
**Q15. My payment failed. What should I do?**
Check if your card supports online/international transactions, ensure sufficient balance, and verify OTP/3D Secure authentication.
**Q16. Can I retry payment after a failure?**
Yes. You may retry payment using the same or a different supported payment method.
**Q17. I accidentally closed the payment window. What happens now?**
You can reopen the payment link from your email or reattempt payment through the booking page if available.
**Q18. Can I change my payment method after starting payment?**
Yes, if payment is not completed, you may retry using a different method. Once payment is successful, the method cannot be changed.
***
## 5. Duplicate & Incorrect Payment FAQs
**19. I was charged twice for the same exam. What should I do?**
Do not make additional payments. [Contact support](https://talview.freshdesk.com/support/tickets/new) with transaction details and screenshots for resolution.
**Q20. Why do I see a pending charge on my card?**
Pending charges are temporary and usually reversed automatically if payment fails.
**Q21. Will I be refunded for a failed or duplicate payment?**
Yes. Refunds are typically processed automatically within your bank’s standard timeline, which is 14 days.
***
## 6. Rescheduling & Cancellation FAQs
**Q22. Can I reschedule my exam after booking?**
Rescheduling depends on the exam provider’s policy and the time remaining before the exam.
**Q23. Why am I unable to reschedule my exam?**
Rescheduling may be disabled due to cutoff time restrictions, no available slots, or provider policies.
**Q24. Can I cancel my exam booking?**
Cancellation policies vary by exam. Some exams may not allow cancellation or refunds.
**Q25. What happens if I select the wrong exam time?**
If rescheduling is not available, [contact support](https://talview.freshdesk.com/support/tickets/new) immediately with booking details.
***
## 7. Invoice, Receipt & Tax FAQs
**Q26. How do I download my payment receipt or invoice?**
Receipts are usually sent via email after payment. Some exams may also allow invoice download from the booking page.
**Q27. I paid but did not receive an invoice.**
Wait for a few minutes and check spam/junk folders. If missing, contact support.
**Q28. Can I change billing details on my invoice?**
Currently, Talview does not capture detailed billing information during payment. The invoice generated will only include the candidate’s name as provided during booking. Because of this, invoice details cannot be modified after payment.
***
## 8. Slot Availability & Timing FAQs
**Q29. Why does a slot show available but becomes unavailable when I try to book it?**
Another candidate may have booked it simultaneously. Refresh the page and choose another slot.
**Q30. How long is a slot held during payment?**
Slots are temporarily reserved during payment. If payment is not completed within the allowed time, the slot may be released.
***
## 9. Technical & Access FAQs
**Q31. The booking page is not loading properly. What should I do?**
Don’t worry. Make sure you have proper internet connection. If that’s not the issue then, clear browser cache, disable extensions, or try a different browser/device.
**Q32. What if my internet disconnects during booking or payment?**
You can always retry payment. If not, then, reopen the booking link and check if the payment or booking was completed before retrying.
***
# Booked Exam Slot Not Showing – Troubleshooting Guide
Source: https://docs.talview.com/candidates/scheduling-payments/diagnostics/booked-exam-slot-not-showing-troubleshooting-guide
If you booked an exam slot in Talview but are unable to find the booking details in your inbox, don’t worry. This guide explains the most common reasons why exam slots may not appear and gives you clear steps to fix the problem.
## Common Troubleshooting Steps
| Reason | What to Do |
| :-------------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Payment Not Completed or Pending** | Verify that your payment went through. Pending or incomplete payments delay slot confirmation. |
| **System Delay or Syncing Issue** | Wait a few minutes and refresh the dashboard; backend syncing may take time. |
| **Multiple Accounts or Email Mix-up** | Confirm the booking was made with the same email/account you’re checking. |
| **Workflow Issues (Book & Pay / Pay & Book)** | - If slot reserved but payment is pending → Complete payment to confirm. - If payment was successful but slot not selected → Use the link in your email/dashboard to schedule. |
| **Mark as “Not Spam”** | If you find the email, mark add Talview to **“Not Spam”** to ensure future emails from Talview reach your inbox. |
## How to Find Your Exam Slot
Follow these steps in order:
1. Log in with the same email ID you used for booking.
2. Refresh or try a different browser/device.
3. Check your email inbox, spam, and junk folders for a confirmation message.
4. If still missing, verify your payment status with your bank.
5. If payment was successful but slot not visible, check your email for a scheduling link
# Currency & Cross-Border Payment Issues - Troubleshooting Guide
Source: https://docs.talview.com/candidates/scheduling-payments/diagnostics/currency-and-cross-border-payment-issues-troubleshooting-guide
Talview enables candidates across the world to book exams easily using multiple international payment options.
Sometimes, a payment might not go through due to issues with the card, bank, or local payment regulations. This guide will help you identify the cause and complete your transaction successfully.
## Common Troubleshooting Steps
| What might be wrong? | What to do ? |
| :---------------------------------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------- |
| **Entering incorrect payment details** | Double-check your card number, expiry date, and CVV before submitting. A single digit error can cause the transaction to fail. |
| **Using a card not enabled for international or online payments** | Ensure that your bank or card supports international or e-commerce transactions. Enable these options in your banking app before payment. |
| **Refreshing or closing the browser during payment** | Stay on the payment page until the confirmation message appears. Closing or refreshing may cancel the transaction. |
| **Not completing verification (OTP or 3D Secure)** | Some banks require OTP or secure authentication for online transactions. Keep your registered phone or email accessible during payment. |
| **Ignoring confirmation emails** | Always check your inbox (and spam folder) for Talview’s confirmation mail before assuming payment success. |
## Best Practices
* Use a stable internet connection while making payments.
* Complete your transaction in a single attempt to avoid duplicate payments.
* Keep payment proof (transaction ID or receipt) for quick resolution if needed.
* Contact [**Talview Support**](https://certification.talview.com/support/tickets/new) if confirmation is delayed.
# Duplicate Payment Issues in Talview Exam Booking – Troubleshooting Guide
Source: https://docs.talview.com/candidates/scheduling-payments/diagnostics/duplicate-payment-issues-in-talview-exam-booking
If you notice duplicate charges on your card or bank account after booking a Talview exam, don’t worry. This may happen due to multiple payment attempts, network errors, or session timeouts.
This guide explains why duplicate charges occur, expected timelines and steps to resolve.
## Common Troubleshooting Steps
| **What Might be Wrong ?** | **What to Do ?** |
| :--------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Duplicate charge visible but payment pending | Wait up to 24 hours for the system to sync. |
| Both charges successful but only one booking created | Check your email → only **one confirmed slot** should appear. In case not refunded, contact [Talview support](https://talview.freshdesk.com/support/solutions). |
| Charges deducted but no booking reflected | Save your transaction receipts and immediately raise a [Talview Support ticket](https://talview.freshdesk.com/support/solutions). |
| Bank shows “on hold” / “processing” for one charge | This is usually released automatically within 5–7 business days. Monitor your bank statement. |
## Additional Tips
* Wait for confirmation before retrying payment.
* Avoid refreshing or closing the browser during the transaction.
* Use stable internet and secure devices for payment.
# Exam Booking Confirmation Email Not Received – Troubleshooting Guide
Source: https://docs.talview.com/candidates/scheduling-payments/diagnostics/exam-booking-confirmation-email-not-received-troubleshooting-guide
Talview sends a confirmation email for your payment and/or slot confirmation on successful transaction. In case you are unable to locate this email, follow the steps below to troubleshoot and ensure your booking is confirmed.
## Common Troubleshooting Steps
| What Might Be Wrong | What to Do |
| :---------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Email in spam/junk/promotions | Check all folders. Mark Talview emails as “Not Spam.” |
| Incorrect email ID | Verify registered email in Talview account. Update if necessary and request resend from [Talview support.](https://talview.freshdesk.com/support/solutions) |
| Email delivery delay | Wait 15–20 minutes; refresh inbox and ensure internet connection is stable. |
| Email filters/rules | Disable filters or whitelist Talview domain. |
## Additional Tips
To avoid missing booking confirmation emails:
* Double-check that the registered email ID is entered correctly during signup/booking.
* Keep a screenshot of your payment confirmation or booking reference. This is essential if your confirmation email is delayed.
**Tip:** Always verify your email ID during booking. Keep a screenshot of your payment confirmation for reference if emails are delayed.
# Exam Slot Not Available or Fully Booked: Troubleshooting Guide
Source: https://docs.talview.com/candidates/scheduling-payments/diagnostics/exam-slot-not-available-or-fully-booked-troubleshooting-guide
If you don’t see any available slots while trying to schedule your exam, it usually means that the exam slots have reached full capacity or the booking window has temporarily closed.
This guide explains why this happens, how to troubleshoot, and what to do next.
## Common Troubleshooting Steps
| What might be wrong? | **What to Do** |
| :------------------------ | :--------------------------------------------------------------------------------------------------------------------------------------- |
| **All Slots Booked** | Check back later. New slots may open if other candidates cancel or reschedule. Refresh the page or log in again after some time. |
| **Exam Window Closed** | Verify your exam schedule or invitation email for valid dates. Contact your exam administrator or institution if the window has expired. |
| **Technical Cache Issue** | Clear browser cache and cookies, then refresh the exam portal or try a different browser. |
## Additional Tips
* Always book your slot early once registration opens to avoid last-minute unavailability.
* Use a stable internet connection while scheduling your exam.
* Avoid using multiple tabs or devices at the same time while booking.
* If slots remain unavailable after repeated attempts, contact your exam organizer or [Talview Support](https://talview.freshdesk.com/support/solutions) for assistance.
# Unable to complete the payment on Talview
Source: https://docs.talview.com/candidates/scheduling-payments/diagnostics/how-to-fix-international-card-payment-failures-on-talview
If your international card payment on Talview fails, it may be due to card restrictions, bank blocks, or payment gateway issues.
This article explains the most common reasons and provides clear steps to resolve the issue so you can successfully complete your exam booking
## Troubleshooting Common Issues
| What might be wrong ? | What to do ? |
| :------------------------------------------- | :----------------------------------------------------------------------------- |
| Card not enabled for international purchases | Contact your bank or card issuer to authorize international transactions |
| Foreign transaction blocks or restrictions | Some banks block international payments by default; request activation |
| Currency conversion or cross-border fees | Confirm your bank’s policies and fees for international transactions |
| Insufficient funds or credit limits | Ensure your balance or credit limit can cover the payment amount plus fees |
| 3D Secure or authentication failures | Complete OTP, 3D Secure, or any other security verifications sent by your bank |
| Fraud detection or payment gateway blocks | Notify your bank in advance of the payment and retry after confirmation |
| Incorrect billing address or card details | Double-check that billing address matches exactly with your card statement |
## Additional Tips
1. **Contact Your Bank or Card Issuer**
* Ensure your card is enabled for **international and online payments**
2. **Verify Card Details Carefully**
* Enter the correct card number, expiry, CVV, and billing address
3. **Complete Any Required Authentication**
* Respond promptly to OTPs, 3D Secure, or other security checks required by your bank
4. **Try a Different Payment Option**
* Use another card (Visa, MasterCard, Amex, etc.) or a supported digital wallet if your primary card continues to fail
* This can help bypass specific card or bank restriction
**Tip:** Keep your card issuer’s international support number handy. In case of repeated payment failures, quick contact can save time and reduce stress before exam bookings.
# How to Reschedule or Change a Wrong Exam Date on Talview
Source: https://docs.talview.com/candidates/scheduling-payments/diagnostics/how-to-reschedule-or-change-a-wrong-exam-date-on-talview
This guide helps candidates who accidentally booked the wrong exam date on Talview. It explains how to confirm your payment status, check reschedule eligibility, and update your exam booking to the correct date.
## Troubleshooting common issues
| Scenario / Symptom | Action Required / Next Steps |
| :----------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------- |
| **Cannot see the reschedule option** | You can reschedule if your exam body permits it. Some exam bodies may charge a rescheduling fee—check your exam policy before proceeding. |
| **Payment completed for wrong date** | Contact Talview support with your **transaction ID** and **confirmation email** to update the exam date. |
## Additional Troubleshooting Tips
1. **Verify Booking Details** – Double-check for exam date, time, and payment status.
2. **Determine Payment Status** – Check whether the payment succeeded. If it failed, book the correct date immediately.
Tip: Always save your transaction ID and confirmation email. These help Talview support verify your booking quickly and process date changes faster.
# How to Update Talview Exam Slot Payment Method After Booking
Source: https://docs.talview.com/candidates/scheduling-payments/diagnostics/how-to-update-talview-exam-slot-payment-method-after-booking
Description of your new file.
After booking an exam slot on Talview, you may need to update their payment method due to failed or pending transactions, accidentally closed payment windows, or switching to a preferred card.
This guide helps you identify the issue, complete the payment successfully, and know when to contact support.
## Common Troubleshooting Steps
| What might be wrong ? | What to do ? |
| :--------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Payment failed or was declined | Reach out to [Talview Support](https://talview.freshdesk.com/support/solutions) to retry payment for same booking or start a fresh booking |
| Payment is pending | Wait upto 24 hours to wait for the payment status. If not updated, reach out or start a fresh booking |
| Want to switch payment method | Use the “Retry Payment” or “Update Payment Method” option or via the payment link sent by email, before you begin your payment. Enter new payment details securely and submit. |
| Closed payment window accidentally | Check email for a payment link sent by Talview. Else, you can attempt to book again. |
| Cannot find payment update options | Contact [Talview support](https://talview.freshdesk.com/support/solutions) with booking details so they can either retry booking or send a new payment link. |
| Unsure if payment succeeded | Verify your bank statement or email for receipts. Wait upto 24 hours for system synchronization if payment was recent. If the transaction or payment is successful, payment has already been debited and cannot be altered |
## Additional Tips
1. **Retry Payment / Update Method:**
* Look for **“Retry Payment”** option.
* If unavailable, check your email for a payment retry link.
2. **Enter New Payment Details:**
* Enter your new card details or choose an alternative payment method in Talview’s secure payment gateway.
* Confirm and submit the payment to complete the transaction.
3. **Confirm Payment Completion:**
* Wait for the **email confirmation.**
* Ensure your booking status reflects successful payment.
4. **Escalate to Support if Needed:**
* If retry options are missing or payment fails repeatedly, contact Talview support with all relevant details.
**Tip:** Always verify that the payment is successful by checking invoice and booking confirmation emails or before attempting a retry.
# Lost Connection During Booking/Payment - Troubleshooting Guide
Source: https://docs.talview.com/candidates/scheduling-payments/diagnostics/lost-connection-during-booking-and-payment-troubleshooting-guide
If your internet connection drops while booking an exam or making a payment, it can **interrupt the process** and create uncertainty about whether your slot is booked or your payment was successful.
This guide explains common causes, diagnostic steps, and recommendations to safely resolve such issues.
## Common Troubleshooting Steps
| **Issue** | **What to Do** |
| :------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Payment Status Unclear** | Check your bank statement, payment app, or card transaction history to confirm if the payment was processed. |
| **No Confirmation Email** | A successful payment should trigger a confirmation email with invoice and transaction ID. If missing, the payment may not have gone through. |
| **Repeated Payment Attempts** | Avoid retrying payment multiple times without verifying status to prevent duplicate charges. |
| **Portal Session Timeout** | Refresh or reopen the [booking portal](https://cx-v2.talview.com/scheduling/drive-registration?driveScheduleId=1797\&tid=3041), log in with your registered email ID, and check your slot status. |
| **Browser Cache/Session Issues** | Clear browser cache and cookies, or try a different browser/device to resolve stale session problems. |
| **Uncertain Booking or Payment** | Contact [Talview Support](https://talview.freshdesk.com/support/solutions) promptly with any transaction ID, email, or payment details for verification. |
### **Additional Tips**
Always use a stable internet connection during booking and payment.
Keep a record of transaction attempts and monitor your email for confirmation.
Wait a few minutes after reconnection before retrying booking or payment.
# OTP Not Working During Talview Payment – Troubleshooting Guide
Source: https://docs.talview.com/candidates/scheduling-payments/diagnostics/otp-not-working-during-talview-payment-troubleshooting-guide
When completing a payment on Talview, you may need a One-Time Password (OTP) sent to your registered mobile or email. Sometimes, the OTP may not work, show as invalid, or expire, preventing successful payment.
This guide helps you identify the cause and complete your transaction smoothly,
## Common Troubleshooting Steps
| What Might Be Wrong | What to Do |
| :-------------------------- | :---------------------------------------------------------------------------------------------------------------------- |
| Expired OTP | Request a new OTP by clicking "Resend OTP." Enter it within 5-10 minutes (check SMS for specific validity time) |
| Incorrect OTP | Carefully enter the digits as received; avoid copy-paste errors |
| Bank authentication failure | Confirm card details and contact your bank if OTP is not generated |
| Payment Gateway Delay | Wait a few minutes and then retry the transaction |
| Multiple failed attempts | Wait 15-30 minutes before retrying. Your bank may temporarily block the card for security. Contact your bank if blocked |
## Additional Tips
* Stable Internet Connection: Always ensure a strong and reliable connection before initiating payment
* Use Updated Browsers: Use the latest versions of Chrome , Edge , or Safari for secure payment processing
* Stay Reachable: Keep your registered email and phone accessible to receive OTPs promptly
* Disable Interfering Tools: Turn off VPNs, ad blockers, or privacy tools that may block payment flows
**Tip:** Always save your transaction reference number. If the OTP fails, you can quickly track the transaction with Talview support or your bank.
# Payment Debited but Talview Exam Slot Not Booked – Troubleshooting Guide
Source: https://docs.talview.com/candidates/scheduling-payments/diagnostics/payment-debited-but-talview-exam-slot-not-booked-troubleshooting-guide
If your Talview exam booking hasn’t been confirmed, this guide helps identify possible causes, verify your status, and resolve the issue quickly.
Follow the steps below to prevent duplicate payments and ensure your slot is secured.
## Common Troubleshooting Steps
| What might be wrong? | **What to Do?** |
| :-------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **System Delay in Booking** | Sometimes the system takes a few minutes to sync with the payment gateway. Wait and check your email for confirmation. |
| **Payment Confirmation Not Received** | Check your inbox and spam/junk folders for payment or booking emails. Sometimes confirmations are delayed. |
| **Attempted Duplicate Payment** | Do not pay again immediately. This could lead to duplicate charges. Wait for support verification. |
| **Transaction Not Reflected in System** | Contact [Talview support](https://talview.freshdesk.com/support/solutions) with your transaction ID, booking details, date/time of payment, and screenshots of payment success/error. |
| **Refund or Slot Confirmation Pending** | Talview support will either confirm your booking or initiate a refund. Monitor your email for updates. |
Tip: Keep all payment documentation ready and avoid multiple payments. Talview support can verify and resolve your original transaction safely.
# Refund not credited after Exam Cancellation/Payment Failure – Troubleshooting Guide
Source: https://docs.talview.com/candidates/scheduling-payments/diagnostics/refund-not-credited-after-exam-cancellation-or-payment-failure-troubleshooting-guide
If your **refund has not been credited** after cancelling an exam slot or a failed payment attempt, it may be due to processing delays or technical issues.
This guide explains common causes, diagnostic checks, and recommended actions to help you track and resolve refund-related concerns effectively.
## Common Troubleshooting Steps
***
| What Might be Wrong ? | **What to Do ?** |
| :------------------------------------------------ | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Cancellation or Payment Failure Not Confirmed** | Verify that your exam cancellation or payment failure has been identified and processed. A confirmation email will be sent once it’s complete. |
| **Refund Still Processing** | Refunds may take 10-14 business days depending on your bank or payment gateway. Check the expected processing time in your confirmation email. |
| **Multiple Refund Requests** | Avoid submitting multiple refund requests for the same transaction. It may cause confusion or delay resolution. |
| **No Refund Confirmation Email** | Check your inbox for the refund confirmation message, which includes reference or transaction IDs. It rarely goes to spam or junk unless the sender has been unsubscribed. |
| **System or Technical Delay** | Refunds are processed automatically, so delays are rare. If the expected timeline has passed, contact [Talview Support](https://talview.freshdesk.com/support/solutions) with transaction details for review. |
## Additional Tips
* Keep a copy of your cancellation confirmation or failed payment receipt.
* Track refund progress through your bank or payment provider before escalating.
***
Tip : Refund timelines vary by bank and payment provider. Always wait for the full processing period before raising a support ticket to ensure accurate tracking and resolution.
# Talview Invoice/Receipt Missing After Payment – Troubleshooting Guide
Source: https://docs.talview.com/candidates/scheduling-payments/diagnostics/talview-invoice-or-receipt-missing-after-payment-troubleshooting-guide
This guide helps you understand why an invoice or receipt might not appear in Payment success page or in mail after a payment or booking on Talview, provides step-by-step solutions, and explains when to contact support for assistance.
## Common Troubleshooting Steps
| What might be wrong? | What to do? |
| :------------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------- |
| Email delivery delay | Wait a few minutes as automated invoices can take time to be delivered. |
| Email landed in Spam/Junk folder | Check spam, junk, or promotional folders. Mark Talview as a safe sender. |
| Incorrect/misspelled email address | Verify the registered email during booking/payment and correct any typos. |
| Notification blocked by system/email filters | Add Talview’s support email domain to your safe sender/whitelist. |
| Multiple windows or session conflicts | Complete your booking/payment in a single browser tab on one device to prevent session conflicts that may delay invoice generation. |
| Invoice generation in progress | Some invoices generate only after final payment confirmation. Wait and refresh. |
## Additional Tips
1. Use the same email linked to your Talview registration and payment.
2. Keep your email app updated and check your spam filter settings regularly.
3. Try accessing the page on another browser/device if email isn’t received.
4. Check if your organization’s IT/email admin has blocked automated messages.
**Tip:** Always capture a screenshot of your payment confirmation. It helps in faster resolution if support is needed.
# Talview Payment Status Processing – How to Resolve
Source: https://docs.talview.com/candidates/scheduling-payments/diagnostics/talview-payment-status-shown-as-processing-how-to-resolve
Sometimes after making a payment on Talview, the status may appear as **“Processing”**. This usually means your transaction is still being verified by the bank or payment provider
This guide explains the reasons for this status, what you can do, and when to contact support
## Common Troubleshooting Steps
| What Might Be Wrong | What to Do |
| :---------------------------------------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Payment gateway is still verifying or settling the transaction | Wait for the payment gateway to complete verification and update the status. This can take up to 24 hours |
| Temporary communication delay between Talview and the payment processor | Talview will send a confirmation email with your receipt once the payment is successfully processed. If the payment fails, Talview will notify you via email |
| Payment undergoing additional bank/fraud/security checks | Check your bank statement to confirm whether the amount is debited or placed on hold |
| Network or synchronization lag during high transaction volumes | Avoid multiple payment attempts; wait for the first one to resolve |
| Email or notification delay | Check your registered email for confirmation or follow-up from Talview |
## Additional Tips
1. Ensure a stable internet connection and use a supported browser to avoid transaction interruptions.
2. Do not close the payment tab until confirmation appears.
## Checklist Before & After Payment
| Stage | Best Practice | Why It Helps |
| :----------------- | :----------------------------------------- | :----------------------------------------------- |
| **Before Payment** | Ensure stable internet and updated browser | Prevents interruptions during processing |
| **During Payment** | Complete OTP/security steps without delays | Ensures quicker transaction approval |
| **After Payment** | Talview will notify via email | Confirms reconciliation between bank and Talview |
***
# Talview Slot Booking: Payment Interrupted by Closed Tab
Source: https://docs.talview.com/candidates/scheduling-payments/diagnostics/talview-slot-booking-payment-interrupted-by-closed-tab
If you accidentally close the payment tab or window during a transaction, this may interrupt communication between the payment gateway and Talview system.
This guide provides focused troubleshooting steps and guidance on resolving the status of your payment and booking.
## What Happens When You Close the Payment Tab?
The outcome depends on when the payment tab was closed. The payment may or may not have been completed, depending on how far the transaction progressed.
* **If you close the tab before completing the payment:**
The transaction likely did not process, so the exam slot may remain reserved but unpaid. You will need to restart the payment process or use retry options. You can reach out to [Talview Support](https://talview.freshdesk.com/support/solutions) to generate a payment link for you.
* **If you close the tab after completing the payment:**
The payment gateway may have processed the payment successfully, but Talview might not have received the confirmation yet. This can cause a delay in booking confirmation on Talview’s side.
## What To Do If You Accidentally Close the Payment Tab or Window
* Wait for a few minutes: The transaction may still be processing despite the premature closure.
* Check your registered email for payment confirmation or failure notifications.
* Review your bank or card statement for any debit corresponding to the transaction.
* Do not immediately retry payment until you verify whether the transaction succeeded or failed.
* Collect transaction details like payment IDs and screenshots if available, for a proof if needed.
## Common Troubleshooting Steps
| What Might Be Wrong | What to Do |
| :------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------ |
| Payment debited but confirmation not displayed | Wait for 10–15 minutes. Check email for payment confirmation. |
| Payment failed and window closed prematurely | Review bank/card statement for charges. Retry payment only if no deduction observed. |
| Multiple attempts caused confusion or duplicate payments | Verify transactions before retrying; contact [Talview support](https://talview.freshdesk.com/support/solutions) for duplicate dispute resolution. |
## Additional Tips
* Keep the payment tab/window open until receiving clear payment success or failure confirmation.
* Confirm stable internet connection before initiating payment.
* Use supported browsers like Chrome or Edge with their latest versions.
* Avoid multiple payment attempts simultaneously on different devices/tabs.
# Unable to Book Slot After Payment – Troubleshooting Guide
Source: https://docs.talview.com/candidates/scheduling-payments/diagnostics/unable-to-book-slot-after-payment-troubleshooting-guide
If you are unable to book your exam slot after completing payment on Talview, it usually indicates a temporary synchronization issue, incomplete workflow step, or browser-related problem.
This guide explains the common causes, diagnostic checks, and recovery steps.
## Common Troubleshooting Steps
| **What might be wrong?** | **What to Do** |
| :----------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Payment not fully processed** | Check your **bank statement**, payment app, or **email invoice** to confirm payment success. If the amount is deducted but booking isn’t confirmed, wait 5–10 minutes for synchronization. |
| **Slot booking page not redirected** | After payment, you will be redirected to confirmation page with a link to book slot not, refresh the page, or log out and log back in using the same credentials. |
| **No available slots** | All exam slots may be booked or not yet released. Refresh the booking page periodically or check back later when new slots are opened by the administrator. |
| **Session timeout or login issues** | Inactivity can cause your login to expire. Re-login to restore access and retry booking a slot. |
| **System synchronization delay** | Occasionally, there’s a brief delay in linking your payment to the booking system. Wait a few minutes, then recheck the slot page. |
## Additional Tips
* Keep your session active while completing both the payment and booking steps. If you don’t book your slot immediately after payment, you will receive an email with a link to complete the slot booking later.
* Avoid multiple payment attempts - always verify first whether your payment has been processed.
* Check your registered email (and spam folder) for payment receipts, booking confirmations, or slot release notifications.
# Unable to Cancel Talview Booking – Troubleshooting Guide
Source: https://docs.talview.com/candidates/scheduling-payments/diagnostics/unable-to-cancel-talview-booking-troubleshooting-guide
If you want to cancel your Talview exam booking, but are unsure how to proceed or face issues during cancellation, this guide will help you understand common causes, diagnostic checks, and safe recovery actions.
## Common Troubleshooting Steps
| What might be wrong? | **What to Do?** |
| :------------------------------ | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Booking Close to Exam Time** | Cancellation eligibility depends on the **exam provider’s policy**. Most providers allow cancellations only a few hours before the scheduled exam. Requests made beyond this window may not be accepted. |
| **Cancel Option Not Available** | This could be a configuration where cancellations are disabled by the \*\*\*\*exam provider. In such cases, the option will not appear in your confirmation email or booking page. |
| **Cannot Find Cancel Option** | To cancel your exam slot, use the **Cancel** option available in your confirmation email or directly on the booking page right after scheduling. |
| **Cancellation Not Processing** | Refresh the page and try again. Ensure your session is active and that you are using a supported browser. Long inactivity can cause buttons to become unresponsive. |
| **No Confirmation Email** | After a successful cancellation, you’ll receive an automated email confirming the action. |
| **Refund Not Reflected** | Refund timelines (typically 10–14 business days) depend on the payment provider’s policy such as and your bank’s processing time. |
## Additional Tips
* Always complete the cancellation in one continuous session without long pauses.
* Use the latest version of a supported browser for smooth performance.
* Automated notifications will keep you informed about cancellation and refund status.
* Contact [Talview support](https://talview.freshdesk.com/support/solutions) if you encounter technical issues or delayed refunds
# Unable to Download Talview Invoice or Receipt – Troubleshooting Guide
Source: https://docs.talview.com/candidates/scheduling-payments/diagnostics/unable-to-download-talview-invoice-or-receipt-troubleshooting-guide
Once your payment is completed, the invoice will be available on your payment confirmation screen and will also be sent via email to your registered email address.
If you are unable to download your invoice or receipt after completing a payment for a Talview exam or service, this guide will help you understand the common causes, perform diagnostic checks, and take safe recovery actions.
## Common Troubleshooting Steps
| What might be wrong? | **What to Do?** |
| :---------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Verify Email Delivery** | Ensure that your registered email is correct and functional. Check if payment is confirmed. If payment is processing, invoice will be generated after its confirmed. |
| **Invoice Email Not Received** | Check your registered email inbox, including spam/junk folders. Talview automatically sends invoices after successful payments. |
| **Browser Cache or Compatibility Issues** | Clear your browser cache and cookies. Try using an updated supported browser like Chrome, Firefox, or Edge. |
| **Browser Extensions Blocking Downloads** | Disable browser extensions such as ad blockers that might prevent file downloads. |
| **Issues with Download Link** | Contact Talview support with your booking ID and payment details. Request that your invoice/receipt be sent directly via email. Keep your transaction ID handy for faster assistance. |
## Additional Tips
1. **Contact Support:** If you still cannot access your invoice, submit a support request with all relevant payment and booking details. [Talview support](https://talview.freshdesk.com/support/solutions) can provide the document manually.
2. **Keep Records:** Always save your transaction ID, payment confirmation, and any email correspondence for reference.
Tip : Talview’s system is designed to automate invoice generation and email delivery. Manual intervention is rarely needed but is available if technical issues prevent automated access.
# Unable to Proceed After Selecting a Slot – Troubleshooting Guide
Source: https://docs.talview.com/candidates/scheduling-payments/diagnostics/unable-to-proceed-after-selecting-a-slot-troubleshooting-guide
If you are unable to proceed after selecting a slot or completing payment during the Talview booking process, it usually indicates the system failed to transition to the next step (payment initiation or slot confirmation). This may happen in either workflow:
This guide explains common causes, diagnostic checks, and safe recovery actions.
## Common Troubleshooting Steps
| **What Might Be Wrong?** | **What to Do?** |
| :---------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Unable to Select Time After Choosing Date** | After selecting the exam date, check if the available time slots are visible. If not, refresh the calender page or return to the previous step and try again. |
| **Unable to Click “Confirm” After Selecting Date and Time** | Once both date and time are selected, ensure that the \*\*Confirm \*\*button is active. If not, refresh the page and try again. |
| **Unable to Proceed to Payment After Clicking “Confirm”** | If the Checkout page doesn’t load after confirming the slot, wait for a minute and then refresh. Check if the browser is blocking redirects to the payment gateway. |
| **Session Timeout or Inactivity** | Refresh the page and check for any session timeout message. Long inactivity can cause automatic logout, making the **Proceed** button unresponsive. |
| **Pop-up or Redirect Blocked** | Disable pop-up blockers or browser extensions that may be blocking the payment gateway redirect after slot selection. |
| **Persistent Loading or Blank Screen** | Wait few minutes for system synchronization before refreshing. Avoid reselecting the slot multiple times to prevent double bookings or slot lockouts. |
| **Weak or Unstable Internet** | Switch to a stable private connection (avoid public Wi-Fi) to prevent interruptions when loading the payment page. |
| **No Progress Despite Retries** | Note your browser/device details, slot time, and timestamp, and contact [Talview Support](https://www.talview.com/contact) with this information for backend review. |
## Additional Tips
* Use the latest version of a supported browser for smooth performance.
* Avoid repeating slot selections too quickly, which can create booking conflicts.
* Close extra browser tabs or multiple windows; simultaneous sessions can block the payment redirect.
If the \*\*Proceed \*\*button doesn’t respond, refresh and relogin before retrying. In most cases, this restores the workflow without needing technical support.
# Unable to Reschedule or Cancel Talview Exam Slot - Troubleshooting Guide
Source: https://docs.talview.com/candidates/scheduling-payments/diagnostics/unable-to-reschedule-or-cancel-talview-exam-slot-troubleshooting-guide
If you are **unable to reschedule or cancel your booked exam slot**, it may be due to policy restrictions, payment issues, or technical glitches in the *Pay and Book* or *Book and Pay* workflows.
## Common Troubleshooting Steps
| What might be wrong ? | **What to Do ?** |
| :------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Rescheduling/Cancellation Window Expired** | Verify if your request is within the allowed timeframe specified in the exam’s policy. Requests outside this window will be blocked. |
| **Incomplete or Failed Payment** | Ensure the original booking payment was successful. Only confirmed payments allow rescheduling or cancellation. |
| **Login or Authentication Issues** | Log in with the registered email ID and complete OTP verification before attempting changes. |
| **Reschedule Fee Not Paid** | Rescheduling may require a fee, depending on how closer to the exam is the candidate rescheduling (Airline logic) Make sure valid card/payment details are entered and the fee is processed. |
| **System Errors or Timeouts** | Refresh the page, clear browser cache, or try a different browser/device to avoid session-related issues. |
| **Incorrect or Expired Booking Link** | Use the links from your booking confirmation email for rescheduling or cancellation. |
| **Voucher Restrictions** | Some discounts or vouchers may restrict rescheduling or cancellation. Review the coupon terms. |
| **Browser Compatibility** | Ensure you are using an updated and supported browser for the Talview platform. |
## Additional Tips
* Act within the allowed reschedule/cancellation period to avoid blocked requests.
* Ensure your original payment is complete before initiating changes.
* Keep your booking confirmation email handy for reference.
* Have valid card/payment details ready if a reschedule fee applies.
Tip : Always attempt rescheduling or cancellation from the **official booking link** and on a **supported browser** to minimize technical issues.
# Unable to Reschedule Talview Booking – Troubleshooting Guide
Source: https://docs.talview.com/candidates/scheduling-payments/diagnostics/unable-to-reschedule-talview-booking-troubleshooting-guide
If you want to reschedule your Talview exam slot, but are facing issues or are unsure how to proceed, this guide explains common causes, diagnostic checks, and safe recovery actions.
## Common Troubleshooting Steps
| What might be wrong? | **What to Do?** |
| :--------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Rescheduling Close to Exam Time** | Rescheduling is allowed only up to a few hours before the scheduled exam, based on the provider’s policy. Check your eligibility window. |
| **No Available Slots** | Check the calendar for available slots. Rescheduling may be restricted if all slots are full or blocked. |
| **Reschedule Fee Not Received** | If you’ve paid a reschedule fee, it may still be processing. Payment usually confirms within a few hours, after which your new slot and confirmation email appear. |
| **Confirmation Not Received** | After rescheduling, you should receive an automated confirmation email. |
| **Rescheduling option restricted as per the policy** | In some cases, rescheduling may not be permitted depending on the exam provider’s policy. Always review the certification provider’s terms before attempting to reschedule. |
## Additional Tips
* Complete the rescheduling in one continuous session to avoid session timeouts.
* Use a supported, updated browser for smooth navigation.
* Automated notifications will confirm the new slot and any payment adjustments.
* Contact [Talview support](https://talview.freshdesk.com/support/solutions) if you encounter technical issues or delayed refunds.
***
Tip: Always complete the rescheduling in one session to avoid timeouts, and use a fully updated browser for best results.
# Voucher Applied but Discount not Reflected in Talview Payment
Source: https://docs.talview.com/candidates/scheduling-payments/diagnostics/voucher-applied-but-discount-not-reflected-in-talview-payment
If you applied a **voucher or coupon code** during your exam payment but the **discount isn’t showing** in your total fee, it may be due to code validity, currency mismatch, or workflow errors in *Pay and Book* or *Book and Pay* processes.
This guide helps you identify the cause and fix the issue before completing payment.
## Common Troubleshooting Steps
| **What might be wrong?** | **What to Do** |
| :---------------------------------- | :------------------------------------------------------------------------------------------------------------------------ |
| **Invalid or Mistyped Code** | Double-check that the coupon code matches exactly. Codes are case-sensitive. |
| **Expired or Usage-Limited Coupon** | Verify that the coupon is still valid and has not reached its usage limit (either per user or overall). |
| **Entered in Wrong Field** | Make sure the code is applied in the **discount/voucher field** before moving to payment. |
| **System Synchronization Delay** | Refresh or revisit the payment page after applying the code; the discount may appear after a short delay. |
| **Partial or Interrupted Payment** | If your earlier payment attempt was interrupted, retry with a fresh session before reapplying the coupon. |
| **Exam or Schedule Restriction** | Check if the coupon applies only to specific exams, sessions, or time frames. Refer to the coupon’s terms and conditions. |
## Additional Tips
* Enter the code exactly as provided, with no spaces or extra characters.
* Confirm eligibility and coupon validity period before use.
* If the discount does not appear, do not proceed with payment — contact your exam coordinator.
* Keep a screenshot or record of the coupon code and the page where you applied it.
* Always refresh your payment page before reapplying the voucher.
**Tip:** Discounts apply only after the coupon passes system validation. If it doesn’t show in your total amount, stop and recheck before paying.
# Wrong Phone Number or Email Entered – Troubleshooting Guide
Source: https://docs.talview.com/candidates/scheduling-payments/diagnostics/wrong-phone-number-or-email-entered-troubleshooting-guide
Entering an incorrect **email address** or **phone number** during exam booking may prevent you from receiving important updates like payment confirmations or exam details. If your **verification code** isn’t received or working, recheck your **email ID** for any spelling mistakes before retrying.
This guide explains how to identify the issue, perform quick checks, and correct your contact details safely.
## Common Troubleshooting Steps
| **What might be wrong?** | **What to Do?** |
| :---------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Incorrect Email Entered** | Log in to your Talview account and check your registered email address. If the email ID was sent from parent exam organization, reach out to them to correct the email address |
| **Incorrect Phone Number Entered** | Ensure the correct phone number is updated in your Talview profile. Wrong numbers can block SMS alerts and OTPs. You can ask them to contact [Talview support](https://talview.freshdesk.com/support/solutions) to correct phone number |
| **Both Email and Phone Incorrect** | Contact [Talview Support](https://talview.freshdesk.com/support/solutions) and provide your Candidate ID, Transaction Reference Number, and correct contact details for backend update. |
| **Emails Not Received Despite Correct Details** | Check your **Spam/Junk folders** for confirmation messages. Add Talview’s domain to your safe sender list. |
| **Tried to Rebook to Fix Details** | Avoid canceling and rebooking; this can cause duplicate payments. Always use the edit or support route for corrections. |
## Additional Tips
* Double-check all personal details (especially phone number and email) before submitting any exam registration form.
* Maintain documentation such as payment receipts, transaction IDs, and acknowledgment pages.
* Avoid multiple account creation unless instructed by official support; duplicate accounts can cause verification issues.
* Act quickly if you realize an error and reach out to [Talview Support](https://talview.freshdesk.com/support/solutions) with your registered name, exam name, and payment reference for immediate correction.
# What are the supported payment methods to pay for your exam?
Source: https://docs.talview.com/candidates/scheduling-payments/how-to/supported-payment-methods
When paying for your exam on Talview, you can choose from multiple secure payment options including credit cards, debit cards, PayPal, and Apple Pay (where available). This guide explains all supported payment methods and helps you select the right option based on your location and currency.
***
### Supported payment methods
When paying for your exam on Talview, you can choose from multiple secure payment options including credit cards, debit cards, PayPal, and Apple Pay (where available).
**1. Credit & debit cards**
Talview supports most major **domestic credit and debit cards** issued within your country.
These include:
* Visa
* Mastercard
* American Express
* Discover
* Local/regional card networks depending on your country
**Important:**
* **Paying in your local currency?** Any domestic card from your country will work. \
*For example, an Indian-issued domestic RuPay or Visa card can be used only when the exam is priced in INR.*
* **Paying in a different currency?** You need an internationally-enabled card
* Your bank may require 3D Secure verification or OTP authentication
**2. PayPal**
PayPal is supported for exam payments in regions where PayPal is operational.
You can complete your payment by selecting PayPal at checkout and logging into your account.
**3. Apple Pay**
Apple Pay is supported with **limited availability** and may appear only in regions where:
* Apple Pay is enabled by local regulations
* Your device and browser support Apple Pay
* Your card issuer supports Apple Pay transactions
* The payment gateway provider supports Apple pay wallet
If Apple Pay is available in your region, it will automatically appear as a payment option during checkout.
***
### Unsupported payment methods
If you're looking for one of these payment options, they are not currently available:
* Google Pay
* UPI
* Digital wallets other than Apple Pay and PayPal
* Net banking / online banking
* Buy Now Pay Later options (Affirm, Klarna, Afterpay, etc.)
* Cryptocurrency
* Cash, cheque, DD, or bank transfers
***
### Global availability
Our payment gateway partners support transactions across most countries and currencies.
Depending on your region, you may see additional local payment methods automatically enabled for convenience.
If a payment method is unavailable in your geography, it will not appear on the checkout screen.
**What happens after payment?**
Once your payment is successfully processed, you'll receive an immediate confirmation. Most payments are verified within seconds, though some payment methods may take a few minutes for authorization.
# Why am I not receiving the Ivy audio call?
Source: https://docs.talview.com/candidates/screening/ivy-audio-call/diagnostics/why-am-i-not-receiving-the-ivy-audio-call
If a call from Ivy, Talview's AI Interviewer, was expected but never reached you, it usually comes down to a network or phone settings issue rather than anything wrong with your application. This can happen due to poor coverage, call-blocking settings, or restrictions on international numbers.
In this article, you will identify the likely cause and resolve it so the call can reach you successfully.
***
#### 🔎 Troubleshooting Common Issues
| What Might Be Wrong | How to Fix It |
| :------------------------------------------------------------------------- | :---------------------------------------------------------------------------- |
| You were in a poor-network or no-coverage area when the call was attempted | Move to an area with strong network coverage and keep your phone reachable. |
| Your phone blocked the call through a spam filter or call-blocking app | Check and disable any spam-blocking or call-blocking app for unknown numbers. |
| Do Not Disturb was switched on | Turn off Do Not Disturb. |
| Your handset or network is set to block international or unknown numbers | Allow calls from international and unknown numbers in your phone settings. |
**Additional Tips**
If you still do not receive a call after trying the above, contact your recruiter to have it arranged again.
# Why can't I hear Ivy clearly during the call?
Source: https://docs.talview.com/candidates/screening/ivy-audio-call/diagnostics/why-cant-i-hear-ivy-clearly-during-the-call
If Ivy's voice, Talview's AI Interviewer, sounds muffled, delayed, or keeps cutting out during your call, this is usually caused by a weak network signal or a handset setting rather than an issue with the call itself.
In this article, you will identify the likely cause of the audio quality issue and take the appropriate steps to resolve it.
***
#### 🔎 Troubleshooting Common Issues
| What Might Be Wrong | How to Fix It |
| :------------------------------------------------------------ | :------------------------------------------------------------------------------------------------------------------------------------ |
| A weak network signal is affecting call quality | Move to an area with a stronger network signal. |
| Your phone's audio settings are affecting clarity | Increase your phone volume and turn off speaker mode if the audio is unclear. |
| A headset or earphones are causing the issue | Remove any headset or earphones that may be causing the issue, and use the handset directly. |
| The audio was too poor to continue and you disconnected early | Ivy will automatically call you again, up to 3 more times. Note that if you stay on the line without speaking, no retry is made. |
**Additional Tips**
If you expected a retry and did not receive one, contact your recruiter to arrange the call again.
# Why did I accidentally hang up during the Ivy audio call?
Source: https://docs.talview.com/candidates/screening/ivy-audio-call/diagnostics/why-did-i-accidentally-hang-up-during-the-ivy-audio-call
Ending your call with Ivy, Talview's AI Interviewer, by mistake doesn't mean you're unable to complete the hiring process. This can happen if you tap the wrong button or the call ends unintentionally partway through.
In this article, you will understand what to do next and what happens to the responses you'd already given.
***
#### 🔎 Troubleshooting Common Issues
| What Might Be Wrong | How to Fix It |
| :------------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------- |
| You ended the call unintentionally before completing the conversation | Ivy will automatically call you again, up to 3 more times. Do not try to call the number back, as it is inbound-only and will not connect you to anyone. |
| You had already completed about half of the conversation before hanging up | Ivy will not call again. Your responses so far are passed to the recruitment team. |
| You expected a retry and did not receive one | Contact your recruiter so the call can be arranged again. |
**Additional Tips**
Keep your phone reachable and stay in an area with good network coverage for the next attempt.
# Why did I reject the Ivy audio call thinking it was spam?
Source: https://docs.talview.com/candidates/screening/ivy-audio-call/diagnostics/why-did-i-reject-the-ivy-audio-call-thinking-it-was-spam
Declining a call from Ivy, Talview's AI Interviewer, because it looked like spam is a common and understandable mix-up, particularly since the call comes from an unknown US or UK number rather than a local one. This does not mean you have been removed from the hiring process or that your application has been affected in any way.
In this article, you will learn how to confirm that the call was genuine, what to expect from the next attempt, and how to avoid missing it again.
***
#### 🔎 Troubleshooting Common Issues
| What Might Be Wrong | How to Fix It |
| :------------------------------------------------------------------------------------------------------ | :------------------------------------------------------------------------------------------------------------- |
| The call came from an unknown US or UK number, which can appear to be spam if you were not expecting it | Confirm the call was genuine by checking that you have an active application with a hiring team. |
| You declined or did not answer the call | Ivy will automatically try again, up to 3 more times. Answer the next attempt when it comes through. |
| Your phone or network settings may block unknown or international numbers | Allow calls from unknown and international numbers in your phone settings so you do not miss the next attempt. |
**Additional Tips**
* If you miss all the retry attempts, contact your recruiter to have the call arranged again.
* If you remain unsure whether a call is genuine even after checking your application status, refer *How to confirm an Ivy audio call is genuine and not a fraud call* for further verification steps
# Why did my Ivy audio call drop while I was answering?
Source: https://docs.talview.com/candidates/screening/ivy-audio-call/diagnostics/why-did-my-ivy-audio-call-drop-while-i-was-answering
If your call with Ivy, Talview's AI Interviewer, cuts off while you're in the middle of answering a question, this is usually caused by an unstable network connection rather than anything you did. This can happen even after the conversation has been going smoothly for a while, since network conditions can change during the call.
In this article, you will understand what happened, what determines whether Ivy calls you back, and what to expect for the responses you'd already given.
***
#### 🔎 Troubleshooting Common Issues
| What Might Be Wrong | How to Fix It |
| :---------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------- |
| An unstable network dropped the call while you were mid-answer | Stay in an area with good network coverage and keep your phone reachable for the next attempt. |
| The drop happened early in the conversation | Ivy will automatically call you again, up to 3 more times. |
| You had already completed about half of the conversation | Ivy will not call again. Your responses up to that point are passed to the recruitment team. |
| Ivy's audio was cutting out or sounding unclear before the call dropped | This is often a sign of a weak signal. See *Why can't I hear Ivy clearly during the call?* for handset and network checks. |
**Additional Tips**
* If you expected a retry and did not receive one, contact your recruiter to resume the process.
* Avoid basements, lifts, and other low-coverage areas for the duration of the call to reduce the chance of a drop.
# Why does my Ivy audio call disconnect in the middle?
Source: https://docs.talview.com/candidates/screening/ivy-audio-call/diagnostics/why-does-my-ivy-audio-call-disconnect-in-the-middle
An Ivy audio call, powered by Talview's AI Interviewer, may disconnect before the conversation is complete. This is most often caused by a weak or unstable mobile network signal rather than an issue with the call itself.
In this article, you will identify the cause and understand what happens to your responses if this occurs.
***
#### 🔎 Troubleshooting Common Issues
| What Might Be Wrong | How to Fix It |
| :------------------------------------------------------------------------- | :----------------------------------------------------------------------------------------------------------------- |
| A weak or unstable network signal caused the call to drop midway | Move to a location with a stronger, more stable network signal and keep your phone reachable for the next attempt. |
| The call dropped early in the conversation | Ivy will automatically call you again, up to 3 more times, since the call was disconnected. |
| You had already completed about half of the conversation before it dropped | Ivy will not call again. Your responses so far are passed to the recruitment team for review. |
**Additional Tips**
If you expected a retry and did not receive one, contact your recruiter to complete the conversation.
# Why does the Ivy call keep dropping or breaking up?
Source: https://docs.talview.com/candidates/screening/ivy-audio-call/diagnostics/why-does-the-ivy-call-keep-dropping-or-breaking-up
If your call with Ivy, Talview's AI Interviewer, repeatedly drops or the audio keeps breaking up, the cause is almost always related to your network signal rather than the call itself. This can happen if you're in a low-coverage zone or if your signal fluctuates during the call.
In this article, you will identify what's causing the repeated drops and understand what happens if you're unable to complete the call.
***
#### 🔎 Troubleshooting Common Issues
| What Might Be Wrong | How to Fix It |
| :------------------------------------------------------------ | :--------------------------------------------------------------------------------------------------------------------------------------------------- |
| You're in a low-coverage zone or your signal is fluctuating | Move to a location with strong and stable coverage, ideally near a window or an open area. Avoid basements, lifts, and areas with known weak signal. |
| Other apps or downloads are affecting your line | Switch off any active downloads or calls on other apps that may affect your line. |
| A call dropped early | Ivy will automatically try again, up to 3 more times. |
| Half the conversation was already completed before it dropped | No further attempt is made, and your responses are sent to the recruitment team. |
**Additional Tips**
If repeated drops prevent you from completing the call and no further attempt reaches you, contact your recruiter.
# Why would Ivy call me again after I missed or dropped the call?
Source: https://docs.talview.com/candidates/screening/ivy-audio-call/diagnostics/why-would-ivy-call-me-again-after-i-missed-or-dropped-the-call
If you missed a call from Ivy, Talview's AI Interviewer, or the call dropped before you finished the conversation, you have not been automatically removed from the hiring process.
In this article, you will understand when Ivy retries a call, when it does not, and what to do if you need another attempt.
***
#### 🔎 Troubleshooting Common Issues
| What Might Be Wrong | How to Fix It |
| :------------------------------------------------------------------------------------------- | :----------------------------------------------------------------------------------------------- |
| You did not pick up, or you disconnected before completing the conversation | Ivy will automatically call you again, up to 3 more times, for a maximum of 4 attempts in total. |
| You picked up but did not speak, or you had already completed about half of the conversation | Ivy will not call again, and your responses are passed to the recruitment team. |
| No further call reaches you and you still need to complete the process | Contact your recruiter through your usual channel to request another attempt. |
**Additional Tips**
Keep your phone reachable and stay in an area with good coverage so the next retry attempt succeeds.
# Candidate Screening FAQs - Ivy Audio Call
Source: https://docs.talview.com/candidates/screening/ivy-audio-call/faqs/candidate-screening-faqs-ivy-audio-call
Ivy is an AI voice agent used by recruitment teams on Talview to speak with candidates over a phone call during the hiring process. If you've been told to expect an Ivy audio call, this guide answers the questions candidates most commonly ask before, during, and after the call.
From confirming the call is genuine to understanding what happens to your responses, use this FAQ as a quick reference so you know exactly what to expect.
***
### 1. About the call
**Q1. Why am I getting a call from an unknown number?**
Ivy calls are made from US or UK numbers, even if you're applying from elsewhere. This is expected and is linked to your active application, so it is not a spam call.
**Q2. Do I need an internet connection to take the call?**
No. It's a standard inbound phone call, the same as receiving any other call on your phone. You don't need data, Wi-Fi, or any app to take it.
**Q3. How long does the call take?**
The call usually lasts about 5 to 10 minutes, depending on how many questions apply to your application.
**Q4. What language will Ivy speak in?**
Ivy speaks in conversational English, and you can respond the same way you would in any normal phone conversation.
**Q5. What kind of questions will Ivy ask?**
Ivy asks screening, interview, availability, and scheduling questions related to your application, and may ask relevant follow-up questions based on how you respond. For a full breakdown of question types and examples, see *What questions does Ivy ask during the audio call?*
***
### 2. After the call
**Q1. Can I call back the number that called me?**
No. The number is inbound only, so calling it back will not connect you to anyone and will not trigger any action. For any queries, contact your recruiter.
**Q2. What happens after the call ends?**
Your responses are shared with the recruitment team, who review them and communicate the next steps in your hiring process, whether that's moving forward, requesting more information, or closing out the process.
**Q3. What should I do if I am not available when Ivy calls?**
If you do not pick up, Ivy will automatically try to call you again, up to 3 more times, for a maximum of 4 attempts in total. If you are unable to take any of the attempts, contact your recruiter through your usual channel to arrange the call at a suitable time.
***
#### 3. Verifying the call
**Q1. Will Ivy ask for sensitive information like passwords, OTPs, or payment details?**
No. Ivy only asks hiring related questions. It will never ask for passwords, OTPs, bank details, or payment of any kind, so if a call asks for these, do not share them.
**Q2. Who should I contact if I still have questions about my call?**
Contact your recruiter or the recruitment team through the same channel they've used to communicate with you. They can confirm any details about your Ivy audio call and guide you on next steps.
***
# How Ivy retries a call
Source: https://docs.talview.com/candidates/screening/ivy-audio-call/how-tos/how-ivy-retries-a-call
If your call with Ivy doesn't connect or ends early, Talview's system may retry the call automatically. In this article, you will learn when Ivy retries a call and when it does not.
***
### 🔁 When Ivy will call you again
* You did not pick up the call.
* You picked up but disconnected the call before completing the conversation.
In these cases, Ivy will automatically try again up to 3 more times, for a maximum of 4 attempts in total.
### 🚫 When Ivy will not call you again
* You picked up but did not speak during the call.
* You had already completed about half of the conversation before the call ended.
In these cases, whatever responses were captured are passed to the recruitment team, and no further attempt is made.
**Additional Tips**
To make sure you don't miss a retry, keep your phone reachable and stay in an area with good network coverage.
***
**📚 Related Articles**
* [What is an Ivy audio call](https://docs.talview.com/candidates/screening/ivy-audio-call/how-tos/what-is-an-ivy-audio-call)
* [What to expect during an Ivy audio call](https://docs.talview.com/candidates/screening/ivy-audio-call/how-tos/what-to-expect-during-an-ivy-audio-call)
* [**Why would Ivy call me again after I missed or dropped the call?**](https://docs.talview.com/candidates/screening/ivy-audio-call/diagnostics/why-would-ivy-call-me-again-after-i-missed-or-dropped-the-call)
# How to prepare for an Ivy audio call
Source: https://docs.talview.com/candidates/screening/ivy-audio-call/how-tos/how-to-prepare-for-an-ivy-audio-call
A little preparation before your **Ivy audio call** can help the conversation go smoothly without interruptions. In this article, you will learn what to do before your call so you're ready when Ivy calls.
***
#### Step-by-Step Guide
1. **Choose a quiet location** Find a calm space with minimal background noise so Ivy can clearly hear your responses, and you can clearly hear the questions.
2. **Ensure strong network coverage** The call is a normal phone call and depends on your mobile network. Stay in an area with a strong signal. Avoid basements, lifts, and low-coverage zones.
3. **Set aside enough time** The call typically lasts 5 to 10 minutes. Make sure you have this time free and won't be disturbed.
4. **Keep your details ready** Have any relevant information handy, such as your availability for interviews or scheduling, so you can answer without delay.
5. **Answer clearly** Speak in clear English at a normal pace. If you don't understand a question, you can ask Ivy to repeat it.
**Additional Tips**
You don't need an internet connection for this call. It's a standard inbound phone call and doesn't require data, Wi-Fi, or any app.
***
**📚 Related Articles**
* [What is an Ivy audio call?](https://docs.talview.com/candidates/screening/ivy-audio-call/how-tos/what-is-an-ivy-audio-call)
* [What to expect during an Ivy audio call](https://docs.talview.com/candidates/screening/ivy-audio-call/how-tos/what-to-expect-during-an-ivy-audio-call)
* [**How to verify an Ivy audio call is genuine**](https://docs.talview.com/candidates/screening/ivy-audio-call/how-tos/how-to-verify-an-ivy-audio-call-is-genuine)
# How to verify an Ivy audio call is genuine
Source: https://docs.talview.com/candidates/screening/ivy-audio-call/how-tos/how-to-verify-an-ivy-audio-call-is-genuine
If the call comes from an unknown international number, you may be unsure whether it's genuine. Talview helps you confirm that an Ivy audio call is a legitimate part of your hiring process. In this article, you will learn how to confirm that an Ivy audio call is genuine and not a fraud call.
***
#### Step-by-Step Guide
1. **Check that you have an active application** An Ivy call is only made to candidates who have applied for a role or are already in a hiring process. If you have a live application with us, the call is expected.
2. **Confirm the type of questions being asked** Ivy only asks hiring-related questions, such as screening, interview, availability, and scheduling questions. A genuine Ivy call stays within these topics.
3. **Watch for what Ivy will never ask** Ivy will never ask for passwords, OTPs, bank details, card numbers, or any payment. If a call asks for any of these, it's not a genuine Ivy call and you should not share the information.
4. **Cross-check with your recruiter** If you're still unsure, contact your recruiter or the recruitment team through the official channel they used to communicate with you, and confirm the call.
**Additional Tips**
You cannot call the number back to verify it. The number is inbound-only, so use your recruiter contact for any confirmation.
***
**📚 Related Articles**
* [What is an Ivy audio call](https://docs.talview.com/candidates/screening/ivy-audio-call/how-tos/what-is-an-ivy-audio-call)
* [What questions does Ivy ask during an audio call](https://docs.talview.com/candidates/screening/ivy-audio-call/how-tos/what-questions-does-ivy-ask-during-an-audio-call)
# What is an Ivy audio call
Source: https://docs.talview.com/candidates/screening/ivy-audio-call/how-tos/what-is-an-ivy-audio-call
Ivy is an AI voice agent used by our recruitment team to speak with candidates over a normal phone call. Instead of a human recruiter making an initial call, Ivy calls you to ask a few questions about your application and gather information needed to move you to the next stage.
The call is fully conversational. Ivy speaks in natural English, asks you questions, listens to your answers, and asks relevant follow-up questions based on what you say. You simply respond as you would in any phone conversation.
An Ivy call is typically used for one or more of the following:
* Initial screening questions about your profile and experience
* Interview-style questions relevant to the role
* Checking your availability
* Helping schedule the next steps in your hiring process
***
### 📤 What happens with your responses
Once the call ends, your responses are shared with the recruitment team handling your application. They review what you said and get back to you with the next steps, whether that's moving forward to another round, requesting more information, or closing out the process.
**Additional Tips**
* If you're unsure whether a call is genuine, refer [*How to verify an Ivy audio call is genuine*](https://docs.talview.com/candidates/screening/ivy-audio-call/how-tos/how-to-verify-an-ivy-audio-call-is-genuine)
* Ivy calls typically come from a US or UK number.
***
📚 **Related Articles**
* [What to expect during an Ivy audio call](https://docs.talview.com/candidates/screening/ivy-audio-call/how-tos/what-to-expect-during-an-ivy-audio-call)
* [How to prepare for an Ivy audio call](https://docs.talview.com/candidates/screening/ivy-audio-call/how-tos/how-to-prepare-for-an-ivy-audio-call)
* [**What questions does Ivy ask during an audio call**](https://docs.talview.com/candidates/screening/ivy-audio-call/how-tos/what-questions-does-ivy-ask-during-an-audio-call)
# What questions does Ivy ask during an audio call
Source: https://docs.talview.com/candidates/screening/ivy-audio-call/how-tos/what-questions-does-ivy-ask-during-an-audio-call
Knowing what to expect can help you feel confident during your call. Talview designed Ivy to ask relevant, conversational questions rather than follow a rigid script. In this article, you will learn the types of questions Ivy may ask and how the conversation is structured.
***
#### 💬 How the conversation works
Ivy asks questions in conversational English, one at a time. After you answer, Ivy may ask a follow-up question based on your response to understand it better. You respond naturally, just as you would with a person on a phone call.
> **Note**: There are no trick questions. Answer honestly and clearly, and ask Ivy to repeat anything you didn't understand.
#### 🗂️ Types of questions Ivy may ask
* **Screening questions**: Basic questions about your background, experience, and suitability for the role.
* **Interview questions**: Role-relevant questions that help assess your fit.
* **Availability questions**: Questions about when you are available for the next steps.
* **Scheduling questions**: Questions that help arrange the timing of upcoming interviews or stages.
#### Example of a follow-up
If Ivy asks about your notice period and you say you're currently serving one, Ivy may follow up by asking your last working day. This back-and-forth is normal and expected.
***
**📚 Related Articles**
* [What is an Ivy audio call](https://docs.talview.com/candidates/screening/ivy-audio-call/how-tos/what-is-an-ivy-audio-call)
* [What to expect during an Ivy audio call](https://docs.talview.com/candidates/screening/ivy-audio-call/how-tos/what-to-expect-during-an-ivy-audio-call)
* [**How to verify an Ivy audio call is genuine**](https://docs.talview.com/candidates/screening/ivy-audio-call/how-tos/how-to-verify-an-ivy-audio-call-is-genuine)
# What to expect during an Ivy audio call
Source: https://docs.talview.com/candidates/screening/ivy-audio-call/how-tos/what-to-expect-during-an-ivy-audio-call
If you've applied for a role and are told to expect a call from Ivy, this article walks you through the entire experience from start to finish. Knowing what happens at each stage of the call can help you feel prepared and recognize that everything happening is a normal part of the process, not something to be concerned about.
This article explains what happens from the moment your phone rings until the Ivy call ends, so you know exactly how the conversation will flow.
***
### **Step-by-step Guide:**
1. **Receiving the call** You'll get an incoming call, usually from a US or UK number. This is expected. Answer the call as you would any normal phone call.
2. **Starting the conversation** Ivy will introduce itself and explain the purpose of the call. Listen to the introduction before you begin answering.
3. **Answering the questions** Ivy will ask you a series of questions in conversational English. These may cover screening, interview, availability, or scheduling topics. Answer each question naturally and clearly.
4. **Responding to follow-up questions** Based on your answers, Ivy may ask follow-up questions to understand your responses better. This is a normal part of the conversation.
5. **Ending the call** Once Ivy has gathered the required information, the call will end automatically. The full conversation usually lasts about 5 to 10 minutes.
**Additional Tip**
Stay in a quiet place with good network coverage for the full duration so the conversation isn't interrupted.
📚 **Related Articles**
* [What is an Ivy audio call?](https://docs.talview.com/candidates/screening/ivy-audio-call/how-tos/what-is-an-ivy-audio-call)
* [How to prepare for an Ivy audio call](https://docs.talview.com/candidates/screening/ivy-audio-call/how-tos/how-to-prepare-for-an-ivy-audio-call)
* [What questions does Ivy ask during the audio call?](https://docs.talview.com/candidates/screening/ivy-audio-call/how-tos/what-questions-does-ivy-ask-during-an-audio-call)
# Why does it say my camera streaming has stopped?
Source: https://docs.talview.com/candidates/system-diagnostics/Why-does-it-say-my-camera-streaming-has-stopped
If you see a message saying your camera streaming has stopped during a proctored session on Talview, it usually means the connection to your secondary device's camera was interrupted - either because you stopped it yourself or because of a connection issue. In this article, you'll find the most common causes and fixes to get your camera streaming back up.
***
#### 🔎 Troubleshooting Common Issues
| **What Might Be Wrong** | **How to Fix It** |
| ---------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| You manually stopped the stream | If you clicked the recording button to pause your camera streaming, this is expected. Click the same button again to resume - the stream should reconnect right away. |
| Your device lost its network connection | Check that your smartphone or tablet is still connected to Wi-Fi or mobile data. If the connection dropped, reconnect to a stable network and click the recording button to restart the stream. |
| The secondary device went to sleep or the browser tab was closed | Make sure your secondary device's screen is still on and the browser tab running the session hasn't been closed or minimized for too long. Reopen it and reconnect if needed. |
| Camera permission was revoked or blocked | Check your device's camera permissions for the browser you're using. If access was turned off, re-enable it in your device settings and refresh the page. |
| Low battery triggered a device restriction | Some devices restrict camera access when the battery is critically low. Plug in your device and try reconnecting the stream. |
***
**Additional Tips**
* The **"Camera streaming stopped"** message clears automatically once the stream reconnects successfully, you don't need to refresh the page.
* If you didn't intentionally stop the stream and it keeps disconnecting, this is likely a network or device issue rather than something wrong with the button itself.
* Keep your secondary device plugged in and on a stable network throughout the session to avoid unexpected disconnections.
# Why is my camera not being detected or found?
Source: https://docs.talview.com/candidates/system-diagnostics/Why-is-my-camera-not-being-detected-or-found
If your camera isn't being detected or you're seeing a "no camera found" error during your assessment, Talview may not be able to access it due to permission blocks, connection issues, or driver problems. Without camera access, you won't be able to complete identity verification or proctored test requirements. This article will help you resolve the issue before your session begins.
***
### 🔎 Troubleshooting Common Issues
| **What Might Be Wrong** | **How to Fix It** |
| --------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Browser doesn't have camera permissions** | [Grant camera access to your browser.](https://docs.talview.com/candidates/system-diagnostics/secondary-camera-setup-guide#how-to-enable-permissions-if-blocked)**Chrome/Edge:** Click the lock icon in the address bar > **Site settings** > **Camera** > **Allow**. **Safari:** **Safari** > **Settings for This Website** > **Camera** > **Allow**. Refresh the page completely after granting permissions. |
| **Another app is using the camera** | Close all apps that might be accessing your camera: Zoom, Teams, Skype, FaceTime, Slack, Discord, or any camera/video apps. **Windows:** Open **Task Manager** (`Ctrl+Shift+Esc`) > **Processes** tab > find and end video conferencing apps. **Mac:** Open **Activity Monitor** > search for these apps > click **X** to quit. Restart your browser after closing conflicting apps. |
| **Browser page has cached old permission settings** | Do a hard reload to refresh permission settings. **Windows:** Press `Ctrl+Shift+R` or `Shift+F5`. **Mac:** Press `Cmd+Shift+R`. If the camera is still not detected, close all browser tabs and restart the browser completely. |
| **OS hasn't granted camera access to the browser** | **Windows:** Go to **Settings** > **Privacy & Security** > **Camera** > ensure **"Camera access"** is ON and your browser is in the allowed list. **Mac:** Go to **System Settings** > **Privacy & Security** > **Camera** > check the box next to your browser (**Chrome**, **Safari**, or **Edge**). |
| **Camera is disabled in Device Manager (Windows)** | Open **Device Manager** > expand **"Cameras"** or **"Imaging Devices"** > if your camera shows a down arrow or yellow triangle, right-click it > **Enable device** or **Update driver**. Restart your computer after making changes. |
| **Physical privacy shutter is blocking the camera** | Check if your laptop has a physical privacy shutter near the webcam and slide it to the open position. Remove any tape, stickers, or privacy covers from the camera lens. |
| **USB port isn't providing enough power** | Try connecting your external webcam to a different USB port, plugging directly into your computer rather than through a USB hub. For laptops, ensure you're plugged into AC power as battery mode can sometimes limit USB power output. |
| **Multiple cameras are confusing the system** | In your browser's site settings, explicitly select the camera you want to use. Disconnect any cameras you're not using, leaving only the one intended for your assessment. |
| **Antivirus or security software is blocking the camera** | Add your browser to the antivirus exceptions list. **Windows Defender:** Go to **Windows Security** > **Virus & Threat Protection** > **Manage Settings** > **Add Exclusions** > add your browser. For third-party antivirus, check its documentation for allowing camera access. |
| **Camera drivers are outdated or corrupted** | **Windows:** Open **Device Manager** > expand **"Cameras"** or **"Imaging Devices"** > right-click your camera > **Update driver** > **Search automatically for drivers**. If that doesn't work, select **Uninstall device** and restart your computer to reinstall. **Mac:** Go to **System Settings** > **Software Update** and install any available updates. |
***
**Additional Tips:**
* Restart your device before your assessment after making any driver or permission changes to ensure all settings take effect.
* Test your camera using your system's built-in camera app (**Windows Camera** or **Mac Photo Booth**) before starting your assessment to confirm it's working.
* If you're using an external USB webcam, ensure it's a modern model (2018 or newer) with up-to-date drivers, as older webcams may have compatibility issues with modern systems.
* Keep your USB webcam cable as short as possible and avoid extension cables, which can cause connection instability.
# How to enable device permissions for camera and microphone?
Source: https://docs.talview.com/candidates/system-diagnostics/camera-and-microphone/how-to-enable-device-permissions-for-camera-and-microphone
If your camera or microphone is not accessible, even after enabling browser permissions are set, the issue may be related to **device-level privacy or hardware settings**. Without these permissions, your test or interview cannot proceed.
This article explains how to enable camera and microphone permissions on **desktop/laptop devices** as well as on a **mobile phone used as a secondary camera**
## ✅ Common Causes and Fixes
| What Might Be Wrong | What You Can Do |
| :------------------------------------------------------------------------ | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| OS-level privacy settings are blocking access (Desktop/Laptop) | **Windows:** Go to `Settings → Privacy → Camera / Microphone `and allow access for apps and your browser. **Mac:** Go to `System Settings → Privacy & Security → Camera / Microphone `and allow access for Chrome or Safari. |
| OS-level privacy settings are blocking access (Mobile / Secondary Device) | **Android:** Go to `Settings → Privacy → Permission Manager → Camera / Microphone` and allow access for Chrome or the browser being used. **iOS:** Go to `Settings → Safari → Camera / Microphone and set access to Allow.` |
| Hardware access is disabled globally | Ensure **Camera** and **Microphone** access toggles are turned **ON** at the device level (desktop or mobile). |
| Using an external device that isn’t selected | In browser settings, select the correct external camera or microphone from the device dropdown. |
| Another app is using the camera or mic | Close apps such as Zoom, Skype, Teams, OBS, or virtual camera tools on both desktop and mobile devices. |
| Device driver issue (Windows only) | Update camera and microphone drivers using **Device Manager**. |
| Work laptop or managed mobile device restrictions | Company-managed devices may restrict camera or mic access. Contact your IT administrator to enable permissions for your browser or test application. |
## 📱 Mobile Device (Secondary Device) Permission Steps
If you are using a **mobile phone as a secondary camera**, ensure the following permissions are enabled:
### **On Android (Chrome Browser)**
1. Open **Settings** on your phone
2. Go to **Privacy → Permission Manager**
3. Select **Camera** and set browser access to **Allow while using the app**
4. Select **Microphone** and allow access for the same browser
5. Open Chrome and refresh the exam page
### **On iPhone (Safari Browser)**
1. Open **Settings**
2. Scroll to **Safari**
3. Enable **Camera** and **Microphone** access
4. Set permissions to **Allow** or **Ask**
5. Return to the exam page and refresh
> ⚠️ If camera or microphone permissions are denied on your mobile device, the secondary camera connection will fail, and you may be unable to continue.
***
## ✅ Final Check: Confirm Device-Level Permissions
Before retrying your test:
* Confirm system-level permissions are enabled for your browser on **both primary and secondary devices**
* Ensure no other application is using the camera or microphone
* Run a device test
You should be able to:
* See your **video feed**
* Observe **audio input bars moving** when you speak
If the issue persists after completing these steps, restart the device and repeat the permission checks before rejoining the test.
***
# How to fix “Microphone not found” error?
Source: https://docs.talview.com/candidates/system-diagnostics/camera-and-microphone/how-to-fix-microphone-not-found-error
Encountering a **'Microphone not found' error** during onboarding can prevent you from proceeding with your assessment. This error typically occurs due to hardware connection issues, browser permission settings, incorrect input selection, or conflicting applications that are already using your microphone.
This article helps you resolve microphone detection issues so you can complete your session successfully.
***
## 🔎 Troubleshooting Common Issues
| **What might be wrong** | **How to fix it** |
| :--------------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| External microphone or headset not properly connected | Ensure your external microphone or headset is securely plugged into your computer and powered on. Check that all cables are firmly connected. If using USB, try a different port. If using Bluetooth, reconnect the device. |
| Browser does not have permission to access your microphone | Click the **Lock icon 🔒** next to the URL in your browser's address bar, select **'Site settings'** or **'Permissions for this site'**, and set microphone permission to **'Allow'.** |
| Another application is currently using your microphone | Close applications like Skype, Zoom, or Microsoft Teams that might be accessing your microphone. Check `Task Manager (Windows)` or `Activity Monitor (Mac)` for background processes using the microphone. |
| System privacy settings blocking microphone access | Go to `Settings > Privacy & Security > Microphone`, and enable **'Microphone access'**, **'Let apps access your microphone'**, and **'Let desktop apps access your microphone'.** |
| Incorrect microphone selected as default input device | Open your system sound settings and ensure the correct microphone is selected as the default input device. Also verify the correct microphone is selected in browser microphone settings. |
| Browser page not refreshed after permission changes | Perform a hard reload by pressing `Ctrl + Shift + R (Windows)` or `Command + Shift + R (Mac)` to apply the new microphone settings. |
### **Additional Tips**
* Test your microphone using your system’s sound settings to confirm input levels respond when you speak.
* Restart your browser completely after adjusting microphone permissions to ensure settings take effect.
* If using a corporate or school network, check with your IT team about firewall or device control settings that might be blocking microphone access.
* If the issue persists after trying all steps, try using a different supported browser such as Google Chrome, Microsoft Edge, or Mozilla Firefox.
* Restart your device if the microphone is still not detected after completing all troubleshooting steps.
# What to do if your camera is not found?
Source: https://docs.talview.com/candidates/system-diagnostics/camera-and-microphone/what-to-do-if-your-camera-is-not-found
Encountering a **'Camera not found' error** during an onboarding can prevent you from proceeding with your assessment. This error typically occurs due to hardware connection issues, browser permission settings, or conflicting applications that are already using your camera.
This article helps you resolve camera detection issues so you can complete your session successfully.
## 🔎Troubleshooting Common Issues
| **What might be wrong** | **How to fix it** |
| :----------------------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| External camera not properly connected to your device | Ensure your external camera is securely plugged into your computer and powered on. Check that all cables are firmly connected. |
| Browser does not have permission to access your camera | Click the lock icon next to the URL in your browser's address bar, select 'Site settings' or 'Permissions for this site' and set camera permission to '**Allow'.** |
| Another application is currently using your camera | Close applications like Skype, Zoom, Microsoft Teams, or messaging apps that might be accessing your camera. Check `Task Manager (Windows)` or` Activity Monitor (Mac)` for background processes using the camera. |
| System privacy settings blocking camera access | Go to `Settings > Privacy & Security > Camera`, and enable 'Camera access', 'Let apps access your camera', and 'Let desktop apps access your camera'. |
| Browser page not refreshed after permission changes | Perform a hard reload by pressing` Ctrl + Shift + R (Windows)` or `Command + Shift + R (Mac)` to apply the new camera settings. |
### **Additional Tips:**
* [Test your camera](/candidates/system-diagnostics/run-diagnostics) to confirm it's functioning properly before starting the onboarding process.
* Restart your browser completely after adjusting camera permissions to ensure settings take effect.
* If using a corporate or school network, check with your IT team about firewall settings that might be blocking Talview's camera access.
* If the issue persists after trying all steps, try using a different browser (Chrome, Edge, or Firefox are recommended)
# Why did my Audio check fail?
Source: https://docs.talview.com/candidates/system-diagnostics/camera-and-microphone/why-did-my-audio-check-fail
We use your microphone to capture responses and ensure assessment integrity. Any disruption can prevent the test from starting or recording correctly. Resolving audio errors avoids delay and technical issues during the exam.
Follow this guide to identify and fix common microphone issues before starting your assessment.
## ✅ Common causes and fixes
| What might be wrong? | What to do ? |
| :------------------------------------ | :--------------------------------------------------------------------- |
| **Microphone not connected** | External or USB microphones may not be recognized. |
| **Incorrect input device selected** | System or browser may default to a different microphone. |
| **Muted microphone** | Mic may be muted physically or via software. |
| **Permissions not granted** | Browser or OS may block microphone access. |
| **Conflicting applications** | Apps like Zoom or Skype may conflict the mic access. |
| **Low volume or environmental noise** | Mic sensitivity or background noise can prevent detection. |
| **Audio output routing issue** | Incorrect playback device can interfere with instructions or feedback. |
### Additional Tips
* Grant microphone permissions in your browser (click the lock icon)
* Select the correct microphone in system sound settings
* Close other apps that may be using the microphone
* Use wired headphones with a built-in mic
* Sit in a quiet, furnished room
* Always [test ](https://video-diagnostics.talview.org/) your microphone before starting the exam.
## 📚 Related Articles
Still seeing the warning? Try these steps:
* [Preparing Your Audio Setup for the Test](https://docs.talview.com/candidates/system-diagnostics/preparing-your-audio-setup-for-the-test)
* [**Why does using headphones improve test audio quality?**](https://docs.talview.com/candidates/system-diagnostics/why-does-using-headphones-improve-test-audio-quality)
# Why is my mobile phone (secondary device) camera not working?
Source: https://docs.talview.com/candidates/system-diagnostics/camera-and-microphone/why-is-my-mobile-phone-secondary-device-camera-not-working
If your mobile phone camera is not working, not connecting, or getting disconnected when used as a **secondary device** during a proctored assessment or live interview, it may be due to permission issues, network instability, battery restrictions, or device settings.
This guide helps you troubleshoot common mobile camera issues and ensure your secondary device stays connected and functional throughout your assessment or interview.
## ✅ Common causes and fixes
| **What might be wrong** | **How to fix it** |
| :--------------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Camera permission not granted to the browser or camera app | Ensure camera access is allowed on your phone for the browser or camera app used to connect the secondary device. **Android:** Settings > Apps > Browser (Chrome) or Camera app > Permissions > Allow Camera. **iOS:** Settings > Privacy & Security > Camera > Enable access for the relevant browser or scanning app. Close and reopen the app, then re-scan the QR code if prompted. |
| Camera permission blocked after first attempt | If camera access was denied earlier, the phone may continue blocking it. **Android:** Settings > Apps > Browser > Permissions > Camera > Allow. **iOS:** Settings > Safari (or relevant browser) > Camera > Allow. Restart the browser and reconnect the secondary camera. |
| Camera app or browser closed or minimized | The secondary camera must remain active throughout the assessment or interview. Keep the camera app or browser open and in the foreground. Do not switch apps, lock the screen, or minimize the browser once the session has started. |
| Screen auto-lock or battery saver enabled | Auto-lock or power-saving modes can interrupt the camera feed. Disable auto-lock or extend screen timeout. Turn off Battery Saver / Low Power Mode. Keep the phone connected to a charger for the entire session. |
| Unstable or weak internet connection | A poor network can cause camera freezes or disconnections during monitoring or interviews. Use a stable Wi-Fi connection where possible. Avoid switching between Wi-Fi and mobile data. Move closer to the router to improve signal strength. |
| QR code session expired or camera disconnected | If the camera disconnects, follow the on-screen instructions on your primary device. Re-scan the QR code to reconnect the secondary camera and resume the session as instructed. |
| Camera lens blocked or incorrect phone positioning | A blocked or unclear camera view may affect monitoring or interview visibility. Remove any covers, stickers, or accessories blocking the lens. Position the phone in landscape mode on a stable surface with a clear view of you and your primary screen. |
| Phone overheating during extended use | Long camera usage during assessments or interviews may cause overheating. Remove the phone case if needed. Keep the phone in a cool, ventilated area away from direct sunlight. Close background apps to reduce load. |
| Multiple apps accessing the camera | Other apps may interfere with camera access. Close video calling, social media, and camera-based apps before starting. Restart the phone to clear background processes, then reconnect the secondary camera. |
| Outdated or unsupported phone software | Older operating systems may not support continuous camera streaming. **Android:** Settings > Software Update. **iOS:** Settings > General > Software Update. Restart the phone after updating and reconnect the secondary camera. |
### **Additional tips:**
* Restart your mobile phone before the exam to clear background processes
* Remove any phone case or cover that may block the camera lens
* Avoid notifications, incoming calls, or switching apps during the exam, as this may disconnect the camera feed
# Why is my mobile (secondary device) microphone not working?
Source: https://docs.talview.com/candidates/system-diagnostics/camera-and-microphone/why-is-my-mobile-secondary-device-microphone-not-working
If your mobile phone microphone is not working, not detected, or stops capturing audio when used as a **secondary device** during your assessment, it is usually due to permission restrictions, device settings, hardware blocks, or connectivity issues. Since the secondary device may require audio capture for session and environment monitoring, microphone issues can impact exam continuity.
This guide helps you identify common mobile microphone issues and explains how to fix them to ensure uninterrupted audio capture.
## ✅ Common causes and fixes
| **What might be wrong** | **How to fix it** |
| :----------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Another app is using the microphone | Close all apps that may be accessing the microphone. **Android:** Open Recent Apps and close all background apps. **iPhone:** Swipe up from the bottom and close all apps, then reopen the secondary device connection link. |
| Microphone permissions are not granted | Ensure the browser or app used for the secondary device has microphone access. **Android:** `Settings > Privacy > Permission manager > Microphone > Allow` access for the browser or app being used. **iPhone:** `Settings > Privacy & Security > Microphone > Enable` access for the browser (Safari/Chrome) or app being used. |
| Browser or app microphone access is blocked | Use a supported mobile browser or the recommended camera/microphone app. Avoid using in-app browsers (for example, opening links inside Gmail, WhatsApp, or SMS apps). |
| Phone is muted or volume settings are restricted | Ensure the phone is not on silent mode or Do Not Disturb. Increase system volume and disable any sound restrictions before starting the exam. |
| Headphones or Bluetooth devices connected | Disconnect wired headphones, earphones, or Bluetooth devices, as the phone may route audio input to them instead of the built-in microphone. If required, reconnect only after confirming which microphone is active. |
| Phone locked or screen turned off | Keep the phone screen ON throughout the exam. **Android:** `Settings > Display > Screen timeout > Set to a longer duration or “Never.”` **iPhone:** `Settings > Display & Brightness > Auto-Lock > Set to “Never” or the maximum available time.` |
| Network connection is unstable | A weak or unstable network may disrupt audio streaming. Connect to a stable Wi-Fi network. Avoid switching between Wi-Fi and mobile data during the exam. |
| Microphone blocked or obstructed | Ensure the microphone opening is not covered by a phone case, dirt, or debris. Remove thick cases or covers that may block the mic. |
| OS or browser version is outdated | Update your mobile operating system to the latest version. Update your mobile browser from the App Store or Play Store to ensure compatibility. |
### **Additional tips:**
* Restart your mobile phone before the exam to clear background processes
* Test the microphone by recording a short voice note or using a voice recorder app before starting the assessment
* Speak clearly and avoid placing the phone too far away from you
* Avoid notifications, incoming calls, or switching apps during the exam, as this may interrupt microphone access
# List of supported devices for mobile phone
Source: https://docs.talview.com/candidates/system-diagnostics/device-compatibility-and-access/list-of-supported-devices-for-mobile-phone
Talview uses a mobile phone as a **secondary device** to enable enhanced proctoring and environment monitoring during assessments. To ensure a stable connection and uninterrupted camera and microphone feed, your mobile phone must meet the supported device and system requirements listed below. Using unsupported devices may prevent the secondary camera from connecting or functioning correctly.
## ✅ Supported Mobile Phones (Secondary Device)
You may use a **smartphone** as a secondary device if your organization has enabled secondary camera usage for the assessment.
### **Minimum Device Requirements**
| **Component** | **Requirement** |
| :-------------------- | :-------------------------------------------------------------- |
| Device Type | Smartphone (Android or iOS) |
| Operating System (OS) | Android 10 or later iOS 15 or later |
| Camera | Functional rear camera (mandatory) |
| Microphone | Built-in microphone (mandatory) |
| Browser | Latest version of Google Chrome or Safari |
| Network | Stable Wi-Fi or mobile data connection |
| Power | Device must remain connected to a charger during the assessment |
## ❌ Not Supported as Secondary Devices
The following devices are not supported for use as a secondary device:
* Feature phones (non-smartphones)
* Laptops or desktops
* Chromebooks (Google Chrome OS)
* Emulators or virtual devices
### **Before You Begin: Final Checks**
Before starting your assessment, ensure that:
* Your organization has enabled the use of a mobile phone as a secondary device
* Camera and microphone permissions are allowed for the browser being used
* The phone battery is fully charged and connected to a power source
* Auto-lock, battery saver, and low power modes are disabled
* The phone is positioned in landscape mode with a clear view of you and your primary screen
* You have a stable and uninterrupted internet connection
Using a supported mobile phone that meets these requirements helps ensure smooth secondary camera setup, continuous monitoring, and a secure assessment experience.
# List of supported OS for mobile phone
Source: https://docs.talview.com/candidates/system-diagnostics/device-compatibility-and-access/list-of-supported-os-for-mobile-phone
Talview uses a mobile phone as a **secondary device** to support enhanced proctoring by capturing additional camera and audio input during assessments. This secondary device operates alongside your primary device to provide extended visibility of your test environment.
To ensure *compatibility, stability, and uninterrupted monitoring, your mobile phone must run a supported operating system (OS)*. Using an unsupported or outdated OS can result in connection failures, camera interruptions, or session termination.
## ✅ Supported Mobile Operating Systems
The following mobile operating systems are supported **when used as a secondary device**, provided your organization has enabled secondary camera usage for the assessment.
### **Minimum OS Requirements:**
| Mobile Platform | Supported Version |
| :-------------- | :---------------------- |
| Android | **Android 10 or later** |
| iOS | **iOS 15 or later** |
## ❌ Unsupported Operating Systems
The following operating systems and configurations are **not supported** for use as a secondary device:
* Android versions **below Android 10**
* iOS versions **below iOS 15**
* Custom ROMs or modified OS builds (rooted or jailbroken devices)
* Emulated, virtual, or simulator-based mobile operating systems
* Devices running enterprise-restricted or kiosk-mode OS configurations
Using any of the above may prevent the secondary device from connecting or remaining active during the assessment.
### Additional OS Requirements for Secondary Devices
For reliable secondary camera performance, ensure the following OS-level conditions are met on your mobile phone:
* Battery optimization, low power mode, and data saver features are **disabled**
* Auto-lock and screen timeout are **turned off or extended**
* The device allows background camera and microphone usage
* The OS permits continuous browser or app activity without interruption
Aggressive OS restrictions may suspend the camera feed or disconnect the session.
### **Before You Begin: Final Checks**
Before starting your assessment:
* Verify your phone’s OS version in device settings
* Update the OS to the latest supported version if required
* Restart the device after updates to ensure all system changes take effect
* Confirm camera and microphone permissions are enabled for the browser in use
Using a mobile phone with a supported operating system helps ensure reliable secondary camera setup and a secure assessment experience.
# Why OS issues cause app crashes?
Source: https://docs.talview.com/candidates/system-diagnostics/device-compatibility-and-access/why-os-issues-cause-app-crashes
If an app crashes during your proctored exam or interview, the root cause is often related to your device’s **operating system (OS)** on either your **primary device** or a **secondary device (mobile phone)** used for environment monitoring. Outdated software, restrictive system settings, or aggressive background controls can interrupt app stability and force the session to close unexpectedly.
In this article, we explain how OS-related issues, especially on **mobile secondary devices**, can lead to app crashes and what you can do to prevent them before your assessment.
## ✅ Common Causes and Fixes
| What Might Be Wrong | What You Can Do |
| :------------------------------------------------------ | :------------------------------------------------------------------------------------------------------------------------------ |
| Outdated OS version (desktop or mobile) | Update your device to the latest supported OS version to ensure compatibility and security patches. |
| Power-saving or battery optimization enabled | Disable **Battery Saver / Low Power Mode** on both primary and secondary devices before starting. |
| Device hasn’t been restarted recently | Restart the device to clear temporary memory, background processes, or hung system services. |
| System performance or background restrictions enabled | Restore default performance settings and remove aggressive background limits, especially on mobile devices. |
| Multiple apps running in the background | Close all non-essential apps on desktop and mobile to free memory and system resources. |
| Required permissions not granted (camera, mic, storage) | Open OS settings and allow all required permissions for the app or browser being used. |
| Secondary device OS restrictions (mobile) | Disable battery optimization, data saver, and background app limits for the mobile browser or app used as the secondary camera. |
## 📱 How OS Issues Affect Secondary Devices (Mobile)
When a **mobile phone is used as a secondary camera**, OS-level restrictions are a common cause of disconnections and crashes:
* **Battery optimization** may pause or terminate the camera stream
* **Screen lock or auto-sleep** can stop background recording
* **Data saver modes** may throttle or block video streaming
* **Background app limits** can close the browser or camera session
These interruptions can cause the proctoring session to disconnect or fail compliance checks.
## 🛠 Recommended Steps Before Retrying
* Fully **restart your device**
* Ensure your OS meets the **minimum supported version**
* Disable **battery saver, data saver, or background limits**
* Grant **camera, microphone, and storage permissions**
* Reopen the app only after completing the above steps
## 📚 Helpful Guides
If the issue persists, follow these step-by-step resources:
* 🔗 [Update your iOS device](https://support.apple.com/en-in/guide/iphone/iph3e504502/ios)
* 🔗 [Update your Android device](https://support.google.com/android/answer/7680439?hl=en)
* 🔗 [Grant camera and mic permissions](https://docs.talview.com/candidates/system-diagnostics/camera-and-microphone/how-to-enable-device-permissions-for-camera-and-microphone)
# Device disconnected during test
Source: https://docs.talview.com/candidates/system-diagnostics/device-disconnected-during-test
Attendees may experience **device disconnection issues** during their proctored assessment session, which can interrupt their test. Device disconnection means that the system has lost a required connection with one or more of your **devices or components (primary laptop/desktop, secondary mobile camera, network, or secure browser),** causing your *assessment window, proctoring feed, or checks to stop or exit unexpectedly*.
This article helps attendees troubleshoot and resolve device disconnection issues that occur during their proctored test session, allowing them to resume their assessment without losing progress.
## 🔎 Troubleshooting Common Issues
| **What might be wrong** | **How to fix it** |
| :--------------------------------------------------------------------------------------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Unstable internet connection** | Check your internet connection strength and switch to a more stable network if possible. If using Wi-Fi, move closer to the router or connect via an ethernet cable for a more reliable connection. [**Run a speed test**](https://speed.talview.com/) |
| **Browser crashed or froze** | Refresh the browser page or restart your browser. If using **Talview Secure Browser (TSB)**, close and relaunch the application. Your progress should be saved, and you can resume the test. |
| **Device battery died or power interruption** | Charge your device and restart it. Once powered on, return to the assessment link to resume your session. Ensure your device is plugged in or fully charged before continuing. |
| **Camera or microphone access revoked** | Check your browser or device settings to ensure camera and microphone permissions are still granted to Talview. Re-enable permissions if they were accidentally disabled. |
| **Screen sharing stopped** | If screen sharing was stopped, restart screen sharing when prompted. You can resume the exam without redoing pre-checks, regardless of how many times screen sharing is stopped. |
| **Device overheating or performance issues** | Close unnecessary applications and browser tabs to reduce device load. Allow your device to cool down if overheating. Ensure you're using recommended device specifications for optimal performance. |
| **Session timeout due to inactivity** | Return to the assessment link and log back in using your credentials. Your session should resume from where you left off unless the maximum time allowed has expired. |
| [**Secondary device (mobile) disconnected**](https://www.notion.so/V8-Proview-3033461472f3809e822ae7b748652f22?pvs=21) | If using a secondary device for proctoring, check that it remains connected and the Talview Candidate app is still running. Reconnect the device by scanning the QR code again if needed. |
### **Additional Tips**
* **Use recommended browsers:** Ensure you're using a supported browser (Chrome, Firefox, Edge) or *Talview Secure Browser (When recommended)* for the best experience.
* **Check system requirements:** Verify that your device meets Talview's minimum system requirements before starting the test.
* **Keep backup connectivity ready:** Have a mobile hotspot or alternative internet connection available as a backup in case your primary connection fails.
* **Monitor network stability:** Before starting your test, [**run a speed test**](https://video-diagnostics.talview.org/) to ensure your connection is stable (minimum 2 Mbps upload/download recommended).
* **Contact support immediately:** If disconnection issues persist, contact your test administrator or Talview support with your candidate ID and details of the issue so they can assist you or extend your test time, as per allowed rules.
# Environment Check Guide
Source: https://docs.talview.com/candidates/system-diagnostics/environment-setup/environment-check-guide
During certain assessments or live interviews, you will be required to complete an **Environment Check**. This step helps ensure that your test environment meets proctoring and security requirements and that the session is conducted in a fair and distraction-free setting.
This guide explain what the environment check is and how to complete it successfully.
***
### ✅ What is an Environment Check?
An environment check is a verification step where you are asked to show your surroundings using your camera. Before starting the environment check, make sure that:
* You are in the room where you will complete the assessment or interview
* There are no unauthorized materials or additional screens nearby.
* The environment is quiet and well lit
* ## If using a secondary device, it is connected successfully using the QR code and verification process
### 📌 How to complete the Environment Check?
Follow the on-screen instructions shown during your session.
**1. Start the Environment Check**
When prompted, the environment check will begin automatically. Instructions will appear on your screen guiding you through the process.
**2. Show Your Surroundings**
Using your camera, slowly follow steps on your device and show the following.
* Your desk or workspace
* The area around your chair
* The floor and ceiling
* All walls in the room
Move slowly and clearly so all areas are visible.
**3. Follow System Prompts**
Talview may guide you with on-screen cues or prompts during the scan. Continue until the system confirms that the check is complete.
**4. Resume Your Session**
Once the environment check is completed, you will move to the next system check or return to your assessment or interview.
**Important Notes**
* If the environment check is incomplete or unclear, you may be asked to repeat it
* Interruptions or changes in surroundings during the session may trigger alerts
* Do not proceed with the assessment unless the environment check is completed successfully
**Tips for a Smooth Environment Check**
* Ensure good lighting to avoid dark or unclear video
* Move your camera slowly to avoid blurred images
* Do not switch apps, refresh the page, or lock your device during the check
* Remain in the same room for the entire assessment
# How to reduce background noise and visual distractions?
Source: https://docs.talview.com/candidates/system-diagnostics/environment-setup/how-to-reduce-background-noise-and-visual-distractions
Background noise and visible distractions during an assessment can interfere with proctoring and audio monitoring, potentially triggering alerts or interrupting your session.
This checklist helps you identify common environmental issues and explains how to eliminate distractions.
***
### ✅ Common Sources of Distractions
| **Distraction Type** | **Examples** |
| :--------------------- | :----------------------------------------------------------------- |
| Audio noise | TV sounds, music, phone calls, conversations, household appliances |
| Visual movement | People walking behind you, pets, open doors, background activity |
| Environmental activity | Street noise, construction sounds, shared living spaces |
### ✅ How to Reduce Background Noise?
* Turn off televisions, radios, speakers, and streaming devices in nearby rooms.
* Inform family members, roommates, or colleagues in advance and request uninterrupted privacy.
* Close doors and windows to block external noise such as traffic or voices.
* Silence mobile phones and keep them out of reach during the assessment.
* Schedule your test during a quieter time of day when household activity is minimal.
### ✅ How to Minimize Visual Distractions?
* Choose a **private, enclosed room** where no one will enter during the test.
* Sit with your **back facing a wall** to prevent movement or people from appearing on camera.
* Keep doors closed and avoid transparent or high-traffic areas.
* Ensure pets are kept out of the room for the entire duration of the test.
* Maintain a clean, neutral background free from unnecessary objects or movement.
**Additional Tips:**
* Use **headphones** (if permitted) to reduce ambient sound pickup by your microphone.
* Perform a quick **environment check** before starting to ensure all potential distractions are eliminated.
* Avoid speaking aloud, reacting verbally, or making sudden movements during the test.
* Test your microphone and camera beforehand to confirm clear audio and stable visuals.
# Verification code not working?
Source: https://docs.talview.com/candidates/system-diagnostics/environment-setup/verification-code-not-working
When connecting a **secondary device** (mobile phone or tablet) to your assessment session, Talview uses a verification code to securely pair the secondary device with your primary device (laptop or desktop). This process ensures both devices are correctly linked for proctoring.
If the **verification code is not working**, fails to validate, or does not connect your device, review the troubleshooting guidance below.
***
### ✅ Common causes and fixes
| **What might be wrong** | **How to fix it** |
| :----------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Incorrect verification code entered | Ensure all **8 digits** are entered exactly as shown on the secondary device. Re-enter the code carefully. |
| Network connection is unstable | An unstable or switching network can interrupt verification. Ensure both devices are on a stable internet connection. Avoid switching between Wi-Fi and mobile data during pairing. |
| Page refreshed or navigated away during verification | Refreshing or leaving the page mid-process can break the connection. Keep both devices on the verification screen until the pairing is confirmed. |
| Unsupported or in-app browser used on secondary device | In-app browsers (for example, links opened inside Gmail, WhatsApp, or SMS apps) may block verification. Open the QR link in a supported browser such as **Chrome (Android)** or **Safari (iOS)**. |
| Secondary device screen locked or app minimized | Keep the secondary device screen ON and the browser open until the device is connected. |
**Additional Tips:**
* Close background apps on the secondary device before scanning the QR code
* Scan the QR code again and enter the newly generated 8-digit code immediately
* Ensure both devices remain powered and connected to the internet throughout the process
# Why did my Environment review fail?
Source: https://docs.talview.com/candidates/system-diagnostics/environment-setup/why-did-my-environment-review-fail
Talview’s **environment review** ensures the integrity of your exam by verifying your surroundings before you begin. If your environment check fails during the pre-check or proctored setup, follow this guide to quickly identify and fix common issues.
***
### ✅ Common causes and fixes
| **What Might Be Wrong** | **How to Fix It** |
| :---------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Cluttered desk or room** | Clear your surroundings of all papers, books, phones, or other unauthorized items before scanning. |
| **Other people visible or audible in the room** | Make sure you are alone in a quiet, enclosed space. Close doors and windows to minimize background noise or interruptions. |
| **Incomplete 360° room scan** | Perform a slow and complete scan of the entire area, including the floor, ceiling, desk, and under the table. Avoid skipping corners. |
| **Poor lighting or unclear video feed** | Use bright, even lighting so your camera can clearly capture every part of the room. Avoid strong backlight or dark shadows. |
| **System failed to submit scan** | Weak or unstable internet connection might be the cause. Check your internet connection. |
| **System failed to record or upload the scan** | Retry the scan. Ensure no pop-up blockers or extensions interfere with Talview’s upload process. |
| **Repeated failure despite following steps** | Contact [**Talview Support**](https://talview.freshdesk.com/support/solutions) or your exam administrator for assistance. Include screenshots or short clips of your setup for faster resolution. |
**Additional Tips**
* Move your camera slowly to capture every corner; incomplete scans are the most common reason for failure.
* Keep your webcam and microphone active throughout the pre-check process.
* Do not switch tabs or minimize the browser while scanning.
# Guide to Fixing Face Capture Errors
Source: https://docs.talview.com/candidates/system-diagnostics/face-and-id-verification/guide-to-fixing-face-capture-errors
Capturing a clear and properly aligned face image is critical for processes such as identity verification and facial recognition. Face capture errors often occur due to lighting, camera positioning, or movement during capture.
This guide walks you through best practices to fix common face capture issues and successfully retake your photo.
## 📍 Steps for Successful Face Capture
| **Steps** | **Action** |
| :--------------------------------- | :----------------------------------------------------------------------------------- |
| **1. Prepare the Environment** | Choose a quiet space with good lighting and a plain background. |
| **2. Adjust Camera Settings** | Position the camera at eye level and ensure the lens is clean and unobstructed. |
| **3. Position Yourself Correctly** | Sit straight and align your face within the on-screen frame. |
| **4. Capture Technique** | Keep the camera steady and avoid moving while the image is being captured. |
| **5. Review and Retake** | Review the captured image immediately and retake it if clarity or alignment is poor. |
***
## ⚠️ Common Troubleshooting Steps
| **What might be wrong** | **What to do** |
| :-------------------------------- | :--------------------------------------------------------------------------- |
| Blurred image | Keep the device steady and avoid movement during capture. |
| Poor lighting | Improve lighting using natural light or a soft lamp placed in front of you. |
| Face misalignment | Center your face within the frame and keep your head straight. |
| Overexposed or underexposed image | Adjust lighting or move slightly closer to or farther from the light source. |
**Additional Tips:**
* **Use a quality camera:** A device with a high-resolution front camera produces better results.
* **Eliminate glare:** Avoid reflections from glasses, windows, or overhead lights.
* **Avoid disturbances:** Ensure no interruptions or sudden movements during capture.
# How to Upload an ID Card successfully?
Source: https://docs.talview.com/candidates/system-diagnostics/face-and-id-verification/how-to-upload-an-id-card-successfully
This article guides attendees through uploading their ID card during Talview’s onboarding process. Following these steps helps ensure successful identity verification and prevents delays in proceeding to the assessment.
***
## ✅ Prerequisites
Before you begin, ensure you have:
* A valid physical-original government-issued photo ID (Passport, National ID, or Driver’s License)
* A working webcam with a clean lens
* Adequate lighting in your onboarding environment
* Close Background applications that use the camera (such as Zoom)
***
## How to upload your ID card
Watch the step-by-step walkthrough:
When you reach the **Photo ID Verification** step during onboarding:
1. Click **Proceed** to begin the ID upload process.
2. Select the **Country** that issued your ID.
3. Select the **State** where the ID was issued.
4. Choose the **Type of ID** (Driver’s License, Passport, Voter ID, Aadhaar Card, or Student ID).
5. Capture clear images of **both the front and back** of the ID card as prompted.
6. Review the images and submit them for verification.
***
## What happens after ID card upload
After submission, your ID is securely sent for verification. An exam supervisor reviews the uploaded ID to confirm that it matches your captured image.
This verification typically takes **up to 10 minutes**, though timing may vary. Once approved, you proceed to the **Environment Check** and subsequent hardware checks before entering the exam environment.
### Best practices for a successful upload
* Clean your camera lens to avoid blur or smudges
* Use a plain, uncluttered background
* Hold the ID card steady at a readable distance
* Ensure all text and the photo on the ID are clearly visible
* Keep the ID flat and aligned with the camera to prevent distortion
# Why does my webcam look grainy or blurry?
Source: https://docs.talview.com/candidates/system-diagnostics/face-and-id-verification/why-does-my-webcam-look-grainy-or-blurry
If your webcam looks grainy, blurry, pixelated, or low quality during your assessment, it can affect face detection, identity verification, and proctoring visibility. Grainy video is typically caused by insufficient lighting, camera sensor limitations, or incorrect camera settings.
This guide helps you troubleshoot poor webcam quality and improve video clarity.
## ✅ Common Causes and Fixes
| **What Might Be Wrong** | **What You Can Do** |
| :--------------------------------- | :----------------------------------------------------------------------------------------------------------------- |
| Low lighting in the room | Sit in a **well-lit room**, preferably with **natural light** or a lamp facing you. Avoid backlighting. |
| Dirty or smudged webcam lens | Gently clean the webcam lens with a **soft cloth** before starting the test. |
| Webcam resolution is set too low | Close all apps using your camera, then restart the test. |
| Using a low-end or external webcam | Use your **built-in laptop webcam** if possible — they usually offer better quality for proctoring. |
| Background is too dark | Sit against a **neutral-colored wall** in a well-lit space to avoid contrast issues. |
| Internet speed is unstable | Graininess may appear if video is compressed. Run a [speed test](http://google.com/) and ensure stable connection. |
### **Additional Tips:**
Still facing grainy camera issues?
* Make sure no other apps (Zoom, Teams, Meet) are using the camera in the background
* **Restart** your system and re-open the **Talview test session**
* Avoid sitting under harsh overhead lights - soft lighting works best
# Why ID verification fails in night mode or low light?
Source: https://docs.talview.com/candidates/system-diagnostics/face-and-id-verification/why-id-verification-fails-in-night-mode-or-low-light
ID verification can fail when images are captured in night mode or low-light conditions. While these camera features are designed to improve visibility, they often introduce image distortions that interfere with automated verification systems.
This article explains why these failures occur and how to fix them before retrying.
## ✅ Common Causes and Fixes
| **What Might Be Wrong** | **How to Fix It** |
| :------------------------------ | :------------------------------------------------------------------------------------------------ |
| Night mode is enabled | Turn off night mode before capturing your ID. Use standard camera mode for more accurate results. |
| Insufficient lighting | Move to a well-lit area using natural light or a bright lamp facing the ID. |
| Reflections or glare on the ID | Disable flash and slightly adjust the angle of the camera to reduce glare. |
| Blurry or shaky image | Hold the device steady or place it on a stable surface while capturing the image. |
| Poor focus on ID details | Tap on the ID on your screen to force the camera to focus before capturing. |
| Incorrect distance or angle | Hold the camera parallel to the ID and ensure the full ID is visible within the frame. |
| Color distortion from low light | Improve lighting to maintain natural colors and avoid yellow or bluish tones. |
### ✅ Recommended Troubleshooting Steps
* **Adjust Device Settings**\
Disable night mode, HDR, or any low-light enhancement features that may alter the image.
* **Review the Captured Image**\
After capturing, verify that all text, your photo, and ID edges are sharp and clearly readable.
* **Retake in Better Conditions**\
If the image appears dark, blurry, or reflective, retake it immediately under improved lighting.
**Additional Tips**
* **Use a Stable Setup**: Rest your device on a flat surface or use a tripod to avoid motion blur.
* **Choose a Neutral Background**: Place the ID on a plain, non-reflective surface for better contrast.
* **Avoid Cluttered Environments**: A clean environment helps the camera focus correctly on the ID.
# Why ID verification fails on retake?
Source: https://docs.talview.com/candidates/system-diagnostics/face-and-id-verification/why-id-verification-fails-on-retake
If your ID verification fails again during a retake, it is usually due to image quality issues, incorrect ID selection, or repeated submission errors rather than a system malfunction. Retakes are closely reviewed, and small mistakes that were overlooked earlier may cause repeated failures.
This article explains the most common reasons ID verification fails on retake and how to submit your ID correctly without triggering additional flags.
## ✅ Common Reasons ID Verification Fails on Retake
### 1. Using the Same Low-Quality Image Again
If you re-upload the same blurry, dark, or cropped image that failed previously, the system is likely to reject it again.
**What to do**
* Capture a **new image** instead of reusing the old one
* Ensure the ID is sharp, well-lit, and fully visible
### 2. Poor Lighting or Glare on the ID
Reflections, shadows, or uneven lighting can hide important details such as your name, photo, or ID number.
**What to do**
* Use bright, even lighting
* Avoid glare from overhead lights or flash
* Place the ID on a flat surface
### 3. Cropped or Partially Visible ID
Missing edges, corners, or cropped sections of the ID often lead to verification failure.
**What to do**
* Ensure **all four corners** of the ID are visible
* Do not zoom in excessively
* Keep the ID centered in the frame
### 4. Using an Unsupported or Invalid ID
Some IDs may not be accepted by the exam sponsor, even if they look valid.
**What to do**
* Prefer a **government-issued photo ID**
* Ensure the ID is **not expired**
* Match the ID name with your registration details
### 5. Blurry or Out-of-Focus Capture
Motion blur or autofocus issues can reduce readability, especially during retakes.
**What to do**
* Keep your hands steady or place the ID on a surface
* Wait for the camera to focus before capturing
* Use a higher-resolution camera if available
### 6. Masked or Obscured Information
Covering any part of the ID, intentionally or unintentionally can trigger rejection.
**What to do**
* Do not cover or blur any details
* Avoid stickers, fingers, or reflections on the ID
### 7. File Format or Size Issues (Upload Method)
Incorrect file formats or oversized files may fail silently or be rejected.
**What to do**
* Use **JPG, JPEG, or PNG** formats
* Keep the file size **under 3 MB**
## 🛠 Best Practices for a Successful Retake
Before submitting again:
* Use a **new, clear image**
* Ensure your **face photo and name are clearly visible**
* Capture the ID in **good lighting**
* Avoid shadows, glare, or reflections
* Keep the ID **flat and aligned**
* Double-check image clarity before uploading
**Final Checklist Before Retrying**
* ID is valid and not expired
* Image is clear, sharp, and well-lit
* All edges of the ID are visible
* No information is hidden or cropped
* Correct file format and size are used
Following these steps significantly improves your chances of passing ID verification on retake without triggering system flags or delays.
# Why is my face capture and verification failing?
Source: https://docs.talview.com/candidates/system-diagnostics/face-and-id-verification/why-is-my-face-capture-and-verification-failing
If your face capture is being rejected or verification is failing during your assessment, you may be experiencing image quality, lighting, positioning, or camera issues. Face capture is required for identity verification, and failed attempts can prevent you from starting your proctored test or interview.
This guide helps you troubleshoot common face capture problems and ensure successful verification.
## ✅ Common Causes and Fixes
| **What Might Be Wrong** | **What You Can Do** |
| :----------------------------------------- | :--------------------------------------------------------------------------------------------- |
| Image is blurry | Stay steady during the capture and ensure your camera is focused before submitting |
| Image is distorted | Position the camera at eye level to avoid distortion |
| Face is cropped | Look straight at the camera with your head centered. Ensure entire face is visible in the view |
| Poor lighting conditions | Ensure you are in a well-lit area, avoid backlighting that can obscure your face |
| Reflections or Glare on the Face | Adjust your position to minimize glare from lighting sources |
| Obstructed face | No hats, sunglasses, or anything that blocks your face unless for religious or medical reasons |
| Still failing after trying the steps above | Contact your administrator with a screenshot of the error for further assistance |
## 🛠 Final Check: Ensure Your Face is Clear
Before submitting your face for verification, check that the following details are clearly visible:
* Your whole face without obstructions.
* Proper lighting that enhances your features.
* No shadows or reflections that could obscure your details.
👉 [**Run a Test Capture**](/candidates/system-diagnostics/run-diagnostics) to confirm clarity before proceeding with your face submission using your laptop or mobile camera.
# Why is my ID upload failing or not working?
Source: https://docs.talview.com/candidates/system-diagnostics/face-and-id-verification/why-is-my-id-upload-failing-or-not-working
If your ID upload is failing, timing out, or showing an error during **Talview** verification, you may be experiencing file format, size, quality, or technical issues. Failed ID uploads can prevent you from completing registration or starting your assessment. This guide helps you troubleshoot ID upload problems and ensure your document is submitted successfully.
## ✅ Common Causes and Fixes
| What might be wrong | How to fix it |
| :------------------------------------------ | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| File format is not supported | Ensure your ID file is in an accepted format: **PDF (.pdf), JPEG (.jpg or .jpeg), or PNG (.png).** If your file is in a different format (HEIC, BMP, TIFF), convert it using a free online converter or your device's photo editing software before uploading. |
| File size exceeds maximum limit | Your ID file must be 3 MB or smaller. To reduce file size: compress the image using online tools, reduce image resolution to 1920x1080 or lower, or use JPEG format instead of PNG (JPEG files are typically smaller). Check file size by right-clicking > Properties (Windows) or Get Info (Mac). |
| ID details are not clear or visible | Ensure all required information is clearly visible: full name, ID number, photo, expiration date, and issuing authority. Zoom in on your uploaded file to verify all text is readable. If any information is unclear, retake or rescan your ID with better quality. |
| Using an old or outdated ID photo | Upload a scan or photo of your most recent, currently valid ID. Old IDs or expired documents will not be accepted. Check the expiration date and ensure your ID is valid on the date of your assessment. |
| ID image is blurry, dark, or poorly lit | Capture or scan your ID in a well-lit area with even lighting. Ensure the image is in focus—not blurry or pixelated. If scanning, use at least 300 DPI resolution. If photographing, hold your device steady and tap to focus before capturing. |
| ID is cropped or edges are cut off | Ensure all four corners and edges of your ID are fully visible in the image. Leave a small border of space around the ID—don't crop right to the edges. Lay your ID flat on a contrasting background and capture the entire document within the frame. |
| Information is covered, masked, or redacted | Do not cover, redact, or hide any information on your ID. All fields must be visible and unobstructed—don't use stickers, tape, or digital editing to block information. If concerned about privacy, note that ID verification is secure and confidential. |
| Browser is not compatible or has issues | Use the latest version of Chrome or Edge for best upload compatibility. Clear your browser cache and cookies:` Settings > Privacy > Clear browsing data.` Disable browser extensions that might interfere with uploads (ad blockers, privacy tools). |
| Session expired during upload attempt | If you took too long to select your file, your session may have expired. Refresh the page to start a new session, then immediately proceed with the upload. Have your ID file ready and easily accessible before starting the upload process. |
**Additional tips:**
* Have your ID file prepared and saved on your desktop before starting the upload process to avoid session timeouts
* Use your device's built-in camera app or scanner to capture your ID rather than third-party apps, which may add watermarks or reduce quality
* Name your file clearly (e.g., "passport\_john\_smith.jpg") to easily find it when uploading
* For best results, scan your ID using a scanner at 300 DPI or higher rather than photographing it with a phone camera
* If you have a physical copy of your ID available, you can complete verification by capturing the ID directly through your camera by following the on-screen instructions—this alternative method often works when file uploads fail
# Why is my ID upload not completing?
Source: https://docs.talview.com/candidates/system-diagnostics/face-and-id-verification/why-is-my-id-upload-not-completing
If your ID upload does not complete and keeps restarting or getting stuck, it is usually caused by file issues, connectivity problems, or session interruptions during the verification process in Talview.
This checklist helps you identify the cause and complete your ID upload successfully.
## ✅ Common Causes and Fixes
| What might be wrong | How to fix it |
| :------------------------------------ | :------------------------------------------------------------------------------------ |
| Unstable or slow internet connection | Switch to a stable network and avoid changing Wi-Fi or mobile data during the upload. |
| Unsupported file format | Upload the ID only in **JPG, JPEG, PNG, or PDF** format. |
| File size exceeds the limit | Reduce the file size to meet the upload limit before retrying. |
| Blurry, dark, or low-quality ID image | Capture a new image in good lighting with all details clearly visible. |
| Cropped or partially visible ID | Ensure all four edges of the ID are visible and fully within the frame. |
| Expired or unsupported ID | Use a valid, non-expired ID that is accepted by your exam or interview sponsor. |
| Browser cache or session conflict | Clear your browser cache and cookies, then reopen the upload link. |
| Page refreshed or upload interrupted | Restart the upload and allow it to complete without refreshing the page. |
| VPN or proxy enabled | Disable any VPN or proxy before retrying the upload. |
| Temporary system or session error | Refresh the page or reopen the verification link to reset the session. |
**Additional tips:**
* Use a device with a good quality camera for capturing your ID
* Place the ID on a flat surface and avoid glare or reflections
* Keep the browser window active until the upload finishes
* Avoid switching apps or tabs while the upload is in progress
# Why is my ID verification failing?
Source: https://docs.talview.com/candidates/system-diagnostics/face-and-id-verification/why-is-my-id-verification-failing
If your submitted ID is blurry or unclear during the verification process, it may block you from proceeding. Follow the steps below to resolve the possible issues.
## ✅ Common Causes and Fixes
| **What Might Be Wrong** | **What You Can Do** |
| :----------------------------- | :------------------------------------------------------------------------------------------------------- |
| Low quality ID | Use a high-resolution image for ID Verification. |
| Details are not clear | Check that the following details are clearly visible: ID number, your photo, validity, full name. |
| Unstable camera position | Hold your ID steadily during the capture. |
| Poor lighting conditions | Ensure you are in a well-lit area. Avoid backlighting that may obscure the ID. |
| Distance from the camera | Hold the ID at a distance where it can be captured clearly, generally about 6-12 inches from the camera. |
| Reflections or glare on the ID | Adjust the angle of your ID to minimize any glare from lights or windows. |
| Cropped sections in ID | Ensure all the 4 corners or edges of the ID are in the frame |
| Masked information | Make sure no information is covered |
## 🛠 Final Check: Ensure Your ID is Clear
Before submitting your ID for verification, check that the following details are clearly visible:
* ID number
* Your photo
* Expiration date
* Full name
👉 [Run a Test Scan](https://video-diagnostics.talview.org/) to confirm clarity before proceeding with your ID submission.
# Why isn't my face being detected or recognized?
Source: https://docs.talview.com/candidates/system-diagnostics/face-and-id-verification/why-isnt-my-face-being-detected-or-recognized
If your face isn't being detected, recognized, or is showing "face not found" errors during your assessment, improper webcam positioning, lighting issues, or camera settings may be preventing the system from locating and verifying your face. Face detection is required for identity verification and proctoring, and detection failures can delay or prevent you from starting your test.
This guide helps you troubleshoot face detection problems and ensure successful recognition.
## ✅ Common Causes and Fixes
| What might be wrong | How to fix it |
| :----------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| You're sitting too close or too far from camera | Sit 18-24 inches (arm's length) from your webcam. Move closer if you appear tiny in the preview, or move back if your face is cropped. The system needs to see your full face from hairline to chin with some space around the edges. |
| Lighting is behind you causing silhouette effect | Position yourself facing a window or light source, never sit with a bright window or lamp behind you. Backlighting creates a dark silhouette where the camera can't detect facial features. Use natural light from windows in front of you, or position desk lamps on either side of your monitor to illuminate your face evenly from the front. |
| Wearing hat, sunglasses, or face coverings | Remove hats, sunglasses, headphones, masks, or anything partially covering your face. Pull hair back from your forehead so it doesn't cover your eyes or eyebrows. The system needs to see your entire face clearly from forehead to chin. Religious head coverings are permitted if your full face remains unobstructed. |
| Background is too busy or has other faces | Sit in front of a plain, solid-colored wall or background. Avoid sitting in front of windows, mirrors, posters with faces, or busy patterned backgrounds. Other faces in the background (photos, posters, other people) can confuse the detection system. Choose a simple, uncluttered background where you're the only face visible. |
| Camera lens is dirty or obstructed | Clean your camera lens with a soft, dry cloth to remove smudges, fingerprints, or dust. Check that nothing is physically blocking the lens (tape, stickers, privacy covers). A dirty or obstructed lens significantly reduces image clarity and can prevent face detection. |
| Browser doesn't have camera permissions | Grant camera access to your browser. **Chrome/Edge:** Click lock icon in address bar > Site settings > Camera > Allow. **Firefox:** Click lock icon > More information > Permissions > Camera > Allow. **Safari:** Safari > Settings for This Website > Camera > Allow. Refresh the page after granting permissions and try detection again. |
| Using virtual background or camera filters | Disable all virtual backgrounds, filters, beauty modes, or AR effects in your camera software. These features interfere with face detection by altering or obscuring your actual facial features. Use your camera's natural, unfiltered view. Check your camera app settings and webcam software to ensure all effects are turned off. |
| Head is turned to the side or tilted | Face the camera directly with your head straight, don't tilt your head to the side, look down, or turn away from the camera. Your face should be in a neutral, front-facing position as if taking a passport photo. Profile views or angled faces may not be detected properly. |
**Additional tips:**
* Test your webcam positioning and face detection using your device's built-in camera app before starting your assessment to ensure the setup works
* Sit in a stationary chair at a desk or table, avoid couches or beds where you might slouch or move around, affecting your camera position
* Keep your face centered in the camera preview throughout the test—avoid leaning to the side or forward during your session
* Adjust your monitor brightness to 70-80% so you can comfortably see the screen without harsh light reflecting on your face
* Close other applications that might be using your camera (video chat apps, recording software) as they can conflict with face detection
# Why isn't my ID type accepted?
Source: https://docs.talview.com/candidates/system-diagnostics/face-and-id-verification/why-isnt-my-id-type-accepted
If your ID type isn't being accepted during **Talview** verification, it may not be on the approved list for your specific assessment, or it might not meet the required criteria. ID verification typically requires government-issued photo identification, though some assessments accept alternative documents like student IDs or employee IDs depending on the exam sponsor's requirements.
This guide helps you understand which ID types are accepted.
## ✅ Accepted Types of ID
| **Type of ID** | **Description** |
| :------------------------- | :----------------------------------------------------------------------------------------------------- |
| Government issued Photo ID | Includes passports, national identity cards, and driver’s licenses with your photo. |
| Student ID Card | Cards issued by educational institutions that contain your name, photo, and other identifying details. |
| Residency Card\* | Includes permanent residency cards that clearly display your identity information. |
| Employee ID Card\* | Valid ID issued by an employer that includes your photo and name. |
| Military ID\* | Identification cards issued to active and retired military personnel that include a photo. |
> \*These IDs may not be accepted by all exam sponsors. Please check your exam instructions. We would strongly recommend using government issued ID photo ID cards for your onboarding.
***
## 🛠 Final Check: ID Requirements
Before submitting your ID for verification, make sure it meets the following criteria:
* Must be valid and **not expired**.
* Clearly displays your **name** and **photo**.
# Why is audio not playing through the correct device?
Source: https://docs.talview.com/candidates/system-diagnostics/hardware-testing-and-setup/why-is-audio-not-playing-through-the-correct-device
If you’re unable to hear instructions, alerts, or audio playback during your Talview test, your **audio output may be routed to the wrong device**. This commonly happens when headphones, Bluetooth devices, or external monitors are connected. Misrouted audio can affect audio- or video-based questions and disrupt your test flow.
In this article, you’ll learn why this happens and how to fix it quickly.
## ✅ Common Causes and Fixes
| **What Might Be Wrong** | **What You Can Do** |
| :----------------------------------------------- | :------------------------------------------------------------------- |
| Audio is playing through a different device | Check and **set the correct output device** in your system settings |
| Bluetooth device is connected but inactive | Turn Bluetooth off temporarily or reconnect the headphones properly |
| **HDMI monitor** with no speakers is selected | Switch output from the monitor to **internal speakers** or headset |
| Output device was unplugged mid-test | Replug your headset or speakers and reselect them in the output list |
| Browser or OS audio settings are *misconfigured* | Restart your browser and verify permissions for sound output |
## 🛠 How to Check Output Settings
### On **Windows**:
1. Click the **🔊 Sound icon** in the taskbar
2. Click the arrow next to the **volume slider**
3. Select your **preferred output device** (e.g., Headphones, Speakers)
### On **Mac**:
1. Go to **System Settings → Sound**
2. Under **Output**, select your desired device (e.g., MacBook Speakers, USB Headphones)
3. Adjust the **volume slider** if
## 🌐 Final Check: Audio Working?
Once your device is selected:
* Play any sound or system audio to verify it's working
* Rejoin your **Talview test link** and check if the **test audio plays**
* Make sure your **volume is not muted**
### Additional Tips
* Disconnect all extra audio devices (Bluetooth, HDMI) and use only **one output device**
* Refresh the **Talview test page** after switching audio devices
* Avoid using **screen-sharing apps or conferencing tools** during the test — they can interfere with audio routes
# Why is my camera and microphone blocked?
Source: https://docs.talview.com/candidates/system-diagnostics/hardware-testing-and-setup/why-is-my-camera-and-microphone-blocked
If your test or interview cannot access your **camera or microphone**, it usually means the browser or operating system has blocked the required permissions. This can prevent you from starting the session or being seen and heard during a live or proctored assessment.
In this article, you’ll learn why camera or microphone access gets blocked and the steps you can take across different browsers and operating systems to fix it quickly.
## ✅ Common Issues and Fixes
| **What Might Be Wrong** | **What You Can Do** |
| :-------------------------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Browser does not have permission to use camera/microphone | Open your **browser settings** → **Privacy & Security** → **Site Settings / Permissions** → Set **Camera** and **Microphone** to **Allow** for the test site |
| You selected “Block” on the permission prompt | Reload the page, click the **site permission icon** in the address bar, change Camera and Microphone to **Allow**, then refresh |
| Another application is using the camera or microphone | Close apps like Zoom, Teams, Skype, screen recorders, or background utilities using audio/video |
| Incorrect camera or microphone selected | In browser settings, ensure the **correct input devices** are selected for Camera and Microphone |
| Browser tab is not secure | Ensure the test link starts with **https\://**. If not, contact support |
| OS-level permissions are disabled | On **Windows or macOS**, open **System Privacy Settings** and allow your browser to access the camera and microphone |
| External camera or mic not detected | Reconnect the device, refresh the page, and confirm it appears in the device selection list |
### Additional Tips
* Close **all other browser tabs and windows**
* Restart your browser after changing permissions
* Avoid using **private/incognito mode** unless explicitly supported
* Ensure you are using a **supported and up-to-date browser**
### ✅ Final Check: Confirm Camera and Microphone Access
Before restarting your test or interview:
* Test your [**camera and microphone**](/candidates/system-diagnostics/run-diagnostics)
* Verify that video preview is visible
* Confirm your microphone input shows activity
Once confirmed, rejoin your session to continue without interruptions.
# Why is my external camera not connecting?
Source: https://docs.talview.com/candidates/system-diagnostics/hardware-testing-and-setup/why-is-my-external-webcam-not-connecting
If your external camera is not detected or does not work during a test or interview, it is usually caused by connection, permission, or software conflicts. A working camera is mandatory for identity verification and proctoring, so this issue must be resolved before you proceed.
In this article, you’ll learn why external cameras fail to connect and how to fix the issue step by step.
### 🔍 Why This Happens
External webcams may fail to connect for one or more of the following reasons:
* Loose or faulty USB connection
* Camera permissions not granted in the browser or operating system
* Another application already using the camera
* Incorrect camera selected as the default device
* Outdated or corrupted camera drivers
* Temporary system or hardware glitches
### ✅ How to Fix External Camera Connection Issues
Follow the steps below in order until the camera is detected.
**1. Check Physical Connections**
* Ensure the webcam is **securely plugged into a USB port**
* Try a **different USB port**
* Inspect the cable for damage or looseness
* Avoid using USB hubs; connect the camera directly to the system
**2. Check Browser Camera Permissions**
Make sure your browser is allowed to access the external camera.
* Click the **lock icon** next to the website URL
* Open **Site settings / Permissions**
* Set **Camera** to **Allow**
* Select your **external webcam** from the device list
* Refresh the page after making changes
**3. Close Conflicting Applications**
If another application is using the camera, it cannot be accessed by the test platform.
* Fully close apps such as **Zoom, Microsoft Teams, Skype, Google Meet**, or screen recorders
* Check background processes using:
* **Task Manager (Windows)**
* **Activity Monitor (macOS)**
**4. Set the External Camera as the Default Device**
If your system has both an internal and external camera, ensure the correct one is selected.
**On Windows:**
* Go to **Settings > Privacy & Security > Camera**
* Ensure camera access is enabled for apps and browsers
**On macOS:**
* Go to **System Settings > Privacy & Security > Camera**
* Confirm browser access is enabled
**5. Test the Camera Outside the Session**
* Use a camera testing page or system camera app
* If the camera works elsewhere, the issue is likely permission-related
* If it doesn’t work at all, the issue may be hardware or driver-related
**6. Update Camera Drivers**
**Windows:**
* Open **Device Manager**
* Expand **Cameras / Imaging Devices**
* Right-click the external camera and select **Update driver**
**macOS:**
* Camera drivers are updated via **system updates**
* Go to **System Settings > Software Update**
**7. Restart Your System**
Restarting refreshes hardware connections and clears temporary conflicts that may block camera access.
***
### 🔎 Final Check
Before rejoining your test or interview:
* Confirm the external camera is selected
* Ensure no other apps are using the camera
* Refresh the browser after permission changes
If the issue persists after completing all steps, contact **Talview Support** with details of your device, browser, and camera model.
# Why is my microphone echoing or buzzing?
Source: https://docs.talview.com/candidates/system-diagnostics/hardware-testing-and-setup/why-is-my-microphone-echoing-or-buzzing
If your microphone produces an **echo**, **buzzing**, or **feedback noise** during a test or interview, it can significantly reduce audio clarity and may interfere with communication or automated proctoring checks.
In this article, we explain the most common reasons for microphone echo or buzzing and the steps you can take to resolve the issue quickly.
## ✅ Common Causes and Fixes
| **What Might Be Wrong** | **What You Can Do** |
| :------------------------------------------ | :------------------------------------------------------------------------------------------------------------ |
| Microphone too close to speakers | Move the microphone away from your **laptop speakers** or any **external speakers** to reduce audio feedback. |
| Using built-in mic and speakers together | Use **wired headphones or earphones** to prevent internal audio looping and echo. |
| Faulty microphone hardware | Test with a **different microphone or headset** to rule out hardware issues. |
| Loose or damaged mic cable | Reconnect the microphone securely and avoid using **frayed or damaged cables**. |
| Microphone input volume too high | Lower the **mic input/gain level** in your system or audio settings. |
| Outdated or unstable audio drivers | Restart your device or **update audio drivers** to refresh the connection. |
| Echo cancellation disabled | Enable **echo cancellation or noise suppression** in your browser or system audio settings. |
| Background noise or electrical interference | Move to a **quieter room**, avoid power-heavy devices nearby, or use a **noise-canceling microphone**. |
### Additional Tips
If the issue persists, try the following:
* Restart your device and rejoin the session
* Ensure the **correct microphone** is selected in your browser or system audio settings
* Disconnect and reconnect any external audio devices
* Avoid using Bluetooth audio devices if possible, as they may introduce latency or interference
## 🛠 Final Check: Test Your Microphone
Before joining your interview, verify your mic is working clearly.
👉 [Run a Mic Test](https://www.notion.so/1d73461472f38001a772e238965c2d4a?pvs=21) to confirm it's working well.
You should see yourself and hear audio from your mic input.
# How network latency affects audio and video quality?
Source: https://docs.talview.com/candidates/system-diagnostics/how-network-latency-affects-audio-and-video-quality
Latency is the time it takes for data to travel between your device and Talview servers, measured in milliseconds (ms). High latency can disrupt live interviews and proctored assessments by causing delays in audio, video, and real-time interactions.
In this article, you’ll learn why latency matters, how it impacts your session, and what you can do to reduce it.
## 👋 What Is Latency and Why It Matters?
* **Low latency = smooth audio, video, and interaction**
* **High latency = delays, lags, or interruptions**
This is especially important for **live interviews** and **proctored assessments**, where real-time communication is key.
### 🚨 What Causes High Latency?
High latency can happen due to several common reasons:
* **Weak Wi-Fi signal** or being far from the router
* **VPNs or proxy networks** slowing down your connection
* **Busy networks** (others streaming, gaming, or video calling)
* **Apps running in the background** that use bandwidth (e.g., Zoom, YouTube, cloud sync)
* **Mobile data or hotspot usage**, which may be unstable
### ✅ Ideal Latency for Talview Sessions
To ensure a smooth experience, here’s what your latency should look like:
| **Latency Range** | **Experience Quality** |
| ----------------- | ----------------------------------- |
| **0–50 ms** | Excellent – Fully supported |
| **51–100 ms** | Acceptable – Minor delays may occur |
| **100+ ms** | Poor – Risk of audio/video issues |
> 👉 You can measure this using the [Network Speed Test](https://speed.talview.com/).
### ⚠️ How to Know If You Have High Latency
You might have high latency if:
* There’s a delay when someone speaks or responds
* Your video is freezing or skipping
* Conversations overlap or echo
* You get flagged during proctoring due to delayed reactions
* Internet disconnection happening in spite of having good upload and down
### 🛠 Steps to Reduce Latency
Try these quick fixes to lower your latency:
* **Use a wired (LAN) connection** for a stable network
* **Move closer to your router** if on Wi-Fi
* **Disconnect unused devices** from the same network
* **Turn off VPNs or proxies** unless required
* **Close other apps** using internet (e.g., Netflix, Zoom, OneDrive)
* **Restart your router/modem**
* **Switch to a home broadband connection** if using mobile data
After trying these steps, [Run a Network Speed Test](https://speed.talview.com/) again to check your improvement.
> **When to Retest** Once you've taken the steps above, go back and **re-run the System Readiness Check** to ensure your latency score is in the safe range.
## 📚 Related Articles
* [*Using Mobile Hotspot Without Interruption*](https://docs.talview.com/candidates/system-diagnostics/how-to-use-mobile-hotspot-without-interruption)
* [*How Background Apps Can Slow You Down*](https://docs.talview.com/candidates/system-diagnostics/network-and-connectivity/why-do-background-applications-cause-bandwidth-and-latency-issues)
* [*Troubleshooting High Latency With VPN*](https://docs.talview.com/candidates/system-diagnostics/why-does-vpn-usage-trigger-high-latency-warnings#why-does-vpn-usage-trigger-high-latency-warnings)
* [*Minimum Network Requirements for Talview*](https://docs.talview.com/candidates/system-diagnostics/why-is-my-network-not-meeting-test-requirements#minimum-network-requirements)
# How to adjust microphone sensitivity settings?
Source: https://docs.talview.com/candidates/system-diagnostics/how-to-adjust-microphone-sensitivity-settings
If your voice sounds **too soft**, **too loud**, or **broken** during the microphone test in Talview, the issue may be with your **microphone sensitivity settings**, not the mic itself. Properly adjusting this can help ensure you pass the speech test smoothly.
## ✅ Common Causes and Fixes
| **What Might Be Wrong** | **What You Can Do** |
| :----------------------------------- | :---------------------------------------------------------------------------------------- |
| Mic input is too low | Increase **microphone sensitivity** in system settings so your voice is picked up clearly |
| Mic picks up background noise | Lower mic sensitivity slightly and speak closer to the mic |
| You’re speaking too far from the mic | Sit closer (about 6–12 inches) and speak directly toward the mic |
| External mic isn’t being used | Go to **system audio settings** and **set the correct input device** |
| Mic is covered or blocked | Make sure it’s not covered by hands, clothes, or stickers |
### 🛠 How to Adjust Mic Sensitivity (Windows)
1. Right-click the **🔊 sound icon** → Click **Sound settings**
2. Under **Input**, select your **microphone** → Click **Device properties**
3. Adjust the **Input volume slider** — set it around **70–90%**
4. Speak and check the **volume bar** — it should bounce when you talk normally
### 🛠 How to Adjust Mic Sensitivity (Mac)
1. Go to **System Settings → Sound**
2. Under **Input**, select your **microphone**
3. Use the **Input volume slider** — aim for the *middle-to-high range*
4. Test your voice — make sure your **input level reacts as you speak**
### Additional Tips
* Use **wired headphones with a mic** if your laptop mic sounds muffled
* Restart your browser after making changes to mic settings
* Close apps like Zoom or Teams that might interfere with your microphone
***
# How to allow permissions in Chrome?
Source: https://docs.talview.com/candidates/system-diagnostics/how-to-allow-permissions-in-chrome
When you take an assessment or join an interview on Talview, Chrome needs permission to access your camera, microphone, and screen sharing. In this article, you will learn how to allow each of these permissions so your session can proceed without interruptions.
### Before you begin
* Make sure you're using the latest version of Chrome. You can check by going to `Settings > About Chrome`.
* Close any other apps that may be using your camera or microphone, such as Zoom, Teams, or Skype.
***
### **Allowing camera and microphone permissions**
1. Open your Talview assessment or interview link in Chrome.
2. When Chrome displays a pop-up asking to use your camera and microphone, click **Allow**.
3. If you don't see a pop-up, or if you previously clicked **Block**, click the **tune icon** (or **lock icon**) in the address bar next to the site URL.
4. Click **Site settings**.
5. Find **Camera** and set it to **Allow**.
6. Find **Microphone** and set it to **Allow**.
7. Go back to your Talview tab and refresh the page.
If Chrome still doesn't prompt you, you can update permissions from the browser settings:
* Click the **menu** in the top-right corner of Chrome and select **Settings**.
* Go to `Privacy and security > Site settings`.
* Under Permissions, click **Camera** and make sure **Sites can ask to use your camera** is turned on.
* Do the same for **Microphone**.
* Go back to your Talview link, refresh the page, and click **Allow** when prompted.
***
### Allowing screen sharing **permissions**
1. When your assessment or interview requires screen sharing, Chrome will display a dialog asking you to choose what to share.
2. Select **Entire Screen** (unless instructed otherwise).
3. Click **Share** to confirm.
If you're on a Mac and screen sharing doesn't start:
* Go to`System Settings > Privacy & Security > Screen Recording`.
* Make sure **Google Chrome** has a checkmark next to it.
* If you just added Chrome to the list, quit Chrome completely and reopen it for the change to take effect.
> If you're on Windows, screen sharing in Chrome generally works without any additional system-level settings.
**Additional tips**
* If you're using Chrome at work or school, your network administrator may have restricted camera, microphone, or screen sharing permissions. Contact your IT team for help.
* Antivirus or endpoint protection software sometimes blocks camera access even when Chrome shows permissions as allowed. Check your antivirus settings for a webcam or video protection feature and add Chrome as a trusted app.
* Try opening the Talview link in an incognito window if permissions aren't working as expected. This helps rule out browser extensions that may be interfering.
# How to allow permissions in Mozilla Firefox?
Source: https://docs.talview.com/candidates/system-diagnostics/how-to-allow-permissions-in-mozilla-firefox
When you take an assessment or join an interview on Talview, Mozilla Firefox needs permission to access your camera, microphone, and screen sharing. In this article, you will learn how to allow each of these permissions so your session can proceed without interruptions.
### Before you begin
* Make sure you're using the latest version of Firefox. You can check by going to `Settings > General` and scrolling to **Firefox Updates**, or by clicking the `menu > Help > About Firefox`.
* Close any other apps that may be using your camera or microphone, such as Zoom, Teams and Skype.
***
### Allowing camera and microphone permissions
1. Open your Talview assessment or interview link in Firefox.
2. When Firefox displays a pop-up asking to use your camera and microphone, click **Allow**.
3. If you don't see a pop-up, or if you previously clicked **Don't Allow**, click the **permissions icon** (camera or microphone icon) in the address bar.
4. Click the "**X"** next to the blocked permission to clear it.
5. Refresh the page and click **Allow** when prompted again
If Firefox still doesn't prompt you, you can update permissions from the browser settings:
* Click the **menu** in the top-right corner of Firefox and select **Settings**.
* Go to **Privacy & Security** and scroll down to the **Permissions** section.
* Next to **Camera**, click **Settings** and make sure the Talview site is not listed under blocked sites. If it is, select it and click **Remove Website**.
* Do the same for **Microphone**.
* Go back to your Talview link, refresh the page, and click **Allow** when prompted.
***
### **Allowing screen sharing permissions**
1. When your assessment or interview requires screen sharing, Chrome will display a dialog asking you to choose what to share.
2. Select **Entire Screen** (unless instructed otherwise).
3. Click **Share** to confirm.
If you're on a Mac and screen sharing doesn't start:
* Go to `System Settings > Privacy & Security > Screen Recording`.
* Make sure **Google Chrome** has a checkmark next to it.
* If you just added Chrome to the list, quit Chrome completely and reopen it for the change to take effect.
> If you're on Windows, screen sharing in Chrome generally works without any additional system-level settings.
**Additional tips**
* If you're using Chrome at work or school, your network administrator may have restricted camera, microphone, or screen sharing permissions. Contact your IT team for help.
* Antivirus or endpoint protection software sometimes blocks camera access even when Chrome shows permissions as allowed. Check your antivirus settings for a webcam or video protection feature and add Chrome as a trusted app.
* Try opening the Talview link in an incognito window if permissions aren't working as expected. This helps rule out browser extensions that may be interfering.
# How to disable browser extensions
Source: https://docs.talview.com/candidates/system-diagnostics/how-to-disable-browser-extensions
Browser extensions can sometimes interfere with your exam experience, causing pop-ups, screen-sharing prompts, or unexpected behavior during a proctored session. In this article, you will learn how to disable browser extensions on Chrome, Firefox, Edge, and Safari before starting your exam on Talview.
#### **Before You Begin**
* Make sure you know which browser you'll be using for your exam
* Close any active exam sessions before making changes to your browser settings
#### **Step-by-Step Guide**
**Google Chrome**
1. Open Chrome and click the three-dot menu in the top-right corner
2. Go to **Extensions**, then select **Manage Extensions**
3. Toggle off any extensions you don't need for your exam
4. Refresh the session to apply changes
**Mozilla Firefox**
1. Open Firefox and click the three-line menu in the top-right corner
2. Select **Add-ons and themes**
3. Under **Extensions**, toggle off the ones you want to disable
4. Refresh the session to apply changes
**Microsoft Edge**
1. Open Edge and click the three-dot menu in the top-right corner
2. Go to **Extensions**, then select **Manage extensions**
3. Toggle off the extensions you don't need
4. Refresh the session to apply changes
**Safari**
1. Open Safari and click **Safari** in the top menu bar
2. Select **Settings**, then go to the **Extensions** tab
3. Uncheck the box next to each extension you want to disable
4. Refresh the session to apply changes
**Additional Tips**
* Disabling extensions rather than uninstalling them lets you turn them back on after your exam
* If you use multiple browser profiles, repeat these steps for each profile you might use during the exam
* Ad blockers and VPN extensions are common culprits that interfere with proctoring, check these first.
# How to disable the Gemini shortcut in Google Chrome?
Source: https://docs.talview.com/candidates/system-diagnostics/how-to-disable-the-gemini-shortcut-in-google-chrome
Google Chrome's built-in Gemini AI assistant can interfere with Talview proctored assessments. The Gemini side panel, keyboard shortcut, and sparkle icon may trigger proctoring alerts from Alvy during your exam session.
In this article, you will learn how to unpin the Gemini button and disable Gemini features in Chrome before starting your assessments.
### Before you begin
* Make sure you are using Google Chrome on a Mac or Windows computer.
* These steps apply to Chrome version 141 and later.
* Complete these steps **before** launching your proctored assessment
***
### Step-by-step Guide
**Step 1: Unpin the Gemini button from the toolbar**
1. Look for the sparkle-shaped **Gemini** button in the top-right corner of Chrome, next to your tabs.
2. Right-click the **Gemini** button.
3. Select **Unpin Gemini**.
The icon disappears from the toolbar. However, the Gemini side panel can still be triggered using a keyboard shortcut (`Alt+G` on *Windows*, `Cmd+G` on *Mac*), so continue with the next steps to fully disable them.
**Step 2: Turn off Gemini in Chrome settings**
1. Click the three-dot menu in the top-right corner of Chrome.
2. Click **Settings**.
3. In the left sidebar, click **AI innovations**.
4. Click **Gemini in Chrome**.
5. Toggle off all the settings listed under this section.
This removes the side panel, stops Gemini from reading your current tab, disables the sparkle prompt on text selection, and disables the keyboard shortcut.
**Step 3: Turn off additional AI features**
While you are still in the **AI innovations** section:
1. Click **Help me write**.
2. Toggle off **Offer writing help**.
This prevents Chrome from automatically opening AI writing suggestions in text boxes across websites, which can trigger proctoring alerts during your assessment.
**Additional tips**
* After completing these steps, restart Chrome and verify that the Gemini button and side panel are no longer visible before starting your assessment.
* These settings only affect Gemini inside Chrome. They do not change Gemini features in Gmail, Google Search, or other Google services.
* If you do not see the **AI innovations** option in your Chrome settings, your version of Chrome may not have Gemini enabled yet, and no action is needed.
* Using Chrome in **Incognito mode** also prevents Gemini from activating during a session, but disabling via settings is the recommended approach for a proctored assessment.
# How to install and position a Secondary Camera?
Source: https://docs.talview.com/candidates/system-diagnostics/how-to-install-and-position-a-secondary-camera
A secondary camera is your mobile device’s front camera used for monitoring during your exam session. This mobile device will provide an additional angle for proctors, allowing them to have a wider view of your test environment.
Below is a step-by-step guide on how to install and position your secondary camera successfully.
## ✅ Prerequisites
1. A mobile device (smartphone or tablet) to be used as the secondary camera.
2. A stable internet connection.
## ⏲️ Step-by-Step Guide
### Step 1: Preparing Your Secondary Camera
1. **Charge Your Device**: Ensure that the mobile device you are using for the secondary camera is fully charged to avoid interruptions.
2. **Functional Front Camera:** Ensure your mobile device’s front camera is functional
### Step 2: Connecting the Secondary Camera
1. **QR Code Scanning**:
* During your onboarding, you will see an option to connect your secondary camera using a QR code.
* Use your secondary device’s camera to scan the QR code.
2. **Check for Permissions**
* Your default browser will need permissions to access your camera and microphone.
* Read here on how to give permissions
3. **Follow On-Screen Instructions**:
* Read through the instructions and proceed to the next steps on your mobile device.
### Step 3: Positioning the Secondary Camera
1. **Choose an Optimal Location**:
* **Wide Angle**: Place the secondary camera in a diagonal position from your test desk. Should not be more than 2 feet apart from your seat.
* **Avoid Obstruction**: Ensure that no objects or furniture block the camera’s line of sight.
2. **Mounting the Camera**:
* Use a tripod or a stable surface (like a shelf or table) to position the camera securely.
* If using a mobile phone holder or a stands, make sure it’s sturdy.
3. **Height and Angle Adjustment**:
* Position the camera at eye level or slightly above, directing it towards where you will be seated during the test.
* Tilt the camera downwards slightly to capture your face and immediate surroundings.
### Step 4: Verify Connectivity
1. Ensure that both the primary and secondary devices remain connected to the internet throughout your test.
2. Run a quick internet speed test to confirm a stable connection is maintained.
### Final Check
Before beginning your test, double check that:
* The secondary camera is properly linked to the primary device.
* The positioning provides a clear and unobstructed view of your testing area.
* Both devices are charged or connected to a power supply and ready for the duration of the exam.
# How to pass the speech test as a non-native english speaker?
Source: https://docs.talview.com/candidates/system-diagnostics/how-to-pass-the-speech-test-as-a-non-native-english-speaker
As part of the system checks, you will be asked to **read a sentence aloud while your voice is recorded**. This is just to verify your **microphone** and speaking ability- **not an English fluency test**.
If you're a non-native English speaker, don’t worry - you can absolutely pass this with a few simple tips.
## ✅ What the Speech Test Looks For
| **What It Checks** | **How You Can Pass** |
| :----------------------- | :--------------------------------------------------------------------------------------- |
| Voice clarity and volume | Speak clearly and at a normal volume — not too soft or too loud |
| Sentence accuracy | Read **exactly what’s shown on screen**, word for word |
| Background noise | Find a **quiet room** and close windows, doors, and background apps |
| Mic input quality | Use your **laptop mic or a basic headset** — avoid covering it with your hand or clothes |
## 🗣️ Tips to Pass as a Non-Native Speaker
* **Don’t rush.** Read at a calm, steady pace - clarity matters more than speed.
* **Speak naturally.** No need to fake an accent or over-pronounce.
* **Practice aloud once** before clicking “Start Recording”.
* If you’re unsure of a word, **sound it out confidently** — don’t skip or replace it.
* Avoid filler sounds like "uh", "umm", or whispering.
### Before You Begin
* Make sure your microphone is **unmuted** and working (you can test in your system settings)
* Sit in a quiet space and avoid fans, TV, or talking around you
* Close apps like Zoom, Teams, or Meet that may be using the mic
# How to run a network speed test?
Source: https://docs.talview.com/candidates/system-diagnostics/how-to-run-a-network-speed-test
Before attending any assessment or interview, it’s important to ensure that your internet connection is fast, stable, and reliable.
The **System Readiness Check** helps you identify any network issues in advance so you can avoid disruptions during your session.
## 🚀 What the Network Speed Test Checks
When you click **Start Check**, Talview’s system will automatically test:
* **Connectivity** – Verifies that your device is online and able to connect to our servers.
* **Bandwidth** – Checks if your internet speed is sufficient for video streaming and real-time interaction.
* **Latency** – Measures how quickly data travels between your device and our servers. Lower latency means smoother video and audio.
This check usually takes a few seconds and shows real-time results for each area.
### ✅ How to Run the Check
1. Go to the **System Readiness Check** page.
2. Click the **Start Check** button.
3. Wait while the system analyzes your internet connection.
Each test will be marked as either **Passed**, **Warning**, or **Failed**, along with helpful messages to guide you.
### 🔍 Understanding the Results
If all tests pass, you're ready to proceed with your assessment or interview.
* If **Connectivity** fails: You are not connected to a stable internet source.
* If **Bandwidth** is low: You may experience frozen video or delayed audio. You may be using a congested or limited-speed network.
* If **Latency** is high: You may face choppy video or audio echo due to data delays.
### ⚠️ What to Do if You See a Warning or Failure
Here are some tips if your speed test result indicates high latency, low bandwidth, or unstable connectivity:
* **Use a wired connection** instead of Wi-Fi if available.
* **Close apps and tabs** that use the internet heavily (e.g., Zoom, Netflix, YouTube).
* **Avoid VPNs**, as they may increase latency.
* **Restart your modem/router** before retrying the check.
* **Sit closer to your Wi-Fi router** if you're on wireless.
* If you're using a mobile hotspot, ensure you have full signal and no background apps consuming data.
### 🔁 When Should You Retest?
Click **Retest** if:
* You've made any network changes (e.g., switched to mobile data or a different Wi-Fi).
* You closed apps or restarted your router.
* Your test showed a warning or failure earlier.
This ensures you're fully prepared before your session begins.
**Pro Tips for a Smooth Experience on Talview**
* Run the system check at least 15 minutes before your scheduled test or interview.
* Use a quiet, well-lit room with minimal distractions.
* Ensure your camera and microphone are working and allowed in your browser.
* Do not switch devices or networks once you’ve started the session.
## 📚Related Articles:
For detailed help, check these:
* [*Latency Issues and Their Impact on Audio/Video*](https://docs.talview.com/candidates/system-diagnostics/how-network-latency-affects-audio-and-video-quality#how-network-latency-affects-audio-and-video-quality)
* [*Background Apps Eating Bandwidth (Zoom, Netflix, etc.)*](https://docs.talview.com/candidates/system-diagnostics/network-and-connectivity/why-do-background-applications-cause-bandwidth-and-latency-issues#why-do-background-applications-cause-bandwidth-and-latency-issues)
* [*VPN Use and High Latency Errors*](https://docs.talview.com/candidates/system-diagnostics/why-does-vpn-usage-trigger-high-latency-warnings#why-does-vpn-usage-trigger-high-latency-warnings)
* [*Packet Loss: What It Is and How to Fix It*](https://docs.talview.com/candidates/system-diagnostics/why-is-packet-loss-affecting-my-video-or-audio#why-is-packet-loss-affecting-my-video-or-audio)
* [*Minimum Network Requirements (Upload/Download/Latency)*](https://docs.talview.com/candidates/system-diagnostics/why-is-my-network-not-meeting-test-requirements#minimum-network-requirements)
* [*Using Mobile Hotspot Without Interruption*](https://docs.talview.com/candidates/system-diagnostics/how-to-use-mobile-hotspot-without-interruption#how-to-use-mobile-hotspot-without-interruption)
* [*Wi-Fi Strength Testing G*](https://docs.talview.com/diagnostics/wifi-strength-testing-guide)[*uide*](https://docs.talview.com/candidates/system-diagnostics/why-is-a-strong-wi-fi-signal-required-for-live-sessions#why-is-a-strong-wi-fi-signal-required-for-live-sessions)
# How to soundproof a temporary test space?
Source: https://docs.talview.com/candidates/system-diagnostics/how-to-soundproof-a-temporary-test-space
When setting up a temporary test space, minimizing ambient noise is crucial for a smooth and fair experience. Here's how to soundproof your temporary setup briefly and effectively:
When using a temporary room for your assessment or interview, reducing ambient noise is essential to avoid audio issues or monitoring alerts. This checklist helps you quickly minimize external sounds and improve audio clarity in short-term setups.
***
### ✅ Common Causes and Fixes
| What might be wrong | How to fix it |
| :------------------------------------------ | :------------------------------------------------------------------------- |
| Room is close to outside or household noise | Choose the innermost room, away from streets, common areas, or appliances |
| Noise entering through windows | Select a room with fewer windows and keep them fully closed |
| Sound leaking through door gaps | Use a door sweep, draft stopper, or rolled towel at the bottom of the door |
| Noise coming from vents or air gaps | Temporarily cover vents or gaps if safe and feasible |
| Door not fully blocking sound | Keep the door closed and ensure it is firmly latched |
**Additional tips:**
* Use headphones with a built-in microphone to reduce ambient sound pickup.
* Inform household members of your test time and request minimal noise.
* Turn off fans, air conditioners, or appliances that create background hum.
* Run the system or video diagnostic check before starting and address any audio warnings.
* Set up the space at least **10 minutes early** to make adjustments if needed.
# How to troubleshoot latency warnings?
Source: https://docs.talview.com/candidates/system-diagnostics/how-to-troubleshoot-latency-warnings
Latency warnings indicate delays in network communication or processing times that exceed expected thresholds. These warnings can adversely affect system performance, user experience, and application responsiveness.
This article provides a step-by-step diagnostic approach to identify, troubleshoot, and resolve latency warnings in various IT environments.
## Common Causes of Latency Warnings
* Network congestion or packet loss
* Insufficient bandwidth
* Overloaded servers or hardware resources (CPU, RAM, Disk I/O)
* Misconfigured network devices (routers, switches, firewalls)
* Faulty or outdated network cables and hardware
* Background processes consuming excessive resources
## 📶Steps to Troubleshoot Latency Warnings
1. **Check Network Connectivity**
* [Run a speed test](https://speed.talview.com/) to verify internet speed.
* Use `ping` or `traceroute` to identify network delays or packet loss.
* Restart network devices (routers, switches).
2. **Monitor System Resources**
* Use Task Manager (Windows) or Activity Monitor (Mac) to check CPU and memory usage.
* On servers, use commands like `top`, `htop`, or resource monitoring tools.
* Close unnecessary applications or services consuming excessive resources.
3. **Review Application Performance**
* Check application logs for errors or warnings.
* Update software to the latest version to fix bugs or inefficiencies.
* Restart the application or service experiencing latency.
4. **Inspect Hardware Health**
* Verify disk health and speed using system tools.
* Ensure sufficient RAM is available.
* Replace or upgrade aging or faulty hardware components.
5. **Validate Configuration Settings**
* Review network and application configurations for incorrect settings.
* Reset to default or optimized configurations if needed.
### **Additional Tips:**
* **Reboot devices:** Restart computers, routers, and modems regularly to clear temporary network issues.
* **Run speed tests:** Check your internet speed to confirm you are receiving expected bandwidth.
* **Use wired connections:** Prefer Ethernet over Wi-Fi for sensitive or high-bandwidth applications.
* **Monitor latency continuously:** Use network monitoring tools to detect patterns and proactively manage issues.
# How to use mobile hotspot without interruption?
Source: https://docs.talview.com/candidates/system-diagnostics/how-to-use-mobile-hotspot-without-interruption
If you are using a mobile hotspot for your session, fluctuations in signal strength or bandwidth can cause warnings, lag, or disconnections in Talview. This checklist helps you identify common hotspot-related issues and stabilize your connection before continuing.
## ✅ Common Issues and Fixes with Mobile Hotspot
| **What Might Be Going Wrong** | **What You Can Do** |
| ---------------------------------------------- | ---------------------------------------------------------------------------------------- |
| Weak mobile signal or poor network zone | Move to an area with better signal (near a window or open space) |
| Battery saver mode on your phone or laptop | Disable battery saver to prevent Wi-Fi/hotspot interruptions |
| Hotspot auto-turn-off due to inactivity | Adjust your phone's settings to **keep hotspot always on** |
| Other apps using mobile data in the background | Turn off background apps and data sync (especially on the hotspot device) |
| Shared hotspot with other users or devices | Disconnect all other devices and use the hotspot only for your test or interview session |
## ⚠️ Signs Your Hotspot Isn’t Stable
Watch out for these indicators during your system check or live session:
* You see a **“Connectivity: Warning”** or **“Bandwidth: Low”** alert
* Your audio or video keeps cutting out
* The session freezes or reconnects automatically
* You are logged out of a proctored assessment or interview mid-way
## 🛠️ How to Optimize Hotspot Usage for Talview
Here’s how to get the best performance out of your mobile hotspot:
* **Use 4G or 5G network** — Avoid 2G/3G connections
* **Keep the hotspot device plugged in and charged**
* **Place the hotspot device close to your computer**
* **Limit movement** during your session to avoid signal drops
* **Enable airplane mode + Wi-Fi hotspot** on your mobile (if supported) to avoid call interruptions
* **Avoid using the same phone for both hotspot and Talview session** — use separate devices if possible
> Once done, [Run a Network Speed Test](https://speed.talview.com/) to check if you're ready.
## 🔁 When to Switch Networks
If you continue to face issues despite optimizations:
* Try switching to a home or office **Wi-Fi connection**
* Or, use a **wired (LAN) connection** for best stability
## 📚 Related Articles
* [*Latency Issues and Their Impact on Audio/Video*](https://docs.talview.com/candidates/system-diagnostics/how-network-latency-affects-audio-and-video-quality#how-network-latency-affects-audio-and-video-quality)
* [*Background Apps That Eat Up Bandwidth*](https://docs.talview.com/candidates/system-diagnostics/network-and-connectivity/why-do-background-applications-cause-bandwidth-and-latency-issues#why-do-background-applications-cause-bandwidth-and-latency-issues)
* [*Minimum Network Requirements for Talview*](https://docs.talview.com/candidates/system-diagnostics/why-is-my-network-not-meeting-test-requirements#minimum-network-requirements)
* [*How to Run a Network Speed Test*](https://docs.talview.com/candidates/system-diagnostics/how-to-run-a-network-speed-test#how-to-run-a-network-speed-test)
***
# How to resolve connection failure error?
Source: https://docs.talview.com/candidates/system-diagnostics/network-and-connectivity/how-to-resolve-connection-failure-error
If your system check shows a **“Connectivity: Failed”** status, your device is unable to reach Talview’s servers. In this article, we’ll guide you through common causes and solutions to resolve connectivity issues and ensure a smooth session.
## ✅ Common Causes and Fixes
| **What Might Be Wrong** | **What You Can Do** |
| :----------------------------------- | :--------------------------------------------------------------------------------------------------------------------- |
| Your internet is slow or unstable | Restart your modem/router. If possible, switch to a wired (LAN) connection. |
| Weak Wi-Fi signal | Move closer to your router or change to a stronger network. |
| VPN or proxy is interfering | [Disable VPN/Proxy](https://www.notion.so/Network-Connectivity-1ea3461472f38084a502fd2dfc3ffe03?pvs=21) and try again. |
| Using a school or office network | Contact your IT team to **whitelist Talview domains or use a personal hotspot.** |
| Multiple background apps | Close apps like video streaming, cloud backups, or downloads. |
| Your browser is outdated | Update to the latest version of Google Chrome, Microsoft Edge, Safari or Firefox |
| Security software is blocking access | Temporarily disable or allow Talview through your firewall/antivirus. Ask IT for help if needed. |
## 🌐 Final Check: Test Your Internet
Before reattempting your test/interview, make sure your connection is strong.
👉 [Run a Network Speed Test](http://google.com/)
## 📚 Related Articles
Still facing issues? Try these:
* Check this guide: [Troubleshoot VPN/Proxy Issues](https://docs.talview.com/candidates/system-diagnostics/why-does-vpn-usage-trigger-high-latency-warnings)
* Review our [Firewall and Network Setup Guide](https://docs.talview.com/candidates/system-diagnostics/talview-secure-browser-tsb-compatibility/why-is-antivirus-or-firewall-blocking-talview-secure-browser)
* Confirm your [Browser & Device Compatibility](https://docs.talview.com/candidates/interviews/diagnostics/system-requirements-for-a-smooth-interview-experience)
# How to resolve Connection warning error?
Source: https://docs.talview.com/candidates/system-diagnostics/network-and-connectivity/how-to-resolve-connection-warning-error
If you see a **“Connectivity: Warning”** status during the system check, it means your device is experiencing intermittent issues connecting to Talview’s servers. This can cause delays, buffering, or disruptions during your test or interview session.
In this article, we’ll guide you through common causes and fixes to resolve the warning quickly.
## ✅ Common Causes and Fixes
| **What Might Be Wrong** | **What You Can Do** |
| :---------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------- |
| Your internet is slow or fluctuating | Restart your **modem/router**. If possible, use a **wired (LAN) connection** for better stability. |
| Too many devices sharing the same network | Disconnect unused devices or avoid streaming or downloading on any connected device during your session. |
| Using a VPN or proxy server | [Disable VPN/Proxy](https://www.notion.so/1f53461472f3800eb73df1f91a426e4f?pvs=21) temporarily and try again. |
| Office firewall or network restrictions | Switch to a **home network or personal hotspot** or follow this [Firewall Setup Guide](https://www.notion.so/1f53461472f3800eb73df1f91a426e4f?pvs=21). |
| Using an outdated browser | Make sure you’re using the **latest version** of Chrome, Edge, Firefox, or Safari. |
## 🌐 Final Check: Test Your Internet
Before starting your test or interview, confirm your network is ready:
👉 [Run a Network Speed Test](http://www.speedtest.net/)
Make sure your:
* **Download speed** is at least 5 Mbps
* **Upload speed** is at least 1 Mbps
* **Latency (ping)** is below 100ms
Following these steps ensures a smooth and uninterrupted Talview session.
## 📚 Related Articles
Still seeing the warning? Try these steps:
* [How to Troubleshoot VPN or Proxy Issues](https://docs.talview.com/candidates/system-diagnostics/why-does-vpn-usage-trigger-high-latency-warnings)
* [Firewall and Network Configuration Guide](https://docs.talview.com/candidates/system-diagnostics/talview-secure-browser-tsb-compatibility/why-is-antivirus-or-firewall-blocking-talview-secure-browser)
* [Browser and Device Compatibility Checklist](https://docs.talview.com/candidates/interviews/diagnostics/system-requirements-for-a-smooth-interview-experience)
# How to use Internet Speed Booster apps?
Source: https://docs.talview.com/candidates/system-diagnostics/network-and-connectivity/how-to-use-internet-speed-booster-apps
Internet speed booster apps claim to improve connection performance by optimizing network settings, managing background activity, or refreshing cached network data. While these apps cannot increase your actual internet plan speed, they may offer **minor improvements** in specific situations when used correctly.
This article explains **how these apps work**, **how to use them safely**, and **when they should not be used**.
### ✅ What Internet Speed Booster apps actually do?
Most speed booster apps focus on software-level optimizations, such as:
* Clearing DNS or network cache
* Closing or limiting background apps that consume bandwidth
* Resetting network configurations
* Prioritizing foreground app traffic
These actions may help **reduce minor software inefficiencies**, especially on older devices or heavily loaded systems.
### 🛠️ How to Use Internet Speed Booster apps effectively?
If you choose to use a speed booster app, follow these best practices:
* **Use it before your session**, not during a live test or interview
* **Run it once**, then close the app completely
* **Allow only essential permissions**
* **Restart your device** after optimization, if prompted
* **Run a network speed test** afterward to verify any improvement
Speed booster apps are most useful when:
* Your device has many background apps running
* Your system has not been restarted for a long time
* You experience minor, intermittent slowdowns
### 🚫 When NOT to use Internet Speed Booster apps?
Speed booster apps are **not effective** in the following situations:
* **Your internet plan speed is low**\
Apps cannot increase the speed provided by your ISP.
* **You have a weak Wi-Fi signal**\
Distance from the router, walls, or interference cannot be fixed by software.
* **Your router or hardware is outdated**\
Old routers, damaged cables, or faulty network adapters require hardware fixes.
* **You are using a mobile hotspot with poor signal**\
Cellular signal quality depends on network coverage, not device optimization.
* **The app runs continuously in the background**\
Apps that consume CPU, memory, or bandwidth can actually **worsen performance**.
* **The app promises unrealistic speed increases**\
Claims like “2× faster internet” or “boost speed by 300%” are unreliable.
### Better alternatives to improve internet performance:
Instead of relying on speed booster apps, consider these proven steps:
* Restart your modem and router
* Use a wired (LAN) connection where possible
* Move closer to your Wi-Fi router
* Close bandwidth-heavy apps (Zoom, streaming, cloud sync)
* Disable VPNs or proxies unless required
* Run a network speed test before starting your session
***
# Why do background applications cause bandwidth and latency issues?
Source: https://docs.talview.com/candidates/system-diagnostics/network-and-connectivity/why-do-background-applications-cause-bandwidth-and-latency-issues
If you're seeing **“Latency: Warning”** or **“Bandwidth: Low”** during the system check, background apps running on your device might be using up your internet bandwidth. This can lead to:
* Delayed audio or video
* Freezing screens
* Buffering during your test or interview
* Unstable proctoring sessions
Even if you're not actively using other apps, some may still run in the background and consume bandwidth. Applications such as video conferencing tools, streaming platforms, cloud backups, and system updates often continue to transmit data in the background, competing with your session for network resources.
## ✅ Common Background Bandwidth Consumers
* **Video conferencing apps** (Zoom, Google Meet, Microsoft Teams)
* **Streaming services** (Netflix, YouTube, Spotify)
* **Cloud sync tools** (OneDrive, Google Drive, Dropbox)
* **System or software updates** running automatically
* **Other users on the same network** streaming or downloading content
### ⚠️ How this affects your session?
You may experience bandwidth or latency issues if:
* Audio cuts out or is delayed
* Video freezes, buffers, or appears pixelated
* The system check shows **“Low Bandwidth”** or **“Latency: Warning”**
* Your session freezes or disconnects unexpectedly
### 🛠️ How to prevent Bandwidth drain?
Before starting your session:
* Close all unnecessary apps and browser tabs
* Exit video calls and stop media streaming completely
* Pause cloud backups and file sync services
* Temporarily disable auto-updates
* Ask others on the same network to pause heavy internet use
* Restart your device to clear background processes
Once completed, run a [Network Speed Test](https://www.speedtest.net/) to confirm your connection is stable and meets the minimum requirements.
## 📚 Related Articles
* [Latency Issues and Their Impact on Audio/Video](https://docs.talview.com/candidates/system-diagnostics/how-network-latency-affects-audio-and-video-quality#how-network-latency-affects-audio-and-video-quality)
* [Using Mobile Hotspot Without Interruption](https://docs.talview.com/candidates/system-diagnostics/how-to-use-mobile-hotspot-without-interruption#how-to-use-mobile-hotspot-without-interruption)
* [Troubleshooting VPN or Proxy-Related Latency](https://docs.talview.com/candidates/system-diagnostics/why-does-vpn-usage-trigger-high-latency-warnings)
* [Minimum Network Requirements for Talview](https://docs.talview.com/candidates/system-diagnostics/why-is-my-network-not-meeting-test-requirements#minimum-network-requirements)
***
# Preparing Your Audio Setup for the Test
Source: https://docs.talview.com/candidates/system-diagnostics/preparing-your-audio-setup-for-the-test
Echo or reverb in your room can reduce the clarity of your speech during audio checks or live sessions. These issues can cause proctor/interviewer to be alerted or poor detection during identity verification.
Clear audio is essential for instructions, identity verification, and monitoring during an assessment or interview. This guide helps you prepare your audio environment in advance to avoid echo, background noise, or microphone issues that could affect audio checks or trigger alerts.
***
### ✅ Audio Readiness Checklist
| What to Check | What to Do |
| :----------------- | :------------------------------------------------------------- |
| Microphone clarity | Speak at a normal volume and ensure your voice sounds clear |
| Room acoustics | Choose a smaller, furnished room to reduce echo or reverb |
| Background noise | Turn off TVs, music, fans, and nearby devices |
| Headphones | Use wired headphones with a built-in microphone, if permitted |
| Mic distance | Sit close enough so the microphone clearly captures your voice |
| Other audio apps | Close video calls, recorders, or voice assistants |
### 🔎 **Reducing Echo and Reverb**
Echo or reverb usually occurs in large or empty rooms with hard surfaces.
* Avoid unfurnished rooms or halls
* Sit closer to the microphone to reduce sound reflections
* Use soft furnishings like carpets, curtains, or cushions
* Prefer headphones with a built-in mic over laptop microphones
### 🔎 **Minimizing Background Noise**
Unexpected sounds can interfere with audio checks and monitoring.
* Inform others that you need uninterrupted privacy
* Close doors and windows to block street or household noise
* Silence mobile phones and keep them away
* Keep pets out of the room for the full duration
### 🔎 **Using Headphones for Better Audio**
Headphones help isolate your voice and prevent feedback.
* Use **wired headphones** to avoid Bluetooth latency
* Ensure the correct microphone is selected
* Avoid gaming headsets with heavy audio processing
* Connect headphones before opening the test link
### 🔎 **Final Audio Check**
Before starting your test:
* [**Test audio**](https://video-diagnostics.talview.org/) to confirm sound output
* Speak a few sentences to check for echo or distortion
* Ensure no other applications are using the microphone
* Do not change audio devices once the test begins
**Additional tips:**
* Set up your audio environment at least **10 minutes early**
* Stay in the same room for the entire session
* Avoid whispering or speaking too loudly
* Keep only test-related browser tabs open
***
# Preparing Your Test Environment Before You Begin
Source: https://docs.talview.com/candidates/system-diagnostics/preparing-your-test-environment-before-you-begin
Before starting your assessment or interview, it is important to set up a distraction-free, well-positioned, and compliant test environment. This guide walks you through the essential checks to ensure your seating, camera, audio, and surroundings meet monitoring requirements and help prevent avoidable interruptions.
***
### ✅ Environment Readiness Checklist
Use the checklist below to confirm your setup before launching the test.
| **What to Check** | **What to Do** |
| :------------------ | :---------------------------------------------------------- |
| Desk and chair | Sit at a stable desk using a proper chair with back support |
| Seating posture | Sit upright and centered; avoid slouching or leaning back |
| Camera position | Adjust your laptop or camera so it is at eye level |
| Camera framing | Ensure your face and shoulders are clearly visible |
| Background area | Choose a clean, neutral background with no movement |
| Room privacy | Make sure no people or pets will enter during the test |
| Noise level | Turn off TVs, music, and nearby devices |
| Phone interruptions | Silence your phone and keep it out of reach |
### 🔎 **Desk and Chair Setup (Required)**
Your seating arrangement directly affects camera framing and monitoring accuracy.
* Use a **desk or table**, not a bed, couch, or floor
* Sit on a **chair with proper back support**
* Keep your laptop on a **stable surface**, not your lap
* Adjust your seat height or laptop position so the **camera is at eye level**
### 🔎 **Camera and Visibility Checks**
Before starting:
* Sit with your **back facing a wall** to prevent movement behind you
* Ensure your **face and shoulders remain in frame**
* Avoid excessive movement, leaning, or turning away
* Check lighting so your face is clearly visible and not shadowed
### 🔎 **Audio and Noise Control**
* Turn off televisions, radios, and nearby devices
* Inform others that you need uninterrupted privacy
* Silence your mobile phone and keep it out of reach
* Use headphones (if permitted) to reduce ambient noise pickup
### 🔎 **Final Pre-Test Check**
Immediately before starting your test:
* Confirm camera framing and lighting
* Ensure no background movement or noise
* Verify that your seating position is comfortable and stable
Once the test begins, avoid adjusting your seat, desk, or camera unless instructed.
**Additional tips:**
* Set up your environment at least **10–15 minutes early**
* Avoid shared or high-traffic spaces
* Do not switch rooms, devices, or seating mid-test
* Keep only test-related browser tabs open
# Guide to Share your screen
Source: https://docs.talview.com/candidates/system-diagnostics/proctoring-onboarding/guide-to-share-your-screen
Screen sharing is mandatory during Talview's onboarding process to verify your identity and maintain assessment integrity. During the attendee onboarding, you'll be required to share your **entire screen** to allow the platform to monitor and record your on-screen activities throughout the session.
This article helps you understand the complete process of granting **screen sharing** permissions at both the system and browser levels.
***
### Supported Browsers
Talview V8 Proview supports screen sharing on the following browsers:
* Google Chrome
* Microsoft Edge
> **Note:** Avoid using *incognito or private browsing* mode, as it may block screen sharing permissions.
***
### System Permissions Setup
Before sharing your screen in the browser, you must grant system-level permissions for screen recording.
**For Windows:**
1. Click the **Start** button and open **Settings**.
2. Select **Privacy & Security** from the left sidebar.
3. Under **App permissions**, enable **Camera**, **Microphone**, and **Notifications** for your web browser.
4. Make sure screen capture is allowed in Privacy settings.
**For Mac:**
1. Open **System Settings** from the Apple menu.
2. Navigate to `Privacy & Security > Screen Recording`.
3. Enable screen recording permission for your browser (Chrome, Edge, or Firefox).
***
### How to Share Your Entire Screen
In the interview/assessment page, continue with the prechecks and when prompted to share the screen:
1. Click **Proceed to Exam** when prompted to initiate screen sharing.
2. A browser permission window will appear displaying screen sharing options.
3. Select **Entire screen** from the options at the top of the window.
4. Click on the *thumbnail preview* of your screen below the options.
5. Click the **Share** button to confirm and begin sharing.
You must select and share your **entire screen** to proceed with the assessment. Sharing individual tabs or application windows is not permitted.
**Additional Tips:**
* Use a personal device with full access rather than corporate laptops with admin restrictions.
* Disable browser extensions that may interfere with screen sharing permissions.
* If you stop screen sharing during the session, you can resume by sharing your screen again without restarting prechecks.
* Ensure your device doesn't have endpoint protection software that blocks screen recording.
# How to access help during a proctored session
Source: https://docs.talview.com/candidates/system-diagnostics/proctoring-onboarding/how-to-access-help-during-a-proctored-session
During a proctored exam, technical issues or setup-related questions can arise at any stage, before the exam starts or during onboarding. To ensure your exam experience remains smooth and uninterrupted, the proctoring system provides a **built-in Help option** that is available throughout the session.
In this article, you can understand how this feature allows you to quickly reach support, access self-help articles, run diagnostics, or raise a ticket, without exiting your exam flow.
A **Need Help** option is always visible at the **bottom-left corner of the screen**, ensuring support is just one click away.
***
### Using the “Need Help” option
The **Need Help** option opens the **Chat with a Proctor** window, where you can view all proctor messages and send queries in real time. Messages from the proctor may include:
* **Session instructions and guidelines** – shared at the beginning of your session
* **Rule violation warnings** – sent if any prohibited behavior is detected during the session
* **Query responses** – answers to any questions you raise during the session.
**Step 1: Open the Help panel**
If you face **any issue or difficulty**, click on the **Need Help** button.
This opens a **chat panel** where you can explain the issue you’re facing.
**Step 2: Describe your issue clearly**
* Be **direct and specific** about the problem (for example: *camera not turning on*, *mic blocked*, *network issue*)
* Clear details help the **proctor or Assistance bot respond faster**
The system may:
* Connect you to a **live proctor**, or
* Share **relevant help articles and diagnostics steps** instantly through the chatbot
**Step 3: Attach a screenshot**
Near the typing area, you’ll see an **Attach** option.
Use this 📎 to upload a **screenshot of the issue** you’re facing.
This helps support teams understand the problem faster and resolve it more efficiently.
***
### Using the Help Center
At the **top-right corner of the Help panel**, you’ll see three icons.
**Help Center (Open book icon)**
* Opens the **Help Center**
* Lists **common issues** you might face during onboarding or the exam
* Each article provides **immediate, step-by-step solutions**
If the proctor is taking time to respond, you can search or select an article here to resolve the issue on your own.
🔗 **Need more help?**
At the bottom of the Help Center, you’ll find a **Need more help** link.
Clicking this allows you to **raise a support ticket**, and the team will get back to you shortly.
To return to the chat, simply click the **Chat** icon in the same location.
***
### Running Diagnostics
Diagnostics button (next to Need Help)
If you suspect a technical issue, click the **Diagnostics** option.
This allows you to:
* Check **device compatibility**
* Verify your **operating system**
* Confirm **browser compatibility**
* Test **camera and microphone**
* Grant required **permissions** if access is blocked
Running diagnostics early can help prevent interruptions during the exam.
***
### Exiting the Help panel
The **third icon** in the top-right corner lets you **exit the Help panel** and return to the onboarding or exam screen once your issue is resolved.
**What you need to know**
* Help is available **throughout onboarding and the exam**
* Be **clear and specific** when reporting issues
* Use screenshots whenever possible
* Try the **Help Center and Diagnostics** for faster resolution
# How to access help on your phone
Source: https://docs.talview.com/candidates/system-diagnostics/proctoring-onboarding/how-to-access-help-on-your-phone
During your assessment, when accessing **Help** on your mobile device (secondary device), you may notice that no pop-up appears after tapping the **Help** option.
Help resources are accessible through your *primary device*, not the secondary (mobile) device used for proctoring.
***
### **Understanding Help Access Limitations**
During Attendee Onboarding:
* Your **primary device** (laptop/desktop) runs the assessment interface.
* Your **secondary device** (mobile phone) functions as a proctoring camera.
The Help module is designed to open on the **primary device interface only**.
For security and session stability reasons, Help pop-ups are not displayed on the mobile device.
***
### **Accessing Help During Your Assessment**
**✅ If Your Primary Device Is Available**
1. Switch to your **primary device (laptop/desktop)**.
2. Click on the **Help** option from the assessment interface.
3. The Help window or support options will open there.
All troubleshooting guidance and support links will be available through the primary screen.
***
**❗ If Your Primary Device Is Not Accessible**
If you are unable to access Help from your primary device:
You can still get assistance through the following options:
* Visit the official Talview documentation at: [**docs.talview.com**](http://docs.talview.com) . You can run diagnotiscs on your secondary device using this [**link**](https://docs.talview.com/candidates/system-diagnostics/run-diagnostics).
* Raise a support ticket via your assessment communication channel (if provided).
> **Note**: Search for relevant guidance under the **Candidates → System Diagnostics** section.
***
**Important Notes**
* Help functionality is intentionally restricted to the primary device in V8 Proview.
* The mobile device is strictly used for proctoring and monitoring.
* No pop-up appearing on the phone when tapping Help is normal and not a technical error.
> If you are experiencing technical issues during onboarding, always attempt to access **Help** from your primary device first.
# How to share your screen during a proctored session
Source: https://docs.talview.com/candidates/system-diagnostics/proctoring-onboarding/how-to-share-your-screen-during-a-proctored-session
In this article, we explain what screen sharing is, why it is mandatory for a proctored exam, and how it helps ensure a fair and secure assessment. Screen sharing allows the system to monitor your exam screen in real time, without it, the exam **cannot begin**.
***
### Screen sharing during the exam
**Step 1: Review the instructions**
On the screen-sharing page:
* You’ll see a **short visual guide (GIF or preview)** showing how to share your screen
* A message explains that the proctor needs to view your **entire screen** before the exam starts
This ensures all exam activity is visible and monitored correctly.
**Step 2: Click “Share Screen”**
Click the **Share Screen** button to proceed.
A system window will open, allowing you to choose what you want to share.
**Step 3: Choose what to share**
You’ll see **three options**:
* **Browser (Any browser tab)**
* **Window**
* **Entire Screen**
**Important**
You are expected to select **Entire Screen**. Selecting any other option may prevent you from continuing.
**Step 4: Start sharing**
Once you’ve selected **Entire Screen**:
* Click **Share**
* Your screen sharing will begin
* The proctoring system will confirm the screen is visible
After this step, you’ll be allowed to proceed with the exam.
**What you need to know**
* Screen sharing is **mandatory** for all proctored exams
* Always select **Entire Screen** when prompted
* Do not stop screen sharing during the exam
* If you face issues, use the **Need Help** option
# Parental consent for underage test takers
Source: https://docs.talview.com/candidates/system-diagnostics/proctoring-onboarding/parental-consent-for-underage-test-takers
# Proctored Exam Onboarding Guide
Source: https://docs.talview.com/candidates/system-diagnostics/proctoring-onboarding/proctored-assessment-onboarding-guide
Please read this guide **before starting your exam session**.
Make sure you have a **stable internet connection**, a **laptop**, a **secondary device (mobile device/tablet)**, and a **valid photo ID**.
***
### Step-by step Guide
**Step 1: Start the Session**
Start your exam session from the link provided to you. Once the session starts, you will be onboarded with the steps preparing your system for a proctored session.
**Step 2: Onboarding**
**Recording and Privacy**
* Review the data collected throughout the session.
* Face Capture
* Session Recording
* Photo ID Check
* Click **Accept and Continue**.
* The **Need Help** option will be available at the **bottom-left corner** throughout the session.
**Instructions**
* **Photo ID Confirmation**
* Make sure your **photo ID** is with you.
* Click **Yes, it’s ready**.
* **Secondary Device Check**
* Ensure you have a **fully charged secondary device** (phone or tablet).
* Click **Yes, it’s ready**.
**Allow Camera and Microphone access**
* Your browser will ask for permission to access:
* Camera
* Microphone
* **Allow both** to continue the session.
**Camera Position Check**
Sit facing the camera in a **well-lit area**. Make sure your **entire face is clearly visible**.
* Use the camera preview shown at the **bottom-left** to adjust your position.
* Click **Continue**.
**Share Screen**
A short visual guide will appear showing how to share your screen. You must share your **entire screen** to start the exam.
* Click **Share Screen**.
* You will see three options:
* Microsoft tab
* Window
* Entire Screen
* Select **Entire Screen** (not a tab or window).
* Continue once screen sharing is enabled.
**Step 3: Connect Secondary Device**
**Scan QR Code**
* Use your secondary device to **scan the QR code** shown on the laptop.
* Click **Continue** on the laptop.
* Enter the **8-digit verification code** displayed on your secondary device.
* Once connected, click **Get Started**.
**Step 4: Onboarding on Secondary Device**
**Allow Permissions**
* Allow **camera and microphone access** on the secondary device.
* Click **Continue**.
**Environment Check**
* Click **Proceed**.
* Use the camera to show a **360° view** of your exam environment.
* Match the blue **dots** for a steady and clear scan.
* Once completed successfully, click **Continue**.
**Photo ID Verification**
* Click **Proceed**.
* Select the following details:
* Country
* State
* ID Type
* Capture your ID:
* Front side → Click **Next**
* Back side → Click **Continue**
**Verification Complete**
* Wait while your ID and environment are verified.
* Once all checks are successful, click **Continue**.
**Place Secondary Device**
* Place the secondary device on a **stable surface**.
* Rotate and position it **horizontally** as instructed.
* Click on **Continue** on Primary device.
**Step 5: Exam and Session Control**
**Begin Exam**
* Onboarding is now complete.
* Your exam will start automatically once you click **Begin Exam**.
* If you face any issues during the exam, use the **Need Help** option at the bottom-left corner of the screen to reach your proctor.
***
📚 **Related Articles**
* [Why we use Proctoring and how it works](https://docs.talview.com/candidates/assessments/how-to/why-we-use-proctoring-and-how-it-works)
* [How to access help during a proctored session](https://docs.talview.com/candidates/system-diagnostics/proctoring-onboarding/how-to-access-help-during-a-proctored-session)
* [How to share your screen during a proctored session](https://docs.talview.com/candidates/system-diagnostics/proctoring-onboarding/how-to-share-your-screen-during-a-proctored-session)
# What information is collected and processed for a proctored session?
Source: https://docs.talview.com/candidates/system-diagnostics/proctoring-onboarding/what-information-is-collected-and-processed-for-a-proctored-session
Proctoring helps maintain the **integrity, fairness, and security** of the assessment. All information is collected **only for exam monitoring and verification purposes**. Please read this carefully before starting your proctored session.
This article explains the **type of information collected and processed** during a proctored exam session.
***
### A. Candidate and Session Information
During the session, the following basic details are processed:
* Name and email ID used to access the assessment
### B. Identity Verification Information
#### Photo Capture
To verify your identity, the system collects:
* A live photo of the candidate
* Images captured during onboarding
These images are used only to confirm that the registered candidate is taking the exam.
#### Photo ID Information
For identity verification, the following ID-related information is collected:
* Country and state selected by the candidate
* Type of ID provided
* Front and back images of the ID card
The ID images are processed for verification of the test taker.
### C. Device and Technical Information
#### Camera and Microphone Data
During the session, access is required to:
* Webcam (for face capture and monitoring)
* Microphone (to detect background audio)
Audio and video are recorded to ensure exam compliance.
#### Screen Sharing Information
To monitor exam activity, the following is collected:
* Entire screen view of the candidate’s system
* On-screen activity during the exam
Only **full screen sharing** is allowed. Partial screen or tab sharing is not accepted.
#### Device and Browser Information
The platform may collect:
* Browser type and version
* Device type (laptop/desktop)
* Operating system information
This helps ensure compatibility and troubleshoot technical issues.
### D. Secondary Device Information
#### Secondary Device
If a secondary device is used, the following information is processed:
* Camera and microphone access on the secondary device
* Verification code used to connect the device
* Live video feed during the session
The secondary device helps provide an additional view of the exam environment.
#### Environment Scan
During onboarding, the system collects:
* A 360° view of the exam environment
* Visual confirmation that no unauthorized materials are present
This information is used only to verify the exam setup.
### E. Exam Session Monitoring Data
#### Session Recording
Throughout the exam, the following may be recorded:
* Candidate video feed
* Screen activity
* Audio input
These recordings are reviewed **only if required by a trained proctor or exam administrator,** such as in case of policy violations or disputes.
#### Event Data
The system may log:
* Warnings or alerts generated during the session
* Connectivity interruptions
* Exam start and submission times
This helps maintain exam integrity.
### F. Post-Exam Information
#### Assessment Submission
After the exam:
* Your responses are securely submitted
* Session completion status is recorded
* Feedback is collected
A confirmation message is shown once submission is successful.
**Important Notes**
* All data is collected **strictly for proctoring and assessment purposes**.
* Access is limited to **authorized personnel only**.
* Information is handled according to applicable **data protection and privacy standards**.
# Why is a 360° room scan required for proctored exams
Source: https://docs.talview.com/candidates/system-diagnostics/proctoring-onboarding/why-is-a-360-room-scan-required-for-proctored-exams
Before your exam begins, V8 Proctoring asks you to complete a **360° room scan** using your camera. This step helps confirm that your exam environment is secure, distraction-free, and compliant with exam rules.
Without completing the room scan, the system can’t verify your surroundings, which may prevent you from starting or continuing the exam.
***
### ✅ Why to perform a 360° room scan
| **What we check** | **Why it matters** |
| :----------------------------------------- | :----------------------------------------------------------- |
| Presence of other people | Ensures no one else is assisting you during the exam |
| Unauthorized items (notes, books, devices) | Confirms no external help or reference material is available |
| Extra screens or electronic devices | Prevents unfair advantages or policy violations |
| Overall room visibility | Confirms the full exam area is visible and monitored |
| Distraction-free setup | Reduces interruptions and unnecessary alerts during the exam |
### 💡 How the 360° room scan helps you
* The scan is done **once**, before the exam starts
* It helps avoid **interruptions, warnings, or session flags** during your test
* The recording is used **only for exam verification** and reviewed **only if required**
* Your privacy is respected, and all data is stored securely
Completing the scan upfront helps your exam run smoothly so you can focus fully on answering questions.
**Tips for a successful room scan**
* Remove books, papers, and extra devices from your desk
* Choose a quiet room with good lighting
* Move your camera slowly and steadily during the scan
* Make sure all corners of the room are visible
# Run Diagnostics
Source: https://docs.talview.com/candidates/system-diagnostics/run-diagnostics
Standalone pre-session diagnostics runner
# How to enable screen share permission on windows?
Source: https://docs.talview.com/candidates/system-diagnostics/screen-sharing-and-permissions/how-to-enable-screen-share-permission-on-windows
Enabling screen sharing for online assessments and interviews is crucial for a smooth experience. These permissions ensure the integrity of the assessment process and facilitates effective communication during interviews.
If you're encountering issues with screen sharing on Windows, this article will help you diagnose and resolve common problems.
## ✅ Common Causes and Fixes
| What might be wrong | What you can do |
| :------------------------------------------------------------------------------------------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Browser permissions not granted (Chrome, Firefox, Edge, etc. | Check Browser Site Settings: a. **For Chrome**: Click the lock icon to the left of the URL in the address bar. Go to "Site settings." Look for "Screen" or "Camera and microphone" and ensure it's set to "Allow.” b. **For Firefox:** Click the lock icon, then "More information." Go to the "Permissions" tab and ensure "Share the screen" is set to "Allow.” c.**For Edge** : Click the lock icon, then "Permissions for this site." Ensure "Screen" is set to "Allow.” d.**Restart** your browser after making changes. |
| **Windows Privacy Settings** Restricting Screen Recording: Windows has built-in privacy settings that can block applications from accessing your screen. | Adjust Windows Privacy Settings: a. Go to **Start** > **Settings** > **Privacy & security** > **Screen recording** (or "Camera" under "App permissions" for older Windows versions) b. Ensure that "**Screen recording access**" is "On.” c. Under "Let apps access your screen recordings," ensure that the browser you are using for Talview (e.g., Google Chrome, Microsoft Edge) is toggled ON. d. If you are using a desktop application for Talview, ensure that application is also allowed access. |
| Multiple Monitors or Specific Monitor Selection Issues | Ensure Correct Monitor Selection: a. When prompted to share your screen, carefully review the options. You should see thumbnails or names of your connected displays. b. Select the specific monitor you intend to share. c. If you're sharing an application window, make sure that window is actively open and visible on your screen. |
| Browser Extensions causing conflicts | Disable Browser Extensions: a. Temporarily disable all browser extensions, especially those related to privacy, ad-blocking, or screen recording. b. Test screen sharing again. If it works, re-enable extensions one by one to identify the culprit. |
**Additional Tips:**
1. **Restart Your Computer:** Sometimes, a simple restart can resolve temporary glitches and refresh system permissions.
2. **Check for Pending Restarts:** After Windows updates, your system might require a restart to apply the changes fully.
3. **Test with a Different Browser:** If you're still facing issues, try using a different compatible browser to see if the problem persists. This can help determine if the issue is browser specific.
***
# Why is my screen share showing a black screen?
Source: https://docs.talview.com/candidates/system-diagnostics/screen-sharing-and-permissions/why-is-my-screen-share-showing-a-black-screen
If your screen share is showing a black screen, blank display, or nothing is visible during your assessment, permission issues, source selection problems, or graphics settings may be preventing proper screen capture. A black screen means others can't see your desktop or applications, which can prevent proctoring verification.
This guide helps you troubleshoot black screen issues and ensure your screen share displays correctly.
## ✅ Common Causes and Fixes
| What might be wrong | How to fix it |
| :------------------------------------------------------------------------------------ | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Selected wrong screen or window to share | When the screen sharing dialog appears, carefully select "Entire Screen" or your primary monitor (usually called "Screen 1" or "Display 1"), not "Application Window" or "Chrome Tab." If you selected a specific application that's minimized or closed, you'll see black. Click "Stop Sharing" and restart, selecting the correct entire screen option. |
| macOS screen recording permission not granted | **Mac:** System Settings > Privacy & Security > Screen Recording > check the box next to your browser (Chrome, Safari, Firefox, Edge). Your browser must completely quit and restart after granting this permission. Without screen recording permission, macOS shows a black screen instead of your actual display for security reasons. |
| Hardware acceleration causing conflictsDisable hardware acceleration in your browser. | **Chrome/Edge:** `Settings > System > turn OFF "Use hardware acceleration when available" > restart browser. ` **Firefox:**`Settings > General > Performance > uncheck "Use hardware acceleration" > restart.` Hardware acceleration can cause black screens with certain graphics cards or drivers. |
| Sharing application window that's minimized | If you selected a specific application window to share (not entire screen), that window must remain open and visible on your screen. Minimizing it shows black. Either maximize the application or switch to sharing your entire screen instead, which shows everything regardless of what's open. |
| Multiple monitors with wrong monitor selected | If you have multiple monitors, verify you're sharing the correct one. When prompted, select the monitor where your test content is displayed. If you selected your secondary monitor but your test is on the primary, viewers see black or a blank desktop. Disconnect extra monitors if unsure which is which. |
| Browser doesn't have permission to capture specific window | Some operating systems require additional permissions to capture certain windows. **Mac:** System Settings > Privacy & Security > Screen Recording must include your browser. **Windows:** Ensure no applications are blocking screen capture (some corporate security software prevents it). Try sharing entire screen instead of specific windows. |
**Additional tips:**
* Always select "Entire Screen" when prompted during screen sharing, not "Application Window" or "Chrome Tab", entire screen is most reliable and shows everything
* [**Test your screen share**](https://video-diagnostics.talview.org/) before your assessment by sharing your screen with a friend or family member to verify they can see your display correctly
* If using multiple monitors, disable or disconnect secondary monitors before your test to avoid confusion about which screen to share
* After granting any new permissions (especially on Mac), completely quit and restart your browser, permissions often don't take effect until the browser restarts
* Close all video streaming services, media players, and any tabs playing video content before screen sharing DRM protection causes black screens
* If black screen persists despite trying everything, restart your computer to reset all display and graphics systems to a known-good state
* Keep a backup device (laptop, tablet) available in case primary device screen sharing issues cannot be quickly resolved
# Why is Screen sharing blocked by admin restrictions?
Source: https://docs.talview.com/candidates/system-diagnostics/screen-sharing-and-permissions/why-is-screen-sharing-blocked-by-admin-restrictions
If you're unable to share your screen during a test or interview, it might be due to restrictions set by your system administrator or IT policy. This can prevent the platform from verifying your activity, which may result in delays, auto-cancellation of the session, or disqualification.
Follow the steps below to identify and resolve the issue quickly.
## ✅ Common Causes and Fixes
| **What Might Be Wrong** | **What You Can Do** |
| :--------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Device is managed by an organization (school/work) | Use a personal device if possible, or request temporary access permissions from your IT team. |
| Browser lacks screen share permissions | **On Google Chrome**, click the 🔒 lock icon in the address bar > Select Site settings > Set Camera, Microphone, and Screen sharing (if visible) to Allow > Refresh or restart the browser for changes to apply. **On Microsoft Edge**, click the 🔒 lock icon in the address bar > Choose Permissions for this site > Set Camera, Microphone, and Screen sharing (if available) to Allow > Restart the browser for changes to apply. On **Mozilla Firefox**, visit the site > When prompted, select the screen/window/tab to share > Click Allow to confirm sharing > Make sure you're not using Private Mode, as screen sharing is blocked there. |
| Security software blocking screen capture | Temporarily disable or configure antivirus/firewall settings to allow screen sharing. |
| Screen share not enabled for virtual desktops or remote sessions | Try using a direct system (not through Remote Desktop, Citrix, or similar environments). |
| Outdated browser or OS restrictions | Update your browser and operating system to the latest versions. |
## 🔐 For macOS Users: Grant Screen Recording Access
1. Go to **System Settings > Privacy & Security > Screen Recording**
2. Enable access for your browser (e.g., Chrome or Edge)
3. Restart the browser after enabling
### Additional Troubleshooting:
Still facing issues? Try these:
* Restart your browser and system
* Join the session using **Google Chrome, Microsoft Edge or Firefox** (recommended)
* Check if **screen recording is allowed** in your OS settings (especially on macOS)
## 🛠 Final Check: Test Your Screen Sharing
Before joining your interview, ensure that your system allows screen sharing.
👉 [Run a Screen Share Test](https://www.notion.so/1d73461472f38001a772e238965c2d4a?pvs=21) to confirm it’s working correctly.
You should be able to select and share your entire screen or a specific window.
# Why is screen sharing not working on Mac?
Source: https://docs.talview.com/candidates/system-diagnostics/screen-sharing-and-permissions/why-is-screen-sharing-not-working-on-mac
If screen sharing isn't working, shows a black screen, or you're getting permission errors on your Mac during your assessment, macOS Screen Recording permissions may not be granted. macOS requires explicit Screen Recording permission for browsers to capture and share your screen.
This guide helps you troubleshoot Mac-specific screen sharing issues and grant the necessary permissions.
## ✅ Common Causes and Fixes
| What might be wrong | How to fix it |
| :-------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Browser doesn't have Screen Recording permission | Grant Screen Recording permission to your browser. Go to System Settings (or System Preferences) > Privacy & Security > Screen Recording. Check the box next to your browser (Chrome, Safari, Firefox, Edge). **Important:** Your browser must completely quit and restart after granting this permission, close all browser windows, wait 10 seconds, then reopen. Screen Recording permission is required for screen sharing on Mac. |
| Permission prompt never appeared | If macOS never prompted you for Screen Recording permission, manually check:`System Settings > Privacy & Security > Screen Recording`. If your browser isn't listed, try screen sharing again, macOS should prompt you. If still no prompt, add your browser manually by clicking the "+" button and selecting it from Applications folder. |
| Screen share shows black screen after granting permission | Ensure you completely quit and restarted your browser after granting Screen Recording permission. **Important:** Clicking the red X doesn't quit on Mac, use `Cmd+Q or Chrome menu > Quit Chrome`. Permissions don't take effect until the browser fully restarts. After restarting, try screen sharing again. |
| Multiple browsers causing confusion | If you've used multiple browsers, ensure you granted Screen Recording permission to the specific browser you're using for your assessment. Each browser needs its own permission. Check `System Settings > Privacy & Security > Screen Recording `and verify your active browser is checked. |
| Screen Recording permission is grayed out | If the Screen Recording checkbox is grayed out and you can't change it, you may not have administrator access. Click the lock icon at bottom left of System Settings, enter your password (or admin password), then try checking the box again. Some corporate or school Macs restrict this, contact IT if locked. |
| macOS version too old | Screen Recording permission was introduced in macOS Catalina (10.15). If using an older macOS version (Mojave or earlier), update to at least macOS Catalina, or preferably the latest version. `Apple menu > System Settings > Software Update`. Screen sharing requires modern macOS security features. |
| Permission was granted but then revoked | macOS can revoke permissions if it detects issues. Go to `System Settings > Privacy & Security > Screen Recording`, uncheck your browser, click Apply, then check it again and click Apply. Quit browser completely (Cmd+Q), restart it, and try screen sharing again. This resets the permission. |
| System recently updated and permissions reset | Major macOS updates sometimes reset permissions. After updating macOS, always re-verify that Screen Recording permission is still granted: System Settings > Privacy & Security > Screen Recording > ensure browser is checked. Re-grant if needed and restart browser. |
| Full Disk Access confusion | Screen sharing typically needs **Screen Recording** permission, NOT Full Disk Access. Full Disk Access is for file system access (rarely needed for browser screen sharing). If someone mentioned Full Disk Access, they likely meant Screen Recording. Check Screen Recording permission first. |
### **Additional Tips:**
1. **Update macOS**: Ensure your macOS is up to date. Apple frequently releases updates that improve security and compatibility.
2. **Restart Your Router:** A simple router restart can sometimes resolve network-related issues that might be affecting screen sharing.
3. **Check Internet Connection:** Ensure you have a stable and strong internet connection. Poor connectivity can lead to dropped screen shares.
# Secondary Camera Setup Guide
Source: https://docs.talview.com/candidates/system-diagnostics/secondary-camera-setup-guide
For enhanced exam security, Talview uses your **mobile phone as a secondary camera**. This provides proctors with an extended view of your test environment, ensuring visibility beyond the primary webcam and helping maintain exam integrity.
In this article, you’ll learn how to prepare your **mobile device**, grant the required **mobile browser permissions**, position the camera correctly, and manage the secondary camera before and during the exam.
***
## ✅ Before You Begin
Ensure your **secondary device (mobile phone)** meets the following requirements before starting your test:
* **Fully charged battery** or connected to a power source to avoid interruptions
* **Functional front-facing camera** (selfie camera) and back camera
* **Stable internet connection** maintained throughout the test
* **Updated browser** - Google Chrome or Safari latest version
* **QR code scanning capability** through your phone's camera app or dedicated QR scanner
***
## 🧰 Setting Up Your Secondary Camera
### Step 1: Scan the QR Code
During candidate onboarding, a QR code will appear on your **primary device (laptop/desktop)**.
* Open your **mobile phone camera** or QR scanning app
* Point it at the QR code displayed on the primary screen
* This links your mobile phone as the **secondary camera** to the proctoring system
### Step 2: Grant Mobile Device Permissions
After scanning the QR code, your mobile browser will request permission to access device features. These permissions are **mandatory** for the secondary camera to function correctly.
#### Required Permissions on Mobile
You must allow the following:
* **Camera** – required to stream your environment
* **Microphone** – required for audio monitoring
* **Browser access** – allow permissions when prompted
#### How to Enable Permissions (If Blocked)
If permissions are denied accidentally -
**On Android (Chrome):**
1. Go to `Settings → Privacy & Security → Site Settings`
2. Select **Camera** and **Microphone**
3. Allow access for the exam URL
4. Refresh the browser page
**On iPhone (Safari):**
1. Go to `Settings → Safari`
2. Enable **Camera** and **Microphone**
3. Return to the exam page and refresh
> ⚠️ If camera or microphone permissions are not enabled, the secondary camera setup will fail, and you may not be allowed to continue the exam.
### Step 3: Position Your Phone
Place your **mobile phone (secondary device)** in a stable position using a tripod, phone holder, shelf, or table.
* Position the phone diagonally from your test desk
* Ensure it is no more than **2 to 2.5 feet away** from your seating position
* Do not handhold the phone during the exam
***
## 📷 Camera Positioning Guidelines
### 1. Optimal Setup Requirements
| **Positioning Aspect** | **Best Practice** |
| :--------------------- | :------------------------------------------------------------------------------------------------- |
| **Orientation** | Use landscape mode (hold phone sideways) for a wider viewing angle |
| **Camera Angle** | Position at eye level or slightly above, tilted downward toward your face |
| **View Coverage** | Capture your face, upper body profile (waist to head), computer screen, keyboard, and desk clearly |
| **Distance** | Place your secondary camera **2 to 2.5 feet away** from your primary device |
| **Lighting** | Ensure adequate lighting so the camera can see you clearly |
| **Obstructions** | Remove any objects or furniture blocking the camera’s line of sight |
### 2. Device Settings
* Disable **auto-lock / screen timeout** on your mobile phone
* Keep the phone **plugged into a power source** throughout the exam
* Close unnecessary apps to prevent background interruptions
***
## 📌 Essential Do's and Don'ts
### **Dos**
* Keep the secondary camera running continuously without interruptions.
* Maintain your phone in the same stable position throughout the test.
* Ensure both your primary and secondary devices stay connected to the internet.
* Keep both the *primary and secondary device* charged.
### **Don'ts**
* Do not touch, move, or reposition the mobile phone once set
* Do not block or obstruct the camera view
* Do not allow the phone battery to drain or disconnect
***
## 📲 What to do if you don’t have a Secondary device?
If you do not have access to a mobile phone or another supported device for use as a secondary camera:
* Check the test instructions or invitation to see if a secondary camera is mandatory for your assessment.
* Contact your exam administrator or organization in advance to inform them of the limitation.
* Do not start the exam unless you receive confirmation or alternate instructions, as proceeding without a required secondary camera may lead to disqualification or session termination.
Starting the exam without a required secondary camera may result in **session termination or disqualification**.
### **Additional Tips**
* Run a quick [internet speed test](https://speed.talview.com/) before your exam to confirm stable connectivity.
* Double-check that the secondary camera is properly linked to your primary device before beginning your test.
* Once the secondary camera reconnects successfully, resume your test as usual.
* Make sure your secondary device maintains a stable internet connection throughout reconnection.
* Ensure your camera view remains unblurred and clearly shows your testing area.
* Do not ignore warning messages when the proctor asks you to adjust your secondary camera during the examination.
# Setting Up a Quiet Space for Proctored Sessions
Source: https://docs.talview.com/candidates/system-diagnostics/setting-up-a-quiet-space-for-proctored-sessions
A quiet testing environment is critical for accurate speech detection, clear audio recording, and uninterrupted monitoring during a proctored session. Background noise or sudden sounds can interfere with system checks and may cause your session to be flagged for suspicious activity.
Follow the guidance below to create a distraction-free environment and avoid unnecessary interruptions during your assessment.
***
### ✅ Common Noise Sources and How to Reduce Them
| **Noise source** | **What you can do** |
| ----------------------------- | :--------------------------------------------------------------------------------------------------------- |
| Traffic, pets, people talking | Close doors and windows; inform others you’re taking a test or try taking the session from a quieter room. |
| Appliance hums or fans | **Turn off** non-essential electronics or relocate |
| Phone notifications or alerts | Enable **Do Not Disturb (DND)** mode and silence notifications on all nearby devices |
| Echo or poor room acoustics | Select a smaller room or add soft furnishings such as curtains or carpets to reduce echo |
### ☑️ Quiet Setup Checklist (Before You Begin)
* Choose a room with minimal background noise and echo
* Sit away from windows, balconies, or common areas
* Close all doors and windows securely
* Place your device on a stable surface
* Ensure pets and other people cannot enter the room during the session
### ⚠️ During the Proctored Session
* Avoid speaking unless instructed by the system or proctor
* Do not play music or use headphones unless explicitly permitted
* Remain seated and limit movement to prevent accidental noise detection
### 🔊 Audio Configuration Best Practices
Proper audio configuration ensures clear voice capture and helps the proctoring system accurately monitor your session. Incorrect audio settings may result in poor sound quality, missed prompts, or unnecessary alerts.
**Follow these audio best practices before starting your test:**
* Use the default system microphone unless another option is explicitly approved
* Ensure the microphone input volume is neither too low nor excessively high
* Disconnect unused audio devices (such as Bluetooth headsets or speakers)
* [**Test your microphone**](https://video-diagnostics.talview.org/) during the pre-check to confirm clear audio detection
* Avoid changing audio settings once the session has started
Correct audio setup reduces the risk of interruptions and helps maintain a smooth, compliant proctored testing experience.
# Supported Browsers and Versions
Source: https://docs.talview.com/candidates/system-diagnostics/supported-browsers-and-versions
If your test does not load correctly or certain features are unavailable, the issue is often related to the browser you are using on your primary (laptop/desktop) or secondary device (mobile phone/tablet). Unsupported, outdated, or restricted browsers can block access to the test or interfere with critical functions such as *camera, microphone, QR-code linking, and secondary camera streaming.*
In this article, you’ll learn which browsers and versions are supported on *desktop and mobile devices*, common browser-related issues, and how to verify that your setup meets the requirements, especially when a mobile phone is used as a secondary camera.
***
## ✅ Supported Browsers (Desktop)
Use the **latest stable version** of any of the following:
* **Google Chrome** (Recommended)
* **Mozilla Firefox**
* **Microsoft Edge** (Chromium-based)
Unsupported browsers include Internet Explorer, Opera, Brave, and heavily customized Chromium builds.
### **Desktop Browser Compatibility Status**
| **Browser** | **Passed (✅)** | **Warning (⚠️)** | **Failed (❌)** |
| :---------- | :--------------------------------------- | :----------------------------------------- | :---------------------------------- |
| Chrome | Version 114+, all permissions enabled | Version 100–113 or key permissions blocked | \< 100 or modified builds |
| Firefox | Version 102+, WebRTC and mic/cam enabled | Version 90–101, minor permission issues | \< 90, WebRTC missing, private mode |
| Edge | Version 114+ (Chromium) | Version 100–113 or enterprise restrictions | Legacy Edge or \< 100 |
***
## 📱 Supported Mobile Browsers
If your assessment requires a **secondary camera**, your *mobile phone browser* must also meet compatibility requirements. The secondary device is used to stream your environment and must remain connected throughout the session.
* **Android:** Google Chrome (latest version)
* **iOS:** Safari or Chrome (WebKit-based)
**Avoid:**
* In-app browsers (Gmail, LinkedIn, WhatsApp, Facebook, etc.)
* Private/Incognito mode
* Android WebView–based browsers
***
### **Mobile Browser Compatibility Status**
| **Platform** | **Browser** | **Passed (✅)** | **Warning (⚠️)** | **Failed (❌)** |
| :----------- | :---------- | :---------------------------- | :------------------------------------- | :------------------------------- |
| Android | Chrome | Version 114+, mic/cam allowed | Version 100–113, battery saver enabled | \< 100, WebView, mic/cam blocked |
| iOS | Safari | iOS 14+, permissions granted | iOS 12–13, limited features | iOS \< 12 |
| iOS | Chrome | Latest iOS + Chrome | Slightly outdated iOS | In-app browsers |
**Important Notes for Secondary Devices (Mobile)**
* The mobile browser must remain **open and active** for the entire test
* Do not minimize, lock, or switch apps once the secondary camera is connected
* Battery optimization, data saver, and background restrictions may interrupt streaming
* Always open the QR-code link in a **supported mobile browser**, not an in-app preview
***
## ✅ Common Causes and Fixes
| What might be wrong | What you can do |
| :---------------------------------------------------------- | :----------------------------------------------------------------------------------------- |
| Using an unsupported browser | Switch to one of the supported browsers listed below |
| Browser version is outdated | Update the browser to the latest available version |
| Browser running in compatibility or legacy mode | Disable compatibility settings and use standard mode |
| Using a mobile in-app browser (email or social apps) | Open the test or QR link directly in **Chrome (Android)** or **Safari (iOS)** |
| Using restricted browsers (Opera, Brave, Internet Explorer) | These are not supported—use Chrome, Firefox, or Edge |
| Secondary device browser not supported | Ensure your **mobile phone uses a supported browser** and is not in private or in-app mode |
***
## ✅ Final Check: Confirm Your Browser
Before starting your test:
1. Open your browser on both **primary and secondary devices**
2. Visit [**whatismybrowser.com**](http://whatismybrowser.com)
3. Confirm the browser name and version match the supported list
4. Update the browser if required
Using a supported and up-to-date browser on **both devices** ensures full compatibility, uninterrupted proctoring, and a smoother test experience.
***
# Supported Devices for Assessments
Source: https://docs.talview.com/candidates/system-diagnostics/supported-devices-for-assessments
To ensure a smooth and uninterrupted assessment or interview experience on Talview, you must use a **supported device** that meets the required technical standards. Using unsupported devices may prevent you from starting or completing your assessment.
## ✅ Allowed Devices
### **Primary Device: Laptop (Mandatory)**
All candidates are required to use a **laptop** as their primary device for assessments and interviews.
### Mobile Device (Conditionally Supported)
Mobile phones may be used **only if your organization has allowed attending the assessment on a mobile device**. If mobile access is not enabled by your organization, you will not be able to proceed using a mobile phone.
## ✅ Minimum Device Specifications
| **Component** | **Requirement** |
| :------------------------ | :--------------------------------------------------------------------- |
| **Device Type** | Laptop (mandatory for assessments) |
| **Operating System (OS)** | Windows 10 or latermacOS 12.6.7 |
| **RAM** | Minimum: 4 GBRecommended: 8 GB |
| **Processor** | Intel Core i3 (10th Gen or later)AMD Ryzen 3 or laterApple M1 or later |
| **Processor Speed** | 2.0 GHz or higher |
## ❌ Not Allowed Devices
The following devices are **not supported** for assessments:
* Tablets (iPad, Android tablets)
* Chromebooks (Google Chrome OS)
## 🛠 Final Check: Before You Begin
Before starting your assessment, make sure you have:
* Verified that your **laptop is functioning properly**
* Updated your **operating system and browser** to the latest supported version
* Completed the **system diagnostics check** provided in the test link
Using a supported device that meets these requirements helps avoid technical interruptions and ensures a secure assessment experience.
# Supported Devices for Interviews
Source: https://docs.talview.com/candidates/system-diagnostics/supported-devices-for-interviews
When attending a job interview on Talview, it is important to use a supported device to ensure a smooth and uninterrupted experience. Using compatible hardware and software helps avoid issues with video, audio, and connectivity during the interview.
## ✅ What is supported?
| Supported Devices | Supported Specifications |
| :-------------------- | :-------------------------------------------------------------------------------------------- |
| Laptops (Recommended) | **Operating Systems**: Windows 10 and above, macOS 12.6.7 and above, Linux RAM: 4GB and above |
| Mobile | **Operating Systems**: Android, iOS **RAM: 4GB** and above |
| Tablets | **Operating Systems**: Android, iOS |
### ✅ Recommended Setup
Although mobile phones and tablets are supported, **using a laptop is strongly recommended** for interviews. Laptops provide:
* A more stable and optimized interview interface
* Better support for typing, coding, or technical tasks
* Improved camera, microphone, and screen handling during live interviews
### 🛠️ Final Check: Preparing for Your Interview
Before the start of your meeting, please ensure that you have:
* Tested your device’s camera and microphone to confirm it functions properly.
* Ensure its charged or connected to a power source
* Ensure its connected to a strong wi-fi network.
# Supported OS Versions for Assessments
Source: https://docs.talview.com/candidates/system-diagnostics/supported-os-versions-for-assessments
To ensure your assessment or interview runs smoothly, your device must be on a **supported operating system (OS)**. The platform relies on OS-level support for critical features such as **camera access, microphone permissions, screen sharing, and secure browser functionality**.
Using an outdated or unsupported OS may prevent you from starting or completing the test.
## ✅ Supported OS Versions
| **Operating system** | **Minimum supported version** |
| -------------------- | ----------------------------- |
| Windows | **Windows 10 and above** |
| macOS | **macOS 12.6.7 and above** |
| iPhone/iPad | **iOS 14 and above** |
| Android | **Android 10 and above** |
Devices running older versions may experience issues such as blocked camera or microphone access, failed system checks, screen-sharing errors, or secure browser launch failures.
## 🔍 OS Compatibility Status Explained
| **OS Category** | **Passed** | **Warning** | **Failed** |
| --------------- | ------------------------------------- | ------------------------------- | -------------------------------------------- |
| **Windows** | Windows 10+ fully updated (no S mode) | Outdated Windows (\<10; S mode) | Unsupported OS (XP, RT, S mode, test builds) |
| **macOS** | 10.15+, 11+ | 10.13–10.14 | \< 10.13 |
| **Linux** | Ubuntu 18.04+ | Older but supported distros | Unsupported or test builds |
## 🖥 How to Check Your OS Version?
* **Windows:** `Settings → System → About`
* **macOS:** `Apple menu → About This Mac`
* **iOS:** `Settings → General → About`
* **Android:** `Settings → About phone`
## 🔄 What to do if your OS is outdated?
* Update your device to the latest available OS version
* Follow these links:
* 🔗 [Update your iOS device](https://support.apple.com/en-in/guide/iphone/iph3e504502/ios)
* 🔗 [Update your Android device](https://support.google.com/android/answer/7680439?hl=en)
* 🔗 [Update your macOS device](https://support.apple.com/en-in/108382)
* 🔗 [Update your Windows device](https://support.microsoft.com/en-us/windows/install-windows-updates-3c5ae7fc-9fb6-9af1-1984-b5e0412c556a)
* Switch to another supported device if your current one cannot be updated
* Contact your **test coordinator** if you’re unable to access a compatible device
# How to resolve Installation issues with TSB?
Source: https://docs.talview.com/candidates/system-diagnostics/talview-secure-browser-tsb-compatibility/how-to-resolve-installation-issues-in-sb
Installing the correct version of Talview Secure Browser (TSB) is essential to access secure assessments without interruptions. TSB installation issues can cause delays, test access errors, or disqualify your session.
Thus, if you're facing issues during installation, don’t worry, this article will help you resolve them step by step.
## ✅ Common Issues and Fixes
| **What Might Be Wrong** | **What You Can Do** |
| :------------------------------------------ | :--------------------------------------------------------------------------- |
| Admin restrictions on the device | Use a personal laptop or request admin access if using a work/school device. |
| Antivirus or firewall blocking installation | Temporarily disable **antivirus**/**firewall** and try again. |
| Incompatible OS | Ensure that you use the latest version of OS. |
| Poor internet connection | Reconnect to stable internet and retry download. |
| Installation blocked by browser security | Click on **keep** or **allow** when the browser shows a warning |
| The downloaded file is not running | Right-click and select **‘Run as Administrator’**. |
### Additional Tips
* Clear your browser cache and **cookies**
* Disable **browser extensions** temporarily
* Use a **different browser** (Chrome or Edge recommended)
* Restart your computer before retrying
## Additional checklist before the exam
Before you begin the exam, make sure that :
* You are using a **personal system**
* You have a **stable internet connection**
* You’re using **Google Chrome** or **Microsoft Edge** to download TSB
# How to uninstall Talview Secure Browser?
Source: https://docs.talview.com/candidates/system-diagnostics/talview-secure-browser-tsb-compatibility/how-to-uninstall-talview-secure-browser
**Talview Secure Browser (TSB)** is a specialized application designed to ensure exam integrity by restricting unauthorized access during online proctored assessments.
This article provides step-by-step instructions to uninstall TSB from **Windows** and **macOS** systems after completing your tests. Follow these guidelines to safely remove the browser and avoid common issues like leftover files or launch errors on future sessions.
**Before You Start**
* Make sure you have finished all scheduled tests and closed the *Secure Browser* before uninstalling it.
* On organization managed devices, consult your IT administrator before proceeding.
* If you plan to **reinstall TSB**, keep your original test email or download link handy so you can quickly install the latest version after uninstalling.
***
### **Uninstall Talview Secure Browser**
**1. Uninstall on Windows**
* Navigate to the **Windows Start menu.**
* Open `Settings > Apps > Installed apps (or Apps & features)`.
* Search for **"TalviewSecureBrowser"** in the search bar.
* Select and click on `three dots` .
* Click on `Uninstall`; confirm the action.
* Remove any remaining shortcuts from Start menu, desktop, or taskbar.
**2. Uninstall on macOS**
1. Open Finder and navigate to the Applications folder.
2. Drag or Move "**Talview Secure Browser**" to Trash (enter admin credentials if prompted).
3. Empty Trash to remove the application completely from your system (This is an optional step).
**Additional Tips:**
* Restart your computer after uninstalling to ensure all background processes and file locks are cleared.
* On managed devices (work or school laptops), confirm with your IT administrator that removal aligns with organizational policies.
* Verify complete removal by searching your system for "Talview" in file explorers or application lists.
# TSB - Platform Compatibility and System Requirements
Source: https://docs.talview.com/candidates/system-diagnostics/talview-secure-browser-tsb-compatibility/tsb-platform-compatibility-and-system-requirements
TSB ensures a secure, locked-down environment for online assessments on Windows and macOS devices, preventing access to unauthorized applications and maintaining test integrity.
Before starting your Talview assessment, ensure your device meets the minimum platform and network requirements listed below. Incompatible systems may prevent exams from launching or cause interruptions during proctored sessions.
***
### **Audience**
Candidates, administrators, and IT teams setting up systems for Talview-based online exams.
***
### **Prerequisites**
* Admin rights on the device to install or update applications
* Stable internet connection
* Functional webcam and microphone
* Permissions granted for camera, microphone, and screen sharing at system level to Secure browser
***
## **Platform Compatibility**
| Platform | Supported Versions | Notes |
| :------------ | :---------------------------------------------- | :---------------------- |
| **Windows** | Windows 10 (Version 1909 and above), Windows 11 | Fully supported for TSB |
| **macOS** | macOS Monterey (12.6.7) and above | Fully supported for TSB |
| **Linux** | Browser-based assessments only | TSB not supported |
| **Chrome OS** | Browser-based assessments only | TSB not supported |
> ⚠️ TSB is not supported on mobile devices, tablets, or virtual machines.
***
## **Hardware Requirements**
| Component | Minimum | Recommended |
| :---------------------- | :------------------------------------------------- | :------------------------------------ |
| **RAM** | 4 GB (2 GB free before launch) | 8 GB (4 GB free) |
| **Processor** | Intel Core i3 (10th Gen+) / AMD Ryzen 3 / Apple M1 | Intel Core i5+ / Ryzen 5+ / Apple M2+ |
| **Disk Space** | 500 MB free | 1 GB free |
| **Webcam & Microphone** | 720p HD webcam, functional microphone | Full HD webcam, functional microphone |
| **Display Resolution** | 1280×720 | 1920×1080 (Full HD) |
| **Power Source** | Plugged in during exam | UPS for longer sessions |
***
## **Software Requirements**
**Operating Systems:**
* Windows 10 or 11
* macOS 12.6.7 (Monterey) or above
Linux and Chrome OS only support browser-based tests; TSB installation not available.
## **Browser Requirements (for browser-based tests):**
* Google Chrome (latest to 3 versions prior)
* Microsoft Edge (latest to 3 versions prior)
Firefox and Safari are not supported for proctored sessions.
**Permissions:**
* Administrator rights are required to install or update TSB.
* Camera, microphone, and screen-sharing permissions must be granted during setup.
**Updates:**
* TSB automatically updates at launch.
* Launch TSB **15–20 minutes before the exam** to allow updates to complete.
* If you are facing any issues in updating Secure Browser, uninstall all previous versions and install the new version.
***
## **Network & Bandwidth Requirements**
For stable performance during live or recorded proctoring, ensure your connection meets the following parameters:
| Parameter | Recommended Value |
| :------------------ | :--------------------------------------------------- |
| **Connection Type** | Wired Ethernet preferred, Wi-Fi acceptable if stable |
| **Bandwidth** | Minimum 1 Mbps upload/download; 5 Mbps recommended |
| **Latency** | \<150 ms |
| **Jitter** | \<30 ms |
| **Packet Loss** | \<1% |
***
## **Additional Technical Considerations**
**Corporate or Managed Devices:**
* May require IT assistance for admin rights, firewall permissions, or proxy whitelisting.
**Not Supported:**
* Multiple monitors
* Virtual environments (VMware, Citrix, etc.)
* VPNs, screen recorders, and remote access tools
**Best Practices:**
* Close unnecessary background apps before launch
* Restart your system before the test
* Use a wired connection for better stability
* Keep webcam and microphone active and unobstructed
***
## **Quick System Check (Recommended)**
### **Internet Connection Check**
Before your exam, verify that your internet connection is stable and meets the required speed for proctored sessions.
* **Speed Test:** Run a quick test at [Talview Speed Test](https://speed.talview.com/) to ensure a **minimum speed of 5 Mbps** for both download and upload.
> *Tip: A wired Ethernet connection provides better stability than Wi-Fi.*
### **Camera and Microphone Test**
Your device must have a working camera and microphone for identity verification and continuous monitoring during the test.
* **Hardware Check:** Visit [Talview Video Diagnostics](/candidates/system-diagnostics/run-diagnostics) to confirm your **camera, microphone, and system audio** are functioning properly.
> *Ensure you allow all browser permission prompts for camera and microphone access.*
### **Run Diagnostics**
Launch Secure browser and run Diagnostics to check if any restricted applications are open. If you see the warning for applications being open, follow the instructions on screen and close the applications. This ensures smooth experience when attending the session in Secure Browser.
# What Causes the Restricted Software Error in TSB?
Source: https://docs.talview.com/candidates/system-diagnostics/talview-secure-browser-tsb-compatibility/what-causes-the-restricted-software-error-screen-in-tsb
When accessing Talview Secure Browser (TSB), you may encounter the **Restricted Software Error Screen**. This error occurs when unauthorized or conflicting software is detected on the system during the exam setup or launch process.
The purpose of this screen is to ensure exam integrity by blocking software that could interfere with the secure environment, such as screen recorders, remote desktop applications, or communication tools.
## ✅ Common Issues and Fixes
| **What Might Be Wrong** | **What You Can Do** |
| :-------------------------------------------------------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Background applications running during the exam | Check the system for apps running in the background. Disable unnecessary background apps from Task Manager (Windows) / Activity Monitor (Mac)→ Startup/Processes tabs or Settings → Apps → Startup Apps to prevent interference. |
| Antivirus or security software interfering with TSB | Disable Antivirus or Security Popups Temporarily. Some antivirus software may flag TSB. Disable it temporarily and re-enable it after the exam. |
| Multiple user accounts or virtual machines running simultaneously | Restart your computer to ensure all blocked processes are closed. Launch TSB again directly after restart. |
| Unauthorized browser extensions or monitoring tools | Reinstall Talview Secure Browser (if needed) Uninstall the current version. Download and install the latest version of TSB from the official Talview link provided in your exam instructions. |
| Background software or messaging apps auto-launching (e.g., WhatsApp, Zoom, Microsoft Teams, Slack) | `Settings → Apps → [App Name] → Advanced Options → Background App Permissions → Set to “Never” `
`Settings → Apps → Startup → Turn off [App Name]`
Also, ensure to close these apps from background processes before launching TSB. |
### Additional Tips
* Ensure you are using a **compatible operating system** (latest Windows or macOS).
* Contact **Talview Support** with a screenshot of the error screen and details of the software running on your system.
# Why Am I Seeing a “Virtual Desktop Detected” Error in the Secure Browser?
Source: https://docs.talview.com/candidates/system-diagnostics/talview-secure-browser-tsb-compatibility/why-am-i-seeing-a-virtual-desktop-detected-error-in-the-secure-browser
When accessing the Talview Secure Browser (TSB) for your exam, you may encounter a “Virtual Desktop Detected” error. This error appears when the system identifies that your device is connected to another system through Remote Desktop, Virtual Machine (VM), or screen-sharing software, or if you try to switch to a virtual desktop during the exam.
The purpose of this screen is to maintain exam integrity by preventing remote access tools or virtual environments that can compromise secure test conditions.
***
## ✅ Common Issues and Fixes
| What might be wrong? | What to do? |
| :-------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Another device or remote desktop connection is active** | Disconnect any remote desktop sessions, virtual machines, or screen-sharing apps. Close all remote access tools before launching TSB. |
| **Multiple devices connected with screen mirroring** | Ensure no other device (e.g., secondary screen, remote monitor, or device mirroring) is connected. Disconnect additional displays, HDMI cables, or screen-sharing setups. |
| **Security or IT policies from organization systems** | If using a work or institute-provided laptop, switch to a **personal system** without organizational security policies that enforce virtual desktops. |
## ✅ **Additional Troubleshooting Steps**
* Ensure you are using a compatible operating system (latest Windows or macOS version).
* Restart your system and launch TSB directly (without opening other apps first).
* If you continue facing the error, contact Support with:
* A screenshot of the error screen
* Details of connected devices or remote software previously installed.
Following these steps typically resolves the “Virtual Desktop Detected” error and allows you to proceed with your Talview exam smoothly.
***
# Why did TSB crash or close?
Source: https://docs.talview.com/candidates/system-diagnostics/talview-secure-browser-tsb-compatibility/why-did-tsb-crash-or-close
If the **Talview Secure Browser (TSB)** crashes or closes unexpectedly during your test or interview, it may interrupt the session or result in auto-submission. This can happen due to system limitations, background conflicts, or security software interference.
## ✅ Common Causes and Fixes
| **What Might Be Wrong** | **What You Can Do** |
| :----------------------------------------------- | :---------------------------------------------------------------------------------------------------- |
| System resources (RAM/CPU) are maxed out | Close all other applications before launching TSB. Avoid running screen recorders, IDEs, or browsers. |
| Antivirus or firewall force-closes TSB | Allow **TSB.exe** or **Talview Secure Browser** through your firewall/antivirus. |
| System auto-sleep or screen timeout is triggered | Set your power settings to "Never sleep" and disable screen savers during the session. |
| OS or driver issues | Ensure Windows/macOS is up to date. Restart your device before the test to apply pending updates. |
| Corrupted TSB installation | Reinstall TSB using the official download link from your test invitation. |
| External devices interfere | Disconnect any external displays or input devices (e.g., game controllers, docking stations). |
### Additional Tips
* [******Review the System Requirements for TSB******](https://pages.talview.com/tsb/): Ensure your device meets the necessary specifications for running the Talview Secure Browser.
* See our guide on [**Allowing TSB in Antivirus & Firewall**](https://talview.freshdesk.com/support/solutions/articles/11000129091-secure-browser-troubleshooting-guide): Learn how to configure your security settings to prevent interference with TSB.
* Reinstall using the [**Latest TSB Version**](https://www.talview.com/download-center): Download and install the most recent version of the Talview Secure Browser to ensure optimal performance.
## 🌐 Final Check: Prepare for Re-Launch
Before you relaunch TSB or resume the test:
* Restart your computer to clear temporary glitches
* Make sure your battery is charged or the device is plugged in
* Close all apps except TSB
# Why do browser extensions interfere with the Secure Browser?
Source: https://docs.talview.com/candidates/system-diagnostics/talview-secure-browser-tsb-compatibility/why-do-browser-extensions-interfere-with-the-secure-browser
If the **Talview Secure Browser (TSB)** fails to launch, crashes, or shows permission errors, the issue may be caused by **active browser extensions**. Extensions like ad blockers, VPNs, password managers, or screen recording tools can conflict with system checks or block access to the camera, mic, or secure features. This can result in missed sessions or test disqualification. Here’s what you can check to fix it.
## ✅ Common Issues and Fixes
| **What Might Be Wrong** | **What You Can Do** |
| :----------------------------------------- | :-------------------------------------------------------------------------- |
| Extensions are blocking camera/mic access | Disable all active browser extensions before launching TSB |
| Ad blockers are interfering | Temporarily turn off ad blockers (e.g., uBlock, AdBlock, Ghostery) |
| VPN, proxy, or security plugins running | Turn off browser-based VPN/proxy extensions before test |
| Password managers or autofill tools pop up | Disable tools like LastPass, Bitwarden, or browser password prompts |
| Extensions continue to run in background | Use a browser profile with no extensions, or try **private/incognito mode** |
### Additional Tip
To disable extensions:
* **On any browser**:
Open **Settings or Preferences** → Navigate to **Extensions/Add-ons**
Toggle **off all extensions** before starting your test
* **Or use Private/Incognito Mode**:
Most browsers block extensions by default in this mode
* Restart your browser and **relaunch the secure browser from your test link**
## 🌐 Final Check: Launching TSB
Before entering the test:
* Ensure no extensions are running in your other browsers.
* Fully close all regular browser windows
* Launch TSB from the provided link or shortcut without any browsers running
# Why does TSB show blank screen?
Source: https://docs.talview.com/candidates/system-diagnostics/talview-secure-browser-tsb-compatibility/why-does-tsb-show-blank-screen
If the **Talview Secure Browser (TSB)** opens but shows a **blank screen** or gets stuck while loading, it can stop you from starting your test or interview. This usually happens due to display settings, outdated system files, or blocked access.
## ✅ Common Causes and Fixes
| **What Might Be Wrong** | **What You Can Do** |
| :-------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Low system memory or slow boot | Restart your device and try opening TSB again after 1–2 minutes. |
| TSB is not installed properly | Uninstall TSB, then [download the latest version](https://pages.talview.com/securebrowser/) and reinstall it. |
| Black screen caused by antivirus | Open your antivirus and allow [**TSB/Talview Secure Browser**](https://talview.freshdesk.com/support/solutions/articles/11000129091-secure-browser-troubleshooting-guide) in the list of trusted apps. . |
| **System graphics driver** needs update | Update your Windows/macOS to the latest version and restart. |
| Display scaling or resolution issues | Right-click on desktop → **Display Settings** → Set **scale to 100%** and resolution to **Recommended**. |
| Multiple screens or display drivers | Disconnect external monitors and use only your main screen for the test. |
### Additional Tips
* Make sure your system meets the [TSB Requirements](https://pages.talview.com/securebrowser/)
* Fully restart your computer before retrying
* If the screen is still blank after loading, wait 1–2 minutes and don’t press any keys
## 🌐 Final Check: Try a Fresh Launch
Before retrying:
* Fully close TSB
* Disconnect all external displays or devices
* Right-click the **TSB icon → Run as Administrator** (on Windows)
# Why is antivirus or firewall blocking Talview Secure Browser?
Source: https://docs.talview.com/candidates/system-diagnostics/talview-secure-browser-tsb-compatibility/why-is-antivirus-or-firewall-blocking-talview-secure-browser
If your Windows or antivirus software flags **Talview Secure Browser (TSB)** or prevents it from downloading or launching, it may be due to your system's security settings.
Rest assured, TSB is a secure application trusted by leading institutions.
To resolve the issue:
* Add TSB to your antivirus or firewall’s list of trusted applications
* Or temporarily disable your antivirus while installing and launching TSB
***
## ✅ Common causes and fixes
| **What Might Be Wrong** | **What You Can Do** |
| :---------------------------------------------------------------------- | :---------------------------------------------------------------------------------------------------------- |
| Real-time protection closes the browser mid-test | Temporarily turn off **real-time protection** just for the duration of the test. Turn it back on afterward. |
| You’re using both antivirus and a firewall app | Allow TSB in both if you have separate antivirus and firewall tools. |
| Antivirus flags TSB as suspicious | Open your antivirus settings and add **Talview Secure Browser (TSB)** to the list of trusted apps. |
| Firewall is blocking internet access for TSB | Allow TSB through your firewall so it can connect to Talview’s servers. |
| “You may not have the appropriate permissions to access the item” error | Right-click on **TSB icon** and select **“Run as Administrator.”** |
### 🔐 How to disable antivirus & firewall (temporarily)?
* **Windows Defender (default antivirus/firewall):**
1. Open **Windows Security** > **Virus & threat protection**
2. Click **Manage settings** under "Virus & threat protection settings"
3. Toggle off **Real-time protection**
4. Now go to **Firewall & network protection**
5. Select the active network > Toggle off **Microsoft Defender Firewall**
> **Note:** Remember to turn these back on after the test.
* **Third-party antivirus/firewall software:**
1. Open the antivirus app > Settings > Look for **real-time protection** or **web protection** > Disable them temporarily
2. Also, check **Firewall settings** within the app and allow **Talview Secure Browser (TSB)**
### Additional Tips
* [Reinstall TSB ](https://www.talview.com/download-center)
* Restart your computer after making antivirus/firewall changes
* Don’t run any screen recorders, third-party security apps, or remote desktop tools
## 🌐 Final check: Relaunch TSB safely
Before restarting the test:
* Make sure your antivirus isn’t blocking TSB
* Close all apps except TSB
* Right-click on the **TSB icon → Run as Administrator** (on Windows)
# Why it’s a safer choice to use a personal device?
Source: https://docs.talview.com/candidates/system-diagnostics/using-personal-device-instead-of-corporate-one
Company-managed (corporate) devices often have restrictions that can interfere with proctored exams, such as blocking camera/mic access, preventing screen sharing, or disabling required browser features.
## ✅ Why use a personal device?
| **Corporate device risks** | **Personal device advantages** |
| -------------------------- | ---------------------------------------- |
| Camera/mic blocked by IT | Full access to hardware permissions |
| Screen sharing disabled | Screen share works with no admin blocks |
| Browser updates restricted | You can update or change browsers easily |
**Setup tips for personal devices**
* Use **Chrome**, **Edge**, or **Firefox** (latest version)
* Allow browser permissions for **camera**, **microphone**, and **screen sharing**
* Ensure you're not on a restricted **work network** (e.g., VPN or proxy)
***
# What are the Do’s and Don’ts for using a mobile hotspot?
Source: https://docs.talview.com/candidates/system-diagnostics/what-are-the-dos-and-donts-for-using-a-mobile-hotspot
Using a mobile hotspot for assessments or interviews can be convenient, but it requires careful handling to avoid connectivity issues. This article outlines essential do’s and don’ts to ensure a stable connection throughout your session.
## ✅ Common Causes and Fixes
| Do’s | Don’ts |
| :------------------------------------------------------------------------------------------------------------------------------------------------------------ | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Test Your Connection Ahead of Time:** Make sure to run a **speed test** on your mobile hotspot before the interview or test day | **Don’t Rely Solely on Cellular Signal:** Mobile hotspots can fluctuate in signal quality depending on your location. Don’t assume your signal will be strong, plan for a backup. |
| **Charge Your Device:** Make sure your mobile device is fully charged before the interview or test. If possible, keep it plugged in during use. | **Don’t Use Public Hotspots:** Public Wi-Fi networks can be insecure and unreliable. Stick with your personal mobile hotspot for a secure connection. |
| **Use A Dedicated Hotspot Device:** If available, use a dedicated mobile hotspot instead of tethering from your phone. This can improve connection stability. | **Don’t Multitask on Your Network:** Avoid streaming video or using other devices on the same hotspot during your interview or test to maintain bandwidth. |
| **Choose Your Location Wisely**: Find a spot that maximizes your signal strength—typically near a window or in a less obstructed area. | **Don’t forget about Security Protocol:** Ensure that your hotspot is password-protected to prevent unauthorized access, which could slow your connection speed. |
### **Additional Tips:**
1. **Have a Backup Plan:** Prepare a secondary connection option. Consider having access to a Wi-Fi network nearby or another mobile device with hotspot capabilities.
2. [**Run a speed test**](http://www.speedtest.net/)**:** Before starting your test or interview, it's a good idea to check your connection speed.
3. **Reboot Your Device:** If you experience connectivity problems, restarting your mobile device can sometimes resolve issues by refreshing the network connection.
# What are the recommended bandwidth and latency?
Source: https://docs.talview.com/candidates/system-diagnostics/what-are-the-recommended-bandwidth-and-latency
When it comes to a seamless internet experience, *bandwidth and latency* play vital roles. **Insufficient bandwidth** can slow down your connection, while **high latency** can lead to lag, especially during using real-time applications.
This article explores recommended bandwidth requirements for various online activities, the significance of latency, and tips to improve your internet performance.
## ✅Understanding Bandwidth and Latency
* **Bandwidth** refers to the maximum rate of data transfer across a given path in the network, usually measured in megabits per second (Mbps). It determines how much data can be transmitted in a certain timeframe.
* **Latency**, on the other hand, is the delay before a transfer of data begins following an instruction for its transfer. It is typically measured in milliseconds (ms). High latency means a delay in communication over the network, which can lead to interruptions in online activities.
## ☑️Recommended Bandwidth
When using Talview’s platform for video interviews, assessments, or any interactive features, it is essential to have an adequate internet connection. Here is the bandwidth recommendations based on typical use cases:
### **1. Video Interviews:**
* **Recommended Upload/Download Speed:** 2 Mbps
* **Optimal Experience:** 5 Mbps or higher
### **2. Live Assessments:**
* **Recommended Upload/Download Speed:** 2-3 Mbps
* **Optimal Experience:** 5 Mbps or higher
### **3. Pre-recorded Assessments:**
* **Recommended Upload Speed (for candidates):** 1 Mbps
* **Download Speed:** Varies based on content but generally 1 Mbps is sufficient for streaming.
### **4. Low-Latency Requirements:**
For activities that require real-time interaction, such as video conferencing or live coding assessments, reduced bandwidth requirements can lead to noticeable improvements in quality.
### **5. Minimum Requirements:**
* **Video Quality:** Standard quality.
* **Audio Quality:** Clear and uninterrupted.
### **6. Mobile Assessments:**
* For candidates using mobile devices, it’s recommended to have at least a **4G LTE** connection to ensure fluid performance during assessments.
## ☑️Recommended Latency
Latency, measured in *milliseconds (ms),* refers to the time taken for data to travel from the source to the destination. The lower the latency, the better the performance of real-time applications. Here are the latency recommendations for Talview's services:
### **1. Ideal Latency:**
* **Less than 100 ms:** This level of latency ensures a smooth experience during live video interactions and minimizes delays during assessments.
### **2. Acceptable Latency:**
* **100-200 ms:** While still functional, latency within this range may lead to minor disruptions in conversations and interactions.
> ***Caution:*** Above **200 ms -** High latency can significantly affect the overall experience, leading to delays in audio and video, causing frustration for users.
### **Additional Tips to Resolve Connectivity Issues**
To ensure a seamless experience while using Talview’s products, here are additional tips:
**1. Use Wired Connections:**
* Whenever possible, use an Ethernet connection for stability instead of relying on Wi-Fi. Wired connections are generally more reliable and offer lower latency.
**2. Test Your Connection:**
* Conduct a *speed test* before assessments to ensure your bandwidth and latency meet the recommended standards. Websites like [Speedtest.net](http://Speedtest.net) can provide a quick assessment.
**3. Limit Background Applications:**
* Close any unnecessary applications on your device that might consume bandwidth, such as video streaming services or large downloads, which can affect your upload/download speeds.
**4. Mobile Hotspot Backup:**
* Have a mobile hotspot ready as an alternative. It can serve as a backup connection in case your primary network fails unexpectedly.
# What to do if the Secondary camera fails to setup?
Source: https://docs.talview.com/candidates/system-diagnostics/what-to-do-if-the-secondary-camera-fails-to-setup
If your secondary camera stops working or fails to connect on your mobile device during an assessment or interview, it can interrupt your session or prevent you from proceeding. In this article, you’ll learn how to identify the failure, take immediate corrective actions, and safely restore the secondary camera connection.
## 🚨 How to identify a Secondary camera failure?
You may be experiencing a secondary camera failure if:
* The mobile screen freezes or shows no video
* The camera feed disappears after initially connecting
* You see repeated “Disconnected” or “Reconnecting” messages
* Your main device shows a warning about the secondary camera
* The mobile browser closes unexpectedly
## 🧪 Common Issues and How to Fix Them
| **Problem** | **What You Can Do** |
| :------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| QR code is not scanning | Clean your mobile camera lens and increase screen brightness on your computer. If scanning still fails, manually enter the code displayed on your main device. |
| Stuck on the “Connecting” screen | Ensure both your mobile device and computer are connected to the **same Wi-Fi network**. Restart your phone and retry if the issue persists. |
| Camera feed is not loading | Close other apps that may be using the camera, such as Zoom, Teams, or WhatsApp. Restart the mobile browser or app and try again. |
| Blank or black video screen | Confirm that camera permission is allowed for the mobile browser or app. Refresh the page and reinitiate the connection. |
| Secondary device disconnects during the test | Keep your phone connected to a charger and placed on a stable surface. Avoid switching networks or letting the screen turn off. |
### ⚙️ Basic Setup Checklist
Before starting your assessment:
* Connect both your computer and mobile phone to the **same Wi-Fi network**
* Scan the QR code shown on your main test screen using your mobile device
* Allow camera access when prompted on the mobile browser or app
* Keep your phone **still and the screen active** throughout the session
* Disable screen auto-lock if possible
* Plug your phone into a charger to avoid battery interruptions
### 🛑 What to Avoid
* Do not use **mobile data** on your phone while your computer is on Wi-Fi
* Do not minimize the browser or app on your mobile device
* Do not rotate, move, or reposition the phone after setup
* Avoid switching apps or locking the phone screen during the test
### Additional Tip: Best Phone Placement
* Place your phone on the **left or right side** of your desk on a stable surface
* Ensure your **face, hands, and workspace** are clearly visible
* Use a phone stand or stable support to maintain the correct angle
Proper setup and placement of the secondary camera help ensure a smooth, uninterrupted testing experience.
***
# When to use desktop over mobile?
Source: https://docs.talview.com/candidates/system-diagnostics/when-to-use-desktop-over-mobile
Choosing the right device is critical for a smooth and compliant assessment or interview experience. While mobile devices offer convenience, certain test types require the capabilities of a desktop or laptop to meet proctoring, performance, and compatibility requirements.
This article explains **when and why a desktop/laptop should be used instead of a mobile device**, based on the type of test you are taking.
## ✅ Device Recommendations by Test Type
| **Test Type** | **Recommended Device** | **Why This Device Works Best** |
| -------------------------------------- | ---------------------- | ------------------------------------------------------------------------------------------- |
| **Proctored Assessments** | Desktop/Laptop | Supports webcam, microphone, screen monitoring, and browser compatibility |
| **Live Interviews (One-way or Panel)** | Desktop/Laptop | Stable video/audio quality and access to screen sharing and large video panels |
| **Coding Simulations or Typing Tests** | Desktop/Laptop | Optimized interface, keyboard efficiency, and system resource compatibility |
| **MCQ-based Non-Proctored Tests** | Mobile or Desktop | Simple interface that works on both, but mobile use should still ensure strong connectivity |
## ⚠️ Common Issues When Using the Wrong Device
| **Device Mismatch** | **Possible Impact** |
| ---------------------------------- | ---------------------------------------------------- |
| Mobile used for proctored test | Camera/mic access failure or system disqualification |
| Mobile used for coding test | Interface lag, response delays, or unresponsive UI |
| Switching between devices mid-test | Test resets or session dropout |
| Using unsupported browsers | Proctoring features disabled or page not loading |
### 📱 Why not use a mobile?
While mobile devices offer convenience, they may lack the capabilities required for certain test types:
* Limited support for **screen proctoring** and **browser permissions**
* Smaller screen size affects visibility and focus
* Restricted performance during **long-form responses** or coding activities
* May experience **interrupted background calls or app notifications**
### 🧪 How to Choose the Right Device?
1. **Check your test notification**
* Look for mentions like “proctored test,” “live interview,” or “coding assessment.”
2. **Match your device to the recommended type (see the table above)**
3. **Run a system compatibility check**
> Look for a "**System Check**” link in your invitation to test your webcam, microphone, browser, and internet connection strength.
***
# Why built-in cameras work better than external ones?
Source: https://docs.talview.com/candidates/system-diagnostics/why-built-in-cameras-work-better-than-external-ones
If you're getting ready for an interview or a proctored assessment, you'll need a working camera. You can use either the camera that comes built into your laptop or an external webcam. But from our experience, **built-in cameras usually work better** and cause fewer issues.
This guide explains why built-in cameras work better, and what to do if you're using an external webcam.
## ✅ Why Built-in Cameras Are Better?
| **What Matters** | **Built-in Camera** | **External Camera** |
| ------------------------------ | ------------------------------------- | ----------------------------------------- |
| **Easy to detect** | Yes, system picks it up automatically | Sometimes needs manual setup |
| **Stable connection** | Fewer chances of disconnection | May stop working if USB is loose |
| **Less setup required** | Just open the browser and go | May need to choose camera from settings |
| **More secure for test rules** | Fixed in place | Can be moved around, may trigger warnings |
## ❌ Common Issues with External Cameras
| **Problem** | **Why It Happens** | **What You Can Try** |
| ------------------------- | ------------------------------------------------- | ------------------------------------------------- |
| Camera not found | Not plugged in properly or not allowed by browser | Reconnect the camera and restart your browser |
| Black screen | Permissions not given to use the camera | Go to browser settings and allow camera access |
| Video is blurry or slow | Low-quality camera or old drivers | Try using your built-in camera instead |
| Camera turns off mid-test | USB gets loose or power drops | Use a different port or switch to built-in camera |
## 🔍 How to Check Your Camera Before Starting
You can use this system check before your test or interview. It will check your camera.
To avoid any issues:
1. Make sure **only one camera** is connected.
2. If you have both a built-in and external camera, the system may ask you to choose one.
3. **Pick the built-in one** (it may show as “Integrated Camera” or “Laptop Camera”).
> If your camera isn’t working, don’t start the test yet - **try fixing it first.**
## 📌 When to Use an External Camera
You can use an external camera if:
* Your laptop camera is broken or blocked
* You need better video quality
* You're using a desktop that doesn’t have a built-in camera
Just make sure it’s connected properly and selected in your browser settings.
# Why can’t I hear my audio?
Source: https://docs.talview.com/candidates/system-diagnostics/why-cant-i-hear-my-audio
If you’re unable to hear instructions or audio prompts during your assessment, the issue is usually related to browser-level audio settings rather than your device volume.
Use the checklist below to quickly identify and resolve common causes.
## ✅Common Causes and Fixes
| What might be wrong | How to fix it |
| :--------------------------------------- | :----------------------------------------------------------------------------- |
| Browser tab is muted | Right-click the test tab in your browser and select **Unmute site** |
| Audio permission was blocked earlier | Close the tab, reopen the test link, and allow audio when prompted |
| Browser audio is not working | Play audio in another tab (for example, a video site) to confirm browser sound |
| Audio output is routed to another device | Disconnect Bluetooth headphones, HDMI monitors, or external speakers and retry |
## 🌐 Final Check: Can You Hear Now?
After unmuting:
* Reload your Talview assessment link
* Watch for instructions or voice-based system checks
* Make sure **no Bluetooth headphones or HDMI screens** are silently taking over the output
**Additional tips:**
* Reload the test page after unmuting the tab to ensure changes take effect.
* Restart the browser if audio still does not play after fixing settings.
* Avoid using wireless audio devices during the test, as they may redirect sound output.
* Ensure no other applications are actively controlling system audio.
***
***
***
# Why can’t I share a specific application window?
Source: https://docs.talview.com/candidates/system-diagnostics/why-cant-i-share-a-specific-application-window
If you are unable to share a single application window during a screen-sharing session, browser or system permissions in Talview may be limiting what can be captured.
This checklist helps you identify common causes and apply quick fixes before your session begins.
## ✅ Common Causes and Fixes
| What might be wrong | How to fix it |
| ----------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- |
| Application window not visible in share options | Ensure the application is already open and not minimized before starting screen share. |
| Entire screen shares instead of one window | Select the “Application Window” or “Window” tab in the screen share picker instead of “Entire Screen.” |
| Screen share permissions not granted | Check browser site settings and allow **Screen sharing, Camera, and Microphone**, then restart the browser. |
| macOS screen recording access blocked | Go to `System Settings → Privacy & Security → Screen Recording → Enable access for your browser → Restart the browser`. |
| Windows privacy settings restricting capture | Open `Settings → Privacy → Camera and Microphone → Ensure access `is enabled for your browser. |
| Unsupported or outdated browser | Update your browser and use Google Chrome, Microsoft Edge, or Firefox for best compatibility. |
### **Additional Tips:**
1. **Screen Share Options Not Visible:** Ensure that your screen-sharing application is updated and that you are logged in correctly. Check your internet connection, as poor connectivity can hinder functionality.
2. **Application Window Not Listed:** If the desired application isn’t appearing in the sharing options, make sure the application is open and active on your desktop. Restart the application if needed.
3. **Permissions Problems:** Depending on your operating system, you may need to enable permissions for your screen sharing application to capture the application window.
* For **Windows**, Go to `Settings > Privacy > Screen Recording` (for Windows 10/11, this option is often under Camera and Microphone settings).
* For **macOS**, go to `System Preferences > Security & Privacy > Privacy tab`, and ensure screen recording permissions are enabled for your application.
# Why does my camera conflict with video conferencing tools?
Source: https://docs.talview.com/candidates/system-diagnostics/why-does-my-camera-conflict-with-video-conferencing-tools
If you encounter errors such as **“camera already in use,” “camera unavailable,”** or see a **blank video feed** during your assessment, it usually means another application is accessing your camera. Video conferencing tools and background software can lock the camera, preventing your browser from using it for the assessment.
This article explains why these conflicts occur and how to resolve them effectively before or during your test.
## ✅ Common Causes and Fixes
| **What Might Be Wrong** | **How to Fix It** |
| :--------------------------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Video conferencing app is using the camera | Fully close all video apps such as Zoom, Microsoft Teams, Google Meet, Skype, FaceTime, Slack, Discord, or WebEx. Do not just minimize them. |
| Background process still running after closing the app | **Windows:** Open Task Manager (Ctrl + Shift + Esc) → Processes → end all related app processes. **Mac:** Open Activity Monitor → search for the app → quit all instances. Restart your browser afterward. |
| Another browser tab is using the camera | Check all open tabs for a camera indicator icon. Close any tab using the camera, or close the browser completely and reopen only the assessment tab. |
| Camera or photo software is open | Close built-in camera apps or photo/video tools (e.g., Camera app, Photo Booth, Photos, video editors). These can hold camera access even when idle. |
| Multiple browser windows or profiles open | Close all browser windows and profiles except the one being used for your assessment. Other profiles may still access the camera. |
| Browser did not release the camera from a previous session | Completely restart your browser. If the issue persists, restart your computer to reset camera resources. |
| Camera privacy settings blocking access | **Windows:** Settings → Privacy & Security → Camera → enable camera access and browser permissions. **Mac:** System Settings → Privacy & Security → Camera → allow your browser. |
### **Additional Tips**
* Close all camera-using applications **before** launching your assessment.
* Check Task Manager (Windows) or Activity Monitor (Mac) to confirm no background processes are using the camera.
* Restart your system 5–10 minutes before the test for a clean setup.
* Keep system monitoring tools accessible during the test for quick troubleshooting.
* If using a work-managed device, confirm with IT whether monitoring software may interfere.
* Disconnect and reconnect external webcams if used.
* Consider keeping a backup device available in case camera conflicts cannot be resolved quickly.
# Why does my session crash when the network drops?
Source: https://docs.talview.com/candidates/system-diagnostics/why-does-my-session-crash-when-the-network-drops
If your assessment or interview session suddenly freezes, ends, or logs you out, a network drop may be interrupting your connection. Even brief connectivity losses can disrupt live sessions, cause loss of progress, or trigger automatic logouts in proctored environments.
In this article explains how even brief connectivity losses can disrupt live sessions, cause loss of progress, or trigger automatic logouts in proctored environments.
## ✅ Common Causes and Fixes
| **What Might Be Happening** | **What You Can Do** |
| --------------------------------------------------- | --------------------------------------------------------------------------------------- |
| Weak or unstable Wi-Fi connection | Use a **wired (LAN) connection** for better stability, if possible |
| Mobile hotspot signal fluctuates | Switch to a **broadband network** |
| Router temporarily dropped signal | **Restart your modem/router**, wait 2 minutes, then reconnect |
| Internet used by multiple people or devices | Ask others to **pause heavy internet usage** (streaming, downloads) during your session |
| Power-saving or auto-sleep settings disrupt network | Turn off **battery saver** or **auto-sleep** modes on your device and router |
### ⚠️ Signs You're Experiencing Network Drops
[Run a Network Speed Test](https://speed.talview.com/) to ensure your connection is stable.
You may be facing intermittent disconnections if:
* Your session **freezes** and resumes or ends abruptly
* You’re **logged out without warning**
* The **“Connectivity” status in System Check keeps changing**
* You see **“Reconnecting…”** messages during a live interview
### 🛠️ How to Prevent Session Crashes?
To stay connected throughout your session, try the following:
* **Use a wired Ethernet connection** instead of Wi-Fi
* If on Wi-Fi, **sit close to the router** for the strongest signal
* **Disable background apps** and updates on your device
* **Turn off auto-sleep** on your computer and hotspot device
* **Keep your device plugged in and fully charged**
* **Avoid switching networks** mid-session (e.g., between Wi-Fi and mobile data)
### 🔁 If a Session Crashes...
If your session gets disconnected:
* Check your network connection and do a network speed test if needed.
* Try reconnecting immediately using the same link
* If prompted, **resume from where you left off**
* If unable to rejoin, take a screenshot of the error and your network speed test
Then, reach out to Talview Support for assistance.
## 📚 Related Articles
* [*Using Mobile Hotspot Without Interruption*](https://docs.talview.com/candidates/system-diagnostics/how-to-use-mobile-hotspot-without-interruption)
* [*Background Apps That Eat Bandwidth*](https://docs.talview.com/candidates/system-diagnostics/network-and-connectivity/why-do-background-applications-cause-bandwidth-and-latency-issues)
* [*Minimum Network Requirements for Talview*](https://docs.talview.com/candidates/system-diagnostics/what-are-the-recommended-bandwidth-and-latency)
* [*Troubleshooting Latency Warnings*](https://docs.talview.com/candidates/system-diagnostics/how-network-latency-affects-audio-and-video-quality)
***
# Why does using headphones improve test audio quality?
Source: https://docs.talview.com/candidates/system-diagnostics/why-does-using-headphones-improve-test-audio-quality
Using headphones during assessments or interviews helps improve audio clarity, reduce background noise, and prevent common sound-related disruptions.
This article explains how headphones enhance audio performance and what you can do to ensure the best possible setup before starting your session.
## ✅ Common causes and fixes
| What might be wrong | How to fix it |
| :------------------------------------------------ | :---------------------------------------------------------------------------------------- |
| Echo or feedback during audio playback | Use headphones so test audio is routed directly to your ears instead of external speakers |
| Background noise interfering with audio detection | Use headphones with a built-in microphone positioned close to your mouth |
| Difficulty hearing instructions or prompts | Wear headphones to receive clearer and more consistent audio output |
| Delays or interruptions in audio | Use wired headphones to avoid Bluetooth latency or connection drops |
| Microphone picking up unintended sounds | Disable external speakers and rely on headphone audio only |
## 📌 Best practices -
* Use **wired headphones,** if possible, to avoid Bluetooth lag.
* Ensure mic permissions are granted for your headphones.
* Avoid using **gaming headsets** with heavy audio processing.
**Additional tips:**
* Prefer **wired headphones** over Bluetooth devices to reduce lag and avoid pairing issues.
* Connect your headphones **before opening the test link** so the browser detects them correctly.
* Confirm that the correct microphone and audio output device are selected in your system settings.
* Avoid gaming headsets or devices with aggressive noise cancellation or sound enhancement features.
* [**Test audio**](https://video-diagnostics.talview.org/) before starting the assessment or interview.
# Why does VPN usage trigger high latency warnings?
Source: https://docs.talview.com/candidates/system-diagnostics/why-does-vpn-usage-trigger-high-latency-warnings
Using a VPN during an online test or interview can significantly affect network performance. If you see **“High Latency”** warnings, experience delayed audio or video, or notice a **“VPN detected”** message during system checks, it usually indicates that your connection is being rerouted or slowed down. This can interfere with real-time communication and may impact proctoring accuracy or session stability.
In this article, you’ll understand why VPN usage causes latency issues and how to fix them before your session.
## 🚨How does VPN impact latency?
A VPN encrypts internet traffic and routes it through external servers. While this improves privacy, it can introduce delays because:
* Data travels a longer path between your device and the platform servers
* Encryption and decryption add processing overhead
* VPN servers may be congested or geographically distant
* Some VPNs throttle speed on certain networks
These factors increase **ping (latency)** and can cause lag, audio delays, or video freezes during live sessions.
## ✅ Common Causes and Fixes
| **What Might Be Wrong** | **What You Can Do** |
| ----------------------------------------- | --------------------------------------------------------------------------------------------------- |
| VPN or proxy is enabled | Disable VPN or proxy settings from your device or browser. |
| High network latency (ping >150ms) | Restart your modem/router. Switch to a wired (LAN) connection if possible. |
| Using a distant VPN server | Disconnect from the VPN or choose a server closer to your actual location. |
| Network is overloaded (home or office) | Pause large downloads, streaming apps, and cloud sync services during your session. |
| You're on a school/office firewall | Contact your IT team to **whitelist Talview domains** and ensure no proxy restrictions are applied. |
| Using a mobile hotspot or metered network | Switch to a stable broadband connection for smoother performance. |
### ⚠️ Signs VPN-Related Latency Is Affecting Your Session
You may be impacted if:
* Audio responses are delayed or cut off
* Video freezes, skips, or appears out of sync
* The system check shows **High Latency** or **VPN Detected**
* Your session freezes or reconnects unexpectedly
### 🌐 Final Check: Test Your Latency
Before rejoining your session:
* Ensure **VPN/Proxy is turned off**
* Run a [Speed and Latency Test](https://www.speedtest.net/)
* Confirm:
* Ping \< 50 ms (ideal)
* Jitter \< 30 ms
* Stable upload and download speeds
If results don’t meet the recommended thresholds, switch networks or retry after making the fixes above.
## 📚 Related Articles
Still seeing **“High Latency”** or **“VPN Detected”** errors? Try these:
* [*Disable VPN/Proxy Instructions*](https://docs.talview.com/candidates/system-diagnostics/why-does-vpn-usage-trigger-high-latency-warnings#common-causes-and-fixes)
* [*Network Setup for Talview*](https://docs.talview.com/candidates/system-diagnostics/why-is-my-network-not-meeting-test-requirements#minimum-network-requirements)
* [*Check Browser & Device Compatibility*](https://docs.talview.com/candidates/system-diagnostics/supported-browsers-and-versions)
# Why enterprise or MDM restrictions block app installation?
Source: https://docs.talview.com/candidates/system-diagnostics/why-enterprise-or-mdm-restrictions-block-app-installation
Security settings on your work or school device can sometimes block the secure browser from installing or launching on Talview, which may delay the start of your exam.
This article will help you identify the most likely causes and walk you through the steps to resolve the issue before your session begins.
***
## ✅ Common Causes and Fixes
| **What Might Be Wrong** | **How to Fix It** |
| :-------------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **MDM or enterprise policy** is blocking the installation | Your device is managed by your organization, which restricts app installations. Try using a personal laptop instead, this is the quickest way to get unblocked. |
| **App store or software installs are locked** | Your device may not allow installations from external sources. Switch to a personal laptop if you have one available. |
| **You don't have admin rights** on the device | Without admin rights, you can't install new software. Use a personal laptop to avoid this restriction. |
| **Antivirus or firewall** is blocking the installer | Your security software may be flagging the installer. On a personal laptop, you can temporarily disable antivirus or whitelist the installer file. |
| **Custom security settings** are preventing the install | Your organization may have applied device-level restrictions. A personal laptop won't have these limitations. |
**Additional Tips:**
* Using a **personal laptop** is the fastest and most reliable way to get past device restrictions, try this first.
* If you don't have access to a personal laptop, contact your **IT support team** and share the app name and installer link so they can assist you.
* Make sure your IT team checks that the **firewall and antivirus** aren't blocking the installer.
* Check your test guidelines to confirm whether using a personal device is permitted.
# Why is a strong wi-fi signal required for live sessions?
Source: https://docs.talview.com/candidates/system-diagnostics/why-is-a-strong-wi-fi-signal-required-for-live-sessions
A strong and stable Wi-Fi signal is essential for live intreviews and assessments on the Talview platform. Weak Wi-Fi can lead to buffering, audio delays, frozen video, or unexpected disconnections, which may interrupt your session or affect monitoring and evaluation.
In this article, you’ll learn why Wi-Fi strength matters, how weak signals impact live sessions, and what you can do to improve your connection before joining.
## ✅ Common Causes and Fixes
| **What Might Be Wrong** | **What You Can Do** |
| ------------------------------ | ------------------------------------------------------------------------------------------------- |
| You're far from the router | Move closer to your router or into the same room. Walls and floors can weaken the signal. |
| Router is obstructed or buried | Place the router in an open, central location—avoid cabinets or corners. |
| Too many devices connected | Disconnect unused devices or ask others to pause streaming/gaming temporarily. |
| Using the 2.4 GHz band only | Switch to the 5 GHz band for faster, more stable connections (if your router supports it). |
| Router or device is outdated | Restart your router. If the issue persists, consider a hardware upgrade. |
| Interference from appliances | Move away from microwaves, cordless phones, and Bluetooth devices which may interfere with Wi-Fi. |
### ⚠️ How Weak Wi-Fi Affects Live Sessions
You may experience Wi-Fi-related issues if:
* Video freezes or appears blurry
* Audio cuts out or becomes distorted
* System checks show fluctuating connectivity status
* Your session disconnects or reconnects unexpectedly
These issues can disrupt live interviews, trigger proctoring alerts, or cause session interruptions.
### 🌐 Final Check: Test Your Wi-Fi Strength
Before starting your session, make sure your signal is strong and stable.
👉 [Run a Wi-Fi Signal Strength Test](https://speed.talview.com/)
Look for:
* **Signal Strength: Excellent or Good**
* **Download Speed > 5 Mbps**
* **Upload Speed > 2 Mbps**
* **Ping \< 100ms**
If you're on mobile or a laptop, walk around and test in different areas of your home to find the strongest spot.
## 📚 Related Articles
Still getting signal drops or slowness? Try these:
* [***Using Mobile Hotspot Without Interruption***](https://docs.talview.com/candidates/system-diagnostics/how-to-use-mobile-hotspot-without-interruption)
* [***Recommended Bandwidth and Latency***](https://docs.talview.com/candidates/system-diagnostics/what-are-the-recommended-bandwidth-and-latency)
* [*Browser & Device Compatibility Guide*](https://docs.talview.com/candidates/interviews/diagnostics/system-requirements-for-a-smooth-interview-experience)
# Why is my camera not being detected or found?
Source: https://docs.talview.com/candidates/system-diagnostics/why-is-my-camera-not-being-detected
If your camera is not being detected, recognized, or showing "no camera found" errors during your assessment, connection issues, permission blocks, or driver problems may be preventing your system from recognizing the camera. Without camera access, you won't be able to complete identity verification or proctored test requirements.
This guide helps you troubleshoot camera detection issues and ensure your camera is recognized by your system and browser.
## ✅ Common causes and fixes
| What might be wrong | How to fix it |
| :------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Another application is using the camera | Close all applications that might be accessing your camera **Windows:** `Open Task Manager (Ctrl+Shift+Esc) > Processes tab > find and end video conferencing apps`. **Mac:** `Open Activity Monitor > search for these apps > click 'X' to quit. Restart your browser after closing conflicting apps`. |
| Browser doesn't have camera permissions | Grant camera access to your browser. **Chrome/Edge:** `Click lock icon in address bar > Site settings > Camera > Allow`. **Firefox:** `Click lock icon > More Information > Permissions > Camera > Allow`. **Safari:** `Safari > Settings for This Website > Camera > Allow. Refresh the page completely after granting permissions`. |
| Browser page cached old permission settings | Perform a hard reload to refresh permission settings. **Windows:** `Press Ctrl+Shift+R or Shift+F5`. **Mac:** `Press Cmd+Shift+R`. This forces the browser to reload without using cached data and re-check camera permissions. If still not detected, close all browser tabs and restart the browser completely. |
| Camera drivers are outdated or corrupted | **Windows:** `Open Device Manager (search in Start menu) > Expand "Cameras" or "Imaging devices" > Right-click your camera > Update driver > Search automatically for drivers`. If that doesn't work, try Uninstall device, then restart your computer to reinstall. **Mac:** Camera drivers update through system updates - go to System Settings > Software Update and install any available updates. |
| Operating system hasn't granted camera access to browser | **Windows:** `Go to Settings > Privacy & security > Camera > Ensure "Camera access" is ON and "Let desktop apps access your camera" is enabled > Verify your browser is in the allowed list`. **Mac:** `Go to System Settings > Privacy & Security > Camera > Check the box next to your browser (Chrome, Safari, Firefox, Edge) to allow camera access`. |
| Camera is disabled in Device Manager (Windows) | **Windows:** `Open Device Manager > Expand "Cameras" or "Imaging devices" > If your camera shows a down arrow or is grayed out, right-click it > Enable device`. If it shows a yellow triangle with exclamation mark, r`ight-click > Update driver or Uninstall device`, then restart to reinstall. |
| Privacy shutter or cover blocking camera | Check if your laptop has a physical privacy shutter slider near the webcam, slide it to the open position. Remove any tape, stickers, or stick-on privacy covers from your camera lens. |
| USB port not providing enough power | Some external webcams need more power than certain USB ports provide. Try connecting to a different USB port, avoiding USB hubs, plug directly into your computer. |
| Multiple cameras causing system confusion | If you have both built-in and external cameras, your system may be confused about which to use. In your browser's site settings or system camera settings, explicitly select which camera should be the default. |
| Antivirus or security software blocking camera | Check if your antivirus is blocking camera access. Add your browser to the antivirus exceptions/allowed list. **Windows Defender:** `Windows Security > Virus & threat protection > Manage settings > Add exclusions > add your browser`. For third-party antivirus, check documentation for allowing camera access. |
**Additional tips:**
* Restart your device before your assessment after making any driver or permission changes to ensure all settings take effect
* [Test your camera](https://video-diagnostics.talview.org/) using your system's built-in camera app (Windows Camera or Mac Photo Booth) before starting your assessment to confirm it's being detected
* If using an external USB webcam, ensure it's a modern model (2018 or newer) with up-to-date drivers, very old webcams may have compatibility issues with modern systems
* Keep your USB webcam cable as short as possible and avoid extension cables which can cause connection instability
# Why is my microphone not detected in Secure Browser?
Source: https://docs.talview.com/candidates/system-diagnostics/why-is-my-microphone-not-detected-in-secure-browser
If you're using a **Secure or Locked-down Browser** (often required for proctored tests) and your microphone isn’t being detected, it’s usually due to restricted permissions or system-level blocking. This can prevent the system from capturing your audio, which may lead to interruptions, inability to communicate, or even disqualification from the test.
In this article, you’ll learn the common reasons this happens and how to resolve it.
## ✅ Common Causes and Fixes
| **What Might Be Wrong** | **What You Can Do** |
| :--------------------------------------------- | :------------------------------------------------------------------------------- |
| Secure browser blocks device access | Restart the secure browser and ensure all permissions are granted when prompted. |
| Mic access not allowed in system settings | Go to system settings and enable mic access for all apps. |
| Another app is locking the mic | Close other apps like Zoom, Teams, or Skype that might be using the mic. |
| External mic not connected properly | Reconnect the USB or audio jack. Try a different port if needed. |
| Mic disabled in BIOS or device manager | Check system BIOS (advanced) or use Device Manager to enable it. |
| Antivirus or security software is blocking mic | Temporarily allow mic access or ask IT to whitelist the secure browser. |
## 🔧 Final Check: Allow Microphone at OS Level
Make sure the operating system allows microphone access for all applications:
### **Windows**:
* Go to: `Settings > Privacy & Security > Microphone`
* Enable microphone access for **all apps** (secure browsers may not appear by name)
### **macOS**:
* Go to: `System Settings > Privacy & Security > Microphone`
* Ensure **microphone access is turned ON** system-wide
### **Secure Browsers Tip**:
* If you denied mic permission when prompted at launch, **exit and relaunch** the secure browser—it won’t ask again unless restarted.
* [Run a Mic Test](https://video-diagnostics.talview.org/) before launching the secure browser to verify it’s functioning.
* Use the **internal mic** if the external one fails
* Reboot your device before launching the secure browser again
# Why is my network not meeting test requirements?
Source: https://docs.talview.com/candidates/system-diagnostics/why-is-my-network-not-meeting-test-requirements
A reliable network is critical for a smooth experience on the platform, whether you're attending a live interview, taking a proctored assessment, or conducting an evaluator session. Poor connectivity can lead to video lag, audio distortion, or session disconnections.
This article outlines the network requirements needed for an uninterrupted experience.
## ✅ Minimum Network Requirements
| **Network Parameter** | **Recommended Value** | **Minimum Required** |
| --------------------- | --------------------- | -------------------- |
| **Download Speed** | 10 Mbps or higher | 5 Mbps |
| **Upload Speed** | 5 Mbps or higher | 2 Mbps |
| **Latency (Ping)** | \< 50 ms | Lesser than 100 ms |
| **Jitter** | \< 30 ms | \< 50 ms |
| **Packet Loss** | 0% | Maximum 2% tolerated |
Anything below the minimum threshold may cause:
* Video/audio lag
* Delays in system checks
* Session timeouts or dropped connections
## 📶 How to Check Your Network Speed
👉 [Run a Speed Test](https://speed.talview.com/)
After the test, review your:
* Download and upload speed
* Latency (ping)
* Jitter and packet loss, if available
**Tip:** Always test your connection at the exact location and on the same device you'll use for the session.
## 🛠️ If Your Network Doesn’t Meet the Minimum:
| **Issue** | **Quick Fixes** |
| -------------------------- | ---------------------------------------------------------------------- |
| Slow speed | Switch to a wired (LAN) connection, or restart your router |
| High latency | Pause background apps or connect to a less congested network |
| High jitter or packet loss | Avoid using mobile data or public Wi-Fi, switch to a broadband network |
| Upload issues | Ensure no cloud backups or sync tools are running in the background |
# Why is my Secondary camera showing the wrong angle?
Source: https://docs.talview.com/candidates/system-diagnostics/why-is-my-secondary-camera-showing-wrong-angle
A secondary camera ensures a complete view of your testing environment. If it shows the wrong angle, it may disrupt your test. This article explains how to troubleshoot and fix this issue.
## ✅ Common Causes and Fixes
| **What Might Be Wrong** | **What You Can Do** |
| ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Misalignment of the Camera** | Reposition the camera to face your test area diagonally. Ensure it covers the your desk and seat sufficiently. Check the height and angle, tilting it downwards as needed. Ensure your phone is placed in landscape mode. |
| **Movement During Setup** | Make sure your camera is steady. Secure the camera in place if using a tripod or mobile stand. Ensure the base is steady to avoid camera from shaking or moving |
| **Obstructions in the View** | Clear the area of any items blocking the camera view. Ensure there is a clear line of sight to capture the test area adequately. |
| **Connectivity Issues** | Verify that both devices are connected to a stable internet connection. Run a speed test and resolve any network unstable issues. Reconnect devices if necessary. |
### Final Checks
* After making adjustments, conduct a final test to ensure that the camera angle is correct and provides the coverage you need.
* Confirm that the camera feed is stable and uninterrupted, with a clear view of your test environment.
# Why is my speech not being detected or recognized?
Source: https://docs.talview.com/candidates/system-diagnostics/why-is-my-speech-not-being-detected-or-recognized
If your microphone is working and picking up sound, but your speech isn't being detected or recognized during your assessment setup, the system may not be able to distinguish your voice from background noise, or speech detection settings may need adjustment.
This guide helps you troubleshoot speech recognition issues when your mic audio levels are fine but words aren't being recognized.
## ✅ Common causes and fixes
| What might be wrong | How to fix it |
| :---------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Speaking too softly or inconsistently | Speak at a normal conversation volume (60-70% of your maximum volume) directly toward the microphone. Maintain consistent volume—don't trail off at the end of sentences. Position yourself 6-12 inches from the mic for built-in laptop mics, or 4-8 inches for external microphones or headsets. |
| Too far from microphone | Move closer to your microphone, distance significantly affects speech detection even if overall audio levels are adequate. For built-in laptop mics, sit directly in front of your device at a normal viewing distance. For external mics or headsets, ensure the mic is positioned near your mouth, not off to the side or below your chin. |
| Background noise overpowering your voice | Move to a completely quiet room with no background noise: turn off fans, AC, TVs, music, and ask others to be silent. The system needs your voice to be significantly louder than ambient noise. |
| Incorrect microphone input device selected | **Windows:** `Right-click speaker icon in taskbar > Sound settings > Input > Select your microphone from the dropdown` (ensure it shows green bars when you speak). **Mac:** `System Settings > Sound > Input tab > Select correct microphone > verify Input level meter responds to your voice`. Make sure you're selecting the mic you're actually using, not a disabled or disconnected device. |
| Browser doesn't have microphone permissions | Grant microphone access when prompted. **Chrome/Edge:** `Click lock icon in address bar > Site settings > Microphone > Allow`. **Firefox:** `Click lock icon > Permissions > Microphone > Allow.` **Safari:** `Safari > Settings for This Website > Microphone > Allow`. Refresh the page after granting permissions and try speech detection again. |
| Microphone volume or sensitivity too low | Increase your mic input volume to 75-90%. **Windows:** Settings > System > Sound > Input > Device properties > Volume slider to 75-90%. **Mac:** System Settings > Sound > Input > Input volume slider to 75-90%. Low sensitivity prevents the system from detecting speech even if audio is present. Test the meter, it should show strong response when speaking normally. |
| Operating system speech services not responding | Restart your browser first, then restart your device completely to reset all speech detection services. **Windows:** Speech recognition services can hang—restarting clears them. **Mac:** Ensure Dictation is enabled in `System Settings > Keyboard > Dictation` (even if not using it, the underlying services support speech detection). |
| Accent, pronunciation, or speech pattern issues | Speak slowly and clearly, enunciating each word. Speech detection systems are trained on standard pronunciation, heavy accents or fast speech can cause issues. Pause briefly between words. If repeatedly failing, try speaking slightly more formally and deliberately than normal conversation. The system improves recognition with clear articulation. |
| Network latency affecting real-time detection | Ensure you have a stable internet connection. Speech detection often processes in real-time or sends audio to servers, poor connection causes delays or failures. If on Wi-Fi, move closer to your router. Check that no other applications are consuming bandwidth (streaming, downloads, video calls). |
| Speech detection timing out too quickly | Some systems expect responses within a certain timeframe. When prompted to speak, respond immediately without long pauses. If the detection times out, try again promptly. Don't wait more than 1-2 seconds after the prompt to start speaking. Speak for 2-3 seconds minimum so there's enough audio to analyze. |
**Additional tips:**
* [**Test your speech**](https://video-diagnostics.talview.org/) detection before your assessment using the system check or practice run to identify issues with time to resolve them
* Use a headset with a built-in microphone rather than laptop built-in mics, headset mics are closer to your mouth and pick up speech more clearly with less background noise
* Speak in complete, clear sentences during detection tests, avoid single words or very short phrases which may not provide enough audio data for recognition
* If speech detection repeatedly fails, close all other applications that might be using your microphone (Zoom, Teams, Skype) and restart your browser
* Ensure your testing environment is genuinely quiet, background noise you've tuned out (refrigerator hum, computer fan, air conditioning) can still interfere with detection
# Why is my USB microphone not working?
Source: https://docs.talview.com/candidates/system-diagnostics/why-is-my-usb-microphone-not-working
If your USB microphone isn’t being detected or isn’t capturing audio during your test or interview, it could be due to connection issues, permissions, or system settings. This can lead to missing audio input, which may affect your ability to communicate clearly, result in incomplete recordings, or even lead to your test/interview session being flagged or disqualified.
In this article, you’ll learn the common reasons this happens and how to resolve it.
## ✅ Common Causes and Fixes
| **What Might Be Wrong** | **What You Can Do** |
| :----------------------------------- | :--------------------------------------------------------------------------------------------------------- |
| USB mic not recognized by the system | Unplug and reconnect the mic. Try a different **USB port** (avoid *USB hubs* if possible). |
| Wrong mic selected as input | Go to your **system** or **browser settings** and choose your **USB mic** as the **default input device**. |
| Mic is muted | Check for a **mute button** on the mic or cable, and unmute it. |
| Permissions not granted | Allow microphone access in your **browser** and **operating system** settings. |
| Outdated or missing drivers | **Restart your system**. If it still doesn’t work, update *audio* or *USB drivers*. |
| USB port is faulty | Try plugging the mic into another **USB port** or **device** to test. |
| Background apps using the mic | Close other apps like **Zoom**, **Skype**, or **Teams** that may be locking mic access. |
## 🛠 Final Check: Confirm Mic is Detected
1. Check if your mic is listed and selected as the input device:
* **Windows**:
`Settings > System > Sound > Input > Choose your input device`
* **Mac**:
`System Settings > Sound > Input > Select USB Microphone`
2. [Run a Mic Test ](https://video-diagnostics.talview.org/) to confirm it's working well.
### Additional Tips
Still not working? Try these:
* Restart your device
* Test the mic on another device
* Try a different USB cable if the mic is detachable
# Why is packet loss affecting my video or audio?
Source: https://docs.talview.com/candidates/system-diagnostics/why-is-packet-loss-affecting-my-video-or-audio
Packet loss happens when data packets traveling between your device and Talview servers don’t reach their destination. Even small packet loss can cause **video freezes, audio cutouts, or lag** during your assessments or interviews. In this article, we’ll cover common causes and steps to fix packet loss for a smooth session.
## ✅ Common Causes and Fixes
| **What Might Be Wrong** | **What You Can Do** |
| --------------------------------------- | --------------------------------------------------------------------------------- |
| Weak or unstable internet | Switch to a wired (LAN) connection. Restart your modem/router. |
| Wi-Fi interference or distance | Move closer to your router or switch to a more reliable network. |
| Too many devices on your network | Limit the number of users or pause heavy downloads/streams during your session. |
| Background applications using bandwidth | Close apps like Google Drive sync, Zoom, streaming platforms, or large downloads. |
| Outdated network drivers | Update your device’s Wi-Fi/network adapter drivers. |
| ISP-level issues | Contact your Internet Service Provider with speed test and packet loss data. |
### ⚠️ How to spot Packet loss?
You may be experiencing packet loss if:
* Video freezes or stutters during your session
* Audio cuts in and out or lags behind
* System check shows low bandwidth or intermittent connectivity
### 🌐 Final Check: Test for Packet Loss
* Before rejoining your test or interview: [*Run a Speed and Packet Loss Test*](https://speed.talview.com/)
* Check for **latency**, **jitter**, and **packet loss percentage**.
* Even small losses (2–5%)can impat video or audio
## 📚 Related Articles
Still experiencing disruptions? Try these:
* [*Recommended Network Settings for Talview*](https://docs.talview.com/candidates/system-diagnostics/why-is-my-network-not-meeting-test-requirements#minimum-network-requirements)
* [*Browser & Device Compatibility Guide*](https://docs.talview.com/candidates/system-diagnostics/supported-browsers-and-versions)
# Why is Screen share not available on work devices?
Source: https://docs.talview.com/candidates/system-diagnostics/why-is-screen-share-not-available-on-work-devices
If you are attempting to take an assessment or an interview on a company issued or IT-managed device, screen sharing may be unavailable due to administrator level security restrictions. Many organizations disable screen capture, recording, or sharing features to protect sensitive data. These restrictions can prevent the platform from verifying your activity, which may result in warnings, delays, or an inability to continue the session.
Understanding why this happens and choosing the right setup in advance can help you avoid last-minute disruptions.
## ✅ Use the Right Device
| **Restricted devices** | **Recommended alternatives** |
| :------------------------------------------------------- | :---------------------------------------------------------- |
| Corporate or office-issued laptops with admin locks | Personal laptop or desktop with full system access |
| Devices managed by IT policies or MDM tools | Devices where you can modify browser and system permissions |
| Systems with endpoint protection blocking screen capture | Devices with screen sharing and recording enabled |
## ✅ Setup Guidelines
Before starting your assessment or interview, confirm the following:
* Use a supported browser with full screen-sharing capabilities: **Google Chrome, Microsoft Edge, or Mozilla Firefox**
* Avoid **incognito/private browsing mode**, as it can block required permissions
* Disable or remove **browser extensions** that interfere with permissions (privacy blockers, security tools, screen recorders)
### 🔧System Permissions Check
* **On macOS:**\
Go to `System Settings → Privacy & Security → Screen Recording`, and ensure your browser is enabled
* **On Windows:**\
Open `Settings → Privacy`, and verify that screen capture and screen sharing are allowed for apps and browsers
### Additional Troubleshooting
Still facing issues? Try following the steps in these articles:
* [Turn screen sharing On in Mac](https://support.apple.com/en-in/guide/mac-help/mh11848/mac)
* [How to share screen in Windows](https://answers.microsoft.com/en-us/surface/forum/all/screen-sharing-between-windows-11-and-windows-10/8761fd40-2fb2-429e-9def-4374229aa3fa)
# Why is there no sound from my speakers?
Source: https://docs.talview.com/candidates/system-diagnostics/why-is-there-no-sound-from-my-speakers
If you are not hearing any sound from your speakers, it can disrupt system checks, instructions, or audio prompts during a test or interview. In this article, we walk through the most common causes of speaker issues and the steps you can take to identify and fix them quickly.
## ✅Common Causes and Fixes
| What might be wrong | What you can do |
| :-------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Speakers are muted or Volume is Low | a. **Check Speaker Volume:** Ensure your speaker’s physical volume knob or digital volume control is turned up. b. **Unmute Speakers:** Look for a mute button on your speaker or in your operating system’s sound settings. Click it to unmute. c. **Check Application volume:** Some applications have their own sound controls. Ensure these aren’t muted or set too low. |
| Incorrect Playback Device selected | **Verify Default Playback Device:** Right click the speaker icon in your system tray. Select “Sound settings” (Windows) or “System Preferences> Sound” (macOS) Under “Playback” ensure your intended speakers are selected as the default device |
| Loose or Incorrect Cable Connections | Ensure all speaker cables are securely plugged into the correct ports on your computer and speakers themselves If you have multiple audio output ports (e.g., front and back on desktop), try plugging your speakers into a different one. |
| Speaker Hardware Issues | a. Connect your speakers another device (e.g., phone, tablet) to see if they produce sound. This helps determine if speakers themselves are faulty. b. Ensure your speakers are powered on and receiving power. For USB speakers, ensure the USB cable is fully inserted. |
| System Sound Settings Issues (Advanced) | a. **Run Audio Troubleshooter:** (Windows) Search for "Troubleshoot settings" in the Start menu, then select "Playing Audio" and run the troubleshooter. b. **Disable Audio Enhancements**: Some audio enhancements can cause issues. In Sound settings, under the "Enhancements" tab (if available), try disabling them. |
| Disconnect Other Audio Devices | If you have headphones or other audio devices connected, disconnect them and see if the speakers start working. They might be overriding the speaker output. |
| Test with External Speakers/Headphones | If you have a different set of speakers or headphones, try connecting them to your computer. If they work, it indicates an issue with your primary speakers. |
## Additional Tip
1. Before starting your assessment or interview, run the [**Video Diagnostic Test**](https://video-diagnostics.talview.org/) and carefully review the audio section.
2. Pay close attention to the audio section and address any warnings.
3. Taking a few minutes to confirm your speaker setup in advance can help ensure you hear all instructions clearly and have a smooth testing experience.
# Why is TSB not launching in Mac?
Source: https://docs.talview.com/candidates/system-diagnostics/why-is-tsb-not-launching-in-mac
If Talview Secure Browser (TSB) doesn’t launch on your Mac, macOS security may be blocking it, preventing you from proceeding with the test. This is common when installing apps from outside the App Store.
## ✅ Common Causes and Fixes
| **What Might Be Wrong** | **What You Can Do** |
| :------------------------------------------ | :------------------------------------------------------------------------------------------------------------- |
| TSB wasn’t installed correctly | Delete the app, then [download the latest version](https://pages.talview.com/securebrowser/) and reinstall it. |
| You opened the file directly from Downloads | Move TSB to your **Applications** folder and launch it from there. |
| Mac doesn't show any warning at all | Open `System Settings → Security → Allow Apps from Identified Developers.` |
| Background restrictions or slow startup | Restart your Mac, close all other apps, then try launching TSB again. |
### Additional Tips
Still stuck?
* Open `Finder → Applications → Double-click TSB` to launch
* Make sure you installed **only the Mac version**
* Review [Mac-specific TSB guide](https://talview.freshdesk.com/support/solutions/articles/11000129091-secure-browser-troubleshooting-guide) for permissions
## 🌐 Final Check: Confirm It’s Working
After fixing permissions:
* Go to the **Applications folder** and open TSB
* Wait 10–15 seconds for it to launch
* Approve any macOS permission or firewall prompt
# Why is TSB not launching in Windows?
Source: https://docs.talview.com/candidates/system-diagnostics/why-is-tsb-not-launching-in-windows
If clicking on the Talview Secure Browser (TSB) doesn’t open anything on Windows, it may be due to installation issues, blocked permissions, or background apps. This can prevent you from starting your test.
## ✅ Common Causes and Fixes
| **What Might Be Wrong** | **What You Can Do** |
| :------------------------------------ | :----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| TSB didn’t install correctly | Uninstall TSB completely, then [download and reinstall the latest version](https://www.talview.com/download-center). |
| App is blocked by antivirus | Open your antivirus and [**add TSB as a trusted app**](https://talview.freshdesk.com/support/solutions/articles/11000129091-secure-browser-troubleshooting-guide). |
| You don’t have permission to run apps | Right-click the `TSB icon → Run as Administrator.` |
| Background apps are interfering | Close apps like screen recorders, VPNs, remote desktops, or pop-up blockers. |
| System is still *booting* or lagging | Restart your computer and wait 1–2 minutes before trying again. |
### Additional Tips:
* Try launching TSB from the **Desktop icon** or **Start Menu**
* Make sure the **installation file** was **actually run** after downloading
* Confirm your antivirus/firewall is not silently blocking the app
## 🌐 Final Check: Confirm It’s Working
Before reattempting the test:
* Right-click the TSB icon and choose **Run as Administrator**
* Wait up to 10–15 seconds on slower systems
* Allow any pop-ups or permission requests
# Why isn't screen sharing working or starting?
Source: https://docs.talview.com/candidates/system-diagnostics/why-isnt-screen-sharing-working-or-starting
If screen sharing isn't working, won't start, or shows permission errors during your assessment, browser extensions, privacy settings, or permission blocks may be preventing screen capture. Screen sharing is required for proctoring, and failures can prevent you from starting or continuing your test.
This guide helps you troubleshoot screen sharing issues and ensure proper functionality.
## ✅ Common Causes and Fixes
| What might be wrong | How to fix it |
| :---------------------------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Browser extensions blocking screen sharing | Disable browser extensions that block tracking or modify privacy settings. Common culprits: uBlock Origin, AdBlock, Ghostery, Privacy Badger, DuckDuckGo Privacy Essentials, NoScript. **Chrome/Edge:** Menu > Extensions > toggle off all extensions. **Firefox:** Menu > Add-ons > Extensions > disable all. **Safari:** Safari > Settings > Extensions > uncheck all. Refresh the page after disabling. |
| Site doesn't have screen sharing permissions | Grant screen sharing permissions to the assessment site. **Chrome/Edge:** Click lock icon in address bar > Site settings > Screen share or Display capture > Allow. **Firefox:** Click lock icon > More information > Permissions > Display capture > Allow. **Safari:** Safari > Settings for This Website > Screen Recording > Allow. Refresh after granting permissions. |
| Operating system hasn't granted screen recording permission | **Mac:** `System Settings > Privacy & Security > Screen Recording > check the box` next to your browser (Chrome, Safari, Firefox, Edge) to allow screen recording. Your browser must quit and restart after granting this permission. **Windows:** Screen capture permissions are typically browser-level, ensure browser has necessary access in Privacy settings. |
| Multiple browser tabs or windows causing conflicts | Close all other tabs or browser windows that might be attempting screen sharing. Only keep your assessment tab open. Close video conferencing tools (Zoom, Teams, Meet) or remote desktop software (TeamViewer, AnyDesk) that can conflict with screen sharing. |
| Using wrong browser for screen sharing | Use Google Chrome (recommended), Microsoft Edge, or Firefox for best screen sharing compatibility. Avoid Safari on older macOS versions, Opera, Brave, or other Chromium-based browsers with heavy privacy modifications that may block screen sharing. |
| Corporate or school network blocking screen sharing | Corporate firewalls or network policies may block screen sharing protocols. Try switching to a personal network (home Wi-Fi, mobile hotspot) if possible. Contact your IT department if you must use the corporate network, they may need to whitelist screen sharing for assessment sites. |
| Screen sharing dialog doesn't appear | The screen sharing permission dialog should pop up when you start sharing. If it doesn't appear, check that pop-up blockers aren't enabled. **Chrome/Edge:** Address bar will show a blocked pop-up icon, click it and allow pop-ups for the site. Your browser may need to be in focus (active window) for the dialog to appear. |
### 🧪 Final Check: Test Your Screen Sharing Setup
Before your session, confirm that your device allows screen sharing.
👉 [Run a Screen Share Test](https://video-diagnostics.talview.org/) to ensure WebRTC is functioning properly.
You should be able to see a *screen preview* and select the window or tab to share.
### **Additional Troubleshooting**
Still facing issues? Try these:
* Restart your browser and rejoin the session
* Try screen sharing in **incognito/private mode** to bypass extensions
* Use a different supported browser or device
# Why jailbroken or rooted devices are not supported?
Source: https://docs.talview.com/candidates/system-diagnostics/why-jailbroken-or-rooted-devices-are-not-supported
If your device is **jailbroken (iOS)** or **rooted (Android)**, you will not be able to start or continue a Talview interview or proctored assessment. These devices fail system checks because they bypass essential security controls required to maintain exam integrity and fairness.
In this article, we explain why jailbroken or rooted devices are blocked, how this impacts your session, and what you can do to proceed.
## ✅ Common causes and fixes
| **What Might Be Wrong** | **What You Can Do** |
| :---------------------------------------------------- | :--------------------------------------------------------------------------------------- |
| Your device is jailbroken or rooted | Use a device with a **secure, unmodified operating system** |
| You’re unsure whether your device is modified | Contact your **device manufacturer or service provider** to confirm |
| Device was altered using unofficial tools or software | **Restore the device to factory settings** (if possible) or use another supported device |
## 🛠 What to do before your assessment or interview?
* Switch to a **non-rooted Android** or **non-jailbroken iOS** device
* Avoid using devices that were previously modified, even if the changes seem minor
* Complete the **system check in advance** to confirm device compatibility
* If you cannot access a compliant device, **contact your test coordinator** for guidance
Once a device is detected as jailbroken or rooted, the restriction **cannot be bypassed** during the session. Using a compliant device is the only way to proceed.
# Why should I switch to a stable network before my session?
Source: https://docs.talview.com/candidates/system-diagnostics/why-should-i-switch-to-a-stable-network-before-my-session
If your internet connection is unstable, you may experience video lag, audio dropouts, or session interruptions. This checklist helps you identify unreliable network conditions and switch to a more stable connection before your test or interview begins.
## ✅ Common Causes and Fixes
| **What Might Be Wrong** | **What You Can Do** |
| ------------------------------------------------ | --------------------------------------------------------------------------------------- |
| Using public Wi-Fi or mobile data | Switch to a private, stable home or office broadband connection. Avoid mobile hotspots. |
| Network has inconsistent speed | Restart your router/modem or connect to a stronger network. Use LAN if possible. |
| Others are using bandwidth heavily | Ask others to pause streaming, gaming, or large downloads during your session. |
| You're on a metered or capped network | Move to an uncapped network to avoid throttling or cutoffs mid-session. |
| Using school or office network with restrictions | Contact IT to whitelist Talview domains and ensure open access. |
| Weak signal due to distance | Move closer to your router or use a wired connection for improved reliability. |
**Additional tips:**
* Avoid VPNs or proxy networks during your session.
* Close unused browser tabs and background applications.
* Restart your system after switching networks to ensure changes apply.
* Always switch networks at least 15–30 minutes before your session starts.
## 🌐 Final Check: Test Your Network
[Run a Speed Test](https://speed.talview.com/) before your test or interview, ensure you're on a **stable and fast connection**.
Make sure:
* **Download speed > 5 Mbps**
* **Upload speed > 2 Mbps**
* **Latency \< 100ms**
* **No packet loss or jitter**
> **Note**: Switch networks if your results fall below the recommended thresholds.
## 📚 Related Articles
Still unsure about your connection? Try these:
* [*Recommended Network Settings for Talview*](https://docs.talview.com/candidates/system-diagnostics/what-are-the-recommended-bandwidth-and-latency)
* [**How to use mobile hotspot without interruption?**](https://docs.talview.com/candidates/system-diagnostics/how-to-use-mobile-hotspot-without-interruption)
* [*Browser & Device Compatibility Checklist*](https://docs.talview.com/candidates/interviews/diagnostics/system-requirements-for-a-smooth-interview-experience)
# Why using Incognito mode fails?
Source: https://docs.talview.com/candidates/system-diagnostics/why-using-incognito-mode-fails
Using Incognito or Private Browsing mode can prevent your assessment or interview from running correctly. Incognito mode restricts how browsers store data and handle permissions, which interferes with essential test and proctoring features.
## ✅ Common Problems in Incognito Mode
| What Goes Wrong | Why It Happens |
| :-------------------------------------- | :----------------------------------------------------- |
| Camera or microphone access fails | Permissions are not retained or are blocked by default |
| Screen sharing does not start | Incognito restricts persistent screen and tab access |
| Test session resets or fails to load | Cookies and local storage are cleared or unavailable |
| Pop-ups or system prompts do not appear | Pop-up handling is more restrictive |
| Proctoring features do not activate | Secure monitoring requires saved session data |
### Final Check Before You Begin
Before launching your test, confirm that:
* You are using a standard browser window
* Camera and microphone permissions are enabled
* The page loads fully without privacy warnings
* The browser session remains active without clearing data
## 📚 Related Articles
Still facing issues?
* Review: [Chrome Site Permissions](https://support.google.com/chrome/answer/2693767)
* Check: [*Browser Compatibility Requirements*](https://docs.talview.com/candidates/system-diagnostics/supported-browsers-and-versions)
***
# Why won’t Secure Browser launch on an outdated OS?
Source: https://docs.talview.com/candidates/system-diagnostics/why-wont-secure-browser-launch-on-an-outdated-os
Secure Browser is designed to enforce strict security and proctoring controls during assessments. If your operating system (OS) is outdated, the Secure Browser may fail to launch or function correctly. This is because older OS versions often lack the security frameworks, permissions model, and hardware compatibility required for a secure testing environment.
## ✅ Common Causes and Fixes
| **Cause** | **What You Can Do** |
| :--------------------------------------- | :------------------------------------------------------------ |
| OS version is no longer supported | Update your system to a supported OS version |
| Missing security or system features | Install the latest OS updates to enable required capabilities |
| Compatibility issues with Secure Browser | Restart after updating and relaunch Secure Browser |
## ✅ Supported OS Versions
Ensure your device is running **one of the latest three official OS versions**:
* **Windows:** Windows 11
* **macOS:** Sequoia, Sonoma, Ventura
Devices running older versions may fail system checks or block Secure Browser entirely
## ✅ What to do next?
* Go to `System Settings > Software Update`
* Install all pending **OS updates**
* Restart your system and try launching **Secure Browser** again.
### If You Can’t Update Your OS
* Switch to another supported device that meets OS requirements
* Contact your test coordinator to inform them of the limitation
# Center Admin FAQs
Source: https://docs.talview.com/center-and-proctor-administration/center-admin/faqs/center-admin-faqs
This document provides a comprehensive FAQ guide for the **Talview In-Center Admin Dashboard**, designed to support **Center Managers**, **Center Admins**, and **Proctors** in managing in-person and virtual exam operations efficiently.
The In-Center workflow enables end-to-end administration of exam centers, from configuring center details and planning capacity slots to managing rooms, assigning proctors, and handling candidate check-ins and real time exam day activities.
Whether you are setting up a new center, planning recurring slots, monitoring seat utilization, or managing candidate lifecycle actions, this FAQ guide serves as a quick reference to ensure smooth and compliant exam delivery.
***
### Getting Started
**Q1. What is the In-Center Dashboard?**
The In-Center Dashboard is the central hub for managing exam centers, rooms, capacity slots, and candidate activity for in-person and virtual exam delivery. It gives admins a real-time view of all centers associated with an exam - including their status, location, exam types, room count, and upcoming booking load.
**Q2. Who can access the In-Center Dashboard?**
Access is role-based:
* **Center Admin** — Operational access to check in candidates, verify identity, and manage exam-day activities at specific assigned centers.
**Q3. How do I navigate to the In-Center Dashboard?**
Click the **Centers** icon in the left-hand navigation bar. This opens the Centers list view showing all exam centers associated with your account.
**Q4. What information is visible on the Centers list?**
The Centers table shows:
* Center name
* Status (Active or Inactive)
* Location
* Exam type (CBT, PBT, or both)
* Number of rooms
* Booking load for the next 14 days
***
### Searching & Filtering Centers
**Q5. How do I find a specific center?**
Use the **Search bar** at the top of the Centers list. You can search by center name or location. Search is case-insensitive and supports partial text matching.
**Q6. Can I search by Center Code or Center ID?**
Yes. The search bar supports searching by Center Code and Center ID in addition to center name and location.
**Q7. What filters are available on the Centers list?**
You can filter centers by:
* **Center Status** — Active or Inactive
* **Exam Type** — CBT or PBT
* **Location** — Filter by city, state, or region
Click the **Filter icon** to open the filter panel, apply your selections, and the table will update accordingly. A filter strip will appear to show active filters. Click **Clear All** to remove all filters.
***
### Adding a New Center
**Q8. How do I add a new center?**
Click the **+ Add Center** button on the Centers list page. A side panel will open where you can fill in the center details.
**Q9. What are the required fields when creating a center?**
The following fields are mandatory:
* Center Name
* Center Type — Physical or Virtual
* Exam Type — CBT, PBT, or both
* Time Zone
Optional fields include: Center Code, Contact Name, Contact Email, Contact Phone, Google Maps Link, and Test Accommodations.
* **Physical** — A real-world location where candidates physically attend. Requires a location address and shows on Google Maps.
* **Virtual** — A remote/online center. Location fields are hidden since there is no physical address.
**Q10. What exam types can a center support?**
A center can be configured for:
* **CBT (Computer-Based Testing)** — exams taken on computers
* **PBT (Paper-Based Testing)** — exams taken with paper answer sheets
* **Both** — a center can support both formats simultaneously
**Q11. What accommodations can I configure for a center?**
When adding a center, you can select from the following test accommodations:
* Wheelchair Accessible Seating
* Service Animal Allowed
* Private / Separate Testing Room
* Extra Time Allowed
* Scheduled / Medical Breaks Allowed
* Scribe Allowed
* Screen Reader Allowed
* Assistive Technology Required
* Ergonomic / Adjustable Seating
* Low-Distraction Testing Environment
* Food / Water Allowed
**Q12. Can I create duplicate centers?**
No. The system validates for duplicate Center Codes. If you try to create a center with a code already in use, you will see an error prompting you to choose a different code.
***
### Center Overview Tab
**Q13. What does the Center Overview tab show?**
The Overview tab displays all key information's like center name, status, type, location, operating hours, time zone, room list, quick statistics etc. about a specific center.
**Q14. How do I open a center's Overview?**
Click the **Center Name** in the Centers list. This navigates directly to the center's Overview tab.
**Q15. What does Active/Inactive status mean?**
* **Active** — The center is available for scheduling and can accept bookings.
* **Inactive** — The center is not currently available. Candidates cannot be scheduled here until it is reactivated.
**Q16. How do I change a center's status?**
From the Center Overview, click **Edit Details**. You can toggle the status between Active and Inactive. Changes are saved immediately.
**Q17. How do I edit center information?**
On the Center Overview tab, click **Edit Details**. This opens the edit flow where you can update center name, location, time zone, contact details, exam type, accommodations, and status. Click **Save** to confirm. If required fields are left blank or contain invalid values, inline validation errors will appear and changes will not be saved.
**Q18. How do I edit a center's operating hours?**
In the Overview tab, click the **pencil/edit icon** next to the Operating Hours section. A modal will open showing all days of the week (Monday–Sunday). You can:
* Set open and close times for individual days
* Mark a day as Closed
* Apply changes in bulk across multiple selected days
**Q19. What does the embedded map show?**
For physical centers, the embedded map shows the exact geographic location of the center. For virtual centers, a placeholder illustration is shown instead since there is no physical location.
**Q20. What are Quick Statistics?**
Quick Statistics provide an at-a-glance summary of the center's current state, including total rooms, total seats, number of active rooms today, room utilization percentage, and recent candidate registrations.
***
### Managing Rooms
**Q21. How do I add a room to a center?**
From the Center Overview tab, click **+ Add Room**. In the form, provide:
* Room Name (required)
* Room Capacity (number of seats, required)
* Exam Type supported by the room
* Room Status (Active or Inactive)
**Q22. How do I edit a room's details?**
Click on the room row in the Overview tab. The Edit Room side panel opens where you can modify room name, capacity, exam type, and status.
**Q23. How do I delete a room?**
Use the menu next to the room and select **Delete**. Note: rooms with existing bookings cannot be deleted.
**Q24. How do I manage seat layout within a room?**
Click the capacity number for a room in the Overview tab. The Edit Room side panel opens and shows the **Seat Allocation** section. You can:
* Add individual seats with custom seat labels
* Edit existing seat labels
* Remove seats (seats with active bookings cannot be removed)
***
### Capacity Planning
**Q25. What is the Capacity tab?**
The Capacity tab provides a slot-wise view of exam availability, room allocation, booked seats, and utilization. It helps admins plan and monitor exam delivery capacity over time.
**Q26. What information does each row in the Capacity table show?**
Each row represents one time slot and displays:
* Date and time of the slot
* Number of rooms allocated
* Total seats available
* Bookings count (Lobby + Checked-in)
* Room utilization indicator
* Assigned proctor (if any)
**Q27. How do I plan slots for a center?**
Click **+ Planning** on the Capacity tab. The Recurring Availability panel opens. Fill in:
* Start date and end date
* Days of the week
* Time range (start time and end time)
* Exam type
* Room allocation
The system will generate recurring slots across the selected date range.
**Q28. How do I filter or search within the Capacity tab?**
Use the **Search** icon to look up specific slot groups by name or date. Use the **Filter** icon to filter by:
* Date range (From – To)
* Exam Type
* Time slot
Click **Clear All** to reset all filters.
**Q29. How do I edit capacity for an existing slot?**
Click the menu for a slot row and select **Edit Capacity**. You can change the room allocation and seat count for that slot. You can also apply this change to multiple selected slots in bulk.
**Q30. How do I enable or disable a slot?**
Click the menu next to the slot and select **Disable** to temporarily stop bookings for that slot, or **Enable** to resume. Disabled slots with existing bookings will retain those bookings but won't accept new ones.
**Q31. How do I delete a slot?**
Click the delete icon for the slot row. A confirmation modal will appear showing the slot date and time. If the slot has confirmed bookings, deletion will be blocked. If there are no bookings, confirm to proceed. You can also delete multiple slots in bulk by selecting them and using the bulk delete action.
**Q32. How do I assign a proctor/invigilator to a slot?**
Click on a slot row to open the Allocation view. You will see the list of rooms for that slot. Click **Assign Proctor** next to a room and select from available proctors. Use the breadcrumb navigation (Center → Capacity → Allocation) to go back.
***
### Candidates Tab
**Q33. What does the Candidates tab show?**
The Candidates tab lists all candidates booked at the center. By default, it shows todays and upcoming candidates. Each row displays the candidate's name, external ID, exam name, slot, duration, rooms and assigned seats, accommodation’s, status and registration date.
**Q34. What do the different candidate statuses mean?**
* **Invited** — Candidate has been scheduled at this center
* **Active** — Candidate is confirmed and approaching exam time
* **Lobby** — Candidate has arrived and is in the waiting area
* **Checked-in** — Candidate has completed the check-in process
* **Seated** — Candidate has been assigned a seat
* **In Progress** — Exam is actively ongoing
* **Paused** — Exam is temporarily halted
* **Completed** — Exam has been finished
* **Checked Out** — Candidate has exited the exam session
**Q35. How do I search for a candidate?**
Use the **Search bar** in the Candidates tab. You can search by:
* Candidate Name
* Candidate Email
* Registered Exam Name
* External ID
Search is case-insensitive and supports partial matching.
**Q36. How do I filter the candidates list?**
Click the **Filter icon** to filter by:
* Candidate Status
* Room (multi-select)
* Seat
* Accommodation Type
* Date/Slot
**Q37. How do I view detailed information about a candidate?**
Click on the candidate row to open the candidate detail panel. This shows the candidate's full exam details, slot, seat, accommodation requirements, and status history.
***
### Candidate Check-In
**Q38. How do I check in a candidate?**
Click the **Check-in icon** in the workflow to open the Check-in side panel. Then:
1. Search for the candidate by Email ID or Candidate ID
2. Select the candidate from the search results
3. Capture a photo of the candidate
4. Capture front and back of the candidate's ID document
5. Select an available room and seat
6. Confirm check-in
The candidate's status will update to Checked-in and the seat will be marked as occupied.
**Q39. What ID types can be captured during check-in?**
Only ID types configured for that specific workflow are available for selection during ID capture. The admin captures both the front and back of the selected ID.
**Q40. What happens if a seat is already occupied?**
Occupied seats are not selectable during check-in. Only available (unoccupied) seats are shown for allocation.
**Q41. Can I reassign a candidate's room or seat after check-in?**
Yes. From the menu next to the candidate, select **Reassign**. A modal will open showing available rooms and seats. Select the new room and seat and confirm. The previous seat will be freed and the new allocation saved.
**Q42. Can I update a candidate's status manually?**
Yes. From the menu, select **Update Status**. Choose the new status from the dropdown. A reason field may be required for certain status changes.
***
### Other Candidate Actions
**Q43. How do I reschedule a candidate's exam?**
From the candidate's menu, select **Reschedule**. The Reschedule modal opens, showing available slots. Select the new slot and confirm. The candidate's booking is updated and their original seat is released.
**Q44. How do I cancel a candidate's booking?**
From the menu, select **Cancel Booking**. A confirmation modal appears explaining the impact. Confirm to proceed. The seat is freed and the candidate's status is updated accordingly.
**Q45. How do I report an incident for a candidate?**
From the menu, select **Report Incident**. The Report an Exam Incident modal opens. Fill in:
* Description
* Any supporting evidences
The incident is logged against the candidate's record.
# How to access the search command palette in the In-Center platform
Source: https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/how-to-access-the-search-command-palette-in-the-in-center-platform
In Talview's In-Center platform, you can use the keyboard shortcut **Ctrl+K** (Windows) or **Cmd+K** (Mac) to open the search command palette and quickly take actions on your current screen without navigating through menus.
In this article, you will learn how to use this shortcut across different sections of the Center Management module.
***
## Step-by-step guide
**A. Use the shortcut on the Centers page**
1. Go to **Centers** in the left navigation panel.
2. Press **Ctrl+K** / **Cmd+K**.
3. The command menu displays the option **Create center -** *Create a brand new exam center with hours, rooms, and contacts.*
4. Click **Create center** to proceed, or type in the search bar to filter available actions.
**B. Use the shortcut within a center**
1. Open a center by clicking its name from the Centers list.
2. Press **Ctrl+K** / **Cmd+K**.
3. The command palette displays the option **Add room** — *Go to rooms to create a new testing space.*
4. Click **Add room** to be directed to the Rooms section where you can create a new testing space.
***
**Additional tips**
* The command palette is context-aware, the actions it shows depend on which page you're currently on.
* You can type keywords in the search bar within the command palette to quickly find a specific action.
* This shortcut works across all major sections of the Center Management module.
# How to activate or deactivate a center
Source: https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/how-to-activate-or-deactivate-a-center
Center administrators may sometimes need to temporarily stop or resume operations at a center. You can activate or deactivate a center from the **Center Overview** page to control whether the center is available for exam scheduling.
This article explains how to activate or deactivate a center to manage its operational status.
***
### Step-by-Step Guide
**1. Locate the center you want to modify**
Use the **search bar** or scroll through the list to find the center whose status you want to update.
**2. Open the Center Overview page**
Click the **center name** to open the **Center Overview** page.
This page displays the configuration and operational details for that center.
**3. Locate the center status option**
At the top of the overview page, next to the **center name**, locate the **Edit** icon associated with the center status.
**4 Open the status selection window**
Click the **Edit** icon to open the status selection modal.
**5. Select the desired status**
Choose one of the following options:
* **Active** – The center is available for scheduling exams.
* **Inactive** – The center is temporarily unavailable for scheduling.
**6. Confirm the status change**
Confirm the update to apply the new status.
Once saved, the center status updates immediately, and the new status is reflected across the center management dashboard.
**Additional Tips**
* Deactivating a center prevents **new exam slots and bookings** from being scheduled at that location.
* Existing exam records and historical data remain available even if the center is deactivated.
* If **future exam slots already exist**, review them to ensure they align with the updated center status.
* Only users with **center administrator permissions** can change the center status.
# How to add a new center
Source: https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/how-to-add-a-new-center
This article explains how to create and configure a new exam center from the In-Center dashboard.
***
### Before You Begin
Ensure you have the following information ready:
* Center name
* Center type (Physical or Virtual)
* Supported exam type(s) (CBT and/or PBT)
* Google Maps location link
* Time zone
* Available accommodations (if any)
* Contact name, number, and email
* Workflow(s) (exam templates) to assign
***
### Steps to Add a New Center
**1. Open the Add Center Form**
From the **In-Center dashboard**, click **Add Center** in the top-right corner.
A **Workflow Templates page** will open, displaying all available workflows.
**2. Select Workflow(s)**
Choose one or more **workflows (exam templates)** that you want to enable for the center.
These workflows determine which exams will be available at the center.
After selecting the required workflows, proceed to the **New Center** form.
**3. Enter Center Name**
In the **Center Name**\* field, type the official name of the exam center.
This is the primary identifier displayed in the dashboard.
**4. (Optional) Enter Center Code**
In **Center Code (optional)**, enter an internal reference code if required.
You may leave this blank if not applicable.
**5. Select Center Type**
Under **Center Type**\*, choose one:
* **Physical** — for in-person test centers
* **Virtual** — for remote/online centers
**6. Select Exam Type**
In **Exam Type**\*, choose the supported mode(s):
* **CBT** (Computer-Based Testing)
* **PBT** (Paper-Based Testing)
A center can support one or both depending on availability.
**7. Add Location**
You need to fill in the **Location**\* field if the exam is physical. For this, you need to:
* Search for the location **or**
* Paste the Google Maps link of the center
Make sure it’s correct, as it will be shared with candidates during booking.
**8. Select Time Zone**
From the **Time Zone**\* dropdown, choose the correct time zone for the center location.
This ensures accurate scheduling and slot distribution.
**9. Choose Accommodations**
In **Accommodations**, select any supported accessibility or facility options such as:
* Wheelchair accessibility
* Service animal
* Separate testing room
* Extra time
* Medical breaks
* Food/water allowed
**10. Enter Contact Details**
Provide the center’s point of contact:
* **Contact Name**
* **Contact Number**
* **Contact Email**
**11. Confirm Creation**
After verifying all required fields, click **Confirm**.
> The new center will be successfully added to the In-Center dashboard and will appear in the centers list.
***
### After Adding a Center
Once created, you can:
* View it in the centers table
* Open its Overview by clicking the center name
* Access **workflow-specific tabs** for candidate management
* Monitor status and upcoming distribution
* Edit details later if needed
# How to add rooms in a center
Source: https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/how-to-add-rooms-in-a-center
Rooms are where exams are conducted within a center. Each room is linked to a specific workflow step, determining which exam type it supports. In this article, you will learn how to add a room to a center in the Center dashboard.
***
### Before You Begin
Make sure you have:
* Logged in with the appropriate role credentials (Center Admin, Center Manager, Proctor Lead, or Proctor)" to reflect that other roles can also perform candidate actions.
* Opened a center from the Center dashboard.
***
### Step-by-Step Guide
**1. Navigate to the Overview tab**
From the center detail page, make sure you're on the **Overview** tab. Scroll down to the **Rooms** section.
**2. Click + Add Room**
Click the **+ Add Room** button at the top right of the Rooms section. The **New Room** modal opens.
**3. Select a workflow step**
Click the **Workflow Step** dropdown and choose which exam type this room will be used for. This is a required field, each room must be linked to a specific workflow step.
**4. Enter a room name**
In the **Room Name** field, type a name for the room. This is a required field.
**5. Enter a room code (optional)**
In the **Room Code** field, you can add an optional identifier for the room. This can be used for internal tracking or reference purposes.
**6. Save the room**
Click **Save Changes** to create the room. The new room will appear in the Rooms table on the Overview tab with an **Active** status by default. Click **Cancel** to discard without saving.
**Additional Tips**
* New rooms are created with **Active** status by default. You can change the status later from the room's edit options.
* Each room is tied to one workflow step. If your center supports multiple exam types, you'll need to create separate rooms for each.
* After adding a room, you'll need to add seats to the room separately. See the related article for details.
* The room will appear in the Rooms table with its Workflow Step, Status, Capacity, and 14 Day Distribution columns.
# How to add seats to a room
Source: https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/how-to-add-seats-to-a-room
Seats represent the individual exam spots available within a room. Adding seats helps define the room’s total capacity and determines how many candidates can be accommodated during an exam session.
Before candidates can be allocated to a room, the required number of seats must be configured.
***
### Steps to Add Seats in a Room
1. Navigate to the **Centers** dashboard where all exam centers are listed.
2. Click on the **Center Name** where the room is located.
This will open the center’s **Overview page**.
3. Navigate to the **Rooms** section within the center.
4. Locate the room where you want to add seats.
5. Click on the **Room Name** to open the room details.
6. Navigate to the **Seats** section inside the room.
7. Click the **Add Seat** option.
8. Enter the required seat information, such as:
* **Seat Number / Seat Name** – A unique identifier for each seat within the room.
9. Click **Save** to add the seat to the room.
***
**Additional Tips**
* Use **sequential seat numbers** (for example: Seat 1, Seat 2, Seat 3) to keep seat arrangements organized.
* Ensure each seat has a **unique identifier** to avoid confusion during candidate allocation.
* Review the seating configuration after adding seats to confirm that the room capacity is accurately reflected.
# How to assign a Proctor and Proctor Lead to a Capacity slot
Source: https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/how-to-assign-a-proctor-and-proctor-lead-to-a-capacity-slot
Proctor leads and proctors are assigned at different levels to ensure proper oversight during an exam session. A **proctor lead** is assigned at the **slot level** from the Capacity tab, they are responsible for overseeing the entire session across all rooms and candidates in that time slot. A **proctor** is assigned at the **individual seat level** from the Seat Allocation view, they are responsible for monitoring specific candidates during the exam.
In this article, you will learn how to assign both roles in Center dashboard.
***
### Before You Begin
Make sure you have:
* Logged in with your Center Admin credentials.
* Opened a center and navigated to the **Capacity** tab.
* At least one planning slot created with rooms and seats assigned.
***
### Step-by-Step Guide
### Assigning a Proctor Lead
**1. Locate the Proctors column**
From the **Capacity** tab, find the slot you want to assign a proctor lead to. The **Proctors** column shows any currently assigned proctor leads as avatars.
**2. Click the "+" icon**
Click the **+** icon in the Proctors column for that slot. A dropdown opens showing:
* **Currently assigned proctors** at the top, each with a **delete (trash) icon** to remove them.
* A **search field** to find a specific proctor.
* A list of **available proctors** below, showing their name and email.
**3. Select a proctor lead**
Click on a proctor's name from the available list to assign them as a proctor lead for the slot. Their avatar will appear in the Proctors column. You can assign multiple proctor leads to a single slot.
**4. Remove a proctor lead (if needed)**
To remove an assigned proctor lead, click the **+** icon to open the dropdown, then click the **delete (trash) icon** next to the proctor you want to remove.
***
### Assigning a Proctor to Individual Seats
**5. Open the Seat Allocation view**
Click on the slot's **time link** (e.g., "4 PM – 6 PM") to open the Seat Allocation view.
**6. Assign a proctor to a seat**
In the **Proctor** column, each seat shows either an assigned proctor avatar or is empty. To assign a proctor, click on the **Proctor** column for the seat you want to assign. Select a proctor from the available list.
**7. Remove a seat-level proctor (if needed)**
To remove a proctor from a seat, click the "**✕"** icon on their avatar in the Proctor column. The seat will return to an unassigned state.
***
**Additional Tips**
* You can assign the same proctor to multiple seats within the same room.
* Use the search field in the proctor dropdown to quickly find a specific proctor by name or email.
* If a slot shows bookings but no proctors assigned, consider assigning them before the session starts.
# How to assign a seat to a candidate after check-in
Source: https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/how-to-assign-a-seat-to-a-candidate-after-check-in
Once a candidate is checked in, a seat can be assigned to ensure they are placed in the correct room for the exam.
***
### Steps to Assign a Seat
1. Go to the **Centers** section.
2. Select the required **center**.
3. Open the relevant **Workflow tab**.
4. Click on the **candidate’s name** to open the **Candidate Details panel**.
5. Click on Check-In
***
### Assigning the Seat
1. In the Candidate Check-In, locate the **Seat Allocation** section.
2. Click on the **edit (pencil) icon** next to the seat details.
3. Select:
* **Room**
* **Available Seat**
4. Confirm the selection.
***
### What Happens After Assignment
* The selected **seat is assigned** to the candidate.
* The seat status changes from **Available to Occupied**.
* Capacity is updated automatically.
* The assigned **room and seat number** are reflected in the candidate details.
***
**Note**
* Only **available seats** can be assigned.
* Seats that are **occupied, blocked, or inactive** cannot be selected.
* Ensure the correct room and seat are chosen before confirming.
# How to assign room and seats to a slot
Source: https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/how-to-assign-room-and-seats-to-a-slot
Once a planning slot has been created, you can assign rooms to it from the Seat Allocation view. When a room is assigned, its seats automatically become available for candidate allocation within that slot. In this article, you will learn how to assign rooms and seats to a scheduled slot in Center dashboard.
***
### Before You Begin
Make sure you have:
* Logged in with the appropriate role credentials (Center Admin, Center Manager, Proctor Lead, or Proctor)" to reflect that other roles can also perform candidate actions.
* Opened a center and navigated to the **Capacity** tab.
* At least one planning slot created and rooms configured in the center.
***
### Step-by-Step Guide
**1. Open the Seat Allocation view**
From the **Capacity** tab, click on the **time link** of the slot you want to assign rooms to. This opens the Seat Allocation view.
**2. Click + Add room**
Click the **+ Add room** button at the top right. The **Add rooms to \[slot time]** modal opens, displaying available rooms from your center plan.
**3. Select rooms to add**
The modal shows rooms that are available for this time slot. Select the rooms you want to assign. If no rooms are available, the modal displays "No additional rooms available to add." This means all rooms in your center are already assigned to this slot or configured for a different workflow step.
**4. Confirm the selection**
Click the **Add rooms** button to assign the selected rooms. The button dynamically updates to show the count of rooms you've selected. Click **Cancel** to go back without adding.
**5. Verify the assignment**
After adding, the Seat Allocation view updates to show the room's seats listed individually. Each seat row displays the seat name, candidate assignment (if any), status (**Available** or **Occupied**), and proctor assignment. The seats are grouped under a label showing the room name and session date.
**Additional Tips**
* The total slot capacity is automatically calculated based on the combined seat count of all assigned rooms.
* Only rooms that match the slot's workflow step are available for selection. For example, a Speaking Session slot will only show rooms configured for the Speaking workflow step.
* After assigning rooms, you can assign proctors to individual seats from the Seat Allocation view.
* To remove a seat from a slot, use the **delete (trash) icon** on the seat row.
* You need to create a planning slot before you can assign rooms to it. See the article on how to create a planning slot for details.
# How to change room status
Source: https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/how-to-change-room-status
Room status determines whether a room is available for scheduling, capacity planning, and candidate seat allocation.
This article explains how to change the status of a room in the In-Center workflow.
***
### Steps to Change Room Status
**Step 1: Navigate to the Center**
1. Go to the **Centers** dashboard.
2. Click on the relevant **Center Name**.
3. You will land on the **Overview** tab.
**Step 2: Locate the Room**
1. In the **Rooms** section, find the room whose status needs to be updated.
2. Click on the room row or open the three-dot (⋮) action menu.
**Step 3: Update the Status**
1. Select **Edit Room** (if applicable).
2. Locate the **Room Status** field.
3. Change the status:
* Select **Active** to make the room available.
* Select **Inactive** to temporarily disable it.
**Step 4: Save Changes**
Click **Save** to apply the updated status.
The room status will immediately reflect in the Rooms list.
**Important Considerations**
* Deactivating a room does not delete it.
* Rooms with ongoing or upcoming sessions should be reviewed carefully before deactivation.
* Always verify that no critical exams are scheduled before changing the status.
* Status changes take effect immediately after saving.
**Best Practice**
Before marking a room as Inactive:
* Review upcoming slots in the **Capacity** tab.
* Inform relevant stakeholders (proctors, center admins).
* Ensure candidates are reassigned if required.
# How to check in a candidate
Source: https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/how-to-check-in-a-candidate
The **Check-In** process is used to mark a candidate as present at the test center and complete their verification before the exam begins. This step ensures that the candidate is properly identified, assigned a seat, and ready to start their exam.
Candidates are organized under **Workflows**. Each workflow represents a specific exam or exam type configured for the center.
***
### Accessing the Candidate
To check in a candidate:
1. Navigate to the **Centers** section.
2. Select the **center** where the candidate is scheduled.
3. Click on the relevant **Workflow tab** (this replaces the earlier Candidates tab).
4. Locate the candidate in the list.
You will see the candidate’s **current status** in the table.
***
### Opening Candidate Details
1. Click on the **candidate’s name**.
2. The **Candidate Details panel** will open.
3. Click on Check-In
This panel displays key information about the candidate, including:
* Candidate name and email
* Current status (e.g., Registered, Checked-in)
* Seat allocation (Room and Seat number)
* Check-in details section
***
### Starting the Check-In Process
If the candidate has not been checked in:
1. Click on **Complete Check In**.
This opens the **Check-In Details view**, where verification steps can be completed.
***
### Understanding the Check-In Screen
The Check-In screen includes the following sections:
#### 1. Check-In Status
Displays whether the check-in has been completed or is still pending.
***
#### 2. Seat Allocation
Shows the assigned:
* **Room number**
* **Seat number**
You may also have the option to edit this using the **edit (pencil) icon**, if reassignment is needed before completing check-in.
***
#### 3. ID Capture
This section is used to verify the candidate’s identity.
* Capture or upload the candidate’s **ID proof**
* The system records who captured the ID
***
#### 4. Face ID
This section is used for **facial verification** of the candidate.
* Capture the candidate’s face image
* Used for identity validation and monitoring
***
### Completing the Check-In
Once all required steps are completed:
1. Click **Complete Check In** at the bottom of the panel.
After successful check-in:
* The candidate’s status updates to **Checked-in**
* The candidate is marked as ready for the exam
* The seat assignment is confirmed in the system
***
**Important Notes**
* Check-in can only be performed if the candidate is in an eligible state (e.g., Registered/Invited).
* Ensure **ID and Face verification** are completed before finalizing check-in.
* Seat allocation should be verified before completing the process.
* Once checked in, the candidate moves forward in the exam workflow.
***
> To check in a candidate, navigate to the relevant **Workflow tab**, open the candidate’s details, and complete the verification steps in the **Check-In panel**. This ensures the candidate is properly verified, seated, and ready to begin their exam.
# How to check the address of the center in map?
Source: https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/how-to-check-the-address-of-the-center-in-map
You can view the exact location of a center directly from the **Overview tab** using the map view.
***
### Steps to View the Location
1. Go to the **Centers** section.
2. Select the required **center**.
3. Navigate to the **Overview** tab.
You can access the map in two ways:
**Option 1: From Center Details**
* In the **Center Details** section, locate the **address/location**.
* Click on it to open the map view.
**Option 2: From Map View Panel**
* On the **right side**, you will see a **map preview**.
* Click on the map to open a detailed view.
***
### What Happens Next
* The system opens the location in a **map view**.
* You can see the **exact address and pin location** of the center.
# How to configure center operating hours
Source: https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/how-to-configure-center-operating-hours
Operating hours define when a center is available to conduct exams and generate exam slots. Administrators can set or update operating hours for each day of the week to ensure exams are scheduled only during the center’s available time.
This article explains how to configure or update the operating hours for a center.
***
### Step-by-Step Guide
**1. Open the Center Overview page**
Navigate to the **Overview** tab for the center.
This page displays key information about the center, including **exam type, operating hours, and other configuration details**.
**2. Locate the Operating Hours section**
In the **Overview** page, find the **Operating Hours** section.
This area displays the current schedule for each day of the week (for example, **Monday–Friday open hours and Saturday–Sunday closed**).
**3. Open the operating hours editor**
Click **Edit Details** below the **Operating Hours** section.
This opens the **Hours configuration panel**, where you can modify the working schedule.
**4. Choose the day you want to edit**
In the **Hours panel**, each day of the week appears with its current status.
Click the **Edit (pencil) icon** next to a specific day to modify its schedule.
**5. Set the operating time for the selected day**
If the center operates on that day:
* Enter the **Start time** (for example, **9:00 AM**).
* Enter the **End time** (for example, **8:00 PM**).
If the center does not operate on that day, set the status to **Closed**.
**6. Repeat the configuration for other days**
Update the operating hours for any other days where changes are required.
**7. Review the configured schedule**
Confirm that the selected **days and time ranges** accurately reflect the center’s working hours.
**8. Save the operating hours**
Click **Submit** to apply the changes.
The updated hours will immediately appear in the **Operating Hours** section on the **Overview** page.
Once saved, these operating hours determine the **time range within which exam slots can be created** for the center.
**Additional Tips**
* Exam slots can only be scheduled **within the configured operating hours**.
* If a day is marked **Closed**, no exam slots can be generated for that day.
* Always review operating hours **before generating slots using the Planning feature**.
* If operating hours change, verify that **existing slots still fall within the updated time window**.
# How to create a planning slot
Source: https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/how-to-create-a-planning-slot
Planning slots let you define recurring exam availability for your center. Using the Recurring availability modal, you can schedule time windows across multiple days for a specific workflow step. In this article, you will learn how to create a planning slot in Talview's Center dashboard.
***
### Before You Begin
Make sure you have:
* Logged in with your Center Admin credentials.
* Opened a center and navigated to the **Capacity** tab.
***
### Step-by-Step Guide
**1. Open the Recurring availability modal**
From the **Capacity** tab, click the **+ Planning** button at the top right. The **Recurring availability** modal opens.
**2. Enter a schedule name**
In the **Schedule name** field, type a name for the schedule. This name will appear as the slot grouping label on the Capacity tab.
**3. Select a workflow step**
Click the **Workflow step** dropdown and choose the exam type this slot is for (e.g., "Listening-Reading-Writing Session" or "Speaking Session"). This is a required field - each planning slot must be linked to a specific workflow step.
**4. Set the date and time**
Fill in the following fields:
* **Start date** - the first date the slot should begin. Click the calendar icon to select a date.
* **Start time** - the session start time. Select from the dropdown.
* **End time** - the session end time. Select from the dropdown.
The time zone is displayed below the date and time fields (e.g., "Times are in Asia/Kolkata") to confirm which time zone the slot is being created in.
**5. Select recurring days**
Click on the **day buttons** (M, T, W, T, F, S, S) to choose which days of the week the slot should repeat on. Selected days appear highlighted. You can select multiple days.
**6. Set an end date**
In the **Until** field, select the last date the recurring schedule should run until. Click the calendar icon to choose the date.
**7. Save the planning slot**
Click **Save** to create the recurring slots. The new slots will appear on the Capacity tab, grouped under the schedule name and date. Click **Cancel** to discard without saving.
***
**Additional Tips**
* The schedule name is used as the grouping label on the Capacity tab (e.g., "Thursday, 18 Jun 2026 - LRW test"), so use a clear and descriptive name.
* Make sure the start and end times fall within the center's configured operating hours.
* After creating a planning slot, you'll still need to assign rooms and proctors to each slot from the [**Seat Allocation view**](https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/understanding-the-seat-allocation-view).
* To delete a scheduled slot, use the trash icon on the slot row in the Capacity tab.
# How to create a room within a workflow step
Source: https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/how-to-create-a-room-within-a-workflow-step
Adding rooms to a center allows you to define where exams will be conducted. Rooms are now linked to specific **Workflows** (exam types), making it easier to manage capacity per exam.
***
### **Steps to Add a Room**
1. Go to the **Centers** section.
2. Select the **center** where you want to add a room.
3. Navigate to the **Overview** tab.
4. Scroll down to the **Rooms** section.
5. Click on **Add Room**.
***
### **Configure Room Details**
Once the **Add Room** panel opens, fill in the required details:
* **Workflow Selection** – Choose the workflow (exam) this room will be assigned to
* **Room Name** – Enter a unique name for the room
* **Room Code** – Which is optional as of now
> Each room must now be mapped to a specific workflow.
***
### Save the Room
1. After entering all details, click **Save**.
2. The room will be added to the center and linked to the selected workflow.
***
**Note**
* A room is **associated with a specific workflow**, not globally across all exams.
* Ensure you select the correct workflow while creating the room.
* Capacity defined here directly impacts seat planning and allocation.
# How to decline a candidate booking
Source: https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/how-to-decline-a-candidate-booking
Sometimes due to operational issues, duplicate bookings, or candidate requests Center administrators can submit a decline booking request so the exam coordinator can review and reassign the booking and/or reschedule the booking
This article explains how to submit a decline booking request for a candidate from the **Candidates** tab.
***
## Step-by-Step Guide
Follow these steps to decline a candidate booking.
**1. Open the Candidates tab**
Navigate to the **Candidates** tab within the center workflow.
This page displays the list of candidates scheduled to take exams at the center, along with details such as **exam slot, status, and assigned room**.
**2. Locate the candidate booking**
Scroll through the candidate list or use available **filters** to find the candidate whose booking needs to be declined.
Each row represents a candidate booking associated with a specific exam slot.
**3. Open the candidate action menu**
On the right side of the candidate row, click the **menu** to view the available actions.
**4. Select the Decline booking option**
From the action menu, click **Decline booking**.
This opens the **Decline booking request panel**.
**5. Select the reason for declining the booking**
From the **Reason** dropdown, choose the most appropriate reason for declining the booking.
Common reasons include:
* **Technical issue at center**
* **Center operational issue**
* **Other** (with optional remarks)
**6. Add remarks (optional)**
If additional explanation is required, enter details in the **Remarks** field to provide context for the request.
**7. Confirm the decline request**
Click Confirm **decline request** to send the request to the exam coordinator for review.
Once submitted, the booking remains active until the **exam coordinator reviews and approves the request**.
**Additional Tips**
* Declining a booking does **not cancel** the candidate’s slot but the slot will no longer be tagged to them
* Provide **clear remarks** when selecting **Other** as the reason.
* Decline requests cannot be submitted if the candidate’s exam status is **In Progress** or **Completed**.
* If the request is approved, the candidate will be **removed from the slot and the slot capacity will increase**.
# How to delete a room?
Source: https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/how-to-delete-a-room
Deleting a room removes it from the center’s configuration. This action should be performed carefully, as it affects capacity planning and future scheduling.
This article explains how to permanently delete a room from a center in the In-Center workflow.
***
### Before You Delete a Room
Before proceeding, ensure:
* The room has **no upcoming or active bookings**.
* The room is not assigned to any future capacity slots.
* You have the required role permissions (typically Center Manager or authorized Admin access).
> **Important:** Deleting rooms with existing or confirmed bookings comes with a one time warning.
***
### **Steps to Delete a Room**
**Step 1: Navigate to the Center**
1. Go to the **Centers** dashboard.
2. Click on the relevant **Center Name**.
3. You will land on the **Overview** tab.
**Step 2: Locate the Room**
1. In the **Rooms** section, find the room you want to delete.
2. Click the **delete icon** next to the room.
**Step 3: Select Delete**
1. From the action menu, select **Delete**.
2. A confirmation modal will appear showing the room details.
**Step 4: Confirm Deletion**
1. Review the confirmation message carefully.
2. Click **Confirm** to permanently delete the room.
The room will immediately be removed from the Rooms list.
**Best Practice**
Before deleting a room:
* Review the **Capacity tab** for future slot allocations.
* Check the **Candidates tab** for upcoming seat assignments.
* Communicate changes to relevant center staff.
If the room might be used again in the future, consider marking it **Inactive** instead of deleting it.
# How to delete a scheduled exam slot
Source: https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/how-to-delete-a-scheduled-exam-slot
Administrators may occasionally need to remove a scheduled exam slot due to scheduling changes, operational adjustments, or incorrect slot creation. You can delete an existing slot from the **Capacity** schedule when it is no longer required.
This article explains how to delete an exam slot from the **Capacity** table.
***
### Before You Begin
Make sure that:
* The slot you want to delete exists in the **Capacity** schedule.
* The slot does **not have candidates currently taking the exam**, as such slots cannot be deleted.
* If candidates are assigned to the slot, they may need to be **rescheduled to another slot** before deletion.
***
### Step-by-Step Guide
**1. Open the Capacity tab**
Navigate to the **Capacity** tab inside the center configuration.
This page displays all scheduled slots along with details such as **date, time, exam type, assigned rooms, and seat capacity**.
**2. Locate the slot you want to delete**
Scroll through the **Capacity table** to find the slot that needs to be removed.
Each row represents a scheduled slot and displays the relevant scheduling details.
**3. Open the slot actions menu**
On the right side of the slot row, click the **menu** to view the available actions for that slot.
**4. Select the delete option**
From the menu, click **Delete slot**.
A confirmation dialog will appear to prevent accidental deletion.
**5. Review the deletion confirmation**
The confirmation modal displays a warning indicating that deleting the slot will permanently remove it from the **Capacity** schedule.
**6. Confirm slot deletion**
Click **Delete slot** to proceed with the deletion.
The slot will be removed from the **Capacity table** and will no longer be available for candidate booking.
**Additional Tips**
* Slots with **active or ongoing exam sessions** cannot be deleted.
* If candidates are already assigned to a slot, you may need to **reschedule or cancel their bookings** before deleting it.
* Deleting a slot **frees the room capacity** for that time period.
* Always verify the **slot date, time, and room allocation** before confirming deletion.
# How to delete seats in a room
Source: https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/how-to-delete-seats-in-a-room
You can remove individual seats from a room through the Edit Room panel. This is useful when you need to reduce a room's capacity or remove seats that are no longer in use.
In this article, you will learn how to delete seats from a room in Center dashboard.
***
### Before You Begin
Make sure you have:
* Logged in with your Center Admin credentials.
* Opened a center and navigated to the **Overview** tab.
***
### Step-by-Step Guide
**1. Open the Edit Room panel**
From the **Overview** tab, scroll down to the **Rooms** section. Click on the room you want to edit. The **Edit Room** panel opens, showing the room's **Seat Allocation** table.
**2. Locate the seat you want to remove**
The Seat Allocation table lists all seats in the room with two columns:
* **Seat Name** - the seat identifier.
* **Status** - the current state of the seat (e.g., "Active").
**3. Click the delete icon**
Click the **delete (trash) icon** on the row of the seat you want to remove. The seat is removed immediately - changes are saved automatically.
**4. Close the panel**
Once you're done, click **Cancel** or the "**✕"** icon to close the Edit Room panel. The room's capacity on the Overview tab will update to reflect the new seat count.
***
**Additional Tips**
* Changes are saved automatically, there's no separate save button. Be careful when clicking the delete icon as the seat is removed immediately.
* Make sure the seat isn't currently assigned to a candidate in an upcoming or active session before removing it.
* Deleting a seat reduces the room's overall capacity, which may affect slot planning and bookings.
* You can also remove seats from within the **Seat Allocation view** on the Capacity tab using the trash icon on individual seat rows.
# How to edit center details
Source: https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/how-to-edit-center-details
Accurate center information helps administrators manage exam operations, communicate with candidates, and maintain reliable scheduling records.
Center administrators can update key details such as location, contact information, operating hours, and accessibility accommodations directly from the **Center Overview** page.
This article explains how to edit center details to ensure the center configuration remains accurate and up to date.
***
### Step-by-Step Guide
1. **Select the field you want to edit.**
Each editable field includes an **Edit** icon beside it.
Click the **Edit** icon next to the field you want to update.
2. **Update the required information.**
Enter the updated or corrected information in the input field.
Ensure that details such as **email address**, **phone number**, and **location** are accurate and properly formatted.
3. **Review your changes before saving.**
Verify that the updated information is correct and free of typing errors.
4. **Save the updated center details.**
Click **Save changes** to apply the updates.
The information will immediately update on the **Center Overview** page.
Once saved, the updated details will be reflected across the center configuration and used for future scheduling and administrative processes.
| Field | Description |
| :------------------ | :------------------------------------------------------------ |
| **Location** | The physical address of the center |
| **Email** | Contact email used for center communication |
| **Contact number** | The primary phone number for the center |
| **Accommodation** | Accessibility or support arrangements available at the center |
| **Operating hours** | The hours during which the center can conduct exams |
**Additional Tips**
* Ensure the **contact email and phone number** are accurate so candidates and support teams can reach the center when necessary.
* If you update the **location**, confirm that directions to the center remain correct for candidates.
* When modifying **operating hours**, verify that the new schedule does not conflict with existing exam slots.
* Editing center details does not affect **previous exam records or completed sessions**.
* Only users with **center administrator permissions** can make these changes.
# How to edit exam types (PBT/CBT)
Source: https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/how-to-edit-exam-types-pbt-cbt
You can update the exam type for a center from the **Overview tab** under center details.
***
### Steps to Edit Exam Type
1. Go to the **Centers** section.
2. Select the required **center**.
3. Navigate to the **Overview** tab.
4. In the **Center Details** section, locate **Exam Type**.
5. Click on the **edit (pencil) icon** next to it.
6. Select the required option:
* **PBT (Paper-Based Test)**
* **CBT (Computer-Based Test)**
7. Save the changes.
***
**Note**
* You can select the exam type based on the center’s setup and requirements.
* Changes apply to how exams are configured and conducted at that center.
* Ensure the correct type is selected before saving.
# How to edit room details
Source: https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/how-to-edit-room-details
Room details may sometimes need to be updated due to changes in naming, room availability, or administrative updates. The platform allows coordinators to easily modify room information within a center.
***
### Steps-by-step Guide
1. Navigate to the **Centers** dashboard where all available exam centers are listed.
2. From the list of centers, click on the **Center Name** where the room is located.
This will open the center’s **Overview page**.
3. Navigate to the **Rooms** section of the center where all the rooms configured for that center are displayed.
4. Locate the room whose details you want to update.
5. Click the **Edit** option available for that room.
6. The **Edit Room** form will open, allowing you to modify the room information. Update the required fields such as:
* **Room Name** – Update the name if the room has been renamed or needs clearer identification.
* **Room Code** – Modify the room code if required for internal tracking.
* **Room Status** – Change the status to **Active** if the room is available for exams, or **Inactive** if the room should not be used.
7. After making the necessary changes, click **Save** to update the room details.
**Additional Tips**
* Use **clear and recognizable room names** so coordinators can easily identify rooms during exam operations.
* If a room becomes temporarily unavailable, change its status to **Inactive** instead of deleting it.
* Always review the updated information before saving to ensure the correct room details are maintained.
# How to edit seats in a room
Source: https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/how-to-edit-seats-in-a-room
Seat details may need to be updated if there are changes to the seat identifier, numbering format, or seating arrangement within a room. Editing seat information helps maintain accurate seating records and ensures candidates can be allocated correctly during exam sessions.
***
### Steps-by-step Guide
1. Navigate to the **Centers** dashboard where all exam centers are listed.
2. Click on the **Center Name** where the room is located.
This will open the center’s **Overview page**.
3. Navigate to the **Rooms** section within the center.
4. Locate the room that contains the seat you want to edit.
5. Click on the **Room Name** to open the room details.
6. Navigate to the **Seats** section where all seats configured for that room are displayed.
7. Locate the seat you want to modify.
8. Click the **Edit** option available for that seat.
9. Update the required seat information, such as:
* **Seat Number / Seat Name** – Modify the identifier if the seating arrangement or numbering needs to be updated.
10. Click **Save** to apply the changes.
**Additional Tips**
* Maintain a **consistent seat numbering format** across the room to make seat identification easier.
* Ensure that each seat has a **unique identifier** to prevent allocation conflicts during exam scheduling.
* Double-check the updated seat details before saving to avoid errors in the seating configuration.
# How to export candidate data
Source: https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/how-to-export-candidate-data
You can export candidate data from a workflow tab to download a file containing all the candidate information for that specific exam type.
In this article, you will learn how to export candidate data in Talview's Center dashboard.
***
### Before You Begin
Make sure you have:
* Logged in with your Center Admin credentials.
* Opened a center and navigated to a **workflow tab** (e.g., Listening-Reading-Writing Session).
***
### Step-by-Step Guide
**1. Navigate to the workflow tab**
From the center detail page, click on the workflow tab for the exam type you want to export data for.
**2. Apply filters (optional)**
If you want to export a specific subset of candidates, use the **Filter** icon or **Search (Ctrl+K)** bar to narrow down the list before exporting. Only the filtered results will be included in the export.
**3. Click Export**
Click the **Export** button at the top right of the page. The file downloads automatically.
***
**Additional Tips**
* The export contains data only for the current workflow tab. To export data for a different exam type, switch to that workflow tab and export separately.
* Apply filters before exporting to get a targeted dataset - for example, export only candidates with a specific status or exam date.
# How to export capacity data
Source: https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/how-to-export-capacity-data
In this article, you can understand how the **Export** feature in the Capacity tab allows you to download center capacity details for reporting and analysis.
***
### Steps to Export Capacity Data
1. Go to the **Centers** section.
2. Select the required **center**.
3. Navigate to the **Capacity** tab.
4. Click on the **Export** button (available at the top right).
The data will be downloaded as an **Excel file**.
***
### Exporting Specific Workflow Data
If you want to export data for a specific workflow or schedule:
1. Use the **Search bar** (Ctrl + K) to find the required workflow or schedule.
2. Filter the results based on your search.
3. Click on **Export**.
Only the **filtered data** will be exported.
***
\*\*Note \*\*
* Exported data includes **slots, rooms, capacity, bookings, and related details**.
* Search before exporting if you need **workflow-specific data**.
* The file is downloaded in **Excel format** for easy sharing and analysis.
# How to export the center data
Source: https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/how-to-export-the-center-data
The **Export** feature allows you to download the list of centers for reporting or analysis.
***
### Steps to Export Center Data
1. Go to the **Centers** section.
2. Locate the **Export** button at the top right (next to the filter and add center options).
3. Click on the **Export** button.
The system will download the center data as an **Excel file**.
***
**Note**
Use the **Export** button on the Centers page to download center data. Apply filters if needed to export specific results.
# How to filter and search within the candidate tab
Source: https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/how-to-filter-and-search-within-the-candidate-tab
When viewing candidates in a workflow tab, you can use filters and search to narrow down the list and quickly find specific candidates.
In this article, you will learn how to use the filter and search options within a workflow tab in Talview's Center dashboard.
***
### Before You Begin
Make sure you have:
* Logged in with your Center Admin credentials.
* Opened a center and navigated to a **workflow tab**
***
### Step-by-Step Guide
**1. Search for a candidate**
Use the **Search (Ctrl+K)** bar at the top right of the page to search for a candidate by name or email. The list filters in real time as you type.
**2. Open the filter panel**
Click the **Filter** icon (at the far right of the header row) to open the filter dropdown. You'll see a list of available filters along with a search field to find a specific filter option.
**3. Apply filters**
The following filters are available:
* **Status** - filter by candidate status (e.g., Registered, Checked-in, No Show).
* **Slot time** - filter by the scheduled time window.
* **Allocated room** - filter by the room the candidate is assigned to.
* **Allocated seat** - filter by the specific seat assigned.
* **Exam** - filter by the registered exam name.
* **Exam date** - filter by the date of the exam.
Click on a filter to expand it and select the criteria you want to apply.
**4. Combine search and filters**
You can use the search bar and filters together. For example, search for a candidate by name while filtering by a specific status or slot time to narrow down results further.
**5. Clear filters**
To remove applied filters, open the filter panel and deselect the active criteria. This restores the full candidate list.
***
**Additional Tips**
* Filters apply only to the current workflow tab. Switching to a different workflow tab resets the filters.
* Use the **Exam date** filter to quickly view candidates for a specific day without scrolling through the date-grouped list.
* Filters don't persist between sessions, if you leave and return, you'll need to reapply them.
# How to filter and search within the Capacity tab
Source: https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/how-to-filter-and-search-within-the-capacity-tab
The Capacity tab in Talview displays all scheduled exam slots across dates, exam types, time ranges, rooms, and seat availability. As the number of slots grows, scrolling through the full list to find what you need becomes time-consuming. Filtering and search options help you narrow the list to specific slots so you can review and manage scheduling faster.
In this article, you will learn how to use filters and the search bar in the Capacity tab, understand what each filter option does, and combine filters with search to locate slots efficiently.
***
### Before you begin
* You need administrator or center manager access to view the Capacity tab.
* The Capacity tab is accessible from the center overview. Make sure exam slots have already been created before attempting to filter or search.
***
### Step-by-step guide
**1. Open the Capacity tab**
* Navigate to the center overview.
* Select the **Capacity** tab. The page displays all scheduled slots with details such as date, time, exam type, assigned rooms, and seat availability.
**2. Apply filters to narrow down slots**
* At the top of the Capacity table, click the **Filter** icon to open the filtering panel.
* Select one or more filter criteria from the available options. Each filter narrows the displayed slots based on the value you choose:
* **Date** - Limits the view to slots scheduled on a specific date or within a date range. Use this when reviewing upcoming schedules or checking availability for a particular day.
* **Exam type** - Shows only slots associated with a specific exam type. This is helpful when your center hosts multiple exam formats and you need to manage one type at a time.
* **Time slot** - Filters slots that fall within a specific time range. Use this to focus on morning, afternoon, or evening sessions without scanning the entire list.
* After selecting your filter values, apply the filters. The table refreshes and displays only the slots matching your selected criteria.
* To return to the full slot list, click **Clear filters** to remove all applied filters.
> Filters don't carry over between sessions. Each time you open the Capacity tab, the view resets to show all slots. Reapply filters as needed.
**3. Search for slots in the Capacity tab**
* At the top of the Capacity tab, locate the **Search** field.
* Enter a keyword related to the slot you're looking for - such as a date, time, or exam type name.
* As you type, the table automatically updates to show slots matching your search term.
* To return to the full list, clear the text from the **Search** field.
> Search matches against visible column data. If you're not finding a slot you expect, check whether an active filter is hiding it - clear all filters first, then search again.
# How to filter and search within the center tab
Source: https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/how-to-filter-and-search-within-the-center-tab
The **Centers tab** provides search and filter options to help you quickly locate specific centers and refine the list based on your requirements.
***
### Searching for a Center
1. Go to the **Centers** section.
2. Locate the **Search bar** at the top right.
3. Enter the **center name**.
The list will automatically update and display matching results.
***
### Available Filters
You can filter centers based on:
* **Center Status** (Active / Inactive)
* **Exam Type** (CBT / PBT)
* **Center location**
***
### Applying Filters
1. Click on the **Filter icon** next to the search bar.
2. Select the required filter criteria.
3. Apply the filters to refine the results.
***
# How to manage candidate actions in a session
Source: https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/how-to-manage-candidate-actions-in-a-session
Talview's assessment view gives you the tools to manage candidates in a session based on their current status. In this article, you will learn how to view and take action on candidates directly from the assessment tab.
***
### Step-by-Step Guide
1. Go to the Centers list and click on the specific center you want to manage candidates for.
2. Click on the Assessment tab.
3. Click on the candidate's name to view the available actions for that candidate.
The actions available will depend on the candidate's current status:
* **Registered**
* View Profile - view the candidate's profile details.
* Check In - check the candidate in to their assessment.
* Decline Booking - decline the candidate's booking for the session.
* Mark as Absent - record that the candidate didn't attend their assessment.
* **Checked-In**
* View Profile - view the candidate's profile details.
* Re Check-In - check the candidate in again if needed.
* Decline Booking - decline the candidate's booking for the session.
* Mark as Absent - record that the candidate didn't attend their assessment.
* Report Incident - log an incident related to the candidate during the session.
* **No Show**
* View Profile - view the candidate's profile details.
* Check In - check the candidate in to their assessment.
* Decline Booking - decline the candidate's booking for the session.
* Mark as Absent - record that the candidate didn't attend their assessment.
***
**Additional Tips**
* The **Report Incident** action is only available for candidates with a **Checked-In** status.
* If a candidate's status doesn't look right, try refreshing the page before taking any action.
# How to mark a candidate as absent
Source: https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/how-to-mark-a-candidate-as-absent
When a candidate doesn't show up for their scheduled exam, you can mark them as absent directly from the workflow tab. This updates the candidate's status to **No Show**, indicating that they did not attend the session.
In this article, you will learn how to mark a candidate as absent in Talview's Center dashboard.
***
### Before You Begin
Make sure you have:
* Logged in with the appropriate role credentials (Center Admin, Center Manager, Proctor Lead, or Proctor) to reflect that other roles can also perform candidate actions.
* A center with candidates in a **Registered** status.
***
### Step-by-Step Guide
**1. Open the center and navigate to the workflow tab**
From the **Centers** list, click on the center. Then click on the relevant workflow tab to view the candidate list for that exam.
**2. Locate the candidate**
Find the candidate you want to mark as absent. You can scroll through the date-grouped list or use the **Search (Ctrl+K)** bar for windows and **(Cmd+K)** for Mac to find them by name or email.
**3. Open the actions menu**
Click the **three-dot menu (⋯)** on the candidate's row.
**4. Click Mark as absent**
Select **Mark as absent** from the menu. The candidate's status will update to **No Show**.
**Additional Tips**
* **Mark as absent** is only available for candidates whose status allows it. If the option appears greyed out, the candidate may already be checked in or in a completed state.
* This action is different from **Decline booking,** declining sends the booking to the exam coordinator for review, while marking as absent directly updates the candidate's status to **No Show**.
# How to perform actions on a candidate from the Workflow tab
Source: https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/how-to-perform-actions-on-a-candidate-from-the-workflow-tab
From the workflow tab, you can take various actions on individual candidates depending on their current status. These actions are accessed through the three-dot menu on each candidate row. In this article, you will learn what actions are available, when they can be used, and how they behave based on candidate status.
***
### Before You Begin
Make sure you have:
* Logged in with the appropriate role credentials (Center Admin, Center Manager, Proctor Lead, or Proctor).
* Opened a center and navigated to a **workflow tab**.
***
### Step-by-Step Guide
**1. Open the actions menu**
From the workflow tab, locate the candidate you want to take action on. Click the **three-dot menu (⋯)** at the far right of their row.
**2. Review available actions**
The menu displays the following actions:
* **View profile** - opens the candidate's profile side panel showing their activity timeline, check-in history, photos, ID documents, and registration details.
* **Check In** - initiates the check-in flow for the candidate, including seat allocation, ID capture, and face verification.
* **Decline booking** - sends a decline request to the exam coordinator for review. You'll be asked to select a reason (e.g., technical issue, center operational issue, other) and can add optional remarks.
* **Mark as absent** - updates the candidate's status to **No Show**, indicating they did not attend the session.
* **Report incident** - opens the incident report form to log an issue such as a candidate complaint, suspected cheating, or rule violation.
**3. Understand greyed-out actions**
Not all actions are available for every candidate. Certain actions become greyed out depending on which stage of the exam the candidate is currently in. For example, **Report incident** is only available once a candidate has been checked in, since incidents can only be logged during an active session. Similarly, **Mark as absent** is not available if the candidate has already been checked in or has completed the exam. Greyed-out actions are still visible in the menu so you can see the full range of possible actions, but they cannot be clicked until the candidate reaches the appropriate stage.
**4. Action availability by status**
The table below shows which actions are available based on the candidate's current status:
| Action | Registered | Checked-in | No Show |
| :-------------- | :--------- | :--------- | :--------- |
| View profile | ✅ | ✅ | ✅ |
| Check In | Greyed out | Greyed out | Greyed out |
| Decline booking | ✅ | ✅ | ✅ |
| Mark as absent | ✅ | Greyed out | Greyed out |
| Report incident | Greyed out | ✅ | Greyed out |
**Additional Tips**
* **Check In** may only become available when the session is active or within a specific time window before the slot starts.
* **Mark as absent** and **Decline booking** serve different purposes, marking as absent directly updates the status to No Show, while declining sends a request to the exam coordinator for review.
* **Report incident** is only available for candidates who have been checked in, as incidents can only be logged during an active session.
* You can also access **View profile** by clicking directly on the candidate's name in the list.
# How to reassign a candidate's room or seat after check-in
Source: https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/how-to-reassign-a-candidates-room-or-seat-after-check-in
In some situations, administrators may need to move a candidate to a different **seat** or **room** after the candidate has already been checked in. This may be required due to seating adjustments, room changes, technical issues, or operational requirements at the exam center.
In this article, you can understand how the **Reassign Seat** option allows administrators to safely move a candidate to another available seat while ensuring that the center’s capacity and seat allocation remain accurate.
***
## When Seat Reassignment Is Available
The **Reassign Seat** option appears in the candidate’s **menu** within the **Candidates tab**.
This option is available only when:
* The candidate **already has a seat assigned**
* The candidate is in an **eligible status**, such as:
* **Checked-in**
* **Seated**
Seat reassignment is **not available** when the candidate’s exam session has already ended or reached a restricted state.
Reassignment is **blocked** if the candidate status is:
* **Completed**
* **Checked Out**
* **Stopped**
* **Suspended**
***
## How to Reassign a Candidate’s Room or Seat
Follow these steps to reassign a candidate’s seat:
1. Navigate to the **Centers** section and open the required **center**.
2. Click the **Candidates** tab.
3. Locate the candidate in the candidates list.
4. Click the **menu** next to the candidate.
5. Select **Reassign Seat**.
The system will open the **Check-in Details view** for that candidate.
***
## Information Displayed in the Reassign View
In the reassignment screen, administrators can view:
* **Current Room**
* **Current Seat Number**
* **Exam Slot Details**
This view helps administrators clearly see the candidate’s current allocation before making any changes.
***
## Selecting a New Seat
Only **available seats** can be selected for reassignment.
The following seats **cannot be selected**:
* Seats that are **already occupied**
* Seats that are **blocked**
* Seats that are **inactive**
This ensures that the reassignment does not create seat conflicts or capacity issues.
***
## Reassigning Within the Same Room
If the administrator selects a **different available seat in the same room** and confirms the action:
* The **previous seat is released**
* The **new seat is assigned**
* The room **capacity updates automatically**
* The candidate’s record reflects the **new seat number**
* A **success confirmation message** appears
***
## Reassigning to a Different Room
Administrators can also move the candidate to a **seat in another room within the same exam slot**.
When reassignment is confirmed:
* The **previous seat is released**
* The candidate is assigned to the **new seat in the selected room**
* **Room capacity updates automatically**
* The candidate’s record updates with the **new room and seat**
* A **success confirmation message** is displayed
***
## What Happens if No Seats Are Available
If the selected room **does not have any available seats**, the system:
* **Blocks the reassignment**
* Displays a message indicating **no seats are available**
The candidate’s original seat assignment remains unchanged.
***
## Reassignment During an In-Progress Exam
If a candidate’s status is **In Progress**, seat reassignment may be restricted depending on system rules.
In this case, the system will either:
* **Block the reassignment**, or
* Require the administrator to **confirm the action before proceeding**
This prevents accidental disruption of an ongoing exam.
***
# How to report an exam incident for a candidate
Source: https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/how-to-report-an-exam-incident-for-a-candidate
When an issue occurs during an exam session such as a candidate complaint, suspected cheating, or a rule violation, you can report an incident against the specific candidate using the three-dot menu on their row in the workflow tab. The incident is logged in the candidate's profile timeline and includes details such as severity, workflow step, and actions taken.
In this article, you will learn how to report an exam incident in Center dashboard.
***
### Before You Begin
Make sure you have:
* Logged in with the appropriate role credentials (Center Admin, Center Manager, Proctor Lead, or Proctor) to reflect that other roles can also perform candidate actions.
* Opened a center and navigated to a **workflow tab.**
* A candidate in **Checked-in** status (incident reporting is only available for checked-in candidates).
***
### Step-by-Step Guide
**1. Open the actions menu**
From the workflow tab, locate the candidate you want to report an incident for. Click the **three-dot menu (⋯)** on their row.
**2. Click Report incident**
Select **Report incident** from the menu. This opens the incident report form. If the option appears greyed out, the candidate's current status doesn't allow incident reporting, only candidates with a **Checked-in** status can have incidents reported against them.
**3. Fill in the incident details**
Complete the following fields:
* **Nature of Incident** - select the type of incident (e.g., "Candidate Complaint", suspected cheating, unauthorized devices, rule violation).
* **Severity** - choose the severity level: **Low**, **Medium**, or **High**.
* **Select Sub Test** - specify the workflow step the incident relates to. While the label in the side panel says "Sub Test", this refers to the specific workflow step that was active when the incident occurred.
* **What Happened** - describe what occurred. Include the time of the incident for reference.
* **Action Taken** - document what action was taken in response (e.g., warning issued, exam paused, materials confiscated).
* **Reason** - provide any additional context or reasoning.
**4. Submit the incident**
Click **Submit** to log the incident. The incident is recorded in the candidate's profile timeline as a **red-dot entry** with the timestamp of when it was reported.
**5. View the incident report**
To review a reported incident, open the candidate's profile by clicking their name. In the activity timeline, click on the **red-dot incident entry** (e.g., "Candidate Complaint") to open the full **Incident Report** showing all the details you entered.
**6. Return to the profile timeline**
To go back from the incident report view to the main profile timeline, click the **← back arrow** at the top of the report.
***
**Additional Tips**
* Report incidents as soon as they occur, include the exact time in the **What Happened** field for accurate records.
* The **Severity** level helps prioritize incidents during review. Use **Low** for minor issues, **Medium** for moderate concerns, and **High** for serious violations.
* Incidents are recorded in the candidate's profile timeline and remain visible for future reference.
# How to search schedules
Source: https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/how-to-search-schedules
Talview's capacity view in the In-Center dashboard includes a search feature that lets you filter schedules by assessment. In this article, you will search for a specific schedule using the search bar on the capacity view.
***
### Step-by-Step Guide
1. Go to the Centers list and click on the center you want to search schedules for.
2. Click on the Capacity tab.
3. In the Search bar in the top right, type in the name of the assessment you're looking for.
* The capacity list will automatically filter to show only the matching schedule.
***
**Additional Tips**
* The capacity list filters in real time as you type, so you don't need to press **Enter** to see results.
* If no results appear, double-check the spelling of the assessment name.
* If you need to view all schedules again, clear the **Search** bar.
# How to update candidate status
Source: https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/how-to-update-candidate-status
The **Update Status** option allows administrators to manually change a candidate’s exam status during the in-center exam process. This helps staff accurately reflect the candidate’s progress and manage the exam workflow in real time.
***
### Accessing the Candidate Status Option
To update the status of a candidate:
1. Navigate to the **Centers** section from the main dashboard.
2. Select the **center** where the candidate is scheduled.
3. Click on the **Candidates** tab.
4. Locate the candidate in the **Candidates table**.
5. Click the **menu (⋯)** at the end of the candidate’s row.
6. Select **Update Status** from the available options.
A status selection window will appear, allowing you to change the candidate’s current status.
***
### Available Candidate Statuses
When updating a candidate’s status, you may see several possible status options depending on the stage of the exam session. These statuses indicate the candidate’s current progress.
| Status | Description |
| :-------------- | :------------------------------------------------------------------------------------------- |
| **Invited** | The candidate has been scheduled for the exam but has not yet started the exam process. |
| **Checked-In** | The candidate has arrived at the test center and completed the initial verification process. |
| **Lobby** | The candidate is waiting in the system lobby before being seated for the exam. |
| **Seated** | The candidate has been assigned a seat in the exam room. |
| **In Progress** | The candidate has started the exam and is currently taking it. |
| **Paused** | The exam session has been temporarily paused. |
| **Completed** | The candidate has finished the exam. |
| **Checked Out** | The candidate has completed the entire exam process and exited the center workflow. |
***
### Updating the Status
After selecting **Update Status**:
1. Choose the appropriate **status** from the list.
2. Confirm the change.
Once updated, the new status will immediately appear in the **Status column** in the Candidates table.
**Best Practices When Updating Status**
To maintain accurate exam tracking:
* Ensure the candidate has completed the required step before updating their status.
* Verify candidate identity before marking them as **Checked-In**.
* Only mark **Completed** after the exam session has officially ended.
* Use **Paused** only when an exam session needs to be temporarily halted.
Keeping candidate statuses updated helps maintain clear visibility of exam progress across the center.
***
# How to view a candidate's profile in Center dashboard
Source: https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/how-to-view-a-candidates-profile-in-center-dashboard
The candidate profile gives you a detailed view of a candidate's session activity, including a record of their check-in attempts, captured photos and ID documents, registration details, and any reported incidents. In this article, you will learn how to access and navigate the candidate profile within the Center dashboard.
***
### Before You Begin
Make sure you have:
* Logged in with the appropriate role credentials (Center Admin, Center Manager, Proctor Lead, or Proctor).
* Opened a center and navigated to a **workflow tab** (e.g., Listening-Reading-Writing Session).
***
### Step-by-Step Guide
**1. Open the candidate profile**
From a workflow tab, click on the **candidate's name** in the list. A side panel opens on the right displaying the candidate's profile.
**2. Review the profile header**
At the top of the panel, you'll see:
* **Candidate name** and **status badge** (e.g., "Checked-in" in green).
* **Email address**.
* **Registered exam** name.
* **Accommodation tags** - displayed as pill badges with icons (e.g., "Religious attire", "Extra time (25%)").
**3. Navigate the activity timeline**
Below the header, the profile displays a chronological activity timeline. Each entry is marked with a color-coded dot:
* 🔴 **Red dot** - indicates an incident (e.g., "Candidate Complaint"). Click on the entry to view the full incident report.
* 🔵 **Blue dot** - indicates a successful action (e.g., "Checked in · Attempt 2").
* ⚫ **Grey dot** - indicates informational events (e.g., Registration Details).
Each entry includes a timestamp (e.g., "29 April 2026, 10:37 AM").
**4. Review check-in details**
Under a blue-dot check-in entry, you'll see the following details:
* **Method** - the check-in method used (e.g., "Physical").
* **Slot** - the scheduled time window (e.g., "9:30 AM - 11:30 AM").
* **Room / Seat** - the assigned room and seat (e.g., "Room A / LRW-10").
* **Center Step** - the center-level workflow step.
* **Exam Step** - the exam-level workflow step.
The attempt number is shown in the entry heading (e.g., "Checked in · Attempt 2"), indicating how many check-in attempts the candidate has made.
**5. View captured photos and ID documents**
Below the check-in details, two sections display verification data:
* **Photos captured** - shows the **Face Capture** taken during check-in with a thumbnail image. Click to view the full image.
* **ID documents captured** - shows **ID Card Front** and **ID Card Back** as separate entries with thumbnail images. Click to view the full document.
**6. Review Registration Details**
At the bottom of the timeline, under a grey dot, the **Registration Details** section shows:
* **Name** - candidate's full name.
* **External ID** - the candidate's external identifier (if assigned).
* **Email** - the candidate's email address.
* **Slot** - the scheduled time window.
* **Room / Seat** - the assigned room and seat.
* **Center Step** - the center-level workflow step.
* **Exam Step** - the exam-level workflow step.
**7. View an incident report**
If the timeline contains a red-dot incident entry, click on it to open the **Incident Report** within the side panel. The report shows:
* **Candidate Name** and **Candidate ID**.
* **Nature of Incident** - the type of incident (e.g., "Candidate Complaint").
* **Severity** - the severity level (e.g., "Low" in green).
* **Time Reported** - when the incident was logged.
* **Select Sub Test** - the specific workflow step the incident relates to (e.g., "Writing"). While the label says "Sub Test," this refers to the workflow step that was active when the incident occurred.
* **What Happened** - a description of the incident.
* **Action Taken** - what action was taken in response.
* **Reason** - additional context or reasoning.
Click the **← back arrow** to return to the main profile timeline.
**Additional Tips**
* The activity timeline is ordered with the most recent events at the top.
* Multiple check-in attempts are logged separately, so you can see the full record of a candidate's check-in activity.
* To close the profile panel, click the **✕** icon at the top right of the side panel.
# How to view candidates for a specific center
Source: https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/how-to-view-candidates-for-a-specific-center
The **Candidates** tab within a center allows administrators to view all candidates scheduled to take exams at that specific center. This view provides a consolidated list of candidates along with their exam details, seating allocation, accommodations, and current exam status.
***
### Accessing the Candidates List
To view candidates assigned to a center:
1. Navigate to the **Centers** section from the main dashboard.
2. Select the **center** you want to manage from the centers list.
3. Once inside the center page, click the **Candidates** tab.
The system will display a table containing all candidates scheduled for exams at that center.
***
### Understanding the Candidates Table
Each row in the **Candidates table** represents a candidate scheduled for an exam. The table provides detailed information to help administrators track candidate activity and manage exam operations efficiently.
The table includes the following columns:
| Column | Description |
| :-------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Candidate** | Displays the candidate’s name and registered email address. |
| **External ID** | The unique candidate identifier used in the system. |
| **Registered Exam** | The exam that the candidate is scheduled to take. |
| **Slot** | The scheduled exam start time. |
| **Duration** | The total duration of the exam session. |
| **Room** | The room number where the candidate will take the exam. |
| **Seat** | The specific seat assigned to the candidate within the room. |
| **Accommodations** | Icons indicating any special accommodations assigned to the candidate. |
| **Status** | Shows the current stage of the candidate’s exam session (for example: Invited, Active, Checked-in, Lobby, Seated, In Progress, Paused, Completed, Checked Out). |
| **Registration Date** | The date and time when the candidate registered for the exam. |
Candidates are also grouped by **exam date**, making it easier to track sessions scheduled for different days.
**Searching for a Candidate**
You can quickly locate a candidate using the **Search bar** located at the top of the Candidates page.
Search supports the following fields:
* Candidate name
* Email address
* External ID
* Exam name
The results update dynamically as you type.
**Candidate Actions**
Each candidate row includes a **menu** that provides operational actions such as:
* **Update Status**
* **Cancel Booking**
These actions allow administrators to manage candidate exam workflows directly from the candidates list.
***
# How to view candidates using Workflow tabs
Source: https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/how-to-view-candidates-using-workflow-tabs
In Center dashboard, candidates are organized into workflow tabs based on the exam they're registered for. Instead of a single candidate list, each exam type has its own tab - making it easier to view and manage candidates for a specific assessment. In this article, you will learn how to navigate workflow tabs and view candidates within them.
***
### Before You Begin
Make sure you have:
* Logged in with the appropriate role credentials (Center Admin, Center Manager, Proctor Lead, or Proctor).
* At least one center with active bookings.
***
### Step-by-Step Guide
**1. Open the center**
From the **Centers** list, click on the center you want to view. This opens the center's detail page.
**2. Locate the workflow tabs**
At the top, you'll see tabs alongside **Overview** and **Capacity**. Each additional tab represents a workflow step. These tabs are predefined based on the exam workflows configured for your center.
**3. Click on a workflow tab**
Click on the tab for the exam type you want to view. The page displays a list of candidates registered for that specific exam, grouped by date (e.g., "Wednesday, 29 Apr 2026").
**4. Review candidate details**
Each row shows the following information:
* **Candidate** - name and email address.
* **Accommodations** - displayed as icons (e.g., religious attire, extra time).
* **Registered Exam** - the exam the candidate is registered for.
* **Slot** - the scheduled time window.
* **Duration** - total exam duration.
* **Room** - the assigned room.
* **Seat** - the assigned seat.
* **Status** - current status (Registered, Checked-in, No Show, etc.).
* **Registration Date** - when the candidate was registered.
**5. Take action on a candidate**
Click the **three-dot menu (⋯)** on any candidate row to see available actions. These include **View profile**, **Check In**, **Decline booking**, **Mark as absent**, and **Report incident**. Actions that aren't available for the candidate's current status will appear greyed out.
***
**Additional Tips**
* Use the **Search (Ctrl+K)** bar at the top right to find a specific candidate by name or email within the current workflow tab.
* Use the **Filter** icon to narrow down candidates by status, slot, room, or other criteria.
* The [**Export**](https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/how-to-export-candidate-data) button downloads candidate data for the current workflow tab.
# How to view room capacity
Source: https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/how-to-view-room-capacity
Room capacity refers to the total number of seats configured within a room. It directly impacts slot planning, seat allocation, and overall center utilization.
This article explains how to view the seating capacity of a room in the In-Center workflow.
***
### Where Can I View Room Capacity?
You can view room capacity from:
* The **Overview** tab (center-level view)
* The **Capacity** tab (slot-level view)
***
### Method 1: View Capacity from the Overview Tab
**Step 1: Open the Center**
* Go to the **Centers** dashboard.
* Click on the relevant **Center Name**.
* You will land on the **Overview** tab.
**Step 2: Locate the Rooms Section**
In the **Rooms** section, you will see a table listing all configured rooms.
The table displays:
* Room Name
* Room Status (Active/Inactive)
* Capacity (total seats)
* Next 14 Days Distribution
The **Capacity column** shows the total number of seats available in that room.
**Step 3 (Optional): View Detailed Seat Allocation**
*To see individual seats:*
* Click on the room row (or click on the capacity number).
* The **Edit Room** side panel will open.
* Navigate to the **Seat Allocation** section.
*Here you can:*
* View all configured seat labels
* Add new seats (if required)
* Edit or remove seats (if no active bookings exist)
***
### Method 2: View Capacity from the Capacity Tab (Slot-Level)
**Step 1: Open the Capacity Tab**
* From the center page, click on the **Capacity** tab.
**Step 2: Review Slot Information**
Each row in the Capacity table shows:
* Date and time slot
* Number of rooms allocated
* Total seats available for that slot
The **Seats column** displays the combined capacity across all rooms allocated to that specific slot.
This helps you understand how room capacity translates into actual scheduling availability.
**Important Notes**
* Inactive rooms do not contribute to available capacity for new bookings.
* Capacity updates automatically when seats are added or removed.
* Seats with active bookings cannot be deleted.
* Slot-level capacity depends on which rooms are allocated to that slot.
# Understanding Candidates Dashboard
Source: https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/understanding-candidates-dashboard
The Candidates tab in **Talview's In-Center platform** gives the center admin a session-level view of all candidates at a specific exam center. In this article, you will learn how to monitor candidate progress, verify seating, manage accommodations, and perform operational actions during an exam session.
***
### **Accessing the Candidates tab**
From the center's page, click the **Candidates** tab next to **Overview** and **Capacity**. The full candidate roster for that center opens.
**Viewing candidate profile details**
Each row in the table displays key candidate information:
* Candidate name and email
* External ID
* Registered exam
* Scheduled slot
* Exam duration
* Assigned room and seat
* Accommodations (if any)
* Current status
* Registration date
**Searching for a candidate**
Use the **Search** bar at the top right to locate a candidate by name, email, or ID.
**Monitoring candidate status**
The **Status** column shows the candidate's current stage in the exam journey. Statuses include:
* Invited
* Active
* Lobby
* Checked-in
* Seated
* In Progress
* Paused
* Completed
* Checked Out
**Verifying room and seat assignments**
The **Room** and **Seat** columns show where each candidate is placed. Use these to manage seating logistics, support on-ground staff, and resolve seating conflicts.
**Reviewing accommodations**
The **Accommodations** column displays icons representing approved accommodations for each candidate. This helps you quickly identify candidates who require special support during the exam.
**Performing candidate actions**
Each candidate row includes a three-dot menu with the following actions:
* **Update Status** — manually adjust the candidate's exam status when required
* **Check-in** — mark the candidate as checked in
* **Report incident** — log any exam-related issues
* **Upload results** — submit or attach exam outcomes
* **Reschedule** — move the candidate to a different slot
* **Cancel booking** — cancel the candidate's exam appointment
**Navigating by exam date**
Candidates are grouped by exam date. Use this to manage daily test sessions, track attendance per day, and review historical activity.
**Managing pagination**
Use the **Page controls** and **Rows per page** selector at the bottom of the table to navigate through large candidate lists.
# Understanding Capacity Dashboard
Source: https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/understanding-capacity-dashboard
The **Capacity** tab provides a time-slot level view of how an exam center’s rooms and seats are being utilized. It helps admins monitor bookings, track check-ins, and evaluate room utilization trends over a selected date range.
***
## Accessing the Capacity Tab
Click the **Capacity** tab next to Overview.
This opens the slot-wise capacity management view for that specific center.
***
## What You Can Do in the Capacity Tab
### Adjust the date range
At the top left, the **Date Range** selector (for example, *Next 30 Days*) controls the time window displayed.
* Modify this to analyze capacity for different periods.
* Use the edit icon to change the range as needed.
* Select **Clear All** to reset filters.
This helps in short-term or long-term planning.
***
### View slot-wise scheduling
The table is organized by **date and time slots** (for example, 9:00 AM – 12:00 PM).
For each slot, you can quickly understand:
* when the exam window is scheduled
* what exam mode is running
* how much capacity is allocated
This enables precise monitoring of daily operations.
***
### Identify exam mode per slot
The **Exam Type** column shows whether the slot is:
* **CBT** (Computer-Based Testing)
* **PBT** (Paper-Based Testing)
This helps ensure the correct infrastructure is being used for each session.
***
### Monitor rooms allocated
The **Rooms** column displays how many rooms are assigned to that slot.
Use this to:
* verify room allocation
* detect under- or over-allocation
* plan redistribution if required
***
### Track total seat availability
The **Seats** column shows the total seating capacity available for the slot across assigned rooms.
This gives a quick view of maximum intake for that session.
***
### Analyze bookings and check-ins
The **Bookings** bar provides a visual and numeric breakdown of candidate flow:
* **Lobby** — candidates registered/scheduled
* **Checked-in** — candidates who have completed check-in
This helps coordinators:
* monitor real-time attendance flow
* anticipate crowding
* identify no-show patterns
***
### Review room utilization trends
The **Room Utilization** graph shows how effectively rooms are being used for that slot.
With this you can:
* spot high-utilization periods
* identify idle capacity
* optimize future slot planning
***
### Create or adjust planning
Use the **+ Planning** button in the top-right to configure or modify slot planning for the center.
This is typically used when:
* adding new exam windows
* adjusting capacity distribution
* updating future schedules
***
# Understanding Center Overview
Source: https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/understanding-center-overview
The Center Overview page gives you a detailed view of a specific center, including its configuration, location, rooms, and real-time statistics.
In this article, you will learn what each section on the Center Overview page displays and how to navigate it.
***
### Before You Begin
Make sure you have:
* Logged in with the appropriate role credentials (Center Admin, Center Manager, Proctor Lead, or Proctor)" to reflect that other roles can also perform candidate actions.
* Opened a center from the Center dashboard by clicking on its name.
***
### Step-by-Step Guide
**1. Navigate to the Overview tab**
After clicking a center name from the dashboard, you'll land on the **Overview** tab by default. The breadcrumb at the top shows your navigation path. You'll also see additional tabs: **Capacity** and one or more **workflow step tabs.**
**2. Review center details**
The main section displays the center's configuration, which can be edited:
* **Center name** - shown at the top with an **Active** or **Inactive** status badge.
* **Center Code** - the unique identifier for the center. Virtual centers display "Virtual" here.
* **Location** - a clickable link showing the city and country code (e.g., "London, GBR"). Not applicable for virtual centers.
* **Exam type** - the supported formats shown as badges: **CBT**, **PBT**, or both. Click the **edit (pencil) icon** to modify.
* **Operating Hours** - the center's schedule for each day of the week, showing the time range (e.g., "9 am–8 pm") or "Closed." Click **Edit Details** to update.
* **Time Zone** - the center's configured time zone (e.g., "Europe/London", "Asia/Kolkata").
* **Email** - the contact email for the center.
* **Contact name** - the name of the center's primary contact.
* **Contact phone** - the contact phone number.
* **Accommodations** - displayed as icons representing the accommodations available at the center (e.g., wheelchair access, extra time, separate room).
**3. View the map**
On the right side, a map panel shows the center's location with a pin marker. Click **Get Directions** to open the location in a maps application. For virtual or remote centers, the panel displays "Map preview not available" with a prompt to add a Google Maps link.
**4. Review Quick Statistics**
Below the map, the **Quick Statistics** panel provides a real-time snapshot:
* **Rooms** - total number of rooms in the center.
* **Seats** - total seat capacity across all rooms.
* **Rooms active today** - how many rooms are currently active.
* **Today's Utilization** - the percentage of seats in use today.
* **This Week Avg** - the average utilization for the current week.
* **Registered Today** - number of candidates registered for today's sessions.
* **14 Day Distribution** - a sparkline showing booking activity over the next 14 days with a total count.
Click **View Capacity Management →** to navigate directly to the Capacity tab.
**5. Review the Rooms section**
Below center details, the **Rooms** section shows all rooms configured for the center. The table columns are:
* **Room Name** - the name of the room.
* **Workflow Step** - the exam type assigned to the room (e.g., "Listening, Reading & Writing", "Speaking"). Each room is mapped to a specific workflow step.
* **Status** - **Active** (green) or **Inactive**.
* **Capacity** - the number of seats in the room. Click the number to view individual seat details.
* **14 Day Distribution** - a sparkline showing the room's booking activity over the next 14 days with a total count.
Each room row also has a **delete (trash) icon** on the far right to remove the room.
**6. [Add a room](https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/how-to-add-rooms-in-a-center) or view the room map**
At the top of the Rooms section, you'll see:
* **Room map** - click to add rooms in bulk.
* **+ Add Room** - click to add a new room to the center.
***
**Additional Tips**
* The total room count is displayed next to the "Rooms" heading (e.g., "Rooms · 2").
* Rooms are linked to specific workflow steps - when adding a room, you'll need to select which workflow step it belongs to.
* Consider deactivating rooms instead of deleting them if they're only temporarily unavailable.
# Understanding the Allocation View
Source: https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/understanding-the-allocation-view
The **Allocation view** helps administrators manage how rooms, seats, and proctors are assigned for a specific exam slot This view provides a detailed breakdown of the slot configuration, including which rooms are allocated, how many seats are available, and which proctors are assigned to supervise each room.
***
### Step-by-Step Guide
**1. Open the Capacity tab**
* Navigate to the **Capacity** tab in the center workflow.
* This page displays the list of scheduled exam slots, including details such as **date, time, exam type, and total slot capacity**.
**2. Locate the slot you want to review**
Scroll through the **slot table** to find the specific slot whose room and seat allocation you want to review.
**3. Open the slot allocation view**
* Click anywhere on the **slot row**.
* This opens the **Allocation view**, where you can see how the slot is distributed across rooms.
***
### Key Actions in the Allocation view
Once the allocation view opens, you will see detailed information about how the slot is configured.
**Rooms assigned to the slot**
The allocation view lists all **rooms allocated** for the selected slot.
Each room entry typically displays:
* **Room name or number**
* **Room seat capacity**
* **Current seat usage**
If multiple rooms are assigned, the **combined capacity of all rooms** determines the total number of candidates that can be scheduled for the slot.
**Seat allocation**
For each room, the system shows the **number of seats available, and the number of seats already used**.
Seat availability depends on:
* The **seat layout configured for the room**
* The **number of candidates assigned to the slot**
If seat capacity changes due to room adjustments, administrators may need to **reassign seats** for candidates.
**Proctor assignment**
Each room in the allocation view includes an option to **assign or view a proctor** responsible for supervising that room.
When a proctor is assigned, the view displays:
* **Proctor name**
* **Room assigned for supervision**
Assigning a proctor ensures that every exam room has **proper supervision during the exam session**.
**Additional Tips**
* The **total slot capacity** is calculated based on the combined seat capacity of all assigned rooms.
* If a room is **removed from the allocation**, the slot capacity may decrease.
* Ensure that **each room has an assigned proctor** before the exam begins.
* If a room’s **seat configuration changes**, review the allocation view to confirm seat availability
# Understanding the Capacity Tab
Source: https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/understanding-the-capacity-tab
The Capacity tab provides a slot-level view of your center's exam scheduling. It shows all planned time slots along with their exam types, rooms, seat capacity, proctor assignments, and booking status.
In this article, you will learn what information is available on the Capacity tab and what actions you can take from it.
***
### Before You Begin
Make sure you have:
* Logged in with the appropriate role credentials (Center Admin, Center Manager, Proctor Lead, or Proctor) to reflect that other roles can also perform candidate actions.
* Opened a center from the Center dashboard.
***
### Step-by-Step Guide
**1. Navigate to the Capacity tab**
From the center detail page, click the **Capacity** tab at the top. You can also get here by clicking **View Capacity Management →** from the Quick Statistics panel on the Overview tab.
**2. Review the slot list**
The Capacity tab displays all scheduled slots grouped by date and schedule name. Each row represents a time slot with the following columns:
* **Slot** - the time window for the session. Displayed as a clickable blue link that opens the Seat Allocation view.
* **Exam type** - the exam formats for the slot, shown as badges: **CBT**, **PBT**, or both.
* **Step** - the workflow step associated with the slot.
* **Rooms** - the number of rooms assigned to the slot.
* **Total capacity** - the combined seat count across all rooms assigned to the slot.
* **Proctors** - proctor avatars assigned to the slot. Click the **+** icon to assign additional proctors.
* **Bookings** - shows the number of candidates in two stages: **Lobby** (candidates who have registered and are waiting to be checked in) and **Checked-in** (candidates who have completed the check-in process and are ready for the exam). Displayed as a count with a mini progress bar.
Each slot row also has a **delete (trash) icon** on the far right to remove the slot.
**3. Create a planning slot**
Click the **+ Planning** button at the top right to open the **Recurring availability** modal. This lets you create recurring time slots for a workflow step across selected days.
**4. Search for a slot**
Use the **Search (Ctrl+K)** bar for windows and **(Cmd+K)** for Mac at the top right to search for slots by assessment or schedule name. The list filters in real time as you type.
**5. Filter slots**
Click the **Filter** icon to narrow down slots by criteria such as date, exam type, or time slot.
**6. Export capacity data**
Click the **Export** button at the top right to download the capacity data as a CSV spreadsheet. Any active filters or search terms will be applied to the export.
**7. Open the Seat Allocation view**
Click on a slot's **time link** to open the Seat Allocation view, where you can see individual seat assignments, candidate allocations, and per-seat proctor assignments for that slot.
**8. Navigate between pages**
If there are more slots than the page can display, use the page controls at the bottom right to move between pages. You can adjust the **Rows per page** setting.
**Additional Tips**
* Slots are grouped by both date and schedule name, making it easy to identify different sessions running on the same day.
* The Proctors column gives you a quick visual of staffing without needing to open each slot individually.
* If a slot shows bookings but no proctors, consider assigning proctors before the session starts.
# Understanding the Center Dashboard
Source: https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/understanding-the-center-dashboard
The Center dashboard is the main landing page of the Center platform. It displays all exam centers in a single list view, giving you a quick overview of each center's status, location, exam types, room count, and upcoming booking activity.
In this article, you will learn what each element on the Center dashboard represents and how to navigate it.
***
### Before You Begin
Make sure you have:
* Logged in with the appropriate role credentials (Center Admin, Center Manager, Proctor Lead, or Proctor) to reflect that other roles can also perform candidate actions.
***
### Step-by-Step Guide
**1. Access the Center dashboard**
After logging in, you'll land on the **Centers** page. This is the main dashboard that lists all centers in your organization.
**2. Review center details**
Each row in the table represents a center. The columns are:
* **Center name** - the name of the center.
* **Status** - either **Active** (green) or **Inactive** (grey). Active centers can accept bookings; inactive centers cannot.
* **Location** - for physical centers, this shows the city and country code with a blue map pin icon (e.g., "Bengaluru, IND"). For virtual/remote centers, this shows a globe icon with "Remote."
* **Exam type** - the exam formats supported at the center, shown as badges: **CBT** (Computer-Based Test), **PBT** (Paper-Based Test), or both.
* **Rooms** - the total number of rooms configured for the center.
* **14 day distribution** - an activity graph showing booking activity over the next 14 days. Each bar represents one day, taller bars mean more bookings. A number at the end shows the total booking count for the 14-day period.
**3. Search for a center**
Click the **Search (Ctrl+K)** bar for Windows and **(Cmd+K)** for Mac at the top right and type a center name. The list filters in real time as you type.
**4. Filter centers**
Click the **Filter** icon (next to the search bar) to open the filter panel. You can filter by:
* **Center status** - Active or Inactive.
* **Exam type** - Computer-Based Test (CBT) or Paper-Based Test (PBT).
* **Location** - filter by city or region.
Use the search field within the filter panel to quickly find a specific filter option.
**5. Export center data**
Click the **Export** button at the top right to download the center list as a CSV spreadsheet. Any active filters will be applied to the export.
**6. Navigate between pages**
If you have more centers than the page can display, use the page controls at the bottom right to move between pages. You can adjust the **Rows per page** setting (default is 50).
***
**Additional Tips**
* Columns are sortable, click on any column header to sort the list in ascending or descending order.
* The **+ Add center** button at the top right lets you create a new center.
* To view a center's full details, click on its name to open the Center Overview page.
# Understanding the Next 14 Days Distribution column
Source: https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/understanding-the-next-14-days-distribution-column
The 14 day distribution column provides a quick visual snapshot of upcoming booking activity for each center and room. It appears on both the Center dashboard and the Center Overview page. In this article, you will learn how to read and interpret the 14 day distribution column in Center dashboard.
***
### Before You Begin
Make sure you have:
* Logged in with the appropriate role credentials (Center Admin, Center Manager, Proctor Lead, or Proctor) to reflect that other roles can also perform candidate actions.
***
### Step-by-Step Guide
**1. Locate the column**
The **14 day distribution** column appears in two places:
* On the **Center dashboard** - in the main centers list, showing the distribution for each center.
* On the **Center Overview** page - in the Rooms section, showing the distribution for each room. It also appears in the **Quick Statistics** panel on the right.
**2. Read the activity graph**
The column displays a small bar graph where each bar represents one day over the next 14 days, starting from today. The height of each bar indicates how many bookings are scheduled for that day - the taller the bar, the more bookings. A flat or dashed line means no bookings are scheduled for that day.
**3. Check the booking count**
A **number** is displayed at the right end of the graph. This shows the total booking count across the entire 14-day period. A count of "0" means no bookings are scheduled for the next 14 days.
**4. Interpret the color coding**
The bars use color to indicate utilization levels:
* **Grey bars** - normal booking levels with available capacity.
* **Red bars** - high utilization or at-capacity slots. Red indicates that the center or room is heavily booked on that day and may need attention for staffing or capacity adjustments.
**Additional Tips**
* Use the distribution column to quickly identify busy days across your centers without opening each one individually.
* The graph on the Quick Statistics panel in the Center Overview gives you a center-wide view, while the per-room graphs in the Rooms section help you identify which specific rooms are heavily booked.
# Understanding the Seat Allocation view
Source: https://docs.talview.com/center-and-proctor-administration/center-admin/how-tos/understanding-the-seat-allocation-view
The Seat Allocation view gives you a seat-level breakdown of a specific time slot. It shows the information you can expect to see for each seat, including which candidate is assigned, the seat's current status, and the proctor responsible, along with the actions available to you. In this article, you will learn what the Seat Allocation view displays and what you can do within it.
***
### Before You Begin
Make sure you have:
* Logged in with your Center Admin credentials.
* Opened a center and navigated to the **Capacity** tab.
***
### Step-by-Step Guide
**1. Open the Seat Allocation view**
From the **Capacity** tab, click on a slot's **time link** (e.g., "4 PM – 6 PM"). This opens the Seat Allocation view. The breadcrumb at the top confirms your navigation path.
**2. Identify the room and schedule**
Seats are grouped under a label showing the room name and session date (e.g., "LRW1 — Thursday, Jun 18, 2026"). This tells you which room the seats belong to and the date of the session. A **three-dot menu (⋯)** on the right provides additional actions for that room.
**3. Review seat details**
Each row represents an individual seat. The columns are:
* **Seat** - the seat identifier.
* **Candidate** - shows the assigned candidate's name and email with an avatar. If no candidate is assigned, this displays a dash (—).
* **Status** - the current state of the seat:
* **Available** (green) - the seat is open and can be assigned to a candidate.
* **Occupied** (grey) - a candidate is currently assigned to the seat.
* **Proctor** - the proctor assigned to the seat, shown as an avatar. Click the **✕** icon on the avatar to remove the proctor assigned.
Each row also has a **delete (trash) icon** on the far right to remove the seat from the slot.
**4. Add a room to the slot**
Click the **+ Add room** button at the top right to assign additional rooms to this time slot. A modal will open showing available rooms from your center plan. Select the rooms you want to add and confirm.
**5. Navigate between pages**
If there are more seats than the page can display, use the page controls at the bottom right to move between pages. You can adjust the **Rows per page** setting.
***
**Additional Tips**
* Proctors are assigned at the individual seat level. You can assign the same proctor to multiple seats or different proctors to different seats within the same room.
* Removing a seat from this view frees up that seat's capacity for the time slot.
* To go back to the Capacity tab, use the breadcrumb navigation at the top or click the **Capacity** tab.
# Cancelling a Schedule
Source: https://docs.talview.com/center-and-proctor-administration/center-federation/cancelling-a-schedule
Understand what happens to synced schedules and partner organization slots when you cancel a planning slot.
## Overview
When you cancel or remove a planning slot from your center, Center Sync removes the corresponding slot from connected partner organizations. This keeps both sides in sync and prevents partners from showing capacity that is no longer available at your center.
Before cancelling a slot, check with your partner organization. If candidates are already booked into that slot on their side, those bookings are **not** automatically cancelled. The partner organization must manage their own candidate communications and booking changes.
***
## How schedule cancellation works
When you cancel or delete a planning slot:
1. The slot is removed from your center's **Capacity** tab.
2. Center Sync detects the change and removes the corresponding slot from the partner organization.
3. The partner organization's capacity view no longer shows the cancelled slot.
4. Any candidate bookings that existed within the cancelled slot on the partner side remain in place — they are not automatically cancelled or notified.
***
## Steps to cancel a planning slot
Navigate to the center and click the **Capacity** tab to view all scheduled slots.
Find the slot you want to cancel. Use the date filters or search to narrow down the list if needed.
Click the **trash icon** on the right side of the slot row.
Confirm the action when prompted. The slot is removed from your center and the sync to partner organizations begins automatically.
***
## Cancelling a recurring schedule
If the slot is part of a recurring schedule, you will typically be asked whether you want to:
* **Cancel this occurrence only** — removes a single date from the schedule
* **Cancel this and all future occurrences** — ends the recurring schedule from that date forward
* **Cancel the entire schedule** — removes all past and future occurrences
The same scope of cancellation is reflected in the partner organization's copy of the schedule.
***
## Before you cancel: coordination checklist
Ask your partner organization to check whether any candidates are booked into the slot you are about to cancel. See [What is Not Synced](/center-and-proctor-administration/center-federation/what-is-not-synced) — candidate booking data is not visible in your organization's dashboard.
If bookings exist, work with the partner organization to notify affected candidates and offer rebooking options before you proceed with the cancellation.
Once both organizations are aligned, proceed with the cancellation. The slot is removed from the partner organization automatically.
***
## Frequently asked questions
No. Cancelling a planning slot on your side does not trigger automatic notifications to candidates booked on the partner side. The partner organization is responsible for communicating any schedule changes to their candidates.
Proctor assignments are not synced and are managed independently by each organization. Removing the slot from the partner's capacity view does not automatically unassign proctors. The partner team will need to manage their own assignments after the slot is removed.
Yes. You can create a new planning slot with the same configuration. The partner organization will receive a fresh copy of the slot when the sync runs.
Currently, the options are to keep the slot active (synced) or delete it (removed from partner). There is no "pause visibility" option for individual slots. If you need to restrict a slot temporarily, coordinate directly with your partner organization.
# Rooms & Seat Map
Source: https://docs.talview.com/center-and-proctor-administration/center-federation/managing-rooms-and-seats
Adding, editing, or removing rooms and seats in your center automatically updates the floor plan in connected partner organizations.
## Overview
The room and seat configuration of your center — often called the **floor plan** or **seat map** — is fully synced to partner organizations. When you add a new room, change its capacity, update seat identifiers, or remove a room, those changes flow to the partner side automatically.
This ensures that the partner organization always has an accurate picture of your center's physical layout and availability when planning candidate sessions.
***
## Room configuration that is synced
For each room in your center, the following details are mirrored:
| Field | Description |
| ----------------- | --------------------------------------------------------------------------------------- |
| **Room name** | The display name shown in the dashboard |
| **Workflow step** | Which exam step the room is assigned to (e.g. Listening, Reading & Writing or Speaking) |
| **Capacity** | The total number of seats in the room |
| **Status** | Whether the room is Active or Inactive |
| **Seats** | Individual seat identifiers within the room |
***
## Adding a room
Navigate to the center from the **Centers** list and open its **Overview** page.
In the **Rooms** section at the bottom of the overview, click **+ Add Room**.
Enter:
* **Room name** — the label that will appear in dashboards and session views
* **Workflow step** — select which exam step this room serves
* **Capacity** — the number of seats to initially allocate
Click **Confirm**. The new room and its seats appear immediately in your center, and a sync to partner organizations begins automatically.
***
## Editing a room
On the center **Overview** page, find the room in the **Rooms** list.
Click the room name to open its detail view, then click **Edit**.
You can change the room name, workflow step assignment, capacity, or status.
Click **Confirm**. Changes sync to partner organizations automatically.
Updating a room's capacity does not automatically change the number of seat records. If you increase capacity, add new seats manually. If you reduce capacity, remove the extra seats first before lowering the room capacity.
***
## Removing a room
On the center **Overview** page, find the room you want to remove.
Click the **trash icon** next to the room name.
Confirm the action when prompted. The room is removed from your center and the partner organization's copy is updated accordingly.
Removing a room from your center also removes it from partner organizations on the next sync. If candidates are booked in that room on the partner side, those bookings are **not** automatically cancelled or reassigned. Coordinate with your partner organization before removing rooms that have upcoming sessions.
***
## Seat management
Seats are the individual positions within a room. They carry an identifier (for example, `seat-1`, `seat-2`) and are synced along with the room they belong to.
| Action | Effect on partner organization |
| -------------------- | ----------------------------------------------- |
| Add seat | New seat appears in the partner's room |
| Edit seat identifier | Updated identifier reflects on the partner side |
| Remove seat | Seat is removed from the partner's room |
For how-to instructions on managing seats, see:
* [How to add seats to a room](/center-and-proctor-administration/center-admin/how-tos/how-to-add-seats-to-a-room)
* [How to edit seats in a room](/center-and-proctor-administration/center-admin/how-tos/how-to-edit-seats-in-a-room)
* [How to delete seats in a room](/center-and-proctor-administration/center-admin/how-tos/how-to-delete-seats-in-a-room)
***
## Room map view
The **Room map** button on the center overview opens a visual floor plan of your rooms and seats. This view is also available to partner organizations and reflects your current configuration.
***
## Frequently asked questions
Yes. The room name is a synced attribute. The partner organization sees the updated name after the next sync.
No. Room configuration is managed exclusively by your organization (the source). The partner organization's copy reflects only what you have configured. Any local additions on the partner side may be overwritten on the next sync cycle.
The workflow step change is synced as a configuration update. Existing scheduled slots in the partner organization are not automatically cancelled. Review upcoming capacity slots in coordination with your partner if a workflow step reassignment would affect scheduling.
When you save a room change, your center's status briefly shows **Syncing**. Once it returns to **Active** (or its previous status), the sync is complete and the partner organization's copy has been updated.
# Center Sync — Overview
Source: https://docs.talview.com/center-and-proctor-administration/center-federation/overview
Understand how center configuration is automatically kept in sync across connected organizations.
## What is Center Sync?
When your organization shares exam center infrastructure with a partner organization, **Center Sync** keeps both sides aligned automatically. Any time you update your center's details, rooms, schedules, or forms, those changes are mirrored to the partner organization — without any manual export or re-configuration on their end.
Center Sync requires that a federation relationship has already been configured between your organization and the partner organization by your platform administrator. This guide assumes that setup is complete.
***
## How it works
Your organization is the **source** — you own and manage the center. When you make a change (publish a center, edit details, add a room, modify a schedule), the platform detects that change and automatically pushes an updated copy of your center's configuration to the partner organization.
The partner organization receives a **synchronized copy** of your center. They can view and reference it, but your organization remains the authoritative owner. Any updates you make flow to them; changes made locally in the partner organization are overwritten on the next sync.
Think of Center Sync like a shared document: you control the original, and your partner always sees the latest version you've saved.
***
## What is synced
When Center Sync runs, the following configuration is mirrored to the partner organization:
| What | Details |
| --------------------- | ------------------------------------------------------------------- |
| **Center details** | Name, location, operating hours, time zone, exam type, contact info |
| **Rooms** | Room names, workflow steps, capacity, status |
| **Seats** | Individual seat definitions within each room |
| **Schedules** | Planning schedules and recurring availability |
| **Capacity slots** | Drive occurrences and slot-level capacity |
| **Workflows & steps** | Exam workflow structure attached to the center |
| **Forms** | Forms and their fields associated with workflow steps |
| **Accommodations** | Workflow step accommodations |
***
## What is NOT synced
Some operational data is intentionally **not** copied to the partner organization:
| What | Why |
| ----------------------------- | ------------------------------------------------------------ |
| **Proctor assignments** | Each organization manages their own proctor staff |
| **Lead proctor assignments** | Each organization manages their own team |
| **Candidate bookings** | Bookings belong to the tenant where the candidate registered |
| **Check-in and session data** | Session records stay with the organization running the exam |
See [What is Not Synced](/center-and-proctor-administration/center-federation/what-is-not-synced) for the full explanation.
***
## Sync trigger
Center Sync is **automatic** — it runs whenever a change is detected on your center. You do not need to press a sync button or schedule a job. The platform monitors your center for updates and triggers a sync in the background.
During a sync, your center's status briefly shows **Syncing**. Edits to the center are temporarily paused while the sync completes to keep both sides consistent.
***
## Pages in this section
What happens when you publish a center for the first time
How changes to center details sync to partner organizations
How room additions, edits, and removals are reflected
How planning slots and schedules are mirrored
What happens to synced schedules when you cancel
How seat allocation changes flow to partner organizations
Proctor assignments, bookings, and session data
# Publishing a New Center
Source: https://docs.talview.com/center-and-proctor-administration/center-federation/publishing-a-new-center
When you create and activate a new center, it is automatically synced to connected partner organizations.
## What happens when you publish a new center
Creating a center in your organization is the starting point for Center Sync. Once your center is set up and active, the platform automatically establishes a synchronized copy in every connected partner organization. Your partner does not need to create anything manually — the center, its rooms, seats, schedules, and workflows all appear on their side automatically.
***
## Steps to publish a new center
From the **In-Center dashboard**, click **Add Center** in the top-right corner and complete the setup form. This includes entering the center name, location, time zone, exam type, operating hours, and contact details.
For a full walkthrough, see [How to add a new center](/center-and-proctor-administration/center-admin/how-tos/how-to-add-a-new-center).
During creation, you will be asked to select one or more **workflow templates** (exam types) to attach to the center. These define the exam steps, schedules, and room assignments that will be available.
After the center is created, add your rooms and configure seats within each room. The room name, workflow step association, and seat capacity are all included in the sync payload.
See [Rooms & Seat Map](/center-and-proctor-administration/center-federation/managing-rooms-and-seats) for details.
Set the center status to **Active**. This is the trigger that makes the center visible to partner organizations through Center Sync.
A center must be **Active** to be synced. Inactive centers remain private to your organization.
***
## What the partner organization sees
Once the sync completes, the partner organization will see a copy of your center in their dashboard. This includes:
* **Center name, code, and location** — exactly as you configured them
* **Operating hours and time zone** — carried across unchanged
* **Exam type** (CBT / PBT) — reflected on the partner side
* **Rooms** — all rooms you added, with their names and capacities
* **Seats** — individual seat identifiers within each room
* **Schedules and planning slots** — any recurring slots you have created
* **Workflows and form configurations** — the exam structure attached to the center
***
## Status during sync
While the initial sync is running, you will see your center status temporarily change to **Syncing**. During this window:
* The center is visible and operational for your organization
* Edits to the center configuration are temporarily paused
* The status returns to **Active** (or whatever status you set) once the sync completes
This typically takes a few seconds. If the status remains on **Syncing** for an extended period, contact your platform administrator.
***
## Frequently asked questions
No. The sync is fully automatic. As soon as your center is active and a federation relationship exists, the partner organization's copy is created without any action on their side.
The partner organization can view the center and use it for their operations (such as assigning their own proctors to sessions). However, configuration changes — such as editing center details, rooms, or schedules — are controlled exclusively by your organization. Any local edits made by the partner may be overwritten when the next sync runs.
The platform uses internal identifiers and a matching process to link centers. If a center with matching attributes already exists on the partner side, it is adopted as the synced copy rather than duplicated. Your platform administrator can resolve any ambiguous matches if needed.
Yes. If your organization has federation relationships with multiple partners, a synced copy is created for each of them.
# Schedules & Capacity Planning
Source: https://docs.talview.com/center-and-proctor-administration/center-federation/schedules-and-capacity-planning
Planning slots and recurring schedules created in your center are automatically mirrored to connected partner organizations.
## Overview
When you create a **planning slot** (a scheduled exam session window), Center Sync automatically creates a matching slot in every connected partner organization. This allows the partner to see your center's capacity calendar, understand room availability, and plan candidate bookings accordingly.
Partner organizations see your schedules in their **Capacity** tab, labeled with the originating source information.
***
## What schedule data is synced
| Element | Synced to partner organization |
| --------------------------- | -------------------------------------------------------- |
| **Schedule name** | Displayed in the partner's capacity view |
| **Workflow step** | Which exam step the slot applies to (e.g. LRW, Speaking) |
| **Slot date and time** | Start and end times for each occurrence |
| **Exam type** | CBT or PBT |
| **Rooms assigned** | Which rooms are allocated to the slot |
| **Total capacity** | Aggregate seat count across assigned rooms |
| **Recurring schedule rule** | Frequency and end date for recurring slots |
| **Schedule overrides** | One-off changes to a recurring schedule |
***
## Creating a planning slot
Navigate to the center from the **Centers** list and click the **Capacity** tab.
Click the **+ Planning** button in the top-right area of the Capacity tab.
Configure the slot:
* **Schedule name** — a descriptive name (for example, "LRW Schedule - 2026-05-23")
* **Workflow step** — select the relevant exam step
* **Start date and start time** — when the slot begins
* **End time** — when the slot ends
* **Recurring days of the week** — select which days this slot repeats
* **Until date** — when the recurrence ends
Click **Save**. The slot is created in your center and immediately queued for sync to partner organizations.
For step-by-step instructions, also see [How to create a planning slot](/center-and-proctor-administration/center-admin/how-tos/how-to-create-a-planning-slot).
***
## How synced slots appear in the partner organization
In the partner organization's **Capacity** tab, synced slots are displayed identically to locally created slots. The schedule name you assigned (for example, "OET Sydney Test Centre - LRW Schedule - 2026-05-23") is visible as the slot group header, making it easy for the partner team to identify which slots originated from your center.
Each synced slot shows:
* **Date and time range**
* **Exam type**
* **Workflow step**
* **Number of rooms**
* **Total capacity** (seats)
* **Bookings** (lobby count and checked-in count — partner-side data, not synced from your organization)
The **Bookings** column in the partner organization's capacity view reflects their own candidate registrations. Your organization's booking data is never synced to the partner. See [What is Not Synced](/center-and-proctor-administration/center-federation/what-is-not-synced).
***
## Recurring schedules
Recurring planning slots work the same way as single slots. The recurrence rule is synced, meaning the partner organization sees all future occurrences — not just the first one.
If you modify the recurring rule (for example, changing the end date or adding a day of the week), the change is synced and the partner organization's schedule is updated accordingly.
***
## Schedule overrides
A **schedule override** lets you adjust a single occurrence within a recurring schedule (for example, moving a slot to a different time on a specific date, or blocking a specific date). Overrides are synced to the partner organization as part of the schedule configuration.
***
## Frequently asked questions
Yes. The total capacity (based on the rooms assigned to the slot) is synced. The partner sees the same seat count and room allocation.
No. Planning slots for synced centers are managed exclusively by your organization. The partner organization's view is read-only for configuration purposes. They can view capacity and manage their own candidate bookings within those slots.
The slot time change is synced as a configuration update. Existing candidate bookings in the partner organization are not automatically moved or cancelled. Coordinate with the partner organization before changing slot times when candidates are already registered.
No. You create the slot once in your organization. Center Sync distributes it to all connected partner organizations automatically.
There is no limit enforced by Center Sync. Practical limits depend on your center's room and seat capacity.
# Slot Capacity Updates
Source: https://docs.talview.com/center-and-proctor-administration/center-federation/slot-capacity-updates
Changes to room and seat allocations within a capacity slot are synced to partner organizations, keeping available capacity accurate on both sides.
## Overview
Each planning slot in your center is backed by a **seat allocation** — the specific rooms and seats assigned to that time window. When you add rooms to a slot, remove rooms, or adjust which seats are included, those changes sync to your partner organizations so their capacity view stays accurate.
***
## What slot capacity data is synced
| Element | Description |
| --------------------- | -------------------------------------------------------- |
| **Rooms in the slot** | Which rooms are assigned to a specific occurrence |
| **Total capacity** | Aggregate seat count across all rooms in the slot |
| **Individual seats** | Seat identifiers available within each room for the slot |
| **Seat status** | Whether a seat is active and available for assignment |
**Candidate and proctor assignments are not synced.** The "Candidate" and "Proctor" columns in your seat allocation view show data specific to your organization. The partner organization manages their own assignments independently. See [What is Not Synced](/center-and-proctor-administration/center-federation/what-is-not-synced).
***
## Adding a room to a slot
If you need to expand capacity for a specific slot occurrence, you can add an additional room to it:
From the **Capacity** tab, click on the slot time (for example, "10 AM – 12 PM") to open the seat allocation view for that occurrence.
Click the **+ Add room** button in the top-right corner of the seat allocation view.
Choose the room to add to this slot. Only rooms configured in the center and assigned to the relevant workflow step are available.
Click **Confirm**. The room and its seats are added to the slot. The updated capacity is synced to partner organizations automatically.
***
## Removing a room from a slot
From the **Capacity** tab, click on the slot time to open the seat allocation view.
Click the **trash icon** next to the room row header (for example, "LRW Room — Friday, May 1, 2026") to remove that room from this occurrence.
Confirm the action. The room is removed from the slot and the partner organization's capacity for that slot is updated accordingly.
Removing a room from a slot reduces the total capacity visible to the partner organization. If the partner has already assigned candidates to seats in that room, those assignments are not automatically cleared. Coordinate with your partner before reducing slot capacity when bookings exist.
***
## Managing individual seats within a slot
From the seat allocation view, you can:
* **View all seats** — see each seat identifier, its status (Available, Occupied), and any assigned candidate or proctor in your organization
* **Remove a seat** — click the trash icon next to a seat to remove it from the slot for this occurrence
* **Add a seat** — capacity is determined by the room's configured seats; add seats to the room (see [Rooms & Seat Map](/center-and-proctor-administration/center-federation/managing-rooms-and-seats)) to make them available in slots
Seat-level changes sync to the partner organization as part of the slot's configuration.
***
## Effect on partner organization's capacity view
After a slot capacity update, the partner organization's **Capacity** tab reflects:
| Your action | Partner organization sees |
| ------------------------- | ----------------------------------------- |
| Add a room to a slot | Room added; total capacity increases |
| Remove a room from a slot | Room removed; total capacity decreases |
| Add seats to a room | More seats available in that room's slot |
| Remove seats from a room | Fewer seats available in that room's slot |
***
## Frequently asked questions
Yes. Once the sync completes (typically within seconds), the additional room and its seats appear as available in the partner organization's seat allocation view, and candidates can be booked into them.
Reducing capacity (removing rooms or seats) does not automatically cancel bookings. Bookings that existed before the reduction remain assigned. Consult with the partner organization to manage any over-allocation if needed.
Yes. You can open any individual occurrence (by clicking its time in the Capacity tab) and add or remove rooms just for that date, without affecting other occurrences in the series.
The capacity columns in both organizations should match after a completed sync. If there is a discrepancy, wait a few seconds for the sync to complete. If the mismatch persists, contact your platform administrator.
# Updating Center Attributes
Source: https://docs.talview.com/center-and-proctor-administration/center-federation/updating-center-attributes
Changes to center details — name, location, operating hours, contact info, and more — are automatically synced to partner organizations.
## What are center attributes?
Center attributes are the core details that describe your exam center:
* **Center name and code**
* **Location** (address and map link)
* **Exam type** (CBT, PBT, or both)
* **Operating hours** (days and times the center is open)
* **Time zone**
* **Contact name, phone, and email**
* **Accommodations** (accessibility options)
Any time you update these details in your organization, Center Sync automatically pushes the updated information to your partner organizations.
***
## How to update center details
From the **Centers** list, click the center you want to update to open its **Overview** page.
In the center information panel, click the **Edit Details** button (pencil icon).
Update any combination of:
* Center name or center code
* Location (update the address or Google Maps link)
* Exam type
* Operating hours (toggle days, adjust time ranges)
* Contact name, phone, or email
* Accommodations
For time zone updates, use the edit icon next to the **Time Zone** field directly on the Overview page.
Click **Confirm** to save your changes. The sync to partner organizations begins automatically.
***
## What the partner organization sees
Once the sync completes, the partner organization's copy of the center reflects your updated details. This includes:
| Field updated | What changes in the partner organization |
| --------------- | ------------------------------------------------ |
| Center name | Displayed name updates everywhere it appears |
| Location | Map link and address update |
| Operating hours | Hours reflect the updated schedule |
| Time zone | Sessions and slots are displayed in the new zone |
| Contact details | Contact name, phone, and email update |
| Exam type | CBT / PBT indicator updates |
| Accommodations | Available accommodations list updates |
If you are making several changes at once, save them all together. Each save triggers one sync — batching updates is more efficient and reduces the brief **Syncing** window that partners see.
***
## Center status during sync
When you save changes, your center status temporarily changes to **Syncing**. During this time:
* The center remains fully operational for your organization
* Edits to the center are temporarily paused to maintain consistency with the partner side
* Normal status resumes automatically once the sync completes (typically within seconds)
If you attempt to edit the center while it is in the **Syncing** state, the platform will show a message indicating that edits are temporarily unavailable. Wait for the sync to complete before making further changes.
***
## Frequently asked questions
Changes are usually reflected in the partner organization within a few seconds of saving. If a sync is already in progress (for example, because another change was saved just before), it will complete the current run and pick up your new changes in the next cycle.
Yes. The sync uses internal identifiers, not the center name, to match records. Renaming your center updates the name on the partner side — it does not create a second copy or break any existing mappings.
The change is synced immediately. The partner organization's copy will show the updated exam type. Any existing slots or schedules that were tied to the previous exam type remain; consult your platform administrator if a structural change to schedules is needed.
Operating hours are configuration data — syncing them updates the displayed hours but does not automatically cancel or reschedule existing candidate bookings. Booking management remains with each organization.
# What is Not Synced
Source: https://docs.talview.com/center-and-proctor-administration/center-federation/what-is-not-synced
Some operational data intentionally stays within each organization. Understand what Center Sync does not share between connected organizations.
## Overview
Center Sync is designed to mirror **configuration** — the structural definition of a center (its details, rooms, seats, schedules, and workflows). It does not replicate **operational data** — the day-to-day records that belong to each organization's specific exam operations.
The following information is **never** synced between organizations:
***
## Proctor and Lead assignments
Proctor and lead proctor assignments are **not** synced.
Each organization manages its own proctoring staff independently. Your organization's proctor roster is not visible to the partner organization, and vice versa. When the partner organization opens a planning slot, they assign their own team members to it.
This means:
* **Your proctor assignments** — visible only in your organization's capacity view
* **Partner proctor assignments** — visible only in the partner organization's view
* **No crossover** — neither side can see the other's staff assignments through the center interface
If you need to coordinate proctor availability or coverage between organizations, use your existing communication channels outside of the platform.
***
## Candidate booking data
Candidate bookings are **not** synced.
When a candidate registers for an exam at a federated center, the booking record is created in the organization that manages the exam registration — not mirrored to other organizations. Each organization's **candidate list** reflects only the candidates registered through their own workflows.
This means:
* **Your candidate list** — shows only candidates registered through your organization
* **Partner candidate list** — shows only candidates registered through the partner organization
* **No shared view** — you cannot see partner-side bookings from your center dashboard, and they cannot see yours
***
## Session and check-in data
Session records, check-in status, candidate room assignments, and proctor activity logs are **not** synced.
These records are produced at the time of the exam session and belong entirely to the organization running that session. They are not copied or visible to connected organizations.
***
## Exam scores and results
Assessment outcomes, scores, and result attributes are **not** synced through Center Sync.
Each organization retains the results for the candidates it examined. Any cross-organization result sharing is handled through separate integration flows, not through Center Sync.
***
## Where to view this information
Even though booking and session data is not visible in the center dashboard of the other organization, **the same operational information is accessible through the Exam module**.
| Data type | Where to find it |
| ------------------- | ------------------------------------------------------------ |
| Candidate bookings | **Coordinator → Exam module** for the relevant tenant |
| Proctor assignments | **Capacity → Slot view** within each organization |
| Session records | **Session history** in the organization that ran the session |
| Check-in data | **In-Center dashboard → Candidate tab** in the relevant org |
If you are a coordinator who needs visibility into both organizations' operational data, your platform administrator can grant you access to the **Exam module** on both tenants. This provides a consolidated view of exam logistics without requiring data to be copied between organizations.
***
## Summary table
| Data | Synced? | Managed by |
| ---------------------------- | ------- | --------------------------------------- |
| Center name and details | ✅ Yes | Source organization |
| Rooms and seats | ✅ Yes | Source organization |
| Schedules and planning slots | ✅ Yes | Source organization |
| Workflows and forms | ✅ Yes | Source organization |
| Proctor assignments | ❌ No | Each organization independently |
| Lead proctor assignments | ❌ No | Each organization independently |
| Candidate bookings | ❌ No | Organization where candidate registered |
| Check-in and session data | ❌ No | Organization running the session |
| Exam results and scores | ❌ No | Organization running the session |
***
## Frequently asked questions
Candidate bookings are created and managed by the organization responsible for exam registration. Duplicating booking records across organizations would create conflicting versions of the truth — for example, if a candidate is rebooked or cancelled on one side, the other side's copy would become stale. Keeping bookings within the registering organization avoids this problem and keeps each organization's records authoritative.
Visibility into partner-side bookings is available through the **Exam module** on the coordinator tenant, where cross-organization exam logistics are managed. Your platform administrator can configure the appropriate access. Contact your administrator if you need this view.
Not through Center Sync. Each organization manages its own user directory and proctor assignments separately. Cross-organization staff management requires a separate configuration or user access setup by your platform administrator.
The **Exam module** in the coordinator tenant provides a combined view of scheduling and capacity across connected organizations. Speak with your platform administrator about granting the appropriate access to the relevant team members.
# Getting Started - Center and Proctor Management
Source: https://docs.talview.com/center-and-proctor-administration/center-getting-started
***
Guides for center administrators and proctoring administrators to get the most out of Talview. Here you’ll find curated instructions, walkthroughs, and best practices tailored to your role and needs.
Learn how to setup and manage your exam centers
Learn how to manage bookings and schedule for each center
Learn how to manage your schedules, room assignments and exam protocols
Sign up, log in, and access your account using your organization's configured login method.
# Center Manager Or Proctor Lead FAQs
Source: https://docs.talview.com/center-and-proctor-administration/center-manager-or-proctor-lead/faqs/center-manager-or-proctor-lead-faqs
The Center Manager / Proctor Lead role gives you visibility across the centers and proctors you oversee. You can monitor schedules, review candidate progress, and track proctor activity - but your access is read-only access, meaning you can't make edits or changes directly.
This FAQ serves as a quick reference to help you navigate the platform and understand what you can see and do in your role.
***
### Getting Started
**Q1. What can I do as a Center Manager / Proctor Lead on Talview?**
You can view the centers and proctors assigned to you, monitor schedules, and track candidate progress in real time. You have read-only access. If something needs to be updated, your Center Admin can action it on your behalf.
**Q2. Where do I start once I log in?**
Once you log in, you'll land on your dashboard where you can see the centers you have access to. Navigate to the relevant center to view its schedules, proctor details, and candidate activity.
**Q3. Can I use Talview on a mobile device or browser?**
Yes. Talview is accessible via a web browser. For the best experience, use a supported browser on a desktop or laptop.
**Q4. Who should I contact if I need something changed?**
Since you have read-only access, any changes — to center settings, proctor assignments, bookings, or candidate data — need to be made by a Center Admin. Reach out to your Center Admin directly to action any updates.
**Q5. I'm having trouble logging in. What should I do?**
Check that you're using the correct login credentials for your organization. If the issue persists, contact your Center Admin or your organization's IT support for assistance.
***
### Centers
**Q1. Can I view the centers assigned to me?**
Yes. You can view all centers assigned to you, including their details such as operating hours, room configuration, schedules, bookings, and candidate information.
**Q2. Can I edit a center's settings, such as operating hours or room configuration?**
No. You have read-only access only. Editing center settings is restricted to the Center Admin role. If a change is needed, contact your Center Admin.
**Q3. Can I view how many rooms and seats are available at a center?**
Yes. You can view the room and seat configuration for each center you have access to. This helps you get a sense of the center's capacity at any given time.
**Q4. Can I view the capacity details for a center?**
Yes. You can view capacity information such as available seats and room assignments across schedules. You can't modify these details, but you can use this information to stay informed about center utilization.
**Q5. I can see a center but some details look incorrect. What should I do?**
Since you have read-only access, you can't correct the details yourself. Flag the issue with your Center Admin so they can review and make the necessary corrections.
**Q6. Can I view multiple centers at the same time?**
You can view all centers assigned to you, but you'll need to navigate to each center individually to see its specific details, schedules, and candidate information.
***
### Proctors
**Q1. Can I view the proctors assigned to my centers?**
Yes. You can view the list of proctors associated with the centers you have access to, along with their profile details and assigned schedules.
**Q2. Can I assign or reassign proctors to a schedule?**
No. You have read-only access only. Assigning or reassigning proctors is an admin-level action. Contact your Center Admin if changes are needed.
**Q3. Can I add a new proctor to the platform?**
No. Adding new users to the platform is outside the scope of your role. Your Center Admin manages user access and onboarding.
**Q4. Can I view which proctor is assigned to a specific schedule?**
Yes. You can view proctor assignments within schedules to understand who is managing each session at your centers.
**Q5. A proctor's details appear to be incorrect or outdated. What should I do?**
Since you have read-only access, you can't update proctor details yourself. Raise it with your Center Admin so they can review and correct the information.
**Q6. Can I remove a proctor from a center?**
No. Managing proctor assignments is restricted to the Center Admin role. Contact your Center Admin to action any changes.
***
### Schedules
**Q1. Can I view schedules for my centers?**
Yes. You can view offline schedules for all centers you have access to, including booking details, assigned proctors, and candidate information.
**Q2. Can I create, edit, or cancel a booking?**
No. You have read-only access only. Any changes to bookings need to be made by a Proctor or Center Admin with the appropriate permissions.
**Q3. Can I view candidate details within a schedule?**
Yes. You can view candidate information such as their status, assigned room and seat, accommodations, and exam progress — but you can't update or change any of this information.
**Q4. Can I see completed schedules?**
Yes. You can view past schedules to monitor historical activity across your centers. This can be useful for reviewing how sessions ran and tracking overall center performance.
**Q5. Can I view the candidate list for an upcoming schedule before it starts?**
Yes. You can view the candidate list for any schedule you have access to, including upcoming ones. This helps you stay informed ahead of exam day.
**Q6. What information is shown for each schedule?**
Each schedule shows the date, slot name, time, room, assigned proctor, and total seat count. Within a schedule, you can also see individual candidate details such as their status, seat assignment, and exam name.
**Q7. Can I download or export schedule data?**
Export functionality is not part of the Center Manager / Proctor Lead role. If you need a report or export, speak to your Center Admin.
# Proctor FAQs
Source: https://docs.talview.com/center-and-proctor-administration/proctor/faqs/proctor-faqs
The Proctor workflow covers the day-to-day management of in-center exam schedules, from viewing your upcoming schedules and starting a session, to checking in candidates, monitoring their progress, and taking action when needed.
This FAQ serves as a quick reference to help you navigate your schedule view and manage candidates efficiently during a live exam.
***
### Getting Started
**Q1. Where can I see my upcoming schedules?**
Log in to Talview and navigate to **Bookings**. Your assigned schedules are listed here, showing the date, time, room, and seat count for each slot.
**Q2. How do I search for a specific schedule slot?**
Use the **Search slots** bar at the top right of the Bookings page to look up a slot by name or date.
**Q3. How do I start a schedule?**
Find the schedule you want to start and click **Start Schedule**. This takes you to the candidate list for that slot.
**Q4. Can I see schedules that have already been completed?**
Yes. Select the **Completed** tab on the Bookings page to view your past schedules.
**Q5. What information is shown for each schedule on the Bookings page?**
Each schedule card shows the date, slot name, time, room, and total seat count.
**Q6. What does "Up Next" mean on the Bookings page?**
"Up Next" lists your upcoming schedules that are not yet ready to start. The schedule at the top of the page with the **Start Schedule** button is your most immediately active one.
***
### Candidate Statuses & Progress
**Q1. What are the different candidate statuses I'll see in the schedule view?**
You'll see the following statuses: Checked-in, Paused, Lobby, Exam in Progress, and Suspended.
**Q2. What does "Lobby" mean for a candidate?**
The candidate hasn't been checked in yet and is waiting to begin their exam.
**Q3. What is the difference between "Paused" and "Suspended"?**
"Paused" means the candidate has temporarily stopped their exam — either on a permitted break or due to a technical interruption. "Suspended" means a proctor has actively halted the session, typically due to a violation or integrity concern.
**Q4. What does "Disconnected" mean?**
The candidate has lost their connection and may reconnect. This is a technical state, not a deliberate action taken by the proctoring team.
**Q5. What does the progress bar show for a candidate?**
The progress bar reflects how far along the candidate is in their exam. It updates in real time as they move through each stage.
**Q6. What does the Step column indicate?**
The Step column shows the current status of the candidate's exam through an icon.
**Q7. What do the icons below a candidate's name in the schedule view indicate?**
The icons represent the accommodations available or active for that candidate's session - such as breaks in between the session, extra time, or special assistance requirements like wheelchair access, etc.
***
### Candidate Actions
**Q1. How do I check in a candidate?**
Locate the candidate in the list, click the menu at the end of their row, and select **Check-in**.
**Q2. How do I view a candidate's profile?**
You can view a candidate's profile in two ways, click directly on the candidate's name, or click the menu at the end of their row and select **View profile**.
**Q3. How do I update a candidate's status?**
Click the menu at the end of the candidate's row, select **Update status**, and choose the appropriate status from the options available.
**Q4. How do I report an incident for a candidate?**
Click the menu at the end of the candidate's row and select **Report incident**. Fill in the required details and confirm.
**Q5. How do I suspend a candidate?**
Click the menu at the end of the candidate's row and select **Suspend candidate**. You'll be prompted to select a reason before confirming.
***
### Seat & Exam Details
**Q1. What does the Seat column show?**
The Seat column displays the room number and seat number assigned to each candidate - for example, Room 101, Seat 12A.
**Q2. What does the Exam column show?**
The Exam column displays the name of the exam the candidate is taking and the institution associated with it.
**Q3. Can two candidates in the same schedule be taking different exams?**
Talview doesn't restrict multiple exams from running in the same schedule slot. However, centers can manage this by creating separate schedules for each exam.
***
### Search & Navigation
**Q1. Can I search for a candidate within a schedule?**
Yes. Use the **Search** bar at the top of the schedule view to look up a candidate by name or ID.
**Q2. How do I go back to the Bookings page from the schedule view?**
Click **Bookings** in the breadcrumb at the top left of the page to return to your schedule list.
**Q3. How do I navigate between pages in the candidate list?**
Use the pagination controls at the bottom of the list. You can also adjust the number of rows displayed per page using the **Rows per page** dropdown.
# How to access a candidate's profile
Source: https://docs.talview.com/center-and-proctor-administration/proctor/how-tos/how-to-access-a-candidates-profile
During a session, proctors may need to review a candidate’s details such as their check-in information, exam details, and any reported incidents. The **Candidate Management** view allows you to quickly access a candidate’s profile directly from the candidate list.
***
### Viewing a Candidate’s Profile
You can open a candidate’s profile in two ways:
**Method 1: Clicking the Candidate Name**
1. Start the scheduled session from the **Bookings** page.
2. In the **Candidate Management** view, locate the candidate in the list.
3. Click on the **candidate’s name**.
4. The **candidate profile panel** will open, displaying detailed information.
**Method 2: Using the Menu**
1. Locate the candidate in the **Candidate Management** list.
2. Click the **menu** next to the candidate’s name.
3. Select **View profile**.
The candidate’s profile will open in a side panel.
***
### **Candidate Profile Overview**
The candidate profile provides important session-related details, including:
**Candidate Information**
* Candidate name
* Email address
* Candidate ID
**Check-In Details**
* Time when the candidate was checked in
* The proctor who performed the check-in
**Exam Details**
* Exam name
* Scheduled date
* Session time
* Assigned room and seat
**Reported Incidents**
* Any incidents reported during the session
* If no issues have been reported, the profile will display **No incidents reported**
**Face Authentication**
* Face authentication data will be visible to confirm identity of the candidate
**Viewing a candidate’s profile helps proctors,**
* Verify **candidate and exam details**
* Confirm **check-in information**
* Review any **reported incidents during the session**
* Quickly access important session data without leaving the dashboard
The profile panel allows you to monitor candidate information efficiently while managing the session.
# How to check-in a candidate
Source: https://docs.talview.com/center-and-proctor-administration/proctor/how-tos/how-to-check-in-a-candidate
Once a session has started, proctors can manage candidates from the **Candidate Management** view. One of the key actions available is **checking in a candidate**, which confirms that the candidate has arrived and is ready to begin the exam process.
***
### Navigating to Check-In
1. Navigate to the **Bookings** page.
2. Locate the scheduled session and click **Start Session**.
3. You will be directed to the **Candidate Management** view for that session.
4. Find the candidate in the **Candidate list**.
5. Click the **menu (three-dot icon)** next to the candidate’s name.
6. Select **Check-in** from the available options.
Once the action is completed, the candidate’s **Status** will update to **Checked-in**.
***
### Verifying the Check-In Status
After checking in a candidate, you can confirm the update in the candidate list:
* The **Status** column will display **Checked-in**.
* The **Step** indicator will reflect the candidate’s current stage in the process.
* The **Progress** bar will show the candidate’s exam progression once the test begins.
**Best Practices**
* Confirm the **candidate’s identity** before performing the check-in.
* Verify the **seat assignment and exam details** shown in the dashboard.
* Ensure the candidate is **physically present and ready** before completing the check-in.
# How to report an incident
Source: https://docs.talview.com/center-and-proctor-administration/proctor/how-tos/how-to-report-an-incident
During a session, proctors may need to document any irregularities, rule violations, or technical issues. The updated **Report Incident** flow allows you to capture structured and detailed information for accurate review and record-keeping.
***
### Reporting an Incident
1. Navigate to the **Bookings** page and start the scheduled session.
2. In the **Candidate Management** view, locate the candidate involved.
3. Click the **menu (three-dot icon)** next to the candidate’s name.
4. Select **Report Incident**.
This will open the **Report Incident panel**.
***
### Filling Out the Incident Report
The report consists of the following required fields:
**1. Nature of Incident**
* Select the **type of incident** from the dropdown.
* This helps categorize the issue for easier tracking and review.
**2. Incident Description**
* Provide a **detailed description** of the incident.
* Include:
* **Time of occurrence** (in **hh:mm** format)
* **Relevant test section or context** (if applicable)
* Example: *Reading Part A (10:05) – Candidate was seen using unauthorized notes.*
**3. Action Taken**
* Clearly mention the **steps you took** in response to the incident.
* Example actions may include:
* Warning the candidate
* Pausing the exam
* Informing the venue manager
* Confiscating unauthorized materials
***
### Submitting the Report
1. After filling in all required fields, click **Submit incident**.
2. The incident will be **logged and linked to the candidate’s session**.
***
### After Reporting an Incident
* The incident becomes part of the candidate’s **session record**.
* It can be reviewed later by **administrators or monitoring teams**.
* It will also be visible in the **candidate’s profile under reported incidents**.
***
**Best Practices**
* Report incidents **immediately after they occur**.
* Ensure descriptions are **clear, factual, and time-stamped**.
* Always include the **action taken** to provide full context.
* Avoid vague statements, be as specific as possible.
# How to search for a scheduled slot
Source: https://docs.talview.com/center-and-proctor-administration/proctor/how-tos/how-to-search-for-a-scheduled-slot
The **Bookings** page includes a search feature that allows proctors to quickly locate a specific schedule slot without manually browsing through the list of sessions. In this article, you will learn how to use the search feature to find a specific schedule slot in the Bookings page.
***
### Searching for a Schedule Slot
1. Navigate to the **Bookings** page.
2. Locate the **Search slots** field at the top right of the **Sessions** section.
3. Click inside the search bar.
4. Enter the **session name or relevant keyword** related to the schedule you want to find.
5. The list of sessions will automatically update to display **matching schedule slots**.
***
### Viewing the Search Results
Once you enter a keyword:
* Only the **sessions that match your search** will appear in the results.
* Each result will display the session details, including:
* **Session name**
* **Date**
* **Session timing**
* **Room information**
* **Seat capacity**
This allows you to quickly identify and access the correct schedule slot.
**When to Use the Search Feature**
The search function is helpful when:
* You have **multiple scheduled sessions** and need to locate one quickly.
* You want to find a **specific session by name**.
* You want to avoid scrolling through a long list of schedules.
Using the search option helps you efficiently locate the required schedule slot and proceed with managing or starting the session.
# How to start a scheduled session
Source: https://docs.talview.com/center-and-proctor-administration/proctor/how-tos/how-to-start-a-scheduled-session
Proctors can start a scheduled session directly from the **Bookings** page. Once a session is ready to begin, you can launch it from the session card and proceed to manage the candidates assigned to that schedule.
***
### Starting a Scheduled Session
1. Navigate to the **Bookings** page after logging in.
2. In the **Sessions** tab, locate the session that is ready to begin.
3. Review the session details such as **date**, **time**, and **assigned room** to ensure you are starting the correct schedule.
4. Click the **Start Session** button on the session card.
Once the session is started, you will be redirected to the **candidate management view** for that schedule.
***
### What Happens After Starting the Session
After the session starts, you will be able to:
* View the **list of candidates assigned to the session**
* Monitor each candidate’s **status and progress**
* Perform actions such as **check-in, profile view, incident reporting, and status updates**
* Track **seat assignments and exam details**
**Best Practices Before Starting a Session**
Before starting the schedule, ensure that:
* The **session start time has arrived**
* The **correct room and setup are ready**
* You are starting the **intended session** from your schedule list
Starting the session at the correct time ensures that candidate monitoring and check-in can begin smoothly.
# How to suspend a candidate
Source: https://docs.talview.com/center-and-proctor-administration/proctor/how-tos/how-to-suspend-a-candidate
During a session, if a candidate violates exam rules or engages in inappropriate behavior, proctors have the option to **suspend the candidate** directly from the **Candidate Management** view. Suspension temporarily stops the candidate’s exam and flags the case for further review.
***
### Suspending a Candidate
1. Navigate to the **Bookings** page and start the scheduled session.
2. In the **Candidate Management** view, locate the candidate you want to suspend.
3. Click the **menu** next to the candidate’s name.
4. Select **Suspend candidate** from the available options.
5. In the suspension panel:
* Choose a **reason for suspension** from the available options (e.g., unauthorized materials, communication violation, identity mismatch, etc.).
* Add any **additional context** if required.
6. Click **Confirm Suspension**.
***
### What Happens After Suspension
* The candidate’s **status** will be updated to **Suspended**.
* The exam session for that candidate will be **stopped immediately**.
* The action may require **administrator review**, depending on the system workflow.
* The suspension will be **recorded for future reference**, including the reason and any notes added.
***
### When to Suspend a Candidate
You should suspend a candidate when:
* There is a **serious rule violation**
* The candidate is using **unauthorized materials**
* There is a **clear identity mismatch**
* The candidate shows **disruptive or suspicious behavior**
* The exam integrity is **compromised**
**Best Practices**
* Ensure you have **valid justification** before suspending a candidate.
* Select the **most appropriate reason** for accurate reporting.
* Provide **clear additional context** to support further review.
* Use suspension only when necessary, as it directly impacts the candidate’s exam attempt.
# How to view your upcoming schedules
Source: https://docs.talview.com/center-and-proctor-administration/proctor/how-tos/how-to-view-your-upcoming-schedules
The **Bookings** section allows proctors to view all their scheduled sessions in one place. From here, you can quickly see your **current sessions**, **upcoming schedules**, and basic session details such as time, room, and seat capacity.
***
### Accessing Your Schedules
1. Navigate to the **Bookings** page after logging in.
2. The **Sessions** tab displays all scheduled sessions assigned to you.
***
### Understanding the Sessions View
Your schedules are organized in a clear, time-based layout so you can easily track what you need to proctor.
**Current / Active Session**
* The session that is about to start or is currently active appears at the **top of the page**.
* It includes key details such as:
* **Session name**
* **Date**
* **Start and end time**
* **Room number**
* **Number of seats available**
* A **Start Session** button is available for sessions that are ready to begin.
**Upcoming Sessions**
* Sessions scheduled **later in the day or on future dates** appear under the **Up Next** section.
* These sessions are displayed in chronological order so you can easily see what is scheduled next.
***
### Session Information Available
Each session card provides a quick overview of the schedule, including:
* **Session title**
* **Date of the session**
* **Session timing**
* **Assigned room**
* **Total seat capacity**
* **Device or setup indicators (if applicable)**
***
### Completed Sessions
To review sessions that have already finished:
1. Click the **Completed** tab.
2. This tab shows sessions that were previously conducted.
**Best Practices**
* Review your **Bookings dashboard regularly** to stay aware of upcoming sessions.
* Check session details in advance so you are prepared before the session start time.
* Start sessions promptly using the **Start Session** option when the time arrives.
# Understanding candidate status types
Source: https://docs.talview.com/center-and-proctor-administration/proctor/how-tos/understanding-candidate-status-types
Candidate statuses help administrators track a candidate’s progress throughout the exam lifecycle at the center. As a candidate moves through the exam process, from arrival at the center to exam completion the system updates their status accordingly.
This article explains the different candidate status types and what each status represents during the exam process.
***
### Candidate status types explained
The following table describes each candidate status and when it is typically used.
| Status | Description |
| :--------------- | :------------------------------------------------------------------------------------------------------------------------------------ |
| **REGISTERED** | The candidate record has been created in the system, but the candidate has not yet started the check-in process at the center. |
| **LOBBY** | The candidate has arrived at the center and is waiting to begin the check-in process or be assigned to a seat. |
| **CHECKED-IN** | The center administrator has verified the candidate’s identity and completed the check-in process. |
| **SEATED** | The candidate has been assigned to a specific seat in an exam room and is ready to start the exam. |
| **IN\_PROGRESS** | The candidate has started the exam and is actively taking the test. |
| **PAUSED** | The exam session has been temporarily paused, usually due to technical issues or administrative intervention. |
| **STOPPED** | The exam session has been stopped before completion, typically due to rule violations, technical issues, or administrative decisions. |
| **COMPLETED** | The candidate has successfully finished the exam. |
| **CHECKED OUT** | The candidate has completed the exam and finished the exit process at the center. |
| **SUSPENDED** | The candidate has been suspended from the exam due to misconduct, malpractice, or other policy violations. |
| **NO SHOW** | The candidate did not show up till the last entry time |
***
### Updating a candidate's status
While the system automatically updates most statuses as the exam progresses, you can manually update a candidate's status when operational requirements change.
1. Go to the **Candidates** tab from the center's page.
2. Locate the candidate whose status you want to update.
3. Click the three-dot menu at the end of the candidate's row.
4. Select **Update Status**.
5. Choose the appropriate status from the list.
6. Confirm the change.
The candidate's status is updated and reflected immediately in the **Status** column.
**Additional Tips**
* Candidate statuses help administrators **monitor exam progress in real time**.
* Some statuses are **automatically updated by the system** as the exam progresses.
* Administrators may **manually update certain statuses** based on operational requirements.
* Once a candidate reaches **Completed** or **Checked out**, the exam session is considered finished.
# Understanding the Candidate check-in flow
Source: https://docs.talview.com/center-and-proctor-administration/proctor/how-tos/understanding-the-candidate-check-in-flow
Once a proctor clicks on the **Check-in** option for a candidate, the system opens a detailed **check-in panel**. This panel guides the proctor through the necessary steps to verify the candidate and complete the check-in process.
***
### Overview of the Check-In Panel
The check-in panel provides all the required information and actions in one place. It typically includes:
* **Candidate details** (name and email)
* **Current status** (e.g., Checked In or not yet completed)
* Sections for **Seat Allocation**, **ID Capture**, and **Face ID**
* A **Complete Check In** button to finalize the process
***
### Step-by-Step Guide
**1. Review Candidate Status**
* At the top of the panel, you can see the candidate’s **current status**.
* If check-in is not yet completed, the system will indicate that the process is pending.
**2. Verify Seat Allocation**
* The **Seat Allocation** section shows the assigned **room and seat**.
* Confirm that the candidate is seated correctly.
* If required, you can **edit the seat allocation** using the edit (pencil) icon.
**3. Capture Candidate ID**
* In the **ID Capture** section, record the candidate’s identification details.
* This ensures the candidate’s identity matches the registered information.
* The system may show whether the ID has been captured or is pending.
**4. Capture Face ID**
* In the **Face ID** section, capture the candidate’s facial verification.
* This step helps ensure **identity validation and exam integrity**.
**5. Complete the Check-In**
* Once all required steps are verified and completed:
* Click on **Complete Check In**.
* The candidate’s status will update to **Checked In**.
***
### **Next steps after check-in**
* The candidate is marked as **Checked-in** in the dashboard.
* They are now ready to **begin the exam process**.
* Their check-in details (time and proctor) are recorded in their profile.
***
**Best Practices**
* Ensure the candidate is **physically present at the assigned seat**.
* Carefully verify **ID and facial details** before completing check-in.
* Do not complete check-in if **any discrepancies** are found.
* Use the edit option only when **seat reassignment is necessary**.
# Understanding the Candidate profile
Source: https://docs.talview.com/center-and-proctor-administration/proctor/how-tos/understanding-the-candidate-profile
The **Candidate Profile** provides detailed information about a candidate participating in a session. It helps proctors quickly review the candidate’s identity, exam details, check-in information, and any incidents reported during the session.
You can access the candidate profile from the **Candidate Management** view by either **clicking the candidate’s name** or selecting **View Profile** from the **menu (three-dot icon)** next to the candidate.
***
### Information Available in the Candidate Profile
The candidate profile contains several sections that provide important session-related details.
* **Candidate Information**
This section displays the basic details of the candidate, such as:
* **Candidate name**
* **Email address**
* **Candidate ID**
These details help confirm the identity of the candidate assigned to the session.
* **Check-In Details**
This section shows information related to the candidate’s check-in, including:
* **Check-in time**
* **Name of the proctor who performed the check-in**
This helps track when and by whom the candidate was admitted into the session.
* **Exam Details**
This section provides information about the exam assigned to the candidate, such as:
* **Exam name**
* **Session date**
* **Session time**
* **Assigned room**
* **Seat assignment**
These details help ensure that the candidate is scheduled for the correct exam and location.
**Incident Records**
The profile also displays any **incidents reported during the session**.
If no incidents have been recorded, the section will display **No incidents reported**.
**Face Authentication**
The profile displays the face authentication captured, which can be used as an identification factor for the candidate.
**Key Benefits of the Candidate Profile**
The candidate profile allows proctors to:
* Verify **candidate and exam information**
* Review **check-in activity**
* Monitor **reported incidents**
* Access key session details quickly while managing the session
Having all this information in one place helps proctors manage candidates efficiently during the exam session.
***
# Understanding the Candidate progress
Source: https://docs.talview.com/center-and-proctor-administration/proctor/how-tos/understanding-the-candidate-progress
The **Progress** column in the **Candidate Management** view shows the real-time state of a candidate’s exam activity. It helps proctors understand whether a candidate is actively taking the exam, facing connectivity issues, or temporarily away.
***
### Progress states
Below are the key progress states you may encounter:
**Online**
* The candidate is **actively connected and taking the exam**.
* No action is required.
**Reconnecting**
* The candidate has temporarily **lost connection and is attempting to reconnect**.
* This may be due to network instability.
* Monitor the candidate to ensure they reconnect successfully.
**Candidate Break**
* The candidate is on an **approved break** during the exam.
* The exam is paused for the candidate during this period.
**Proctor Break**
* The exam is paused due to a **proctor-initiated break**.
* This may be used in special situations requiring intervention or review.
**Disconnected**
* The candidate is **completely disconnected** from the session.
* Immediate attention may be required to determine the cause and next steps.
**Suspended**
* The candidate’s exam has been **suspended due to a violation or issue**.
* This typically requires **administrator review** before any further action.
***
### Using the Progress column
The Progress column helps you:
* Monitor whether candidates are **actively taking the exam**
* Identify candidates facing **technical issues**
* Track candidates who are **on break or paused**
* Take quick action in case of **disconnection or suspension**
**Best Practices**
* Keep an eye on candidates marked as **Reconnecting** or **Disconnected**.
* Ensure that **breaks are properly managed and monitored**.
* Investigate and document cases where candidates are **suspended or frequently disconnected**.
Understanding these progress states allows you to respond quickly and maintain a smooth and fair exam experience for all candidates.
# Understanding the Step column
Source: https://docs.talview.com/center-and-proctor-administration/proctor/how-tos/understanding-the-step-column
The **Step** column in the **Candidate Management** view indicates the current stage of a candidate within the exam workflow. It helps proctors quickly understand where each candidate is in the process and whether any action or attention is required.
***
### **Overview of the Step column**
The Step column provides a **visual indicator** of a candidate’s progression through the session lifecycle. Instead of reading detailed logs, proctors can glance at this column to assess the candidate’s current state.
**Common Step Indicators**
You may see the following indicators in the Step column:
* **In Progress (Active Step)**
* Displayed as a **green check icon**.
* Indicates that the candidate has successfully completed the previous step and is currently progressing normally.
* No action is required from the proctor.
* **Pending / Waiting**
* Displayed as an **hourglass icon**.
* Indicates that the candidate is in a waiting state (e.g., in the lobby or awaiting the next step).
* The proctor may need to take action, such as checking in the candidate.
***
### Using the Step column
The Step column helps you:
* Quickly identify candidates who are **waiting or stuck**
* Monitor candidates who are **progressing normally**
* Spot candidates who may need **immediate intervention**
**Best Practices**
* Regularly scan the Step column during a session to stay updated.
* Prioritize candidates showing **alerts or waiting indicators**.
* Use the Step column along with **Status** and **Progress** for a complete understanding of the candidate’s situation.
Understanding the Step column ensures that you can proactively manage candidates and maintain a smooth exam flow.
# Session Summary Report FAQs
Source: https://docs.talview.com/center-and-proctor-administration/session-playback/summary-report/faqs/session-summary-report-faqs
The session summary report gives proctors a consolidated view of a candidate's session integrity concerns, helping them make informed review decisions without needing to watch the full recording.
In this FAQ, you will find answers to common questions about the features currently available in the session summary report.
***
### General
**Q1. What is the session summary report?**
The session summary report is a structured overview of a candidate's proctored session. It displays the session outcome, candidate details, an AI-generated summary, and any flagged incidents, giving proctors everything they need to assess a session efficiently in one place.
**Q2. What does the session outcome rating mean?**
The session outcome rating appears as a banner at the top of the report and indicates the overall integrity level of the session:
* **Needs Review** means the session requires proctor attention before a decision can be made.
* **Low** indicates a low integrity score, meaning there is a higher risk of integrity incidents.
* **High** indicates a high integrity score, meaning there is a lower risk of integrity incidents.
***
### Candidate header
**Q1. What photo is shown in the candidate header?**
The photo shown is the candidate's base image, which is the face captured the first time they took a proctored exam on the platform. Reviewers can use this as a visual reference to confirm the candidate's identity during the review.
**Q2. What is the candidate ID shown in the report?**
The candidate ID is the external ID assigned to the candidate by the exam organization's system. It can be used to cross-reference the candidate across platforms if needed.
**Q3. What is the AI-generated summary?**
The AI-generated summary is a brief, plain-language overview of how the session went from a proctoring perspective, including whether any incidents occurred. It is an AI-assisted starting point and should be used alongside the incidents and video evidence when making a review decision, rather than as a definitive conclusion.
**Q4. What do the session start time and end time mean?**
The session start time is when the candidate began their proctored exam session and the session end time is when they completed it. Reviewers can use these timestamps to understand the duration of the session and identify any unusual timing patterns.
***
### Contributing incidents
**Q1. What is a contributing incident?**
A contributing incident is a group of events that were detected and flagged during the session. These appear in the contributing incidents section of the report.
**Q2. What do the incident severity levels mean?**
Severity indicates the risk level of a contributing incident:
* **High** (red) indicates a significant integrity concern that warrants close review.
* **Medium** (orange) indicates a moderate integrity concern that may require further assessment.
**Q3. What does the duration shown on an incident card mean?**
The duration is the time window during which the flagged events were grouped together. Any events that occur within the defined incident window are captured in the same incident.
**Q4. What does the event count on an incident mean?**
The event count shows how many individual events were detected and grouped together to form that incident within the duration window.
**Q5. Can I go through the timeline inside an incident video clip?**
The video evidence on an incident card supports play, pause, and full screen. To review the full session in more detail, use the Session Playback link in the candidate header.
# How to open the session recording from the summary report
Source: https://docs.talview.com/center-and-proctor-administration/session-playback/summary-report/how-tos/how-to-open-the-session-recording-from-the-summary-report
When reviewing a flagged session, Talview's session summary report gives reviewers quick access to the full session recording without having to search for it separately. In this article, you will learn how to open the session recording directly from the summary report.
***
### Step-by-step guide
1. **Open the session summary report.**
* Navigate to the session you want to review and open its summary report.
2. **Locate the Session Playback button.**
* At the top of the report, find the candidate header. The **Session Playback** button is located directly beneath the candidate ID.
3. **Click the Session Playback button.**
* The full session recording will open in the video player, where you can review the candidate's entire exam session.
**Additional Tips**
If you only need to review a specific incident rather than the full recording, incident cards on the summary report include short video clips that can be played inline without opening the full session playback.
# How to read the incident summary in the session report
Source: https://docs.talview.com/center-and-proctor-administration/session-playback/summary-report/how-tos/how-to-read-the-incident-summary-in-the-session-report
When a session contains flagged activity, related events are grouped together into contributing incidents. These incidents give reviewers a structured, at-a-glance summary of what occurred during a session, reducing the time spent manually reviewing lengthy recordings.
In this article, you will learn what each element of an incident means and how to use it to assess flagged activity efficiently.
***
### Elements of an incident card
| Element | Description |
| :----------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------- |
| **Duration window** | The window during which flagged events were grouped together. Any events that occur within the same window are captured in the same incident. |
| **Event count** | The total number of events flagged within that duration window. |
| **Severity** | The risk level of the incident: **High** (red) or **Medium** (orange) |
| **AI-generated summary** | A short description of what was detected, giving reviewers a quick read of what happened without opening the full session recording. |
| **Video evidence** | Short video clips of the flagged events within that window. Clips can be played inline or expanded to full screen for a closer look. |
**Additional Tips**
* Incidents are only shown for medium or high severity activity. If no incidents appear, no significant suspicious activity were detected during the session.
* Use the AI-generated summary alongside the video evidence to get a full picture of what occurred before deciding on any next steps.
# How to review incident video clips in the summary report
Source: https://docs.talview.com/center-and-proctor-administration/session-playback/summary-report/how-tos/how-to-review-incident-video-clips-in-the-summary-report
Incident video evidence gives you short clips automatically captured at the moment each incident occurred, so you can see exactly what the candidate was doing at that point in the session and make a more informed review decision.
In this article, you will open incident clips, navigate the timeline, and use the player controls to review flagged moments in detail.
***
### Step-by-step guide
1. Scroll to the **Contributing Incidents** section of the summary report.
2. Find the incident card you want to review. Each card shows the **severity level**, **event count**, and a summary of the specific violations identified, including an explanation of why that severity score was assigned.
3. Click **Play** on a clip to watch it inline. Clips are organized by stream. A clip only appears for streams where incidents were detected:
* **Primary:** candidate's camera feed
* **Secondary:** candidate's mobile feed
* **Primary Device Screen:** candidate's screen
4. Click the **Maximize** icon on a clip to open it in a larger view.
5. Use the **timeline** below the video to navigate the clip. Click or drag anywhere on the timeline to jump to that point. Hover over any segment on the timeline to see all the events detected within that window.
6. As the clip plays, watch for the overlay label in the bottom left of the video — it shows the name of the event detected at that moment. A **red dot** indicates the event was detected by the system. A **blue dot** indicates the event was added manually by a reviewer.
***
### Player controls
| Control | Action |
| :--------------- | :----------------------------------------- |
| **Play** | Start the clip |
| **Pause** | Pause the clip at any point |
| **Rewind** | Jump back 5 seconds |
| **Fast Forward** | Skip ahead 5 seconds |
| **Mute** | Turn off the audio |
| **Unmute** | Restore the audio |
| **Minimize** | Close the modal and return to the incident |
**Additional tips**
* Read the incident summary before watching the clip. Understanding what was flagged and why the severity was assigned helps you review the clip more efficiently.
* If a stream clip is missing, it means no relevant events were detected on that stream for that incident, this is expected behavior.
# How to view a candidate's face capture submission in the report
Source: https://docs.talview.com/center-and-proctor-administration/session-playback/summary-report/how-tos/how-to-view-a-candidates-face-capture-submission-in-the-report
During onboarding, candidates are required to capture a photo of their face. This image is compared against their base image to verify their identity. Reviewing the face capture lets you confirm that the person taking the exam is who they are expected to be.
***
### **Viewing the face capture submission**
1. Scroll to the **Candidate Submissions section** of the session report.
2. Click the **Face Capture** row to expand it. The pass or fail status reflects whether the candidate's face capture was approved during onboarding, either by the proctor or automatically by the system.
3. The **Session Face Verification** section displays two images side by side:
* **Session face capture:** photo taken during the session
* **Base image:** the face captured the first time the candidate took a proctored exam
> Note: Hover over the info icon next to the Session Face Verification label for a brief explanation of what is being compared.
4. If your exam is configured with face validation, a match status is shown to the right of the images - either **Matched** or **Mismatch** - indicating whether the session face capture was verified against the base image.
***
**Additional tips**
* If the status shows Mismatch, cross-reference with the Contributing Incidents section for any related flagged activity.
* If the candidate has multiple submissions, you can review their previous face capture submissions as well.
# How to view a candidate's submitted photo ID in the report
Source: https://docs.talview.com/center-and-proctor-administration/session-playback/summary-report/how-tos/how-to-view-a-candidates-submitted-photo-id-in-the-report
When reviewing a completed session, you may want to verify the photo ID the candidate submitted during onboarding, to confirm whether the document is the correct type and whether the face on the ID matches the candidate's photo on file. The ID Verification section of the summary report gives you a side-by-side view of both checks so you can assess them at a glance.
***
### Step-by-step guide
**1. Expand the ID Verification subsection** In the **Candidate Submissions** section, click the arrow next to **ID Verification** to expand it.
> **Note**: You'll see the overall result, **Passed** or **Failed** - displayed next to the section header.
**2. Review the ID Type Match** Under **ID Type Match**, you'll see the **ID Front** and **ID Back** images the candidate submitted.
> **Note**: The status on the right, **Matched** or **Not Matched** tells you whether the document matches the expected ID format.
**3. Review the Face Match** Under **Face Match**, you'll see the **Photo ID Face** extracted from the submitted ID alongside the candidate's **Base Image**. The status tells you whether the two faces are consistent.
> **Note:** Hover over the ⓘ icon next to **ID Type Match** or **Face Match** to understand what each check validates and how the result is determined.
**4. Click on an image to view it in detail** Click any image to open it in an expanded modal for a closer look.
***
**Additional tips**
* A single mismatch in either check is enough to result in an overall **Failed** status for ID Verification.
* The **Photo ID Face** is the face extracted from the candidate's submitted photo ID.
* The **Base Image** is the reference photo captured during the candidate's first ever proctored session and is used for all future face comparisons.
# How to view and play an incident's video evidence
Source: https://docs.talview.com/center-and-proctor-administration/session-playback/summary-report/how-tos/how-to-view-and-play-an-incidents-video-evidence
When reviewing a session, reviewers can access short video clips automatically captured at the moment each incident occurred, showing exactly what the candidate was doing at that time.
Being able to play these clips directly from the summary report saves proctors time by allowing them to assess flagged behavior without having to review the full session recording at once. In this article, you will learn how to play incident video clips and expand them to full screen for a closer look.
***
### **Step-by-step guide**
1. **Locate the incident card.**
* Scroll to the contributing incidents section of the summary report and find the incident you want to review.
2. **Play the video clip.**
* Video clips are displayed at the bottom of the incident. Click the **Play** button to start the clip inline.
3. **Expand to full screen (optional).**
* Click the **Full Screen** button on the video player to expand the clip for a closer view. Click the same button again to minimize it.
***
### **Video player controls**
| Control | Description |
| :---------- | :----------------------------------------------------- |
| Play | Start the video clip |
| Pause | Pause the video clip |
| Full Screen | Expand the video clip to full screen for a closer view |
**Additional Tips**
* Review the incident card details alongside the video clip before taking any action. The summary, severity level, and event count provide important context for what you are watching.
* If the video clip alone is not enough to make a confident decision, you can open the full session recording using the Session Playback button in the candidate header.
# How to view previous face capture submissions
Source: https://docs.talview.com/center-and-proctor-administration/session-playback/summary-report/how-tos/how-to-view-previous-face-capture-submissions
When reviewing a session, you may notice more than one face capture submission on record, this could happen if the candidate experienced a disconnection or had to redo their onboarding. Viewing previous submissions lets you see every face capture attempt alongside its match result, so you have a complete picture before making your assessment.
***
### Step-by-step guide
**1. Expand the Face Capture subsection** In the **Candidate Submissions** section, click the arrow next to **Face Capture** to expand it.
**2. View previous submissions** Click **View previous submissions** to expand the list of earlier face capture attempts. Each entry shows the submission timestamp, a face thumbnail, and a **Matched** or **Not Matched** status.
**Additional Tips**
* Previous submissions are listed in chronological order, with the earliest attempt at the top.
* If only one face capture was submitted during the session, the **View previous submissions** section will be empty.
# Understanding candidate header in session summary report
Source: https://docs.talview.com/center-and-proctor-administration/session-playback/summary-report/how-tos/understanding-candidate-header-in-session-summary-report
The candidate header appears at the top of every session summary report and gives reviewers an at-a-glance overview of who the candidate is and how their session went.
In this article, you will learn what each element in the candidate header means so you can orient yourself quickly before reviewing the details of a session.
***
### Elements of the candidate header
| Element | Description |
| :------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Session integrity outcome** | The overall risk level of the session: **Needs Review** (requires attention) **Low** (higher risk of integrity incidents) **High** (lower risk of integrity incidents) |
| **Candidate photo** | The candidate's base image from their first proctored session, used to confirm identity |
| **Candidate name** | The candidate's full name as registered for the exam |
| **Candidate ID** | The ID issued by the candidate's exam organization, also referred to as the external candidate ID |
| **Session playback** | A link to open the full session recording |
| **AI-generated summary** | A concise summary of candidate verification outcomes, notable incidents, and any unusual behaviors observed during the session |
| **Candidate start and end time** | The time the candidate began and completed their proctored exam session |
**Additional Tips**
The session integrity outcome banner is the first thing to check when opening a report. It gives an immediate signal of how much attention the session may need before reviewing individual incidents.
# Session Video Player FAQs
Source: https://docs.talview.com/center-and-proctor-administration/session-playback/video-player/faqs/session-video-player-faqs
The session video player is dedicated tool for reviewing completed proctored sessions. It brings together the candidate's camera feeds, screen recording, and review tools in one place. You can access it directly from the session summary report.
This FAQ is a quick reference for understanding the video player's features and how to use them during a review.
***
### 1. Session playback
**Q1. What is the video player?**
The video player is a dedicated view for reviewing a completed proctored session. It shows the candidate's camera feeds and screen share alongside tools that let you flag, acknowledge, and dismiss incidents. You can open it from the session summary report.
**Q2. What are the three streams shown in the session playback?**
The session playback shows three streams:
* **Primary camera:** the candidate's face during the session.
* **Secondary camera:** the candidate's surrounding environment.
* **Screen share:** everything displayed on the candidate's screen.
You can review each stream independently to get a full picture of what the candidate was doing.
**Q3. What does the timeline in the session playback show?**
The timeline gives you a visual overview of the entire session. It includes three elements:
* **Progress bar:** shows where you are in the playback.
* **Audio waveform:** highlights periods when audio was detected.
* **Colored incident markers:** pinpoint moments where incidents were flagged, color-coded by severity.
Use the timeline to spot areas of interest and jump directly to them.
**Q4. What do the colored incident markers on the timeline mean?**
The markers are color-coded by severity:
* 🔴 **Red:** high severity
* 🟠 **Orange:** medium severity
* 🟡 **Yellow:** low severity
Use these colors to prioritize which incidents to review first before diving into the timeline.
**Q5. What's the difference between session playback and activity playback?**
They serve different purposes:
* **Session playback** shows the candidate's camera feeds and screen share alongside the incident timeline. Use this to review flagged events in context.
* **Activity playback** shows a detailed replay of what the candidate did on their screen during the session. Use this when you need to verify whether they accessed unauthorized content, switched tabs, or interacted with restricted applications.
**Q6. What does "Feed unavailable" mean on a stream?**
It means the recording for that stream wasn't captured or isn't accessible for this session. When this happens, review the remaining available streams and note the missing feed when making your determination.
***
### 2. Activity playback
**Q1. What is an Activity playback?**
The **Activity Playback** tab provides a complete replay of the candidate's on-screen activity during the session. It captures every interaction on the candidate's screen, allowing reviewers to verify whether the candidate accessed unauthorized content, switched between applications, or interacted with anything outside the exam environment.
**Q2. What does the “Skip inactive” toggle do?**
The **Skip Inactive** toggle automatically skips periods where there was no mouse or keyboard activity on the candidate's screen. It helps you get through the recording faster without missing anything relevant.
***
### 3. Side panes
**Q1. What panes are available in the video player?**
The video player includes the following panes:
* **Rules pane:** shows the rules that applied to this session.
* **Candidate details pane:** displays the candidate's profile and session information.
* **Onboarding checks pane:** summarizes the checks completed during the candidate's onboarding.
* **System overview pane** (left strip): shows an overview of the candidate's system and environment.
* **Candidate chat pane:** shows the conversation history between the candidate and proctor.
* **Flagged incidents panel** (right strip): lists all incidents flagged during the session.
**Q2. What is the incidents panel?**
The **Incidents** panel is a consolidated list of all incidents flagged during the session, grouped by severity. You can review each incident here and take actions like acknowledging or dismissing them.
**Q3. Why is the candidate chat read-only in the video player?**
The chat pane shows the conversation history from the completed session. Because the session has ended, you can't send new messages. It's available for reference only.
***
### 4. Review actions
**Q1. What's the difference between acknowledging and dismissing an incident?**
* **Acknowledging** confirms the incident is valid and has been noted.
* **Dismissing** marks it as a false positive or resolved. You'll need to provide a reason when dismissing.
**Q2. What's the difference between a red dot and a blue dot on an incident event?**
* 🔴 **Red dot:** the event was generated automatically by the system.
* 🔵 **Blue dot** (with a Reviewer tag): the event was manually added by a proctor or reviewer.
**Q3. Why aren't my review changes showing in the report yet?**
Your changes are saved, but won't appear in the report until you click **Recalculate Risk Index** and confirm. This gives you a chance to review everything before the report is updated.
**Q4. What happens when I click Recalculate Risk Index?**
This is the final step in the review process. When you confirm, all staged changes are committed and the session's outcome rating in the report is updated. You can't make further edits after confirming.
**Q5. Can I undo my review after submitting?**
No. Once you confirm **Recalculate Integrity Outcome**, the review is final and no further edits can be made.
**Q6. What's the difference between reporting a new incident and adding an event to an existing incident?**
* **Reporting a new incident** creates a brand-new entry in the **Incidents** panel.
* **Adding an event to an existing incident** adds more detail to an incident that already exists.
**Q7. Where does a manually reported incident appear after I submit it?**
It appears as a new entry in the **Incidents** panel. It appears in the report once you finalize your review by clicking **Recalculate Integrity Outcome**.
# How to access the incidents in the video player
Source: https://docs.talview.com/center-and-proctor-administration/session-playback/video-player/how-tos/how-to-access-the-incidents-in-the-video-player
When reviewing a session, the video player gives you a visual overview of all incidents flagged during the session directly on the timeline. Each incident is color-coded by severity, so you can spot areas of concern at a glance before deciding where to focus your review.
***
### Step-by-step guide
**1. Open the video player** On the session summary report, click **Session Playback** to open the video player.
**2. Look at the timeline** The timeline at the bottom of the player shows color-coded incident markers:
* 🔴 **Red** - High severity
* 🟠 **Orange** - Medium severity
* 🟡 **Yellow** - Low severity
**3. Interact with an incident marker**
* Hover over any incident marker to see a popup showing the incident name and all the individual events within it. Each event is plotted on a mini-timeline showing when it occurred within the incident window, so you can see at a glance how events were distributed across the incident.
* The timeline also shows you where high, medium, and low severity incidents occurred throughout the session, giving you a quick sense of which parts of the recording need the most attention.
* Click the marker to jump directly to that point in the recording.
**Additional Tips**
* Use the color coding to prioritize which incidents to review first, start with red markers to address the most critical incidents before moving to orange and yellow.
* If an incident has multiple events clustered closely together, click the incident marker on the timeline to jump to that moment and review the recording directly.
# How to acknowledge an incident in the session recording
Source: https://docs.talview.com/center-and-proctor-administration/session-playback/video-player/how-tos/how-to-acknowledge-an-incident-in-the-session-recording
Acknowledging an incident confirms that you have reviewed it and consider it valid. This creates a clear record of who reviewed the incident and when, which is useful for audit purposes and for anyone else accessing the session.
***
### Step-by-step guide
1. Click the second icon in the right strip to open the Incidents pane.
2. Find the incident you want to acknowledge.
3. Click the **acknowledge icon** on the right side of the incident row.
4. A confirmation note appears below the incident reading: "Acknowledged by \[your name] at \[timestamp]."
**Additional tips**
* Acknowledging an incident does not affect the session's integrity outcome, it is a record-keeping action only. The incident remains active and will be included in the recalculation when you submit your review via **Recalculate Risk Index**.
# How to bring a specific video stream into the main view
Source: https://docs.talview.com/center-and-proctor-administration/session-playback/video-player/how-tos/how-to-bring-a-specific-video-stream-into-the-main-view
During a session review, the video player gives you access to three streams — the primary camera, secondary camera, and screen recording. You can bring any one into the main view instantly at any point during playback.
***
### Step-by-step guide
**Step 1: Locate the video streams**
In the playback view, you'll see three streams:
* **Primary camera** : the candidate's webcam feed
* **Secondary camera**: the feed from the candidate's phone
* **Screen recording:** the candidate's screen activity
**Step 2: Click a stream to bring it into the main view**
Click any smaller preview to expand it. The previously active stream moves to a smaller preview.
**Step 3: Switch streams at any time**
You can switch streams while playback is running, it won't interrupt or reset the recording.
# How to change the severity of an incident in session recording
Source: https://docs.talview.com/center-and-proctor-administration/session-playback/video-player/how-tos/how-to-change-the-severity-of-an-incident-in-session-recording
The system assigns a severity level to each incident based on the events detected, but this may not always reflect what you observe when reviewing the recording. If you believe an incident has been rated too high or too low, you can manually override the severity before submitting your review.
***
### Step-by-step guide
1. Click the second icon in the right strip to open the Incidents pane.
2. Find the incident whose severity you want to update. The current severity is shown as a badge on the right side of the incident row.
3. Click the **severity badge** to open the severity dropdown.
4. Select the severity that best reflects the incident:
| Option | When to use |
| :--------- | :---------------------------------------------------- |
| **High** | The incident reflects a significant integrity concern |
| **Medium** | The incident is notable but not critical |
| **Low** | The incident is minor or needs limited follow-up |
5. The severity badge updates immediately to reflect your selection.
**Additional tips**
* If you're unsure which severity to assign, review the incident details and any available video clips before making a change.
* Severity changes are not saved until you submit your review via **Recalculate Risk index**. You can adjust the severity at any point before submitting.
# How to dismiss an incident
Source: https://docs.talview.com/center-and-proctor-administration/session-playback/video-player/how-tos/how-to-dismiss-an-incident
When reviewing a session, you may come across incidents that were incorrectly flagged by the system. Dismissing an incident marks it as a false positive and excludes it from the final integrity rating, keeping your review accurate without removing the incident from the record entirely.
***
### Step-by-step guide
1. Click the second icon on the right strip of the video player to open the incidents pane.
2. Locate the incident you want to dismiss and click the **dismiss icon** on the right side of the incident row.
3. In the modal that appears, enter a reason for dismissal in the text field provided. The **Dismiss** button remains disabled until a reason has been entered.
4. Click **Dismiss** to confirm.
5. The incident title is struck through to indicate it has been dismissed. A note appears below the incident showing who dismissed it, at what time, and the reason provided.
**Additional Tips**
* Always enter a clear and accurate reason for dismissal, as this helps maintain a reliable review record.
# How to dismiss an individual event within an incident
Source: https://docs.talview.com/center-and-proctor-administration/session-playback/video-player/how-tos/how-to-dismiss-an-individual-event-within-an-incident
Not every event flagged by the system accurately reflects a violation. Dismissing an individual event lets you remove a false positive detection without dismissing the entire incident, keeping your review accurate without losing the context of what else was flagged.
***
### Step-by-step guide
1. Click the second icon in the right strip to open the Incidents panel.
2. Click the **chevron** on the incident that contains the event you want to dismiss to expand it. The individual events that contributed to the incident will appear below.
3. Click the **dismiss icon** on the right side of the event you want to dismiss.
4. The event is immediately struck through, indicating it has been dismissed.
**Additional tips**
* When you dismiss an event, the incident severity may be updated based on the configuration and its logic.
* Before dismissing an event, cross-reference it with the video evidence to validate whether it was correctly flagged by the system.
# How to submit your review using Recalculate Risk Index
Source: https://docs.talview.com/center-and-proctor-administration/session-playback/video-player/how-tos/how-to-submit-your-review-using-recalculate-risk-index
When reviewing a session, any changes you make - acknowledging incidents, dismissing events, adjusting severity, or adding new events, are saved as staged changes and won't be reflected in the session report until you submit your review. Recalculate Risk Index is the final step that commits all your changes and updates the report with the revised assessment.
***
### Step-by-step guide
**1. Complete your review actions** Make sure you've finished reviewing all incidents and events in the session before proceeding.
**2. Click the Recalculate Risk Index button** Below the video player, click the circular **Recalculate Risk Index** button. When there are staged changes waiting to be submitted, the button will show a red dot.
**3. Confirm the action** A confirmation modal will appear. Review the following before proceeding:
* All staged changes including modifications to incident severity, acknowledged or dismissed incidents, dismissed events, and manually added events or incidents, will be applied to the session summary report.
* Click **Recalculate** to confirm and submit your review.
**4. Check the updated outcome** Click **Back to Report** in the top left to return to the session summary report and see the updated risk index reflecting your review.
**Additional Tips**
* Staged changes are only visible to you until you submit. The session report will continue to show the original outcome until you click **Recalculate Risk Index**.
* This action cannot be undone, make sure all your review actions are final before submitting.
# How to use the playback controls in the activity playback
Source: https://docs.talview.com/center-and-proctor-administration/session-playback/video-player/how-tos/how-to-use-the-playback-controls-in-the-activity-playback
When reviewing a session in the **Activity Playback** tab, the playback controls at the bottom of the player let you manage how you watch the recording, so you can move through it at your own pace and focus on the moments that matter.
***
### Step-by-step guide
**1. Play or pause the recording** Click the **pause** icon to stop the recording at any point. Click it again to resume.
**2. Adjust the playback speed** Click any speed option - **1x**, **2x**, **4x**, or **8x** to control how fast the recording plays. Use higher speeds to move through inactive periods quickly.
**3. Skip inactive periods** Toggle **skip inactive** on to automatically skip periods where no activity was detected, so you only watch the moments where the candidate was active.
**4. Maximize the player** Click the **maximize** icon (↗) in the bottom right to expand the activity playback to full screen for a closer look.
**Additional Tips**
* Use **skip inactive** together with a higher playback speed to move through long sessions efficiently.
* The seekbar at the bottom shows your current position in the recording, click or drag it to jump to any point.
# How to use the session playback controls in the video player
Source: https://docs.talview.com/center-and-proctor-administration/session-playback/video-player/how-tos/how-to-use-the-session-playback-controls-in-the-video-player
Sessions can range from a few minutes to several hours. The playback controls at the bottom of the video player gives you the flexibility to move through a recording at your own pace, skipping ahead through uneventful sections, slowing down to examine a specific moment, or adjusting audio and captions to suit your review environment.
***
### The playback controls
1. **Play and pause**
* Click the **Play** button to start the recording. Click it again at any point to pause.
2. **Rewind and fast forward**
* Click the **Rewind** button to jump back 5 seconds, or the **Fast Forward** button to skip ahead 5 seconds. Click either button multiple times to move further in that direction.
3. **Mute and unmute**
* Click the **Mute** button to turn off audio. Click it again to restore sound.
4. **Playback speed**
* Click the **Playback speed** button on the toolbar — the default is **1x**. Select the speed that fits your review:
| Speed | When to use it |
| :------------------ | :--------------------------------------------------- |
| **Less than 1x** | Slow down to examine a specific moment in detail |
| **1x** | Review at normal speed |
| **Greater than 1x** | Move quickly through uneventful parts of the session |
* The recording adjusts to the selected speed immediately. You can change it at any point without pausing.
1. **Captions**
* Click the **CC** button to enable captions. This is useful when you want to follow what a candidate is saying without relying solely on audio, for example when reviewing in a noisy environment or when audio quality is unclear.
* A transcription of the candidate's speech appears on the player, synchronized with the audio.
* Click **CC** again to turn captions off.
**Additional Tips**
* You can switch between the **Primary**, **Secondary**, and **Screenshare** feeds at any point during playback by clicking the stream you want to bring into focus.
* Use **Rewind** and **Fast Forward** to zero in on a specific moment without dragging the seek bar.
* Muting is useful when reviewing in a shared or noisy environment where audio may be distracting.
* You can toggle captions and mute on or off at any point without pausing the recording.
# How to view a candidate's 360 environment scan in the session summary report
Source: https://docs.talview.com/center-and-proctor-administration/session-playback/video-player/how-tos/how-to-view-a-candidates-360-environment-scan-in-the-session-summary-report
Before a candidate begins their exam, they are required to complete a 360 environment scan - a full rotation of their surroundings captured on camera during onboarding. Reviewing this scan lets you verify that the candidate's environment was clear of any unauthorized materials or assistance at the start of the session.
***
### Step-by-step guide
1. Scroll to the **Candidate Submissions** section of the session report.
2. Click the **360 Environment Scan** row to expand it. The pass or fail status is shown on the right side of the header.
> **Note**: The **pass** or **fail** status reflects whether the candidate's environment scan was approved during onboarding, either by the proctor or automatically by the system.
3. A preview of the images captured from the candidate’s environment scan are displayed.
4. Use the left and right arrows to pan through the images and inspect their surroundings.
5. Click on any image to expand it and inspect it more closely. Click the “✕” in the top right of the modal to close it and return to the report.
**Additional tips**
* The **View previous submissions** toggle only appears when more than one submission exists. If there was only one submission, it won't be shown.
* If the candidate has multiple submissions, you can review their previous scans as well.
# How to view the events within an incident in the side panel
Source: https://docs.talview.com/center-and-proctor-administration/session-playback/video-player/how-tos/how-to-view-the-events-within-an-incident-in-the-side-panel
Each incident is made up of one or more individual events detected during the session. Expanding an incident lets you see exactly what contributed to it, giving you the full context you need to decide whether to acknowledge, dismiss, or modify the incident.
***
### Step-by-step guide
1. Click the second icon in the right strip to open the Incidents pane.
2. Find the incident you want to review and click the **chevron** on the left side of the incident row to expand it.
3. The expanded incident shows a list of all individual events that contributed to it. For each event you will see:
| **Event name** | The type of violation detected |
| :--------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Timestamp** | When the event occurred in the session |
| **Source** | Indicated by a colored dot. A red dot means the event was detected by the system. A blue dot means the event was manually added by a reviewer, and will include a **Reviewer** tag. |
| **Dismiss icon** | To dismiss the event if it was incorrectly flagged |
**Additional Tips**
* Use the timestamp on each event to jump to that moment in the recording and verify what actually occurred.
* If an incident contains a mix of system-generated and reviewer-added events, look at each individually before deciding whether to dismiss or acknowledge the incident as a whole.
# What do the dots inside a suspicious moment mean
Source: https://docs.talview.com/center-and-proctor-administration/session-playback/video-player/how-tos/what-do-the-dots-inside-a-suspicious-moment-mean
This document explains the three types of dots visible inside the incident hover pop-up in the session playback view and how reviewers can use them to make informed decisions during a session review.
***
### Overview
When you hover over an incident zone on the timeline, a pop-up appears showing a mini-timeline with dots on it. Each dot represents a single occurrence of a flagged event within that incident's time window. The dots are not all the same — their appearance indicates how the event was flagged and what action, if any, has been taken on it.
Understanding the difference between dot types helps reviewers quickly assess the nature of flagged activity before deciding whether to investigate further.
***
### Types of dots visible inside the incident hover pop-up
**1. Filled red dots: system-detected events**
Filled red dots represent events that were automatically detected and flagged by the AI during the session.
| Attribute | Details |
| :------------------ | :---------------------------------------------------------------------------------------------------------------------- |
| **Appearance** | Solid filled red dot |
| **Origin** | Automatically detected by the AI proctoring system |
| **What it means** | The system identified suspicious behavior at this moment, such as face not detected, background voice, or tab switching |
| **Action required** | Review the event in the context of the full incident to determine if it represents genuine misconduct |
***
**2. Red dots with a red border: manually added by a proctor**
Red dots with a red border represent events that were manually flagged by a proctor during the live session. These indicate that a human reviewer observed suspicious behavior that may not have been detected automatically by the system.
| Attribute | Details |
| :------------------ | :-------------------------------------------------------------------------------------------------------- |
| **Appearance** | Red dot with a red border |
| **Origin** | Manually added by a proctor during the live session |
| **What it means** | A proctor observed and flagged suspicious behavior at this moment that warranted human intervention |
| **Action required** | Treat these with high attention, as they reflect a deliberate human judgment call made during the session |
***
**3. Gray dots: dismissed events**
Gray dots represent events that were previously flagged but have since been dismissed. A dismissal indicates that the event was reviewed and determined not to represent genuine misconduct.
| Attribute | Details |
| :------------------ | :--------------------------------------------------------------------------------------- |
| **Appearance** | Gray dot |
| **Origin** | Previously flagged (by the system or a proctor) but subsequently dismissed after review |
| **What it means** | The event was investigated and ruled out as a false positive or non-issue |
| **Action required** | No immediate action needed, but dismissed events remain visible for audit trail purposes |
***
### Dot types at a glance
| Dot type | Origin | Status |
| :------------------------- | :------------------------ | :----------------------- |
| 🔴 Filled red dot | System-detected | Active, pending review |
| 🔴 Red dot with red border | Manually added by proctor | Active, flagged by human |
| ⚪ Gray dot | System or proctor flagged | Dismissed after review |
***
# Why are math equations not displaying correctly?
Source: https://docs.talview.com/content-and-exam-admins/assessment-and-exam-coordinators/content-manager-creator/diagnostics/why-are-math-equations-not-displaying-correctly
If math equations in your assessment are showing as blank, displaying raw code, or not rendering the way you expect, this is usually caused by a syntax issue or a browser compatibility problem in Talview. In this article, you will identify the cause and resolve the display issue on both the author and candidate side.
### 🔎 Troubleshooting common issues
| What might be wrong | How to fix it |
| ----------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Equation is showing raw code instead of a formatted equation | There may be a syntax error or an unsupported command. Check your equation syntax, correct any errors, and re-insert the equation. Refer to the KaTeX documentation for supported commands. |
| Equation block appears blank | The equation may be missing required delimiters. Delete the block and re-insert it using the slash menu. |
| Equation renders correctly on the author side but not for the candidate | This may be a rendering delay or a browser issue on the candidate side. Ask the candidate to refresh their browser or try a supported browser such as Chrome, Edge, or Firefox. |
| Nested or complex equations are broken | Complex nesting may not be supported. Try simplifying the equation or splitting it into multiple blocks. |
| Equation disappears after saving | Re-insert the equation using the slash menu and confirm it renders correctly in preview before saving again. |
| Equation renders in preview but breaks in the candidate-facing question | This is likely a browser compatibility issue. Confirm the candidate is using a supported and up-to-date browser. Mobile browsers may have limited support for equation display. |
**Additional Tips**
* Always preview your equation after inserting it and before publishing the assessment to catch any display issues early.
* If the issue persists after trying the steps above, report it with the following details: the exact equation input used, a screenshot of the broken output, your browser and operating system, and the question ID.
# Why can't candidates see the reference file on a long form question?
Source: https://docs.talview.com/content-and-exam-admins/assessment-and-exam-coordinators/content-manager-creator/diagnostics/why-cant-candidates-see-the-reference-file-on-a-long-form-question
If a candidate can't see or download the reference file attached to a long form question, there are a few common reasons this can happen in Talview. In this article, you will identify the cause and get the file visible and downloadable for your candidate.
### 🔎 Troubleshooting common issues
| What might be wrong | How to fix it |
| ----------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| The download button is not visible to the candidate | The file may not have been attached, or the question may not have been saved correctly. Re-open the question in the Assessment Engine, re-attach the PDF, and republish the question. |
| The download button is visible, but the file won't download | The candidate's browser may be blocking downloads. Ask the candidate to check their browser's pop-up and download settings, or try a supported browser such as Chrome, Edge, or Firefox. |
| The file is attached in the Assessment Engine but not showing in the candidate view | This may be a publishing or sync delay. Wait a few minutes and ask the candidate to refresh their browser and try again. If the issue persists after 30 minutes, escalate. |
| The file was uploaded in a format other than PDF | Only PDF files are supported as reference attachments for long form questions. Re-upload the file as a PDF and republishes the question. |
| The file size exceeds the supported limit | Check that the file is within the supported upload limit. If it's too large, reduce the file size and re-upload. |
**Additional Tips**
* Before asking the candidate to retry, confirm the question is fully published and not sitting in draft. A question saved as a draft will not be visible in the candidate view.
* Always test the download flow yourself as a candidate before the assessment goes live to catch any issues early.
* If the file is confirmed attached in the Assessment Engine but still not showing in the candidate view after 30 minutes, escalate with the following details: question ID, assessment ID, tenant ID, and the candidate's browser and operating system.
# Why can't my candidate access their assessment?
Source: https://docs.talview.com/content-and-exam-admins/assessment-and-exam-coordinators/content-manager-creator/diagnostics/why-cant-my-candidate-access-their-assessment
If a candidate is unable to access their assessment, it may be because a step window is restricting when they can enter in Talview. In this article, you will identify the reason for the block and resolve the issue so the candidate can access their assessment.
### 🔎 Troubleshooting common issues
| What might be wrong | How to fix it |
| ------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Candidate is too early and sees a waiting screen with a countdown | The onboarding window hasn't opened yet. Let the candidate know when the window opens and ask them to return at that time. |
| Candidate sees a holding screen showing the session open time | The action window hasn't opened yet and no onboarding window is configured. Let the candidate know when they can enter and ask them to return at that time. |
| Candidate sees a session closed or expired message | The step window has passed. Navigate to the workflow in Workflow Tools or the Coordinator Console, locate the assessment step, and extend the window or create a new invite for the candidate. |
| Candidate is within the window but still blocked | There may be a timezone mismatch in the configuration. Navigate to the workflow, locate the assessment step, and verify that the timezone setting matches the candidate's local time. Correct it if needed. |
| Onboarding window is set for the future, but the action window is current | This is expected behaviour. The system uses the action window when no onboarding window is active. Confirm the candidate is seeing the correct message. |
| No windows are configured but the candidate is still blocked | The invite validity period may have expired. Check the invite validity and update it or resend a new invite. |
**Additional Tips**
* Always verify the timezone setting in the workflow configuration before escalating. Timezone mismatches are the most common cause of access issues.
* If the issue can't be resolved using the steps above, escalate with the following details: workflow ID, step ID, candidate email, configured window times, and a screenshot of what the candidate sees.
* After making any changes, ask the candidate to refresh their browser and try again before confirming the fix.
# Why is the estimated duration showing as "undefined" in assessment emails?
Source: https://docs.talview.com/content-and-exam-admins/assessment-and-exam-coordinators/content-manager-creator/diagnostics/why-is-the-estimated-duration-showing-as-undefined-in-assessment-emails
If you or your candidates are seeing "undefined" where the estimated duration should appear in an assessment invite or reminder email, this is usually because the section time hasn't been set for that assessment in Talview. In this article, you will resolve the issue and ensure candidates see the correct duration in their emails.
### 🔎 Troubleshooting common issues
| What might be wrong | How to fix it |
| ----------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Section time has not been set for the assessment | Open the Assessment Engine, navigate to the relevant assessment, go to the section settings, set the **Section Time** value, and save. Resend the invite - the updated email will include the estimated duration. |
| Estimated duration is not visible at all (no "undefined", just missing) | This is expected behaviour. When no section time is set, the duration field is hidden rather than showing "undefined." To make it appear, set the section time as described above. |
| Section time is intentionally not set (open-ended assessment) | No action needed. The duration field will not appear in the email, and this is expected. |
**Additional Tips**
* After setting the section time, send a test invite to yourself to confirm the estimated duration appears correctly and is readable (for example, 30 mins or 1 hr 15 mins).
* Emails that have already been sent will not be updated. Only new invites sent after the change will reflect the duration.
* If the duration field is missing and no section time is needed for the assessment, no fix is required - this is working as intended.
# How to specify a job role for an AI Interviewer persona
Source: https://docs.talview.com/content-and-exam-admins/assessment-and-exam-coordinators/content-manager-creator/how-tos/how-to-specify-a-job-role-for-an-ai-interviewer-persona
Talview's Ivy persona builder platform generates a list of interviewer avatars based on the job position you are hiring for. In this article, you will select a job position to populate the avatar list when creating an AI interviewer persona.
### **Step-by-step guide**
1. **Open the avatar list.**
* The avatar list appears on the left side of the screen after you have entered a job position and selected a track.
2. **Review the available avatars.**
* Each avatar in the list displays a name, photo, description, team, and skills. Review these details to find the best match for the job position you are hiring for.
3. **Select an avatar.**
* Click the avatar that best fits the job position you are hiring for.
**Additional tips**
* Pay close attention to the skills listed for each avatar, as this is the most reliable indicator of whether the avatar is a good fit for the job position.
* If none of the avatars feel like the right match, go back and adjust the job position or track you entered to refresh the list.
* You can review as many avatars as you need before making a selection, as there is no limit to how many you can browse before moving forward.
# How to add a center to an exam
Source: https://docs.talview.com/content-and-exam-admins/assessment-and-exam-coordinators/exam-coordinators/How-to/center/how-to-add-a-center-to-an-exam
Centers are the physical locations where candidates sit for their exam. Before candidates can book a slot at a center, the center must first be assigned to the exam. Talview's Coordinator Console lets you add existing centers to an exam directly from the Centers tab. In this article, you will learn how to add a center to an exam in the Coordinator Console.
**Before You Beign:**
Make sure you have:
* Coordinator role access on your Talview account.
* An active exam to assign centers to.
* At least one center already configured in your tenant. Centers are set up by your platform administrator, you cannot create new centers from this screen.
***
### Step-by-Step Guide
**1. Open the exam from the Exams list**
From the Coordinator Console, navigate to the **Exams** section using the left sidebar. Click on the exam you want to add centers to.
**2. Go to the Centers tab**
Inside the exam, click the **Centers** tab. This shows all centers currently assigned to the exam. If no centers have been added yet, the tab will be empty.
**3. Click + Add Center**
In the top-right area of the Centers tab, click **+ Add Center**. This opens the **Add Existing Center** modal.
**4. Configure the center assignment**
In the modal, fill in the following:
* **Select Exam Step** - choose the assessment step this center will be assigned to. For multi-step exams, you can assign different centers to different steps.
* **Guest Capacity** - optionally set the number of guest seats available at this center for this exam. Leave blank to use the center's default capacity.
**5. Select the centers**
The modal displays a searchable list of all available centers in your tenant, each showing the center name and location. Select one or more centers by checking the checkbox next to each.
**6. Click Add**
Click **Add** to confirm. The modal closes and the selected centers appear in the Centers table with their details, including center name, type, step, status, location, contact, capacity, and booking distribution.
***
**Additional Tips**
* You can add multiple centers at once by selecting multiple checkboxes before clicking Add.
* Adding a center to an exam only maps it to that exam, it does not change the center's original configuration or affect its availability in other exams.
* If the center you need is not in the list, contact your platform administrator to have it configured in the tenant.
* You can remove a center from the exam at any time from the Centers tab if it is no longer needed.
* If you are unable to see any centers in the list, reach out to your customer support manager to have them configured for your tenant.
# How to filter centers in the coordinator console
Source: https://docs.talview.com/content-and-exam-admins/assessment-and-exam-coordinators/exam-coordinators/How-to/center/how-to-filter-centers-in-the-coordinator-console
The Centers tab in the Coordinator Console shows all centers assigned to an exam. In this article, you will learn how to filter centers in the Coordinator Console.
***
### Before You Begin
Make sure you have:
* Coordinator role access on your Talview account.
* An active exam with at least one center assigned to it.
***
### Step-by-Step Guide
**1. Open the exam from the Exams list**
From the Coordinator Console, navigate to the **Exams** section using the left sidebar. Click on the exam whose centers you want to filter.
**2. Go to the Centers tab**
Inside the exam, click the **Centers** tab. This displays all centers assigned to the exam in a table with the following columns:
* **Center** - the center name and center code.
* **Step** - the assessment step the center is assigned to (e.g., Listening, Reading & Writing, Speaking).
* **Status** - the current status of the center (e.g., Active).
* **Location** - the center's physical address, displayed as a clickable link.
* **Contact** - the name and email address of the center contact person.
* **Capacity** - the number of seats available at the center for this exam.
* **Next 14 days distribution** - a visual bar showing booking distribution across the next 14 days.
**3. Click the filter icon**
In the top-right area of the Centers tab, click the **filter icon** (next to the Search bar). A **Filters** dropdown opens with the following options:
* **Center status** - filter by the current status of the center (e.g., Active).
* **Location** - filter by the center's physical location.
* **Capacity** - filter by the number of seats available at the center.
**4. Select a filter**
Click on the filter you want to apply. Depending on the filter type, a set of options or an input field will appear. Select or enter your criteria to apply the filter.
Use the **search bar** at the top of the Filters dropdown to quickly find a specific filter option.
**5. Review the filtered results**
The Centers table updates to show only the centers that match your selected filters. You can apply multiple filters at the same time to further narrow down the results.
**6. Clear the filters**
To remove the filters and return to the full centers list, click the filter icon again and clear your selections.
***
**Additional Tips**
* Use the **Location** filter to quickly find centers in a specific city or area, particularly useful when managing large exams spread across multiple regions.
* The **Capacity** filter helps you identify centers with sufficient seating before assigning additional candidates or creating new schedule slots.
* Use the **Search** bar alongside filters for more precise results - for example, search for a center by name while filtering by status.
* Click **Export** to download the filtered centers list for offline reference or reporting.
# How to remove a center from an exam
Source: https://docs.talview.com/content-and-exam-admins/assessment-and-exam-coordinators/exam-coordinators/How-to/center/how-to-remove-a-center-from-an-exam
When a center is no longer required for an exam, you can unlink it from the Centers tab in the Coordinator Console. Removing a center unlinks it from the exam without affecting the center's configuration in your tenant. In this article, you will learn how to remove a center from an exam in the Coordinator Console.
**Before You Begin**
Make sure you have:
* Log in to your Talview account and make sure you have coordinator role access.
### Step-by-Step Guide
**1. Open the exam from the Exams list**
From the Coordinator Console, navigate to the **Exams** section using the left sidebar. Click on the exam you want to manage.
**2. Go to the Centers tab**
Inside the exam, click the **Centers** tab. This displays all centers currently assigned to the exam in a table with the following columns:
* **Center** - the center name and center code.
* **Step** - the assessment step the center is assigned to.
* **Status** - the current status of the center.
* **Location** - the center's physical address, displayed as a clickable link.
* **Contact** - the name and email address of the center contact person.
* **Capacity** - the number of seats available at the center for this exam.
* **Next 14 days distribution** - a visual bar showing the booking distribution across the next 14 days.
**3. Click the Remove Center icon**
In the rightmost column of the row for the center you want to remove, click the **delete icon**. Hovering over the icon shows a **Remove Center** tooltip confirming the action.
***
**Additional Tips**
* Removing a center from an exam only unlinks it from that specific exam - it does not delete the center from your tenant or affect its availability in other exams.
* The same center can appear multiple times in the Centers tab if it has been assigned to more than one assessment step. Make sure you are removing the correct row - check the **Step** column before clicking the delete icon.
* If the center has existing candidate bookings, check with your platform administrator before removing it to avoid disrupting scheduled sessions.
# How to create an exam using a template
Source: https://docs.talview.com/content-and-exam-admins/assessment-and-exam-coordinators/exam-coordinators/How-to/exam-setup-and-candidate-invitation/how-to-create-an-exam-using-a-template
As a coordinator, setting up an exam is the first step before you can invite candidates or manage schedules. The Coordinator Console lets you create a new exam by selecting from a set of pre-configured workflow templates for your tenant, so you don't have to configure the exam structure from scratch. In this article, you will learn how to create an exam using a template in the Coordinator Console.
**Before You Begin**
Make sure you have:
* Coordinator role access on your Talview account.
* The exam name and exam code ready.
* The assessment catalog and flow template you want to use for each step.
***
#### Step-by-Step Guide
**1. Go to the Exams list and click Add Exam**
From the Coordinator Console, navigate to the **Exams** section using the left sidebar. The Exams list shows all existing exams with their name, exam code, status, configuration template, and creation date.
In the top-right corner, click **+ Add Exam**.
**2. Select a workflow template**
A **Select Workflow** panel opens on the right. It displays the pre-configured workflow templates available for your tenant.
The available templates are configured specifically for your tenant and may vary. Each template shows its name, a brief description, and the number of steps it contains. Choose the template that matches your exam structure and validity window configuration, then click **Next**.
* **Only Assessment Step (Invite based window)** - 1 step.
* **Only Assessment Step (defined exam window)** - 1 step.
* **Enrollment and Assessment Step (Invite based window)** - 2 steps.
* **Enrollment and Assessment Step (defined exam window)** - 2 steps.
**3. Enter the exam name and exam code**
The panel updates to the **Add Exam** form. At the top, you'll see a tag showing the workflow you selected.
Fill in the following fields:
* **Exam Name** - the name of the exam as it will appear to candidates.
* **Exam Code** - a unique code to identify this exam.
**4. Configure the assessment step**
Below the exam details, you'll see a section for each assessment step defined in the template. Each step has two fields to configure:
* **Assessment Catalog** - click the dropdown and select the catalog you want to load questions from for this step.
* **Flow** - click the dropdown and select the flow template that defines the candidate experience for this step.
For multi-step exams, repeat this configuration for each step.
**5. Click Add**
Once all fields are filled in, click **Add** to create the exam. The panel closes and the new exam appears at the top of the Exams list with an **Active** status.
***
**Additional Tips**
* The exam code must be unique across your tenant. If the code is already in use, the system will show an inline error and prevent you from proceeding.
* The workflow template determines how many steps your exam has. Once the exam is created, the template structure cannot be changed, if you need a different structure, create a new exam with the correct template.
* The Assessment Catalog and Flow dropdowns only show items that have been configured for your tenant. If the catalog or flow you need isn't listed, contact your customer support manager.
# How to invite candidates to an exam
Source: https://docs.talview.com/content-and-exam-admins/assessment-and-exam-coordinators/exam-coordinators/How-to/exam-setup-and-candidate-invitation/how-to-invite-candidates-to-an-exam
As a coordinator, inviting candidates is how you bring them into an exam workflow and trigger their invitation email. Talview's Coordinator Console lets you invite candidates directly from the assessment view, either by adding them manually one at a time, or by uploading a bulk list using a pre-formatted template.
In this article, you will learn how to invite candidates to an exam in the Coordinator Console.
**Before You Begin**
Make sure you have:
* Coordinator role access on your Talview account.
* An active exam with at least one workflow step configured. If you haven't created an exam yet, see How to create an exam using a template.
***
### Step-by-Step Guide
**1. Open the exam from the Exams list**
From the Coordinator Console, navigate to the **Exams** section using the left sidebar. The Exams list shows all active exams with their name, exam code, configuration template, and creation date.
Click on the exam you want to invite candidates to. This opens the exam's assessment view.
**2. Click the Invite button**
Inside the exam, you'll see a tab for each assessment step. The tab also shows the current candidate count in brackets, when no candidates have been added yet.
In the top-right corner, click **Invite**. This opens the Invite panel on the right side of the screen.
The panel shows the following pre-filled, read-only fields at the top:
* **Workflow** - auto-populated with the current exam's workflow ID.
* **Step** - auto-populated with the current assessment step name.
**3. Set the last date to attend**
The **Last Date to Attend** field only appears in the Invite panel when the exam is configured with fixed validity windows at the exam level. If this field does not appear in your invite panel, skip this step.
If the field is visible, click the calendar icon to open the date and time picker. Select the date by which candidates must complete the exam, then select a time from the list on the right. Click **Apply** to confirm.
This sets the deadline that applies to all candidates being invited in this batch. For more details on this field, see How to set the last date to attend for candidates.
If you leave the Last Date to Attend field empty, the invitation link remains open until the candidate completes the exam. Invitations are sent based on the coordinator's system time zone.
**4. Add candidates**
You have two options to add candidates:
* **Manually add candidates** - Fill in the candidate details in the row provided:
Click the **+** button on the right to add the candidate to the list. A new empty row appears at the top for the next candidate. The panel header updates to show the current count, for example, **Invite (1 Candidate)**.
Repeat this for each additional candidate you want to add.
1. **Name** - required.
2. **External ID** - optional. Use this to map the candidate to an ID in your external system.
3. **Email Address** - required. Must be a valid, unique email address.
4. **Phone Number** - optional.
* **Bulk upload via template** - Click **Download Template** to download a pre-formatted file. Fill in the candidate details and save the file. Then click **Upload** to import the list. After upload, the panel updates to show all imported candidates.
You can also mix both methods - upload a bulk list first, then manually add more candidates before sending the invitations.
**5. Click Invite**
Once you've added at least one candidate, click **Invite** to send the invitations. The panel closes and the assessment view refreshes. The tab updates to reflect the new candidate count and each invited candidate appears in the list with an **Invited** status.
**Additional Tip**
* The **Invite** button stays disabled until at least one candidate with a valid email address has been added to the list.
* If a candidate's email already exists in the system, the existing candidate record is reused, no duplicate is created.
* You can track candidate progress - including exam time, score, and integrity outcome, directly from the assessment view once candidates begin and complete their exam.
***
# How to re-invite a candidate to an exam
Source: https://docs.talview.com/content-and-exam-admins/assessment-and-exam-coordinators/exam-coordinators/How-to/exam-setup-and-candidate-invitation/how-to-re-invite-a-candidate-to-an-exam
There are times when a candidate needs another opportunity to take an assessment, whether their previous invitation expired, they didn't show up, or they need a fresh attempt after completing or being suspended. Talview's Coordinator Console lets you re-invite any candidate regardless of their current enrollment status, without modifying or losing any data from their previous attempts.
In this article, you will learn how to send a fresh invitation to a candidate who already has an existing enrollment.
**Before You Begin**
Make sure you have:
* Coordinator role access on your Talview account.
* An active exam with at least one candidate already invited or enrolled at a workflow step.
***
### Step-by-Step Guide
**1. Open the exam and navigate to the assessment step**
From the **Exams** list, click on the exam containing the candidate you want to re-invite. Navigate to the workflow step tab where the candidate's existing enrollment is listed.
**2. Click Invite**
Click the **Invite** button on the top-right of the candidate list - the same button you use for sending original invitations.
**3. Enter the candidate's details**
In the invite side panel, add the candidate's details as you would for a new invitation. Enter their **Email Address** (required) along with any other details like name or phone number.
If the candidate is currently in an **Invited** status (meaning they already have an active, unused invitation), the system may show a non-blocking informational notice letting you know an active invitation already exists. You can proceed regardless, this notice is informational only and does not prevent the re-invite.
**4. Optionally set a new deadline**
If the exam has a **Last Date to Attend** field, you can set a new deadline for this re-invite. This deadline applies only to the new enrollment and does not affect the deadline on any previous enrollment.
**5. Click Invite to send the fresh invitation**
Click **Invite** to complete the re-invitation. The candidate receives a fresh invitation email with a new access link tied to the new enrollment.
***
**Additional Tips**
* Re-inviting does not reset, cancel, or modify the candidate's existing enrollment. Think of it as creating a completely fresh start for the candidate while preserving the full history of their previous attempts.
* If you need to track how many times a candidate has been invited, look at the multiple enrollment rows in the candidate list, each one represents a separate invitation.
* The re-invite flow uses the same **Invite** button and side panel as the original invite. There is no separate "re-invite" action the system automatically handles the creation of a new enrollment when it detects the candidate already exists at that step.
* You can set a different deadline for each re-invite, giving you flexibility to adjust the access window based on the situation.
# How to set an invitation deadline for candidates
Source: https://docs.talview.com/content-and-exam-admins/assessment-and-exam-coordinators/exam-coordinators/How-to/exam-setup-and-candidate-invitation/how-to-set-an-invitation-deadline-for-candidates
When inviting candidates to an exam, you may need to give specific candidates a different access window than what the exam is configured with by default. Coordinator console lets you set an optional invitation deadline, referred to as **Valid Till** that overrides the default exam window for that particular invite. In this article, you will learn how to set, extend, or shorten the access window for individual candidates at the time of inviting them.
**Before You Begin**
Make sure you have:
* Coordinator role access on your Talview account.
* An active exam to invite candidates to.
***
### Step-by-Step Guide
**1. Open the Invite panel**
From inside an exam, navigate to the assessment step where you want to invite candidates. Click the **Invite** button on the top-right to open the invite side panel.
**2. Locate the Valid Till field**
In the invite panel, you'll see a **Last Date to Attend** field with a date-time picker. This field is optional, you don't need to fill it in to send an invitation.
**3. Set a deadline**
Click the calendar icon next to the **Last Date to Attend** field. A date picker opens alongside a time selector.
* Select a **date** from the calendar. Only future dates are selectable - past dates are disabled.
* Select a **time** from the list on the right side of the picker.
* Click **Apply** to confirm your selection.
The selected date and time will appear in the field (e.g., `08/05/2026 1:00 AM`).
**4. Add candidates and send the invitation**
After setting the deadline, add your candidates (manually or via bulk upload) and click **Invite**. The deadline you set applies to all candidates in this batch.
***
### What happens after the deadline is set
* The candidate can access the exam only until the deadline you specified. Once the deadline passes, the candidate sees a message indicating their invitation has expired and can no longer start or continue the exam.
* The deadline you set is invite-based — the candidate must complete the entire exam process within the specified deadline. Once the deadline passes, the candidate will no longer be able to access or continue the exam..
* The deadline is visible in the coordinator's candidate list, so you can always check what window a candidate is working within.
***
### What happens when no deadline is set
* If you leave the **Last Date to Attend** field empty and send the invitation, the candidate's access window falls back to the default exam window configured at the exam level.
**Additional Tips**
* You can use the deadline to **extend** the exam window, for example, giving a candidate extra time due to special circumstances or to **shorten** it for time-sensitive batches.
* When re-inviting a candidate, you can set a new deadline for the new enrollment. The deadline on any previous enrollment is not affected.
* The timezone displayed in the invite panel reflects your logged-in system timezone. Make sure this is correct before setting a deadline, especially when inviting candidates across regions.
* If you need to change a candidate's deadline after the invitation has been sent, you'll need to re-invite them with a new deadline.
# How to filter the exams list in the coordinator console
Source: https://docs.talview.com/content-and-exam-admins/assessment-and-exam-coordinators/exam-coordinators/How-to/getting-started/how-to-filter-the-exams-list-in-the-coordinator-console
The Exams list in the Coordinator Console displays all exams configured for your tenant. When you manage a large number of exams, filters help you quickly locate specific exams by name, course, or status.
In this article, you will learn how to filter the exams list in the Coordinator Console.
***
### Step-by-Step Guide
**1. Navigate to the Exams list**
From the Coordinator Console, navigate to the **Exams** section using the left sidebar. The Exams list displays all exams configured for your tenant with columns for Exam, Course, Status, Configuration Template, and Created on.
**2. Click the filter icon**
In the top-right area of the Exams list, click the **filter icon** (next to the Search exams bar). A **Filters** dropdown opens with the following options:
* **Exam Name** - filter by the name of the exam.
* **Course** - filter by the course linked to the exam.
* **Status** - filter by the current status of the exam (e.g., Active).
**3. Select a filter**
Click on the filter you want to apply. Depending on the filter type, a set of options or an input field will appear. Select or enter your criteria to apply the filter.
Use the **search bar** at the top of the Filters dropdown to quickly find a specific filter option.
**4. Review the filtered results**
The Exams list updates to show only the exams that match your selected filters. You can apply multiple filters at the same time to further narrow down the results.
**5. Clear the filters**
To remove the filters and return to the full exams list, click the filter icon again and clear your selections.
**Additional Tips**
* Use the **Search exams** bar alongside filters for more precise results - for example, search for a specific exam name while filtering by Status.
* The **Status** filter is useful when you want to view only active exams or identify exams in a specific state.
* The Exams list is paginated - use the page navigation controls at the bottom right to move between pages. The total number of pages is shown next to the page number (e.g., Page 1 - 3).
* Click **Export** to download the filtered exams list for offline reference or reporting.
***
# How to view the exams list in the coordinator console
Source: https://docs.talview.com/content-and-exam-admins/assessment-and-exam-coordinators/exam-coordinators/How-to/getting-started/how-to-view-the-exams-list-in-the-coordinator-console
The Exams list is the starting point in Talview's Coordinator Console. It gives you an overview of all exams set up for your tenant and lets you navigate into any exam to manage candidates, centers, and schedules. In this article, you will learn how to access and navigate the Exams list in the Coordinator Console.
***
### Step-by-Step Guide
**1. Navigate to the Exams section**
After logging in, use the left sidebar to navigate to the **Exams** section. This opens the Exams list, the main landing page for exam management.
**2. Review the Exams table**
The Exams list displays all exams configured for your tenant in a table with the following columns:
* **Exam** - the exam name and exam code displayed together. The exam code is the unique identifier visible to candidates.
* **Course** - the course linked to the exam, if applicable.
* **Status** - the current state of the exam, Active exams are shown with a green **Active** label.
* **Configuration Template** - the exam security template configured for the exam.
* **Created on** - the date and time the exam was created.
**3. Search for an exam**
Use the **Search exams** bar at the top right to find a specific exam by name or exam code.
**4. Filter or export the list**
* Click the **filter icon** next to the search bar to apply filters to the list.
* Click **Export** to download the exams list.
**5. Open an exam**
Click on any exam row to open that exam and access its assessment view, centers, and schedules.
**Additional Tips**
* The Exams list is paginated. Use the **Rows per page** control at the bottom right to adjust how many exams are shown per page and use the page navigation arrows to move between pages.
* Newly created exams appear at the top of the list with an **Active** status by default.
* The **Configuration Template** column shows the exam security template configured for the exam.
***
# How to expand and collapse the Form column group
Source: https://docs.talview.com/content-and-exam-admins/assessment-and-exam-coordinators/exam-coordinators/How-to/managing-enrollments/how-to-expand-and-collapse-the-form-column-group
The Form column group in the Enrollment List View shows candidate-submitted enrollment form data. By default, the group is collapsed to keep the table compact. You can expand it to view all form fields, and collapse it again when you're done. In this article, you will learn how to expand and collapse the Form column group in the Enrollment List View.
**Before You Begin**
Make sure you have:
* Coordinator role access on your Talview account.
* Opened an exam and navigated to the **Enrollment** tab. See How to navigate to the Enrollment List View for the full walkthrough.
***
### Step-by-Step Guide
**1. Scroll to the Form column group**
In the Enrollment List View, scroll horizontally to the right until you see the **Form** header spanning a set of columns on the right side of the table. In the collapsed state, only the first two columns - **DOB** and **Contact No** - are visible under the Form header.
**2. Click the + icon to expand**
Click the **+ icon** next to the **Form** label in the column group header. The Form group expands to reveal all available form columns, which may include:
* DOB
* Contact No
* City
* College Name
* Languages Known
* Resume
* Photo
**3. Review the form data**
With the Form group expanded, you can see all candidate-submitted form details inline in the table without leaving the Enrollment List View.
**4. Click the − icon to collapse**
When you no longer need to view the form details, click the **− icon** next to the **Form** label to collapse the group back to its compact state. Only DOB and Contact No will remain visible.
***
**Additional Tips**
* The columns shown in the Form group depend on the enrollment form configured for your program. If certain fields are not part of your program's form, those columns will not appear even in the expanded state.
* Expanding the Form group is useful when you need to verify candidate details - such as checking a candidate's college name or reviewing their uploaded resume, before approving their enrollment.
# How to filter enrollments in the coordinator console
Source: https://docs.talview.com/content-and-exam-admins/assessment-and-exam-coordinators/exam-coordinators/How-to/managing-enrollments/how-to-filter-enrollments-in-the-coordinator-console
The Enrollments tab in the Coordinator Console gives you a consolidated view of all candidates enrolled in an exam across all assessment steps. In this article, you will learn how to filter enrollments in the Coordinator Console.
**Before You Begin**
Make sure you have:
* Coordinator role access on your Talview account.
* An active exam with at least one candidate enrolled.
***
### Step-by-Step Guide
**1. Open the exam from the Exams list**
From the Coordinator Console, navigate to the **Exams** section using the left sidebar. Click on the exam whose enrollments you want to filter.
**2. Go to the Enrollments tab**
Inside the exam, click the **Enrollments** tab. This displays all candidates enrolled in the exam in a table with the following columns:
* **Candidate Name** - the candidate's full name and email address.
* **Accommodations** - icons indicating any special accommodations configured for the candidate, such as extended time, extra breaks, or assistive tools.
* **Enrollment Status** - the candidate's current status (e.g., Invited).
* **Registration Date** - the date and time the candidate was registered.
* **Result** - the candidate's result, once available.
* **Center** - the center the candidate is assigned to.
**3. Click the filter icon**
In the top-right area of the Enrollments tab, click the **filter icon** (next to the Search enrollments bar). A **Filters** dropdown opens with the following options:
* **Enrollment status** - filter by the candidate's current enrollment status (e.g., Invited, Registered, Completed).
* **Registration date** - filter by the date the candidate was registered.
* **Exam date** - filter by the date of the candidate's scheduled exam.
* **Center** - filter by the center the candidate is assigned to.
* **Accommodations** - filter by candidates who have specific accommodations configured.
**4. Select a filter**
Click on the filter you want to apply. Depending on the filter type, a set of options or a date picker will appear. Select your criteria to apply the filter.
Use the **search bar** at the top of the Filters dropdown to quickly find a specific filter option if the list is long.
**5. Review the filtered results**
The Enrollments table updates to show only the candidates that match your selected filters. You can apply multiple filters at the same time to further narrow down the results.
**6. Clear the filters**
To remove the filters and return to the full enrollments list, click the filter icon again and clear your selections.
***
**Additional Tips**
* Use the **Search enrollments** bar alongside filters for even more precise results - for example, search for a candidate by name while filtering by Enrollment status.
* The **Accommodations** filter is particularly useful when you need to identify candidates who require special arrangements before an exam date.
* The **Exam date** filter helps you focus on candidates scheduled for a specific day - useful when managing large cohorts across multiple slots.
* Click **Export** to download the filtered enrollments list as a file for offline review or reporting.
# How to navigate to the Enrollment List View
Source: https://docs.talview.com/content-and-exam-admins/assessment-and-exam-coordinators/exam-coordinators/How-to/managing-enrollments/how-to-navigate-to-the-enrollment-list-view
The Enrollment List View is where coordinators get a consolidated view of all candidates enrolled in an exam. It shows each candidate's enrollment status, eligibility, current step in the exam journey, payment status, ID verification, exam center, and more — all in one scrollable table. In this article, you will learn how to navigate to the Enrollment List View in the Coordinator Console.
**Before You Begin**
Make sure you have:
* Coordinator role access on your Talview account.
* At least one active exam with candidates enrolled.
***
### Step-by-Step Guide
**1. Log in to the Coordinator Console**
Open the Coordinator Console and log in with your coordinator credentials.
**2. Navigate to the Exams section**
Using the left sidebar, click **Exams**. The Exams list opens, showing all active exams configured for your tenant.
**3. Select an exam**
Click on the exam you want to manage. This opens the exam's detail view.
**4. Click the Enrollment tab**
Inside the exam, you will see a row of tabs at the top - one for each assessment step in the exam. The first tab is always **Enrollment**.
Click the **Enrollment** tab to open the Enrollment List View.
***
### What you'll see in the Enrollment List View
The Enrollment List View displays all candidates enrolled in the exam in a horizontally scrollable table. The following columns are available:
* **Candidate Name** - the candidate's photo, full name, email address, and any accommodation icons. Click the expand arrow to view more candidate details.
* **Enrollment Status** - the candidate's current enrollment status displayed as a colour-coded pill (e.g., Invited, Registered, Approved, Completed, Rejected, Expired, Withdrawn).
* **External ID** - the candidate's external reference ID.
* **Eligibility** - an icon indicating whether the candidate is eligible (✓), not eligible (✗), or pending eligibility review (ⓘ).
* **Current Step** - the candidate's current position in the exam workflow along with the relevant date.
* **Payment** - the payment amount and status (e.g., \$50 / Paid, \$150 / Pending, \$150 / Failed, \$0 / Voucher).
* **ID** - the candidate's ID verification status shown as a colour-coded icon (green = verified, red = failed).
* **Exam Center** - the name and location of the center the candidate is assigned to. If multiple centers are assigned, a **+1 more** link appears.
* **Source** - how the candidate was enrolled, shown as an icon (e.g., invited by coordinator, self-registered, partner).
* **Enrolled On** - the date the candidate was enrolled.
* **Invited by** - the name and date of the coordinator who invited the candidate, if applicable.
* **Form** - additional candidate details including Date of Birth (DOB) and Contact Number.
Each row also has a **menu (⋮)** on the right for candidate-level actions.
***
### Other actions available from this view
From the Enrollment List View you can:
* **Search** for a specific candidate using the search bar at the top right.
* **Filter** the list by Enrollment Status, Eligibility, Current Step, Payment, ID, Source, Enrolled On, Invited by, DOB, City, or Languages Known using the filter icon.
* **Invite** new candidates using the **Invite** button at the top right.
* **Switch between assessment step tabs** - click any workflow tabs to view candidates at that specific step. The number in brackets shows the candidate count for each step.
***
**Additional Tips**
* The Enrollment tab shows all candidates across the full enrollment lifecycle in one place - use the Enrollment Status filter to focus on specific groups, such as candidates awaiting approval or those whose enrollments have expired.
* The table is horizontally scrollable - scroll right to see additional columns like Enrolled On, Invited by, and Form details.
* The candidate count in each step tab gives you a quick overview of how many candidates are at each stage of the exam before you click into it.
* Clicking the expand arrow (>) next to a candidate's name reveals additional details about that candidate inline.
# How to search and filter enrollments in the Enrollment List View
Source: https://docs.talview.com/content-and-exam-admins/assessment-and-exam-coordinators/exam-coordinators/How-to/managing-enrollments/how-to-search-and-filter-enrollments-in-the-enrollment-list-view
When managing a large number of candidates, searching and filtering helps you quickly find the candidates you need without scrolling through the entire list. Talview's Coordinator Console lets you search by candidate name or email, and filter by a wide range of criteria, from enrollment status and payment to city and languages known. In this article, you will learn how to search and filter enrollments in the Enrollment List View.
**Before You Begin**
Make sure you have:
* Coordinator role access on your Talview account.
* Opened an exam and navigated to the **Enrollment** tab.
***
### How to search for a candidate
Use the **Search** bar at the top right of the Enrollment tab to find a specific candidate. Type the candidate's name or email address. The table updates in real time to show only matching candidates.
***
### How to filter enrollments
**1. Click the filter icon**
Click the **filter icon** next to the Search bar at the top right of the Enrollment tab. A filter dropdown opens showing all available filter options.
**2. Select a filter**
Click on the filter you want to apply. The available filters are:
**Enrollment Status**
Filter by the candidate's current enrollment status. Select one or more of the following:
* Invited
* Registered
* Approved
* Completed
* Rejected
* Expired
* Withdrawn
**Eligibility**
Filter by the candidate's eligibility state. Select one or more of the following:
* Eligible
* Not Eligible
* Eligibility Review Pending
**Current Step**
Filter by where the candidate currently is in the exam workflow. Select one or more of the following:
* Enrollment
* Booking
* Test
* Certification
**Payment**
Filter by the candidate's payment status. Select one or more of the following:
* Paid
* Sponsored
* Pending
* Failed
**ID**
Filter by the candidate's ID verification status. Select one or more of the following:
* ID Verified
* ID Verification Pending
* ID Verification Failed
**Source**
Filter by how the candidate was enrolled. Select one or more of the following:
* Self
* Invited
* Partner
**Enrolled On**
Filter by the date the candidate was enrolled. Options include:
* Last week
* This month
* Last month
* Quarterly
* Custom - select a specific date range using the two-month calendar picker. Click **Apply** to confirm, or **Clear** to reset.
**Invited by**
Filter by the coordinator who invited the candidate. A searchable list of coordinator names is shown.
**DOB**
Filter by the candidate's date of birth. Uses the same date range picker as Enrolled On.
**City**
Filter by the candidate's city. A searchable list of city names is shown.
**Languages Known**
Filter by the candidate's known languages. A searchable list of languages is shown.
**3. Apply multiple filters**
You can select multiple filters at the same time to narrow down results further - for example, filtering by Enrollment Status = Approved and Current Step = Booking to find approved candidates who are in the process of booking a slot.
**4. Review the filtered results**
The Enrollment table updates automatically to show only candidates matching your selected filters.
**5. Clear the filters**
To remove all filters and return to the full list, click the filter icon again and clear your selections. For date-based filters, click **Clear** inside the calendar picker before closing.
***
**Additional Tips**
* Use **Search** and **filters together** for the most precise results, for example, search for a candidate name while filtering by Payment = Failed to quickly locate a specific candidate with a payment issue.
* The **Enrolled On** and **DOB** filters both support a **Custom** date range, use this when you need to filter within a specific window that doesn't match the preset options (Last week, This month, etc.).
* Use the **Invited by** filter to view candidates invited by a specific coordinator, helpful when managing large teams where multiple coordinators are sending invitations.
# What do the enrollment status labels mean
Source: https://docs.talview.com/content-and-exam-admins/assessment-and-exam-coordinators/exam-coordinators/How-to/managing-enrollments/what-do-the-enrollment-status-labels-mean
In the Coordinator Console, every candidate in the Enrollment tab has an **Enrollment Status** label that shows where they currently stand in the exam lifecycle. These labels are displayed as colour-coded pills, making it easy to quickly assess the state of your candidate pool at a glance. In this article, you will learn what each enrollment status label means.
***
### How status labels are colour coded
Enrollment status pills use colour to indicate the nature of the status:
* **Grey** - neutral or in-progress states (e.g. Invited, Registered, Withdrawn)
* **Green** - positive states indicating progression or completion (e.g. Approved, Completed)
* **Red** - negative or terminal states requiring attention (e.g. Rejected, Expired)
***
### Enrollment status labels
### Active statuses
These statuses indicate that the candidate is currently in the enrollment lifecycle.
| Status | Colour | What it means |
| :------------- | :----- | :------------------------------------------------------------------------------------------------------------------------------ |
| **Invited** | Grey | The candidate has been sent an invitation to enroll for the exam but has not yet taken any action. |
| **Registered** | Grey | The candidate has completed the enrollment steps and is awaiting coordinator approval before proceeding. |
| **Approved** | Green | The candidate's enrollment has been reviewed and approved. They are cleared to proceed with booking a slot and taking the exam. |
### Terminal statuses
These statuses indicate that the candidate's enrollment has reached a final state.
| Status | Colour | What it means |
| :------------ | :----- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Completed** | Green | The candidate has successfully completed the exam and the enrollment lifecycle has concluded. |
| **Rejected** | Red | The coordinator has rejected the candidate's enrollment. Only reachable from the Registered status. |
| **Expired** | Red | The candidate did not complete the exam within their defined eligibility window. |
| **Withdrawn** | Grey | The candidate has withdrawn from the exam entirely. This is distinct from a booking cancellation - a withdrawn candidate has exited the enrollment lifecycle, not just a specific slot. |
***
### How to use enrollment status in the Enrollment tab
The **Enrollment Status** column is always visible in the Enrollment tab. Each candidate's current status is shown as a pill in this column alongside other key details like Eligibility, Current Step, Payment, and ID verification status.
To view only candidates with a specific enrollment status, use the **Enrollment Status** filter. Click the filter icon at the top right of the Enrollment tab, select **Enrollment Status**, and check the statuses you want to filter by. See How to filter enrollments in the coordinator console for the full walkthrough.
***
**Additional Tips**
The Enrollment Status column updates automatically as candidates progress through the lifecycle, you don't need to refresh the page manually.
Use the colour coding to quickly scan for candidates who need attention - red pills (Rejected, Expired) indicate candidates who may need follow-up action.
**Rejected** and **Expired** are terminal states - no further enrollment actions can be taken on these candidates unless they are re-invited.
**Withdrawn** is different from a booking cancellation. A withdrawn candidate has fully exited the exam - they are not simply removed from a slot.
# What does the Source column show in the Enrollment List View
Source: https://docs.talview.com/content-and-exam-admins/assessment-and-exam-coordinators/exam-coordinators/How-to/managing-enrollments/what-does-the-source-column-show-in-the-enrollment-list-view
The **Source** column in the Enrollment List View tells you how a candidate entered the exam, whether they were invited by a coordinator, registered on their own, or came through an external channel. Understanding the source of each enrollment helps you trace the origin of registrations and manage your candidate pipeline effectively. In this article, you will learn what the Source column shows and what each source value means.
***
### What is the Source column?
The Source column appears in the Enrollment List View and shows an icon indicating how each candidate's enrollment originated. Hovering over the icon reveals additional context, such as the name of the coordinator who invited the candidate and the date of the invitation.
***
### Source values
| Source | What it means |
| :---------- | :------------------------------------------------------------------------------------------------------------------------------- |
| **Invited** | The candidate was directly invited by a coordinator or admin. The invitation was sent manually from the Coordinator Console. |
| **Self** | The candidate enrolled on their own through a self-registration link or portal, without being directly invited by a coordinator. |
| **Partner** | The candidate was enrolled through a partner or agent channel, for example, via a third-party test centre or agency. |
***
### How to use the Source column
**Viewing source information**
The Source column displays an icon for each candidate. Hover over the icon to see additional details - for example, for Invited candidates, the tooltip shows the name of the coordinator who sent the invitation and the date it was sent.
**Filtering by source**
To view only candidates from a specific source, use the **Source** filter in the Enrollment List View. Click the filter icon at the top right, select **Source**, and choose from the available options.
***
**Additional Tips**
* The Source column is useful for auditing enrollment origins, for example, identifying candidates who self-registered vs. those who were directly invited, or tracking which enrollments came through a partner channel.
* If a candidate was invited by bulk upload, the Source value will reflect this rather than showing the individual coordinator's name, since the invitation was part of a batch rather than a direct one-to-one invite.
* Use the **Invited by** column alongside Source to get the full picture of who initiated each enrollment and when.
# What is the Form column group in the Enrollment List View
Source: https://docs.talview.com/content-and-exam-admins/assessment-and-exam-coordinators/exam-coordinators/How-to/managing-enrollments/what-is-the-form-column-group-in-the-enrollment-list-view
The **Form** column group in the Enrollment List View displays the information candidates submitted when they enrolled for the exam. The fields shown here are driven by the custom enrollment form configured for your program, so the columns you see may vary depending on your exam setup. In this article, you will learn what the Form column group is and what it contains.
***
### What is the Form column group?
When candidates enroll for an exam, they typically fill out an enrollment form with personal and academic details. The Form column group surfaces this data directly in the Enrollment List View, so you can review candidate-submitted information without leaving the list.
The Form column group appears as a labelled section header - **Form** - spanning several columns on the right side of the Enrollment table. The columns within it depend on the fields configured in your program's enrollment form, but common examples include:
| Column | What it shows |
| :------------------ | :-------------------------------------------------------------------------------------------- |
| **DOB** | The candidate's date of birth |
| **Contact No** | The candidate's phone number |
| **City** | The candidate's city |
| **College Name** | The candidate's university or institution |
| **Languages Known** | The languages the candidate knows, shown as tags. A candidate can have multiple language tags |
| **Resume** | A document icon linking to the candidate's uploaded resume |
| **Photo** | An image icon showing the candidate's uploaded photo |
***
### Collapsed vs expanded state
The Form column group can be **collapsed** or **expanded** using the icon next to the Form header:
* **Collapsed (default)** - only the first two columns in the group are visible (typically DOB and Contact No). This keeps the table compact when you don't need to review form details.
* **Expanded** - all columns in the Form group are visible. Click the **+ icon** next to the Form header to expand it.
* To collapse it again, click the **− icon** next to the Form header.
***
### Important things to know
* The columns shown in the Form group are configured per program. If your program's enrollment form does not include a particular field, that column will not appear in the Form group.
* File upload fields - such as Resume and Photo - are displayed as icons in the table. Click the icon to view or download the file.
* Candidates who have not submitted a particular field will show a dash (-) in that column.
***
**Additional Tips**
* The Form column group is read-only in the Enrollment List View, you cannot edit candidate form data from here.
* If a candidate has multiple languages listed under Languages Known, all language tags are displayed inline in the same cell.
* Use the Form columns alongside filters like **Languages Known** and **City** to quickly identify candidates with specific attributes - for example, finding all candidates in a specific city or those who speak a particular language.
# How to add a schedule for an assessment step
Source: https://docs.talview.com/content-and-exam-admins/assessment-and-exam-coordinators/exam-coordinators/How-to/schedules/how-to-add-a-schedule-for-an-assessment-step
Schedules define the specific time slots during which candidates can attend an assessment. As an exam administrator, you can control when candidates take an exam by creating one-off or recurring schedule slots, which can be configured across multiple centers. In this article, you will learn how to add a schedule for an assessment step in the Coordinator Console.
**Before You Begin**
Make sure you have:
* Log in to your Talview account and make sure you have coordinator role access.
* An active exam with at least one assessment step configured.
* At least one center added to the exam. Centers must be mapped before schedules can be created for them.
***
### Step-by-Step Guide
**1. Open the exam and go to the assessment step**
From the Coordinator Console, navigate to the **Exams** section and click on the exam you want to schedule. Inside the exam, click on the assessment step tab where you want to add a schedule.
**2. Click + Add Schedule**
In the top-right area of the schedule view, click **+ Add Schedule**. The Add Schedule modal opens.
**3. Set the schedule details**
Fill in the following fields:
* **Start Date** - the date on which this slot should first run. Click the field to open the date picker and select a date.
* **Start Time** - the time the slot begins. Select from the dropdown.
* **End Time** - the time the slot ends. Select from the dropdown.
> Note: All times are in **Asia/Calcutta** timezone, as indicated in the modal. Make sure your selections account for this if your candidates are in a different region.
**4. Set recurrence (optional)**
If you want the slot to repeat on multiple days:
* Toggle the **day-of-week buttons** (M T W T F S S) to select which days the slot should recur on.
* Set the **Until** date - the last date on which this recurring slot should run.
If you only need a one-off slot, leave the day toggles and Until date blank.
**5. Click Create**
Click **Create** to save the schedule. The modal closes and the new slot appears in the schedule table, grouped under its start date. The Capacity and Bookings columns will reflect the center capacity configured for this slot. The capacity for a slot is determined by the number of seats available at the centers mapped to that assessment step — to adjust capacity, update the center configuration in the Centers tab.
**Additional Tips**
* You can create multiple slots for the same assessment step, for example, a morning slot and an afternoon slot on the same day, or daily slots across a full exam window.
* The slot's capacity is determined by the centers mapped to the exam step. If you need to adjust capacity, review the center configuration in the Centers tab.
* For recurring slots, the **Until** date controls how long the recurrence runs. Make sure this aligns with your exam window so candidates don't see slots available outside the intended period.
* To delete a slot, click the delete icon next to it in the schedule table.
***
# How to view schedules for an assessment step
Source: https://docs.talview.com/content-and-exam-admins/assessment-and-exam-coordinators/exam-coordinators/How-to/schedules/how-to-view-schedules-for-an-assessment-step
Schedules define the time slots during which candidates can sit for an assessment at a specific center. You can view all scheduled slots for each assessment step, including center count, capacity, and booking progress. In this article, you will learn how to view schedules for an assessment step in the Coordinator Console.
**Before You Begin**
Make sure you have:
* Log in to your Talview account and make sure you have coordinator role access.
* An active exam with at least one assessment step configured.
***
### Step-by-Step Guide
**1. Open the exam from the Exams list**
From the Coordinator Console, navigate to the **Exams** section using the left sidebar. Click on the exam whose schedules you want to view.
**2. Click on the assessment step tab**
Inside the exam, click on the tab for the assessment step you want to review. This opens the schedule view for that step.
**3. Review the schedule table**
Slots are grouped by date. For each date, the table shows the following columns:
* **Slot** - the time range for the slot (e.g., 9:00 AM – 11:00 AM), displayed as a clickable link. Click it to drill into the candidates booked for that slot.
* **Centers** - the number of centers offering this slot.
* **Capacity** - the total number of seats available across all mapped centers for this slot.
* **Bookings** - a progress bar showing how many candidates are enrolled vs. how many seats remain available.
**4. Use filters or export**
* Click the **filter icon** to filter slots by date, center, or other criteria.
* Click **Export** to download the schedule data.
**5. Add a new schedule**
To add a new slot, click **+ Add Schedule** at the top right.
**Additional Tips**
* Use the Bookings progress bar to quickly identify slots that are nearly full or have low uptake, this helps you decide whether to add capacity or create additional slots.
* Clicking on a slot link gives you a detailed view of all candidates booked in that slot, including their booking status, center assignment, and score (if available).
* If no slots appear in the schedule view, the exam step has not had any schedules created yet. Click **+ Add Schedule** to create the first one.
# How to access a Session playback
Source: https://docs.talview.com/content-and-exam-admins/assessment-and-exam-coordinators/exam-coordinators/How-to/tracking-and-session-review/how-to-access-a-session-playback
Session playback lets coordinators watch a recording of a candidate's exam session after it has been completed. The recording shows multiple streams simultaneously, giving you a comprehensive view of the session. In this article, you will learn how to access session playback for a candidate in the Coordinator Console.
**Before You Begin**
Make sure you have:
* Coordinator role access on your Talview account.
* At least one candidate with a **Completed** status in the assessment tab.
***
#### Step-by-Step Guide
**1. Open the exam from the Exams list**
From the Coordinator Console, navigate to the **Exams** section using the left sidebar. Click on the exam you want to review.
**2. Go to the assessment step tab**
Inside the exam, click the tab for the assessment step you want to review. The tab shows the total candidate count in brackets.
**3. Click on a completed candidate's row**
In the candidate list, find a candidate with a **Completed** status and click on their row. A session details panel opens on the right side of the screen.
**4. Open the Session Summary Report**
In the session details panel, click the **Session Summary Report** icon. The full Session Summary Report page opens.
**5. Click the Session Playback button**
At the top of the Session Summary Report, click the **Session Playback** button. The playback view opens.
***
#### What you'll see in the playback view
The playback view shows the candidate's session across **four streams** simultaneously:
* **Primary** — the main camera feed showing the candidate
* **Secondary** — the feed from the secondary device camera
* **Screenshare** — the candidate's screen during the exam
* **Activity** — a view of the candidate's activity feed captured on their screen & mouse movements
At the bottom of the screen, a **playback timeline** shows the session progress and total duration. Use the standard playback controls at the bottom to play, pause, rewind, or fast-forward through the session.
On the right side, the **Incidents panel** shows all incidents flagged during the session, with their severity level and timestamps. Click on an incident to jump to that point in the session.
The left sidebar of the playback view also gives you quick access to additional session context, including exam and candidate details, candidate submissions from their onboarding, device details, and exam rules.
To return to the Session Summary Report, click **← Back to Report** at the top left of the playback view.
***
#### What coordinators can and cannot do in the playback view
In the coordinator role, the playback view is **read-only**. You can:
* Watch the session across all four streams
* Navigate the playback timeline
* Review the incident list and their timestamps
* View the chat history
The following actions are **not available** to coordinators and are disabled in the view:
* Dismissing individual incidents
* Adding manual events
* Resetting the session
* Assigning a proctor
* Accessing captions and audio waveform controls
***
**Additional Tips**
* Session playback is only available for candidates with a **Completed** status. If a candidate's session was interrupted or is still in progress, the playback may not be available yet.
* To return to the Session Summary Report at any point, click **← Back to Report** at the top left of the playback view.
# How to cancel a candidate's booking
Source: https://docs.talview.com/content-and-exam-admins/assessment-and-exam-coordinators/exam-coordinators/How-to/tracking-and-session-review/how-to-cancel-a-candidates-booking
If a candidate can no longer attend a scheduled slot, or if you cannot accommodate them for their booked slot, you can cancel their booking directly from the slot view in the Coordinator Console. Cancelling a booking removes the candidate's registration for that specific slot without affecting their enrollment in the exam. In this article, you will learn how to cancel a candidate's booking in the Coordinator Console.
**Before You Begin**
Make sure you have:
* Coordinator role access on your Talview account.
* An active exam with at least one schedule slot that has candidate bookings.
***
### Step-by-Step Guide
**1. Open the exam from the Exams list**
From the Coordinator Console, navigate to the **Exams** section using the left sidebar. Click on the exam you want to manage.
**2. Go to the relevant assessment step tab**
Inside the exam, click the tab for the assessment step where the candidate's booking exists.
**3. Click on the slot**
The schedule view shows all slots grouped by date, with columns for Slot, Centers, Capacity, and Bookings. Locate the slot for which you want to cancel a candidate's booking and click the **slot time link** (e.g., 9:00 AM - 6:00 PM). This opens the **Candidates** sub-view for that slot.
**4. Locate the candidate**
The Candidates sub-view shows all candidates booked for that slot with the following columns:
* **Candidate** - the candidate's name and email address.
* **Booking External ID** - the external ID associated with the booking.
* **Status** - the candidate's current booking status (e.g., Registered).
* **Center** - the center the candidate is booked at.
* **Score** - the candidate's score, if available.
Find the candidate whose booking you want to cancel.
**5. Open the three-dot menu**
Click the **menu icon (⋮)** at the right end of the candidate's row. A dropdown appears with two options:
* **Reschedule**
* **Cancel**
**6. Click Cancel**
Click **Cancel**. The candidate's booking for that slot is cancelled.
**Additional Tips**
* Cancelling a booking only removes the candidate from that specific slot, it does not remove them from the exam or cancel their enrollment. The candidate can be rebooked into another slot if needed.
* The Bookings column in the schedule view updates automatically after a cancellation, the available seat count increases to reflect the freed-up capacity.
* If you need to move a candidate to a different slot rather than simply cancelling, use the **Reschedule** option from the same menu instead.
# How to filter the assessment tab in the coordinator console
Source: https://docs.talview.com/content-and-exam-admins/assessment-and-exam-coordinators/exam-coordinators/How-to/tracking-and-session-review/how-to-filter-the-assessment-tab-in-the-coordinator-console
The assessment tab in the Coordinator Console shows all candidates invited to a specific assessment step. When you have a large number of candidates, filters help you quickly narrow down the list by status, score, or risk index. In this article, you will learn how to filter candidates in the assessment tab of the Coordinator Console.
**Before You Begin**
Make sure you have:
* Coordinator role access on your Talview account.
* An active exam with at least one candidate invited to an assessment step.
***
#### Step-by-Step Guide
**1. Open the exam from the Exams list**
From the Coordinator Console, navigate to the **Exams** section using the left sidebar. Click on the exam you want to manage.
**2. Go to the assessment step tab**
Inside the exam, click the tab for the assessment step you want to filter. The tab shows the total candidate count in brackets.
**3. Click the filter icon**
In the top-right area of the assessment tab, click the **filter icon** (next to the Search bar). A filter panel opens on the right with three filter options: **Status**, **Score**, and **Risk Index**.
**4. Select a filter**
**Status**
Filter by the candidate's current status in the assessment. Select one or more of the following:
* **Invited** - candidate has been invited but has not yet started
* **In Progress** - candidate has started the exam
* **Completed** - candidate has finished the exam
* **Selected** - candidate has been selected
* **Hold** - candidate's assessment is on hold
* **Suspended** - candidate's session has been suspended
* **Turned Down** - candidate has been turned down
* **No Show** - candidate did not show up for their scheduled slot
**Score**
Filter by the candidate's score within a defined range. Use the **Min** and **Max** input fields or drag the slider to set your range (0–100). Click **Apply** to confirm or **Cancel** to discard.
**Risk Index**
Filter by the candidate's proctoring risk level. Select one or more of the following:
* **Low** - low likelihood of integrity concerns
* **Needs Review** - session requires coordinator review
* **High** - high likelihood of integrity concerns
**5. Review the filtered results**
The candidate list updates automatically to show only candidates matching your selected filters. You can apply multiple filters at the same time - for example, filtering by Status = Completed and Risk Index = Needs Review to find completed candidates whose sessions require review.
**6. Clear the filters**
To remove all filters and return to the full candidate list, click the filter icon again and clear your selections. For the Score filter, click **Cancel** to discard without applying.
***
**Additional Tips**
* Use the **Search** bar alongside filters for more precise results - for example, search for a candidate by name while filtering by Status = Completed.
* The **Risk Index** filter is particularly useful after a large exam - filter by **Needs Review** or **High** to quickly identify candidates whose sessions require closer inspection before results are finalised.
* The **Score** filter range slider allows you to set precise score thresholds - for example, setting Min = 0 and Max = 50 to find all candidates who scored below 50.
* Click **Export** to download the filtered candidate list for offline reference or reporting.
# How to reschedule a candidate's booking
Source: https://docs.talview.com/content-and-exam-admins/assessment-and-exam-coordinators/exam-coordinators/How-to/tracking-and-session-review/how-to-reschedule-a-candidates-booking
If a candidate needs to move to a different slot, you can reschedule their booking directly from the slot view in the Coordinator Console. Rescheduling reassigns the candidate to a new slot without removing them from the exam.
In this article, you will learn how to reschedule a candidate's booking in the Coordinator Console.
**Before You Begin**
Make sure you have:
* Coordinator role access on your Talview account.
* An active exam with at least one schedule slot that has candidate bookings.
* At least one other available slot for the candidate to be moved to.
***
### Step-by-Step Guide
**1. Open the exam from the Exams list**
From the Coordinator Console, navigate to the **Exams** section using the left sidebar. Click on the exam you want to manage.
**2. Go to the relevant assessment step tab**
Inside the exam, click the tab for the assessment step where the candidate's booking exists - for example, **Listening, Reading & Writing** or **Speaking**.
**3. Click on the slot**
The schedule view shows all slots grouped by date, with columns for Slot, Centers, Capacity, and Bookings. Locate the slot the candidate is currently booked in and click the **slot time link** (e.g., 9:00 AM - 6:00 PM). This opens the **Candidates** sub-view for that slot.
**4. Locate the candidate**
The Candidates sub-view shows all candidates booked for that slot with the following columns:
* **Candidate** - the candidate's name and email address.
* **Booking External ID** - the external ID associated with the booking.
* **Status** - the candidate's current booking status (e.g., Registered).
* **Center** - the center the candidate is booked at.
* **Score** - the candidate's score, if available.
Find the candidate whose booking you want to reschedule.
**5. Open the three-dot menu**
Click the **menu icon (⋮)** at the right end of the candidate's row. A dropdown appears with two options:
* **Reschedule**
* **Cancel**
**6. Click Reschedule**
Select the slot you wish to move the candidate to and Click **Reschedule**. The candidate's booking is moved to the new slot.
**Additional Tips**
* Rescheduling a candidate moves them out of their current slot and into a new one, the original slot's available capacity increases by one seat after the reschedule.
* If no other slots are available for the assessment step, create a new schedule before attempting to reschedule.
* If you want to remove a candidate from a slot entirely without moving them to another, use the **Cancel** option from the same three-dot menu instead.
# How to review candidate exam sessions
Source: https://docs.talview.com/content-and-exam-admins/assessment-and-exam-coordinators/exam-coordinators/How-to/tracking-and-session-review/how-to-review-candidate-exam-sessions
After a candidate completes their exam, the Coordinator Console gives you access to their session details, including the session summary, incident count, ID verification, and session playback. In this article, you will learn how to review a candidate's exam session in the Coordinator Console.
**Before You Begin**
Make sure you have:
* Coordinator role access on your Talview account.
* At least one candidate with a **Completed** status in the assessment tab.
***
#### Step-by-Step Guide
**1. Open the exam from the Exams list**
From the Coordinator Console, navigate to the **Exams** section using the left sidebar. Click on the exam you want to review.
**2. Go to the assessment step tab**
Inside the exam, click the tab for the assessment step you want to review. The tab shows the total candidate count in brackets.
**3. Find the completed candidate**
In the candidate list, locate the candidate whose session you want to review. Candidates who have finished their exam will show a **Completed** status in the Status column.
**4. Click on the candidate's row**
Click anywhere on the candidate's row to open their session details panel on the right side of the screen. The panel shows the following information:
**Session Summary card:**
* **Incident Count** - a breakdown of incidents flagged during the session, categorised by severity: High, Medium, and Low
* **Summary** - an AI-generated text overview of the session, covering anomalies detected and their frequency across the timeline, verification outcomes, and the overall severity rating. If the summary is still being prepared, the panel will show "No summary available" - check back shortly
**ID Verification card:**
* Shows the front capture of the candidate's ID document submitted during the session
**Registration Details card:**
* **Booking External ID** - the unique ID for this candidate's booking
* **Email** - the candidate's email address
* **Slot-** the time slot the candidate was booked in
* **Center** - the center the candidate attended
* **Exam Step** - the assessment step the candidate completed
**5. Access the Session Summary Report**
To view the full session details including contributing incidents and candidate submissions, click the **Session Summary Report** icon in the panel. This opens the full Session Summary Report page.
**6. Watch the session playback**
From the Session Summary Report, click the **Session Playback** button to open the full session recording. See How to access session playback for a candidate for the full walkthrough.
> **Note:** If the candidate's session was interrupted before completion, the panel will display an grey banner stating: "This summary and the risk index is based on the session up to the point the candidate's session stopped." Review the available details carefully before making any decisions.
***
**Additional Tips**
* The session details panel is available only for candidates with a **Completed** status, it will not be accessible for candidates who are Invited, In Progress, or in any other state.
* The session summary text may take a few minutes to generate after the exam is completed. If it shows "No summary available", check back shortly.
* Use the Incident Count in the panel as a quick indicator before opening the full Session Summary Report - if all values are zero, the session is likely straightforward to review.
# How to view candidates in the assessment view
Source: https://docs.talview.com/content-and-exam-admins/assessment-and-exam-coordinators/exam-coordinators/How-to/tracking-and-session-review/how-to-view-candidates-in-the-assessment-view
After inviting candidates to an exam, you can monitor their progress directly from the assessment view inside the exam. Talview's Coordinator Console shows you each candidate's status, exam time, score, and risk index, all in one place. In this article, you will learn how to access and navigate the assessment view in the Coordinator Console.
**Before You Begin**
Make sure you have:
* Coordinator role access on your Talview account.
* An active exam with at least one candidate invited.
***
### Step-by-Step Guide
**1. Open the exam from the Exams list**
From the Coordinator Console, navigate to the **Exams** section using the left sidebar. Click on the exam you want to view.
**2. Navigate to the assessment tab**
Inside the exam, you'll see one or more tabs, one for each assessment step in the exam's workflow. Each tab shows the step name and the current candidate count in brackets.
Click the tab for the assessment step you want to review.
**3. Review the candidate table**
The assessment view displays all candidates for that step in a table with the following columns:
* **Candidate Name** - the candidate's full name and email address.
* **Status** - the candidate's current state in the assessment. Possible values include:
* **Invited** - invitation sent, candidate has not yet started.
* **In Progress** - candidate has started the exam.
* **Completed** - candidate has finished the exam.
* **Exam Time** - the time the candidate spent on the exam.
* **Score** - the candidate's score once the exam is completed and results are available.
* **Risk Index** - the proctoring result for the candidate's session.
**4. Search or export**
* Use the **Search** bar at the top right to find a specific candidate by name or email.
* Click **Export** to download the candidate list for this assessment step.
**5. Invite more candidates**
Click the **Invite** button at the top right to invite additional candidates to this assessment step at any time.
**Additional Tips**
* The candidate count in the tab label updates automatically as you invite more candidates.
* For multi-step exams, each step has its own tab and its own candidate list. Candidates are managed independently per step.
* Once a candidate completes their exam, the Score and Risk Index columns will populate with their results, allowing you to review performance and proctoring outcomes from the same view.
***
# Understanding the Session Summary Report
Source: https://docs.talview.com/content-and-exam-admins/assessment-and-exam-coordinators/exam-coordinators/How-to/tracking-and-session-review/understanding-the-session-summary-report
The Session Summary Report is a post-session review tool available in the Coordinator Console that gives coordinators a structured overview of a candidate's exam session after it has been completed. It is generated automatically after a candidate completes their exam and brings together the most important session information in one place, the overall risk level, an AI-generated session summary, candidate submissions, and contributing incidents, helping coordinators come to a decision or issue a result faster. In this article, you will learn what the Session Summary Report is and what it contains.
#### What the report contains
**Header**
At the top of the report, a colour-coded banner displays the overall risk level for the session. The banner colour and icon update based on the risk outcome assigned to the candidate's session.
The header also displays key candidate details including the candidate's name, ID, and enrollment status, giving coordinators the context they need before reviewing the session.
Below the banner, you'll find the **Session Playback** button, which lets you access the full session recording directly from the report.
**Summary**
The Summary section gives you a high-level text overview of the session. It includes:
* A **verification tag** - highlights any verification area that needs attention
* An **AI-generated summary** - a paragraph describing key observations from the session, such as anomalies detected, their frequency, verification outcomes, and the overall severity rating. This summary is intended to give coordinators a quick read of the session before diving into the details
* **Session timeline** - the session start and end timestamps, shown as a vertical timeline
**Candidate Submissions**
This section shows the verification checks completed by the candidate during onboarding. Each check is displayed as an expandable card:
* **Face Capture -** the candidate's face captured at the start of the session. This is compared against the candidate's base image to verify their identity.
* **ID Verification** - shows the outcome of the candidate's ID verification. This includes ID Verification (IDV), which checks the submitted ID document, and Database Verification (DBV), which validates the ID details against an external database.
* **Environment 360** - the candidate's environment scan captured before the session began
Click the dropdown arrow on each card to expand it and view the details.
**Contributing Incidents**
This section lists all incidents that were flagged during the session and contributed to the overall risk rating. A brief description at the top explains what an incident is - a group of related events that occurred during the session within a defined time window.
Each incident card shows:
* **Incident name** - a description of the type of incident detected
* **Severity** - the severity level assigned to the incident, shown as a colour-coded label
* **Duration and event count** - how long the incident lasted and how many individual events were recorded within it
* **Violations identified** - a breakdown of specific violations detected within the incident, grouped by category
* **Why \[severity] explanation** - a plain-language explanation of why the incident was assigned that severity level
* **Video evidence** - thumbnail clips from the session showing the moment the incident was detected. Click the play button to watch the clip inline, or the fullscreen icon to expand it.
> **Note:** In the coordinator role, the incident list is read-only. Actions such as dismissing incidents or adding manual events are not available from this view.
**Additional Tips**
* The Session Summary Report is available only for candidates who have completed their exam session.
* The AI-generated summary may take a few minutes to appear after the session ends. If it is not yet available, check back shortly.
* The **Candidate Submissions** cards are expandable, click the dropdown arrow on each to view the full details of the face capture, ID verification, and environment scan.
* To watch the full session recording, click the **Session Playback** button at the top of the report. See How to access session playback for a candidate for the full walkthrough.
# Coordinator Console FAQs
Source: https://docs.talview.com/content-and-exam-admins/assessment-and-exam-coordinators/exam-coordinators/faqs/coordinator-console-faqs
The Coordinator Console provides a centralized, workflow-scoped view of all exams assigned to a coordinator. From this dashboard, coordinators can monitor candidate sessions, track exam statuses, review incidents, and access session playback and summary reports.
This FAQ section addresses common questions about navigating the console, understanding session statuses, and accessing review artifacts to help coordinators manage exam oversight efficiently.
***
### Getting Started
**Q1. What can I do from the Coordinator Console?**
From this console, coordinators can:
* View exams they are assigned to
* Access the candidate list for each exam
* Track candidate exam and session status
* Review incidents and integrity outcomes
* Access session playback and summary reports
**Q2. Which exams are visible to me?**
As of now, all exams will be visible to the coordinator. Changes will be made further on.
***
### **Exams Table & Candidate List**
**Q1. What information is shown in the Exams table?**
The Exams table displays the candidate information, exam status, integrity outcome and incident status.
**Q2. Where can I see the candidate information?**
As a **Coordinator**, you can view candidate information directly from the **Coordinator Console → Exams → Candidate List view**.
**Q3. Can I search for a specific candidate?**
Yes. You can use the **search bar** to find candidates by name or email ID or you can search in the enrolment table.
**Q4. Can I filter or sort the candidate list?**
Yes. Coordinators can use filters to narrow down candidates based on status, date, or other available parameters (as configured for the exam).
**Q5. Why do I see the same candidate name multiple times?**
A candidate may appear multiple times if:
* They attempted the exam on different dates
* They had multiple sessions (rescheduled or reattempted)
* They were enrolled in multiple workflows under the same exam
* They were enrolled in different exams
***
### **Candidate Status & Meanings**
**Q1. What does “In Progress” mean?**
The candidate has started the exam and the session is currently ongoing.
**Q2. What does “Completed” mean?**
The candidate has successfully finished the exam and the session has ended normally.
**Q3. What does “No Show” mean?**
The candidate did not join the exam within the allowed start window.
**Q4. What does “Terminated” mean?**
The candidate’s session was ended before completion. This could be due to:
* Proctor intervention
* Rule violations
* Technical or policy-related reasons
**Q5. What does “Suspended” mean?**
The candidate violated exam rules and the session outcome was marked as suspended after review.
**Q6. What does “Needs Review” mean?**
The session requires further review by an examiner or administrator due to flagged incidents or integrity concerns.
***
### **Integrity Outcomes**
**Q1. Can coordinators change the integrity outcome?**
A of now they can’t. Coordinators can **view** integrity outcomes but cannot modify them unless granted additional administrative permissions. It will be modified later on.
***
### Session Playback & Reports
**Q1. How do I access session playback?**
Click the **play icon** next to the candidate entry to open the session playback.
**Q2. What does session playback include?**
Session playback may include:
* Candidate video recording
* Screen recording
* Audio recording
* Timeline of incidents and events
* Session summary report
**Q3. Can I download the session recording?**
The coordinator cannot download the session recording.
**Q4. What is the Summary Report?**
Summary report is a written report provided by the proctor for you to quickly know what happened in the session without requiring to review entire video.
**Q5. Who can access the Summary Report?**
Coordinators can view the Summary Report for candidates within their assigned exams.
**Q6. Why are start and end times missing for some candidates?**
Start and end times may be unavailable if:
* The candidate did not start the exam
* The session is still in progress
* The candidate was a no-show
***
### **Incidents & Accommodations**
**Q1. What are incidents?**
Incidents are system- or proctor-detected events such as:
* Multiple faces detected
* Tab switching
* Device changes
* Suspicious behavior
**Q2. Where can I see the number of incidents?**
The **Incidents column** shows the count of incidents recorded for that session.
**Q3. What are accommodations?**
Accommodations indicate special provisions provided to candidates, such as:
* Extra time
* Assistive devices
* Accessibility support
Icons next to the candidate name represent applied accommodations.
***
### **Access & Permissions**
**Q1. Can coordinators edit candidate details?**
Not as of now. The Coordinator Console is a **read-only view** for candidate and session data as of now. Further changes will be made.
**Q2. Can coordinators enroll or remove candidates?**
Unfortunately no, they cannot.
***
### **Technical & Data Questions**
**Q1. What is the UUID shown for each candidate?**
The UUID is a **unique identifier for the candidate’s exam session**, used for tracking and support purposes.
**Q2. Who should I contact if playback fails to load?**
If playback does not load:
* Refresh the page and retry
* Check your internet connection
**Q3. Is the data shown in real time?**
Not as of now. It will get update a few minutes after the exam is finished.
# Getting Started - Exam Administration
Source: https://docs.talview.com/content-and-exam-admins/getting-started
***
Your step-by-step companion to get the most out of Talview. Here you’ll find curated instructions, walkthroughs, and best practices tailored to your role and needs.
Learn how to create exam workflows, invite candidates, and track assessments.
Learn how to add centers, configure time slots, and manage bookings.
Sign up, log in, and access your account using your organization's configured login method
View and manage candidate profiles and track their assessment status.
# Authentication
Source: https://docs.talview.com/graph-api-reference/authentication
How to authenticate your requests to the Talview Graph API
All API requests to Talview must be authenticated using the **OAuth2 Protocol**. This ensures that only authorized systems can access your data and perform operations on the platform.
All queries and endpoints, but the authentication endpoints, require access tokens.
## Authorization Header
Once you have generated an access token, it must be included in the `Authorization` header of every API request as a Bearer token.
```http theme={null}
Authorization: Bearer
```
***
## Generate an Access Token
Talview provides a RESTful, as well as graphQL endpoint to obtain your access tokens. You will need the credentials (Username, Password, and Tenant ID) shared by Talview for your specific environment.
### Request Details
| Configuration | Value |
| :---------------- | :-------------------------- |
| **Host** | `https://api.talview.com` |
| **Method** | `POST` |
| **REST Route** | `/api/rest/auth_user_login` |
| **graphQL Route** | `/v1/graphql` |
### Request Body Schema
| Parameter | Type | Mandatory | Description |
| :---------- | :------ | :-------- | :------------------------------ |
| `username` | String | Yes | Your Talview-provided username. |
| `password` | String | Yes | Your Talview-provided password. |
| `tenant_id` | Integer | Yes | Your unique Talview Tenant ID. |
### RESTful Endpoint
#### Sample Request
```bash cURL theme={null}
curl --request POST \
--url https://api.talview.com/api/rest/auth_user_login \
--header 'Content-Type: application/json' \
--data '{
"username": "username@yourcompany.com",
"password": "SecurePassword",
"tenant_id": 1
}'
```
```json Body theme={null}
{
"username": "username@yourcompany.com",
"password": "SecurePassword",
"tenant_id": 1
}
```
#### Sample Response
On success, the API returns an access token and a refresh token.
```json theme={null}
{
"auth_user_login": {
"success": true,
"error_message": null,
"data": {
"access_token": "eyJhbGciOiJIUzI1NiIsInR5cCI...",
"expires_in": 3600,
"refresh_token": "d9865001-c918-4903-8209-..."
}
}
}
```
### GraphQL Endpoint
You can also obtain tokens using the `auth_user_login` mutation directly through the GraphQL endpoint. This is useful if you prefer to keep all interactions within GraphQL.
#### Sample Request
```bash cURL theme={null}
curl --request POST \
--url https://api.talview.com/v1/graphql \
--header 'Content-Type: application/json' \
--data '{
"query": "mutation MyMutation($password: String, $tenant_id: Int, $username: String) { auth_user_login(data: {password: $password, tenant_id: $tenant_id, username: $username}) { data { access_token expires_in refresh_token } } }",
"variables": {
"username": "username@yourcompany.com",
"password": "SecurePassword",
"tenant_id": 1
}
}'
```
```graphql Mutation theme={null}
mutation MyMutation($password: String = "", $tenant_id: Int = 10, $username: String = "") {
auth_user_login(data: {password: $password, tenant_id: $tenant_id, username: $username}) {
data {
access_token
expires_in
refresh_token
}
}
}
```
```json Variables theme={null}
{
"username": "username@yourcompany.com",
"password": "SecurePassword",
"tenant_id": 1
}
```
#### Sample Response
On success, the API returns an access token and a refresh token.
```json theme={null}
{
"auth_user_login": {
"success": true,
"error_message": null,
"data": {
"access_token": "eyJhbGciOiJIUzI1NiIsInR5cCI...",
"expires_in": 3600,
"refresh_token": "d9865001-c918-4903-8209-..."
}
}
}
```
# Error Codes
Source: https://docs.talview.com/graph-api-reference/error-codes
How to interpret error codes to your requests to the Talview Graph API
The API uses standard HTTP status codes to indicate the result of an authentication or request attempt. Below are the common error structures you may encounter.
***
## HTTP Status Codes
### 400 Bad Request
Returned when variables are missing or the request is malformed.
```json theme={null}
{
"extensions": {
"code": 400,
"traceId": "06b0de7d2a"
},
"message": "expecting a value for non-nullable variable: \"external_id\""
}
```
### 401 Unauthorized
Returned when the access token is missing or invalid.
```json theme={null}
{
"extensions": {
"code": 401,
"traceId": "..."
},
"message": "..."
}
```
**Resolution:** Re-authenticate to obtain a new access token.
### 403 Forbidden
Returned when the provided token is expired or does not have sufficient permissions.
```json theme={null}
{
"extensions": {
"code": 403,
"traceId": "77020d7cb1"
},
"message": "Token has expired"
}
```
### 422 Unprocessable Entity
Returned when the request is well-formed but contains semantic errors or violates business rules (e.g., validation failures).
```json theme={null}
{
"extensions": {
"code": 422,
"traceId": "93bad0e604"
},
"message": "Candidate Creation failed"
}
```
### 429 Too Many Requests
Returned when the request frequency exceeds the allowed rate limit.
```json theme={null}
{
"extensions": {
"code": 429,
"traceId": "..."
},
"message": "..."
}
```
**Resolution:** Implement exponential backoff. For more details, see the [Rate Limiting](/graph-api-reference/rate-limiting) guide.
### 500 Internal Server Error
Returned when an unexpected error occurs on the Talview server.
```json theme={null}
{
"extensions": {
"code": 500,
"traceId": "93bad0e604"
},
"message": "Internal Server Error"
}
```
### 502 Server Timed Out
Returned when an upstream service did not respond in time.
```json theme={null}
{
"extensions": {
"code": 502,
"traceId": "..."
},
"message": "..."
}
```
***
## Business Logic Errors
In GraphQL, a business rule violation may return an HTTP 200 OK status, but the `success` field within the data block will be `false`.
```json theme={null}
{
"data": {
"booking_create": {
"success": false,
"error_message": "No available slots for selected date",
"data": null
}
}
}
```
### Common Logical Error Codes
These specific strings are often returned within the `error_message` field or GraphQL `extensions` block to provide granular detail:
| Error | Description | Resolution |
| :----------------------------- | :------------------------------------------------- | :----------------------------------------------- |
| `VALIDATION_ERROR` | Input data failed schema or logic checks. | Review input parameters and constraints. |
| `SLOT_UNAVAILABLE` | The selected time slot is no longer available. | Refresh slot availability and select a new slot. |
| `BOOKING_NOT_FOUND` | The provided Booking ID does not exist. | Verify the Booking ID is correct. |
| `RESCHEDULE_NOT_ALLOWED` | Reschedule request violates business policy. | Check reschedule eligibility windows. |
| `PAYMENT_REQUIRED` | Payment is required before the action can proceed. | Process the required payment transaction. |
| `IDENTITY_VERIFICATION_FAILED` | Identity documents or photo failed verification. | Review document quality and retry. |
***
## Best Practices
1. **Check `success` first:** Always evaluate the `success` boolean before attempting to access the `data` object.
2. **Handle Actionable Errors:** Display the `error_message` directly to users for errors like `SLOT_UNAVAILABLE`.
3. **Token Management:** Automatically handle 401/403 errors by refreshing the OAuth2 access token.
4. **Logging:** Log the `traceId` provided in the error response to assist Talview support in debugging.
# Filtering
Source: https://docs.talview.com/graph-api-reference/filtering
How to filter results in the Graph API
This page consists of information regarding filtering in GraphQL requests.
## Current Implementation
Filtering is an upcoming feature with this Graph API, and will be implemented soon!
# Getting Started
Source: https://docs.talview.com/graph-api-reference/getting-started
Introduction to the Graph API
The Supergraph is a unified GraphQL API that provides access to all platform services including authentication, booking, delivery, proctoring, and reporting. It serves as the primary integration point for all internal and external systems.
## Base URL
**GraphQL Endpoint:**
`https://api.talview.com/v1/graphql`
**Apollo Studio Explorer:**
[https://studio.apollographql.com/public/talview/variant/current/explorer](https://studio.apollographql.com/public/talview/variant/current/explorer)
## Authentication
All API requests require authentication using OAuth2 Bearer tokens. You must include your access token in the `Authorization` header for all requests.
For detailed instructions on generating and using access tokens, see the [Authentication Guide](/graph-api-reference/authentication).
## Error Handling
The API follows standard GraphQL error conventions. Errors thrown in both RESTful APIs and GraphQL endpoint use HTTP statuses as framework for error codes.
| Status Code | Description |
| :---------- | :------------------------------------------ |
| 200 | Success - OK, request accepted successfully |
| 400 | Bad Request - Invalid query or variables |
| 401 | Unauthorized - missing or invalid token |
| 403 | Forbidden - insufficient permissions |
| 422 | UnprocessableEntity - validation errors |
| 429 | Too many requests - rate limit exceeded |
| 500 | Internal Server Error |
| 502 | Server timed out |
## Schema Definition and Reference
To explore the full capabilities of the Talview Supergraph, developers should refer to the official schema documentation. These resources provide a comprehensive guide to all available queries, mutations, and subscriptions.
* **[Schema Reference](https://studio.apollographql.com/public/talview/variant/current/schema/reference)**: Use this interactive reference to browse types, fields, and arguments defined in the Graph API.
* **[SDL (Schema Definition Language)](https://studio.apollographql.com/public/talview/variant/current/schema/sdl?selectedSchema=%23%40%21api%21%40%23)**: View the full SDL for a deep dive into the underlying schema structure.
We recommend developers consult these references when building integrations to ensure they are utilizing the most up-to-date and efficient data fetching methods.
# Pagination
Source: https://docs.talview.com/graph-api-reference/pagination
How to handle pagination in the Graph API
List queries in the Supergraph API support cursor-based pagination to handle large datasets efficiently.
## Parameters
You can control pagination using the following parameters in your queries:
* **`limit`**: Number of items per page.
* Default: `20`
* Maximum: `100`
* **`offset`**: Number of items to skip.
* **`order_by`**: Sorting criteria.
## Example Query
Here is an example of how to request a paginated list of items:
```graphql theme={null}
query GetScheduledDrives($limit: Int, $offset: Int) {
sch_drive(limit: $limit, offset: $offset, order_by: { start_time: desc }) {
id
name
start_time
end_time
status
}
}
```
## Variables
```json theme={null}
{
"limit": 10,
"offset": 0
}
```
# Rate Limiting
Source: https://docs.talview.com/graph-api-reference/rate-limiting
Understanding and handling API rate limits
## What is Rate Limiting?
Rate limiting is a strategy used to control the amount of incoming and outgoing traffic to a network or API. By limiting the number of requests a user can make within a specific timeframe, we ensure that the Talview platform remains stable, secure, and available for all users.
Without rate limits, a single high-volume user—whether intentional or due to a coding error (like an infinite loop)—could degrade the performance of the system for everyone else.
## Handling Rate Limits
When your integration exceeds the allowed number of requests, the Talview Graph API will return a specific error response.
### HTTP 429 Too Many Requests
If you are rate limited, the API will respond with an **HTTP 429** status code. Your system should be prepared to handle this code gracefully.
## Best Practices
To avoid being rate limited and to ensure a smooth integration, we recommend the following practices:
1. **Implement Exponential Backoff**: If you receive a 429 error, do not retry immediately. Instead, wait for a short period and then retry. If it fails again, increase the wait time exponentially (e.g., 1s, 2s, 4s, 8s).
2. **Optimize Queries**: Use GraphQL's capability to fetch only the data you need. Avoid making multiple small queries if a single, larger query can retrieve the necessary information.
3. **Cache Data**: If you are requesting data that doesn't change frequently (like catalog details or user roles), cache that information on your server instead of requesting it repeatedly.
4. **Batch Operations**: When possible, use bulk operations or mutations rather than individual requests for each item.
## Current Implementation
Rate Limiting is currently being tuned for the Graph API. While we are in this phase, we recommend following the best practices above to ensure your integration is future-proof and resilient.
# Graph API Reference
Source: https://docs.talview.com/graph-api-reference/reference
# Test Instance Created
Source: https://docs.talview.com/graph-api-reference/webhooks/ae/test-instance-created
Triggered when a new test instance (candidate attempt) is created.
For general webhook concepts like bubble-up behavior, payload visibility rules, and versioned snapshots, see [Webhook Concepts](/graph-api-reference/webhooks/concepts).
## Description
This event is triggered when a new test instance (candidate assessment attempt) is created.
## Integration Details
* **Subscription Key**: `ae.test_instance.created`
* **Use Case**: Notify a proctor or recruiter that a candidate has started their assessment.
* **Related Events**: [`ae.test_instance.updated`](/graph-api-reference/webhooks/ae/test-instance-updated)
## Trigger
* **Event Type:** `ae_test_instance_created`
* **Source:** Insertion of a record into the `ti.instance` table.
## Cross-Service References
This payload joins data from multiple services:
* **Candidate** (`can.candidate`): Snapshot of the candidate's profile.
* **Catalog** (`ae.catalog_assessment`): Assessment and catalog metadata.
* **Evaluation** (`tcf.measurement`): Scoring breakdown with attributes and skills.
## Payload Example
```json theme={null}
{
"id": 789,
"external_id": "ext_ti_789",
"old_id": 1234,
"score": null,
"instance_status": "in_progress",
"candidate_id": 101,
"catalog_assessment_id": 202,
"measurement_id": 505,
"session_instance_id": 3001,
"workflow_candidate_step_id": 4001,
"created_at": "2023-11-05T10:00:00Z",
"created_by": 1,
"updated_at": "2023-11-05T10:00:00Z",
"updated_by": 1,
"candidate": {
"id": 101,
"external_id": "ext_can_101",
"user_id": 123,
"email": "candidate@example.com",
"first_name": "Jane",
"last_name": "Doe",
"middle_name": "Marie",
"phone_number": "+19876543210",
"country": "USA",
"is_tnc_accepted": true,
"is_recording_consent_accepted": true,
"resume_file_id": 2001,
"profile_pic_file_id": 3001,
"cf": {}
},
"catalog_assessment": {
"id": 202,
"assessment": {
"id": 303,
"name": "Python Proficiency Test",
"level": "intermediate",
"status": "published",
"created_at": "2023-11-01T10:00:00Z",
"updated_at": "2023-11-01T10:00:00Z"
},
"catalog": {
"id": 404,
"name": "Standard Assessments",
"description": "Standard assessment catalog for technical roles."
}
},
"measurement": {
"id": 505,
"status": "pending",
"time_taken": "00:00:00",
"report_url": null,
"report_file_id": null,
"measured_at": "2023-11-05T10:00:00Z",
"measured_by": null,
"form_instance_id": null,
"measurement_attributes": [
{
"id": 1,
"numerical_score": null,
"percentile_score": null,
"remarks": null,
"description": "Initial state",
"additional_attributes": {},
"created_at": "2023-11-05T10:00:00Z",
"created_by": 1,
"updated_at": "2023-11-05T10:00:00Z",
"updated_by": 1,
"section_configuration_attribute": {
"id": 10,
"type": "numerical",
"recommended_value": 70,
"recommended_ordinal_id": null,
"attribute": {
"id": 10,
"name": "Logical Reasoning",
"attribute_type": "skill",
"is_required": true,
"min_value": 0,
"max_value": 100,
"skill": {
"id": 5,
"name": "Logic"
}
}
},
"ordinal": null
}
]
}
}
```
## Payload Type Showcase
```typescript theme={null}
{
id: number;
external_id: string | null;
old_id: number | null;
score: number | null;
instance_status: string;
candidate_id: number;
catalog_assessment_id: number;
measurement_id: number | null;
session_instance_id: number | null;
workflow_candidate_step_id: number | null;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
candidate: {
id: number;
external_id: string | null;
user_id: number;
email: string;
first_name: string | null;
last_name: string | null;
middle_name: string | null;
phone_number: string | null;
country: string | null;
is_tnc_accepted: boolean;
is_recording_consent_accepted: boolean | null;
resume_file_id: number | null;
profile_pic_file_id: number | null;
cf: Record;
};
catalog_assessment: {
id: number;
assessment: {
id: number;
name: string;
level: string;
status: string;
created_at: string;
updated_at: string;
};
catalog: {
id: number;
name: string;
description: string | null;
};
};
measurement: {
id: number;
status: string;
time_taken: string | null;
report_url: string | null;
report_file_id: number | null;
measured_at: string;
measured_by: number | null;
form_instance_id: number | null;
measurement_attributes: {
id: number;
numerical_score: number | null;
percentile_score: number | null;
remarks: string | null;
description: string | null;
additional_attributes: Record | null;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
section_configuration_attribute: {
id: number;
type: string;
recommended_value: number | null;
recommended_ordinal_id: number | null;
attribute: {
id: number;
name: string;
attribute_type: string;
is_required: boolean;
min_value: number;
max_value: number;
skill: {
id: number;
name: string;
} | null;
};
};
ordinal: {
id: number;
label: string;
value: string;
sort_key: number;
min_value: number | null;
max_value: number | null;
} | null;
}[];
};
}
```
## Field Notes
* `cf` on candidate is JSONB — shape varies per tenant configuration.
* `time_taken` on measurement is a Postgres INTERVAL rendered as a string.
* `additional_attributes` on measurement attributes is JSONB.
* `instance_status` references the `ti.instance_status` enum.
# Test Instance Updated
Source: https://docs.talview.com/graph-api-reference/webhooks/ae/test-instance-updated
Triggered when a test instance is updated (e.g., score is calculated, status changes).
For general webhook concepts like bubble-up behavior, payload visibility rules, and versioned snapshots, see [Webhook Concepts](/graph-api-reference/webhooks/concepts).
## Description
This event is triggered when a test instance is updated — for example, when a score is calculated or the status changes.
## Integration Details
* **Subscription Key**: `ae.test_instance.updated`
* **Use Case**: Automatically fetch results or update a candidate's status in your ATS once a score is available.
* **Related Events**: [`ae.test_instance.created`](/graph-api-reference/webhooks/ae/test-instance-created)
## Trigger
* **Event Type:** `ae_test_instance_updated`
* **Source:** Update of a record in the `ti.instance` table.
## Cross-Service References
This payload joins data from multiple services:
* **Candidate** (`can.candidate`): Snapshot of the candidate's profile.
* **Catalog** (`ae.catalog_assessment`): Assessment and catalog metadata.
* **Evaluation** (`tcf.measurement`): Scoring breakdown with attributes and skills.
## Payload Example
```json theme={null}
{
"id": 789,
"external_id": "ext_ti_789",
"old_id": 1234,
"score": 85,
"instance_status": "completed",
"candidate_id": 101,
"catalog_assessment_id": 202,
"measurement_id": 505,
"session_instance_id": 3001,
"workflow_candidate_step_id": 4001,
"created_at": "2023-11-05T10:00:00Z",
"created_by": 1,
"updated_at": "2023-11-05T10:00:00Z",
"updated_by": 1,
"candidate": {
"id": 101,
"external_id": "ext_can_101",
"user_id": 123,
"email": "candidate@example.com",
"first_name": "Jane",
"last_name": "Doe",
"middle_name": "Marie",
"phone_number": "+19876543210",
"country": "USA",
"is_tnc_accepted": true,
"is_recording_consent_accepted": true,
"resume_file_id": 2001,
"profile_pic_file_id": 3001,
"cf": {}
},
"catalog_assessment": {
"id": 202,
"assessment": {
"id": 303,
"name": "Python Proficiency Test",
"level": "intermediate",
"status": "published",
"created_at": "2023-11-01T10:00:00Z",
"updated_at": "2023-11-01T10:00:00Z"
},
"catalog": {
"id": 404,
"name": "Standard Assessments",
"description": "Standard assessment catalog for technical roles."
}
},
"measurement": {
"id": 505,
"status": "pending",
"time_taken": "00:20:00",
"report_url": "https://reports.example.com/789",
"report_file_id": 999,
"measured_at": "2023-11-05T10:00:00Z",
"measured_by": 1,
"form_instance_id": null,
"measurement_attributes": [
{
"id": 1,
"numerical_score": 85,
"percentile_score": 92,
"remarks": "Strong logic",
"description": "Candidate demonstrated strong analytical skills.",
"additional_attributes": {},
"created_at": "2023-11-05T10:00:00Z",
"created_by": 1,
"updated_at": "2023-11-05T10:00:00Z",
"updated_by": 1,
"section_configuration_attribute": {
"id": 10,
"type": "numerical",
"recommended_value": 70,
"recommended_ordinal_id": null,
"attribute": {
"id": 10,
"name": "Logical Reasoning",
"attribute_type": "skill",
"is_required": true,
"min_value": 0,
"max_value": 100,
"skill": {
"id": 5,
"name": "Logic"
}
}
},
"ordinal": {
"id": 1,
"label": "High",
"value": "85",
"sort_key": 1,
"min_value": 80,
"max_value": null
}
}
]
}
}
```
## Payload Type Showcase
```typescript theme={null}
{
id: number;
external_id: string | null;
old_id: number | null;
score: number | null;
instance_status: string;
candidate_id: number;
catalog_assessment_id: number;
measurement_id: number | null;
session_instance_id: number | null;
workflow_candidate_step_id: number | null;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
candidate: {
id: number;
external_id: string | null;
user_id: number;
email: string;
first_name: string | null;
last_name: string | null;
middle_name: string | null;
phone_number: string | null;
country: string | null;
is_tnc_accepted: boolean;
is_recording_consent_accepted: boolean | null;
resume_file_id: number | null;
profile_pic_file_id: number | null;
cf: Record;
};
catalog_assessment: {
id: number;
assessment: {
id: number;
name: string;
level: string;
status: string;
created_at: string;
updated_at: string;
};
catalog: {
id: number;
name: string;
description: string | null;
};
};
measurement: {
id: number;
status: string;
time_taken: string | null;
report_url: string | null;
report_file_id: number | null;
measured_at: string;
measured_by: number | null;
form_instance_id: number | null;
measurement_attributes: {
id: number;
numerical_score: number | null;
percentile_score: number | null;
remarks: string | null;
description: string | null;
additional_attributes: Record | null;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
section_configuration_attribute: {
id: number;
type: string;
recommended_value: number | null;
recommended_ordinal_id: number | null;
attribute: {
id: number;
name: string;
attribute_type: string;
is_required: boolean;
min_value: number;
max_value: number;
skill: {
id: number;
name: string;
} | null;
};
};
ordinal: {
id: number;
label: string;
value: string;
sort_key: number;
min_value: number | null;
max_value: number | null;
} | null;
}[];
};
}
```
## Field Notes
* `cf` on candidate is JSONB — shape varies per tenant configuration.
* `time_taken` on measurement is a Postgres INTERVAL rendered as a string.
* `additional_attributes` on measurement attributes is JSONB.
* `instance_status` references the `ti.instance_status` enum.
# User Created
Source: https://docs.talview.com/graph-api-reference/webhooks/auth/user-created
Triggered when a new user is created in the authentication system.
For general webhook concepts like bubble-up behavior, payload visibility rules, and versioned snapshots, see [Webhook Concepts](/graph-api-reference/webhooks/concepts).
## Description
This event is triggered when a new user is created in the authentication system.
## Integration Details
* **Subscription Key**: `auth.user.created`
* **Use Case**: Automatically provision access in your internal systems or send a welcome email.
* **Related Events**: [`auth.user.updated`](/graph-api-reference/webhooks/auth/user-updated)
## Trigger
* **Event Type:** `auth_user_created`
* **Source:** Insertion of a record into the `auth.user` table.
## Payload Example
```json theme={null}
{
"id": 123,
"external_id": "ext_u_123",
"identity_id": "auth0|abc",
"azure_object_id": "00000000-0000-0000-0000-000000000000",
"is_active": true,
"name": "John Doe",
"username": "johndoe",
"email": "john.doe@example.com",
"phone_number": "+1234567890",
"timezone": "UTC",
"profile_pic_file_id": 1001,
"old_id": 567,
"created_at": "2023-10-01T12:00:00Z",
"created_by": 1,
"updated_at": "2023-10-01T12:00:00Z",
"updated_by": 1,
"user_roles": [
{
"id": 1,
"role": "RECRUITER",
"created_at": "2023-10-01T12:00:00Z",
"created_by": 1,
"updated_at": "2023-10-01T12:00:00Z",
"updated_by": 1
}
],
"user_groups": [
{
"id": 1,
"group_id": 10,
"created_at": "2023-10-01T12:00:00Z",
"created_by": 1,
"updated_at": "2023-10-01T12:00:00Z",
"updated_by": 1,
"group": {
"id": 10,
"name": "Engineering",
"description": "Engineering department",
"external_id": "eng_dept",
"parent_group_id": null
}
}
]
}
```
## Payload Type Showcase
```typescript theme={null}
{
id: number;
external_id: string | null;
identity_id: string | null;
azure_object_id: string | null;
is_active: boolean;
name: string;
username: string;
email: string;
phone_number: string | null;
timezone: string | null;
profile_pic_file_id: number | null;
old_id: number | null;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number | null;
user_roles: {
id: number;
role: string;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
}[];
user_groups: {
id: number;
group_id: number;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
group: {
id: number;
name: string;
description: string | null;
external_id: string | null;
parent_group_id: number | null;
};
}[];
}
```
## Field Notes
* `role` on user\_roles references `auth.role` enum values (e.g., `RECRUITER`, `EVALUATOR`, `MASTER_RECRUITER`).
* `user_groups` nests the group summary so consumers can display membership without a separate fetch.
* `azure_object_id` and `identity_id` are included for SSO-integrated consumers.
* Role and group changes on a user trigger bubble-up — the user's `updated_at` is touched, firing an `auth.user.updated` event.
# User Updated
Source: https://docs.talview.com/graph-api-reference/webhooks/auth/user-updated
Triggered when an existing user's information or role assignments change.
For general webhook concepts like bubble-up behavior, payload visibility rules, and versioned snapshots, see [Webhook Concepts](/graph-api-reference/webhooks/concepts).
## Description
This event is triggered when an existing user's information is updated, or when their role or group assignments change (subordinate bubble-up).
## Integration Details
* **Subscription Key**: `auth.user.updated`
* **Use Case**: Sync profile changes (like email, name, or role assignments) to your external database.
* **Related Events**: [`auth.user.created`](/graph-api-reference/webhooks/auth/user-created)
## Trigger
* **Event Type:** `auth_user_updated`
* **Source:** Update of a record in the `auth.user` table, or bubble-up from subordinate changes to `auth.user_role` or `auth.user_group`.
## Payload Example
```json theme={null}
{
"id": 123,
"external_id": "ext_u_123",
"identity_id": "auth0|abc",
"azure_object_id": "00000000-0000-0000-0000-000000000000",
"is_active": true,
"name": "John Doe Updated",
"username": "johndoe",
"email": "john.doe@example.com",
"phone_number": "+1234567890",
"timezone": "UTC",
"profile_pic_file_id": 1001,
"old_id": 567,
"created_at": "2023-10-01T12:00:00Z",
"created_by": 1,
"updated_at": "2023-10-02T10:00:00Z",
"updated_by": 1,
"user_roles": [
{
"id": 1,
"role": "RECRUITER",
"created_at": "2023-10-01T12:00:00Z",
"created_by": 1,
"updated_at": "2023-10-01T12:00:00Z",
"updated_by": 1
}
],
"user_groups": [
{
"id": 1,
"group_id": 10,
"created_at": "2023-10-01T12:00:00Z",
"created_by": 1,
"updated_at": "2023-10-01T12:00:00Z",
"updated_by": 1,
"group": {
"id": 10,
"name": "Engineering",
"description": "Engineering department",
"external_id": "eng_dept",
"parent_group_id": null
}
}
]
}
```
## Payload Type Showcase
```typescript theme={null}
{
id: number;
external_id: string | null;
identity_id: string | null;
azure_object_id: string | null;
is_active: boolean;
name: string;
username: string;
email: string;
phone_number: string | null;
timezone: string | null;
profile_pic_file_id: number | null;
old_id: number | null;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number | null;
user_roles: {
id: number;
role: string;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
}[];
user_groups: {
id: number;
group_id: number;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
group: {
id: number;
name: string;
description: string | null;
external_id: string | null;
parent_group_id: number | null;
};
}[];
}
```
## Field Notes
* `role` on user\_roles references `auth.role` enum values (e.g., `RECRUITER`, `EVALUATOR`, `MASTER_RECRUITER`).
* `user_groups` nests the group summary so consumers can display membership without a separate fetch.
* `azure_object_id` and `identity_id` are included for SSO-integrated consumers.
* Role and group changes on a user trigger bubble-up — the user's `updated_at` is touched, firing an `auth.user.updated` event.
# Candidate Created
Source: https://docs.talview.com/graph-api-reference/webhooks/candidate/candidate-created
Triggered when a new candidate profile is created.
For general webhook concepts like bubble-up behavior, payload visibility rules, and versioned snapshots, see [Webhook Concepts](/graph-api-reference/webhooks/concepts).
## Description
This event is triggered when a new candidate profile is created in the system.
## Integration Details
* **Subscription Key**: `can.candidate.created`
* **Use Case**: Sync new candidate records to your ATS or trigger onboarding workflows.
* **Related Events**: [`can.candidate.updated`](/graph-api-reference/webhooks/candidate/candidate-updated)
## Trigger
* **Event Type:** `can_candidate_created`
* **Source:** Insertion of a record into the `can.candidate` table.
## Payload Example
```json theme={null}
{
"id": 101,
"first_name": "Jane",
"middle_name": "Marie",
"last_name": "Doe",
"email": "jane.doe@example.com",
"phone_number": "+19876543210",
"country": "USA",
"user_id": 123,
"external_id": "ext_can_101",
"old_id": null,
"resume_file_id": null,
"profile_pic_file_id": null,
"cf": {},
"meta": {},
"is_active": true,
"is_tnc_accepted": false,
"is_recording_consent_accepted": null,
"thread_id": null,
"notice_period": null,
"work_authorization": null,
"expected_salary": null,
"total_years_experience": null,
"avg_tenure_months": null,
"created_at": "2023-11-01T10:00:00Z",
"created_by": 1,
"updated_at": "2023-11-01T10:00:00Z",
"updated_by": 1,
"attachments": [],
"contacts": [],
"calendars": [],
"education": [],
"experiences": [],
"certifications": [],
"preferred_locations": [],
"projects": [],
"skill_proficiencies": [],
"social_media_links": []
}
```
## Payload Type Showcase
```typescript theme={null}
{
id: number;
first_name: string | null;
middle_name: string | null;
last_name: string | null;
email: string;
phone_number: string | null;
country: string | null;
user_id: number;
external_id: string | null;
old_id: number | null;
resume_file_id: number | null;
profile_pic_file_id: number | null;
cf: Record;
meta: Record;
is_active: boolean;
is_tnc_accepted: boolean;
is_recording_consent_accepted: boolean | null;
thread_id: number | null;
notice_period: string | null;
work_authorization: string | null;
expected_salary: string | null;
total_years_experience: number | null;
avg_tenure_months: number | null;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
attachments: {
id: number;
file_id: number;
file_type_id: number;
education_id: number | null;
experience_id: number | null;
external_id: string | null;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
}[];
contacts: {
id: number;
phone_number: string | null;
address: string | null;
city: string | null;
state: string | null;
country: string | null;
zipcode: string | null;
is_current: boolean;
external_id: string | null;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
}[];
calendars: {
id: number;
from: string;
to: string;
availability_status: string;
external_id: string | null;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
}[];
education: {
id: number;
title: string | null;
type: string | null;
field_of_study: string | null;
awarding_board: string | null;
institute: string | null;
grade: string | null;
gpa_value: number | null;
started_at: string | null;
completed_at: string | null;
is_current: boolean;
external_id: string | null;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
}[];
experiences: {
id: number;
type: string | null;
organization: string | null;
location: string | null;
designation: string | null;
description: string | null;
started_at: string | null;
completed_at: string | null;
is_current: boolean;
responsibilities: any[];
tools_used: any[];
external_id: string | null;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
}[];
certifications: {
id: number;
name: string;
issuer: string | null;
issue_date: string | null;
expiry_date: string | null;
external_id: string | null;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
}[];
preferred_locations: {
id: number;
location: Record;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
}[];
projects: {
id: number;
title: string;
description: string | null;
start_date: string | null;
end_date: string | null;
external_id: string | null;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
technologies: {
id: number;
technology: string;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
}[];
}[];
skill_proficiencies: {
id: number;
skill_id: number;
proficiency: string | null;
proficiency_label: string | null;
last_used: string | null;
evidence_snippet: Record | null;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
}[];
social_media_links: {
id: number;
social_media: string;
link: string;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
}[];
}
```
## Field Notes
* `cf` (custom fields) and `meta` are JSONB — shape varies per tenant configuration.
* `responsibilities` and `tools_used` on experiences are JSONB arrays.
* `evidence_snippet` on skill proficiencies is JSONB containing parsed resume excerpts.
* `location` on preferred\_locations is JSONB with structured geo data.
* `projects` nests `technologies` as a second-level subordinate.
* `file_type_id` on attachments references a lookup enum to distinguish resumes, certificates, etc.
* All subordinate arrays are pre-filtered to exclude soft-deleted records.
# Candidate Updated
Source: https://docs.talview.com/graph-api-reference/webhooks/candidate/candidate-updated
Triggered when a candidate's profile or subordinate records change.
For general webhook concepts like bubble-up behavior, payload visibility rules, and versioned snapshots, see [Webhook Concepts](/graph-api-reference/webhooks/concepts).
## Description
This event is triggered when a candidate's profile is updated, or when any subordinate record changes (education, experience, attachments, etc.) — all changes bubble up to the candidate root.
## Integration Details
* **Subscription Key**: `can.candidate.updated`
* **Use Case**: Keep candidate data in sync with your ATS or external systems.
* **Related Events**: [`can.candidate.created`](/graph-api-reference/webhooks/candidate/candidate-created)
## Trigger
* **Event Type:** `can_candidate_updated`
* **Source:** Update of a record in the `can.candidate` table, or bubble-up from subordinate changes to any of the candidate's nested records (attachments, contacts, education, experiences, certifications, projects, skill proficiencies, social media links, calendars, preferred locations).
## Payload Example
```json theme={null}
{
"id": 101,
"first_name": "Jane",
"middle_name": "Marie",
"last_name": "Doe",
"email": "jane.doe@example.com",
"phone_number": "+19876543210",
"country": "USA",
"user_id": 123,
"external_id": "ext_can_101",
"old_id": null,
"resume_file_id": 2001,
"profile_pic_file_id": null,
"cf": {},
"meta": {},
"is_active": true,
"is_tnc_accepted": true,
"is_recording_consent_accepted": null,
"thread_id": null,
"notice_period": null,
"work_authorization": null,
"expected_salary": null,
"total_years_experience": null,
"avg_tenure_months": null,
"created_at": "2023-11-01T10:00:00Z",
"created_by": 1,
"updated_at": "2023-11-02T14:00:00Z",
"updated_by": 1,
"attachments": [],
"contacts": [],
"calendars": [],
"education": [
{
"id": 1,
"title": "B.Sc. Computer Science",
"type": null,
"field_of_study": "Computer Science",
"awarding_board": null,
"institute": "MIT",
"grade": null,
"gpa_value": null,
"started_at": null,
"completed_at": "2020-05-15",
"is_current": false,
"external_id": null,
"created_at": "2023-11-01T10:00:00Z",
"created_by": 1,
"updated_at": "2023-11-02T14:00:00Z",
"updated_by": 1
}
],
"experiences": [
{
"id": 1,
"type": null,
"organization": "Acme Corp",
"location": null,
"designation": "Software Engineer",
"description": null,
"started_at": null,
"completed_at": null,
"is_current": true,
"responsibilities": [],
"tools_used": [],
"external_id": null,
"created_at": "2023-11-01T10:00:00Z",
"created_by": 1,
"updated_at": "2023-11-02T14:00:00Z",
"updated_by": 1
}
],
"certifications": [],
"preferred_locations": [],
"projects": [],
"skill_proficiencies": [],
"social_media_links": []
}
```
## Payload Type Showcase
```typescript theme={null}
{
id: number;
first_name: string | null;
middle_name: string | null;
last_name: string | null;
email: string;
phone_number: string | null;
country: string | null;
user_id: number;
external_id: string | null;
old_id: number | null;
resume_file_id: number | null;
profile_pic_file_id: number | null;
cf: Record;
meta: Record;
is_active: boolean;
is_tnc_accepted: boolean;
is_recording_consent_accepted: boolean | null;
thread_id: number | null;
notice_period: string | null;
work_authorization: string | null;
expected_salary: string | null;
total_years_experience: number | null;
avg_tenure_months: number | null;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
attachments: {
id: number;
file_id: number;
file_type_id: number;
education_id: number | null;
experience_id: number | null;
external_id: string | null;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
}[];
contacts: {
id: number;
phone_number: string | null;
address: string | null;
city: string | null;
state: string | null;
country: string | null;
zipcode: string | null;
is_current: boolean;
external_id: string | null;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
}[];
calendars: {
id: number;
from: string;
to: string;
availability_status: string;
external_id: string | null;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
}[];
education: {
id: number;
title: string | null;
type: string | null;
field_of_study: string | null;
awarding_board: string | null;
institute: string | null;
grade: string | null;
gpa_value: number | null;
started_at: string | null;
completed_at: string | null;
is_current: boolean;
external_id: string | null;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
}[];
experiences: {
id: number;
type: string | null;
organization: string | null;
location: string | null;
designation: string | null;
description: string | null;
started_at: string | null;
completed_at: string | null;
is_current: boolean;
responsibilities: any[];
tools_used: any[];
external_id: string | null;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
}[];
certifications: {
id: number;
name: string;
issuer: string | null;
issue_date: string | null;
expiry_date: string | null;
external_id: string | null;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
}[];
preferred_locations: {
id: number;
location: Record;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
}[];
projects: {
id: number;
title: string;
description: string | null;
start_date: string | null;
end_date: string | null;
external_id: string | null;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
technologies: {
id: number;
technology: string;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
}[];
}[];
skill_proficiencies: {
id: number;
skill_id: number;
proficiency: string | null;
proficiency_label: string | null;
last_used: string | null;
evidence_snippet: Record | null;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
}[];
social_media_links: {
id: number;
social_media: string;
link: string;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
}[];
}
```
## Field Notes
* `cf` (custom fields) and `meta` are JSONB — shape varies per tenant configuration.
* `responsibilities` and `tools_used` on experiences are JSONB arrays.
* `evidence_snippet` on skill proficiencies is JSONB containing parsed resume excerpts.
* `location` on preferred\_locations is JSONB with structured geo data.
* `projects` nests `technologies` as a second-level subordinate.
* `file_type_id` on attachments references a lookup enum to distinguish resumes, certificates, etc.
* All subordinate arrays are pre-filtered to exclude soft-deleted records.
# Webhook Concepts
Source: https://docs.talview.com/graph-api-reference/webhooks/concepts
Key behavioral rules that apply across all Talview webhook event types.
Understanding these concepts will help you correctly interpret webhook payloads and build reliable integrations.
***
## Event Naming Convention
Every webhook event follows a consistent naming pattern:
| Format | Example |
| :------------------------------------ | :---------------------- |
| **Subscription Key** (dot-separated) | `can.candidate.created` |
| **Event Type** (underscore-separated) | `can_candidate_created` |
Events are always one of three operations: `created`, `updated`, or `deleted`.
***
## Payload Visibility Rules
All webhook payloads follow two strict visibility rules:
| Excluded Field | Reason |
| :------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `tenant_id` | Implicit from your subscription context. Your webhook subscription is scoped to your tenant, so this field is redundant. |
| `is_deleted` | Internal soft-delete flag. Instead of seeing `is_deleted: true`, you will receive a `deleted` event. Subordinate arrays in payloads are pre-filtered to exclude soft-deleted records. |
If you previously relied on `tenant_id` in payloads, note that it is no longer included. Your subscription already scopes events to your tenant.
***
## Subordinate Bubble-Up
Talview webhooks operate on **root-level objects** only. When a nested (subordinate) record changes, the system does not fire a separate event for the subordinate. Instead, the parent root object's `updated_at` is touched in the same database transaction, which fires an `updated` event on the root with **the full current payload**.
### Example
Adding an education record to a candidate does **not** produce a `can.education.created` event. Instead, it triggers a `can.candidate.updated` event containing the candidate's complete profile, including the new education entry in the `education` array.
### Why this design?
* **Simplicity**: Consumers subscribe to a small set of root events instead of tracking dozens of subordinate tables.
* **Consistency**: Every `updated` payload is a complete snapshot of the root object — no need to merge partial updates.
* **Atomicity**: The subordinate change and the root's `updated_at` touch happen in the same transaction, preventing ordering issues.
***
## Versioned-Snapshot Objects
Most root objects have a dedicated history table (e.g., `sch.meeting_history`, `pay.transaction_status_history`) that records prior states. For these objects, `updated` event payloads contain only the **current** state.
However, some objects have no history table. These are called **versioned-snapshot** objects, and their `updated` payloads include both the previous and current state:
```json theme={null}
{
"old": { /* previous state */ },
"new": { /* current state */ }
}
```
### Objects with versioned-snapshot behavior
| Root Object | Reason |
| :------------------ | :------------------------------------------------------------------------------------------------------------------------ |
| `frm.form_instance` | No `form_instance_history` table exists. The `old` key provides the complete previous row so consumers can compute diffs. |
Check each event's documentation page to see whether `old` state is included in `updated` payloads.
***
## Cross-Service Payloads
Some root objects aggregate data from multiple services to provide full context in a single payload. This means the webhook delivers a rich, denormalized view — no additional API calls needed.
| Root Object | Services Joined | What's Included |
| :------------------ | :------------------------------------------ | :------------------------------------------------------------------------------------------------------------------------------- |
| `coordinator.exam` | coordinator, workflow-tools, scheduler, pm | Workflow steps, drive schedules, rooms, and proctoring center details. |
| `pm.center` | pm, workflow-tools, scheduler, geo-location | Workflow steps, drive schedules with rooms and seats, operating schedule with availabilities and overrides, geographic location. |
| `ae.test_instance` | assessment-engine, candidate, evaluation | Candidate snapshot, catalog/assessment metadata, measurement scores and attributes. |
| `pay.transaction` | payment, order | Full order chain including order items, SKUs, and applied coupons. |
| `sch.meeting` | scheduler, auth | Participant list with user identity snapshots from the auth service. |
| `incident.instance` | incident, session | Session snapshot with status and score from the session service. |
# Exam Created
Source: https://docs.talview.com/graph-api-reference/webhooks/coordinator/exam-created
Triggered when a new exam is created in the coordinator.
For general webhook concepts like bubble-up behavior, payload visibility rules, and versioned snapshots, see [Webhook Concepts](/graph-api-reference/webhooks/concepts).
## Description
This event is triggered when a new exam is created in the coordinator service.
## Integration Details
* **Subscription Key**: `coordinator.exam.created`
* **Use Case**: Set up corresponding records in an external proctoring or scheduling system.
* **Related Events**: [`coordinator.exam.updated`](/graph-api-reference/webhooks/coordinator/exam-updated)
## Trigger
* **Event Type:** `coordinator_exam_created`
* **Source:** Insertion of a record into the `coordinator.exam` table.
## Cross-Service References
This is one of the richest cross-service payloads:
* **Workflow Tools** (`wft.workflow`): Workflow definition with steps.
* **Scheduler** (`sch.drive_schedule`): Drive schedules filtered to `CENTER_PLAN` type, with rooms.
* **Proctoring Management** (`pm.center`): Physical proctoring center details.
## Payload Example
```json theme={null}
{
"id": 501,
"name": "Python Assessment - March 2024",
"workflow_id": 100,
"created_at": "2024-03-01T08:00:00Z",
"created_by": 1,
"updated_at": "2024-03-01T08:00:00Z",
"updated_by": 1,
"workflow": {
"id": 100,
"title": "Technical Hiring Pipeline",
"workflow_type": "hiring",
"status": "active",
"external_id": "ext_wf_100",
"steps": [
{
"id": 1,
"name": "Online Assessment",
"step_type": "assessment",
"sequence": 1,
"is_proctoring": true,
"external_id": null
},
{
"id": 2,
"name": "Technical Interview",
"step_type": "interview",
"sequence": 2,
"is_proctoring": false,
"external_id": null
}
],
"centers": [
{
"id": 201,
"name": "March 2024 - Bangalore Center",
"drive_type": "CENTER_PLAN",
"status": "active",
"start_date": "2024-03-15",
"end_date": "2024-03-15",
"booking_start_date": "2024-03-01",
"booking_end_date": "2024-03-14",
"location": {
"city": "Bangalore",
"country": "India"
},
"timezone": "Asia/Kolkata",
"cron_expression": null,
"external_id": null,
"rooms": [
{
"id": 301,
"external_id": null,
"guest_capacity": 30,
"status": "active",
"workflow_step_id": 1,
"center_id": 401
}
]
}
]
},
"center": {
"id": 401,
"name": "Bangalore Test Center",
"center_type": "physical",
"status": "active",
"external_id": "ext_center_401",
"timezone": "Asia/Kolkata",
"contact_name": "Priya Sharma",
"contact_email": "priya@testcenter.com",
"contact_phone": "+919876543210",
"exam_types": ["online", "offline"],
"geo_location_id": 50
}
}
```
## Payload Type Showcase
```typescript theme={null}
{
id: number;
name: string;
workflow_id: number;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
workflow: {
id: number;
title: string;
workflow_type: string;
status: string;
external_id: string | null;
steps: {
id: number;
name: string;
step_type: string;
sequence: number;
is_proctoring: boolean;
external_id: string | null;
}[];
centers: {
id: number;
name: string;
drive_type: string;
status: string;
start_date: string | null;
end_date: string | null;
booking_start_date: string | null;
booking_end_date: string | null;
location: Record | null;
timezone: string | null;
cron_expression: string | null;
external_id: string | null;
rooms: {
id: number;
external_id: string | null;
guest_capacity: number;
status: string;
workflow_step_id: number;
center_id: number;
}[];
}[];
};
center: {
id: number;
name: string;
center_type: string;
status: string;
external_id: string | null;
timezone: string;
contact_name: string | null;
contact_email: string | null;
contact_phone: string | null;
exam_types: string[];
geo_location_id: number | null;
};
}
```
## Field Notes
* `workflow` is a cross-service join to `wft.workflow` including nested steps and drive schedules.
* `centers` is an alias that filters `drive_schedules` to `CENTER_PLAN` type only.
* `center` is a cross-service join to `pm.center` for the physical proctoring center.
* `location` on drive schedules is JSONB.
* `exam_types` is a Postgres array of strings.
# Exam Updated
Source: https://docs.talview.com/graph-api-reference/webhooks/coordinator/exam-updated
Triggered when an exam's configuration, workflow, or center assignment changes.
For general webhook concepts like bubble-up behavior, payload visibility rules, and versioned snapshots, see [Webhook Concepts](/graph-api-reference/webhooks/concepts).
## Description
This event is triggered when an exam is updated — for example, when its workflow, center assignment, or scheduling changes.
## Integration Details
* **Subscription Key**: `coordinator.exam.updated`
* **Use Case**: Sync exam changes to external scheduling or proctoring systems.
* **Related Events**: [`coordinator.exam.created`](/graph-api-reference/webhooks/coordinator/exam-created)
## Trigger
* **Event Type:** `coordinator_exam_updated`
* **Source:** Update of a record in the `coordinator.exam` table.
## Cross-Service References
This is one of the richest cross-service payloads:
* **Workflow Tools** (`wft.workflow`): Workflow definition with steps.
* **Scheduler** (`sch.drive_schedule`): Drive schedules filtered to `CENTER_PLAN` type, with rooms.
* **Proctoring Management** (`pm.center`): Physical proctoring center details.
## Payload Example
```json theme={null}
{
"id": 501,
"name": "Python Assessment - March 2024 (Updated)",
"workflow_id": 100,
"created_at": "2024-03-01T08:00:00Z",
"created_by": 1,
"updated_at": "2024-03-05T10:00:00Z",
"updated_by": 1,
"workflow": {
"id": 100,
"title": "Technical Hiring Pipeline",
"workflow_type": "hiring",
"status": "active",
"external_id": "ext_wf_100",
"steps": [
{
"id": 1,
"name": "Online Assessment",
"step_type": "assessment",
"sequence": 1,
"is_proctoring": true,
"external_id": null
},
{
"id": 2,
"name": "Technical Interview",
"step_type": "interview",
"sequence": 2,
"is_proctoring": false,
"external_id": null
}
],
"centers": [
{
"id": 201,
"name": "March 2024 - Bangalore Center",
"drive_type": "CENTER_PLAN",
"status": "active",
"start_date": "2024-03-15",
"end_date": "2024-03-15",
"booking_start_date": "2024-03-01",
"booking_end_date": "2024-03-14",
"location": {
"city": "Bangalore",
"country": "India"
},
"timezone": "Asia/Kolkata",
"cron_expression": null,
"external_id": null,
"rooms": [
{
"id": 301,
"external_id": null,
"guest_capacity": 30,
"status": "active",
"workflow_step_id": 1,
"center_id": 401
},
{
"id": 302,
"external_id": null,
"guest_capacity": 20,
"status": "active",
"workflow_step_id": 1,
"center_id": 401
}
]
}
]
},
"center": {
"id": 401,
"name": "Bangalore Test Center",
"center_type": "physical",
"status": "active",
"external_id": "ext_center_401",
"timezone": "Asia/Kolkata",
"contact_name": "Priya Sharma",
"contact_email": "priya@testcenter.com",
"contact_phone": "+919876543210",
"exam_types": ["online", "offline"],
"geo_location_id": 50
}
}
```
## Payload Type Showcase
```typescript theme={null}
{
id: number;
name: string;
workflow_id: number;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
workflow: {
id: number;
title: string;
workflow_type: string;
status: string;
external_id: string | null;
steps: {
id: number;
name: string;
step_type: string;
sequence: number;
is_proctoring: boolean;
external_id: string | null;
}[];
centers: {
id: number;
name: string;
drive_type: string;
status: string;
start_date: string | null;
end_date: string | null;
booking_start_date: string | null;
booking_end_date: string | null;
location: Record | null;
timezone: string | null;
cron_expression: string | null;
external_id: string | null;
rooms: {
id: number;
external_id: string | null;
guest_capacity: number;
status: string;
workflow_step_id: number;
center_id: number;
}[];
}[];
};
center: {
id: number;
name: string;
center_type: string;
status: string;
external_id: string | null;
timezone: string;
contact_name: string | null;
contact_email: string | null;
contact_phone: string | null;
exam_types: string[];
geo_location_id: number | null;
};
}
```
## Field Notes
* `workflow` is a cross-service join to `wft.workflow` including nested steps and drive schedules.
* `centers` is an alias that filters `drive_schedules` to `CENTER_PLAN` type only.
* `center` is a cross-service join to `pm.center` for the physical proctoring center.
* `location` on drive schedules is JSONB.
* `exam_types` is a Postgres array of strings.
# Form Instance Created
Source: https://docs.talview.com/graph-api-reference/webhooks/form/form-instance-created
Triggered when a new form submission is received.
For general webhook concepts like bubble-up behavior, payload visibility rules, and versioned snapshots, see [Webhook Concepts](/graph-api-reference/webhooks/concepts).
## Description
This event is triggered when a new form instance is created — for example, when a candidate submits a survey or registration form.
## Integration Details
* **Subscription Key**: `form.form_instance.created`
* **Use Case**: Automatically process form data or sync survey responses to an external CRM.
* **Related Events**: [`form.form_instance.updated`](/graph-api-reference/webhooks/form/form-instance-updated)
## Trigger
* **Event Type:** `form_form_instance_created`
* **Source:** Insertion of a record into the `frm.form_instance` table.
## Payload Example
```json theme={null}
{
"id": 601,
"external_id": "ext_form_601",
"model_id": 1234,
"old_id": 5001,
"form_data": {
"uuid-1": "John",
"uuid-2": "Doe",
"uuid-3": "Great experience!"
},
"form_version_id": 701,
"submitted_by": 123,
"submitted_at": "2023-11-10T11:00:00Z",
"meta": {},
"created_at": "2023-11-10T11:00:00Z",
"created_by": 1,
"updated_at": "2023-11-10T11:00:00Z",
"updated_by": 1,
"form_version": {
"id": 701,
"version": 1,
"status": "published",
"structure": {},
"created_at": "2023-11-01T10:00:00Z",
"created_by": 1,
"updated_at": "2023-11-01T10:00:00Z",
"updated_by": 1,
"form_fields": [
{
"id": 901,
"uuid": "uuid-1",
"name": "First Name",
"type": "text",
"external_name": "first_name",
"created_at": "2023-11-01T10:00:00Z",
"created_by": 1,
"updated_at": "2023-11-01T10:00:00Z",
"updated_by": 1
}
],
"form": {
"id": 801,
"name": "Candidate Feedback Form",
"type": "feedback",
"url": "https://example.com/forms/feedback",
"is_active": true,
"external_id": "ext_frm_801",
"old_id": 4001,
"created_at": "2023-11-01T10:00:00Z",
"created_by": 1,
"updated_at": "2023-11-01T10:00:00Z",
"updated_by": 1
}
}
}
```
## Payload Type Showcase
```typescript theme={null}
{
id: number;
external_id: string | null;
model_id: number | null;
old_id: number | null;
form_data: Record;
form_version_id: number;
submitted_by: number | null;
submitted_at: string | null;
meta: Record | null;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
form_version: {
id: number;
version: number;
status: string;
structure: Record;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
form_fields: {
id: number;
uuid: string;
name: string;
type: string;
external_name: string | null;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
}[];
form: {
id: number;
name: string;
type: string;
url: string | null;
is_active: boolean;
external_id: string | null;
old_id: number | null;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
};
};
}
```
## Field Notes
* `form_data` is JSONB containing the actual submission values keyed by field UUID. Use `form_fields` to interpret the keys.
* `meta` is JSONB with submission context (source, device, etc.).
* `structure` on `form_version` is JSONB defining the form layout and field configuration.
* The `form_version → form` join provides the parent form metadata (name, type, active status).
# Form Instance Updated
Source: https://docs.talview.com/graph-api-reference/webhooks/form/form-instance-updated
Triggered when a form submission is updated.
For general webhook concepts like bubble-up behavior, payload visibility rules, and versioned snapshots, see [Webhook Concepts](/graph-api-reference/webhooks/concepts).
## Description
This event is triggered when a form instance is updated.
## Integration Details
* **Subscription Key**: `form.form_instance.updated`
* **Use Case**: Track form revision history or detect changes to submitted data.
* **Related Events**: [`form.form_instance.created`](/graph-api-reference/webhooks/form/form-instance-created)
## Trigger
* **Event Type:** `form_form_instance_updated`
* **Source:** Update of a record in the `frm.form_instance` table.
This is a **versioned-snapshot** event. The payload includes both `old` (previous state) and `new` (current state) at the root level because `frm.form_instance` has no history table. See [Versioned-Snapshot Objects](/graph-api-reference/webhooks/concepts#versioned-snapshot-objects).
## Payload Example
```json theme={null}
{
"old": {
"id": 601,
"form_data": {
"uuid-1": "Jon",
"uuid-2": "Doe",
"uuid-3": "Good experience"
},
"submitted_at": "2023-11-10T11:00:00Z",
"updated_at": "2023-11-10T11:00:00Z"
},
"new": {
"id": 601,
"external_id": "ext_form_601",
"model_id": 1234,
"old_id": 5001,
"form_data": {
"uuid-1": "John",
"uuid-2": "Doe",
"uuid-3": "Great experience!"
},
"form_version_id": 701,
"submitted_by": 123,
"submitted_at": "2023-11-10T11:00:00Z",
"meta": {},
"created_at": "2023-11-10T11:00:00Z",
"created_by": 1,
"updated_at": "2023-11-10T12:00:00Z",
"updated_by": 1,
"form_version": {
"id": 701,
"version": 1,
"status": "published",
"structure": {},
"created_at": "2023-11-01T10:00:00Z",
"created_by": 1,
"updated_at": "2023-11-01T10:00:00Z",
"updated_by": 1,
"form_fields": [
{
"id": 901,
"uuid": "uuid-1",
"name": "First Name",
"type": "text",
"external_name": "first_name",
"created_at": "2023-11-01T10:00:00Z",
"created_by": 1,
"updated_at": "2023-11-01T10:00:00Z",
"updated_by": 1
}
],
"form": {
"id": 801,
"name": "Candidate Feedback Form",
"type": "feedback",
"url": "https://example.com/forms/feedback",
"is_active": true,
"external_id": "ext_frm_801",
"old_id": 4001,
"created_at": "2023-11-01T10:00:00Z",
"created_by": 1,
"updated_at": "2023-11-01T10:00:00Z",
"updated_by": 1
}
}
}
}
```
## Payload Type Showcase
```typescript theme={null}
{
old: Partial;
new: FormInstance;
}
// where FormInstance is:
{
id: number;
external_id: string | null;
model_id: number | null;
old_id: number | null;
form_data: Record;
form_version_id: number;
submitted_by: number | null;
submitted_at: string | null;
meta: Record | null;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
form_version: {
id: number;
version: number;
status: string;
structure: Record;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
form_fields: {
id: number;
uuid: string;
name: string;
type: string;
external_name: string | null;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
}[];
form: {
id: number;
name: string;
type: string;
url: string | null;
is_active: boolean;
external_id: string | null;
old_id: number | null;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
};
};
}
```
## Field Notes
* `form_data` is JSONB containing the actual submission values keyed by field UUID. Use `form_fields` to interpret the keys.
* `meta` is JSONB with submission context (source, device, etc.).
* `structure` on `form_version` is JSONB defining the form layout and field configuration.
* The `form_version → form` join provides the parent form metadata (name, type, active status).
# Incident Instance Created
Source: https://docs.talview.com/graph-api-reference/webhooks/incident/instance-created
Triggered when a new proctoring incident is detected.
For general webhook concepts like bubble-up behavior, payload visibility rules, and versioned snapshots, see [Webhook Concepts](/graph-api-reference/webhooks/concepts).
## Description
This event is triggered when a new proctoring incident is detected — for example, via AI detection or a manual proctor flag.
## Integration Details
* **Subscription Key**: `incident.instance.created`
* **Use Case**: Trigger immediate intervention alerts or compliance logging.
* **Related Events**: [`incident.instance.updated`](/graph-api-reference/webhooks/incident/instance-updated)
## Trigger
* **Event Type:** `incident_instance_created`
* **Source:** Insertion of a record into the `incident.instance` table.
## Cross-Service References
* **Session** (`session.instance`): Lightweight snapshot of the associated proctoring session.
## Payload Example
```json theme={null}
{
"id": 134,
"name": "Face not detected",
"description": null,
"status": "TRIGGERED",
"severity": "LOW",
"start_time": "2026-02-03T10:46:23.260Z",
"end_time": null,
"resolution_notes": null,
"session_instance_id": 2523,
"external_id": null,
"created_at": "2026-02-03T09:57:55.341Z",
"created_by": 1,
"updated_at": "2026-02-03T09:57:55.341Z",
"updated_by": 1,
"session": {
"id": 2523,
"uuid": "019c22ef-edc6-765d-9ab3-c2acf41b5253",
"score": null,
"status": "IN_PROGRESS",
"created_at": "2026-02-03T09:57:55.341Z",
"updated_at": "2026-02-03T09:57:55.341Z"
},
"timeline": []
}
```
## Payload Type Showcase
```typescript theme={null}
{
id: number;
name: string | null;
description: string | null;
status: string;
severity: string;
start_time: string;
end_time: string | null;
resolution_notes: string | null;
session_instance_id: number;
external_id: string | null;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
session: {
id: number;
uuid: string;
score: number | null;
status: string;
created_at: string;
updated_at: string;
};
timeline: {
id: number;
action: string;
description: string | null;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
}[];
}
```
## Field Notes
* `status` references a Hasura enum: `TRIGGERED`, `RESOLVED`, `DISMISSED`, `REOPENED`.
* `severity` references a Hasura enum: `LOW`, `MEDIUM`, `HIGH`.
* `session` is a cross-service reference to `session.instance` — included as a lightweight snapshot.
* `timeline` captures the incident lifecycle (detection, escalation, resolution). Empty on creation.
* `action` on timeline entries references the `incident.timeline_action` enum.
* Timeline changes trigger bubble-up to the incident root.
# Incident Instance Updated
Source: https://docs.talview.com/graph-api-reference/webhooks/incident/instance-updated
Triggered when a proctoring incident is updated or resolved.
For general webhook concepts like bubble-up behavior, payload visibility rules, and versioned snapshots, see [Webhook Concepts](/graph-api-reference/webhooks/concepts).
## Description
This event is triggered when a proctoring incident is updated — for example, when its status changes, severity is adjusted, or timeline entries are added (subordinate bubble-up).
## Integration Details
* **Subscription Key**: `incident.instance.updated`
* **Use Case**: Track incident resolution progress or sync status changes to compliance systems.
* **Related Events**: [`incident.instance.created`](/graph-api-reference/webhooks/incident/instance-created)
## Trigger
* **Event Type:** `incident_instance_updated`
* **Source:** Update of a record in the `incident.instance` table, or bubble-up from subordinate changes to `incident.timeline`.
## Cross-Service References
* **Session** (`session.instance`): Lightweight snapshot of the associated proctoring session.
## Payload Example
```json theme={null}
{
"id": 134,
"name": "Face not detected",
"description": null,
"status": "RESOLVED",
"severity": "LOW",
"start_time": "2026-02-03T10:46:23.260Z",
"end_time": "2026-02-03T11:15:00.000Z",
"resolution_notes": "Confirmed candidate was adjusting camera. No violation.",
"session_instance_id": 2523,
"external_id": null,
"created_at": "2026-02-03T09:57:55.341Z",
"created_by": 1,
"updated_at": "2026-02-03T11:15:00.000Z",
"updated_by": 1,
"session": {
"id": 2523,
"uuid": "019c22ef-edc6-765d-9ab3-c2acf41b5253",
"score": 85,
"status": "COMPLETED",
"created_at": "2026-02-03T09:57:55.341Z",
"updated_at": "2026-02-03T11:15:00.000Z"
},
"timeline": [
{
"id": 1,
"action": "ESCALATED",
"description": "Auto-escalated after 5 minutes without face detection.",
"created_at": "2026-02-03T10:51:23.260Z",
"created_by": 0,
"updated_at": "2026-02-03T10:51:23.260Z",
"updated_by": 0
}
]
}
```
## Payload Type Showcase
```typescript theme={null}
{
id: number;
name: string | null;
description: string | null;
status: string;
severity: string;
start_time: string;
end_time: string | null;
resolution_notes: string | null;
session_instance_id: number;
external_id: string | null;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
session: {
id: number;
uuid: string;
score: number | null;
status: string;
created_at: string;
updated_at: string;
};
timeline: {
id: number;
action: string;
description: string | null;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
}[];
}
```
## Field Notes
* `status` references a Hasura enum: `TRIGGERED`, `RESOLVED`, `DISMISSED`, `REOPENED`.
* `severity` references a Hasura enum: `LOW`, `MEDIUM`, `HIGH`.
* `session` is a cross-service reference to `session.instance` — included as a lightweight snapshot.
* `timeline` captures the incident lifecycle (detection, escalation, resolution). Empty on creation.
* `action` on timeline entries references the `incident.timeline_action` enum.
* Timeline changes trigger bubble-up to the incident root.
# Overview
Source: https://docs.talview.com/graph-api-reference/webhooks/overview
General behavior, reliability, and transport mechanics of the Webhook system.
## What are Webhooks?
Webhooks are automated messages sent from one system to another when a specific event occurs. Think of them as "push notifications" for your servers. Instead of your system constantly asking (polling) the Talview API if there are new updates, Talview pushes that data to your system the moment it happens.
This approach is significantly more efficient, reduces API load, and ensures your integration reacts to platform events — like a candidate finishing an exam — in real-time.
***
## Talview Webhooks
Talview uses webhooks to notify your system about critical lifecycle events across assessments, interviews, forms, payments, and more.
Before diving into individual events, review the [Webhook Concepts](/graph-api-reference/webhooks/concepts) page for important behavioral rules such as payload visibility, subordinate bubble-up, and versioned snapshots.
### Available Webhook Events
The following table lists all events that are currently available for subscription, grouped by service:
| Service | Event ID | Trigger Description | Common Use Case |
| :------------------------ | :--------------------------- | :------------------------------------------------------------------ | :----------------------------------------------------------------- |
| **Assessment Engine** | `ae_test_instance_created` | A candidate starts a new assessment attempt. | Logging the start time in an external LMS. |
| | `ae_test_instance_updated` | A test attempt is updated (e.g., score calculated, status changes). | Automatically retrieving results once a test is completed. |
| **Auth** | `auth_user_created` | A new user is created in the Talview system. | Syncing user accounts with your internal HRIS. |
| | `auth_user_updated` | An existing user's profile or role assignments change. | Keeping user details consistent across systems. |
| **Candidate** | `can_candidate_created` | A new candidate profile is created. | Syncing candidate records to your ATS. |
| | `can_candidate_updated` | A candidate's profile or subordinate records change. | Keeping candidate data in sync with external systems. |
| **Coordinator** | `coordinator_exam_created` | A new exam is created in the coordinator. | Setting up corresponding records in an external proctoring system. |
| | `coordinator_exam_updated` | An exam's configuration, workflow, or center assignment changes. | Syncing exam changes to external scheduling systems. |
| **Form** | `form_form_instance_created` | A new form submission is received. | Capturing feedback or registration data. |
| | `form_form_instance_updated` | A form submission is updated. | Tracking form revision history. |
| **Incident** | `incident_instance_created` | A new proctoring incident is detected. | Triggering immediate intervention alerts. |
| | `incident_instance_updated` | A proctoring incident is updated or resolved. | Compliance logging and incident tracking. |
| **Payment** | `pay_transaction_created` | A new payment transaction is initiated. | Tracking pending revenue or booking attempts. |
| | `pay_transaction_updated` | A payment status changes (e.g., Success, Failed, Refunded). | Confirming a candidate's slot after successful payment. |
| **Proctoring Management** | `pm_center_created` | A new proctoring center is created. | Provisioning center resources in an external system. |
| | `pm_center_updated` | A proctoring center's configuration or schedule changes. | Syncing center availability with external calendars. |
| **Scheduler** | `sch_meeting_created` | A new interview or meeting is scheduled. | Adding the event to an external calendar or ATS. |
| | `sch_meeting_updated` | A meeting is rescheduled, cancelled, or its status changes. | Sending updated meeting links to participants. |
### Planned Events
The following root objects have been identified for future webhook support but are **not yet available** for subscription:
| Service | Root Object | Description |
| :------------------ | :----------------------- | :--------------------------------------- |
| Auth | `auth.tenant` | Tenant configuration changes. |
| Auth | `app.instance` | App installation and permission changes. |
| Candidate Auth | `ca.profile` | Candidate authentication profile. |
| Evaluation | `tcf.measurement` | Evaluation measurements. |
| Event | `event.event` | Platform events. |
| Form | `frm.form` | Form definition changes. |
| Help Center | `hc.page` | Help center page updates. |
| Message | `message.channel` | Chat channel changes. |
| Notify | `notify.message` | Notification messages. |
| Payment | `pay.sku` | SKU (product) definition changes. |
| Project | `pc.project` | Project management updates. |
| Scheduler | `sch.drive_schedule` | Drive schedule management. |
| Session | `session.instance` | Session lifecycle events. |
| Sync | `sync.config` | Sync configuration changes. |
| Taxonomy | `tax.skill` | Skill taxonomy updates. |
| VoIP | `voip.call_history` | Call history records. |
| VR | `vr.room` | Virtual room changes. |
| Workflow Tools | `wft.workflow` | Workflow definition changes. |
| Workflow Tools | `wft.job` | Job requisition changes. |
| Workflow Tools | `wft.workflow_candidate` | Candidate pipeline progression. |
| Endpoint Protection | `ep.policy` | Security policy changes. |
These events are under development. Contact your Talview representative for timeline information.
***
## Technical Implementation
### HTTP Request Pattern
All webhooks are delivered using a standard HTTP request pattern:
```http theme={null}
POST HTTP/1.1
Host:
Content-Type: application/json
{
...payload
}
```
* **Method**: Defaults to `POST` (configurable to `PUT` or `PATCH` during registration).
* **Body**: The raw JSON payload of the event. There is no outer "envelope" or wrapper.
# Transaction Created
Source: https://docs.talview.com/graph-api-reference/webhooks/payment/transaction-created
Triggered when a new payment transaction is initiated.
For general webhook concepts like bubble-up behavior, payload visibility rules, and versioned snapshots, see [Webhook Concepts](/graph-api-reference/webhooks/concepts).
## Description
This event is triggered when a new payment transaction is initiated.
## Integration Details
* **Subscription Key**: `pay.transaction.created`
* **Use Case**: Track revenue in real-time or update an external financial ledger.
* **Related Events**: [`pay.transaction.updated`](/graph-api-reference/webhooks/payment/transaction-updated)
## Trigger
* **Event Type:** `pay_transaction_created`
* **Source:** Insertion of a record into the `pay.transaction` table.
## Cross-Service References
The payment payload traverses the order chain to provide full purchase context:
* **Order** (`pay.order`): Order metadata and status.
* **Order Items** → **Item** → **SKU** (`pay.sku`): Product details including pricing and currency.
* **Coupon** (`pay.coupon`): Discount information if applied.
## Payload Example
```json theme={null}
{
"id": 901,
"external_id": "ext_tx_901",
"payment_id": "pay_abc123",
"status": "pending",
"total_amount": 50.00,
"currency_code": "USD",
"narration": "Assessment credit purchase",
"purchased_by": 123,
"order_id": 1001,
"payment_gateway_id": 1,
"rule_id": null,
"receipt_file_id": null,
"created_at": "2023-11-15T09:00:00Z",
"created_by": 1,
"updated_at": "2023-11-15T09:00:00Z",
"updated_by": 1,
"order": {
"id": 1001,
"external_id": "ext_ord_1001",
"status": "open",
"ordered_by": 123,
"entity_name": "candidate",
"created_at": "2023-11-15T08:55:00Z",
"created_by": 1,
"updated_at": "2023-11-15T08:55:00Z",
"updated_by": 1,
"order_items": [
{
"id": 1101,
"unit_price": 50.00,
"total_price": 50.00,
"quantity": 1,
"is_reschedule": false,
"external_id": null,
"created_at": "2023-11-15T08:55:00Z",
"created_by": 1,
"updated_at": "2023-11-15T08:55:00Z",
"updated_by": 1,
"coupon": null,
"item": {
"id": 1201,
"status": "active",
"description": "Python Proficiency Test slot",
"external_id": null,
"drive_occurrence_guest_id": 777,
"meeting_participant_id": null,
"valid_till": "2023-12-31T23:59:59Z",
"sku": {
"id": 1301,
"name": "Assessment Credit",
"type": "credit",
"plan_type": "one_time",
"price": 50.00,
"external_id": "sku_abc",
"currency_code": "USD"
}
}
}
]
},
"transaction_status_history": []
}
```
## Payload Type Showcase
```typescript theme={null}
{
id: number;
external_id: string | null;
payment_id: string | null;
status: string;
total_amount: number;
currency_code: string | null;
narration: string | null;
purchased_by: number | null;
order_id: number;
payment_gateway_id: number | null;
rule_id: number | null;
receipt_file_id: number | null;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
order: {
id: number;
external_id: string | null;
status: string;
ordered_by: number | null;
entity_name: string | null;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
order_items: {
id: number;
unit_price: number;
total_price: number;
quantity: number;
is_reschedule: boolean;
external_id: string | null;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
coupon: {
id: number;
code: string;
external_id: string | null;
discount_percentage: number;
} | null;
item: {
id: number;
status: string;
description: string | null;
external_id: string | null;
drive_occurrence_guest_id: number | null;
meeting_participant_id: number | null;
valid_till: string | null;
sku: {
id: number;
name: string;
type: string | null;
plan_type: string | null;
price: number;
external_id: string | null;
currency_code: string;
};
};
}[];
};
transaction_status_history: {
id: number;
status_from: string;
status_to: string;
error_message: string | null;
created_at: string;
created_by: number;
}[];
}
```
## Field Notes
* `payment_id` is a UUID from the payment gateway (e.g., Stripe, Razorpay).
* `narration` is a human-readable payment description.
* `transaction_status_history` provides the status audit trail. Empty on creation, populated on subsequent status transitions.
* `coupon` on order items is nullable — only present if a discount was applied.
* The `order → order_items → item → sku` chain provides the full purchase context.
# Transaction Updated
Source: https://docs.talview.com/graph-api-reference/webhooks/payment/transaction-updated
Triggered when a payment transaction status changes (e.g., to success or failed).
For general webhook concepts like bubble-up behavior, payload visibility rules, and versioned snapshots, see [Webhook Concepts](/graph-api-reference/webhooks/concepts).
## Description
This event is triggered when a payment transaction status changes — for example, to `success` or `failed`.
## Integration Details
* **Subscription Key**: `pay.transaction.updated`
* **Use Case**: Automatically fulfill orders or unlock features in your app once a transaction becomes `success`.
* **Related Events**: [`pay.transaction.created`](/graph-api-reference/webhooks/payment/transaction-created)
## Trigger
* **Event Type:** `pay_transaction_updated`
* **Source:** Update of a record in the `pay.transaction` table.
This event does **not** include an `old` field. Transaction status changes are tracked in `transaction_status_history` within the payload. See [Versioned-Snapshot Objects](/graph-api-reference/webhooks/concepts#versioned-snapshot-objects).
## Cross-Service References
The payment payload traverses the order chain to provide full purchase context:
* **Order** (`pay.order`): Order metadata and status.
* **Order Items** → **Item** → **SKU** (`pay.sku`): Product details including pricing and currency.
* **Coupon** (`pay.coupon`): Discount information if applied.
## Payload Example
```json theme={null}
{
"id": 901,
"external_id": "ext_tx_901",
"payment_id": "pay_abc123",
"status": "success",
"total_amount": 50.00,
"currency_code": "USD",
"narration": "Assessment credit purchase",
"purchased_by": 123,
"order_id": 1001,
"payment_gateway_id": 1,
"rule_id": null,
"receipt_file_id": 5001,
"created_at": "2023-11-15T09:00:00Z",
"created_by": 1,
"updated_at": "2023-11-15T09:30:00Z",
"updated_by": 1,
"order": {
"id": 1001,
"external_id": "ext_ord_1001",
"status": "completed",
"ordered_by": 123,
"entity_name": "candidate",
"created_at": "2023-11-15T08:55:00Z",
"created_by": 1,
"updated_at": "2023-11-15T08:55:00Z",
"updated_by": 1,
"order_items": [
{
"id": 1101,
"unit_price": 50.00,
"total_price": 50.00,
"quantity": 1,
"is_reschedule": false,
"external_id": null,
"created_at": "2023-11-15T08:55:00Z",
"created_by": 1,
"updated_at": "2023-11-15T08:55:00Z",
"updated_by": 1,
"coupon": null,
"item": {
"id": 1201,
"status": "active",
"description": "Python Proficiency Test slot",
"external_id": null,
"drive_occurrence_guest_id": 777,
"meeting_participant_id": null,
"valid_till": "2023-12-31T23:59:59Z",
"sku": {
"id": 1301,
"name": "Assessment Credit",
"type": "credit",
"plan_type": "one_time",
"price": 50.00,
"external_id": "sku_abc",
"currency_code": "USD"
}
}
}
]
},
"transaction_status_history": [
{
"id": 1,
"status_from": "pending",
"status_to": "success",
"error_message": null,
"created_at": "2023-11-15T09:30:00Z",
"created_by": 0
}
]
}
```
## Payload Type Showcase
```typescript theme={null}
{
id: number;
external_id: string | null;
payment_id: string | null;
status: string;
total_amount: number;
currency_code: string | null;
narration: string | null;
purchased_by: number | null;
order_id: number;
payment_gateway_id: number | null;
rule_id: number | null;
receipt_file_id: number | null;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
order: {
id: number;
external_id: string | null;
status: string;
ordered_by: number | null;
entity_name: string | null;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
order_items: {
id: number;
unit_price: number;
total_price: number;
quantity: number;
is_reschedule: boolean;
external_id: string | null;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
coupon: {
id: number;
code: string;
external_id: string | null;
discount_percentage: number;
} | null;
item: {
id: number;
status: string;
description: string | null;
external_id: string | null;
drive_occurrence_guest_id: number | null;
meeting_participant_id: number | null;
valid_till: string | null;
sku: {
id: number;
name: string;
type: string | null;
plan_type: string | null;
price: number;
external_id: string | null;
currency_code: string;
};
};
}[];
};
transaction_status_history: {
id: number;
status_from: string;
status_to: string;
error_message: string | null;
created_at: string;
created_by: number;
}[];
}
```
## Field Notes
* `payment_id` is a UUID from the payment gateway (e.g., Stripe, Razorpay).
* `narration` is a human-readable payment description.
* `transaction_status_history` provides the status audit trail. Empty on creation, populated on subsequent status transitions.
* `coupon` on order items is nullable — only present if a discount was applied.
* The `order → order_items → item → sku` chain provides the full purchase context.
# Center Created
Source: https://docs.talview.com/graph-api-reference/webhooks/pm/center-created
Triggered when a new proctoring center is created.
For general webhook concepts like bubble-up behavior, payload visibility rules, and versioned snapshots, see [Webhook Concepts](/graph-api-reference/webhooks/concepts).
## Description
This event is triggered when a new proctoring center is created.
## Integration Details
* **Subscription Key**: `pm.center.created`
* **Use Case**: Provision center resources in an external system or sync availability.
* **Related Events**: [`pm.center.updated`](/graph-api-reference/webhooks/pm/center-updated)
## Trigger
* **Event Type:** `pm_center_created`
* **Source:** Insertion of a record into the `pm.center` table.
## Cross-Service References
This is one of the richest cross-service payloads in the system:
* **Workflow Tools** (`wft.workflow`): Workflow definition with steps.
* **Scheduler** (`sch.drive_schedule`): Drive schedules with rooms and room seats, filtered to `CENTER_PLAN` type and this center.
* **Geo-location**: Physical address and coordinates.
* **Schedule**: Operating hours (weekly availabilities) and holiday overrides.
## Payload Example
```json theme={null}
{
"id": 401,
"name": "Bangalore Test Center",
"center_type": "physical",
"status": "active",
"external_id": "ext_center_401",
"timezone": "Asia/Kolkata",
"contact_name": "Priya Sharma",
"contact_email": "priya@testcenter.com",
"contact_phone": "+919876543210",
"exam_types": ["online", "offline"],
"schedule_id": 60,
"workflow_id": 100,
"geo_location_id": 50,
"created_at": "2024-03-01T08:00:00Z",
"created_by": 1,
"updated_at": "2024-03-01T08:00:00Z",
"updated_by": 1,
"geo_location": {
"id": 50,
"address": "100 MG Road, Indiranagar",
"city_name": "Bangalore",
"country_code": "IN",
"postal_code": "560038",
"latitude": 12.9716,
"longitude": 77.5946,
"google_map_link": "https://maps.google.com/?q=12.9716,77.5946"
},
"schedule": {
"id": 60,
"name": "Standard Business Hours",
"schedule_type": "weekly",
"timezone": "Asia/Kolkata",
"external_id": null,
"schedule_availabilities": [
{
"id": 1,
"week_day": "monday",
"from": "09:00:00",
"to": "17:00:00",
"sort_key": 1,
"external_id": null
},
{
"id": 2,
"week_day": "tuesday",
"from": "09:00:00",
"to": "17:00:00",
"sort_key": 2,
"external_id": null
}
],
"schedule_overrides": [
{
"id": 1,
"from_date": "2024-03-25",
"to_date": "2024-03-25",
"is_holiday": true,
"reason": "Holi",
"external_id": null
}
]
},
"workflow": {
"id": 100,
"title": "Technical Hiring Pipeline",
"workflow_type": "hiring",
"status": "active",
"external_id": "ext_wf_100",
"steps": [
{
"id": 1,
"name": "Online Assessment",
"step_type": "assessment",
"sequence": 1,
"is_proctoring": true,
"external_id": null,
"drive_schedules": [
{
"id": 201,
"name": "March 2024 - Bangalore",
"drive_type": "CENTER_PLAN",
"status": "active",
"start_date": "2024-03-15",
"end_date": "2024-03-15",
"booking_start_date": "2024-03-01",
"booking_end_date": "2024-03-14",
"location": {
"city": "Bangalore",
"country": "India"
},
"timezone": "Asia/Kolkata",
"cron_expression": null,
"external_id": null,
"rooms": [
{
"id": 301,
"external_id": null,
"guest_capacity": 30,
"status": "active",
"workflow_step_id": 1,
"room_seats": [
{
"id": 1,
"external_id": "seat-01",
"status": "available"
}
]
}
]
}
]
}
]
}
}
```
## Payload Type Showcase
```typescript theme={null}
{
id: number;
name: string;
center_type: string;
status: string;
external_id: string | null;
timezone: string;
contact_name: string | null;
contact_email: string | null;
contact_phone: string | null;
exam_types: string[];
schedule_id: number | null;
workflow_id: number | null;
geo_location_id: number | null;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
geo_location: {
id: number;
address: string | null;
city_name: string | null;
country_code: string | null;
postal_code: string | null;
latitude: number | null;
longitude: number | null;
google_map_link: string | null;
} | null;
schedule: {
id: number;
name: string;
schedule_type: string;
timezone: string;
external_id: string | null;
schedule_availabilities: {
id: number;
week_day: string;
from: string;
to: string;
sort_key: number;
external_id: string | null;
}[];
schedule_overrides: {
id: number;
from_date: string;
to_date: string;
is_holiday: boolean;
reason: string | null;
external_id: string | null;
}[];
} | null;
workflow: {
id: number;
title: string;
workflow_type: string;
status: string;
external_id: string | null;
steps: {
id: number;
name: string;
step_type: string;
sequence: number;
is_proctoring: boolean;
external_id: string | null;
drive_schedules: {
id: number;
name: string;
drive_type: string;
status: string;
start_date: string | null;
end_date: string | null;
booking_start_date: string | null;
booking_end_date: string | null;
location: Record | null;
timezone: string | null;
cron_expression: string | null;
external_id: string | null;
rooms: {
id: number;
external_id: string | null;
guest_capacity: number;
status: string;
workflow_step_id: number;
room_seats: {
id: number;
external_id: string | null;
status: string;
}[];
}[];
}[];
}[];
} | null;
}
```
## Field Notes
* `center_type`, `status`, and `timezone` are raw enum values — no joined descriptions.
* `geo_location` provides the physical address and coordinates.
* `schedule → schedule_availabilities` defines the weekly operating hours.
* `schedule → schedule_overrides` defines holidays and exceptional closures.
* `workflow → steps → drive_schedules → rooms → room_seats` is a deep cross-service chain filtered to this center via `center_id`.
* `location` on drive schedules is JSONB.
* `exam_types` is a Postgres array of strings.
# Center Updated
Source: https://docs.talview.com/graph-api-reference/webhooks/pm/center-updated
Triggered when a proctoring center's configuration or schedule changes.
For general webhook concepts like bubble-up behavior, payload visibility rules, and versioned snapshots, see [Webhook Concepts](/graph-api-reference/webhooks/concepts).
## Description
This event is triggered when a proctoring center is updated — for example, when its schedule, contact information, or associated rooms change.
## Integration Details
* **Subscription Key**: `pm.center.updated`
* **Use Case**: Sync center availability with external calendars or update proctoring resource allocations.
* **Related Events**: [`pm.center.created`](/graph-api-reference/webhooks/pm/center-created)
## Trigger
* **Event Type:** `pm_center_updated`
* **Source:** Update of a record in the `pm.center` table.
## Cross-Service References
This is one of the richest cross-service payloads in the system:
* **Workflow Tools** (`wft.workflow`): Workflow definition with steps.
* **Scheduler** (`sch.drive_schedule`): Drive schedules with rooms and room seats, filtered to `CENTER_PLAN` type and this center.
* **Geo-location**: Physical address and coordinates.
* **Schedule**: Operating hours (weekly availabilities) and holiday overrides.
## Payload Example
```json theme={null}
{
"id": 401,
"name": "Bangalore Test Center",
"center_type": "physical",
"status": "active",
"external_id": "ext_center_401",
"timezone": "Asia/Kolkata",
"contact_name": "Priya Sharma",
"contact_email": "admin@testcenter.com",
"contact_phone": "+919876543210",
"exam_types": ["online", "offline"],
"schedule_id": 60,
"workflow_id": 100,
"geo_location_id": 50,
"created_at": "2024-03-01T08:00:00Z",
"created_by": 1,
"updated_at": "2024-03-05T10:00:00Z",
"updated_by": 1,
"geo_location": {
"id": 50,
"address": "100 MG Road, Indiranagar",
"city_name": "Bangalore",
"country_code": "IN",
"postal_code": "560038",
"latitude": 12.9716,
"longitude": 77.5946,
"google_map_link": "https://maps.google.com/?q=12.9716,77.5946"
},
"schedule": {
"id": 60,
"name": "Standard Business Hours",
"schedule_type": "weekly",
"timezone": "Asia/Kolkata",
"external_id": null,
"schedule_availabilities": [
{
"id": 1,
"week_day": "monday",
"from": "09:00:00",
"to": "17:00:00",
"sort_key": 1,
"external_id": null
},
{
"id": 2,
"week_day": "tuesday",
"from": "09:00:00",
"to": "17:00:00",
"sort_key": 2,
"external_id": null
},
{
"id": 3,
"week_day": "wednesday",
"from": "09:00:00",
"to": "17:00:00",
"sort_key": 3,
"external_id": null
}
],
"schedule_overrides": [
{
"id": 1,
"from_date": "2024-03-25",
"to_date": "2024-03-25",
"is_holiday": true,
"reason": "Holi",
"external_id": null
}
]
},
"workflow": {
"id": 100,
"title": "Technical Hiring Pipeline",
"workflow_type": "hiring",
"status": "active",
"external_id": "ext_wf_100",
"steps": [
{
"id": 1,
"name": "Online Assessment",
"step_type": "assessment",
"sequence": 1,
"is_proctoring": true,
"external_id": null,
"drive_schedules": [
{
"id": 201,
"name": "March 2024 - Bangalore",
"drive_type": "CENTER_PLAN",
"status": "active",
"start_date": "2024-03-15",
"end_date": "2024-03-15",
"booking_start_date": "2024-03-01",
"booking_end_date": "2024-03-14",
"location": {
"city": "Bangalore",
"country": "India"
},
"timezone": "Asia/Kolkata",
"cron_expression": null,
"external_id": null,
"rooms": [
{
"id": 301,
"external_id": null,
"guest_capacity": 40,
"status": "active",
"workflow_step_id": 1,
"room_seats": [
{
"id": 1,
"external_id": "seat-01",
"status": "available"
}
]
}
]
}
]
}
]
}
}
```
## Payload Type Showcase
```typescript theme={null}
{
id: number;
name: string;
center_type: string;
status: string;
external_id: string | null;
timezone: string;
contact_name: string | null;
contact_email: string | null;
contact_phone: string | null;
exam_types: string[];
schedule_id: number | null;
workflow_id: number | null;
geo_location_id: number | null;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
geo_location: {
id: number;
address: string | null;
city_name: string | null;
country_code: string | null;
postal_code: string | null;
latitude: number | null;
longitude: number | null;
google_map_link: string | null;
} | null;
schedule: {
id: number;
name: string;
schedule_type: string;
timezone: string;
external_id: string | null;
schedule_availabilities: {
id: number;
week_day: string;
from: string;
to: string;
sort_key: number;
external_id: string | null;
}[];
schedule_overrides: {
id: number;
from_date: string;
to_date: string;
is_holiday: boolean;
reason: string | null;
external_id: string | null;
}[];
} | null;
workflow: {
id: number;
title: string;
workflow_type: string;
status: string;
external_id: string | null;
steps: {
id: number;
name: string;
step_type: string;
sequence: number;
is_proctoring: boolean;
external_id: string | null;
drive_schedules: {
id: number;
name: string;
drive_type: string;
status: string;
start_date: string | null;
end_date: string | null;
booking_start_date: string | null;
booking_end_date: string | null;
location: Record | null;
timezone: string | null;
cron_expression: string | null;
external_id: string | null;
rooms: {
id: number;
external_id: string | null;
guest_capacity: number;
status: string;
workflow_step_id: number;
room_seats: {
id: number;
external_id: string | null;
status: string;
}[];
}[];
}[];
}[];
} | null;
}
```
## Field Notes
* `center_type`, `status`, and `timezone` are raw enum values — no joined descriptions.
* `geo_location` provides the physical address and coordinates.
* `schedule → schedule_availabilities` defines the weekly operating hours.
* `schedule → schedule_overrides` defines holidays and exceptional closures.
* `workflow → steps → drive_schedules → rooms → room_seats` is a deep cross-service chain filtered to this center via `center_id`.
* `location` on drive schedules is JSONB.
* `exam_types` is a Postgres array of strings.
# Meeting Created
Source: https://docs.talview.com/graph-api-reference/webhooks/scheduler/meeting-created
Triggered when a new meeting is successfully scheduled.
For general webhook concepts like bubble-up behavior, payload visibility rules, and versioned snapshots, see [Webhook Concepts](/graph-api-reference/webhooks/concepts).
## Description
This event is triggered when a new meeting is successfully scheduled.
## Integration Details
* **Subscription Key**: `sch.meeting.created`
* **Use Case**: Sync interviews or meetings with an external CRM or shared team calendar.
* **Related Events**: [`sch.meeting.updated`](/graph-api-reference/webhooks/scheduler/meeting-updated)
## Trigger
* **Event Type:** `sch_meeting_created`
* **Source:** Insertion of a record into the `sch.meeting` table.
## Cross-Service References
* **Auth** (`auth.user`): `user_details` on each participant provides an identity snapshot from the auth service.
## Payload Example
```json theme={null}
{
"id": 456,
"external_id": "ext_meet_456",
"old_id": null,
"name": "Technical Interview - Jane Doe",
"meeting_type": "interview",
"meeting_status": "scheduled",
"from": "2023-11-01T14:00:00Z",
"to": "2023-11-01T15:00:00Z",
"duration": "01:00:00",
"timezone": "UTC",
"location": {
"type": "virtual",
"url": "https://meet.talview.com/abc-123"
},
"additional_params": {},
"drive_occurrence_id": 101,
"room_id": null,
"provider_service_id": null,
"workflow_candidate_step_id": 4001,
"cancelled_at": null,
"cancelled_by": null,
"created_at": "2023-10-25T09:00:00Z",
"created_by": 1,
"updated_at": "2023-10-25T09:00:00Z",
"updated_by": 1,
"meeting_participants": [
{
"id": 1,
"participant_role": "interviewer",
"participation_status": "active",
"rsvp_status": "accepted",
"guest_id": null,
"user_id": 123,
"online_meeting_link": "https://meet.talview.com/abc-123",
"meta": {},
"external_id": null,
"old_id": null,
"created_at": "2023-10-25T09:00:00Z",
"created_by": 1,
"updated_at": "2023-10-25T09:00:00Z",
"updated_by": 1,
"user_details": {
"id": 123,
"identity_id": "auth0|abc",
"azure_object_id": "00000000-0000-0000-0000-000000000000",
"external_id": "ext_u_123",
"username": "johndoe",
"email": "john.doe@example.com",
"name": "John Doe"
}
}
],
"meeting_files": []
}
```
## Payload Type Showcase
```typescript theme={null}
{
id: number;
external_id: string | null;
old_id: number | null;
name: string | null;
meeting_type: string;
meeting_status: string;
from: string | null;
to: string | null;
duration: string | null;
timezone: string;
location: Record | null;
additional_params: Record | null;
drive_occurrence_id: number | null;
room_id: number | null;
provider_service_id: number | null;
workflow_candidate_step_id: number | null;
cancelled_at: string | null;
cancelled_by: number | null;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
meeting_participants: {
id: number;
participant_role: string;
participation_status: string;
rsvp_status: string | null;
guest_id: number | null;
user_id: number | null;
online_meeting_link: string | null;
meta: Record | null;
external_id: string | null;
old_id: number | null;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
user_details: {
id: number;
identity_id: string | null;
azure_object_id: string | null;
external_id: string | null;
username: string;
email: string;
name: string;
} | null;
}[];
meeting_files: {
id: number;
file_id: number;
created_at: string;
created_by: number;
}[];
}
```
## Field Notes
* `location` and `additional_params` are JSONB — shape varies by meeting configuration.
* `meta` on participants is JSONB with provider-specific metadata.
* `user_details` is a cross-service join to `auth.user` — provides the participant's identity snapshot.
* `meeting_files` are recordings or attachments linked to the meeting.
* `duration` is a Postgres INTERVAL rendered as a string (e.g., `"01:00:00"`).
* Participant and file changes trigger bubble-up to the meeting root.
# Meeting Updated
Source: https://docs.talview.com/graph-api-reference/webhooks/scheduler/meeting-updated
Triggered when a scheduled meeting is updated (e.g., rescheduled, status change).
For general webhook concepts like bubble-up behavior, payload visibility rules, and versioned snapshots, see [Webhook Concepts](/graph-api-reference/webhooks/concepts).
## Description
This event is triggered when a scheduled meeting is updated — for example, when it is rescheduled, cancelled, or a participant's RSVP status changes (subordinate bubble-up).
## Integration Details
* **Subscription Key**: `sch.meeting.updated`
* **Use Case**: Update local calendar entries or trigger follow-up tasks when a meeting status changes.
* **Related Events**: [`sch.meeting.created`](/graph-api-reference/webhooks/scheduler/meeting-created)
## Trigger
* **Event Type:** `sch_meeting_updated`
* **Source:** Update of a record in the `sch.meeting` table, or bubble-up from subordinate changes to `sch.meeting_participant` or `sch.meeting_file`.
This event does **not** include an `old` field. Meeting history is tracked in the `sch.meeting_history` table. Use the [Webhook Concepts](/graph-api-reference/webhooks/concepts#versioned-snapshot-objects) page for more context.
## Cross-Service References
* **Auth** (`auth.user`): `user_details` on each participant provides an identity snapshot from the auth service.
## Payload Example
```json theme={null}
{
"id": 456,
"external_id": "ext_meet_456",
"old_id": null,
"name": "Technical Interview - Jane Doe",
"meeting_type": "interview",
"meeting_status": "rescheduled",
"from": "2023-11-01T15:00:00Z",
"to": "2023-11-01T16:00:00Z",
"duration": "01:00:00",
"timezone": "UTC",
"location": {
"type": "virtual",
"url": "https://meet.talview.com/abc-123"
},
"additional_params": {},
"drive_occurrence_id": 101,
"room_id": null,
"provider_service_id": null,
"workflow_candidate_step_id": 4001,
"cancelled_at": null,
"cancelled_by": null,
"created_at": "2023-10-25T09:00:00Z",
"created_by": 1,
"updated_at": "2023-10-26T08:00:00Z",
"updated_by": 1,
"meeting_participants": [
{
"id": 1,
"participant_role": "interviewer",
"participation_status": "active",
"rsvp_status": "accepted",
"guest_id": null,
"user_id": 123,
"online_meeting_link": "https://meet.talview.com/abc-123",
"meta": {},
"external_id": null,
"old_id": null,
"created_at": "2023-10-25T09:00:00Z",
"created_by": 1,
"updated_at": "2023-10-25T09:00:00Z",
"updated_by": 1,
"user_details": {
"id": 123,
"identity_id": "auth0|abc",
"azure_object_id": "00000000-0000-0000-0000-000000000000",
"external_id": "ext_u_123",
"username": "johndoe",
"email": "john.doe@example.com",
"name": "John Doe"
}
}
],
"meeting_files": []
}
```
## Payload Type Showcase
```typescript theme={null}
{
id: number;
external_id: string | null;
old_id: number | null;
name: string | null;
meeting_type: string;
meeting_status: string;
from: string | null;
to: string | null;
duration: string | null;
timezone: string;
location: Record | null;
additional_params: Record | null;
drive_occurrence_id: number | null;
room_id: number | null;
provider_service_id: number | null;
workflow_candidate_step_id: number | null;
cancelled_at: string | null;
cancelled_by: number | null;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
meeting_participants: {
id: number;
participant_role: string;
participation_status: string;
rsvp_status: string | null;
guest_id: number | null;
user_id: number | null;
online_meeting_link: string | null;
meta: Record | null;
external_id: string | null;
old_id: number | null;
created_at: string;
created_by: number;
updated_at: string;
updated_by: number;
user_details: {
id: number;
identity_id: string | null;
azure_object_id: string | null;
external_id: string | null;
username: string;
email: string;
name: string;
} | null;
}[];
meeting_files: {
id: number;
file_id: number;
created_at: string;
created_by: number;
}[];
}
```
## Field Notes
* `location` and `additional_params` are JSONB — shape varies by meeting configuration.
* `meta` on participants is JSONB with provider-specific metadata.
* `user_details` is a cross-service join to `auth.user` — provides the participant's identity snapshot.
* `meeting_files` are recordings or attachments linked to the meeting.
* `duration` is a Postgres INTERVAL rendered as a string (e.g., `"01:00:00"`).
* Participant and file changes trigger bubble-up to the meeting root.
# Subscribing to Webhooks
Source: https://docs.talview.com/graph-api-reference/webhooks/subscribing
How to register endpoints and manage webhook subscriptions across the platform.
## Overview
Talview webhooks deliver event payloads to your infrastructure when candidate, assessment, scheduling, or payment changes happen. Before you can receive any hook, you must register an application, expose an HTTPS endpoint, and subscribe that application to one or more event types via the Graph API actions (`hook_register_app`, `hook_subscribe`). Tenant or platform administrator privileges are required.
## Registration Workflow
1. **Create a hook application** – call `hook_register_app` with a human-readable name (for example, the system that will consume events).
2. **Provision your endpoint** – host a publicly reachable HTTPS URL, decide which HTTP method (`POST`, `PUT`, or `PATCH`) and headers you support, and plan for retries/signature validation.
3. **Subscribe to event types** – invoke `hook_subscribe` per `event_type_name`, passing the application ID, endpoint URL, and optional overrides for method or transport.
4. **Validate delivery** – trigger a lower-risk event (for example, create a test record) or use the re-trigger action to confirm you log responses correctly.
5. **Operate the lifecycle** – disable, re-trigger, or unsubscribe via the companion actions as needed when rotating endpoints.
### Registration API Inputs
Provide a single field when registering:
* **name**: String. Display name for the consuming system; appears in admin consoles and audit logs.
```typescript theme={null}
type RegisterAppInput = {
name: string;
};
```
### Registration Payload Response Shape
Successful registration returns identifiers and audit metadata. Use the numeric `id` when subscribing.
```typescript theme={null}
type RegisterAppResult = {
id: number;
uuid: string;
name: string;
created_at: string; // ISO timestamp
created_by: number;
updated_at?: string | null;
updated_by?: number | null;
};
```
### Registration Response Example
Successful registration returns identifiers and audit metadata.
```JSON theme={null}
{
"data": {
"hook_register_app": {
"id": 1,
"uuid": "df4e18e2-4a36-403c-9081-5c7cb415fc16",
"name": "Webhook QA Harness",
"created_at": "2026-04-06T06:44:15.375006+00:00",
"created_by": 1,
"updated_at": null,
"updated_by": null
}
}
}
```
### Subscription Options
* **Graph API action (`hook_subscribe`)**: Preferred programmatic path; send a GraphQL mutation to the Hasura endpoint with authenticated admin credentials.
### Subscription API Inputs
Each subscription binds one event type to one endpoint target. Required and optional fields mirror the Joi schema used by the Lambda handler.
* **event\_type\_name**: String identifier (e.g., `ae_test_instance_created`) from the approved enum list.
* **url**: HTTPS endpoint the platform will call.
* **application\_id**: Integer referencing the registered app.
* **method** *(optional)*: One of `POST`, `PUT`, `PATCH`; defaults to `POST`.
* **transport** *(optional)*: Transport enum; currently only `HTTP` is supported and used by default.
```typescript theme={null}
type SubscribeInput = {
event_type_name: string;
url: string;
application_id: number;
method?: 'POST' | 'PUT' | 'PATCH';
transport?: 'HTTP';
};
```
### Subscription Payload Response Shape
The action returns the saved subscription, including its unique identifiers and the event metadata snapshot.
```typescript theme={null}
type SubscribeResult = {
id: number;
uuid: string;
is_enabled: boolean;
event_type: {
id: number;
name: string;
verb: string;
resource_type: string;
service: string;
schema: Record | null;
};
};
```
### Subscription Response Example
The response to the graphql query will be of the following shape
```JSON theme={null}
{
"data": {
"hook_subscribe": {
"id": 3,
"uuid": "03778579-a4c9-460d-b340-8759adb5beaf",
"is_enabled": true,
"event_type": {
"id": 10,
"name": "session.instance.created",
"service": "session",
"resource_type": "instance",
"verb": "created",
"schema": {}
}
}
}
}
```
## Creating a Subscription
Use the Graph API mutation below after registering your app. Replace the variables with your application ID, endpoint URL, and event type. When omitted, `method` becomes `POST` and `transport` becomes `HTTP`.
```graphql theme={null}
mutation HookSubscribe(
$event_type_name: String!
$url: String!
$application_id: Int!
$method: String!
$transport: String!
) {
hook_subscribe(
event_type_name: $event_type_name
url: $url
application_id: $application_id
method: $method
transport: $transport
) {
id
uuid
is_enabled
event_type {
id
name
service
resource_type
verb
schema
}
}
}
```
Example variables:
```json theme={null}
{
"event_type_name": "ae_test_instance_created",
"url": "https://hooks.example.com/talview",
"application_id": 42,
"method": "POST"
}
```
## Managing Existing Subscriptions
* **Disable or delete**: Use the `hook_unsubscribe` action with the subscription `uuid` when retiring an endpoint.
* **Re-trigger deliveries**: `hook_re_trigger` lets platform admins replay events (`event_type_name` + record `id`) to facilitate recovery or testing.
## Testing & Verification
* Trigger a known event in a staging tenant to observe the payload structure before enabling production subscriptions.
* Confirm your endpoint returns a `2xx` status within Talview’s timeout to prevent retries.
* Store the `uuid` so you can map incoming deliveries back to the subscription configuration for troubleshooting.
## Troubleshooting
* **Invalid input**: The actions return `422 Unprocessable Entity` when a required field is missing or `event_type_name` is outside the allow list.
* **Permission denied**: Ensure the auth token carries `TENANT_ADMIN` or `PLATFORM_ADMIN`; other roles cannot call these actions.
* **Duplicate endpoint logic**: The platform allows multiple subscriptions to the same URL; use your own idempotency logic to suppress duplicate downstream processing if needed.
* **Endpoint unreachable**: Retries continue until the service marks the target as failed—monitor your logs and update the subscription with a working URL before re-triggering events.
## Related Resources
* `docs/graph-api-reference/webhooks/overview.mdx` – transport behavior, retry schedule, and event catalog.
* Individual hook docs (for example, `ae_test_instance_created.mdx`) – payload contracts and sample data.
# Unsubscribing from Webhooks
Source: https://docs.talview.com/graph-api-reference/webhooks/unsubscribing
How to disable existing webhook subscriptions safely via the Graph API.
## Overview
When an endpoint is deprecated, compromised, or temporarily offline, you can disable its deliveries by calling the `hook_unsubscribe` Graph action. The action requires the subscription's UUID, which is returned whenever you create or list subscriptions. Tenant and platform administrators can perform this operation; other roles are denied.
## Unsubscription Workflow
1. **Identify the subscription** – retrieve the `uuid` from your records.
2. **Call `hook_unsubscribe`** – send the Graph mutation with the `uuid` payload.
3. **Confirm the response** – inspect the returned `Hook_Subscribe_Output` to verify the intended subscription was disabled.
### Unsubsribing API Inputs
`hook_unsubscribe` expects a single field:
* **uuid**: String
```typescript theme={null}
type UnsubscribeInput = {
uuid: string; // must be a valid UUIDv4
};
```
### Unsubscibing Payload Response Shape
The action mirrors the subscribe response so you can confirm which event and endpoint were affected.
```typescript theme={null}
type UnsubscribeResult = {
id: number;
uuid: string;
is_enabled: boolean;
event_type: {
id: number;
name: string;
verb: string;
resource_type: string;
service: string;
schema: Record | null;
};
};
```
### Unsubscribing Response Example
The action returns the now-unsubcribed subscription, including its unique identifiers and the event metadata snapshot
```JSON theme={null}
{
"data": {
"hook_unsubscribe": {
"id": 4,
"uuid": "848ef0a7-af58-49de-bfea-7830fac8b0e0",
"is_enabled": false,
"event_type": {
"id": 10,
"name": "session.instance.created",
"verb": null,
"resource_type": null,
"service": null,
"schema": null
}
}
}
}
```
## Mutation Example
Use the mutation below with admin credentials. The mutation simply forwards the `uuid` variable to the action.
```graphql theme={null}
mutation HookUnsubscribe($uuid: uuid!) {
hook_unsubscribe(uuid: $uuid) {
id
uuid
is_enabled
event_type {
name
service
resource_type
verb
}
}
}
```
Example variables:
```json theme={null}
{
"uuid": "a97e2443-cffb-4eb3-bcb4-0f1210865d45"
}
```
## Managing the Lifecycle
* **Bulk clean-up**: Iterate through stored UUIDs in automation to remove multiple endpoints; rate limits apply per Graph API policy.
* **Rollback/Resubscribe**: If you unsubscribed by mistake, call `hook_subscribe` again with the same event type and endpoint—new IDs will be issued.
* **Auditing**: Keep the unsubscribe response and mutation request ID for compliance logs; the `created_at`/`updated_at` values remain available via the subscription tables even after disabling.
## Testing & Verification
* After unsubscribing, trigger the original event to confirm your endpoint no longer receives calls.
* Monitor delivery logs; you should see a “disabled target” status associated with the `uuid`.
* In staging, create a fresh subscription, unsubscribe it, and ensure automation handles both states before promoting to production.
## Troubleshooting
* **Unknown UUID**: `422 Unprocessable Entity` indicates the UUID is missing or malformed; validate the identifier format and ensure it exists.
* **Permission denied**: use a token scoped to `TENANT_ADMIN` or `PLATFORM_ADMIN`.
* **Race conditions**: if events arrive between creating a new subscription and unsubscribing the old one, design idempotent consumers to handle duplicate deliveries.
* **Record not found**: the backend returns a not-found error if the subscription was already removed—safe to ignore if you intended a no-op.
## Related Resources
* `docs/graph-api-reference/webhooks/subscribing.mdx` – how to onboard endpoints and capture subscription UUIDs.
* `docs/graph-api-reference/webhooks/overview.mdx` – retry semantics and event catalog.
# What Happens if a Candidate or an Interviewer is a No Show in a Drive?
Source: https://docs.talview.com/hiring-teams/evaluator/drives/diagnostics/what-happens-if-a-candidate-or-an-interviewer-is-a-no-show-in-a-drive
When an interviewer doesn't join their scheduled interview in a drive, it can disrupt the recruitment process and impact the candidate experience. This article explains what happens when an interviewer is a no show and how to prevent or address this situation.
## 🔎 Troubleshooting Common Issues
| **What Might Be Wrong** | **How to Fix It** |
| :--------------------------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Interviewer forgot about the scheduled interview | Check your email for interview invitations and calendar reminders. Enable calendar sync to automatically add interviews to your calendar. |
| Interviewer didn't receive the interview invitation email | Check your spam or junk folder for emails from Talview. |
| You had a scheduling conflict | Contact your hiring coordinator or recruitment team immediately to reschedule. Provide as much advance notice as possible. |
| Technical issues prevented Interviewer from joining | Test your system before the interview time. If issues occur, contact support immediately and inform the recruiter so they can reschedule the candidate. |
| Interviewer is unsure how to access the interview | Review the email invitation for the join link or log in to your Talview interview dashboard. Refer to the **"Joining an Interview from the Drive"** guide for detailed steps. |
| The interview time zone displayed was confusing | Verify your time zone settings in your Talview profile. Contact your recruiter if you need clarification on the correct interview time. |
| Interviewer didn't confirm your availability when assigned | Update your availability to facilitate easy scheduling of future interviews. |
### **Additional Tips**
* Log in to your interview dashboard daily to review upcoming sessions
* Communicate scheduling conflicts as early as possible to the recruiter
* Test your camera, microphone, and internet connection before interview time
* Join interviews 5-10 minutes early to avoid technical delays
* If you cannot attend a scheduled interview, inform your recruiter immediately so they can reassign another interviewer or reschedule the candidate. Also, update your availability to facilitate easy scheduling of future interviews.
# Why didn’t I receive a notification when I was added to a drive?
Source: https://docs.talview.com/hiring-teams/evaluator/drives/diagnostics/why-didnt-i-receive-a-notification-when-i-was-added-to-a-drive
Interviewers play a critical role in recruitment drives, and timely notifications ensure they're prepared and informed when added to a drive. When an interviewer doesn't receive the expected notification email after being added to a drive in Talview's Workflow Tools, it can lead to confusion, missed interviews, and coordination challenges.
This article helps interviewers troubleshoot notification delivery issues and ensure seamless communication during drive management.
## 🔎Troubleshooting Common Issues
| **What might be wrong** | **How to fix it** |
| :----------------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Email address is incorrect or outdated** | Verify the interviewer's email address in their profile settings. Ask the recruiter to confirm the correct email was used when adding the interviewer to the drive. |
| **Notification went to spam or junk folder** | Check the spam, junk, or promotions folder in the email inbox. |
| **Email server issues or firewall restrictions** | Contact the IT department to ensure Talview's email notifications aren't being blocked by corporate firewalls or email security settings. Request whitelisting of Talview notification emails. |
| **System delay or processing issue** | Wait 15-30 minutes for the notification to arrive, as there may be a processing delay. If the notification still doesn't arrive, contact the recruiter to resend the drive invitation. |
### **Additional Tips**
* Confirm with the recruiter that the interviewer was successfully added to the drive by checking the drive dashboard and interviewer list.
* Contact Talview support if notification issues persist across multiple drives or interviewers, as this may indicate a platform-level configuration issue.
# Why do I still see interviews in my list after being removed from a drive?
Source: https://docs.talview.com/hiring-teams/evaluator/drives/diagnostics/why-do-i-still-see-interviews-in-my-list-after-being-removed-from-a-drive
Interviewers may occasionally notice scheduled interviews appearing in their dashboard or email notifications even after a recruiter has removed them from a specific drive.
This article helps interviewers understand why interviews might still be visible after removal and provides troubleshooting steps to resolve access and notification issues
## 🔎Troubleshooting Common Issues
| **What might be wrong** | **How to fix it** |
| :------------------------------------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Cache or browser data displaying outdated information** | Clear your browser cache and cookies, then log out completely from Talview. Close all browser tabs and windows, restart your browser, and log back in to refresh your interviewer dashboard with the most current drive assignments. |
| **Removal applied to one drive day but not the entire drive series** | If the drive was created as a recurring series across multiple days, the recruiter may have removed you from only one specific drive day rather than the entire series. Reach out to the recruiter or master recruiter to verify whether your removal should apply to all drive or just specific drive day. |
| **Platform synchronization delay** | Talview's system may require a few minutes to propagate removal changes across all modules. Wait 10-15 minutes after your removal notification, then refresh your dashboard. If interviews still appear after this time, contact the recruiter to verify the removal was completed on their end. |
### **Additional Tips**
* Double-check the interview date and time in your list to ensure it corresponds to the drive you were removed from, as you may be assigned to multiple drives with similar names or timeframes.
* Keep in mind that completed interviews will remain visible in your history for record-keeping and evaluation purposes, even after drive removal, only upcoming interviews should be removed from active lists.
# Why is No-show status incorrectly marked against candidate or interviewer?
Source: https://docs.talview.com/hiring-teams/evaluator/drives/diagnostics/why-is-no-show-status-incorrectly-marked-against-candidate-or-interviewer
During virtual hiring events and career fairs, accurate attendance tracking is essential for maintaining reliable candidate records and interviewer performance metrics. Sometimes, the system may incorrectly flag a candidate or interviewer as a no-show even when they attended the scheduled session.
This article helps interviewers identify why no-show statuses are incorrectly assigned and provides solutions to correct these markings.
## 🔎Troubleshooting Common Issues
| **What might be wrong** | **How to fix it** |
| :------------------------------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| The participant joined late and missed the automatic attendance window | Manually update the attendance status in the Drive dashboard under the specific session details. |
| Browser or network issues prevented the system from registering attendance | Check the session logs for connection attempts. If logs show connection activity, manually mark the participant as attended and document the technical issue for future reference. |
| The participant joined from a different device or account than registered | Verify alternative login records in the system. Cross-reference participant details and update the attendance status if you can confirm their presence through session recordings or chat logs. |
| Time zone mismatches caused confusion about the actual session timing | Review the scheduled time zone settings for the drive. If the participant joined at the correct local time but wrong system time, adjust the attendance record and send clarification about time zones for future sessions. |
### **Additional Tips**
* Enable session recordings to maintain proof of attendance for dispute resolution.
* Verify participant presence at the start and document any technical difficulties.
# Why is the Drive not updating real-time Interview Status?
Source: https://docs.talview.com/hiring-teams/evaluator/drives/diagnostics/why-is-the-drive-not-updating-real-time-interview-status
When the Drive dashboard fails to reflect real-time interview statuses, interviewers and recruiters lose critical oversight, leading to confusion about candidate progress, scheduling conflicts, and delayed hiring outcomes.
This article helps interviewers troubleshoot and resolve issues when the Drive is not updating interview statuses in real-time within Talview's Workflow Toos.
## 🔎Troubleshooting Common Issues
| **What Might Be Wrong** | **How to Fix It** |
| :---------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Browser cache or cookies are outdated** | Clear the browser cache and cookies, then refresh the Drive dashboard. Use` Ctrl+F5 (Windows)` or `Cmd+Shift+R (Mac)` for a hard refresh to reload the latest data. |
| **Network connectivity issues** | Check the internet connection and ensure stable bandwidth. Switch to a wired connection if using Wi-Fi or restart the router to improve connection stability. |
| **Dashboard auto-refresh is disabled** | Enable auto-refresh settings in the Drive dashboard. Manually refresh the page periodically to ensure the latest interview statuses are displayed. |
| **System sync delays** | Wait 30-60 seconds and refresh the dashboard, as minor sync delays can occur during high-volume drives. |
| **Calendar integration conflicts** | Verify that calendar integrations (Google Calendar, Outlook) are properly synced and permissions are granted for real-time data sharing. |
| **Session timeout or logged-out state** | Log out completely and log back in to refresh the session. Ensure the session has not timed out due to inactivity. |
### **Additional Tip**
Contact Talview support if the problem persists after trying all troubleshooting steps, and provide specific details about the Drive, number of candidates, and when the issue began.
# Why is the Interview link missing or not working from the drive?
Source: https://docs.talview.com/hiring-teams/evaluator/drives/diagnostics/why-is-the-interview-link-missing-or-not-working-from-the-drive
When interviewers access a virtual hiring drive, they may encounter situations where the interview link is either missing from the drive interface or fails to work when clicked. This prevents them from joining scheduled interviews and can disrupt the recruitment process.
**This article helps** interviewers troubleshoot and resolve issues when interview links are missing or not functioning properly within Talview's Workflow Tools.
## 🔎 Troubleshooting Common Issues
| **What might be wrong** | **How to fix it** |
| :----------------------------------------------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Browser cache or cookies are preventing the link from displaying correctly | Clear your browser cache and cookies, then refresh the drive page. |
| The interview link has expired, or the interview time has passed | Check if the interview is still within the valid time window. Request the recruiter to reschedule if needed |
| Network connectivity issues are blocking the link from loading | Check your internet connection stability. Try switching networks or disabling VPN if you're using one |
| The interview was rescheduled or cancelled but you weren't notified | Confirm the interview status with the recruiter. Check your email for any rescheduling notifications |
| The drive is configured for in-person interviews instead of virtual interviews | Contact the recruiter, to confirm whether the drive is set up for in-person or virtual mode. If it should be virtual, request them to update the drive settings and if it’s in-person, you do not require the interview link. |
### **Additional Tips**
* If using multiple tabs, ensure you're viewing the most recent version of the drive by refreshing the page.
* Double-check that you're logged in with the correct interviewer account, as using the wrong credentials can prevent access to assigned interviews.
# Interviewer FAQs - Drive management
Source: https://docs.talview.com/hiring-teams/evaluator/drives/faqs/interviewer-faqs-drive-management
## Introduction
The **Drive Management module** in **Talview Workflow Tools** helps interviewers efficiently participate in large-scale or on-site hiring events, known as **Drives**.
As an interviewer, you can view your schedule, join interviews, mark attendance, and complete evaluations - all from one interface.
This FAQ covers everything you need to know about managing your activities within a drive, including how to view your interviews, handle no-shows, update availability, and complete post-interview actions.
***
## 1. Drive Assignments & Scheduling
**Q1. How will I know if I’m added or removed from a drive?**
When you’re added to a drive, you’ll receive an **email notification** containing the drive name, date, and your assigned slots.
If you’re removed, you’ll receive a **removal confirmation**.
Once removed, you’ll stop receiving all future updates and notifications related to that drive.
**Q2. How do I update my availability if I can’t attend a scheduled drive?**
If you’re unable to attend the drive or specific time slots:
* Inform your **Recruiter** or **Drive Coordinator** as soon as possible.
* They can reassign your slots to another interviewer.
If you have partial availability, communicate your preferred time window so the schedule can be adjusted accordingly.
**Q3. Where can I see all my scheduled interviews in a drive?**
You can view your assigned interviews under the **Interviews** or **My Schedule** tab within the drive.
Each entry displays:
* Candidate name
* Interview time and mode (in-person or virtual)
* Assigned room or link
* Status (Scheduled, Completed, No-Show)
Use filters to sort by **status**, **candidate**, or **time** for easier navigation.
**Q4. Can I see candidate profiles before the interview starts?**
Candidates are assigned dynamically based on their wait times. Hence, showing the profiles beforehand is not possible.
**Q5. Can I join an interview directly from the drive?**
Yes. Once the drive starts, the **Join** button becomes active next to each assigned interview slot.
Click **Join** to start the session from within the Drive Dashboard.
Ensure your **camera, microphone, and browser permissions** are enabled before joining.
**Q6. What should I do if I need a short break during back-to-back drive interviews?**
If you need a short break:
* Inform the **Drive Coordinator** or **Recruiter** so they can pause or adjust the candidate flow.
* Simply click **Join** again when you’re ready for the next interview.
Avoid leaving sessions unattended, as it may delay subsequent interviews.
**Q7. What happens if I accidentally miss joining a drive interview?**
If you miss an interview slot:
* Notify your **Recruiter** immediately so they can reassign the candidate or reschedule the session.
Repeated missed joins may impact scheduling in future drives.
**Q8. What should I do if a candidate doesn’t join on time?**
If a candidate hasn’t joined within **5 minutes** of the scheduled start time:
* You can **end the session** and return to your drive dashboard.
* The system will automatically mark the candidate as a **No-Show** and notify the recruiter.
You can then proceed to your next assigned slot.
**Q9. Who gets notified if a candidate or interviewer is a no-show?**
If a **candidate** is marked as a no-show, the recruiter receives an automated notification.
If an **interviewer** doesn’t join, the recruiter is alerted, and a **backup interviewer** may be assigned.
Both scenarios are tracked in the **Drive Insights Dashboard** for visibility.
***
## 2. Evaluation & Feedback
**Q10. Will I automatically be added as an evaluator for candidates I interview?**
Yes. Once you complete an interview, you are automatically assigned as the **evaluator** for that candidate.
You’ll receive an **evaluation form link** via email and can also access it under the **Evaluations** tab in Workflow Tools.
**Q11. Can I update my evaluation after submitting it in the drive?**
Editing permissions depend on your organization’s settings.
If allowed:
* Navigate to the candidate’s evaluation and click **Edit Evaluation** to update your feedback.
Otherwise, contact your **Recruiter** to reopen your evaluation form.
**Q12. What’s the deadline for submitting my evaluations in a drive?**
Submit your evaluations **within 24 hours** of completing the interview.
Timely submission ensures smooth candidate progression and accurate reporting for drive analytics.
**Q13. Can I view my interview history for completed drives?**
Yes. Go to the **Interviews** section under your interviewer dashboard.
Here, you can view:
* Previously completed interviews in the drive
* Candidate names
* Evaluation status (Submitted/Pending)
* Session outcomes (Attended/No-Show)
This provides a record of your participation and feedback.
***
## **3. Notifications & Communication**
**Q14. Do I continue to receive notifications after being removed from a drive?**
No. Once removed from a drive, you’ll stop receiving all related notifications, reminders, and updates.
However, your previous interviews and evaluations remain visible in your completed drive records.
**Q15. Will I get reminders for my upcoming interviews during a drive?**
Currently, **no automated reminders** are sent for drive interviews.
Please monitor your **Drive Dashboard** or **calendar invite** to stay updated on upcoming sessions.
**Q16. Can I communicate directly with the recruiter or coordinator during a drive?**
Yes. You can contact the recruiter via **email** or **internal chat** as per your organization’s communication process.
For urgent updates (like a no-show or technical issue), use the **Notify Recruiter** or **Report Issue** option in the drive interface (if available).
***
## **4. Technical & Access Support**
**Q17. What should I do if I face technical issues during a drive interview?**
If you experience connectivity, audio, or video issues:
* Refresh or rejoin using the same **Join Interview** link.
* Use **Google Chrome** or **Microsoft Edge** for best performance.
* Check that your **camera/mic permissions** are enabled.
If the problem continues, contact **Talview Support** via the **Help** option, and notify your recruiter.
**Q18. Can I access drive details or join interviews from my mobile device?**
Yes, but desktop or laptop access is recommended for stability.
If joining from a mobile browser:
* Ensure your **camera and microphone** permissions are allowed.
* Maintain a stable network connection.
Some advanced features (like editing evaluations) may not be supported on mobile.
# How to get notified when added or removed from a Drive
Source: https://docs.talview.com/hiring-teams/evaluator/drives/how-tos/how-to-get-notified-when-added-or-removed-from-a-drive
When you're assigned to or removed from a drive in **Talview Workflow Tools**, you'll receive an email notification to keep you informed about your interview responsibilities. In this article, you'll learn how these notifications work and how to access your assigned interviews.
## Getting Notified When You're Added to a Drive
Once a recruiter adds you to a drive, you'll receive an interview invitation email. This notification confirms and provides quick access to join the interview.
### How to Join an Interview?
You can join your assigned interview in two ways:
* Click the join link directly from the invitation email
* Navigate to your Interview Dashboard and select the scheduled interview
The email invitation includes key details such as the **interview date, time and candidate information.**
## Getting Notified When You're Removed from a Drive
If you're removed from a drive, you'll receive an email notification informing you of the change. This ensures you're aware that you're no longer expected to participate in that particular interview.
The removal notification helps you manage your schedule and prevents confusion about upcoming interview commitments.
### **Managing Your Interview Schedule**
To stay on top of your scheduled interviews:
* Check your email regularly for interview notifications
* Review your I\_nterview Dashboard\_ for all scheduled and upcoming interviews
* Update your availability in the system to help coordinators assign drives more effectively
# How to join an interview from the Drive
Source: https://docs.talview.com/hiring-teams/evaluator/drives/how-tos/how-to-join-an-interview-from-the-drive
When you're assigned as an interviewer for a drive in **Talview Workflow Tools**, you'll receive an interview invitation via email. You can join your scheduled interview directly from the email invitation or through the Talview interview dashboard.
## Before You Join
Make sure you have:
* A stable internet connection.
* Your browser permissions enabled for camera and microphone access.
* Joined a few minutes early to ensure your setup is working properly.
## Step-by-Step Guide
### 1. Join from the Email Invitation
Once the drive series is created and you're assigned as an interviewer, you'll receive an email invitation with the interview details.
To join from email:
* Open the interview invitation email.
* Review the interview date, time, and candidate information.
* Click the **Join drive** button in the email.
* You'll be directed to the interview dashboard, click on **Join Now** to begin the interview.
* You'll be taken directly to the interview interface.
### 2. Join from the Interview Dashboard
You can also access your scheduled interviews through Talview Workflow Tools platform.
To join from the dashboard:
* Log in to your Talview account.
* Navigate to the **Interview Dashboard** from the main side panel.
* Locate the scheduled interview from your list of upcoming sessions.
* click on **Join Now** to begin the interview.
* You'll be taken directly to the interview interface.
### **Additional Tips**
* Email invitations are sent when the drive series is created and interviews are assigned.
* You can join the interview up to 10 minutes before the scheduled start time.
* If you don't see the invitation email, check your spam folder or contact the recruiter.
* The interview dashboard shows all your upcoming interviews in one place.
# Why can't I find or edit an evaluation I've already submitted?
Source: https://docs.talview.com/hiring-teams/evaluator/evaluations/diagnostics/why-cant-i-find-or-edit-an-evaluation-i-ve-already-submitted
Submitting an evaluation only to find it missing or locked afterwards can be confusing and disruptive, particularly when you need to make a correction. This is usually caused by a page loading issue, a navigation error, or a permission-related problem on Talview.
In this article, you will find the most common causes and fixes to locate your submitted evaluation and edit it if needed.
***
### 🔎 Troubleshooting Common Issues
| **What Might Be Wrong** | **How to Fix It** |
| :----------------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| The page hasn't loaded the latest data | Try refreshing your browser by pressing `Ctrl + R` (Windows) or `Command + R` (Mac) to reload the page and fetch the latest data. Then navigate back to the candidate and check if your evaluation appears. |
| You're looking under the wrong step | Evaluations are tied to specific steps. Make sure you've navigated to the correct step in the candidate detail view where you originally submitted your evaluation. |
| The candidate has been reassigned to a different evaluator | If the candidate was reassigned after you submitted your evaluation, you may no longer have access to view or edit it. Reach out to the recruiter to confirm your current assignment status for that candidate. |
| The edit option isn't visible due to a browser display issue | Try clearing your browser cache by pressing `Ctrl + Shift + Delete` (Windows) or `Command + Shift + Delete` (Mac), reload the page, and navigate back to the candidate detail view to check again. |
| The workflow or step has been locked by the recruiter | If the recruiter has locked the workflow or step, evaluations may no longer be editable. Check with the recruiter to confirm whether edits are still permitted for that candidate and step. |
| Your browser is preventing the edit option from loading | Try opening the candidate detail view in a different browser. **Chrome**, **Edge**, or **Firefox** are recommended for the best compatibility. |
**Additional Tips**
* If you're unsure whether your evaluation was submitted successfully in the first place, navigate to the candidate detail view and look for your name and recommendation under the relevant step, this confirms the submission went through.
* If you need to make an urgent correction to a submitted evaluation and can't find the edit option, reach out to the recruiter immediately so they're aware of the situation while you work on resolving the access issue.
* Only your own evaluation is editable, you can view but not modify evaluations submitted by other evaluators.
* If the issue persists after trying all the steps above, reach out to your admin or recruiter for further assistance.
# Why can't I see any candidates in my Evaluations list?
Source: https://docs.talview.com/hiring-teams/evaluator/evaluations/diagnostics/why-cant-i-see-any-candidates-in-my-evaluations-list
If your Evaluations list appears empty, it can be frustrating, especially when you're expecting candidates to be ready for review. This is usually caused by a missing assignment, a filter applied to the list, or a access-related issue on Talview. \
In this article, you will find the most common causes and fixes to get your Evaluations list populated and ready to work with.
***
### 🔎 Troubleshooting Common Issues
| **What Might Be Wrong** | **How to Fix It** |
| :------------------------------------------------ | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| No candidates have been assigned to you yet | Check with the recruiter to confirm whether any candidates have been assigned to you for evaluation. Assignments are made manually by the recruiter and you'll receive a notification when they're done. |
| You're logged in with the wrong account | Make sure you're logged in with the correct evaluator credentials. If you have multiple accounts, log out and sign back in with the right one. |
| Your evaluator role hasn't been set up correctly | Your user account must have the **Evaluator** role assigned to it by an admin. If you're unsure, contact your admin to verify your role and permissions. |
| Candidates were assigned to a different evaluator | It's possible the recruiter assigned the candidates to a different evaluator. Reach out to the recruiter to confirm the assignment and request a reassignment if needed. |
| The page hasn't loaded the latest data | Try refreshing your browser by pressing `Ctrl + R` (Windows) or `Command + R` (Mac) to reload the page and fetch the latest data. |
| A filter is hiding candidates from your list | Check if any filters are active on your Evaluations list. Clear all active filters and check if your candidates appear. |
**Additional Tips**
* When a recruiter assigns candidates to you, you'll receive a notification. If you haven't received one, it's likely no assignments have been made yet.
* If you've recently been added as an evaluator for the first time, allow a few minutes for the system to reflect your access before refreshing.
* If the issue persists after trying all the steps above, reach out to your admin or the recruiter who was supposed to assign candidates to you for further assistance.
# Why can't I see other evaluators' evaluations for the same candidate?
Source: https://docs.talview.com/hiring-teams/evaluator/evaluations/diagnostics/why-cant-i-see-other-evaluators-evaluations-for-the-same-candidate
Being unable to view your peers' evaluations for a candidate can make it harder to get a complete picture before or after submitting your own assessment. This is usually caused by a navigation issue, no other evaluations having been submitted yet, or a page loading problem on Talview. \
In this article, you will find the most common causes and fixes to help you locate and view other evaluators' submissions for the same candidate and step.
***
### 🔎 Troubleshooting Common Issues
| **What Might Be Wrong** | **How to Fix It** |
| :----------------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| No other evaluators have submitted their evaluation yet | Other evaluators' submissions are only visible once they've been submitted. If your peers haven't evaluated the candidate yet, there won't be anything to see. Check with the recruiter to confirm whether other evaluators have been assigned and whether they've submitted their evaluations. |
| You're looking in the wrong place for the evaluations | All evaluations across every step are visible together in the evaluation side panel, you don't need to navigate to each step individually to find them. Click the **Evaluate** button on the top right corner of the candidate detail view to open the side panel, where you'll be able to see all evaluations submitted by other evaluators across all steps in one place. |
| The page hasn't loaded the latest data | Try refreshing your browser by pressing `Ctrl + R` (Windows) or `Command + R` (Mac) to reload the page and fetch the latest data. Then navigate back to the candidate detail view and check again. |
| No other evaluators have been assigned to this candidate | It's possible you're the only evaluator assigned to this candidate for that step. Reach out to the recruiter to confirm whether other evaluators were assigned. |
| Your browser cache is causing a display issue | Clear your browser cache by pressing `Ctrl + Shift + Delete` (Windows) or `Command + Shift + Delete` (Mac), reload the page, and navigate back to the candidate detail view to check again. |
| Your browser is blocking the content from loading | Try opening the candidate detail view in a different browser. **Chrome**, **Edge**, or **Firefox** are recommended for the best compatibility. |
| A slow or unstable internet connection is affecting the page | Check your internet connection and switch to a more stable network if possible. Once reconnected, reload the page and check if the other evaluations appear. |
**Additional Tips**
* Other evaluators' submissions are visible to you regardless of whether you've submitted your own evaluation yet, so you don't need to wait until after you've submitted to check.
* If you're expecting evaluations from multiple peers and only some are visible, it's likely that the remaining evaluators haven't submitted theirs yet. Give them some time and check back later.
* If you can see some evaluations but one specific evaluator's submission is missing, ask them directly to confirm whether they've submitted their evaluation for that candidate and step.
* If the issue persists after trying all the steps above, reach out to your admin or recruiter for further assistance.
# Why didn't I receive a notification about assigned candidates?
Source: https://docs.talview.com/hiring-teams/evaluator/evaluations/diagnostics/why-didnt-i-receive-a-notification-about-assigned-candidates
Missing a notification about candidate assignments can cause delays in your evaluation workflow, leaving candidates waiting longer than necessary. This is usually caused by a missing phone number or email configuration, a notification setting issue, or a delivery problem on Talview. \
In this article, you will find the most common causes and fixes to ensure you receive assignment notifications reliably going forward.
***
### 🔎 Troubleshooting Common Issues
| **What Might Be Wrong** | **How to Fix It** |
| :-------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| The notification landed in your spam or junk folder | Check your spam or junk folder for the assignment notification email. If you find it there, mark it as **Not Spam** to ensure future notifications land in your inbox. |
| The assignment was made to a different evaluator | It's possible the recruiter assigned the candidates to a different evaluator by mistake. Reach out to the recruiter to confirm whether the assignment was intended for you. |
| Your email address on your account is incorrect | If your account has an incorrect email address, notifications won't reach you. Contact your admin to verify and update your email address if needed. |
| The recruiter hasn't completed the assignment yet | The notification is only sent once the assignment is successfully completed by the recruiter. Check with the recruiter to confirm whether the assignment has been made. |
| Your organisation's email server is filtering out notifications | Corporate or institutional email servers sometimes filter out automated notification emails. Check with your IT team to ensure notification emails from the platform are whitelisted. |
| There was a temporary notification delivery delay | Notification emails can occasionally be delayed due to server load. Wait a few minutes and check your inbox again before taking further action. |
| Platform-level notifications aren't enabled for your account | Your account may not have notifications enabled. Contact your admin to confirm that notification settings are correctly configured for your evaluator account. |
**Additional Tips**
* Even if you didn't receive a notification, you can still check your **Evaluations** tab directly to see if any new candidates have been assigned to you, the list updates regardless of whether the notification was delivered.
* If you're consistently missing notifications, ask your admin to review your account's notification settings and confirm your email address is correctly registered.
* If your organisation uses a corporate email domain, work with your IT team to whitelist notification emails from the platform to prevent them from being filtered out in the future.
* If the issue persists after trying all the steps above, reach out to your admin or recruiter for further assistance.
# Why is a candidate's resume not loading or accessible from the Evaluations list?
Source: https://docs.talview.com/hiring-teams/evaluator/evaluations/diagnostics/why-is-a-candidates-resume-not-loading-or-accessible-from-the-evaluations-list
Being unable to access a candidate's resume from the Evaluations list can slow down your review process before you even open the candidate's detail view. This is usually caused by an upload issue, a browser problem, or the resume simply not having been added yet on Talview. In this article, you will find the most common causes and fixes to get the resume loading correctly so you can proceed with your evaluation.
***
### 🔎 Troubleshooting Common Issues
| **What Might Be Wrong** | **How to Fix It** |
| :------------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| The resume hasn't been uploaded yet | The resume may not have been uploaded by the recruiter or the candidate. Reach out to the recruiter to confirm whether a resume is available for that candidate. |
| The file failed to upload correctly | The resume may have been uploaded but didn't go through successfully. Ask the recruiter to re-upload the resume and try accessing it again. |
| Your browser is blocking the file from opening | Try opening the resume in a different browser. **Chrome**, **Edge**, or **Firefox** are recommended for the best compatibility. |
| The page hasn't loaded the latest data | Try refreshing your browser by pressing `Ctrl + R` (Windows) or `Command + R` (Mac) to reload the page and fetch the latest data. |
| The file format isn't supported by your browser | Resumes are uploaded in **PDF** or **DOCX** format. If your browser can't open the file, try downloading it first and opening it with a compatible application such as **Adobe Acrobat** for PDF or **Microsoft Word** for DOCX. |
| A slow or unstable internet connection is preventing the file from loading | Check your internet connection and switch to a more stable network if possible. Once reconnected, try accessing the resume again. |
| The file size is too large to load quickly | Resume files can be up to **5 MB** in size. If you're on a slow connection, give the file a few extra moments to load before trying again. |
**Additional Tips**
* If the resume loads partially or appears corrupted, ask the recruiter to re-upload the file in a fresh **PDF** or **DOCX** format to ensure it renders correctly.
* Avoid opening multiple large files at the same time in your browser, this can slow down loading times across all open tabs.
* If you're consistently unable to open resumes across multiple candidates, the issue may be browser-related. Try clearing your browser cache by pressing `Ctrl + Shift + Delete` (Windows) or `Command + Shift + Delete` (Mac) and reloading the page.
* If the issue persists after trying all the steps above, reach out to your admin or recruiter for further assistance.\\
# Why is an assigned Candidate missing from my Evaluations list?
Source: https://docs.talview.com/hiring-teams/evaluator/evaluations/diagnostics/why-is-an-assigned-candidate-missing-from-my-evaluations-list
Submitting an evaluation only to find it missing or locked afterwards can be confusing and disruptive, particularly when you need to make a correction. This is usually caused by a page loading issue, a navigation error, or a permission-related problem on Talview. In this article, you will find the most common causes and fixes to locate your submitted evaluation and edit it if needed.
***
### 🔎 Troubleshooting Common Issues
| **What Might Be Wrong** | **How to Fix It** |
| :----------------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| The page hasn't loaded the latest data | Try refreshing your browser by pressing `Ctrl + R` (Windows) or `Command + R` (Mac) to reload the page and fetch the latest data. Then navigate back to the candidate and check if your evaluation appears. |
| You're looking under the wrong step | Evaluations are tied to specific steps. Make sure you've navigated to the correct step in the candidate detail view where you originally submitted your evaluation. |
| The candidate has been reassigned to a different evaluator | If the candidate was reassigned after you submitted your evaluation, you may no longer have access to view or edit it. Reach out to the recruiter to confirm your current assignment status for that candidate. |
| The edit option isn't visible due to a browser display issue | Try clearing your browser cache by pressing `Ctrl + Shift + Delete` (Windows) or `Command + Shift + Delete` (Mac), reload the page, and navigate back to the candidate detail view to check again. |
| The workflow or step has been locked by the recruiter | If the recruiter has locked the workflow or step, evaluations may no longer be editable. Check with the recruiter to confirm whether edits are still permitted for that candidate and step. |
| Your browser is preventing the edit option from loading | Try opening the candidate detail view in a different browser. **Chrome**, **Edge**, or **Firefox** are recommended for the best compatibility. |
**Additional Tips**
* If you're unsure whether your evaluation was submitted successfully in the first place, navigate to the candidate detail view and look for your name and recommendation under the relevant step, this confirms the submission went through.
* If you need to make an urgent correction to a submitted evaluation and can't find the edit option, reach out to the recruiter immediately so they're aware of the situation while you work on resolving the access issue.
* Only your own evaluation is editabl you can view but not modify evaluations submitted by other evaluators.
* If the issue persists after trying all the steps above, reach out to your admin or recruiter for further assistance.
# Why is resume fitment or fitment reasoning not showing for a candidate?
Source: https://docs.talview.com/hiring-teams/evaluator/evaluations/diagnostics/why-is-resume-fitment-or-fitment-reasoning-not-showing-for-a-candidate
Finding that a candidate's resume fitment or its reasoning is missing can make it harder to assess how well they match the role before diving into a full evaluation. This is usually caused by a configuration setting, a missing resume, or a processing delay on Talview. In this article, you will find the most common causes and fixes to understand why the fitment information isn't showing and what you can do about it.
***
### 🔎 Troubleshooting Common Issues
| **What Might Be Wrong** | **How to Fix It** |
| :------------------------------------------------------------ | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Resume fitment isn't configured for the workflow | Resume fitment is an optional feature that must be enabled for the organization. If it hasn't been configured, it won't appear for any candidate. Check with the admin to confirm whether fitment is enabled for this workflow. |
| The candidate's resume hasn't been uploaded | Resume fitment is generated based on the candidate's resume. If no resume has been uploaded, fitment can't be calculated. Ask the recruiter to upload the candidate's resume and check again after a few minutes. |
| The resume fitment configuration hasn't been set up | Fitment is calculated based on the resume fitment configuration set up for the workflow. If this configuration hasn't been completed, fitment scores and reasoning won't be generated for any candidate in that workflow. Reach out to your admin to confirm whether the resume fitment configuration has been set up correctly for this workflow. |
| The fitment is still being processed | After a resume is uploaded, fitment may take a few minutes to generate. Wait a few minutes and refresh your browser by pressing `Ctrl + R` (Windows) or `Command + R` (Mac) before checking again. |
| The resume was uploaded in an unsupported format | Fitment can only be generated from resumes uploaded in **PDF** or **DOCX** format. If the resume was uploaded in a different format, ask the recruiter to re-upload it in the correct format. |
| Only fitment reasoning is missing but the category is visible | The reasoning may not have been generated fully. Try refreshing the page. If it still doesn't appear, reach out to the recruiter to check on the fitment configuration for that workflow. |
**Additional Tips**
* Resume fitment is system-generated based on the job description associated with the workflow. If the job description is incomplete or too vague, the fitment reasoning may not be detailed enough to be useful, encourage the recruiter to use a thorough job description for better results.
* If fitment is missing for multiple candidates in the same workflow, it's likely a workflow-level configuration issue rather than a candidate-specific one. Flag this to the recruiter so they can address it across all affected candidates at once.
* Even if resume fitment isn't available, you can still proceed with your evaluation using the candidate's resume, registration form details, assessment scores, and interview performance.
* If the issue persists after trying all the steps above, reach out to your admin or recruiter for further assistance.
# Why is the assessment score report or playback not loading?
Source: https://docs.talview.com/hiring-teams/evaluator/evaluations/diagnostics/why-is-the-assessment-score-report-or-playback-not-loading
Being unable to view a candidate's score report or assessment playback can hold up your evaluation and leave you without key information you need to make a decision. This is usually caused by the candidate not having completed the assessment yet, a browser issue, or a connectivity problem on Talview.
In this article, you will find the most common causes and fixes to get the score report or playback loading so you can proceed with your evaluation.
***
### 🔎 Troubleshooting Common Issues
| **What Might Be Wrong** | **How to Fix It** |
| :---------------------------------------------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| The candidate hasn't completed the assessment yet | Score reports and playbacks are only available once the candidate's assessment status shows **Completed**. If the status shows **Invited** or **In Progress**, the report won't be available yet. Check the candidate's status and wait for them to complete it before trying again. |
| The page hasn't loaded the latest data | Try refreshing your browser by pressing `Ctrl + R` (Windows) or `Command + R` (Mac) to reload the page and fetch the latest data. |
| Your browser is blocking the content from loading | Try opening the candidate's assessment details in a different browser. **Chrome**, **Edge**, or **Firefox** are recommended for the best compatibility. |
| A slow or unstable internet connection is preventing the content from loading | Check your internet connection and switch to a more stable network if possible. Once reconnected, try accessing the score report or playback again. |
| The playback is still being processed | For **Ivy** *(Interview-Based)* and **async video** assessments, playback may take some time to process after the candidate completes the assessment. Wait a few minutes and refresh the page before trying again. |
| Your browser cache is causing a loading issue | Clear your browser cache by pressing `Ctrl + Shift + Delete` (Windows) or `Command + Shift + Delete` (Mac), reload the page, and try accessing the content again. |
| The assessment isn't configured to generate a score report | Some assessment types may not produce a numerical or categorical score report. Check with the recruiter to confirm what outputs are expected for that particular assessment. |
**Additional Tips**
* If the playback loads but freezes or buffers frequently, try lowering the playback quality if that option is available, or switch to a faster network connection.
* For **Ivy** and **async video** assessments, playback processing times can vary. If the playback still isn't available after a significant wait, reach out to the recruiter to check whether the session was recorded successfully.
* If the score report is missing for multiple candidates in the same workflow, it may be an assessment configuration issue rather than a candidate-specific one. Flag this to the recruiter so they can investigate across all affected candidates at once.
* If the issue persists after trying all the steps above, reach out to your admin or recruiter for further assistance.
# Why is the evaluation form not loading in the evaluation side panel?
Source: https://docs.talview.com/hiring-teams/evaluator/evaluations/diagnostics/why-is-the-evaluation-form-not-loading-in-the-evaluation-side-panel
Being unable to load the evaluation form when you're ready to submit your assessment of a candidate can bring your workflow to a halt. This is usually caused by a configuration issue, a browser problem, or a connectivity issue on Talview.
In this article, you will find the most common causes and fixes to get the evaluation form loading correctly so you can complete and submit your evaluation without delay.
***
### 🔎 Troubleshooting Common Issues
| **What Might Be Wrong** | **How to Fix It** |
| :------------------------------------------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| No evaluation form has been configured for this step | Evaluation forms are optional and must be configured for each candidate and step by the recruiter or admin. If no form has been set up, it won't appear in the side panel. Check with the recruiter to confirm whether a form is expected for this candidate and step. |
| The page hasn't loaded the latest data | Try refreshing your browser by pressing `Ctrl + R` (Windows) or `Command + R` (Mac) to reload the page and fetch the latest data. Then reopen the evaluation side panel and check again. |
| Your browser is blocking the form from loading | Try opening the platform in a different browser. **Chrome**, **Edge**, or **Firefox** are recommended for the best compatibility. |
| Your browser cache is causing a display issue | Clear your browser cache by pressing `Ctrl + Shift + Delete` (Windows) or `Command + Shift + Delete` (Mac), reload the page, and reopen the evaluation side panel to check if the form appears. |
| A slow or unstable internet connection is preventing the form from loading | Check your internet connection and switch to a more stable network if possible. Once reconnected, reopen the evaluation side panel and try again. |
| The form was configured incorrectly | The evaluation form may have been set up with an error, preventing it from loading properly. Reach out to the recruiter or admin to verify that the form has been configured correctly for this candidate and step. |
| You're viewing the wrong step in the candidate detail view | Evaluation forms are tied to specific steps. Make sure you've navigated to the correct step in the candidate detail view before opening the evaluation side panel. |
**Additional Tips**
* If the evaluation form is missing but you're confident one should be there, don't submit your evaluation yes, reach out to the recruiter or admin first to get the form set up correctly before proceeding.
* If the form loads but some fields appear blank or broken, try refreshing the page and reopening the side panel. If the issue continues, flag it to the recruiter or admin so they can review the form configuration.
* You can still add your **comments** and **recommendation** in the evaluation side panel even if the form isn't loading but confirm with the recruiter whether the form is required before submitting without it.
* If the issue persists after trying all the steps above, reach out to your admin or recruiter for further assistance.
# Why is the interview recording not available for a completed interview?
Source: https://docs.talview.com/hiring-teams/evaluator/evaluations/diagnostics/why-is-the-interview-recording-not-available-for-a-completed-interview
Discovering that a recording is missing for a completed interview can make it difficult to assess the candidate's performance thoroughly. This is usually caused by the recording not being captured during the session, a processing delay, or a configuration issue on Talview. \
In this article, you will find the most common causes and fixes to understand why the recording isn't available and what you can do about it.
***
### 🔎 Troubleshooting Common Issues
| **What Might Be Wrong** | **How to Fix It** |
| :------------------------------------------------------------------------------ | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| The interview was conducted in person and wasn't recorded | Recordings are only available for **online interviews**. In-person interviews aren't recorded. Check the interview type with the recruiter to confirm whether a recording was expected. |
| The recording is still being processed | Recordings may take some time to become available after the interview is completed. Wait a few minutes and refresh your browser by pressing `Ctrl + R` (Windows) or `Command + R` (Mac) before checking again. |
| The recording wasn't captured during the session | Technical issues during the interview session may have prevented the recording from being captured. Reach out to the recruiter to confirm whether the session was recorded successfully. |
| The page hasn't loaded the latest data | Try refreshing your browser by pressing `Ctrl + R` (Windows) or `Command + R` (Mac) to reload the page and fetch the latest data. |
| Your browser is blocking the recording from loading | Try opening the interview details in a different browser. **Chrome**, **Edge**, or **Firefox** are recommended for the best compatibility. |
| A slow or unstable internet connection is preventing the recording from loading | Check your internet connection and switch to a more stable network if possible. Once reconnected, try accessing the recording again. |
| Your browser cache is causing a loading issue | Clear your browser cache by pressing `Ctrl + Shift + Delete` (Windows) or `Command + Shift + Delete` (Mac), reload the page, and try accessing the recording again. |
| The candidate had a No Show status | If the candidate didn't attend the interview, there won't be a recording available. Check the candidate's participation status in the interview timeline to confirm. |
| The candidate or interviewer opted out of recording the session | For compliance reasons, candidates and interviewers have the option to decline recording during the interview session. If either party opted out, no recording will be available. Check with the recruiter to confirm whether this was the case before following up further. |
**Additional Tips**
* If the recording is missing for multiple candidates from the same interview session, it's likely a session-level recording issue rather than a candidate-specific one. Flag this to the recruiter so they can investigate across all affected candidates at once.
* If the recording still isn't available after a significant wait, reach out to the recruiter to check whether the interview platform captured the session correctly.
* Even if a recording isn't available, you can still proceed with your evaluation using the candidate's assessment scores, resume fitment, screening details, and any notes you may have taken during the interview.
* If the issue persists after trying all the steps above, reach out to your admin or recruiter for further assistance.
# How to Access and Fill Out a Evaluation Form
Source: https://docs.talview.com/hiring-teams/evaluator/evaluations/how-tos/how-to-access-and-fill-out-a-evaluation-form
As an interviewer in **Talview's Workflow Tools**, submitting a thorough evaluation is a critical step in the candidate selection process. The evaluation form allows you to provide structured feedback and make hiring decisions that help align your team and accelerate the recruitment workflow.
In this article, you'll learn how to access the evaluation form for a candidate and complete it with detailed feedback to support your hiring decision.
## Step-by-Step Guide
### **1. Select the Candidate**
* Log in to Workflow Tools as an *Evaluator.*
* Click on the **candidate's name** or email address to access their details and track their evaluation progress.
### **2. Navigate to the Evaluation Tab**
* In the candidate’s interview details side panel, press the **Evaluate** button to begin the evaluation process.
* This tab allows evaluators to provide feedback by filling out a form.
### **3.** Fill Out the Evaluation Form
* Expand the **Evaluation** dropdown.
* Fill the form with mandatory field validation.
* Click on **✔️Select/ ✖️Turned Down/ ⏸️Hold** button, based on your decision about the candidate.
> Upon a success notification, the evaluation is now submitted and accessible to recruiters and hiring managers within the centralized workflow dashboard.
# How to check face authentication details in Interview Insights
Source: https://docs.talview.com/hiring-teams/evaluator/evaluations/how-tos/how-to-check-face-authentication-details-in-interview-insights
During a Live interview, Talview periodically captures the candidate's face and runs authentication checks to verify their identity. These results are stored within Interview Insights and can be reviewed after the interview is completed.
In this article, you will learn how to access and review the face authentication details for a candidate from the Interview Summary page.
***
### Before You Begin
Make sure you have:
* Logged in to Workflow Tools with your evaluator credentials.
* Opened the **Interview Summary** page for a candidate with a completed interview.
***
### Step-by-Step Guide
**1. Open the Verification tab**
* On the Interview Summary page, the right panel has two tabs at the top - **Overview** and **Verification**. Click on the **Verification** tab.
* This tab is dedicated to reviewing the candidate's authentication and compliance check details for the interview session.
**2. Identify the session**
* At the top of the Verification tab, you'll see the **Session ID** for the interview, along with the date of the session.
* If the candidate has been through multiple interview rounds, the captures are identified by their time and date, making it easy to distinguish between them.
**3. Check the Face Authentication status**
Below the Session ID, look for the **Face Authentication** label with a status icon.
* A green **Passed** badge next to the timestamp means the candidate's face was successfully verified against the reference image. The system confirmed that the person attending the interview matched the candidate on record.
* If the authentication has failed, the badge will indicate accordingly, signaling a potential identity mismatch that may require further review.
**4. Review the face capture photo**
Below the status badge, a large face capture photo is displayed. This is the image captured during the authentication check.
* Review this photo to visually confirm the candidate's identity.
* The timestamp next to the photo tells you exactly when during the session this capture was taken (e.g., 4:28 PM | 15 Apr 2026).
**5. Browse the timestamped face capture timeline**
On the left side of the Verification tab, you'll see a vertical timeline of face capture thumbnails taken across all interview rounds (e.g., 4:28 PM, 4:22 PM, 3:58 PM, 2:58 PM).
* Click on any thumbnail to view the full-size capture on the right side of the panel.
* These periodic captures allow you to verify that the same person was present across all interview rounds, not just the most recent one.
* The timeline is arranged in reverse chronological order, with the most recent capture at the top.
**6. Compare against the reference image**
Below the main face capture photo, you'll find the **Reference** section. This shows a face capture from a previous interview session along with its timestamp and date.
* The system uses this reference image to perform cross-session face matching - verifying that the same candidate appeared in both the current and previous interview rounds.
* Compare the reference image visually with the current session captures to confirm consistency across rounds.
**7. Expand or collapse session details**
If the candidate has face captures from multiple sessions, you can expand or collapse each session's details using the arrow icon (∧) next to the session header.
* This keeps the Verification tab organized when reviewing candidates who have gone through several interview rounds.
***
**Additional Tips**
* The face authentication check runs automatically during the interview session. Neither the interviewer nor the candidate needs to trigger it manually.
* If a candidate's authentication status shows as failed or the face captures look inconsistent, consider discussing this with the recruiting team before finalizing your evaluation. A failed check does not automatically disqualify a candidate, it flags a potential concern that warrants further review.
* You can switch between the **Overview** and **Verification** tabs at any time without losing your place. Reviewing the authentication details alongside the AI-generated insights gives you a more complete picture of the candidate's interview.
* The **Authentication** column on the workflow dashboard also shows a quick status (e.g., **Matched**) for each candidate, so you can identify candidates who need a closer look before opening their Interview Insights.
# How to Edit a Submitted Evaluation
Source: https://docs.talview.com/hiring-teams/evaluator/evaluations/how-tos/how-to-edit-a-submitted-evaluation
After submitting an evaluation in **Talview's Workflow Tools**, evaluators may need to make changes to their feedback or recommendation decisions. The platform provides flexibility for evaluators to edit their submitted evaluations before final hiring decisions are made, ensuring accurate and thoughtful candidate assessments.
In this article, evaluators will learn how to edit a previously submitted evaluation and understand the different recommendation statuses available.
## Step-by-Step Guide
### **1. Select the Candidate**
* Log in to Workflow Tools as an *Evaluator.*
* Click on the **candidate's name or email address** from the Evaluations tab to view and manage their evaluation details.
### **2. Viewing the evaluation**
In the candidate’s interview details side panel,
* Click on **View Evaluation** to review and manage the candidate’s feedback.
### **3. Edit and manage a candidate’s evaluation**
* At the bottom right of the evaluation panel, click the **Edit** button (represented by a ✏️ icon).
* This action unlocks modifications to both the detailed feedback text and the recommendation status.
### **4. Modify Your Evaluation**
* Update the **Detailed feedback** text field with revised comments or additional observations about the candidate.
* The feedback should provide comprehensive insights supporting the evaluation decision.
### **4. Update the Recommendation Status**
* Choose the appropriate recommendation status by clicking one of the four available options: ✔️Select/ ✖️Turned Down/ ⏸️Hold / 🚫Cancel.
* Each status reflects a different hiring decision for the candidate.
### **5. Save your changes**
* After making the necessary edits, click the updated recommendation button to save and resubmit the evaluation.
* The revised evaluation will replace the previous submission and update the candidate's status in the workflow.
### **Understanding Recommendation Statuses:**
* **SELECT** (displayed with a green background and “✔️” icon) -
* Indicates that the evaluator recommends advancing the candidate to the next interview stage or extending an offer.
* This positive recommendation signals that the candidate's qualifications, technical skills, and cultural fit align well with the position requirements.
* **TURN DOWN** (displayed with a red background and “✖️” icon)
* Indicates that the evaluator does not recommend the candidate for progression.
* This decision suggests the candidate does not meet the necessary qualifications or requirements for the role.
* **HOLD** (displayed with a yellow background and “⏸️” icon)
* Places the candidate in a reserved state for further consideration.
* Evaluators use this status when they need additional information, want to compare the candidate with others, or require more time before making a final decision.
* **CANCEL** (displayed with a grey background and “🚫” icon)
* Allows evaluators to exit the editing process without saving any changes made to the evaluation.
* This returns the evaluation to its previously submitted state.
# How to interpret AI-generated interview summaries
Source: https://docs.talview.com/hiring-teams/evaluator/evaluations/how-tos/how-to-interpret-ai-generated-interview-summaries
Once an interview is completed, Talview automatically generates an AI-powered summary that captures the key takeaways from the session. This summary gives evaluators and recruiters a quick understanding of how the candidate performed without needing to watch the full recording.
In this article, you will learn how to read and make sense of the AI-generated Interview Summary within the Interview Insights page.
***
### Before You Begin
Make sure you have:
* Logged in to Workflow Tools with your evaluator credentials.
* Open the **Interview Summary** page for a candidate with a completed interview.
***
### Step-by-Step Guide
**1. Open the Overview tab**
On the Interview Summary page, the right panel defaults to the **Overview** tab. This is where all the AI-generated insights are displayed.
* The **Overview** tab provides the Interview Summary, including key discussion points, strengths, areas of improvement, and recommended next steps.
**2. Read the Interview Summary section**
The first section under the candidate's name and resume link is the **Interview Summary**. Click the section header to expand or collapse it.
* This is a concise, AI-generated paragraph that captures the overall flow of the interview - what the candidate demonstrated, where they struggled, and how the session concluded.
* Use this as a high-level snapshot before diving into the detailed breakdowns below.
**3. Go through the Key Discussion Points**
The **Key Discussion Points** section provides a topic-by-topic breakdown of what was discussed during the interview.
* Each point begins with a **topic label** (e.g., Event loop, Hoisting, Callback hell and solutions) followed by a brief description of how the candidate responded.
* This section is particularly useful for understanding the breadth of topics covered and how the candidate handled each one individually.
**4. Review the Strengths**
Scroll down to the **Strengths** section. This lists specific areas where the candidate performed well during the interview.
* Each strength is presented as a bullet point, referencing concrete examples from the conversation (e.g., correctly explaining a technical concept or proposing a valid approach to a problem).
* These help you quickly identify what the candidate brings to the table.
**5. Review the Areas of Improvement**
The **Areas of Improvement** section highlights where the candidate fell short or showed uncertainty.
* Like the Strengths section, each area is presented as a bullet point with specific examples from the interview (e.g., giving an incorrect definition, needing guidance to complete a task).
* These help you weigh the candidate's areas of improvement against their strengths when forming your evaluation.
**6. Check the Recommended Next Steps**
The final section under the Interview Summary is **Recommended Next Steps**. This provides AI-generated suggestions for what the hiring team should consider doing next.
* Recommendations might include re-running a specific exercise, asking the candidate to submit additional work, or clarifying experience claims in a follow-up conversation.
* Treat these as guidance to inform your decision, not as final directives.
***
**Additional Tips**
* All sections under the Overview tab are collapsible. Click the arrow icon (∧ or ∨) on any section header to expand or collapse it, making it easier to focus on the areas most relevant to your evaluation.
* The AI-generated summary is based on the full interview session. For additional context on any specific point, you can play back the interview recording in the left panel.
* To access the candidate's resume while reviewing the summary, click the **Resume** link below the candidate's name, or use the **Resume Preview** icon in the top-right action bar.
# How to Interpret Competency Scores in Interview Insights
Source: https://docs.talview.com/hiring-teams/evaluator/evaluations/how-tos/how-to-interpret-competency-scores-in-interview-insights
After an interview is completed, Talview generates an AI-powered breakdown of the candidate's performance including their strengths, areas of improvement, and competency-wise scores.
In this article, you will learn how to locate and read these sections within Interview Insights.
***
### Before You Begin
Make sure you have:
* Logged in to Workflow Tools with your evaluator credentials.
* Opened the **Interview Summary** page for a candidate with a completed interview.
***
### Step-by-Step Guide
**1. Open the Overview tab**
On the Interview Summary page, make sure you're on the **Overview** tab in the right panel.
**2. Review the Strengths**
Scroll past the Interview Summary and Key Discussion Points sections to find **Strengths**.
* Each bullet point references a specific example from the interview where the candidate performed well, such as correctly explaining a concept or proposing a valid approach to a problem.
**3. Review the Areas of Improvement**
Below Strengths, the **Areas of Improvement** section highlights where the candidate struggled or gave incomplete answers.
* Each point references what actually happened during the interview, such as providing a vague explanation, needing guidance, or being unable to complete a task independently.
**4. Expand the Candidate Performance section**
Scroll to the bottom of the Overview tab and expand the **Candidate Performance** section using the arrow icon (∨).
* This displays the candidate's scores organized by individual competencies assessed during the interview (e.g., problem-solving, technical knowledge, communication).
* Higher scores indicate strong ability in that competency. Lower scores suggest the candidate struggled in that area.
**5. Read the sections together**
The three sections work best as a combined view rather than in isolation.
* A low competency score will often correspond to a specific area of improvement called out above, and vice versa. This consistency gives you confidence in the overall assessment.
* Use the **Key Discussion Points** section to add context to any strength, area of improvement, or score that you want to understand in more detail.
***
**Additional Tips**
* These sections are AI-generated and should be used as data points to support your evaluation, not as the sole basis for a hiring decision.
* If a score or area of improvement seems unexpected, play back the relevant portion of the recording in the left panel to verify.
* All sections are collapsible using the arrow icon (∧ or ∨) on the section header.
# How to Submit an Evaluation for a Candidate
Source: https://docs.talview.com/hiring-teams/evaluator/evaluations/how-tos/how-to-submit-an-evaluation-for-a-candidate
Talview's Workflow Tools platform streamlines the evaluation submission process for evaluators, enabling them to provide detailed feedback and make selection decisions directly within a unified workspace.
In this article, evaluators will learn how to submit comprehensive evaluations for candidates, helping hiring teams align on top talent and accelerate decision-making.
## Step-by-Step Guide
### **1. Select the Candidate**
* Log in to Workflow Tools as an *Evaluator.*
* Click on the **candidate's name** or email address to access their details and track their evaluation progress.
### **2. Navigate to the Evaluation Tab**
* In the candidate’s interview details side panel, press the **Evaluate** button to begin the evaluation process.
* This tab allows evaluators to review existing feedback or provide new evaluation input.
### **3. Add Your Evaluation Feedback**
* Expand the **Evaluation** dropdown and enter detailed feedback about the candidate in the provided text box.
* Click on ✔️Select/ ✖️Turned Down/ ⏸️Hold, based on your decision about the candidate.
> Upon a success notification, the evaluation is now submitted and accessible to recruiters and hiring managers within the centralized workflow dashboard.
# How to use Interview Insights to Evaluate Candidates
Source: https://docs.talview.com/hiring-teams/evaluator/evaluations/how-tos/how-to-use-interview-insights-to-evaluate-candidates
Making a hiring decision requires weighing multiple data points, how the candidate performed, where they excelled, where they struggled, and whether their profile aligns with the role. Talview's Interview Insights consolidates all of this into a single view, giving you the information you need to confidently recommend whether to advance, hold, or pass on a candidate.
In this article, you will learn how to use the different components of Interview Insights to arrive at a well-informed hiring decision and submit your recommendation.
***
### Before You Begin
Make sure you have:
* Logged in to Workflow Tools with your recruiter or evaluator credentials.
* Open the **Interview Summary** page for a candidate with a completed interview.
***
### Step-by-Step Guide
**1. Start with the overall Interview Summary**
On the **Overview** tab, read the **Interview Summary** paragraph at the top.
* This gives you the high-level narrative of the interview - what happened, how the candidate responded overall, and how the session ended.
* Ask yourself: does this summary leave you with a positive, neutral, or cautious impression? Use that as your starting frame of reference.
**2. Weigh the Strengths against the Areas of Improvement**
Review the **Strengths** and **Areas of Improvement** sections together rather than in isolation.
* Count isn't everything a candidate with three strengths and five areas of improvement isn't automatically a rejection. What matters is relevance. One strength that directly addresses a critical role requirement can outweigh multiple weaknesses in peripheral areas.
* Similarly, a single area of improvement in a must-have skill for the role may be a significant concern even if the rest of the interview went well.
**3. Check alignment with the job description**
Click the **Job Description Preview** icon in the top-right action bar to open the role's requirements.
* Map the candidate's strengths and weaknesses to the specific skills and qualifications listed in the job description.
* Focus on the non-negotiable requirements first. If the candidate's weaknesses fall primarily in nice-to-have areas, the overall picture may still be strong.
**4. Review the Key Discussion Points for depth**
Scroll through the **Key Discussion Points** to understand how the candidate handled each topic.
* Look for patterns. Did the candidate struggle across most topics, or were the issues concentrated in one or two areas? Scattered issues across many topics may indicate a broader readiness concern, while a concentrated gap might be addressable through training or a follow-up assessment.
* Pay attention to how the candidate responded when challenged, did they recover, ask clarifying questions, and work through problems, or did they stall?
**5. Factor in the Competency Scores**
Expand the **Candidate Performance** section and review the competency-wise scores.
* These scores give you a structured, numerical perspective to complement the qualitative insights in the summary sections above.
* If a candidate's competency scores are consistently strong but the Areas of Improvement section calls out a few specific moments, the overall signal may still be positive. Conversely, if scores are low across the board, the qualitative sections are likely to confirm that pattern.
**6. Consider the Recommended Next Steps**
Review the **Recommended Next Steps** section before making your final decision.
* If the AI suggests significant follow-up actions, such as re-running a technical exercise or asking for additional work samples, consider whether a **Hold** recommendation might be more appropriate than a definitive Select or Turn Down. This gives the hiring team the option to gather more information before committing.
* If the recommendations are minor or confirmatory in nature (e.g., clarifying a specific experience claim), they're unlikely to change the overall direction of your decision.
**7. Verify the candidate's identity**
Before finalizing your decision, switch to the **Verification** tab and confirm the candidate's face authentication status.
* A **Passed** status confirms the candidate's identity was verified throughout the session.
* If the authentication raised any flags, factor that into your decision and flag it for the recruiting team.
**8. Watch key moments from the recording**
If any part of the AI-generated insights feels unclear or you want to validate a specific data point, play back the interview recording in the left panel.
* Focus on the moments related to the candidate's strongest strengths or most concerning weaknesses. Watching even a few minutes of relevant footage can add confidence to your decision.
**9. Submit your recommendation**
Once you've reviewed all the available insights and are confident in your assessment, click the **Evaluate** button in the top-right corner.
* A side panel will open where you can:
* Write detailed comments summarizing your reasoning.
* Fill out an evaluation form, if one is configured for this step.
* Select your recommendation: **Select** (advance the candidate), **Turn Down** (do not recommend), or **Hold** (reserve for further consideration).
* Your recommendation, along with your comments, will be visible to recruiters and other stakeholders in the workflow dashboard.
***
**Additional Tips**
* There's no single "right" section to base your decision on. The value of Interview Insights is in the combination the AI summary gives you the narrative, the strengths and weaknesses give you the specifics, the competency scores give you the structure, and the recording gives you the full context. Use them together.
* You can always return to edit your submitted evaluation if new information comes to light or if you want to revise your recommendation after reviewing additional candidates.
* The candidate's resume is available throughout the process via the **Resume Preview** icon, so you can cross-reference their claimed experience with their actual interview performance at any point.
# How to use Playback with Interview Insights
Source: https://docs.talview.com/hiring-teams/evaluator/evaluations/how-tos/how-to-use-playback-with-interview-insights
The Interview Insights page includes the full interview recording alongside the AI-generated analysis. Rather than relying solely on the written insights, you can play back specific moments from the session to verify key data points, pick up on nuances like tone and hesitation, and build a more confident evaluation.
In this article, you will learn how to use Talview's interview playback in combination with the Interview Insights sections.
***
#### Before You Begin
Make sure you have:
* Logged in to Workflow Tools with your evaluator credentials.
* Opened the **Interview Summary** page for a candidate with a completed interview.
***
#### Step-by-Step Guide
**1. Identify what to verify**
Before playing the recording, review the **Overview** tab - specifically the **Key Discussion Points**, **Strengths**, and **Areas of Improvement** sections.
* Note any points that seem unclear, surprising, or that you want more context on. These are the moments worth revisiting in the recording.
**2. Play back the recording**
In the left panel, click the **Play** button to start the interview recording.
* You don't need to watch the entire session. Use the **Key Discussion Points** as a guide to locate the specific moments you want to verify.
* The recording captures details that a written summary cannot - tone, pauses, how the candidate recovered after a mistake, and how they responded to follow-up questions.
**3. Cross-reference with the Transcript**
Switch to the **Transcript** tab to read the exact words spoken during the session.
* Use the timestamps in the transcript to locate specific exchanges quickly, then play back that portion of the recording for the full context.
**4. Factor your findings into your evaluation**
After verifying the moments that matter most, click the **Evaluate** button in the top-right corner to submit your assessment.
* Reference specific evidence from both the insights and the recording in your comments. For example, rather than writing "the candidate struggled with linked lists," note that the candidate was unable to articulate the pointer logic despite guided prompting - as captured in the Areas of Improvement and confirmed in the recording.
***
**Additional Tips**
* Even revisiting two or three key moments from the recording can significantly increase the accuracy of your evaluation. A full rewatch is rarely necessary.
* If you notice a discrepancy between the AI-generated insights and what you hear in the recording, mention it in your evaluation comments. This helps the hiring team get a complete picture.
* The candidate's resume is available via the **Resume Preview** icon in the top-right action bar if you want to cross-reference claims while watching the recording.
# How to View a Submitted Evaluation
Source: https://docs.talview.com/hiring-teams/evaluator/evaluations/how-tos/how-to-view-a-submitted-evaluation
As an evaluator on **Talview's Workflow Tools**, reviewing the feedback and ratings you've already submitted for candidates helps maintain consistency, track your assessment history, and ensure alignment with hiring decisions.
In this article, evaluators will learn how to access and view their submitted evaluations for candidates they have already assessed.
## Step-by-Step Guide
### **1. Select the Candidate**
* Log in to Workflow Tools as an **Evaluator.**
* Click on the **candidate's name** or email address from the Evaluations tab to review their evaluation progress and details.
### **2. Access and review your submitted evaluation**
* In the candidate’s interview details side panel, Click on **View Evaluation** to access the candidate's feedback and assessment results.
* Here, evaluators can review the rating decision **(Select/Turned Down/Hold)**, detailed comments, and any supporting notes submitted during the evaluation process.
### **Additional Tip**
**Keep Evaluation History for Reference**: Regularly reviewing evaluation history allows evaluators to spot patterns, calibrate ratings with team members, and refine their assessment approach over time, ultimately contributing to better hiring outcomes and reduced bias.
# How to view Interview Insights after a completed interview
Source: https://docs.talview.com/hiring-teams/evaluator/evaluations/how-tos/how-to-view-interview-insights-after-a-completed-interview
After a Live interview is completed, Talview generates an Interview Insights summary that includes an AI-powered overview of the session, candidate strengths, areas of improvement, key discussion points, and recommended next steps. In this article, you will learn how to access Interview Insights for a candidate once their interview has been completed.
***
### Before You Begin
Make sure you have:
* Logged in to Workflow Tools with your evaluator credentials.
* A candidate whose interview has a **Completed** meeting status.
***
### Step-by-Step Guide
**1. Open the workflow**
From the left sidebar, navigate to **Workflows** and select the relevant workflow (e.g., Software Engineer Backend).
* You'll see the candidate pipeline with stage tabs across the top, such as **Screening**, **Technical Interview**, and **Technical Interview**.
**2. Navigate to the interview stage**
Click on the interview stage tab where the completed interview took place (e.g., **Technical Interview**).
* The candidate list will display with columns for **Name**, **Interview Time**, **Meeting Status**, **Attendees**, **Authentication**, **Candidate Status**, **Recording**, and **Organizer**.
**3. Locate the candidate**
Find the candidate whose Interview Insights you want to review. You can use the search bar at the top right to search by name.
* Confirm that the candidate's **Meeting Status** shows **Completed**.
**4. Click View in the Recording column**
In the candidate's row, click the **View** button under the **Recording** column.
* This opens the **Interview Summary** page, where you can review the full Interview Insights for that session.
**5. Review the Interview Insights**
The Interview Summary page is divided into two main areas:
* **Left panel** - Displays the interview recording with a play button, along with session details such as the Session ID, interview title, date and time, and the names of the Candidate, Interviewer, and Organizer.
* **Right panel** - Contains three tabs:
* **Overview** - Includes the candidate's name, a link to their resume, and the AI-generated Interview Insights broken down into collapsible sections such as Interview Summary, Strengths, Key Discussion Points, Areas of Improvement, Recommended Next Steps, and Candidate Performance.
* **Transcript** - Displays a full timestamped transcript of everything said during the interview, with timestamps shown as offsets from the start of the recording.
* **Verification** - Shows the candidate's face authentication status and compliance check details.
***
**Additional Tips**
* Interview Insights are only available after the interview's meeting status is marked as **Completed**.
* You can use the navigation arrows (**\<** and **>**) at the top of the Interview Summary page to move between candidates without going back to the list.
* The top bar also displays the candidate's current evaluation status (e.g., **Yet to evaluate**), so you can quickly see whether the candidate still needs to be assessed.
* To begin your evaluation directly from this page, click the **Evaluate** button in the top-right corner.
# How to view the Interview transcript in Interview Insights
Source: https://docs.talview.com/hiring-teams/evaluator/evaluations/how-tos/how-to-view-the-interview-transcript-in-interview-insights
After a live interview is completed, Talview generates a full timestamped transcript of the conversation that took place during the session. This allows evaluators and recruiters to read through exactly what was said without needing to watch the entire recording.
In this article, you will learn how to access and use the Transcript tab within Interview Insights.
***
### Before You Begin
Make sure you have:
* Logged in to Workflow Tools with your Evaluator credentials.
* Opened the **Interview Summary** page for a candidate with a completed interview.
* The transcript has been successfully generated for the session. If the transcript is still processing, the tab will appear but will be in progress stage.
***
### Step-by-Step Guide
**1. Open the Interview Summary page**
Navigate to the candidate's Interview Insights by clicking **View** in the **Recording** column on the workflow dashboard.
**2. Click on the Transcript tab**
In the right panel, you'll see the **Transcript** tab alongside the **Overview** and **Verification** tabs. Click on it.
* The Transcript tab only appears when a transcript has been successfully generated for the session. If you don't see it, the transcript may still be processing or was not generated for that session.
**3. Read through the timestamped transcript**
The Transcript tab displays a full text transcript of everything said during the interview, with timestamps shown as offsets from the start of the recording.
* Use the timestamps to quickly locate specific moments in the conversation. If you want to hear how something was said, you can cross-reference the timestamp with the interview recording in the left panel.
**4. Use the transcript alongside the Overview tab**
The transcript works best as a companion to the AI-generated insights on the **Overview** tab.
* If a point in the **Strengths**, **Areas of Improvement**, or **Key Discussion Points** sections needs more context, switch to the Transcript tab to find the exact exchange where that topic came up.
* This is especially useful when you want to verify the AI-generated summary against what was actually said.
***
**Additional Tips**
* The transcript is generated at the room level and does not include speaker labels, it captures what was said, but does not identify who said it. Use the interview recording for speaker identification when needed.
* Transcripts are always generated in English, regardless of the language spoken during the interview.
* If the Interview Insights sections on the Overview tab (such as the summary, strengths, or skill scores) are not appearing, it may be because the transcript has not finished processing. The AI-generated insights depend on the transcript being available first.
* You can switch freely between the **Overview**, **Transcript**, and **Verification** tabs without losing your place in any of them.
# What happens if you haven’t responded to an Interview invite?
Source: https://docs.talview.com/hiring-teams/evaluator/interviews/diagnostics/what-happens-if-you-havent-responded-to-an-interview-invite
Missing an interview invitation response can disrupt scheduling workflows and create coordination gaps in your hiring process. When interviewers and candidates don't acknowledge invites, it affects room availability, candidate communication, and overall interview coordination.
This article helps interviewers understand what happens when they haven't responded to interview invitations and how to resolve scheduling issues in Talview.
## 🔎Troubleshooting Common Issues
| **What might be wrong** | **How to fix it** |
| :------------------------------------------------------------ | :---------------------------------------------------------------------------------------------------------- |
| You missed the invitation notification in your email or inbox | Check your email spam/junk folder and your Talview notification inbox for pending invitations |
| The invitation expired before you could respond | Contact your recruiter or admin to request a new invitation link |
| You're unsure which interview slot to accept | Review your calendar availability and respond within the invitation timeframe to secure your preferred slot |
| Multiple invitations are causing confusion | Prioritize responses based on interview dates and confirm each invitation separately in the platform |
| You responded but the system didn't register it | Clear your browser cache, log back into Talview, and resubmit your response |
### **Additional Tips**
* Respond to interview invites within 24-48 hours to maintain professional scheduling etiquette.
* Sync your Talview interview calendar with your work calendar to avoid scheduling conflicts.
* If you're unavailable for all proposed slots, communicate alternative times immediately through the platform.
# Why am I unable to invite an interviewer whose domain is not whitelisted?
Source: https://docs.talview.com/hiring-teams/evaluator/interviews/diagnostics/why-am-i-unable-to-invite-an-interviewer-whose-domain-is-not-whitelisted
When inviting evaluators to a Live interview and you are notified with an an error message. \
This typically occurs when the invitee’s email domain isn’t approved in the organization’s tenant settings.
Follow this guide to identify the cause and fix the issue quickly.
***
### ✅ **Common Troubleshooting Steps**
| **What Might Be Wrong?** | **What You Can Do** |
| :------------------------------------------------------------------------------------------------------ | :------------------------------------------------------------------------------------- |
| The invitee’s email domain is not whitelisted for your tenant. | Identify the domain and request your admin to add it to your organization’s whitelist. |
| The tenant configuration allows invites only from specific domains. | Check with your tenant admin if the domain restrictions are intentional. |
| The corporate firewall or proxy blocks Talview service domains (e.g., `*.talview.com`, `*.proview.io`). | Ask your IT team to whitelist critical service domains to prevent connection errors. |
**Tip:** Before inviting external users, confirm whether your organization restricts invitations to specific email domains. This helps avoid repeated whitelisting errors.
***
### **Additional Troubleshooting Steps**
1. Identify the domain from the invitee’s email address.
* Example: for `user@example.com`, the domain is `example.com`.
2. Share the domain with your organization’s IT or Talview tenant admin team.
3. Once approved, the domain will be added to your tenant’s allow list for future invitations.
4. If the user was recently added to your organization, allow a few minutes for the system to sync before retrying the invite.
5. After confirmation, retry sending the invite from the interview screen.
* The user should now be invited successfully without errors.
# Why can’t I access the Evaluation Form Post-Interview?
Source: https://docs.talview.com/hiring-teams/evaluator/interviews/diagnostics/why-cant-i-access-the-evaluation-form-post-interview
After completing an interview, it’s important for interviewers to submit their evaluations promptly so recruiters can make informed decisions. If you’re unable to access the evaluation form after the interview, it may delay candidate feedback and affect the overall hiring process.
This article helps you identify possible reasons why the evaluation form is not accessible and how to resolve them.
***
## 🔎 Troubleshooting Common Issues
| **What might be wrong** | **How to fix it** |
| :----------------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Form not published or linked to the workflow** | Sometimes evaluation forms are created but not published or attached to the interview workflow. Ask the recruiter to verify the setup in Workflow Tools. |
| **Access restrictions due to role/permissions** | Ensure you’re logged in with the correct Talview account. If you’re a guest interviewer, confirm that you’ve been granted access rights. |
| **Session sync delays** | Occasionally, there can be a short delay before the evaluation form appears after the interview session ends. Refresh the recruiter/interviewer dashboard after a few minutes. |
| **Expired or invalid session link** | If you’re trying to access the form via an expired email or calendar link, request the recruiter to resend the correct evaluation link from the system. |
| **System or browser issues** | Clear cache/cookies, switch to a supported browser (Chrome/Edge), and retry. If the issue persists, check Talview’s system status page or escalate to support. |
### **Additional Tips**
* Always use the **Talview dashboard**
* Submit evaluations immediately after the interview while the form is active.
* Coordinate with recruiters beforehand to confirm the correct evaluation form is attached to the workflow.
* Keep a **backup channel** (Slack, email) to inform recruiters quickly if you face access issues.
# Why didn’t I receive the post-interview summary email?
Source: https://docs.talview.com/hiring-teams/evaluator/interviews/diagnostics/why-didnt-i-receive-the-post-interview-summary-email
After an interview, you may expect to receive a **post-interview summary email** containing session details, candidate information, and evaluation reminders. If you don’t receive this email, it can delay timely feedback and reduce visibility into the candidate’s next steps.
This article helps diagnose why the summary email may not have been received and what actions you can take to resolve it.
***
## 🔎 Troubleshooting Common Issues
| **What might be wrong** | **How to fix it** |
| :------------------------------------ | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Feature not enabled in workflow** | Post-interview summary emails are a configurable feature. Confirm with your recruiter or admin that this option has been enabled for your interview. |
| **Incorrect email mapping** | Ensure the email ID you used to join the interview matches the one configured in the system. Guest interviewers may need to be explicitly mapped in the workflow. |
| **Email caught in spam/junk filters** | Check your spam or promotions folder. If found, mark it as safe to receive future emails without disruption. |
| **Delayed email processing** | Sometimes emails are queued if multiple interviews end around the same time. Wait a few minutes and refresh your inbox. |
| **Notification channel settings** | If your organization has enabled alternate channels (like in-app notifications or dashboards), the summary may appear there instead of email. |
| **System issue** | If the problem persists, escalate to Talview Support with interview details so logs can be checked. |
### **Additional Tips**
* Confirm with recruiters whether **post-interview summary emails** are enabled for your workflow.
* Review your organization’s policy on **email vs in-app notifications** so you know where to expect updates.
* If you frequently don’t receive summaries, report the issue so the admin can review the **configuration**.
# Why is my RSVP status not updating after I respond?
Source: https://docs.talview.com/hiring-teams/evaluator/interviews/diagnostics/why-is-my-rsvp-status-not-updating-after-i-respond
When you receive an interview invite, your RSVP (Accept, Propose New Time, Tentative, or Decline) helps recruiters plan and manage schedules efficiently. If your RSVP response isn’t reflecting in the Talview dashboard, it can lead to confusion and extra coordination for the recruiter.
This article helps diagnose why your RSVP status may not be updating and how to resolve the same.
***
## 🔎 Troubleshooting Common Issues
| **What might be wrong** | **How to fix it** |
| :------------------------------------------------------ | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Response not captured due to external calendar sync** | If you replied directly from Outlook/Google calendar but the sync is delayed, wait a few minutes and refresh. Confirm that the recruiter has calendar integration enabled. |
| **Email response not mapped** | If you RSVP’d by email reply (e.g., typing “Yes”/ “No”), the system may not have parsed it. Always use the **RSVP buttons** in the invite email body or in the ICS file. |
| **Multiple accounts or aliases** | If you responded using a secondary email (alias or personal ID), the system may not match it to your interviewer profile. Ensure you reply with the **same work email** registered in Talview. |
| **System sync delay** | Occasionally, RSVP updates take a short time to appear in the recruiter dashboard. Refresh your calendar and confirm again after a few minutes. |
| **Invite link mismatch** | If the interview was rescheduled and you responded to the old invite, the status may not reflect. Double-check that you responded to the latest calendar invite. |
### **Additional Tips**
* Always respond using the **RSVP buttons** in the invite instead of plain-text replies.
* Ensure you use your **primary work email** tied to Talview, not a personal alias.
* Refresh your calendar if updates don’t appear immediately.
# Why is the evaluation form submitted but not visible to the recruiter?
Source: https://docs.talview.com/hiring-teams/evaluator/interviews/diagnostics/why-is-the-evaluation-form-submitted-but-not-visible-to-the-recruiter
When using **Talview’s Workflow Tools**, interviewers are required to submit evaluation forms after completing an interview. These evaluations are then made visible to recruiters under the candidate’s profile. Sometimes, however, recruiters may report that they are unable to see an evaluation, even though the interviewer has submitted it.
This article helps interviewers diagnose the issue and understand why their submitted evaluation might not be visible to recruiters.
## 🔎 Troubleshooting Common Issues
| **What might be wrong** | **How to fix it** |
| :----------------------------------------------------------------------------------------------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Form saved but not submitted**: The form stores responses locally; recruiters can only view forms once “Submit” is clicked. | Always ensure you click **Submit** at the end of the evaluation. Wait for the confirmation message that your form has been successfully submitted. |
| **Form submitted under the wrong workflow step**: If the evaluation was tied to an incorrect step, recruiters may not find it under the candidate’s profile. | Double-check the interview step before starting the evaluation. If submitted incorrectly, notify the recruiter so the feedback can be reassigned. |
| **Connectivity or browser issues**: Poor internet connection or unsupported browsers may prevent your form from being synced to the platform. | Use a stable connection and the latest version of Chrome or Edge. Refresh only after confirming connectivity. |
| **Role or permission mismatch**: In rare cases, if your permissions are restricted, your form may save but not display to recruiters. | Contact your admin to confirm your role has evaluation submission rights. |
| **System processing delay or outage**: Occasionally, evaluations take time to sync or may be delayed due to platform downtime. | Wait a few minutes and refresh. If the evaluation still doesn’t show, reach out to Talview support. |
### **Additional Tips**
* Save periodically during long evaluations but always remember to click **Submit** at the end.
* Capture a screenshot of the submission confirmation message in case of disputes.
* If recruiters still cannot see your evaluation, share the session details (candidate name, workflow, interview date) with Talview support.
# Why is the “Invite” option disabled during a Live Interview?
Source: https://docs.talview.com/hiring-teams/evaluator/interviews/diagnostics/why-is-the-invite-option-disabled-during-a-live-interview
If evaluators are unable to invite additional panel members during a Live Interview, it usually means the **“Invite”** option is disabled for their role, organization, or the session template.
This guide walks you through common causes and step-by-step solutions to restore this functionality.
***
## 🔎 Troubleshooting Common Issues
| What Might Be Wrong | What You Can Do |
| :-------------------------------------------------- | :--------------------------------------------------------------------------------------------------- |
| Organization-level restriction | Contact your admin to confirm that “Invite” is not globally disabled. |
| Feature not reflected after enabling | Log out and rejoin the session. Refresh the People tab to view updated permissions. |
| Browser cache or session issue | Clear your browser’s cache and cookies, then rejoin the Interview. |
| Joined with incorrect role (co-evaluator, not host) | Ensure that you have joined as a host or panel member. Co-evaluators may not see the Invite control. |
| Template not updated | Log out and rejoin the session after enabling. Refresh the **People** tab. |
> **Note :** Guest Evaluators require a **whitelisted domain** before they can be added via the **Invite** feature.
### Additional Tips
* Use a supported browser (latest version of **Chrome** or **Edge**) for real-time updates.
* Invites to in-house evaluators are sent directly, whereas guest evaluators require a whitelisted domain. Contact your admin if the domain isn’t whitelisted.
# Why isn't the "Join Interview" button visible?
Source: https://docs.talview.com/hiring-teams/evaluator/interviews/diagnostics/why-isnt-the-join-interview-button-visible
Not being able to see the **Join Interview** button when an interview is imminent can be stressful, especially when you're trying to get in on time. This is usually caused by a timing restriction, a page loading issue, or an interview status problem on Talview.
In this article, you will find the most common causes and fixes to get the **Join Interview** button visible so you can join the session without delay.
***
### 🔎 Troubleshooting Common Issues
| **What Might Be Wrong** | **How to Fix It** |
| :---------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| The interview hasn't reached the 10-minute window yet | The **Join Interview** button only becomes active when the interview is scheduled to start within the next **10 minutes**. If you're checking in earlier than that, the button won't be enabled. Check the scheduled start time and return closer to it. |
| The page hasn't loaded the latest data | Try refreshing your browser by pressing `Ctrl + R` (Windows) or `Command + R` (Mac) to reload the page and fetch the latest data. The button may appear after a refresh. |
| The interview status hasn't updated correctly | If the interview status isn't showing as **Scheduled**, the button may not appear. Check the interview status in the timeline view and reach out to the recruiter if it appears incorrect. |
| You're viewing the wrong interview step | Make sure you've navigated to the correct **Interview** step in the candidate detail view. If the workflow has multiple interview steps, the button will only appear under the step the interview is scheduled against. |
| Your browser cache is causing a display issue | Clear your browser cache by pressing `Ctrl + Shift + Delete` (Windows) or `Command + Shift + Delete` (Mac), reload the page, and check again. |
| The interview was cancelled or rescheduled | If the interview was cancelled or moved to a different time, the button won't appear. Check with the recruiter to confirm the current status of the interview. |
| You're not assigned to this candidate's evaluation | The **Join Interview** button is only available to evaluators assigned to that candidate. If you haven't been assigned, reach out to the recruiter to confirm your assignment. |
**Additional Tips**
* Keep the candidate detail view open and refresh the page a minute or two before the scheduled start time, the **Join Interview** button will appear automatically once you're within the 10-minute window.
* If you're still unable to see the button after the interview start time has passed, the session may have already begun without you. Reach out to the recruiter immediately so they can provide assistance.
* Make sure your camera and microphone permissions are enabled in your browser before joining, this will save you time once the button becomes active.
* If the issue persists after trying all the steps above, reach out to your admin or recruiter for further assistance.
* The Join Interview button will only be available for the online interview. Make sure to always double check the type of Interview.
# Why was I marked as a ‘No Show’ even though I joined the session?
Source: https://docs.talview.com/hiring-teams/evaluator/interviews/diagnostics/why-was-i-marked-as-a-no-show-even-though-i-joined-the-session
After completing an interview, you may sometimes see your attendance marked as **“No Show”** in the system, even though you joined the session. This can cause confusion for recruiters reviewing attendance and may delay the evaluation process.
This article helps diagnose why this happens and how to resolve it.
***
## 🔎 Troubleshooting Common Issues
| **What might be wrong** | **How to fix it** |
| :----------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Multiple devices or login mismatch** | If you attempted to join from multiple devices or with an email ID not mapped to the workflow, your presence may not have been recorded correctly. Always join with the account/email tied to the interview invite. |
| **Connectivity issues during session start** | If you briefly lost internet connection while joining, the system may not have logged your entry. Refresh your browser, rejoin promptly, and notify the recruiter that you were present. |
| **Session not refreshed in recruiter dashboard** | Sometimes the recruiter dashboard doesn’t sync immediately. Ask the recruiter to refresh their view or check the **Interview Room logs** to validate your join/leave times. |
| **Calendar invite mismatch** | If the interview was rescheduled but you joined using the old calendar invite, the system might have logged it as the wrong session. Always confirm the latest invite and link from your calendar or Talview portal. |
| **System or tracking delay** | On rare occasions, attendance sync may be delayed. Wait a few minutes and check again. If it persists, escalate to Talview Support with session details. |
### **Additional Tips**
* Always join interviews from the **official Talview link** in your calendar invite.
* Log in **5–10 minutes early** to account for connectivity or setup issues.
* Use the **same email ID/account** as the one registered in the recruiter’s workflow.
* Avoid switching devices during the session unless instructed by support.
* If you experience delays or glitches, immediately **notify the recruiter via email or Notification Inbox**.
# Interviewer FAQs - Live Interviews
Source: https://docs.talview.com/hiring-teams/evaluator/interviews/faqs/interviewer-faqs-live-interviews
### **Introduction**
Talview's Live Interviews are designed to help interviewers and hiring managers conduct efficient, engaging, and secure candidate assessments across geographies.
This FAQ is designed specifically for interviewers, panel members, and evaluators who facilitate and assess candidate live interviews.
***
### **1. Before You Begin**
**Q1. What are Live Interviews and how does it differ from traditional video conferencing?**
Live Interviews are a purpose-built interviewing experience that goes beyond standard video conferencing by integrating specialized assessment tools, real-time candidate verification, built-in evaluation forms, and AI-powered analytics. Unlike generic video tools (Zoom, Teams, Google Meet), Live interviews provides:
* Integrated coding environments (CodeJam) for technical assessments
* Digital whiteboarding for design and problem-solving discussions
* Real-time candidate verification and identity authentication
* Structured evaluation forms within the interview interface
* Interview Insights analytics to detect bias and measure interviewer effectiveness
**Q2. Do I need special setup or training before conducting my first Live Interview?**
Yes. Before your first interview, you should:
* Receive access credentials and login information from your organization's administrator
* Complete basic platform orientation (usually provided by your HR or recruiting team)
* [**Test your camera, microphone,**](https://video-diagnostics.talview.org/) and [**internet connection**](https://speed.talview.com/).
* Familiarize yourself with evaluation forms and question templates your organization uses
* Review your organization's interview guidelines and protocols.
**Q3. What candidate information is available to me before the interview?**
You can access these by logging into the Workflow Tools platform:
* **Resume/CV -** Full employment history and qualifications
* **Profile Details -** Information the candidate provided during application (education, experience, skills)
* **Job Description -** Current role requirements and responsibilities
**Q4. What is the "Interview Builder" and how do I use it during preparation?**
Interview Builder is an AI-powered tool which is available during the interview on the side panel, it provides:
* **Pre-built Question Templates -** Role-specific, bias-free questions relevant to the job
* **Customizable Question Sets -** Behavioral, situational, competency-based, and technical questions
* **Follow-up Suggestions -** AI recommendations for probing deeper into candidate responses
* **Question Consistency -** Ensures all candidates for the same role receive similar core questions
**Q5. What devices can I use to join?**
A Live Interview is compatible with:
* **Computers -** Desktop or laptop (Windows, macOS, or Linux)
* **Mobile Devices -** Smartphone or tablet (iOS or Android)
* **Browsers** - Google Chrome, Microsoft Edge, or Mozilla Firefox (latest versions recommended)
We recommend using a **desktop or laptop computer** for the best experience, as it provides better video quality, stable positioning, and full access to all collaboration tools. If you must use a mobile device, ensure it has a strong internet connection and sufficient battery charge for the full interview duration.
**Q6. What technical requirements do I need to meet?**
To ensure a smooth interview experience, your device should meet these minimum specifications:
| Requirement | Minimum | Recommended |
| :------------------ | :----------------------------------- | :------------------------------------ |
| **RAM** | 4GB | 8GB |
| **Processor** | Dual core at 2 GHz or faster | Quad-core at 2.5 GHz or faster |
| **Graphics Memory** | 512MB internal / 1GB external | 1GB internal / 1.5GB external |
| **Webcam** | 15 fps minimum, 320x240 aspect ratio | Higher resolution with 30 fps |
| **Microphone** | Built-in or external | External quality microphone preferred |
| **Sound Card** | Required | Dedicated sound card preferred |
| **Internet Speed** | 1 Mbps upload / 1 Mbps download | 2 Mbps upload / 2 Mbps download |
> **NOTE:** If your device doesn't meet these specifications, you may experience lag, video freezing, or audio dropouts. Contact your recruiter if you have concerns about your device's compatibility
***
### **2. Interview Experience**
**Q1. What should I do 10 minutes before the scheduled interview?**
Final preparation steps:
* **Join the Pre-Join Lobby** - Click the interview link **10 mins before** the interview
* **Test Your Video** - Ensure your camera is on and your face is clearly visible
* **Test Your Audio** - Verify your microphone is working and speakers are at appropriate volume
* **Check Your Background** - Confirm your environment is professional and tidy
* **Review Candidate Info** - Info can be checked in the email or in the platform
* **Mute Distractions** - Silence phone notifications, close non-essential tabs and apps
**Q2. How do I know when the candidate has joined the interview room?**
When a candidate joins:
* Their video feed will appear on your screen
* You may see a notification saying "Candidate \[Name] has joined"
* If you're using a participant list, their name will appear
* The chat or meeting status may update to show increased participant count
**Q3. How do I use the Interview Builder or question templates during the live interview?**
During the interview:
* Your question templates and **Ask AI** option are accessible on your screen (usually in a sidebar or from the interview menu)
* Use **Ask AI** to manually generate additional questions during the interview based on the **job description and role requirements**
* Reference the suggested questions while maintaining eye contact and a natural conversation flow
* Don’t read questions verbatim; use them as a guide and ask them naturally
* Follow up on interesting responses with deeper or probing questions
* Review follow-up suggestions from Interview Builder or Ask AI, but adapt them to the candidate’s actual response
* Take notes on the candidate’s answers for evaluation later
The templates and AI-generated questions are meant to **support your judgment**, not make the interview feel scripted.
**Q4. What do real-time device monitoring alerts mean and how should I respond?**
You may receive notifications during the interview:
| Alert | Meaning | Action |
| :---------------------------------- | :------------------------------------------------------------------------------------------- | :------------------------------------------------------------------------------------------ |
| **Tab Switch Detected** | Candidate switched to a different browser tab | Note the alert; if it happens repeatedly, remind the candidate to stay on the interview tab |
| **Window Focus Lost (>30s)** | Candidate moved to a new window and remained out of focus for more than 30 seconds (Windows) | Note the behavior; politely check if they’re facing a technical issue |
| **Camera Switched** | Candidate switched to a different camera | Note it; ask if there’s a technical issue if concerned |
| **Multiple Cameras Detected** | Multiple camera sources are connected | Ask professionally if they intended to connect multiple devices |
| **Audio Device Switched** | Candidate switched microphone or speaker | Confirm audio quality remains clear; note for integrity |
| **Multiple Audio Devices Detected** | Multiple audio input devices are connected | May indicate someone else is listening; note and possibly inquire |
| **Face Not Detected** | Face is not visible in the camera feed | The system **captures an image only**; no notification is sent to the interviewer |
| **Multi-Face Detected** | More than one face appears in the video feed | The system **captures an image only**; no notification is sent to the interviewer |
| **Poor Network Detected** | Candidate’s internet connection is weak | Offer to continue, but be aware of possible lag or disruptions |
**Q5. What if I notice multiple faces or people in the candidate's video?**
If multi-face detection triggers:
* Stay calm and professional; there are often legitimate reasons
* Ask: "I notice there may be someone else in the room with you. Can you confirm you're in a private space?"
* The candidate may have a roommate, family member, or pet; ask them to move to a private area
* If they're intentionally bringing someone unauthorized to the interview, this is a significant integrity concern
* Document what you observed and notify your recruiting team or compliance officer immediately
* You can continue the interview once they've moved to a private space, but escalate the concern
**Q6. What happens when I click on Live Interview link?**
When you click the Live Interview link, you are taken to a **pre-join or onboarding screen** where you can:
* Allow access to your camera and microphone
* Check your audio and video setup
* Review interview details or instructions
Once ready, click **Join** to enter the live interview room and start the session with the candidate.
**Q7. Will I see how’s in the Interview?**
Yes. As an interviewer, you can see **all participants** in the interview room, including candidates and co-interviewers. This visibility helps you manage the session, confirm attendance, and coordinate with other interviewers.
**Q8. Can I share my screen my screen?**
Yes. You can share your screen at any time using the **“Share”** option. When prompted, choose to share:
* A specific application window
* A browser tab
* Your entire screen
> **NOTE:** Close any personal, confidential, or unrelated content before sharing your screen.
**Q9. What is “CodeJam” in the interview room?**
**CodeJam** is a collaborative coding environment that allows you to assess a candidate’s coding skills in real time.
**How it works:**
1. You share a coding problem or prompt with the candidate
2. The candidate writes code in the shared editor while you observe
3. You can ask the candidate to explain their thought process as they code
4. Code can be executed and tested instantly, with results visible to both sides
5. You can provide feedback or ask follow-up questions based on their approach
**Q10. What is the “Whiteboard” in the interview room?**
The **Whiteboard** is a digital collaboration tool used to visually explain ideas.
**How it works:**
1. A shared whiteboard opens for both interviewer and candidate
2. Either participant can draw, write, or erase content
3. Use it to explain concepts, create diagrams, flowcharts, or solve problems
4. All changes are visible in real time
5. Content can be modified or cleared as needed during discussion
**Q11. Can I chat with the candidate during the session?**
Yes. The **chat panel** allows you to send text messages to participants. This is useful for:
* Sharing links or instructions
* Clarifying questions
* Handling minor audio or connectivity issues
Use chat professionally and keep communication interview-focused.
**Q12. Can I change between light and dark themes?**
Yes. You can switch between **light and dark themes** based on your preference. The theme toggle changes only your interface view and does not affect other participants.
**Q13. Can I see my own video during the interview?**
Yes. You will see a preview of your own video feed along with the candidate’s video. This helps you ensure proper framing, lighting, and camera positioning throughout the interview.
**Q14. What happens if the candidate joins late or doesn’t join?**
If the candidate does not join at the scheduled time, wait for at least **10 minutes**. Delays can occur due to technical or scheduling issues. If the candidate does not appear after that, follow your organization’s interview or escalation process.
**Q15. Will I receive notifications about interview timing?**
Yes. Interviewers may receive **internal time-based notifications** to help manage the interview duration and ensure all planned topics are covered within the allotted time.
**Q16. Can I provide feedback after the interview?**
Yes. After the session ends, you will be prompted to submit **interview feedback and evaluation**. This feedback is critical for hiring decisions and maintaining a consistent interview process.
**Q17. How should I handle candidate mistakes or misunderstandings?**
Treat the session like an in-person interview:
* Encourage candidates to ask for clarification
* Allow them to correct misunderstandings
* Focus on problem-solving ability, communication, and approach rather than perfection
Virtual interviews can be stressful, and thoughtful guidance helps candidates perform at their best while giving you a clearer assessment of their capabilities.
**Q18. What is a Secondary Camera and when is it used in a Live Interview?**
A **Secondary Camera** is an additional device—usually the candidate’s **mobile phone**—used to provide an alternate camera angle during the interview. It is primarily enabled for **proctoring and interview integrity** purposes.
As an interviewer:
* The primary interview continues through the candidate’s main device (laptop/desktop)
* The secondary camera provides an additional visual view of the candidate’s surroundings
* This feature is enabled only if configured by your organization for the interview
The secondary camera helps ensure a fair and secure interview environment without interrupting the candidate’s experience.
**Q19. Will I see the secondary camera feed during the interview?**
Yes, if secondary camera is enabled for the interview:
* You may see an **additional video tile** or indicator representing the secondary camera
* The view typically shows the candidate’s environment rather than a close-up of their face
* The feed is meant for **monitoring and verification**, not for active interaction
You are not required to continuously watch the secondary camera unless something appears unusual.
**Q20. What should I do if the candidate has trouble connecting the secondary camera?**
If the candidate faces difficulty connecting their secondary device:
* Ask them calmly if they are seeing any on-screen instructions or error messages
* Allow a few minutes for setup, especially if this is their first time using a secondary camera
* If the issue persists, continue the interview and **note the failure** in your evaluation or feedback
* Escalate to your recruiting or compliance team after the interview if secondary camera usage was mandatory
Do not penalize the candidate immediately unless your organization’s policy explicitly requires it.
**Q21. What is a 360° Environment Check?**
A **360° Environment Check** is a guided process where the candidate is asked to briefly show their surroundings using their camera. This helps verify that:
* The candidate is alone in the room
* No unauthorized materials or people are present
* The interview environment meets integrity requirements
This check is typically conducted **at the start of the interview** or when prompted by the platform.
**Q22. What is my role during a 360° Environment Check?**
As an interviewer, your role is to:
* Politely instruct the candidate to rotate their camera or device as guided by the platform
* Observe the environment for any immediate concerns (additional people, screens, notes)
* Maintain a neutral and professional tone throughout the process
The check should take **less than a minute** and should not feel interrogative.
**Q23. What should I do if I notice something concerning during the 360° check?**
If you observe a potential issue:
* Ask a **neutral clarification question**, such as:
> “I noticed something in the background—could you confirm you’re in a private space?”
* Give the candidate a chance to explain or correct the situation
* If the concern remains valid, document it and inform your recruiting or compliance team after the interview
* Continue the interview unless policy requires immediate termination
Avoid making accusations or assumptions during the session.
**Q24. Will the 360° environment check or secondary camera interrupt the interview flow?**
No. Both features are designed to be:
* **Quick and minimally intrusive**
* Conducted at predefined moments (usually before or early in the interview)
* Supportive of interview integrity without disrupting candidate engagement
Your primary focus should remain on evaluating the candidate’s skills, communication, and role fit.
***
### **3. Device Permissions**
**Q1. What device and media permissions do I need to grant to use Live Interviews?**
To participate in interviews, you will need to grant permissions for:
* **Camera** – To be visible during video interviews
* **Microphone** – To communicate with candidates
* **Audio Output (Speakers)** – To hear the candidate
* **Screen Share** (if enabled) – To share your screen when presenting materials
Your browser will prompt you to allow these on first use. Test these permissions well before your interview.
**Q2. How do I grant camera and microphone permissions in my browser?**
When requested for permission:
* **Chrome/Edge/Firefox** – A popup will appear saying "Allow \[site] to use your camera/microphone?" Click "Allow"
* If you declined previously, go to the `browser's address bar →` click the `lock icon → Site settings → Camera/Microphone → Set to "Allow" → Refresh the page`
Do this at least once before your interview to avoid permissions issues during a live session.
**Q2. What is screen sharing and how do I enable it?**
Screen sharing allows you to show your computer screen (or a specific application) to the candidate. To use it:
* In the interview room, click the "Share" button
* Your browser will ask which screen/window to share; select your choice:
* Entire desktop (shows everything)
* Specific window (e.g., a Word document or job description)
* Specific tab (browser tab only)
* The candidate will then see exactly what you're displaying
* Stop sharing when done
**Q3. Is it necessary to use an external camera and microphone, or can I use my laptop's built-in devices?**
Your laptop's built-in camera and microphone are sufficient for most interviews. However, for a more professional appearance and better audio quality, consider:
* An external USB webcam with higher resolution (candidates appreciate clear video of you)
* A quality headset with a noise-canceling microphone (reduces background noise and echo)
* This investment improves the candidate experience and ensures better technical reliability
**Q4. What should I do if my camera or microphone is not working?**
Troubleshoot by:
* Checking that no other video application (Zoom, Teams, Skype) is currently using the camera
* Restarting your browser
* Checking your system's privacy settings to ensure the browser has camera/microphone access
* Verifying that your device's physical camera/microphone is not blocked or muted
* Testing the devices in another application (like a video call tool) to isolate the issue
* Restarting your computer if the issue persists
If issues continue, contact IT support before conducting a candidate interview.
***
### **4. Troubleshooting & Support**
**Q1. What should I do if I cannot access my account or login?**
If you cannot log in:
* Verify your username/email and password are correct (reset password if needed via login page)
* Clear your browser cache and cookies, then try again
* Check that you're using a supported browser (Chrome, Edge, or Firefox)
* Verify if your account has not been deactivated by your administrator
**Q2. What if I cannot access the Live Interview at the scheduled time?**
If you cannot join:
* Try a different supported browser (Chrome, Edge, Firefox)
* Verify you have a stable internet connection
* Confirm the interview link is correct and the interview time has been reached
* Clear your browser cache and restart the browser
* You can also join through a mobile device
If still unable to join, contact your recruiting team immediately so they can arrange an alternative interviewer or reschedule with the candidate.
**Q3. What if a candidate does not receive the interview invitation link?**
If a candidate says they didn't receive the email:
* **Check Email Spam/Junk -** Ask them to check spam folders first
* **Verify Email Address** - Confirm their email address is correct in your system
* Use **Notification Inbox** to forward the email
**Q4. How do I handle a situation where the candidate and I are both present but cannot see or hear each other?**
If there is no audio/video connection:
* Ask the candidate to check the pre-join lobby settings (camera/microphone enabled)
* Confirm that the candidate has granted camera and microphone permissions in their browser
* Ask the candidate to confirm no other apps are using their camera/microphone
* Have the candidate refresh the browser and rejoin
* If still failing, suggest they try a different browser as a temporary measure
* Use chat to communicate while troubleshooting
If the issue affects only you, restart your browser and rejoin. If it affects multiple users, contact support.
**Q5. How long should I wait for a candidate if they're late to the interview?**
If a candidate is late:
* Wait for 10 minutes, call the candidate from the platform if needed
* If you need to leave, send a message to your recruiting team
* Do not make assumptions about why they're late (technical issues, wrong time zone, etc.)
* Your recruiting team will follow up with the candidate to understand the delay and reschedule if appropriate
**Q6. What can I do if my video is freezing or lagging?**
Video freezing is often due to network speed or congestion. Try:
* Closing all non-essential tabs and background apps
* Moving closer to your Wi‑Fi router or switching to a wired connection
**Q7. How can I make sure my device is ready before the actual interview?**
To prepare your device:
* Restart your computer or mobile device before the interview time
* Close non-essential applications
* Run the [Speed test](https://speed.talview.com/) \*\*and \*\*[**Video diagnostics test**](https://video-diagnostics.talview.org/)
* Check your internet speed and stability
* Join the interview link 10 minutes early to complete all checks
**Q8. I received an error saying my browser or OS is not supported. What now?**
If you see a compatibility error:
* Switch to a supported browser (Chrome, Edge, or Firefox)
* Update your browser to the latest version
* Use a device with a supported operating system (Windows 10+, macOS 12.7.2+, supported Linux)
If you cannot access a supported device, inform your recruiter as early as possible.
***
# Interviewer FAQs - Pre and post interview
Source: https://docs.talview.com/hiring-teams/evaluator/interviews/faqs/interviewer-faqs-pre-and-post-interview
## Introduction
This FAQ helps **interviewers** understand how to manage their pre- and post-interview responsibilities within **Talview Workflow Tools**.
It covers how to RSVP and prepare for interviews, handle live scenarios such as delays or no-shows, and complete post-interview evaluations efficiently.
The article also outlines who can view your evaluations, submission timelines, and how to address any concerns after the session.
***
## 1. Pre-Interview: RSVP, Scheduling, and Attendance
**Q1. How do I RSVP to an interview?**
When you’re added as an interviewer, you’ll receive a **calendar invite** and an **email notification** with interview details.
You can RSVP using any of the following methods:
* Click **Accept / Decline / Tentative** in the calendar invite or the attached `.ics` file.
* Choose your RSVP option directly from the **email body**.
* Update your response from the **Interview Details** page within Talview Workflow Tools.
Your response automatically updates the recruiter’s dashboard and helps ensure proper scheduling.
**Q2. Can I change my RSVP after responding?**
Yes. You can change your RSVP **anytime before the interview ends** by:
* Reopening the calendar invite and selecting a new response.
* Choosing another option from the email body.
* Updating your response in the **Interview Details** page within the platform.
Your recruiter will automatically be notified of your updated response.
**Q3. What happens if I don’t RSVP at all?**
If no RSVP is recorded before the scheduled time, your status remains **“Invited.”**
* The system or recruiters may send you reminders.
* If the interview remains unconfirmed close to the scheduled time, the system may **flag it as unconfirmed** and allow recruiters to assign a backup interviewer.
**Q4. What should I do if I can’t join at the scheduled time?**
If you realize you can’t attend:
1. Update your RSVP to **Decline** or **Propose a New Time** immediately.
2. Choose an **alternate interviewer** in the decline flow (from the email body if available).
3. Notify the recruiter via **email or chat** to help them reassign quickly.
This ensures minimal disruption and maintains a smooth candidate experience.
**Q5. How do I know if my attendance was recorded?**
Attendance is automatically tracked once you **join the interview session** using the link in your calendar invite or via the **Interview Details** page.
After the interview:
* The dashboard marks you as **“Attended”** if your join time was logged.
* If you didn’t join, the system will show **“No-Show.”**
**Q6. Can I test my audio/video setup before the interview starts?**
Yes. Before joining, you’ll see a **system check screen** that allows you to:
* Test your **camera**, **microphone**, and **speakers**.
* Verify your **network connectivity** and **permissions**.
If any issue appears, follow the troubleshooting prompts or contact your **IT team** or **Talview Support** before joining the session.
**Q7. Where can I access the candidate’s profile and resume before the interview?**
You can review the candidate’s profile directly in **Workflow Tools** by clicking on the **Resume** icon in the invitation email.
You can also view it from the platform once you login.
***
## 2. Post-Interview: Evaluation & Feedback
**Q8. When will I receive the evaluation form?**
You’ll receive the **evaluation form** immediately after the interview ends.
* A notification email and an in-platform alert will prompt you to complete the evaluation.
* You can also access it anytime later via **Candidate → Evaluations Tab** in Workflow Tools.
**Q9. What’s the deadline for submitting my evaluation?**
The evaluation should ideally be submitted **within 24 hours** of the interview, or within the time defined by your organization’s policy.
Delayed submissions may impact candidate progression.
If you’re unable to complete it on time, inform the **recruiter** so they can plan accordingly.
**Q10. Can I edit my evaluation after submission?**
Editing options depend on your organization’s settings.
If you need to modify your feedback:
* Navigate to the **evaluation form** and click **Edit Evaluation** (if available).
* Alternatively, request the recruiter to **reopen your evaluation** for updates.
**Q11. Who can see my evaluation comments and recommendations?**
Your evaluation and comments are visible only to authorized roles, typically:
* Recruiters
* Hiring Managers
* Master Recruiters
Candidates **never see** your evaluation feedback or internal notes.
**Q12. What does the post-interview summary email contain?**
After the interview, you’ll receive a **summary email** containing:
* Candidate name and interview details (date, time, mode)
* Attendance confirmation
* Evaluation submission link
This email serves as a reminder to complete your evaluation promptly and provides easy access to the candidate record.
**Q13. Who should I contact if I have concerns about a candidate after the interview?** ✅ *\[New]*
If you have specific concerns or observations about a candidate that weren’t included in your evaluation form:
* Reach out directly to the **recruiter** or **hiring manager** via email or chat.
* You can also add a **private note** in the evaluation form (if your organization allows it).
These insights help recruiters and hiring teams make informed decisions.
# Interviewer FAQs - VoIP call feature
Source: https://docs.talview.com/hiring-teams/evaluator/interviews/faqs/interviewer-faqs-vo-ip-call-feature
Talview's live interview room includes a built-in VoIP (Voice over Internet Protocol) calling feature that allows interviewers to call candidates on their phone number directly from the platform without needing an external phone or app. Below are answers to the most commonly asked questions about how the feature works, when to use it, and what to do if something goes wrong.
***
**Q: What is the VoIP call feature?**
The VoIP call feature is a built-in calling tool within the live interview room. It lets interviewers place voice calls to candidates on their phone number directly through the platform using an internet connection, without needing a separate phone, dialer, or third-party app.
***
**Q: When should I use the VoIP call feature?**
The feature is primarily used when a candidate hasn't joined the interview at the scheduled time. You can place a quick call to remind them, confirm their availability, or check if they're experiencing technical issues. It can also be used a few minutes before a scheduled interview to confirm readiness and reduce no-shows.
***
**Q: How do I initiate a VoIP call?**
From the live interview interface, select the **Call** option. A confirmation dialog will appear, click **Yes, Call** to proceed. The system will then attempt to connect with the candidate using secure VoIP technology. Note that a VoIP call can only be initiated if the candidate's phone number has been added to the system.
***
**Q: Do I need to install anything to use VoIP calling?**
No. The VoIP feature is built into the live interview room and works directly in your browser. There's no additional software, plugin, or app to install.
***
**Q: Will the candidate see my phone number when I call them?**
No. Both the interviewer's and the candidate's contact details remain confidential. The call is routed through the platform, so neither party's personal phone number is exposed.
***
**Q: Are VoIP calls recorded?**
Yes. VoIP calls made through the platform can be recorded, and transcripts may be available for review. This supports better documentation, evaluation, and collaboration across the hiring team.
***
**Q: What happens if the candidate doesn't answer the call?**
The system will wait for the candidate to pick up. If they don't answer, you can try again after a short interval or reach out through other coordination methods, such as the in-session chat feature.
***
**Q: What are the network requirements for clear VoIP calls?**
A stable internet connection is required for clear audio. Make sure you're not on a VPN or proxy during the interview, and that your network meets the platform's recommended bandwidth requirements. For detailed specifications, refer to *Understanding Network Requirements for Clear VoIP Calls*.
***
**Q: Why is my VoIP call not connecting or showing "Call is in progress"?**
This can happen due to network instability or a temporary system issue. Try the following:
* Check your internet connection and make sure it's stable.
* Ensure no VPN or proxy is running.
* Refresh the interview room and try placing the call again.
* If the issue persists, contact support at [**support@talview.com**](mailto:support@talview.com).
***
**Q: Can I use VoIP calling on a mobile device?**
The VoIP feature is designed for use on a desktop or laptop browser. If you're joining the interview on a mobile device, the availability of VoIP calling may vary depending on your device and browser.
***
**Q: Can other participants in the interview room see that I placed a VoIP call?**
The call activity is logged within the platform for transparency and documentation purposes. Other participants in the session may be able to see that a call was placed.
# How am I notified when a candidate switches their audio device
Source: https://docs.talview.com/hiring-teams/evaluator/interviews/how-tos/how-am-i-notified-when-a-candidate-switches-their-audio-device
During a Live Interview, maintaining clear and consistent communication is essential. If a **candidate switches their audio input device** during the Live inetrview, the platform automatically notifies the evaluator.
This article explains how evaluators are notified when a candidate switches their audio device and what actions to take.
***
## **How is the Evaluator notified?**
When a candidate changes their audio input device during a Live Interview session on Talview, the system displays an **on-screen pop-up alert**.
The notification:
* Appears prominently during the Live Interview session.
* Clearly indicates that the **candidate has switched their audio device**.
* May display details such as:
* The **previous audio device**
* The **newly selected audio device**
* Includes an acknowledgment button such as **“Ok, got it”** to proceed.
This ensures that the evaluators are immediately informed of any changes to the candidate’s audio configuration.
> **Note**: The notification is informational and designed to maintain transparency and interview integrity. It does not automatically pause or terminate the session.
### **Best Practices**
* Ensure the new audio device provides **clear and stable sound quality**.
* If your organization has strict compliance requirements, verify that the change aligns with interview guidelines.
* Continue the interview once audio quality is confirmed.
# How am I notified when a candidate switches their camera device
Source: https://docs.talview.com/hiring-teams/evaluator/interviews/how-tos/how-am-i-notified-when-a-candidate-switches-their-camera-device
During a Live Interviews, interviewers are notified in real time if a candidate switches their camera device mid-session. This notification ensures transparency and helps maintain interview integrity.
This article explains how evaluators are notified when a candidate switches their camera device and what actions to take.
***
## **How is the Evaluator notified?**
When a candidate changes their camera input device during a Live Interview session, the system displays an **on-screen pop-up alert**.
The notification:
* Appears prominently during the Live Interview session.
* Clearly indicates that the **candidate has switched their camera device**.
* May display details such as:
* The **previous camera device**
* The **newly selected camera device**
* Includes an acknowledgment button such as **“Ok, got it”** to proceed.
This ensures that the evaluators are immediately informed of any changes to the candidate’s video configuration.
> **Note**: The notification is informational and designed to maintain transparency and interview integrity. It does not automatically pause or terminate the session.
**Best Practices**
* Encourage candidates to finalize their setup before the interview begins.
* Avoid frequent interruptions unless the switch impacts video clarity or integrity.
# How am I notified when a Virtual camera is detected from a candidate
Source: https://docs.talview.com/hiring-teams/evaluator/interviews/how-tos/how-am-i-notified-when-a-virtual-camera-is-detected-from-a-candidate
During a **Live Interview**, maintaining the authenticity of the candidate’s video feed is essential. If a **virtual camera** (such as OBS Virtual Camera, Snap Camera, ManyCam, etc.) is detected on the candidate’s device, the platform immediately notifies within the interview interface.
***
## How is the Evaluator Notified?
When a virtual camera is detected:
* A **pop-up alert** appears at the center of the interview screen.
* The alert clearly states: **“Virtual camera detected on candidate’s device.”**
* The specific camera name is displayed (for example: *ManyCam Virtual Webcam (Windows Virtual Camera)*).
* You must acknowledge the alert by clicking **“Ok, got it”** to continue.
This notification is shown in real time during the Live Interview session.
***
## What Does This Mean?
A virtual camera is a software-based camera feed that can:
* Modify or overlay video content
* Display pre-recorded or manipulated video
* Mask the candidate’s actual camera feed
Detection does not automatically stop the interview, but it indicates that the candidate is not using a physical hardware camera.
***
## Recommended Actions for an Evaluator
1. Inform the candidate that a virtual camera has been detected.
2. Request the candidate to switch to a physical camera (built-in or external webcam).
3. Confirm that the live video feed reflects the candidate in real time.
4. If the issue persists, follow your organization’s interview integrity or escalation guidelines.
***
### Important Notes
* The alert is informational and designed to support interview integrity.
* The session will not automatically end due to this detection.
* The Evaluator retains full discretion to proceed or escalate as per internal policy.
If you continue to see the alert even after the candidate switches devices, ask them to refresh the session and ensure all virtual camera software is completely disabled.
# How am I notified when multiple audio devices are detected from candidates
Source: https://docs.talview.com/hiring-teams/evaluator/interviews/how-tos/how-am-i-notified-when-multiple-audio-devices-are-detected-from-candidates
During a Live Interview, the system automatically checks the candidate’s connected audio devices. If more than one microphone is detected, the platform displays a **real-time alert notification** within the interview interface.
This article explains how evaluators are notified when **multiple audio input devices** are detected on a candidate’s system, what the notification means, and what action (if any) is required.
***
## How is the Evaluator notified?
When multiple microphones are detected on the candidate’s device:
* A **pop-up alert** appears inside the Live Interview screen.
* The alert states:
**“Multiple microphone detected on candidate's device.”**
* It displays:
* The **current microphone** in use
* Other connected microphone devices
The alert is informational and allows the evaluator to stay aware of the candidate’s audio configuration.
> **Note**: The Live Interview continues uninterrupted. The notification does **not** automatically pause or terminate the session. It is a **monitoring alert**, not a blocking error.
### Best Practices
To maintain a secure and fair interview environment:
* Review the microphone list when the alert appears.
* Ensure only necessary audio devices are active.
* Follow your organization’s standard interview integrity policy.
# How am I notified when multiple faces are detected during a Live interview
Source: https://docs.talview.com/hiring-teams/evaluator/interviews/how-tos/how-am-i-notified-when-multiple-faces-are-detected-during-a-live-interview
During a Live Interview, the platform continuously performs real-time face detection. If more than one face is detected in the candidate’s camera frame, the system flags the event and surfaces a notification to the evaluator immediately.
This ensures interview integrity and helps you take appropriate action in real time. In this article, you will learn how you are notified when multiple faces are detected and what steps you should take in response.
***
## How the Notification Appears
### Real-Time Flag in the Verification Panel
* Navigate to the **Profile** section during a Live interview.
* Open the **Verification** tab.
* Under the active **Session**, you will see:
* A red status indicator.
* A label such as **Face Authentication – Failed** (if verification fails due to multiple faces).
* A timestamp of when the the event is occured
This is visible in the right-side panel during the session.
***
## What Should You Do If Multiple Faces Are Detected
As an Evaluator, you may:
* Politely ask the candidate to adjust their camera.
* Request that no one else remain in the room.
* Pause the interview if needed.
* Escalate to your internal compliance or hiring operations team.
* Mark the session for review.
Your organization’s proctoring policy should define the required action.
### Important Notes
* Detection is automated and runs continuously during the session.
* Not every detection results in session failure (severity depends on system rules and policy configuration).
* All flagged instances are logged for audit purposes.
***
# How am I notified when the candidate’s face is not detected during a Live interview
Source: https://docs.talview.com/hiring-teams/evaluator/interviews/how-tos/how-am-i-notified-when-the-candidates-face-is-not-detected-during-a-live-interview
During a **Live Interview**, the system continuously validates the candidate’s face visibility as part of the authentication process.
If the candidate’s face is not detected, the system updates the verification status in real time within the interview interface.
***
## Video Guide
### 1. Open the Candidate’s Profile
* During the Live Interview, click **Profile** (top-right corner of the screen).
* The candidate details panel will open on the right side of the interface.
* This panel contains **Details**, **Verification**, and **Environment Check** tabs.
### 2. Click on the Verification Tab
* Under Profile, select the **Verification** tab.
* This section displays authentication attempts recorded during the session.
* If the candidate’s face was not detected: The verification status will show a red **“Failed”** label in the top-right corner of the panel.
> This indicates authentication failure due to face detection issues.
### 3. Review the Failed Verification Entry
Within the **Verification** tab:
* You will see a timeline of captured images with timestamps.
* The specific entry corresponding to the failed attempt will be marked **Failed**.
* A thumbnail image is displayed for review
* You can click on the thumbnail to:
* View the captured frame.
* Understand why the detection failed (e.g., candidate moved out of frame, face not visible, obstruction, lightning issues).
***
## Recommended Action for Interviewers
If you see a **Failed** verification status:
1. Inform the candidate that their face is not clearly visible.
2. Ask them to adjust their seating position or camera angle.
3. Ensure proper lighting and full face visibility.
4. Proceed once visibility is restored.
If repeated failures occur, follow your organization’s escalation guidelines.
***
### What Does “Failed” Mean?
A **Failed** status in the Verification tab typically means:
* The candidate moved out of the camera frame
* The face was partially visible
* Lighting prevented proper detection
* The camera view was obstructed
The system logs the failed authentication attempt automatically.
# How can Evaluators use the Whiteboard during a Live Interviews
Source: https://docs.talview.com/hiring-teams/evaluator/interviews/how-tos/how-can-evaluators-use-the-whiteboard-during-a-live-interviews
Talview Interview Rooms provide evaluators with a collaborative environment that includes a **Whiteboard feature**. Using the Whiteboard allows evaluators to present problems visually, guide candidates through tasks, and encourage collaborative problem-solving in real time.
This article explains how evaluators can seamlessly access and switch to the Whiteboard during an ongoing Talview interview session.
***
## Prerequisites
Before switching to the Whiteboard, ensure the following:
* You have an **active Talview interview session**.
* You are logged in as an **evaluator** with access to interview room features.
* You have a **stable internet connection** for smooth real-time collaboration.
***
## **Steps to switch to the Whiteboard**
### **1. Join the Interview Room**
* Log into your Talview dashboard.
* Access the ongoing interview session where you want to use the Whiteboard.
### **2. Locate the Whiteboard Icon**
* In the interview room toolbar (usually at the bottom left of the screen), look for the Whiteboard icon.
* The icon may appear as a *pen*, *marker*, or *whiteboard* symbol.
### **3. Switch to Whiteboard Mode**
* Click the **Whiteboard** icon.
* The view will switch from video/presentation mode to the interactive Whiteboard.
### **4. Use the Whiteboard Tools**
* Write, draw, highlight, or erase using tools such as pens, markers, shapes, and colors.
* You can clear or reset the board if needed.
### **5. Return to Interview Mode**
* To exit Whiteboard mode, click **Exit Whiteboard** or select **Video/Screen Share** from the toolbar to return to the standard interview view.
**Notes**
* The Whiteboard is **collaborative**; any updates appear in real time for all participants.
* Evaluators control whether candidates can edit or only view the Whiteboard.
* A strong internet connection is recommended for a seamless experience.
**Best Practice**
Use the Whiteboard to test problem-solving, explain scenarios, or encourage candidates to demonstrate their thought process visually.
# How can Interviewers use CodeJam during a Live Interview
Source: https://docs.talview.com/hiring-teams/evaluator/interviews/how-tos/how-can-interviewers-use-code-jam-during-a-live-interview
**CodeJam** is an integrated coding environment within Talview Interview Rooms. It enables collaborative, live coding assessments during technical interviews. This guide explains how interviewers can access and use CodeJam during an ongoing interview session.
***
## Prerequisites
* An active Talview interview session with a scheduled interview.
* Interviewer role with access to Interview Room features.
* A stable internet connection for smooth real-time interaction.
***
## Steps to Switch to CodeJam
### **1. Join the Interview Room**
* Log in to Talview and open the scheduled interview session.
### **2. Locate the CodeJam Icon**
* Find the CodeJam icon on the interview toolbar (usually at the bottom-left).
* The icon resembles a code bracket (``) or terminal symbol.
### **3. Open CodeJam**
* Click the **CodeJam** button to launch the coding environment.
* The video feed will automatically resize or minimize to display the coding panel.
### **4. Set Up the Coding Problem**
* Upload or open pre-prepared coding problems, or start with a blank workspace.
* Share problem instructions verbally or via chat.
### **5. Collaborate with the Candidate**
* CodeJam allows real-time collaboration.
* Both interviewer and candidate can edit the code simultaneously.
### **6. Use Coding Tools**
Features includes:
* Multiple language options
* Syntax highlighting
* Auto-completion
### **7. Exit CodeJam**
* To return to the main video/audio interview mode, click **Exit CodeJam** or the close button on the toolbar.
### Supported Browsers and Devices
* **Browsers:** Latest versions of Chrome, Firefox, and Microsoft Edge.
* **Devices:** Desktop or laptop recommended. (Mobile devices have limited functionality.)
***
### Tips for Interviewers
* Prepare coding problems in advance for smoother transitions.
* Clearly explain the expectations and problem requirements.
* Use Code Jam’s built-in tools to monitor progress and support candidates.
* Switch back to video mode once the coding assessment is complete
# How do Evaluators join a Live Interview
Source: https://docs.talview.com/hiring-teams/evaluator/interviews/how-tos/how-do-evaluators-join-a-live-interview
**Talview Interview Rooms** is a secure, proctored platform that provides evaluators with tools to assess candidates efficiently. This guide explains how to join an interview session, prepare your setup, and use evaluator features.
## Video Guide
### **Step 1: Receive and Confirm Interview Details**
* Verify the interview date, time, and time zone in your invitation
* Note the interview room link provided via email or Talview platform
* Confirm any specific evaluation criteria or focus areas
### **Step 2: Prepare Your Setup**
| Preparation | Best Practices |
| :---------------------------- | :---------------------------------------------------------------------------------- |
| Device | Desktop, laptop and mobile device. (Google Chrome or other supported browsers) |
| Internet | Stable connection (min. 2 Mbps upload/download) |
| Webcam, Microphone & Speakers | Test all devices; ensure clear audio and video |
| Workspace | Quiet, professional, and uninterrupted environment |
| Browser Tabs / Apps | Close unnecessary tabs and apps to free system resources |
| VPN / Proxy | Disable VPNs or proxy servers to avoid connectivity conflicts |
| Evaluator Tools | Familiarize yourself with candidate view, notes, flags, and chat features |
| Preparation | Best Practices |
### **Step 3: Join the Interview**
* Click the Interview Room link 10 minutes before start time
* Log in using your evaluator credentials
* Complete the audio/video test when prompted
### **Step 4 : Familiarize yourself with evaluator tools:**
* **Candidate View:** Monitor candidate's screen and behavior
* **Notes Panel:** Document observations and scores in real-time
* **Chat Feature:** Communicate with support or co-evaluators
***
## Checklist Before Joining
* Confirm date, time, and time zone.
* Test internet speed and connected devices.
* Close unnecessary apps and browser tabs.
* Disable VPNs/proxy servers to avoid connectivity conflicts.
* Check that workspace is quiet and professional.
# How do Evaluators join a Live Interview on a Mobile device
Source: https://docs.talview.com/hiring-teams/evaluator/interviews/how-tos/how-do-evaluators-join-a-live-interview-on-a-mobile-device
**Live Interview** allows evaluators to join, assess, and interact with candidates seamlessly, even on mobile devices.
This guide explains how to access an interview session, prepare your device, and use evaluator tools effectively on the mobile interface.
***
## Video Guide
### Step 1: Receive and Confirm Interview Details
* Check the interview date, time, and time zone in your invitation.
* Locate the Live interview link shared via email.
### Step 2: Prepare Your Mobile Device
| Preparation | Best Practices |
| :---------------------- | :-------------------------------------------------------------------------- |
| **Device** | Use a smartphone or tablet . |
| **Internet** | Ensure a stable internet or Wi-Fi connection (min. 2 Mbps upload/download). |
| **Camera & Microphone** | Grant camera and mic permissions when prompted by the app. |
| **Audio Devices** | Use wired or Bluetooth earphones for clearer audio. |
| **Notifications** | Turn off notifications or enable *Do Not Disturb* mode during the session. |
| **Battery** | Keep your device fully charged or connected to a power source. |
| **Background Apps** | Close unnecessary apps to optimize performance and bandwidth. |
### **Step 3: Join the Interview**
* Tap the Live Interview link directly from your invitation , you’ll be taken straight to the session without needing to log in separately.
* Tap **Join Interview** from the session page.
* Allow necessary permissions (camera, microphone, and screen, if prompted).
### **Step 4: Use Evaluator Tools on Mobile**
Once inside the Interview , you can access all essential evaluator tools with a simplified mobile layout:
* **Candidate View:** Observe the candidate’s video and screen activity.
* **Notes Panel:** Record feedback and observations directly within the app.
* **Chat Feature:** Use the built-in chat to communicate with support or co-evaluators.
* **Session Controls:** Mute/unmute audio or end the session from the bottom toolbar.
## **Evaluator Checklist Before Joining**
* Confirm the interview schedule (date, time, and time zone).
* Test internet speed and confirm camera/mic access.
* Complete a quick audio and video test before entering the room.
* Close background apps to prevent lag.
***
# How do interviewers call candidates using VoIP feature
Source: https://docs.talview.com/hiring-teams/evaluator/interviews/how-tos/how-do-interviewers-call-candidates-using-vo-ip-feature
The Interviewing Platform enables interviewers to connect with candidates instantly through its built-in **VoIP (Voice over Internet Protocol)** feature. This eliminates the need for external phones or apps, allowing direct communication within the platform.
This feature is primarily used when candidates join interviews late, allowing interviewers to quickly follow up and ensure participation. By enabling personal, trackable communication, VoIP helps streamline coordination and enhance the overall candidate experience.
***
## **Steps to Make a VoIP Call**
**1. Initiate the Call**
From the live interview interface, select the **Call** option. You can place the call directly within Platform, no external phone or app required.
**2. Confirm to Proceed**
When ready, click **“Yes, Call”** in the confirmation dialog box. The system will begin the call using secure VoIP technology.
**3. Connection Process**
The system waits for the candidate to answer and then establishes a secure audio connection through the Platform.
**4. During the Call**
Once connected, both parties can communicate freely. Personal numbers remain hidden, and the call is automatically recorded (if enabled).
**5. Ending the Call**
Click **End Call** when finished. Depending on your setup, call details such as time, duration, and status may be logged for internal review.
***
## **Benefits of VoIP Calling from platform**
* Integrated Workflow: No external applications or devices required.
* Time Efficiency: Quickly connect with candidates during or before scheduled interviews.
* Privacy Protection: Both candidate and recruiter contact details remain confidential.
* Improved Documentation: Recording and transcripts support better evaluation and review.
* Enhanced Collaboration: Call insights can be shared across hiring teams for unified decision-making.
### **Additional Tip**
Use the VoIP call feature a few minutes before each scheduled interview to remind candidates and confirm readiness. This simple step can reduce no-shows and improve the overall interview experience.
***
# How does the Pre-join Lobby work for interviewers on the web
Source: https://docs.talview.com/hiring-teams/evaluator/interviews/how-tos/how-does-the-pre-join-lobby-work-for-interviewers-on-the-web
The Pre-Join Lobby allows the interviewer to prepare and adjust all required settings before entering the session.
## Video Guide
1. Upon entering the Pre-Join Lobby, **allow access to your microphone and camera**.
Note: If your browser or system permissions for camera and microphone are not enabled, you will not be able to join the meeting.
Please follow the steps in [Allowing Hardware Permissions](https://www.notion.so/527fd096e82b4646826e2779d12421de?pvs=21) to grant necessary access.
2. Choose your preferred **video and audio devices** for the meeting.
3. Configure your **camera and microphone settings : yo**u can mute or unmute your mic and turn your camera on or off before joining the session.
4. You can also choose to blur your background or apply branded images(if needed) by clicking on the **“Effects "option.**
5. When you're ready for the interview, click on '**Join Interview'** to start the session.
6. You may remain in the Pre-Join Lobby or enter the meeting and wait there until the candidate joins.
7. The lobby displays the **number of participants** already in the meeting.
# How evaluators are notified when multiple cameras are detected from candidates
Source: https://docs.talview.com/hiring-teams/evaluator/interviews/how-tos/how-evaluators-are-notified-when-multiple-cameras-are-detected-from-candidates
During a Live Interview, the system automatically checks the candidate’s connected video devices. If more than one camera is detected, the platform displays a **real-time alert notification** within the interview interface.
This article explains how interviewers are notified when **multiple camera devices** are detected on a candidate’s system, what the notification means, and what action (if any) is required.
***
## How is the Evaluator notified?
When multiple cameras are detected on the candidate’s device:
* A **pop-up alert** appears inside the Live Interview screen.
* The alert states:
**“Multiple camera detected on candidate's device.”**
* It displays:
* The **current camera** in use
* Other connected camera devices
* An acknowledgment button (**Ok, got it**)
The alert is informational and allows the interviewer to stay aware of the candidate’s video device configuration.
> **Note**: The Live Interview continues uninterrupted. The notification does **not** automatically pause, block, or terminate the session. It is a **monitoring alert**, not a blocking error.
### Best Practices
To maintain a secure and fair interview environment:
* Review the listed camera devices when the alert appears.
* Confirm that the active camera clearly shows the candidate.
* Ask the candidate to disconnect unnecessary external cameras, if applicable.
* Follow your organization’s standard interview integrity policy if required.
# How to Access a Candidate’s Resume during a Live Interview
Source: https://docs.talview.com/hiring-teams/evaluator/interviews/how-tos/how-to-access-a-candidates-resume-during-a-live-interview
Evaluators in **Talview Interview Rooms** can instantly access a candidate’s resume during live interviews using the Workflow tool interface. This feature allows smooth, contextual, and efficient evaluation without leaving the session.
***
## Steps to View the Candidate Resume
1. Locate the **Resume** icon/tab at the top-right corner of the Interview Room interface.
2. Click the **Resume** icon/tab to open the candidate’s uploaded resume.
3. Use this view to review qualifications, experience, and tailor your interview questions in real-time.
### Benefits
* **Preparedness** – Have authenticated resume details at hand for informed discussions.
* **Efficiency** – No need to pause or switch screens while interviewing.
* **Contextual Insight** – Reference work history and skills for targeted questioning.
* **Smarter Questioning -** Frame contextual and role-based questions.
* **Enhanced Security -** Confirm candidate identity in real time.
### Best Practices
* Keep the **Resume panel** open when discussing work experience or relevant skills.
* Encourage consistent use of the feature across the panel for streamlined evaluations.
# How to Access Candidate Resumes from Interview emails
Source: https://docs.talview.com/hiring-teams/evaluator/interviews/how-tos/how-to-access-candidate-resumes-from-interview-emails
Interviewers often need quick access to candidate resumes before conducting interviews, whether the session is online or in-person.
With the **Resume Access via Interview Invite** capability, interviewers can now directly view candidate resumes from their **email invite** without needing to log in separately to Workflow Tools.
This feature ensures that authorized interviewers (both internal and external participants) can conveniently access resumes in a secure, permission-controlled manner across **desktop and mobile devices**.
## Steps to Go Through the Flow
### **1. Open the Interview Invite Email**
* As an **interviewer**, check your inbox for the **interview invite** email sent from Talview.
* The email contains details like **interview date**, **time**, **mode (online/in-person)**, and **candidate information**.
### **2. Locate the “Resume” Link**
* Within the email body, beside the candidate's name locate the resume link and click the **“Resume”** link.
* This link appears for both **online** and **in-person** interviews - provided the candidate has uploaded a resume.
### **3. Accessing the Resume**
* When you click **Resume**, a new browser tab will open displaying the candidate’s resume.
* If you are an **assigned participant** in the interview:
* The resume will load in a secure **Talview Resume Viewer**.
* You can **zoom in/out** for better readability or **download** the file for offline reference.
* If you are **not a participant** in the interview:
* You’ll see an **error message** stating that you don’t have permission to view the resume.
### **4. Viewing the Resume on Mobile**
* Resume access works seamlessly on **mobile browsers** as well.
* Tap the **Resume** link in your invite email to open the document in a new tab.
* The same zoom and download controls are available on mobile for a consistent viewing experience.
### **5. Resume Viewer Options**
* Once the resume opens in the viewer, you can:
* **Zoom In/Out** – Use the toolbar or pinch gestures (on mobile) to adjust readability.
* **Download** – Click the download icon to save a copy for offline use.
### **Note:**
* Only **assigned interview participants** can access the candidate resume through this link.
* Users who are not part of the scheduled interview will see an authorization message upon clicking the resume.
* Resume access links work from both **mobile and web browsers**.
* This ensures secure sharing of candidate information while maintaining data privacy and compliance.
# How to Access Candidate’s Ivy responses
Source: https://docs.talview.com/hiring-teams/evaluator/interviews/how-tos/how-to-access-candidates-ivy-responses
## Introduction
Evaluators play a key role in reviewing candidate performance across different assessment types.
With the Ivy response viewer, evaluators can easily access candidate recordings and AI-generated summaries directly from the **Evaluations** menu in **Workflow Tools**.
This feature allows evaluators to review responses captured during the **Ivy AI Interview** - including overall score and skill level score, **recording** and the **summary** - ensuring a seamless and structured evaluation process.
***
## Steps to Go Through the Flow
### **Navigate to the Evaluation Tab**
* Log in to **Workflow Tools** as an evaluator and go to the **Evaluations** tab from the left navigation panel.
* The page displays all candidates assigned to you for evaluation.
### **Select the Candidate to Evaluate**
* Click on the **candidate’s name** under your assigned evaluation list.
* This opens the **Candidate Detail View**, showing assessment summaries and completed stages.
1. **Locate the Ivy Assessment Card**
* Scroll through the candidate’s assessment section until you find the **Ivy Assessment Card**.
* The card shows assessment details such as:
* Assessment name
* Status (Completed / In Progress)
* Score and skill-level score
2. **View Ivy Responses**
* On the Ivy Assessment Card, click **“View responses.”**
* A **side panel** will open on the right-hand side displaying:
* **Candidate Recording** – The video/audio response captured by Ivy.
* **AI Summary** - Key highlights, communication insights, and interaction summary generated by Ivy.
3. **Playback and Review Options**
* Use the playback controls in the side panel to:
* **Play/Pause** the recording.
* **Seek** specific timestamps.
* **Adjust playback speed** (if supported).
* Review the **AI-generated summary** for insights on tone, confidence, and relevance of responses.
4. **Complete the Evaluation**
* After reviewing the Ivy responses and summary, proceed to fill out your **evaluation form** under the same candidate detail view by clicking on “Evaluate”.
* Save or submit your evaluation once completed.
**Important Notes:**
* Only **assigned evaluators** can access Ivy responses for their candidates.
* The recording, score and summary are available only after the candidate has completed the Ivy interview.
# How to Access the Job Description during a Live Interview
Source: https://docs.talview.com/hiring-teams/evaluator/interviews/how-tos/how-to-access-the-job-description-during-a-live-interview
Evaluators can seamlessly access the Job Description (JD) during a live interview in **Talview Interview Rooms** using the Workflow tool interface. This ensures smarter, contextual, and role-aligned assessments without leaving the session window.
***
## Steps to View the Job Description
1. Locate the top-right menu panel in the Interview Room interface.
2. Click the **Job Description** icon/tab to open the job description for the specific position.
3. Use the Job Description view to reference responsibilities, required skills, and qualifications while engaging with the candidate.
### Benefits
* **Role Alignment** – Keep role requirements visible for more accurate evaluation and focused questioning.
* **Efficiency** – No need to minimize or exit the interview screen, reducing disruption and saving time.
* **Smarter Questioning -** Frame contextual and role-based questions.
* **Enhanced Security -** Confirm candidate identity in real time.
### Best Practices
* Keep the **JD panel open** when discussing role responsibilities or skill alignment.
* Encourage all panel members to reference the JD consistently for structured, role-focused evaluation.
# How to Access Verification View during an Live Interview
Source: https://docs.talview.com/hiring-teams/evaluator/interviews/how-tos/how-to-access-verification-view-during-an-live-interview
**Talview Interview Rooms** provide real-time candidate verification to ensure secure and fraud-free interviews. Evaluators can access verification details such as live face capture, and impersonation alerts directly within the interview interface without interrupting the session flow.
***
## How to Access Verification View Mid-Interview
1. In the **Talview Interview Room interface**, locate the top-right menu panel where candidate documents and profile options appear.
2. Click on the **Verification** or **Profile** tab/icon to open the verification view.
3. Monitor **live face capture data** and **system alerts** for suspicious behavior or impersonation attempts.
4. Use this information during or after the interview to confirm candidate identity and ensure compliance.
### Benefits
* **Fraud Prevention** – Detect impersonation with AI-driven face/voice authentication.
* **Efficiency** – View verification data without leaving the interview screen.
* **Compliance** – Supports secure and compliant hiring practices.
* **Smarter Questioning -** Frame contextual and role-based questions.
* **Enhanced Security -** Confirm candidate identity in real time.
### Best Practices
* Regularly check **verification alerts** during high-stakes or secure hiring scenarios.
* Use verification results in conjunction with **evaluation notes** for a complete assessment.
# How to change Light and Dark themes during a Live Interview
Source: https://docs.talview.com/hiring-teams/evaluator/interviews/how-tos/how-to-change-light-and-dark-themes-during-a-live-interview
Talview enables interviewers to switch between **Light**, **Dark**, and **System Default** themes at any point during a Live Interview, allowing better visual comfort and adaptability throughout the session.
***
## **Steps to Change the Theme**
Theme settings are available within the live interview interface and can be updated instantly.
1. While in the live interview, open the **More** menu at the bottom of the screen.
2. Click **Device Settings**.
3. Locate the **Theme** section.
4. Select one of the available options:
* **Light** – Optimized for bright working environments
* **Dark** – Minimizes glare and supports low-light setups
* **System Default** – Syncs with your operating system’s theme
*(This may appear similar to Light mode in some cases.)*
5. The interface updates immediately once a theme is selected.
### **Why Switching Themes Is Useful?**
* Improves readability during extended interview sessions
* Reduces visual fatigue for interviewers conducting multiple interviews
* Supports accessibility and personal comfort preferences
* Does not affect the candidate’s view or interrupt the interview flo
# How to chat with the Live interview participants
Source: https://docs.talview.com/hiring-teams/evaluator/interviews/how-tos/how-to-chat-with-the-live-interview-participants
The **Chat** feature allows interviewers to send and receive text messages with candidates and other interviewers during a Live Interview, enabling quick coordination, clarifications, and non-verbal communication without interrupting the interview.
## How to Chat with Participants
### Step 1: Open the Chat Panel
* Click the **Chat** icon in the interview control panel
* The chat panel opens on the right side of the screen
### Step 2: Send a Message
* Type your message in the text field
* Click the **arrow** to send the message
> **Note**:
>
> * Chat messages are visible only to selected participants
> * Chat supports file uploads
> * You can switch the chat view between Everyone and Interviewers
### **Using Chat Tools During Live Interviews**
* Use the **📎 attachment icon** to share files (case studies, instructions, documents).
* Use the **\ code icon** to insert formatted code snippets during technical interviews.
* Use the **🔗 link icon** to add clickable URLs for reference materials.
* Always verify files and links before sending them to the candidate.
# How to control recording settings in a Live Interview
Source: https://docs.talview.com/hiring-teams/evaluator/interviews/how-tos/how-to-control-recording-settings-in-a-live-interview
This article explains how interviewers can view and manage recording status during a Live Interview. Recording always requires candidate consent, and the interviewer can request consent whenever needed.
***
## Prerequisites
* You must be logged in as an **interviewer**.
* You should be inside the **Live Interview Room**.
* Ensure your camera and mic are allowed in the browser if you plan to record both sides.
***
## Video Guide
### **Recording Indicator**
The top of the Live Interview Room displays the current recording status:
* Red indicator + “This interview is being recorded.”→ Recording is active.
* White indicator + “This interview is not being recorded.”→ Recording is disabled due to candidate preference or compliance rules.
Interviewers can also see whether the candidate has consented or declined recording.
***
## Steps to Request Candidate Consent
If recording is disabled:
1. Click **“Request consent.”**
2. A prompt appears for the candidate.
3. Recording resumes only if the candidate clicks **“I consent.”**
You cannot force or override recording without candidate approval.
***
## Steps to Resume Recording
Once the candidate provides consent:
1. The indicator changes to **red**.
2. The message updates to: **“This interview is being recorded.”**
3. You may continue with the interview as usual.
If the candidate opts out again, the system stops recording immediately.
### Additional Notes
* Always verify that the candidate has given explicit consent before recording.
* Recording features may vary based on compliance requirements in different regions.
* The candidate has full control and can stop recording at any time.
# How to Exit the Live Interviews
Source: https://docs.talview.com/hiring-teams/evaluator/interviews/how-tos/how-to-exit-the-live-interviews
This article explains how interviewers can properly **exit a live interview session** on the platform. Following these correct exit process ensures the live interview session is closed smoothly and allows you to complete any required **post-interview feedback or evaluations**.
***
## **When Should You Exit the Interview?**
You should exit the live interview when:
* The interview has concluded and no further discussion is required.
* The candidate does not join the session or the interview is discontinued.
* You need to leave due to technical issues or unforeseen circumstances.
* The session needs to be ended after sufficient waiting time.
***
## **Steps to Exit the Interview**
### **1. Locate the “Leave” Button**
During the live interview, the **Leave** button is typically:
* Displayed as a **red phone or disconnect icon**
* Located at the **bottom center** of the interview screen
### **2. Click the “Leave” Button**
* Click the red **Leave** button once.
* You will be exited from the live interview session immediately.
### **3. Submit Interview Feedback**
* After exiting, you are automatically redirected to the **Feedback or Evaluation page**.
* Complete and submit the required feedback for the candidate.
* Feedback submission is an important step in closing the interview process.
### **Best Practices**
* Ensure all interview questions and assessments are completed before exiting.
* Always use the **Leave** button instead of closing the browser tab to avoid session issues.
* Submit the feedback form before closing the tab or window.
* If the candidate does not join, wait for the recommended duration before exiting the session.
# How to Instantly Invite Domain-Whitelisted Evaluators
Source: https://docs.talview.com/hiring-teams/evaluator/interviews/how-tos/how-to-instantly-invite-domain-whitelisted-evaluators
The Live Interview allows evaluators to add registered evaluators to an ongoing interview instantly. This feature enhances collaboration, ensures flexibility, and enables smooth coordination during a Live interview.
***
## **Steps to Invite Registered Users**
### **1. Access the People Tab**
During a live session, click the **People** Tab located at the bottom-right corner of the Interview Room. This opens the participant list where you can view and manage participants.
### **2. View and Manage Attendees**
In the **People** tab, you can see:
* Participants who are currently **In meeting & Invited**
### **3. Send Invites to Evaluators**
* Select the **Invite** button at the top of the panel.
* A search field will appear, allowing you to find evaluators who are already registered or assigned to the current interview workflow.
### **4. Find and Invite Registered Evaluators**
* Start typing the evaluator’s name in the search box.
* The system will auto-suggest matching user profiles.
* Click **Invite** next to the correct evaluator’s name to send a real-time invitation.
### **5. Monitor Invite Status**
Once an invitation is sent:
* The evaluator’s status appears as **Invited**
* After joining, their name moves to the **In meeting** section
This allows you to track attendance and ensure all evaluators are present for collaboration.
### **Best Practices**
* Only evaluators registered by the organization will appear in the invite search.
* The real-time invite feature ensures smooth coordination and minimizes session interruptions.
* Use the **People** panel to monitor participant roles and invitation status for transparency and control.
***
# How to manually add or edit questions in Interview Builder
Source: https://docs.talview.com/hiring-teams/evaluator/interviews/how-tos/how-to-manually-add-or-edit-questions-in-interview-builder
The Interview Builder in Talview enables you to create, customize, and manage questions for candidate evaluation.
This guide walks you through adding AI-suggested or custom questions, editing existing questions, and organizing them efficiently to streamline your interview workflow.
***
### **Steps to Add or Edit Questions**
1. View AI Questions: Go to the Guide tab to see AI-generated questions based on the Job Description for reference.
2. Add Custom Questions: **Add** your own questions in the text field to address specific skills, experience, or behavioral traits relevant to the role.
3. Access More Options: Click the More Options icon to access additional actions, such as deleting texts or changing the font color.
4. Clear Text Field: Use the **Delete** option to clear all content from the field if you want to start fresh.
5. Add Notes or Questions: Type new questions or notes directly into the Text field.
6. Format Text: Adjust **font style, size, and alignment** to make your questions organized and easy to read.
Use these steps to quickly add AI-suggested or custom questions, edit existing ones, and organize them to maintain a consistent and professional interview process.
## Best Practices
* Review AI-generated questions before adding your own to avoid duplication.
* Use formatting to differentiate mandatory vs optional questions or highlight key evaluation points.
# How to Provide Feedback and Ratings after Live Interviews
Source: https://docs.talview.com/hiring-teams/evaluator/interviews/how-tos/how-to-provide-feedback-and-ratings-after-live-interviews
Talview enables interviewers to share **feedback and ratings** after live interviews, helping organizations understand usability, performance, and overall experience from the evaluator’s perspective.
***
## **How to Submit Feedback?**
1. End the live interview session.
2. You will be prompted to **Evaluate** the session. (Select Later or Evalute accordingly)
3. Review the **feedback prompt** that appears post-interview.
4. Rate the relevant experience parameters.
5. Add optional comments based on your session experience.
6. Submit the feedback.
All feedback is stored securely and consolidated into reports accessible to recruiters and administrators.
***
### **Why Interviewer Feedback is important?**
* Identifies recurring technical or workflow issues
* Improves interviewer efficiency and experience
* Provides actionable insights for platform optimization
* Supports data-driven enhancements to the interview process
**Best Practice**
Complete the feedback form right after each interview to ensure accurate and detailed input.
# How to request candidates to turn on their video during a Live interview
Source: https://docs.talview.com/hiring-teams/evaluator/interviews/how-tos/how-to-request-candidates-to-turn-on-their-video-during-a-live-interview
During a Live Interview, Interviewers can request candidates to **Turn On** their video if it is currently disabled, ensuring better engagement and visibility throughout the interview session.
## How to Request a Candidate to Turn On Their Video
### Step 1: Identify the Candidate with Video Off
* In the live interview screen, locate the candidate tile showing initials instead of video
* A **Request Video** button appears on the candidate tile
### Step 2: Send a Video Request
* Click **Request Video** on the candidate’s tile
* After the request is sent, the candidate tile displays **Video Requested**
> **Note**: This indicates that the request is active and awaiting candidate action
### Step 3: Candidate Receives Notification
* Once submitted, the candidate immediately receives an in-interview notification prompting them to enable their camera
* The candidate can choose to turn on their video from their end
***
## What Happens If the Candidate Denies the Request
If the candidate chooses not to enable their video:
* The interviewer cannot force-enable the camera
* The session continues without candidate video
* The **Video Requested** status may clear depending on system behavior
* The interviewer may choose to:
* Verbally follow up for clarification
* Continue the interview without video
* Escalate based on organizational interview policy
> **Note**: Camera activation is always controlled by the candidate for privacy and consent reasons.
### Important Notes
* Only a request notification is sent; final control remains with the candidate
* Repeated requests may not trigger multiple immediate notifications
* Video availability depends on device, browser, and permission settings
# How to RSVP to an Interview Invite (Yes, no, tentative)
Source: https://docs.talview.com/hiring-teams/evaluator/interviews/how-tos/how-to-rsvp-to-an-interview-invite-yes-no-tentative
When you receive an interview invitation via email, responding promptly helps maintain clear communication with candidates and keeps your interview schedule organized. Verifying your availability and confirming your attendance through email allows the recruitment team to plan effectively and communicate any necessary details before the interview.
In this article, you'll learn how to check your interview invite details and respond with your availability status, whether you can attend, need to decline, or are tentatively available.
## Step-by-Step Guide
### Locate the Interview Invite Email
Check your inbox for the interview invite email sent by the recruitment team. The email typically includes:
* Interview date and time
* Candidate mail id
* Job position
* RSVP options
* Location or meeting link
### A. RSVP from the email message
* Open the interview invitation email in your inbox and scroll down to review interview details.
* Click on **“here"** which is a *confirmation link* to **accept your interview invitation**.
* If you need to **reschedule**, there are three options you can choose:
* Click **Propose new time -** Select **new date and time** to choose a different interview slot.
* Click **Add availability -** Here, **add interview slot** that you want to repeat weekly, **add override dates** and **mark holidays** to set your interview availability.
* Click **Decline -** Here, mention the **reason to cancel your scheduled interview** and suggest an alternate interviewer (optional).
### B. RSVP from the ICS file
* Click on **RSVP** in the ICS file column to:
* ✔️Accept
* ✖️Decline
* 👁️🗨️Let the organizer/recruiter know that you won’t attend but want to receive information about the meeting.
* ❓**Tentative** to indicate your interest in the meeting while keeping your schedule flexible.
* 🕒Propose a new time
* ↖️RSVP with note to organizer/recruiter
* ↖️ Reply to organizer/recruiter
* ↖️ Reply to all attendees
* ↗️Forward meeting
### **Additional Tips**
* Respond to interview invites within 24 hours to maintain professional communication.
* Add the interview to your office calendar immediately after confirming attendance.
* If you selected "Tentative," update your response to "Yes" or "No" as soon as you confirm your availability.
* Test your technology (camera, microphone, internet connection) before virtual interviews if you've confirmed attendance.
***
# How to Set your Interview Availability and Manage Holidays
Source: https://docs.talview.com/hiring-teams/evaluator/interviews/how-tos/how-to-set-your-interview-availability-and-manage-holidays
Setting up your availability helps streamline the scheduling of future interviews. You can specify the days and time slots you are available, making it easier to coordinate with candidates.
This article provides a step-by-step process to configure your weekly availability using **Talview's Workflow Tools.**
## Step to Setup Availability
### **Step 1: Navigate to the Availability Section**
* On the Talview dashboard, locate the sidebar or main navigation menu.
* Click on **Availability** to facilitate easy scheduling of future interviews.
* The page redirects to Workflow tools - panel calendar.
### **Step 2: Select Your Time Zone**
* Locate the time zone dropdown near the top-left of the availability panel.
* Ensure the correct time zone is selected (e.g., **Indian Standard Time**) to align your availability with your local time.
### **Step 3: Add Availability Time Slots**
* For each day you want to set availability:
* Click the **+ (plus)** icon under the respective day.
* A new time slot block appears where you can input the start and end times.
* To remove a time slot, click the **trash bin icon** next to the corresponding time slot.
* To replicate the same time slot to other days, click the **copy icon** next to the day name, this saves time when you have recurring availability patterns.
* Once all desired time slots have been added and checked, your availability is automatically updated.
### **Step 4: Set Override Dates and Mark holidays (For Exceptions)**
* Scroll to the **Override dates** section below the weekly schedule.
* This section lets you add exceptions to your recurring availability — such as time off, public holidays, or changes in plans.
* To add an *override:*
* Click **Add an override**.
* Select the **date(s)** where your availability differs from usual, add a **time slot** and then click on **save changes**
* To *mark holidays*:
* Click **Mark holidays** and select applicable dates where you won’t be available.
### **Step 5: Choose the Viewing Mode**
* Toggle between **List view** and **Calendar view** as per your ease of use.
* **List view** shows a simple tabular layout of days and time slots.
* **Calendar view** (optional) displays availability in a calendar format.
**Important Note**
* Ensure your time zone setting is accurate to avoid scheduling conflicts.
* Overrides take priority over regular weekly availability for specified dates.
* Keep your availability updated to reflect any changes promptly.
# How to use Interview Guide in an interviews
Source: https://docs.talview.com/hiring-teams/evaluator/interviews/how-tos/how-to-use-interview-guide-in-an-interviews
Interview Builder enables evaluators to create structured and consistent interview scripts using a combination of AI-generated questions and a curated question library. The tool helps reduce bias, standardize assessments, and deliver a uniform candidate experience. Evaluators can add their own prompts, customize or rearrange questions, collaborate with panel members, and even use the tool as a scratchpad during preparation.
## **Steps to Use Interview Builder**
**1. Start Creating the Interview Script**
Begin by opening guide for the the role or position you are evaluating. You can either start from a blank script or questions generated based on job description on common competencies for the role.
**2. Generate Questions Using AI**
If you need customized or role-specific questions, enter prompts such as skills, responsibilities, or focus areas. The AI will instantly generate suitable questions and follow-up prompts you can add to the script.
**3. Customize the Questions**
Edit, rearrange, or remove questions to tailor the script to your organizational needs. You can also manually type your own prompts if you want personalized phrasing or specific situational questions.
**4. Prepare for Cultural and Role Fit Evaluation**
Incorporate questions that measure behavioral traits, cultural alignment, and soft skills. You can refine these questions based on candidate resumes or job expectations.
**5. Collaborate with Interviewers**
Share the script with other evaluators to avoid overlapping questions. Assign areas of focus to each interviewer to ensure smooth and coordinated panel interviews.
**6. Use as a Scratchpad During Preparation**
You can use Interview Builder to jot down notes, draft follow-up questions, or refine your flow. The flexible interface supports iterative preparation.
**7. Ensure Consistency Across Candidates**
Finalize the script and use the same core set of questions for all candidates applying for the same role. This ensures fairness and reduces unconscious bias during evaluation.
### **Best Practices for Evaluators**
* Use both curated and AI-generated questions to balance structure with customization.
* Avoid redundant questioning in panel interviews by coordinating with other evaluators.
* Use AI follow-up suggestions to probe deeper when responses need clarity.
* Capture notes systematically to support fair and accurate scoring.
* Review your question order to ensure a logical, conversational, and time-efficient flow.
* Stay focused on objective assessment by prioritizing behavior- and competency-based questions.
# How to View a Candidate’s Ivy summary in detail
Source: https://docs.talview.com/hiring-teams/evaluator/interviews/how-tos/how-to-view-a-candidates-ivy-summary-in-detail
Evaluators can access the **Ivy AI Interview summary** for candidates directly from **Workflow Tools** once the candidate’s Ivy interview is completed.
This feature allows evaluators to review both the **recording** of the Ivy AI interaction and the **Key Discussion Areas** generated by the AI.
By providing this consolidated view, evaluators can make more informed and consistent evaluation decisions without needing to conduct a separate review session.
***
## Steps to Go Through the Flow
### **1. Log in to Workflow Tools as an Evaluator**
* Use your evaluator credentials to sign in to the **Workflow Tools** platform.
* You’ll be directed to your dashboard, which lists the candidates assigned for evaluation.
### **2. Select the Candidate**
* Locate and click on the **candidate name** whose Ivy interview you want to review.
* This will open the candidate’s evaluation details page, showing all associated assessments and interview steps.
### **3. Locate the Ivy Interview Card**
* In the candidate’s assessment view, identify the Ivy Interview card or tile.
* This represents the AI interview that the candidate has completed.
### **4. Click on “View responses”**
* On the Ivy Interview card, click the **“View responses”** button.
* This will open a **side panel** on the right-hand side of the screen.
### **5. Review the Ivy Interview Summary**
* The side panel displays:
* The **candidate’s Ivy interview recording**, allowing playback of the AI-led session.
* A summary section titled **“Key Discussion Areas”**, highlighting important topics, candidate responses, and themes identified by Ivy.
* Use this summary to understand the candidate’s communication, relevance, and content quality before submitting your evaluation.
### **Pre-requisites**
Before accessing the Ivy interview summary, ensure that:
* You are logged in with an **Evaluator** role assigned to the relevant workflow.
* The candidate’s **Ivy Interview** step is **completed** and processed successfully.
* The **Ivy Interview card** is visible under the candidate’s assessment list.
* Your browser allows **media playback** (for viewing recordings).
***
# How to View candidate details in Profile
Source: https://docs.talview.com/hiring-teams/evaluator/interviews/how-tos/how-to-view-candidate-details-in-profile
Interviewers can view a candidate’s complete profile, including personal details, verification images, and environment insights directly within the Live Interview Room.
In this article, you’ll learn how to access the candidate profile and review key details to validate identity before or during an interview session without interrupting the live session.
## Step-by-step Guide
* During a Live Interview, locate the **Profile** icon at the top-right corner of the screen.
* Click **Profile** to open the candidate’s full profile panel.
This section provides quick access to the candidate’s basic and verification details.
### **1. View details**
* Click **Details** to view the candidate’s **basic information**, such as name, email address, and candidate ID.
* These details help confirm the candidate’s identity during the session.
### **2. Verify candidate identity**
* Select the **Verification** tab to view face authentication data.
* Here, interviewers can **compare the live video feed or current image** with the **base image** captured from the first assessment attempt or one sourced from an upstream system
* This ensures the candidate appearing in the interview matches their registered identity.
### **3. Environment Check**
* Click on **Environment Check** tab to view candidate’s captured images of their test environment.
* This helps confirm that the candidate is in a fair and distraction-free environment, maintaining test integrity and compliance.
### **Additional Tips**
* Access the profile at any time during the session without interrupting the live feed.
* Cross-reference verification images with real-time video for optimal identity checks.
* If discrepancies appear in environment checks, note them in your evaluation feedback.
# How to View interview recordings and comments
Source: https://docs.talview.com/hiring-teams/evaluator/interviews/how-tos/how-to-view-interview-recordings-and-comments
Live Interviews are recorded with participant consent, ensuring transparency and data security. These recordings enable evaluators to revisit candidate responses at any time, supporting fair, collaborative, and well-informed hiring decisions. All recordings are securely stored with end-to-end encryption and access limited to authorized reviewers.
Follow these steps to view and review recorded interviews.
## Video Guide
### Step 1:Access Workflow Tools Platform
* Log in to the Workflow Tools platform.
* This section allows evaluators to review recordings alongside feedback forms and evaluation data.
### Step 2: Select the Candidate
* Once inside Workflow Tools, search for and select the **candidate’s name**.
* The candidate’s interview details, feedback forms, recording and related data will be visible.
### Step 3: View the Interview Recording
* Click the **play icon** beside the candidate’s interview record to start playback.
* The recording opens instantly for review and evaluation.
### Step 4: Review in Maximized View
* When playback starts, the view automatically opens in a **maximized layout** for better visibility.
* Use the **pause**, **replay**, and **seek** controls to navigate through the interview as needed.
### Key Benefits of Recording Interviews
Recordings allow hiring teams to revisit candidate responses , reducing the pressure of making real-time decisions during live sessions.
Talview ensures all recordings are protected with:
* End-to-end encryption for candidate and interviewer data.
* Strict access control, allowing only authorized evaluators to view recordings.
# How to view participant list in Interview Rooms
Source: https://docs.talview.com/hiring-teams/evaluator/interviews/how-tos/how-to-view-participant-list-in-interview-rooms
This article explains how interviewers can quickly view who is present in a Live Interview Room.
It covers how to open the **“People”** panel and identify all participants currently in the interview, including organizers/interviewers, candidates, and any additional invitees.
## GIF guide
### **1. Access the People panel**
* On the *Interview Room screen*, locate the **People** icon at the bottom-right corner.
* Click on **People** to open the participants panel on the right side of the screen.
### **2. View participants in the interview**
* After opening the **People** panel, check the **In meeting** section to see the names and the roles of everyone currently present in the interview (for example, organizer/interviewer and candidate).
* If others were invited but are not yet joined, they may appear under a separate section (such as “Other invited”) so you can confirm who is expected to join versus who is already in the room.
**Additional Tips:**
* If you cannot see the **People** option, refresh the interview page and ensure you are logged in with an organizer or interviewer account that has access to the room.
* When the participant list does not update automatically, close and reopen the **People** panel or ask participants to rejoin the interview so their status is refreshed.
# Understanding Network Requirements for Clear VoIP Calls
Source: https://docs.talview.com/hiring-teams/evaluator/interviews/how-tos/understanding-network-requirements-for-clear-vo-ip-calls
A stable internet connection is essential for clear and uninterrupted VoIP (Voice over Internet Protocol) calls in Talview. Evaluators can initiate calls to candidates directly from the interview landing page, ensuring prompt and seamless communication.
Meeting the recommended network requirements guarantees smooth, real-time audio performance during interviews and assessments.
***
## 📶 Minimum and Recommended Bandwidth
| **Type** | **Minimum Requirement** | **Recommended Requirement** |
| :----------------- | :---------------------- | :-------------------------- |
| **Upload Speed** | 2 Mbps | 5 Mbps |
| **Download Speed** | 2 Mbps | 5 Mbps |
For the best results in Talview interviews, ensure at least 5 Mbps bandwidth and minimal latency for clear audio and zero lag.
***
## 🌐 How to Check Your Network Speed
Before starting your interview or assessment, test your connection using Talview’s [speed test](https://speed.talview.com/) tool.
### Steps:
1. Click **Start Test** to begin.
2. Wait for the test to finish, it automatically measures **download**, **upload**, and **latency**.
3. Compare your results with the values in the **Recommended Network Metrics** table below.
Run the speed test on the same device and browser you’ll use for the interview.
***
## 📊 Recommended Network Metrics
| **Parameter** | **Recommended Value** | **What It Means** |
| :----------------- | :-------------------- | :--------------------------------------------------------------------- |
| **Ping (Latency)** | ≤ 50 ms | Measures response time; lower values mean less delay during calls. |
| **Jitter** | ≤ 30 ms | Indicates connection stability; lower jitter ensures consistent audio. |
| **Download Speed** | ≥ 5 Mbps | Ensures you can receive real-time audio and video smoothly. |
| **Upload Speed** | ≥ 5 Mbps | Ensures your audio is transmitted clearly to others. |
### Tips for Best Performance
* Use a wired Ethernet connection instead of Wi-Fi for better stability.
* Close unused applications or browser tabs that consume bandwidth.
* Test from the same device and location where you’ll attend the session.
* Keep a mobile hotspot backup ready in case of network fluctuations.
> A reliable network is key to maintaining clear, delay-free VoIP communication during interviews and assessments. By ensuring your internet meets these requirements, you can enjoy a professional, uninterrupted experience on the Talview platform.
***
# Understanding Post-Interview Summary Emails
Source: https://docs.talview.com/hiring-teams/evaluator/interviews/how-tos/understanding-post-interview-summary-emails
This article helps **Interviewers** understand the **Post-Interview Summary Email** they receive once an interview is concluded on Talview.
The email provides a quick summary of interview participation details and next steps, ensuring interviewers have complete visibility of attendance status, evaluations, and feedback actions after each interview session.
## Pre-Requisites
* You must be added as an **Interviewer** in the Talview interview workflow.
* The interview session must be **marked as completed** in the platform for the summary email to trigger.
* If evaluation permissions are role-restricted, ensure your recruiter or tenant admin has enabled evaluation access for you.
***
## Steps
1. **Receive the Post-Interview Email**
Once an interview concludes, the system automatically sends an email to all interviewers who were part of the online session.
The subject line will typically read:
> “Interview Summary – \[Role Title]”
2. **View Interview Details**
Inside the email, you will find a section titled **Interview Details**, which includes:
* **Interview Title and Schedule** – The job role (e.g., *Software Developer*) and interview time/date.
* **Candidate Participation** – Indicates whether the candidate **Attended** or was a **No-Show**.
* **Interviewer Participation** – Confirms your attendance status.
**Sample**:
3. **Check Evaluation Details or Action Link**
* If you **have already submitted your evaluation**, the email will display a summary of your evaluation details directly within the email body.
* If you **have not yet submitted your evaluation**, the email will include a **link** that redirects you to the evaluation form in Talview.
> This helps you complete pending feedback quickly without needing to log into the platform manually.
4. **Candidate Attendance Scenarios**
* **Candidate Attended:** You’ll see candidate and interviewer participation details, and if applicable, the evaluation summary.
* **Candidate No-Show:** The email will indicate that the candidate did not attend, along with a message appreciating your participation.
***
# Getting Started - Talent Acquisition
Source: https://docs.talview.com/hiring-teams/getting-started
***
Guides for recruiters and hiring managers to set up, schedule, evaluate, and track hiring workflows with Talview.
Get started by logging in, setting up your profile, and ensuring your device and browser meet compatibility requirements.
Create, manage, and track job requisitions across your hiring pipeline.
Launch assessments, assign them to candidates, review submissions, and score effectively.
Schedule or reschedule interviews, enable self-scheduling, and manage interview logistics with ease.
Use structured scorecards, provide written feedback, and collaborate with your team for fair and consistent evaluations.
Access walkthrough videos, tutorials, and best practices tailored for recruiters and hiring managers.
Learn how Talview's AI screens candidate resumes and surfaces the best-fit candidates for your role.
# Candidate did not receive an assessment invitation email
Source: https://docs.talview.com/hiring-teams/recruiter/assessments/diagnostics/candidate-did-not-receive-an-assessment-invitation-email
You’ve sent an assessment invite from the **Assessment Step** in Workflow Tools, but the candidate reports not receiving it. This article helps you verify common issues and ensure delivery.
## [****](https://docs.talview.com/hiring-teams/for-talent-acquisition/assessments/diagnostic/recruiter/candidate-did-not-receive-an-assessment-invitation-email#%E2%9C%85-common-causes-and-fixes)
## ✅ Common Causes and Fixes
| **What Might Be Wrong** | **What You Can Do** |
| :--------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------ |
| Candidate’s email address was entered incorrectly | Double-check the candidate’s email in the **Candidate Card → Profile** section. Correct and resend if needed. |
| Invitation email went to **spam or promotions** folder | Ask the candidate to check **Spam**, **Promotions**, or **Updates** folders. |
| Candidate unsubscribed from Talview emails earlier | Contact Talview Support to check and **re-subscribe the candidate’s email** if previously unsubscribed. |
| Email was blocked by company firewall (esp. in corporate emails) | Ask the candidate to whitelist `noreply@talview.com` or try with a **personal email** if possible. |
| Assessment not yet triggered | Ensure you’ve clicked **“Send Assessment”** in the assessment step after assigning the test. |
| Assessment status not updated | Refresh the Workflow tab and check if the invite shows as **Sent** under the Assessment section. |
## 🌐 Final Checks for Email Delivery
Before contacting support:
* Verify the **test is assigned** in the correct step
* Confirm **email domain is not blacklisted**
* Check if **duplicate invites** were sent recently (this may cause mail filters to block them)
### **Additional Troubleshooting**
* **Check Activity Log** on the candidate’s card to confirm if the invite was triggered.
* **Resend the invite** after reconfirming candidate details.
* Avoid **bulk uploads with missing email fields** — these may silently skip invites.
# Candidate status not updating to “Completed”
Source: https://docs.talview.com/hiring-teams/recruiter/assessments/diagnostics/candidate-status-not-updating-to-completed
When candidates finish their assessments, their status should automatically update to "Completed" in your workflow. If this isn't happening, it can disrupt your recruitment pipeline and cause confusion.
This article helps you troubleshoot why candidate statuses aren't updating to "Completed" in Talview Workflow Tools and provides solutions to resolve the issue.
## 🔎Troubleshooting Common Issues
| **What might be wrong** | **How to fix it** |
| :---------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Candidate hasn't completed all mandatory stages** | Check the candidate's progress in the workflow timeline. Verify they've finished all required assessments, interviews, or documents. If any stage shows "In Progress" or "Not Started," the status won't update until completion. |
| **System sync delay or cache issue** | Refresh the candidate list page or log out and log back in. If the issue persists, clear your browser cache or try accessing Workflow Tools in an incognito window. Wait 5-10 minutes as status updates may experience slight delays during high traffic. |
| **Browser extensions or ad blockers interfering with workflow updates** | Disable browser extensions, especially ad blockers or privacy tools, and refresh the page. Try accessing Workflow Tools in a different browser or incognito mode to rule out extension interference. |
### **Additional Tips:**
* Ensure you have the necessary permissions to view and manage workflow automation settings.
* Verify that the candidate's email notifications were successfully delivered, as failed communications can sometimes indicate incomplete stages.
* Contact your Administrator if status updates fail across multiple candidates, as this may indicate a system-wide configuration issue
# Candidate stuck in “Invited” status after starting the test
Source: https://docs.talview.com/hiring-teams/recruiter/assessments/diagnostics/candidate-stuck-in-invited-status-after-starting-the-test
When candidates begin an assessment, but their status remains "Invited" in your recruiter dashboard, it disrupts your ability to track progress and manage the hiring workflow effectively.
This article helps you identify why a candidate's status isn't updating correctly and provides solutions to resolve the issue.
## 🔎 Troubleshooting Common Issues
| **What Might Be Wrong** | **How to Fix It** |
| :------------------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Candidate didn't complete the assessment setup** | Contact the candidate to confirm they proceeded past the initial instructions page. The status update happens when the candidate lands on the instruction page. |
| **Browser session timeout or interruption** | Ask the candidate to clear their browser cache, restart their browser, and attempt the assessment again using the original invitation link. |
| **System synchronization delay** | Wait 5-10 minutes and refresh your recruiter dashboard. If the status still doesn't update, check the candidate's activity logs under their profile for assessment start timestamps. |
| **Technical issues on candidate's end** | Verify the candidate meets minimum system requirements (stable internet connection, supported browser version). Ask them to try a different device or network if possible. |
### **Additional Tips:**
* Access the candidate's detailed activity logs in the Assessment module to see if any test interactions were recorded, even if the status didn't update.
* Confirm the candidate received the invitation email and didn't access an outdated link from a previous invitation
* Send yourself a test invitation to replicate the candidate experience and identify where the status update might be failing.
* If multiple candidates show this problem, contact Talview support as it may indicate a broader system issue requiring technical intervention
# Exported assessment data incomplete or blank
Source: https://docs.talview.com/hiring-teams/recruiter/assessments/diagnostics/exported-assessment-data-incomplete-or-blank
When you click the **Export button** in Talview's Workflow Tools, you expect a complete report with all candidate assessment data. However, sometimes the downloaded xlsx file contains incomplete information or appears entirely blank, making it difficult to review candidate performance and make informed hiring decisions.
This article helps recruiters troubleshoot and resolve issues when exported assessment data is incomplete, missing, or blank.
## 🔎 Troubleshooting Common Issues
| **What might be wrong** | **How to fix it** |
| :---------------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Browser cache or download interruption** | Clear your browser cache and cookies, then retry the export. Ensure your internet connection is stable throughout the download process. |
| **File downloaded but didn't open correctly** | Locate the downloaded xlsx file in your Downloads folder and open it with a spreadsheet application (Excel, Google Sheets). The file may have downloaded successfully but didn't auto open. |
| **Assessment scores are still being processed** | Allow 10-15 minutes after the last candidate submission for the system to calculate scores, especially for coding assessments or multi-section tests. Refresh the page and try exporting again |
| **CSV file is corrupted during download** | If the file appears blank when opened, try re-downloading it. Check your Downloads folder for multiple versions of the file and ensure your antivirus software isn't blocking or quarantining the download |
### **Additional Tips:**
* Try exporting a smaller date range or subset of candidates first to isolate whether the issue is related to data volume or specific candidate records.
* If the CSV opens but the file is blank despite candidates completing the assessment, check whether evaluation has been completed.
* Try using a different browser **(Chrome, Firefox, Edge)** if the export consistently fails, as browser-specific issues can sometimes interfere with file downloads.
# Proctoring alerts not visible for a candidate
Source: https://docs.talview.com/hiring-teams/recruiter/assessments/diagnostics/proctoring-alerts-not-visible-for-a-candidate
When monitoring candidates during proctored assessments, you may find that proctoring alerts are not appearing for a specific candidate even though proctoring is enabled. This can prevent you from reviewing flagged behaviors and compromise assessment integrity.
This article helps you troubleshoot why proctoring alerts are not visible for a candidate in Talview's Workflow Tools.
## 🔎 Troubleshooting Common Issues
| **What might be wrong** | **How to fix it** |
| :------------------------------------------------------ | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Proctoring is not enabled for the assessment** | Navigate to the assessment settings and verify that proctoring is enabled. Ensure the proctoring is activated before the candidate begins the test. |
| **Candidate has not started the assessment yet** | Proctoring alerts only generate after a candidate starts the assessment. Check the candidate's status in the **Candidates** tab to confirm they have begun the test. |
| **Network or connectivity issues disrupted monitoring** | Unstable internet connection, VPN usage, or restrictive workplace networks can interrupt the proctoring feed and prevent alerts from being recorded or transmitted to the dashboard. |
| **Candidate's device or browser is incompatible** | The candidate may be using an unsupported browser or outdated version that prevents proper alert transmission. Verify the candidate is using\*\*Chrome, Edge, or Firefox \*\* with the latest updates, and ensure their camera/microphone hardware is functioning correctly. |
| **Browser permissions were denied by the candidate** | The candidate may have denied camera or microphone access during onboarding. Contact the candidate and ask them to refresh the assessment page, then grant the required permissions when prompted. |
| **Candidate left the assessment prematurely** | If the candidate exited or was disconnected before completing significant portions of the test, insufficient monitoring data may have been captured to generate alerts. Review the candidate's completion percentage and session duration. |
### **Additional Tips:**
* **Check real-time monitoring**: Switch to the live proctoring view to see if alerts are being generated in real-time but not displaying in the summary dashboard.
* **Review assessment completion status**: If the candidate has already completed the assessment, alerts should be available in the post-assessment recording.
* **Contact candidate immediately**: If proctoring failed during the assessment, reach out to the candidate to reschedule with proper setup.
# Report not generating or missing candidates
Source: https://docs.talview.com/hiring-teams/recruiter/assessments/diagnostics/report-not-generating-or-missing-candidates
Assessment reports are crucial for evaluating candidate performance and making informed hiring decisions. When reports fail to generate or show incomplete candidate data, it disrupts your recruitment workflow and delays decision-making.
This article helps you troubleshoot issues when assessment reports don't generate, load partially, or exclude candidates who completed the assessment.
## 🔎 Troubleshooting Common Issues
| **What might be wrong** | **How to fix it** |
| :---------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Assessment is still in progress** | Wait until all scheduled candidates complete the assessment. Report will only generate once the candidate completes the assessment |
| **Report generation is processing** | Large assessments with many candidates take time to compile. Refresh the page after 2-3 minutes. Check the notification bell for completion alerts. |
| **Browser cache or session issue** | Clear your browser cache and cookies, then log back in. Try accessing the report in an incognito window or different browser. |
### **Additional Tips:**
* Verify candidates received assessment invitations by checking the workflow's communication logs under the Candidates tab.
* Contact **Talview support** if reports consistently fail after trying these steps.
# Scores not appearing for a completed assessment
Source: https://docs.talview.com/hiring-teams/recruiter/assessments/diagnostics/scores-not-appearing-for-a-completed-assessment
When a candidate completes an assessment, their scores should appear automatically in the recruiter dashboard. If scores are missing or not displaying as expected, several factors could be preventing the results from appearing correctly.
This article helps recruiters troubleshoot and resolve issues when assessment scores don't appear after a candidate has completed their evaluation.
## 🔎 Troubleshooting Common Issues
| **What might be wrong** | **How to fix it** |
| :--------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Assessment is still being processed | Wait 2-3 minutes after completion. Large assessments with video responses or coding tests may take longer to process. Refresh the candidate's profile page to check for updated scores. |
| Score visibility settings are restricted | Check **Assessment Permissions** in the workflow settings. Ensure your user role has permission to view assessment scores. Contact your admin if access needs to be updated. |
| Browser cache or session issue | Clear your browser cache and cookies, then log back into Talview. Try accessing the scores from a different browser or in incognito mode to rule out local caching issues. |
| Assessment submission wasn't recorded | Verify the candidate's submission status shows as "Completed" in the workflow dashboard. If it shows "In Progress," the candidate may not have clicked the final submit button. Ask the candidate to confirm submission. |
### **Additional Tips:**
* Verify that the assessment was properly submitted and not left incomplete; ensure you see a confirmation screen after completing it.
* Refresh the page or log out and back in again, as scores may not show up immediately due to sync delays or browser cache issues.
* Retake the assessment if possible; this can help update your scores on the dashboard and give you clearer feedback on your performance.
# Suspended assessment not moving back to “Invited” after reactivation
Source: https://docs.talview.com/hiring-teams/recruiter/assessments/diagnostics/suspended-assessment-not-moving-back-to-invited-after-reactivation
When you reactivate a suspended assessment, you expect the candidate's status to automatically return to "Invited". However, sometimes the status remains unchanged or doesn't update as expected.
This article helps you troubleshoot why a candidate's assessment status isn't reverting to "Invited" after you've removed the suspension.
## 🔎Troubleshooting Common Issues
| **What might be wrong** | **How to fix it** |
| :------------------------------------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **The candidate already completed the assessment before suspension** | Check the candidate's evaluation history in their profile. If they submitted their assessment before the suspension was applied, reactivation won't change their status back to "Invited." You'll need to reset or reassign the assessment if you want them to retake it. |
| **System sync delay after reactivation** | Wait 5-10 minutes after removing the suspension, then refresh the candidate list. Status updates may take a few moments to reflect across the system. If the status still doesn't update, try logging out and back in. |
| **The workflow stage has progressed beyond the assessment** | Review the candidate's current workflow stage. If they've been moved to a different stage (manually) while suspended, reactivation won't move them backward. You'll need to manually reassign them to the assessment stage. |
### **Additional Tips:**
* Verify you have the necessary permissions to reactivate assessments and modify candidate statuses in your workflow.
* Check if any automated rules or triggers in your workflow are preventing status changes after reactivation.
* Contact your Talview administrator if the candidate appears in multiple workflows simultaneously, as this can cause status conflicts.
# Video recording not playing in the report view
Source: https://docs.talview.com/hiring-teams/recruiter/assessments/diagnostics/video-recording-not-playing-in-the-report-view
When you review a candidate's assessment, you expect to see their video recording, but sometimes the video doesn't load or play as expected in the report view.
This article helps you troubleshoot why a candidate's video recording isn't playing when you open their assessment report.
## 🔎Troubleshooting Common Issues
| **What might be wrong** | **How to fix it** |
| :------------------------------------------ | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Slow internet connection** | Check your network connection and try loading the video again. If you're on a weak connection, wait for the video to buffer completely before attempting to play it. Consider switching to a stronger network or using a wired connection. |
| **Video file is still processing** | Wait a few minutes and refresh the report. Video processing can take time depending on the recording length and system load. If the recording was submitted recently, give it 5-10 minutes before checking again. |
| **Browser compatibility issue** | Switch to a supported browser (Chrome, Firefox, or Edge). |
| **Browser extension blocking media** | Disable ad blockers, privacy extensions, or script blockers temporarily. These extensions can interfere with video playback. Refresh the page after disabling them to see if the video loads. |
| **Video player component not loading** | Refresh the entire page using `Ctrl+F5 (Windows)` or `Cmd+Shift+R (Mac)` to force reload all page elements. This clears any cached issues with the video player. |
| **Session timeout or authentication issue** | Log out of Talview completely and log back in. Your session may have expired, preventing secure video content from loading. |
### **Additional Tips:**
* Try playing other candidate videos in different reports to determine if this is an isolated issue or affects multiple recordings.
* Check if audio plays even when video doesn't display, this can indicate a rendering issue rather than a loading problem.
* Verify that your system's date and time settings are correct, as certificate validation errors can prevent secure video streaming.
* Check with other team members to see if they can access the same video. If they can, the issue is likely on your end.
# Recruiter FAQs - Assessments
Source: https://docs.talview.com/hiring-teams/recruiter/assessments/faqs/recruiter-faqs-assessments
### **1. Invitations & Candidate Access**
**Q1. How do I invite candidates to an assessment?**
You can invite candidates directly from within a workflow by selecting the “Invite” option in the footer and choosing the relevant assessment. Candidates will then receive an email with their unique access link.
**Q2. Can I bulk-invite multiple candidates at once?**
Yes. Upload a candidate list or select multiple candidates in the workflow to send invitations in bulk.
**Q3. What should I do if a candidate didn’t receive the assessment invite?**
Check if the email address is correct. You can also resend the invite from the candidate’s assessment details in the side panel.
**Q4. Can I resend an assessment to a candidate who already completed it?**
Yes, but only if you configure a re-invite. Previous submissions will still remain in history.
***
### **2. Due Dates & Extensions**
**Q1. How do I set a due date for an assessment?**
When inviting candidates, you can define a start date and a due date. The same will be visible in the candidate’s invitation.
**Q2. Can I extend the assessment due date for specific candidates?**
Yes. From the candidate’s assessment details, you can update and extend the deadline for individual candidates or in bulk.
**Q3. What happens if a candidate tries to submit after the due date?**
Candidates cannot access or submit assessments past the due date unless you extend it.
***
### **3. Monitoring Progress & Candidate Status**
**Q1. How can I check which candidates have started or completed their assessment?**
**A.** You can view candidate progress (Not Started, In Progress, Completed) on the assessment dashboard.
**Q2. Can I pause or suspend an assessment for a candidate?**
**A.** Yes. Recruiters can suspend assessments that haven’t been started yet. Suspended candidates will not be able to access the test unless re-invited.
***
### **4. Viewing Scores, Responses & Reports**
**Q1. Where can I view candidate scores after completion?**
Scores will be visible in the candidate’s profile and in the assessment dashboard under the “Score” section.
**Q2. Can I view detailed candidate responses?**
Yes. For each candidate, you can view individual responses, including text, video, or coding submissions (depending on the assessment type).
**Q3. What reports are available for recruiters?**
The system will generate **Candidate-level reports** after the candidates complete the assessment and the same can be viewed from the candidate’s assessment details.
**Q4. Can I download reports for offline sharing?**
No. Reports cannot be exported at the moment from the platform.
***
### **5. Evaluations & Feedback**
**Q1. How do interviewers/evaluators submit evaluations?**
Once an evaluator is assigned to evaluate a candidate, they can log in, access the candidate profile, and fill out the evaluation form associated with the assessment.
**Q2. Can multiple evaluators review the same candidate?**
Yes. Multiple evaluators can provide inputs, and recruiters can see consolidated evaluation views in the candidate’s assessment details.
**Q3. How do I check if evaluations are completed for all candidates?**
The evaluation dashboard shows pending vs. completed evaluations per candidate.
***
### **6. Proctored Assessments**
**Q1. What is a proctored assessment?**
A proctored assessment monitors candidate activity (camera, microphone, screen, or browser) during the test to ensure authenticity and prevent malpractice.
**Q2. How do I enable proctoring for an assessment?**
Currently, this option is only available for the admins when they are setting up the assessment.
**Q3. What candidate details are captured during a proctored session?**
Depending on configuration, details may include:
* Face authentication results
* Video/audio recordings or snapshots
* Browser activity logs
* Flags for suspicious behavior (e.g., multiple faces, tab-switching)
**Q4. How do I review proctoring violations or flags?**
In the candidate’s assessment details, click on the **Proview index** to load the playback view that highlights any incidents.
**Q5. Can candidates see they are being proctored?**
Yes. Candidates are always notified before the test begins.
**Q6. Are proctoring results integrated with the overall assessment score?**
No. Proctoring violations are provided as P**roview indices** for recruiters and evaluators. The candidate’s answers are still scored independently.
***
### **7. Other Topics**
**Q17. How do I handle technical issues raised by candidates?**
**A.** Recruiters should redirect candidates to the support/troubleshooting help center.
**Q18. Can I anonymize candidate results before sharing with hiring managers?**
**A.** No. This feature is not available at the moment.
# Adding Feedback Comments After Assessment and Updating Status
Source: https://docs.talview.com/hiring-teams/recruiter/assessments/how-tos/adding-feedback-comments-after-assessment-and-updating-status
Workflow Tools enables recruiters to leave qualitative feedback for candidates and update their evaluation status directly from the candidate’s side panel. This ensures structured evaluations and clear next steps in the hiring process.
## Steps:
### 1. Open the Relevant Workflow
Navigate to the **Workflow** where the candidate’s assessment step is located.
### 2. Access the Assessment Step
Click on the **tab for the assessment step** that includes the candidate you want to evaluate.
### 3. Open Candidate’s Side Panel
Locate the candidate in the list and click to **open their side panel**.
### 4. Go to the Evaluation Tab
Within the side panel, switch to the **Evaluation** tab.
### 5. Expand “Your Evaluation” Section
Click to **expand the “Your Evaluation” section** where you can input your assessment feedback.
### 6. Add Feedback Comments
Type your qualitative feedback in the **text area field**. This helps document your evaluation reasoning and decision-making.
### 7. Change Candidate Status
Click the **“Change Status”** button below the feedback field.
A dropdown will appear with the available status options:
* **Select**
* **Hold**
* **Suspend**
* **Turn Down**
Choose the desired option and confirm the status update.
# Bulk Invites: Sending Assessments to Multiple Candidates
Source: https://docs.talview.com/hiring-teams/recruiter/assessments/how-tos/bulk-invites-sending-assessments-to-multiple-candidates
The bulk invite feature in Workflow Tools allows recruiters to efficiently send assessment invites to multiple candidates at once, minimizing repetitive work and streamlining the hiring process.
## Steps:
### 1. Select the Workflow
Navigate to the **Workflow** that contains the assessment step you want to invite candidates for.
### 2. Select Candidates
On the **Candidate List** page within the workflow:
* Use the **checkboxes** beside each candidate's name to select multiple candidates that need to take the assessment.
### 3. Open the Invite Side Panel
* Once candidates are selected, find the **Invite** button in th **bottom action bar.**
* Click on the **Invite** button to open the **Invite Side Panel**.
### 4. Configure the Assessment Step
* In the side panel, choose the specific **assessment step** from the **dropdown** (if there are multiple assessmenr stepsin the workflow).
* Ensure the correct assessment is selected before proceeding.
### 5. Send Invites
* After confirming the step and candidate selection, click the **Invite** button to send out the invites.
* Upon successful invite, a **confirmation toast message** will appear, indicating that the invitations have been sent.
# Exporting Candidate Assessment Data
Source: https://docs.talview.com/hiring-teams/recruiter/assessments/how-tos/exporting-candidate-assessment-data
Exporting assessment data from Workflow Tools enables recruiters to download and review detailed reports of candidate performance across different assessments. This is useful for analysis, documentation, or sharing results with stakeholders.
## Steps:
### 1. Open the Relevant Workflow
Navigate to the **Workflow** where the assessment you want to export is configured.
### 2. Go to the Assessment Tab
Click on the **tab corresponding to the assessment step** whose data you wish to export. This tab displays the list of all candidates invited to that particular assessment.
### 3. Click the Export Button
In the assessment tab view:
* Locate the **Export** button.
* Click on it to begin downloading the report.
### 4. Download and Review the Report
A **spreadsheet file** will be downloaded automatically.
* This report includes:
* **Candidate Name and Email**
* **Assessment Status**
* **Total Score**
* **Section-wise Scores**
* **Invited By** (Recruiter who sent the invite)
# How to invite candidates and evaluators to a Live interview?
Source: https://docs.talview.com/hiring-teams/recruiter/assessments/how-tos/how-to-invite-candidates-and-evaluators-to-a-live-interview
**Talview Interview Rooms**, integrated with Workflow Tools, enables recruiters to schedule and invite both candidates and evaluators seamlessly.
This guide explains the step-by-step process to send out invitations, along with checklists, troubleshooting steps, and best practices.
***
## Video Guide
### Step 1: Select Workflow and step
* In Talview Live Interview, choose the relevant **Workflow Type and step.**
### Step 2: Add Candidate
* Enter the candidate’s full name and verify the email address.
Click on **Add and** then on **Invite** to proceed.
### Step 3: Add Interviewer
* Add evaluators/interviewers by entering their **email addresses**.
* Confirm **panel availability** before finalizing.
### Step 4: Finalize Schedule
* Select the interviewer from the dropdown.
* Confirm the **date, time, and time zone** of the interview.
* Ensure the schedule works for both candidates and evaluators.
* Send out **interview invitations**.
Email Details are Sent Automatically to both candidates and evaluators that include :
* Interview date, time, and time zone.
* Secure link to join the Interview Room.
* Support contact information.
* **Automated reminders** before the session.
## Checklist before the invite
Before sending invitations, ensure:
* Candidate and evaluator **email addresses** are correct.
* The **date, time, and time zone** are accurate.
* All evaluators are assigned with the **correct roles**.
* Support contact details are updated in case participants need help.
## Best Practices
* Always double-check time zones when scheduling across regions.
* Send invitations at least 48 hours in advance to allow preparation.
* Use the **reminder system** to reduce no-shows.
* Keep panel size manageable (avoid overloading evaluators).
* Share a troubleshooting guide with candidates beforehand for smoother participation.
# How to Reinvite Candidates Who Missed or Completed an Assessment
Source: https://docs.talview.com/hiring-teams/recruiter/assessments/how-tos/how-to-reinvite-candidates-who-missed-or-completed-an-assessment
Workflow Tools allows recruiters to **reinvite candidates** who either missed or completed a previous assessment. This is especially useful for giving another chance to candidates who faced technical issues or when assessments need to be retaken.
## Steps:
### **1. Open the Relevant Workflow**
Navigate to the **Workflow** where the desired assessment is configured.
### **2. Go to the Assessment Step Tab**
Click on the **assessment step tab** that contains the candidates you want to reinvite.
### **3. Select Eligible Candidates**
Use the checkboxes to **select the candidates** who have either:
* **Missed the assessment** (status still being *Invited*), or
* \*\*Completed the assessment(\*\*eg: status being completed, yet to evaluate **)**, but need to take it again.
### **4. Click the Invite Button**
* After selecting the candidates, click on the **Invite** button that appears at the bottom of the candidate list.
* This opens the **invite side panel**.
### **5. Configure the Reinvite**
In the side panel:
* Ensure the correct **assessment step** is selected in the dropdown.
* Confirm your selections and click **Invite**.
### **6. Confirmation**
A **toast message** will appear on the screen confirming that the reinvites have been sent successfully.
Use reinvites sparingly and with context, for example, when a candidate faced issues accessing the test or when a re-evaluation is required.
# Inviting existing candidates to the assessment
Source: https://docs.talview.com/hiring-teams/recruiter/assessments/how-tos/inviting-existing-candidates-to-the-assessment
This article provides a step-by-step guide to help recruiters invite new candidates to the assessment stage within **Talview's Workflow Tools Platform**.
## Step-by-step Guide
### Step 1: Access the workflow dashboard
* Navigate to the **Workflows** section from the menu.
* Select the workflow, to send the assessment invitation to the existing candidates.
### Step 2: Sending the Invites
* Select the candidates that are already present in the workflow, then click on **Invite.**
* In the side panel, fill in the details such as the right workflow, the step and the candidate details.
* After filling in the details, click on **Invite**.
### Step 3: **Confirmation**
* Invites sent successfully and can be viewed in that respective interview step.
* The invites will be saved in that respective interview stage.
# Inviting new candidates to the assessment
Source: https://docs.talview.com/hiring-teams/recruiter/assessments/how-tos/inviting-new-candidates-to-the-assessment
This article provides a step-by-step guide to help recruiters invite new candidates to the assessment stage within **Talview's Workflow Tools Platform**.
## Step-by-step Guide
### Step 1: Access the workflow dashboard
* Navigate to the **Workflows** section from the menu.
* Select the workflow, to send the assessment invitation to the existing candidates.
### Step 2: Sending the Invites
* Click on **Invite,** to send assessment invites to new candidates.
* Click on **Download template or Upload,** to add the candidates to the workflow with the help of the saved spreadsheet.
* **Or** You can manually add new candidates to the workflow, by clicking on **Add candidates**.
* Provide the candidates details like Name, mail id, phone number with the correct country code and click on **Add.**
* Repeat the same steps to add more candidates.
### Step 3: **Confirmation**
* Click on **Invite,** to send the assessment invites.
* Invites sent successfully and can be viewed in that respective interview step.
# Understanding Candidate Assessment Statuses
Source: https://docs.talview.com/hiring-teams/recruiter/assessments/how-tos/understanding-candidate-assessment-statuses
Within the **Assessment step** of any workflow in Workflow Tools, each candidate is tagged with a real-time status that reflects their current progress in the assessment lifecycle. These statuses help recruiters track engagement, monitor completions, and take necessary actions like evaluation, shortlisting, or reinvites.
## ✅ Status Types and Their Meanings
* **Invited**
The candidate has received the assessment invitation but hasn’t started the test yet.
* **In Progress**
The candidate has opened and begun attempting the assessment, but has not submitted it yet.
* **Yet to Evaluate**
The candidate has completed and submitted the assessment, but it hasn’t been evaluated by a recruiter or evaluator.
* **Selected**
The candidate has been shortlisted for the next stage. This can happen:
* **Automatically**, if an auto-shortlisting rule or score threshold is configured.
* **Manually**, by the recruiter after reviewing the assessment results.
* **Turned Down**
The candidate has been rejected. This can occur:
* **Automatically**, based on a predefined threshold or scoring rule.
* **Manually**, after the recruiter evaluation.
* **Hold**
The candidate has been kept on hold. This can occur:
* **Manually**, after the recruiter evaluation.
## 🌐 Usage
These statuses are visible in the candidate list under the relevant assessment step tab in the workflow. Recruiters can filter, sort, or act upon candidates (e.g., send reminders, reinvite, or evaluate) based on these statuses.
# View a candidate’s Ivy summary in detail
Source: https://docs.talview.com/hiring-teams/recruiter/assessments/how-tos/view-a-candidates-ivy-summary-in-detail
Recruiters can easily review **Ivy AI Interview summaries** for candidates who have completed their Ivy assessments directly within **Workflow Tools**.
This feature provides quick access to both the **candidate’s recorded Ivy interview** and the **AI-generated summary** under the **Overview** tab.
By viewing the **Key Discussion Areas**, recruiters can gain insights into a candidate’s communication style, response quality, and primary discussion topics - enabling faster shortlisting and data-driven decision-making.
***
## Steps to Go Through the Flow
1. **Log in to Workflow Tools as a Recruiter**
* Sign in to your organization’s **Workflow Tools** platform using your recruiter credentials.
* You’ll land on your **Workflow Dashboard**, which lists all your active workflows.
2. **Select the Workflow with Ivy Configured**
* From the dashboard, click on the **workflow name** that includes the Ivy interview step.
* The workflow details page will open, showing all configured steps (e.g., Screening, Assessment,).
3. **Open the Ivy Interview Step**
* Locate the Ivy interview step
* This step displays the list of candidates who have been invited to or completed the Ivy assessment.
4. **Click on a Candidate Who Has Completed the Ivy Interview**
* Select the **candidate's name** from the list.
* A **side panel** will open on the right-hand side of the screen, showing candidate details.
5. **View the Ivy Summary in the Overview Tab**
* Inside the side panel, click on the **Overview** tab
* You will see:
* The **candidate’s Ivy interview response video**.
* Directly below it, the **Summary section** titled **“Key Discussion Areas.”**
6. **Review the Summary Details**
* The **Key Discussion Areas** summarize the most relevant topics and themes discussed during the Ivy interview.
* This helps you quickly assess how well the candidate articulated key points without watching the full recording.
* You can replay the video anytime to cross-verify or review specific parts of the candidate’s responses.
### **Pre-requisites**
Before accessing the Ivy interview summary, ensure that:
* You are logged in with **Recruiter** or **Master Recruiter** permissions.
* The workflow includes a step where **Ivy Interview** is configured.
* The candidate has **completed** the Ivy assessment successfully.
***
# View a proctored assessment response on the platform
Source: https://docs.talview.com/hiring-teams/recruiter/assessments/how-tos/view-a-proctored-assessment-response-on-the-platform
This article provides a step-by-step guide to help recruiters view a proctored assessment response within **Talview's Workflow Tools Platform**.
## Step-by-step Guide
### Step 1: Access the workflow dashboard
* Navigate to the **Workflows** section from the menu.
* Select the workflow for which you want to view a proctored assessment response.
* Select the assessment step inside a workflow to quickly view the candidate's progress.
* Click on a candidate's name to dive into their assessment details.
### **Step 2: Viewing a** proctored candidate assessment response
* In the candidate’s assessment details, switch to the **Score** tab to review the score and proctoring details for the candidate.
* Click on the **Icon** to check the proctoring index and to view the session playback recording.
* In the **session playback**,
* Select a key session event in the alert log to review monitoring actions.
* Switch between the **Primary and secondary camera** feed for real-time insights into candidate behavior.
* When you’re done viewing the playback recording, click on the close icon ✖️ to exit the playback session and return to the candidate overview.
# Viewing candidates' assessment invitation
Source: https://docs.talview.com/hiring-teams/recruiter/assessments/how-tos/viewing-candidates-assessment-invitation
This article provides a step-by-step guide to help recruiters to view the assessment invites within **Talview's Workflow Tools Platform**.
## Step-by-step Guide
### Step 1: Access the workflow dashboard
* Navigate to the **Workflows** section from the menu.
* Select the workflow, to view the assessment invitation.
### Step 2: Viewing the Invites
* Select the **interview stage** to view and manage candidate invites.
* In the interview stage, click on a candidate's name to access detailed profile and assessment information.
* A side panel with the candidate’s details, invitation details and candidate’s response is available.
# What should I do if the room is missing or incorrectly assigned?
Source: https://docs.talview.com/hiring-teams/recruiter/drives/diagnostics/what-should-i-do-if-the-room-is-missing-or-incorrectly-assigned
During a virtual hiring event or a drive, recruiters and interviewers rely on room assignments to manage interviews across multiple interviews and sessions simultaneously.
When rooms are not visible to the intended users or are assigned incorrectly, it disrupts the entire interview workflow, causes candidate delays, and creates confusion for interviewers.
This diagnostic article identifies common causes of room visibility and assignment issues in Drive management system and provides actionable solutions to resolve them quickly.
## 🔎 Troubleshooting Common Issues
| **Issue** | **How to Fix It** |
| :------------------------------------------------ | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Room not assigned to the interviewer profile** | Verify that the interviewer has been explicitly assigned to the specific room in the Drive settings. Navigate to the Drive configuration, select the room, and confirm the interviewer in the assigned interviewer list. Add and confirm the interviewer and save changes. |
| **Room creation incomplete or not published** | If the room is incomplete, finalize all required fields and publish the room to make it active and visible to assigned interviewers and recruiters. |
| **User permissions insufficient for room access** | Review the user's role and permissions within the Drive. Ensure the user has appropriate access levels (interviewer, organizer, or admin) that grant visibility to assigned rooms. |
| **Browser cache or session issues** | Clear the browser cache and cookies, then refresh the page. Instruct users to log out completely and log back in to refresh their session. This resolves visibility issues caused by outdated cached data or stale authentication tokens. |
| **Technical platform synchronization delay** | Wait 2-3 minutes after making room assignment changes, as platform synchronization may take time to propagate across the system. If delays persist beyond 5 minutes, contact Talview support to investigate backend synchronization issues. |
### Additional Tips:
* Provide interviewers with clear instructions on how to access their assigned rooms.
* Maintain a backup communication channel (such as a messaging platform or email thread) where interviewers can quickly report room visibility issues during live events, ensuring rapid response and minimal disruption to the candidate experience.
# Why am I seeing an error while creating a drive?
Source: https://docs.talview.com/hiring-teams/recruiter/drives/diagnostics/why-am-i-seeing-an-error-while-creating-a-drive
When creating a drive, recruiters may occasionally encounter errors that impede successful setup.
This article helps Talent Acquisition and Recruiting teams quickly diagnose and resolve common issues encountered during drive creation, ensuring seamless scheduling and management of virtual career fairs or high-volume hiring events.
## 🔎 Troubleshooting Common Issues
| **What might be wrong** | **How to fix it** |
| :--------------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Scheduling conflicts with interviewer or venue | Reschedule to avoid overlaps or unavailable slots. |
| Unsupported device or browser in use | Switch to a recommended browser (latest Chrome, Firefox, or Edge) on a desktop or laptop. Run the system compatibility check provided within the platform. |
| Platform/network issues | Check internet connectivity and refresh the page. If the error persists, reach out to Talview support. |
| Pending software updates or permissions | Clear cache or update the browser before retrying. |
### **Additional Tips:**
* Ensure all participants are informed of new or rescheduled times to avoid no-shows and improve candidate experience.
* Take a screenshot or download the error logs (if available) and share them with Talview support for faster resolution.
# Why am I unable to edit the drive series?
Source: https://docs.talview.com/hiring-teams/recruiter/drives/diagnostics/why-am-i-unable-to-edit-the-drive-series
Drive Series allow recruiters to organize and manage multi-day virtual hiring events with automated scheduling, room allocation, and interviewer assignment. However, recruiters may sometimes encounter difficulties when attempting to modify scheduled drive dates or details.
This article helps troubleshoot common issues that prevent recruiters from editing drive series.
## 🔎 Troubleshooting Common Issues
| **What Might Be Wrong** | **How to Fix It** |
| :------------------------------------------------------------ | :----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| The drive date has already passed | Only upcoming or current drive dates can be edited. Create a new drive series for future dates instead. |
| The drive has not been scheduled yet | Ensure the drive series has been scheduled within the specific date before attempting edits. Only dates that appear in the drive schedule can be modified. |
| Browser cache or session issues are interfering | Clear the browser cache and cookies, then log in again. Try accessing the platform using an incognito window or a different browser to rule out session conflicts. |
| Candidates have already been assigned to scheduled slots | Reschedule or reassign candidates individually before modifying the drive. |
| Multiple recruiters are editing the same drive simultaneously | Coordinate with team members to avoid concurrent edits. Ensure only one recruiter modifies the drive series at a time to prevent data conflicts. |
### **Additional Tips:**
* Always communicate schedule changes to affected candidates immediately through the **unified notification inbox** to minimize no-shows and confusion.
* Save changes promptly after making adjustments to ensure updates are reflected across the drive schedule.
* Review real-time drive insights to identify scheduling bottlenecks or attendance issues before making edits.
# Why am I unable to view Drive insights?
Source: https://docs.talview.com/hiring-teams/recruiter/drives/diagnostics/why-am-i-unable-to-view-drive-insights
Drive insights provide real-time visibility into each virtual hiring event or a drive, insights include total candidates and interviewers, booked candidates and no-show candidates when these analytics fail to load, recruiters lose critical oversight needed to manage campus hiring drives, bulk recruitment events, and scheduled interview coordination effectively.
## 🔎 Troubleshooting Common Issues
| **What Might Be Wrong** | **How to Fix It** |
| :-------------------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Browser cache or cookies are causing conflicts** | Clear browser cache and cookies, then refresh the page. Try accessing Drive insights in an incognito or private browsing window to rule out cached data issues. |
| **Network connectivity issues or timeout errors** | Check internet connection stability and speed. If using VPN, temporarily disable it and retry. Refresh the page after ensuring stable network connectivity. |
| **Insufficient user permissions to view analytics** | Verify that the user account has appropriate permissions to access Drive insights. Contact the Talview administrator to confirm role-based access settings for analytics and reporting features. |
| **Data not synced or still processing** | Allow time for data synchronization, especially for newly created drives or recent interview activity. Large drive datasets may require additional processing time before insights become available. |
| **Drive configuration errors or incomplete setup** | Review Drive settings to ensure all required fields are completed, including schedules, room assignments, and interviewer allocations. Incomplete drive configurations may prevent insights from generating. |
### **Additional Tips:**
* Refresh the Drive insights page multiple times if data appears stale or outdated, as real-time analytics update dynamically based on ongoing interview activity
* Cross-reference Drive insights with unified notification inbox and candidate profile dashboards to validate data accuracy across Workflow Tools modules.
* Contact Talview support with specific error messages, screenshots, and drive details (drive name, date created number of candidates) to expedite troubleshooting.
# Why is the interviewer not appearing in the drive even after being added?
Source: https://docs.talview.com/hiring-teams/recruiter/drives/diagnostics/why-is-the-interviewer-not-appearing-in-the-drive-even-after-being-added
When an interviewer is added to a drive but doesn't appear in the expected location, this issue typically stems from access permissions, synchronization delays, or configuration errors within the drive management system.
Resolving visibility issues quickly ensures seamless candidate flow and prevents scheduling disruptions.
## 🔎 Troubleshooting Common Issues
| **What Might Be Wrong** | **How to Fix It** |
| :-------------------------------------------------------------------------------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| The drive has not refreshed after the interviewer was added, causing a display lag in the system. | Refresh the drive page or close and reopen the drive pop-up window. Log out and log back in to force a system sync if the interviewer still doesn't appear. |
| The interviewer was added to a different room than expected within the multi-step workflow. | Navigate and check all rooms in the drive to confirm where the interviewer was assigned to. |
| Calendar synchronization conflicts or notification delivery failures prevented the interviewer from receiving their drive assignment details. | Resend the interviewer notification by removing and re-adding them to the drive. Confirm the interviewer's email address is correct |
| Browser cache or stored session data is preventing the updated interviewer list from displaying correctly. | Clear browser cache and cookies, then reload the drive management page. Try accessing the drive from a different browser or device to rule out local storage issues. |
### **Additional Tip:**
Proactively verify interviewer availability before adding them to drives by reviewing their calendar integration and confirming they've synced their availability with the platform's automated scheduling system.
# Recruiter FAQs - Drive Management
Source: https://docs.talview.com/hiring-teams/recruiter/drives/faqs/recruiter-faqs-drive-management
### Introduction
The **Drive Management Module** in Workflow Tools enables recruiters to manage high-volume or on-site interview events efficiently, often referred to as *drives*. Recruiters can coordinate candidates, interviewers, and rooms in real time, ensuring a smooth experience. This FAQ covers how to plan, schedule, monitor, and optimize drives using the platform.
### 1. Drive Planning & Scheduling
**Q1. How far in advance should I create and schedule a drive?**
It’s recommended to create a drive **3–5 days in advance**, depending on the interviewer and candidate availability.
This allows enough time for:
* Interviewer confirmations
* Candidate slot assignment and notifications
* Room allocation and conflict resolution
However, the system also supports **instant drives**, which can be created and launched on the same day if resources are available.
**Q2. How do I add or remove candidates from an active drive?**
You can manage candidates directly from the **Drive Details** page:
* To **add candidates**, share the registration link with them to register.
* To **remove candidates**, click on Cancel beside the slots.
Changes automatically update the drive schedule.
**Q3. Can candidates reschedule their own interview slots within a drive?**
Yes, candidates can modify their slot from the **slot confirmation email**.
Recruiters are notified instantly of any changes, and available time slots are updated dynamically within the drive dashboard.
If this setting is not enabled, recruiters can manually reschedule on behalf of the candidate.
**Q4. Can I pause or extend a drive if we need more interview time?**
* Pausing a drive is not possible.
* To extend a drive, click **Edit Drive** timing and adjust the end time.
All linked sessions and notifications will automatically adjust to the updated schedule.
***
### 2. Interviewer Management
**Q1. How do I reassign interviewers if someone drops out last minute?**
You can open the specific drive schedule, select the candidate’s interview slot, and use the **Reassign Interviewer** option. The system will suggest alternate available interviewers, and notifications will automatically be sent to both the candidate and the new interviewer.
**Q2. Can I bulk-add interviewers to multiple drives?**
Yes. Recruiters can add interviewers in bulk by selecting multiple drives and uploading a list of interviewer details. The system then assigns them based on availability and role requirements.
***
### 3. Room & Resource Availability
**Q1. Can I track room availability across drives?**
Yes. The drive management dashboard provides a **Room Availability View**, allowing recruiters to see which rooms are free, booked, or overbooked across all drives.
**Q2. What happens if a room is double-booked across drives?**
The system automatically flags double bookings. Recruiters can either reassign the session to another available room or adjust interview timings to resolve the conflict.
***
### 4. Drive Insights & Consolidated Reporting
**Q1. Where can I view consolidated insights across multiple drives?**
Recruiters can access the **Drive Insights Dashboard**, which consolidates metrics like:
* Number of candidates scheduled vs. completed interviews
* Interviewer utilization and dropouts
* Room usage and conflicts
* No-shows and completion rates
**Q2. Can I export the drive schedule to share with managers?**
Yes. Drive schedules can be exported in **Excel/CSV/PDF formats**. These exports include candidate schedules, interviewer allocations, room assignments, and status updates, making it easy to share with hiring managers.
***
### 5. Candidate & Interview Flow Tracking
**Q1. Can I track which candidates have checked in or completed their interviews during a drive?**
Yes. The drive dashboard provides **real-time candidate tracking** — showing who has checked in, who is waiting, who is in-progress, and who has completed interviews.
**Q2. What happens if a candidate misses their scheduled slot?**
The system marks it as a **candidate no-show**. Recruiters can reschedule the candidate within the same drive or reassign them to another available interviewer.
***
### 6. Notifications & Alerts
**Q1. Do recruiters get alerts for last-minute interviewer or room changes?**
Yes. The system notifies recruiters in real-time if an interviewer drops out, a room conflict arises, or a candidate has not shown up.
**Q2. Can notifications be sent to hiring managers for daily drive summaries?**
Yes. Managers can receive automated **daily summary notifications** with updates on progress, interviewer participation, and candidate completion rates.
***
# How to add a room within a drive?
Source: https://docs.talview.com/hiring-teams/recruiter/drives/how-tos/how-to-add-a-room-within-a-drive
This article guides you through the step-by-step process of adding a room in a drive:
## Step-by-Step Guide
### Step 1: Log in and access the drive
* Log-in to the platform using your *recruiter or master recruiter* credentials.
* Navigate to the "**Workflows**" section from the main dashboard and select the workflow related to your recruitment drive.
* Within that workflow, locate and click on "**Drive**".
* Select the date and time for which you wish to add a room, pop-up window will appear.
### Step 2: Open the drive to add a room
* In the pop-up window, click on "**Open Drive**".
* Then, click on "**Add Room**" located at right side of the page.
### Step 3: Configure the room addition
* You'll have the option to add a room for a specific interview step; you can also search for and select an interviewer from the drop-down menu.
* Click on "**Add Room**" after setting up the details for the new room.
### Step 4: Confirmation
* A confirmation message will pop up at the bottom right of the page, indicating the **successful addition of the room**.
> **Note:** Ensure the room is allocated to an appropriate interview step and matched with a suitable interviewer.
# How to add interviewers to a drive?
Source: https://docs.talview.com/hiring-teams/recruiter/drives/how-tos/how-to-add-interviewers-to-a-drive
Adding interviewers to a specific drive contributes to a smooth and efficient interviewing process.
Here’s how to add interviewers to a recruitment drive:
## Step-by-Step Guide
### Step 1: Log in and access the drive
* Log-in to the platform using your *recruiter or master recruiter* credentials.
* Navigate to the "**Workflows**" section from the main dashboard and select the workflow related to your recruitment drive.
* Once in the workflow, locate the "**Drive**" button and click on it.
* Identify and click on the specific date and time you want to manage within the drive; a pop-up window will appear.
### Step 2: Open drive to add an interviewer
* In the pop-up window, click on "**Open Drive**".
* Select the interview step you need to add an interviewer to by clicking on it.
### Step 3: Allocate interviewer
* After selecting the desired interview step, search for and select an interviewer from the drop-down menu. (This menu will display a list of available interviewers who can be allocated to the selected room or interview step)
* Once the interviewer is selected, they will automatically receive a notification via email about their addition to the drive. (This email will contain all the necessary details, including the date, time, and any specific instructions related to the interview process.)
> **Note:** You can only add interviewers who have evaluator access to the platform
# How to create a drive?
Source: https://docs.talview.com/hiring-teams/recruiter/drives/how-tos/how-to-create-a-drive
Talview's **Drive** feature allows recruiters and hiring managers to create focused virtual hiring events or assessment campaigns to streamline candidate evaluation. Using Talview’s integrated tools, you can set up a **Drive** to manage and assess multiple candidates efficiently.
This article guides you through the step-by-step process of creating a Drive using Talview's workflow tools.
## Step-by-Step Guide
### Step 1: Log in and Access Your Workflows
* Log-in to the platform using your *recruiter or master recruiter* credentials.
* You will land on the "**Workflows**" page, where all your workflows are conveniently listed.
* Find the "**Create a Drive**" button situated at the bottom of the candidate invite list within your desired workflow, to start setting up your new recruitment drive.
### Step 2: Configure the drive
* Click on "**Create a Drive**" button to open a side panel with various configuration options.
* Choose the appropriate **configurations** from the drop-down menus.
* Set the *date and time* duration of the interview drive.
* Set when and how often do you want the interview drive to *repeat. (Daily, only on weekdays, only on weekends or on alternate days.)*
* In the **Interview details**, mention the *duration* of each interview, Set the number of interview *rooms* to accommodate candidates, Select the *platform or location* for the interviews.
* Set the *time zone* for interviews.
* Click on the "**Create**" button to finalize the drive setup, after configuring the settings.
### Step 3: Share the drive
* A **QR code** and a **link** will be generated, once the drive is created.
* The QR code and the link can be shared with potential candidates to allow them to register for the drive.
# How to edit a drive day?
Source: https://docs.talview.com/hiring-teams/recruiter/drives/how-tos/how-to-edit-a-drive-day
This article explains how recruiters and master recruiters can edit scheduled interview time slots for a specific day within **Talview's Workflow Tools.** This flexibility accommodates last-minute scheduling changes, candidate availability conflicts, and resource adjustments, helping teams maintain an organized interview calendar while adapting to dynamic recruitment needs.
***
## Step-by-Step Guide
### **1. Navigate to the Recruitment Drive**
* **Log in** with your recruiter or master recruiter account.
* From the dashboard, select **Workflows**.
* Choose the workflow containing the recruitment drive you want to modify.
* Click the **Drive** button located at the top of the candidate invite list.
### **2. Select the date to edit**
* Click on the date you wish to edit from the drive schedule.
* A pop-up window will appear for the selected date.
> **Note:** Only dates that have already been scheduled for the drive can be edited.
### **3. Edit the day's details**
* In the pop-up window, navigate to the top right and click on "**Edit**."
* Modify the time slot by selecting a new option from the calendar provided.
* After making your adjustments, click on "**Save Changes**" to update the day's schedule.
### **4. Confirmation**
* Once the changes are saved, the pop-up window will close, and a confirmation message will be displayed at the bottom right of the page, indicating the **successful editing of the drive**.
* The modifications to the specific day's drive are now updated and reflected within the overall drive schedule.
> It's crucial to promptly communicate any changes to the affected candidates to ensure they are aware of the new schedule. This helps in maintaining a smooth and efficient recruitment process, minimizing any potential inconvenience.
### **Tips for efficient drive management:**
* Edit drive dates at least 24-48 hours in advance, to give candidates adequate notice.
* Only scheduled dates can be edited; you cannot modify dates that haven't been added to the drive yet.
* Use the Arcade demo walkthrough above if you need visual guidance through the editing process.
# How to edit a drive series?
Source: https://docs.talview.com/hiring-teams/recruiter/drives/how-tos/how-to-edit-a-drive-series
Editing a recruitment drive allows recruiters or master recruiters to update crucial details such as *the drive's date or time slot*. This is to ensure that the recruitment drive perfectly aligns with the *organization's scheduling needs and candidate availability*.
This article guides you through the step-by-step process of editing a Drive series:
## Step-by-Step Guide
### **Step 1: Log in and access the drive**
* Log-in to the platform using your *recruiter or master recruiter* credentials.
* Navigate to the "**Workflows**" section from the main dashboard and select the workflow you're interested in.
* Locate and click on the "**Drive**" button, at the top of the candidate invite list.
### Step 2: **Edit drive details**
* Scroll down to the bottom of the page and click on "**Details**" to access the drive's settings.
* Click on "**Edit** 📝" icon to edit the **drive date and time slot** by selecting new options from the calendar.
### **Step 3: Save Changes**
* Once you have made the desired changes, click on "**Save Changes**" to update the drive details.
* The side panel will close, and a confirmation message will appear at the bottom right of the page, indicating the **successful editing of the drive.**
> **Note:** Edits to the recruitment drive can only be made if the drive has not started or is not completed. Ensure all changes are finalized before the drive's scheduled start time to avoid any disruptions in the recruitment process.
# How to remove a room from a drive?
Source: https://docs.talview.com/hiring-teams/recruiter/drives/how-tos/how-to-remove-a-room-from-a-drive
Removing interview rooms from a recruitment drive is a necessary task when adjusting the logistics of interview schedules.
Here’s a detailed guide on how to remove a room from a recruitment drive:
## Step-by-Step Guide
### Step 1: Log in and access the drive
* Log-in to the platform using your *recruiter or master recruiter* credentials.
* Navigate to the "**Workflows**" section from the main dashboard and select the workflow related to your recruitment drive.
* Within that workflow, locate and click on "**Drive**".
* Choose the date for which you wish to remove a room, a detailed window for that date will appear.
### Step 2: Open the drive and locate the room
* In the pop-up window, click on "**Open Drive**".
* Find the room you intend to remove.
* Next to the room's name, you will see a **"-"** symbol, indicating the option to remove the room.
### Step 3: Confirm the removal of the room
* A confirmation pop-up window will appear, asking you to confirm your decision.
* Click "**Confirm**" to proceed with the removal of the room.
### Step 4: Confirmation
* After confirming, the pop-up window will close, and a message will appear at the bottom right of the page, indicating the **successful removal of the room**.
> **Note:** Before removing a room, ensure that no interviews are scheduled within it. Removing a room with scheduled interviews could disrupt the interview process for both candidates and interviewers.
# How to remove an interviewer from a drive?
Source: https://docs.talview.com/hiring-teams/recruiter/drives/how-tos/how-to-remove-an-interviewer-from-a-drive
Here’s a detailed guide on how to remove a room from a recruitment drive:
## Step-by-Step Guide
### Step 1: Log in and access the drive
* Log-in to the platform using your *recruiter or master recruiter* credentials.
* Navigate to the "**Workflows**" section from the main dashboard and select the workflow related to your recruitment drive.
* Within that workflow, locate and click on "**Drive**".
* Choose the date for which you wish to remove an interviewer, a detailed window for that date will appear.
### Step 2: Open drive and select the interviewer
* In the pop-up window, click on "**Open Drive**".
* Proceed to click on the name of the interviewer you wish to remove.
### Step 3: Remove the interviewer and confirmation
* To **remove** an interviewer, click the “✖️” icon next to their name
* Click on “**Remove.”**
* Upon confirmation, a message will appear at the bottom right of the page, confirming the **successful replacement of the interviewer**.
# How to replace an interviewer in a drive?
Source: https://docs.talview.com/hiring-teams/recruiter/drives/how-tos/how-to-replace-an-interviewer-in-a-drive
This article guides you through the step-by-step process of replacing an interviewer in a drive:
## Step-by-Step Guide
### **Step 1: Log in and access the drive**
* Sign in with your recruiter or master recruiter credentials.
* Navigate to the "**Workflows**" section from the main dashboard and select the workflow related to your recruitment drive.
* Within that workflow, locate and click on "**Drive**".
* Select the date and time for which you wish to add a room, pop-up window will appear.
### **Step 2: Open drive and select the interviewer**
* In the pop-up window, click on "**Open Drive**".
* Proceed to click on the name of the interviewer you wish to replace.
### **Step 3: Replace the interviewer**
* Click on "**Replace**".
* Select a new interviewer from the drop-down menu. (This menu will list available interviewers suitable for the interview step.)
* After selecting the replacement interviewer, click on "**Confirm**" to finalize the process.
### **Step 4: Confirmation**
* Upon confirmation, a message will appear at the bottom right of the page, confirming the **successful replacement of the interviewer**.
# How to view drive details?
Source: https://docs.talview.com/hiring-teams/recruiter/drives/how-tos/how-to-view-drive-details
This article guides you through the step-by-step process of viewing drive details.
## Step-by-Step Guide
### **Step 1: Log in and access the drive**
* Log-in to the platform using your *recruiter or master recruiter* credentials.
* Navigate to the "**Workflows**" section from the main dashboard and select the workflow related to your recruitment drive.
### Step 2: Viewing **drive details**
* Locate and click on "**Details**" to access the drive's settings.
* Scroll down to the bottom of the page where you will find the **"Details"** option.
* Click on "**Details**" to open a side panel that will display drive details such scheduled date, time, rooms, QR code and link.
# How to view drive insights?
Source: https://docs.talview.com/hiring-teams/recruiter/drives/how-tos/how-to-view-drive-insights
Gaining insights into various metrics and data points related to the recruitment drive is crucial and effective. Here's a Step-by-step guide on how to access these insights:
## Step-by-Step guide
### Step 1: Log in and access the drive
* Log-in to the platform using your *recruiter or master recruiter* credentials.
* Navigate to the "**Workflows**" section from the main dashboard and select the workflow you're interested in.
### Step 2: Viewing drive insights
* Locate and click on "**Details**" to access the drive's settings.
* Scroll down to the bottom of the page where you will find the "**Insights**" option.
* Click on "**Insights**" to open a side panel that will display various metrics and data points related to the recruitment drive.
### Step 3: Review insights
* Utilize these insights to evaluate the success of the drive and to inform future recruitment strategies.
# Why am I not receiving email, SMS, or call notifications in my Notification Inbox?
Source: https://docs.talview.com/hiring-teams/recruiter/notification-inbox/diagnostics/why-am-i-not-receiving-email-sms-or-call-notifications-in-my-notification-inbox
Recruiters using Talview’s Workflow Tools Notification Inbox may occasionally encounter issues where email, SMS, or call notifications do not appear as expected.
This article helps recruiters identify the causes for notification delivery problems and provides proven steps to resolve them efficiently.
## 🔎 Troubleshooting Common Issues
| **What might be wrong** | **How to fix it** |
| :---------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------- |
| Email/SMS provider or firewall is blocking messages | Check organizational security/firewall and whitelist Talview domains or ask IT to allow notification traffic. |
| Email/SMS/call delivery failures (bounced, rejected, or filtered) | Review spam or junk folders and email logs; correct any detected blocks or errors. |
| Using an unsupported browser or device | Use a supported browser (Chrome, Edge, Firefox) and keep it updated; try incognito/private mode for troubleshooting. |
| Browser cache or cookies causing interface issues | Clear browser cache and cookies, then restart the browser and re-login to Talview. |
### **Additional Tips:**
* Update browser and device software frequently to maintain compatibility and security.
* Regularly verify notification preferences after system updates or changes in device/browser.
* If no notifications arrive, escalate to Talview support with error screenshots/logs.
# Why am I receiving duplicate notifications for the same event?
Source: https://docs.talview.com/hiring-teams/recruiter/notification-inbox/diagnostics/why-am-i-receiving-duplicate-notifications-for-the-same-event
Multiple notifications for the same event in the Notification Inbox, can clutter your workflow and make it harder to track important updates. Duplicate notifications typically occur due to system sync issues, multiple triggers firing simultaneously, or configuration overlaps in your notification settings.
This article helps you identify why duplicate notifications appear and provides clear steps to resolve the issue so you can maintain a clean, organized inbox.
## 🔎 Troubleshooting Common Issues
| **What Might Be Wrong** | **How to Fix It** |
| :----------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Browser cache is causing notifications to display twice | Clear your browser cache and cookies, then refresh the page. For persistent issues, try accessing Talview in an incognito/private browsing window. |
| System sync delay is creating duplicate entries | Wait 2-3 minutes and refresh your inbox. If duplicates persist, log out completely and log back in to force a fresh sync. |
| You're logged into multiple devices or browser tabs simultaneously | Close all other active Talview sessions. Keep only one active session open to prevent notification duplication across devices. |
| Notification webhook is firing multiple times | Contact your Talview administrator to review webhook configurations and ensure events are only triggering once. |
| Email forwarding rules are creating duplicate notifications | Check if you have email-to-notification forwarding enabled while also receiving in-app notifications for the same events. Disable one channel. |
### **Additional Tips:**
* **Mark duplicates as read** in bulk to quickly clear your inbox without losing track of the original notification you need to act on
* **Use the search function** to check if you've already received a notification before responding to what appears to be a duplicate
# Why are notification escalation messages not triggering?
Source: https://docs.talview.com/hiring-teams/recruiter/notification-inbox/diagnostics/why-are-notification-escalation-messages-not-triggering
Notification escalation messages are critical reminders that keep recruitment workflows on track by alerting recruiters about no-shows, pending actions, and time-sensitive tasks. When these automated reminders fail to trigger, it can lead to missed follow-ups, delayed hiring decisions, and poor candidate experience.
This article helps recruiters troubleshoot and resolve issues when notification escalation messages fail to trigger in **Talview's Notification Inbox.**
## 🔎 Troubleshooting Common Issues
| **What might be wrong** | **How to fix it** |
| :---------------------------- | :----------------------------------------------------------------------------------------------------------------------------------- |
| Incorrect time zone settings | Review the time zone configuration in Profile Settings to ensure escalation timings align with your operational hours. |
| Email notifications blocked | Check your email spam/junk folder and add Talview's notification domain to your safe senders list. |
| Escalation conditions not met | Review the escalation rule conditions (e.g., "24 hours after no response") to ensure the triggering criteria have actually been met. |
| System cache issues | Clear your browser cache and cookies, then log out and log back in to refresh notification settings. |
### **Additional Tip**
Test escalation rules using a dummy workflow to verify they're functioning before applying them to live recruitment processes.
# Why are notification messages grouped under the wrong candidate or interviewer?
Source: https://docs.talview.com/hiring-teams/recruiter/notification-inbox/diagnostics/why-are-notification-messages-grouped-under-the-wrong-candidate-or-interviewer
When messages are grouped under the wrong candidate or interviewer, this can disrupt recruitment workflows, create confusion, and hinder timely follow-ups in Talview’s Notification Inbox.
This article helps recruiters identify the causes and resolve issues when notifications or conversation threads appear under incorrect profiles, ensuring cleaner communication and accurate tracking.
## 🔎 Troubleshooting Common Issues
| **What might be wrong** | **How to fix it** |
| :--------------------------------------------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------- |
| Candidate/interviewer profiles have similar or duplicate email addresses, resulting in thread misalignment | Verify and update candidate/interviewer emails from the workflow's candidate details panel; avoid duplicates. |
| Interviewer/candidate names edited post-scheduling, but notifications still link to original name/email | Double-check name/email fields and request support for notification thread re-mapping if edits were recent |
| Users are responding from shared or alias emails, merging thread associations | Use only assigned, verified emails for responses; disable alias or shared inbox features during event workflow |
### **Additional Tips:**
* Reassign interview notifications by editing candidate or interviewer panel details, then refresh the Notification Inbox to sync updated threads.
* Check the notification permissions and ensure recruiters are logged in with their dedicated email accounts, shared logins can cause thread mix-ups.
# Why are notifications not appearing in my Notification Inbox?
Source: https://docs.talview.com/hiring-teams/recruiter/notification-inbox/diagnostics/why-are-notifications-not-appearing-in-my-notification-inbox
When notifications are missing from the Talview Notification Inbox in Workflow Tools, it disrupts recruiter workflows and response times for virtual hiring events.
This article helps recruiters systematically diagnose common causes behind missing notifications and offers actionable fixes to restore seamless communication.
## 🔎 Troubleshooting Common Issues
| **What might be wrong** | **How to fix it** |
| :-------------------------------------------- | :------------------------------------------------------------------------------------------------- |
| Browser cache/cookies are outdated | Clear cache and cookies from browser settings and restart the browser. |
| Tab or pop-up blockers restrict notifications | Disable browser extensions (ad blockers, script blockers) that might prevent notification display. |
| Email notifications missed (not in inbox) | Check the spam/promotions folder; add Talview notifications to email whitelist. |
| Internet connectivity is unstable | Ensure a stable internet connection for timely syncing of notifications. |
### **Additional Tips:**
* Refresh the **Notification Inbox** page regularly to see the latest updates.
* When in doubt, log out and log back into Talview to reset notification channels.
* If the issue still persists, contact Talview Support with screenshots.
# Why can’t I reply to or forward messages in the Notification Inbox?
Source: https://docs.talview.com/hiring-teams/recruiter/notification-inbox/diagnostics/why-cant-i-reply-to-or-forward-messages-in-the-notification-inbox
Recruiters sometimes encounter issues where they are unable to reply or forward notifications directly from within the Talview Notification Inbox, especially when managing multiple candidate communications.
This article helps recruiters diagnose common causes and offers actionable solutions to restore and streamline inbox functionality.
## 🔎 Troubleshooting Common Issues
| **What Might Be Wrong** | **How to Fix It** |
| :----------------------------------------------------- | :--------------------------------------------------------------------------------------------------------------------- |
| The inbox UI is frozen or not loading new content | Refresh the browser tab or log out and back in; clear cache and disable browser extensions that may interfere. |
| Outdated browser or unsupported device | Update to the latest version of Chrome or Edge and use desktop whenever possible for full inbox functionality. |
| Network issues or VPN blocks | Test connectivity outside VPN; whitelist Talview platform domains or try a different network. |
| Notification Inbox undergoing maintenance or bug fixes | Refer to Talview release notes or status page for known issues or maintenance schedules and wait for platform updates. |
### **Additional Tips:**
* Always check whether notifications are grouped; some system alerts may be consolidated, making individual replies impossible, refer to grouped alert counts before attempting a reply.
* Use manual outreach (email, WhatsApp, phone) when system generated notifications do not support replies or forwards.
# Why is search not working in the Notification Inbox?
Source: https://docs.talview.com/hiring-teams/recruiter/notification-inbox/diagnostics/why-is-search-not-working-in-the-notification-inbox
When recruiters encounter problems with the search function in the Talview Notification Inbox, it can disrupt candidate tracking and workflow efficiency. This article helps recruiters diagnose why search may not be working and provides actionable solutions for each issue.
## 🔎 Troubleshooting Common Issues
| **What might be wrong** | **How to fix it** |
| :---------------------------------------------------------- | :----------------------------------------------------------------------------- |
| Search term spelling or case mismatch | Double-check search spelling, use correct capitalization, and partial keywords |
| Search index not refreshed after new data entry | Refresh the inbox manually before searching |
| Candidate notifications not loaded in inbox | Reload the page, or try accessing via different device/browser |
| Outdated browser or unsupported browser version | Update browser to latest supported version (prefer Chrome, Edge, Firefox) |
| Browser extensions (ad blockers, privacy tools) interfering | Disable browser extensions and refresh the inbox |
| Browser caching causing outdated results | Clear browser cache and cookies, then refresh and retry |
### **Additional Tips:**
* Ensure you are not logged in simultaneously on multiple devices, as this may impact real-time inbox updates or filter performance.
* Consult Talview’s Help Center for step-by-step guides or troubleshooting diagnostics to resolve advanced issues.
* If multiple users experience the issue, escalate to IT or Talview support for service-level investigation
# Why is there a delay in receiving candidate or interviewer notifications?
Source: https://docs.talview.com/hiring-teams/recruiter/notification-inbox/diagnostics/why-is-there-a-delay-in-receiving-candidate-or-interviewer-notifications
Delay in receiving candidate or interviewer notifications within Talview’s Notification Inbox can be a critical workflow bottleneck for recruiters, affecting coordination, candidate experience, and interview outcomes.
This article helps recruiters diagnose and resolve issues related to notification delays in Talview’s Workflow Tools.
## 🔎 Troubleshooting Common Issues
| **What might be wrong** | **How to fix it** |
| :------------------------------------------------- | :---------------------------------------------------------------------------------------- |
| Inbox clutter due to grouped or bulk notifications | Use “Mark as Read/Unread”, “Reply”, or “Forward” tools to clear or monitor crucial alerts |
| Slow network or system connectivity | Ensure stable internet connectivity and refresh or restart device if delays persist |
| Notification mailbox sync issues | Log out and sign in again or clear cache to force mailbox resync |
### **Additional Tips:**
* Refresh the Notification Inbox regularly; recent enhancements allow faster reading, forwarding, and action on notifications.
* Ensure strong internet connectivity, especially during real-time virtual hiring events to avoid delays in message receipt.
* If notifications still don’t arrive after standard troubleshooting, contact Talview Support for deeper technical diagnosis.
# Recruiter FAQs - Notification Inbox
Source: https://docs.talview.com/hiring-teams/recruiter/notification-inbox/faqs/recruiter-faqs-notification-inbox
### **1. Notification Tracking & Status**
**Q1. What types of notifications are tracked in the Notification Inbox?**
The Notification Inbox tracks **Email, SMS, and Call** notifications sent to the candidates and interviewers from the platform.
**Q2. Can I filter notifications by status or type?**
Yes. You can filter notifications by **channel (Email/SMS/Call)**, **status (Delivered, Read, Bounced, Pending)**, **candidate name**, and **date range** for precise tracking.
**Q3. How can I view the history of a specific notification?**
Click on a notification to open its **detailed view**, which shows the **entire message thread**, including previous sends, replies, and any delivery status changes.
**Q4. How long are notification logs retained?**
Notification logs are retained for **12 months** by default. However, the retention period may vary based on your **tenant’s data retention policy**.
***
### **2. Candidate & Interviewer Communication**
**Q5. Can I reply to a notification directly from the Inbox?**
Yes. Recruiters can reply to email notifications directly. Replies are logged against the candidate’s record.
**Q6. Can I forward a notification to another user?**
Yes. Use the **Forward** option to send the original message to another team member with context.
**Q7. Can I mark a notification as unread after reading it?**
Yes. Notifications can be toggled between **Read** and **Unread** for better tracking.
***
### **3. Email-Specific Questions**
**Q8. Are attachments supported in emails?**
Yes. However, the same cannot be viewed in the inbox view.
**Q9. What do the different email statuses mean?**
* **Sent:** The email was successfully sent from the platform.
* **Delivered:** The email was accepted by the recipient’s mail server.
* **Read:** The recipient opened the email.
* **Bounced:** The email couldn’t be delivered (e.g., invalid address, full inbox, blocked domain).
* **Failed:** The system couldn’t send the message due to a configuration or network error.
* **Queued**: The email is currently in the queue and waiting to be sent from Talview.
**Q10. Why is an email showing as “Bounced”?**
Bounces occur due to invalid email addresses, full inboxes, or blocked domains. Verify and update the candidate’s email before retrying.
**Q11. Can I see when a candidate opened my email?**
Yes. Emails marked as **Read** indicate that the candidate opened the message.
***
### **4. SMS-Specific Questions**
**Q12. How do I know if an SMS was delivered?**
Each SMS notification displays a **Delivery Status -** such as *Delivered*, *Failed*, or Queued. A *Delivered* status confirms the message reached the candidate’s device.
**Q13. What are SMS character limits?**
A single SMS supports up to **160 characters**. Longer messages are automatically split into multiple parts but will appear as one continuous message to the recipient.
**Q14. Why might an SMS fail to deliver?**
SMS delivery can fail due to **invalid numbers**, **carrier restrictions**, or the candidate’s phone being **switched off or out of network range**.
**Q15. Why does my SMS show as “Delivered” but the candidate hasn’t responded?**
“Delivered” confirms that the SMS reached the candidate’s device, but a response depends on the candidate choosing to reply.
**Q16. Can I see the candidate’s SMS reply in the Inbox?**
Yes. SMS replies appear as part of the same conversation thread for that candidate, maintaining full communication context.
***
### **5. Call-Specific Questions**
**Q17. What call types are supported?**
The platform supports **Outbound Voice** calls initiated by the recruiter.
**Q18. Why did a call fail to connect?**
Calls may fail due to **unreachable numbers**, **network errors**, **candidate rejection**, or **IVR configuration issues**.
**Q19. Are calls logged in the Notification Inbox?**
Yes. All inbound and outbound calls made through the system are logged for tracking.
**Q20. Can I listen to recorded calls?**
Yes, recordings can be played when you expand the calls card.
***
### **6. Bulk Actions & Efficiency**
**Q21. Can I mark multiple notifications as read/unread?**
Yes. Select multiple notifications and apply the **Mark as Read/Unread** action in bulk.
**Q22. Can I export notification logs for reporting?**
Yes. Recruiters can export notifications with their statuses (Delivered, Read, Bounced, etc.) for auditing or sharing with stakeholders.
***
### **7. Troubleshooting & Best Practices**
**Q23. Candidate didn’t receive a notification - what should I check first?**
* Confirm the **candidate’s contact information** (email/phone number) is correct.
* Check if the **notification was sent successfully** and its **status**.
* Ensure the candidate’s **email domain or number** isn’t blocked or unsubscribed.
**Q24. Why is an email marked as bounced but the address looks correct?**
This can happen due to temporary issues like the recipient’s inbox being full or the domain server rejecting the email. Retry after a few hours or contact your IT admin.
**Q25. What should I do if a notification keeps bouncing?**
Verify the contact details and communication channel. If the issue persists after updating, escalate to your system administrator for further investigation.
**Q26. Why don’t I see a candidate’s response in the Inbox?**
Check if the candidate replied from the same channel and address (e.g., replying from a different email ID or phone number might not sync automatically).
***
# How to check notifications in Notification Inbox?
Source: https://docs.talview.com/hiring-teams/recruiter/notification-inbox/how-tos/how-to-check-notifications-in-notification-inbox
This article provides a step-by-step guide to help users access and check notifications from the *Notification Inbox* within **Talview's Workflow Tools Platform**. This feature allows you to stay updated on important workflow activities, candidate interviews, and assessments efficiently.
***
## Steps to check for notifications
### **Step 1: Login to Talview’s Workflow Tools Platform**
* Navigate to the Workflow Tools login portal and login as a recruiter.
* Upon successful authentication, you will be redirected to the **Workflow Tools dashboard.**
### **Step 2: Navigate to the Notification Inbox**
* On the navigation bar, locate the **Inbox** icon.
* Click on this **Inbox** icon to open your Notification Inbox.
### Step 3: **View the List of Notifications**
* The Inbox view is split into two sections:
* **Left Pane:** List of mail notifications
* **Right Pane:** Detailed view of the selected notification thread.
* New or unread notifications will be marked with a blue dot 🔵 for easy identification.
* Scroll through the left pane to browse your notifications.
### **Step 4: Select a Notification to Read**
* Click on any notification item in the left pane to open its contents on the right pane.
* You can scroll through the message content to read all details of the notification.
### **Step 5: Use Search or Filters**
* To quickly find a notification, use the **Search Inbox** bar located at the top-right of the Inbox page.
* Type keywords such as *candidate names, workflow titles, or dates* to filter notifications.
# How to forward a notification in Notification Inbox?
Source: https://docs.talview.com/hiring-teams/recruiter/notification-inbox/how-tos/how-to-forward-a-notification-in-notification-inbox
This article provides a step-by-step guide on how to forward a notification mail within Talview's Workflow Tools Platform. Forwarding notification mails can help you keep relevant stakeholders informed or escalate issues quickly.
***
## Prerequisites
* An active email account configured to receive Talview notification mails.
* Basic understanding of workflow tasks assigned in *Talview’s platform*.
* Access to **Talview’s Workflow Tools Platform** for task verification and follow-up.
***
## Steps to Forward a Notification Mail
### **Step 1: Login to Talview’s Workflow Tools Platform**
* Navigate to the Workflow Tools login portal.
* Locate the login form on the main page and complete the authentication process.
* Upon successful authentication, you will be redirected to the **Workflow Tools dashboard.**
### **Step 2: Navigate to the Notification Inbox**
* On the navigation bar, locate the **Inbox** icon.
* Click on this **Inbox** icon to open your Notification Inbox.
### Step 3: **Select a Notification to Read**
* Click on any notification item in the left pane to open its contents on the right panel.
* You can scroll through the message content to read all details of the notification.
### Step 4: Forwarding a notification
* Select the mail you want to forward.
* Click on the **Forward Icon (Arrow pointing towards the right)**.
* Enter the recipient’s mail address correctly, then click on **Send.**
* You will receive a notification - ***“Message forwarded successfully.”***
# How to mark a notification as read or unread in Notification Inbox
Source: https://docs.talview.com/hiring-teams/recruiter/notification-inbox/how-tos/how-to-mark-a-notification-as-read-or-unread-in-notification-inbox
This article provides a step-by-step guide on how to mark notifications as read or unread within Talview's Workflow Tools Platform. Managing your notifications helps you stay organized and ensures you don't miss important updates.
***
## **Prerequisites**
* An active email account configured to receive Talview notification mails.
* Basic understanding of workflow tasks assigned in *Talview’s platform*.
* Access to **Talview’s Workflow Tools Platform** for task verification and follow-up.
***
## Step-by-Step Guide:
## Marking a Notification as Read:
### **Step 1: Login to Talview’s Workflow Tools Platform**
* Navigate to the Workflow Tools login portal.
* Locate the login form on the main page and complete the authentication process.
* Upon successful authentication, you will be redirected to the **Workflow Tools dashboard.**
### **Step 2: Navigate to the Notification Inbox**
* On the navigation bar, locate the **Inbox** icon.
* Click on this **Inbox** icon to open your Notification Inbox.
### Step 3: **Select a Notification to Read**
* Click on the notification item in the left panel to open its contents on the right panel.
* When you select a notification to go through, this marks it as **read.** Now you can see the **Dark blue dot** 🔵 disappear.
## Marking a Notification as Unread:
### Step 1: **Navigate to the Notification Inbox**
* On the navigation bar, locate the **Inbox** icon.
* Click on this **Inbox** icon to open your Notification Inbox.
### Step 2: **Select a Notification to mark as unread**
* Click on the notification item in the left panel to open its contents on the right panel.
* If you want the notification to be kept as unread, click on the **Envelope Icon** ✉️, the notification goes back to being **unread** and the **dark blue dot** 🔵 reappears.
* Clicking the Envelope ✉️ button, will mark a notification as read and unread both.
# How to reply to a notification in Notification Inbox?
Source: https://docs.talview.com/hiring-teams/recruiter/notification-inbox/how-tos/how-to-reply-to-a-notification-in-notification-inbox
This article guides you step-by-step on how to reply to a notification mail using Talview’s Workflow Tools Platform. The process leverages Talview’s automated workflow to streamline communication directly from email notifications triggered by the system.
***
## Prerequisites
* An active email account configured to receive Talview notification mails
* Basic understanding of workflow tasks assigned in *Talview’s platform*.
* Access to **Talview’s Workflow Tools Platform** for task verification and follow-up.
***
## Step-by-Step Guide:
### **1. Check Status in the Table View**
* Login as a recruiter and select the workflow and open the **Interview step**.
* In the table view, look at the candidate and interviewer attendance by hovering on the avatars against them. Their status will display as:
* **Not joined** – The participant has not joined the interview room.
* **Joined** – The participant is currently in the interview room.
* **No Show** – The participant did not join during the interview window.
### **2. View Status in the Side Panel**
* Click on the interview card for any candidate.
* In the side panel, you’ll see the same join statuses (*Yet to Join, Joined, No Show*) for both the candidate and interviewer.
### **3. Recruiter Escalation Email**
* If either the candidate or the interviewer has joined but is waiting alone for more than **5 minutes after the interview start time**, the system automatically sends an **escalation email**.
* This email is sent to the **interview organizer (recruiter)** to notify them of the delay so they can take corrective action.
Checking **join statuses** in real time helps recruiters proactively step in. \
If you receive an escalation email, follow up quickly with the participant who hasn’t joined to prevent interview cancellations or extended waiting times.
# How do Automated No-show Notifications work
Source: https://docs.talview.com/hiring-teams/recruiter/scheduling-and-interviews/how-tos/how-do-automated-no-show-notifications-work
Automated no-show notifications in **Live Interviews** proactively alert recruiters and organizers when candidates or interviewers fail to join a scheduled session. These notifications help reduce disruptions and ensure smooth management of interview workflows.
***
## How Automated No-Show Notifications Work?
* If only one or no participants join an Interview Room within the first **5 minutes**, Talview automatically sends a **“Possible No-Show”** email alert to the recruiter or organizer.
* Candidates and interviewers receive **multi-channel reminders** (email, SMS, push notifications) before the session to minimize no-shows.
* Recruiters can monitor **real-time status updates** in the Interview Room dashboard to track attendance.
***
## What Actions to Take After a No-Show?
* Review the **“Possible No-Show”** alert and confirm attendance in the dashboard.
* Reach out to the absent participant using Talview’s communication tools, email, or phone.
* Decide whether to **reschedule or move forward** with other candidates based on company policy.
* Use Talview’s **rescheduling flows** to offer new timeslots quickly.
* **Document the no-show** in the system for compliance and reporting.
***
## Best Practices to Minimize No-Shows
* Enable **multi-channel reminders** (email, SMS, calendar, IVR).
* Allow **self-scheduling and real-time slot selection** to improve commitment.
* Include **pre-interview instructions** and readiness checks in reminder notifications.
* Track **engagement analytics** to identify and follow up with candidates at risk of no-show.
# How do Recruiters initiate self-scheduling
Source: https://docs.talview.com/hiring-teams/recruiter/scheduling-and-interviews/how-tos/how-do-recruiters-initiate-self-scheduling
Self-scheduling involves the recruiter designating candidates and interviewers, while leaving the decision of the interview time to the candidates, who may select their preferred times based on the availability of the interviewers.
## Steps involved in Self-Scheduling
### 1. Access the workflow dashboard
* Navigate to the **Workflows** section from the side navigation panel.
* Select the workflow for which you want to schedule interviews.
### 2. Schedule an interview
* Select a candidate from the list or click on **"Schedule"** to upload new candidates.
* Click **“Schedule**” button to start organizing interviews for your workflow.
* Assign an **Interviewer (Evaluator)** from the existing list of evaluators.
### 3. Initiate Self-schedule
* Initiate *self-scheduling* for the interview - **no need to select a specific time.**
* Click on **"Schedule".**
### 4. Viewing the scheduled interview
* Click on the **interview step** for which the self-scheduling was initiated.
* To check the schedules initiated, Click on **"View".**
# How to cancel an Interview
Source: https://docs.talview.com/hiring-teams/recruiter/scheduling-and-interviews/how-tos/how-to-cancel-an-interview
This article explains how **Recruiters** and **Master Recruiters** can cancel scheduled interviews in Talview’s Workflow Tools platform. You can cancel interviews either **individually** or **in bulk**, ensuring minimal disruption for both interviewers and candidates. Once cancelled, all participants receive automatic email notifications.
## Step-by-step Guide:
### ***Cancel Interviews in Bulk***
Follow these steps to cancel multiple interviews at once.
### 1. Access the Workflow
* Log in to your Talview account as a **Recruiter** or **Master Recruiter**.
* From the main menu, go to **Workflows**.
* Select the workflow that contains the interviews you want to cancel.
* Navigate to the **Interview Stage** to view the candidate list.
* Select the candidates whose interviews should be cancelled.
* Click the **More (⋮)** menu and choose **Cancel**.
### 2. Confirm Cancellation
* In the confirmation pop-up, click **Yes** to proceed.
* A confirmation message appears once the cancellation is complete.
* **Refresh the page** to verify that the interviews have been cancelled.
* All participants (interviewers and candidates) will be notified via email.
### ***Cancel Individual Interviews***
Follow these steps to cancel a single scheduled interview.
### 1. Access the Workflow
* Log in to your Talview account.
* Navigate to **Workflows** and select the relevant workflow.
* Go to the **Interview Stage**.
* Locate the candidate whose interview you wish to cancel.
* Click the **More (⋮)** icon next to their name and select **Cancel**.
* Alternatively, use the **three dots** beside the **Invite** button and choose **Cancel**.
### Step 2: Confirm Cancellation
* Click **Yes** in the confirmation pop-up.
* A success message appears once the interview is cancelled.
* **Refresh the workflow page** to reflect the update.
* Both the candidate and the interviewer will receive a cancellation email notification.
> Only interviews that are **active** (not completed or previously cancelled) can be cancelled.
# How to create a Workflow and Schedule a Live Interview
Source: https://docs.talview.com/hiring-teams/recruiter/scheduling-and-interviews/how-tos/how-to-create-a-workflow-and-schedule-a-live-interview
**Talview Interview Rooms** is a secure, proctored online interviewing platform designed to streamline the recruitment process by enabling recruiters and hiring teams to schedule, conduct, and manage interviews remotely with ease.
To schedule interviews efficiently in Talview Interview Rooms, from basic setup to advanced proctoring configuration, recruiters can follow a structured workflow that streamlines the entire process and leverages Talview’s intelligent scheduling capabilities. Here is a refined, complete scheduling workflow and best practices guide:
***
## Prerequisites
Before beginning, ensure the following are available:
* Active Talview Recruiter Platform account
* Interview scheduling permissions enabled
* Candidate contact information
* Panel member availability confirmed
***
## What is Talview Interview Rooms?
Talview Interview Rooms is a secure, AI-powered interview platform that enables interview management with advanced proctoring features including face authentication, room scanning, and real-time monitoring.
**Key Benefits include:**
* Streamlined scheduling process
* Built-in security and proctoring
* Automated candidate communications
* Multi-interviewer panel support
***
## Setting Up Interviews Using Workflow Tools
1. **Access Workflow Tools**
* Log in to the Talview Recruiter Platform
* Navigate to **More Apps** > **Workflow Tools**
2. **Create a New Workflow**
* Click on **Create Workflow** to begin
* Review and select from available job role templates
3. **Invite Candidates to the Workflow**
* Select the type of workflow and step from the dropdown
* Use **Add Candidates** to manually invite individuals
* Click **Add and Continue** to proceed
* Send invitations to initiate the workflow process
4. **Manage Candidate Progress**
* Monitor updates and select candidates for further actions
* Schedule the next steps directly within the workflow
5. **Schedule Interviews within Workflow**
* Select the **Interview Provider** (e.g., Interview Rooms)
* Choose the appropriate **Interview Stage**
* Select an **Interviewer** from the dropdown
* Finalize the schedule and confirm with all participants
***
## Detailed Interview Configuration (Interview Rooms)
| Field | Description | Best Practice |
| :-------------- | :---------------------------- | :----------------------------------------------- |
| **Date & Time** | When the interview will occur | Consider candidate's time zone and working hours |
| **Duration** | Length of interview | Add 15-minute buffer for technical setup |
| **Time Zone** | Candidate's local time zone | Always confirm with candidate beforehand |
1. **Add Candidate Information**
* For single candidates: Enter full name and verify email address
* For multiple candidates: Use bulk CSV upload using the provided template
2. **Configure the Interviewers.**
* Add panel members by email
* Assign roles: master recruiter, recruiter, evaluator, interviewer
* Confirm availability before scheduling
3. **Send the Interview Invitation**
* Choose to send immediately, schedule delivery, or save as draft
4. **Candidate Email Contents**
The candidate receives:
* Interview date, time, and time zone
* Interview Rooms link
* Support contact info
* Automated reminders before the interview
**Best Practices for Interview Scheduling**
* Use CSV batch scheduling for multiple candidates; add buffer time between slots
* Verify time zones and send invites at least 48 hours in advance
* Run tech checks before sessions and confirm support is available
* Share evaluation rubrics and feedback timelines with the panel in advance
# How to Handle Tentative or No Response from Candidates/Interviewers?
Source: https://docs.talview.com/hiring-teams/recruiter/scheduling-and-interviews/how-tos/how-to-handle-tentative-or-no-response-from-candidates-interviewers
This article explains what recruiters can do when a candidate or interviewer marks their RSVP as *Tentative* or has not yet responded (status: *Invited*). The platform provides built-in reminders, and recruiters also have options to follow up directly.
***
### Step-by-Step Walkthrough
### 1. Check RSVP Status
* Login as a recruiter and open the workflow and open the **Interview step**.
* In the table view, hover over the candidate or interviewer avatar to see their RSVP status (*Yes, No, Tentative,* or *Invited*) under the Attendees column.
* You can also click on the interview card to open the side panel, where RSVP responses are displayed.
### 2. Rely on Auto-Reminders
* The system automatically sends reminders to candidates and interviewers who have not responded or have marked themselves as *Tentative*.
* These reminders are triggered according to the interview scheduled time and start time logic (30-hour and 1-hour reminders, or a single 1-hour reminder if the gap is shorter).
### 3. Follow Up from the Candidate Profile
* Open the candidate profile and click on the **Interview card**.
* From the side panel, you can directly call the candidate if additional confirmation is needed.
### 4. Reach Out Offline (Optional)
* If required, use offline channels like direct phone calls, emails, or WhatsApp messages to confirm attendance.
* This is particularly useful if the interview start time is close and the RSVP is still pending.
Following up early helps avoid last-minute no-shows. Combine auto-reminders with a quick personal call or offline message to ensure both candidates and interviewers confirm their availability.
# How to manage No-Shows for Candidates and Interviewers
Source: https://docs.talview.com/hiring-teams/recruiter/scheduling-and-interviews/how-tos/how-to-manage-no-shows-for-candidates-and-interviewers
This article explains how recruiters can identify and manage situations where either candidates or interviewers do not show up for their scheduled interviews. The platform provides real-time status updates, escalation notifications, and post-interview summaries to help recruiters take timely action.
***
## Step-by-Step Walkthrough
### 1. Check No-Show Status in the Table View
* Login as a recruiter and select the workflow and open the **Interview step**.
* In the table view, check the candidate and interviewer status:
* **Joined** – Participant is present in the interview room.
* **Not joined** – Participant has not joined.
* **No Show** – Participant did not attend the interview during the scheduled time.
### 2. View No-Show Details in the Side Panel
* Click on the interview card for any candidate.
* In the side panel, you will see the real-time join status (*Joined, Yet to Join, No Show*) for both the candidate and interviewer.
### 3. Automatic Escalation Notifications
* If one participant joins but the other does not join within **5 minutes after the scheduled start time**, the system automatically sends an **escalation email** to the interview organizer (recruiter).
* This allows the recruiter to quickly intervene, contact the missing participant, and decide whether to reschedule or continue waiting.
### 4. Post-Interview Summary Email
* After the interview ends, a **summary email** is automatically sent:
* **To the organizer (recruiter):** Shows who attended, who were marked as no-shows, and overall attendance details.
* **To evaluators:** Shows their own attendance status and the attendance status of other participants.
* Based on this summary, the recruiter can decide whether to **reschedule the interview** if critical participants did not attend.
### 5. Follow-Up Actions
* If the candidate is a no-show:
* Reach out via phone, email, or offline channels to confirm if they faced any issues.
* Decide whether to reschedule or close the interview step.
* If the interviewer is a no-show:
* Contact the interviewer or assign a backup interviewer if possible.
* Communicate with the candidate to manage expectations and reduce frustration.
Always review the post-interview summary email to confirm attendance details. If key participants were no-shows, you can reschedule directly from the workflow to ensure the interview process stays on track.
# How to reschedule an Interview
Source: https://docs.talview.com/hiring-teams/recruiter/scheduling-and-interviews/how-tos/how-to-reschedule-an-interview
As a recruiter or master recruiter, you may occasionally need to change a candidate’s interview schedule due to unforeseen circumstances.This guide explains how to **Reschedule interviews in Talview’s Workflow Tools**, ensuring a smooth experience for both candidates and interviewers.
## Step-by-step Guide:
### Step 1: Access the workflow dashboard
* Navigate to the **Workflows** section from the main menu.
* Select the workflow that contains the candidate whose interview needs to be rescheduled.
* Click the **Interview** stage to view candidates scheduled for interviews.
* Choose the candidate whose interview you want to reschedule.
* In the side panel, scroll to the bottom and click **Reschedule**.
### Step 2: Configure New Interview Details
* A pop-up window appears with rescheduling options.
* Update the **date** and **time** as required.
* Click **Proceed** to confirm the changes.
* You can send an updated interview invitation to the candidate if needed.
Both the candidate and the interviewer will automatically receive an email notification with the updated interview date and time.
### Step 3: Confirm Rescheduling
* After confirmation, a notification appears indicating **successful rescheduling.**
* Refresh the page to view the changes and ensure the new interview schedule is correctly applied.
> **Key Outcome:** The interview schedule is successfully updated in the system, and all participants are notified automatically, ensuring clarity and avoiding missed meetings.
# How to schedule an Interview for a new candidate
Source: https://docs.talview.com/hiring-teams/recruiter/scheduling-and-interviews/how-tos/how-to-schedule-an-interview-for-a-new-candidate
This article explains how**recruiters and master recruiters** can schedule interviews for new candidates within **Talview’s Workflow platform.**
It provides a clear step-by-step guide on downloading the candidate template, adding candidate information, and confirming interview schedules.
## Step-by-step Guide:
### Step 1: Access the workflow dashboard
* From the main menu, navigate to the **Workflows** section.
* Select the **workflow** where you want to schedule interviews.
### Step 2: Configure Interview Details
* Click **Schedule** to begin organizing interviews for your selected workflow.
* From the **Schedule** side panel:
* Choose the **provider** (platform where the interview will be conducted).
* Select the **interview duration**.
* Click **Download Template** to download the candidate spreadsheet.
* Open the downloaded file, fill in candidate details, and **save** it to your system.
* Click **Upload** to import the completed spreadsheet.
* Manually choose the **interviewer**, **interview date**, and **time** from the available options.
**Tip:** Ensure candidate details match the required format in the template before uploading. Incomplete or incorrect data may cause scheduling errors.
### Step 3: Confirm Interview Schedule
* Review all details to ensure accuracy.
* Click **Schedule** to finalize the interview.
* Once scheduled, you can view the interview in the respective **Interview Step** of your workflow.
**Note:** Successfully scheduled interviews will appear in the interview step timeline for easy tracking and updates.
# How to schedule an Interview for an existing candidate
Source: https://docs.talview.com/hiring-teams/recruiter/scheduling-and-interviews/how-tos/how-to-schedule-an-interview-for-an-existing-candidate
This article covers the key functionalities of Talview’s interview scheduling system, providing step-by-step guidance for common scheduling operations.\
Here, recruiters can effortlessly schedule interviews and intelligently have the platform manage all RSVP workflows.
> **Prerequisites:** Before scheduling an interview, ensure:
>
> * Candidate is added to an active workflow
> * Workflow has an interview stage configured
> * Interviewers have connected their calendars to Talview
> * Interview provider (Zoom, Microsoft Teams, Google Meet) is configured for your account
## Step-by-step Guide:
### Step 1: Access the workflow dashboard
* Navigate to the **Workflows** section from the menu.
* Select the workflow for which you want to schedule interviews.
> **Tip:** Use the search bar or filters to quickly locate specific workflows.
### Step 2: Schedule an interview
* Locate the candidate in your workflow dashboard
* Use the search function if you have many candidates
* Or scroll through the candidate cards in the current stage
* Click anywhere on the candidate card to open their profile
* In the candidate profile, click the **Schedule** button.
### ****Step 3: Configure interview details
* From the schedule side panel, choose the provider (platform where the interview will be held) and the duration of the interview.
* If it’s an **In-person interview**, mention the location address.
**Note:** Interviewers must have their calendars connected to Talview for real-time availability to display.
### **Step 4: Confirmation**
* Finalize your interview schedule by clicking on the “**Schedule”** button
* Scheduling completed successfully and can be viewed in that respective interview step.
### **Tips & Best Practices:**
1. **Schedule panel interviews 48+ hours in advance** to give the candidates and the interviewer adequate time to confirm availability and prepare.
2. **Avoid back-to-back interviews** without breaks—schedule at least 15 minutes between interviews for notes and transitions.
3. **Double-check timezones** for international candidates or remote hiring across multiple time zones to prevent no-shows.
# How to Schedule Interviews with Guest Interviewers
Source: https://docs.talview.com/hiring-teams/recruiter/scheduling-and-interviews/how-tos/how-to-schedule-interviews-with-guest-interviewers
Recruiters often need to involve external interviewers or internal interviewers who are on the client domain in the interview process. With the **Guest Interviewer Scheduling** capability, recruiters can now seamlessly schedule interviews with external participants directly from the **Workflow Tools**, supporting both online and in-person interviews. This ensures flexibility in panel composition while maintaining control through domain whitelisting and RSVP tracking.
***
### **Steps to Go Through the Flow**
### 1. Log in and Access the Workflow
* Log in to the platform as a **Recruiter**.
* Navigate to the **Workflow** containing the candidate(s) you want to schedule interviews for.
### 2. Initiate Scheduling via Workflow Tools
* Select the relevant candidate(s) from the workflow.
* Click on the **Schedule** option available in the footer section.
### 3. Add a Guest Interviewer
* In the **Interviewer** dropdown field, you can type the guest interviewer’s **email address**.
* If the guest is not an existing platform user, a prompt will appear **“New user, add as guest”** to add the user as a guest.
* Once the email is entered, the system will **validate the email format**.
### 3. Validation on Scheduling
* Click the **Schedule** button to proceed.
* At this stage, two validations occur:
* **Domain Whitelisting Check** – If the domain is not on the **approved list**, an error message will be shown.
* The interview **will not be scheduled** until the issue is resolved.
### 4. Interview Invite Sent to Guest Interviewer
* Upon successful scheduling, the guest interviewer will receive an **interview invite via email**.
* The invite includes RSVP options and joining details (for online interviews).
Guest interviewers added this way can fully participate in the interview, including joining the session, responding to invites, and viewing limited interview details as per their access level.
This feature works for **both online and in-person interview modes**.
***
# How to Send Interview Reminders and Follow-Ups
Source: https://docs.talview.com/hiring-teams/recruiter/scheduling-and-interviews/how-tos/how-to-send-interview-reminders-and-follow-ups
This article explains how interview reminders and follow-ups are currently handled by the system. Recruiters do not need to send manual reminders, as the platform automatically manages reminder notifications for both candidates and interviewers who have not RSVPed (Invited status) or have marked themselves as *Tentative*.
***
## Step-by-Step Walkthrough
### **1. Check RSVP Status**
To see whether candidates or interviewers have responded to the interview invite:
* Login as a recruiter and open the workflow and select the **Interview step**.
* In the table view, hover over the candidate or interviewer avatar to see their RSVP status (*Accepted, Declined, Tentative,* or *Invited*) under the **Attendees** column.
* You can also click on the interview card to open the side panel, where RSVP details are clearly listed.
### **2. Understand Automated Reminders**
The system automatically sends reminders to candidates and interviewers who:
* Have not RSVPed (*Invited*), or
* Have responded as *Tentative*.
### **3. Reminder Logic Based on Scheduled Time**
The reminders are triggered based on the time gap between when the interview was scheduled and when it is set to start:
* **If the gap is 30 hours or more**:
* Reminder 1 → Sent exactly **30 hours before** the interview start time.
* Reminder 2 → Sent exactly **1 hour before** the interview start time.
* **If the gap is less than 30 hours**:
* Only one reminder is sent exactly **1 hour before** the interview start time.
### **4. No Manual Reminder Option**
Currently, recruiters cannot send reminders manually. The system ensures consistent notifications are sent automatically according to the above logic.
**Tip**: You can always monitor RSVP statuses in the Workflow Tools platform. If a candidate or interviewer still hasn’t responded despite automated reminders, consider reaching out offline (via call, email, or WhatsApp) to avoid last-minute no-shows.
# How to set and manage interview time slot for Live interviews
Source: https://docs.talview.com/hiring-teams/recruiter/scheduling-and-interviews/how-tos/how-to-set-and-manage-interview-time-slot-for-live-interviews
Efficient scheduling ensures smooth coordination between interviewers and candidates. Talview’s built-in scheduling tools help recruiters select accurate time slots based on real-time interviewer availability, synced calendars, and automatic time-zone adjustments, ensuring conflict-free and convenient interview planning.
***
## Video Guide:
1. **Scheduling Interview**
* When creating or editing an interview workflow, navigate to the **Schedule** section.
2. **Select Date**
* Use the calendar dropdown to choose the preferred interview date.
3. **Choose Time Slot**
* Select an available **time slot** from the dropdown.
* Talview automatically displays only the interviewer’s **free/busy** time based on synced Google or Outlook calendars, ensuring accurate scheduling.
4. **Confirm & Save**
* Once saved, Talview sends calendar invites to both interviewers and candidates with the finalized date and time.
* Time zones are automatically adjusted, making it reliable for global interviews.
By following these steps, best practices, and troubleshooting tips, recruiters can schedule interviews efficiently and deliver a seamless candidate experience in Talview.
## Best Practices
* Set time slots in advance to give interviewers and candidates enough preparation time.
* Provide multiple time slot options to increase flexibility and reduce rescheduling efforts.
* Ensure interviewer calendars are synced so only real-time available slots appear during scheduling.
* Use **bulk scheduling** when managing high-volume hiring to streamline the process across multiple candidates.
* Allow candidate self-scheduling (if enabled) to reduce manual coordination and improve overall experience.
# How to Track Live Interview Status from the Interview Dashboard
Source: https://docs.talview.com/hiring-teams/recruiter/scheduling-and-interviews/how-tos/how-to-track-live-interview-status-from-the-interview-dashboard
This article explains how recruiters can track the real-time status of interviews from the **Interview Dashboard**. The dashboard provides a consolidated view of past, current, and upcoming interviews with details about participants, their RSVP responses, and meeting information.
***
## Step-by-Step Walkthrough
### 1. Go to the Workflow
* Login as Recruiter.
* Select the workflow that contains the interviews you want to track.
### 2. Open the Interview Step
* Inside the workflow, select the interview step that you want to track.
* This opens the **Interview Dashboard**, where all interviews for that step are listed.
### 3. View Interviews by Date
* The interviews are automatically arranged by date, showing:
* Past interviews – already completed.
* Current interviews – happening now.
* Upcoming interviews – scheduled for later.
* Cancelled interviews - canceled by the recruiter or candidate has declined.
### 4. Check Candidate and Interviewer Details
* For each interview, you can see:
* **Candidate name and details**
* **Interviewer(s) name and details**
* **RSVP status** (Accepted\*, Declined, Tentative, Invited\*)
* **Participation status** (*Joined, Not joined, No Show, Completed*)
### 5. Monitor Meeting Information
* The dashboard also shows:
* **Meeting status** – whether it has started, is ongoing, or completed.
* **Organizer details** – who scheduled the interview.
* **Recording links** – available for completed online interviews.
Use the **Interview Dashboard** as your single source of truth to track interview progress in real time. From here, you can quickly identify no-shows, check who is waiting, and access recordings after completion.
# How to view Interview Recordings
Source: https://docs.talview.com/hiring-teams/recruiter/scheduling-and-interviews/how-tos/how-to-view-interview-recordings
This article explains how recruiters can access and view interview recordings once an online interview has been completed. Recordings are available directly from the side panel or the list view, making it easy to review past interviews.
***
### Step-by-Step Walkthrough
### 1. Open the Workflow
* Login as a recruiter
* Select the workflow and open the **Interview step** that you want to track the interview.
* Choose the “**Completed**” interview you want to view the recording for.
### 2. View Recording from the List View
* In the interview step, look for the **Recording** column in the list view.
* Click on **View** under this column to access the recording.
### 3. View Recording from the Side Panel
* Click on the interview card for any candidate.
* In the **Interview Summary** section of the side panel, click **View Recording** to open and watch the completed interview in a modal.
Interview recordings are only available for **completed online interviews**.\
If the interview was not completed or was conducted offline, no recording will be shown.
# How to view Scheduled Interviews
Source: https://docs.talview.com/hiring-teams/recruiter/scheduling-and-interviews/how-tos/how-to-view-scheduled-interviews
This article guides recruiters and master recruiters on how to view and manage interview schedules within **Talview’s Workflow Tools.**
Monitoring scheduled interviews helps ensure smooth coordination between candidates and interviewers, supporting efficient recruitment operations.
## Step-by-step Guide:
### 1. Access the workflow dashboard
* Navigate to the **Workflows** section from the main menu.
* Select the workflow where the interviews have been scheduled.
### 2. Viewing the scheduled interviews
* Once you open the desired **workflow**, you’ll land on the **candidate invite list** within that workflow.
* Click on the relevant **Interview Step** to view scheduled interviews.
* You can now see the list of candidates with interviews scheduled under this step, along with key details such as interview time and assigned interviewers.
**Tip**: You can use the **search bar** to quickly locate specific candidates or interview slots, helping streamline review and coordination.
# Managing Interview RSVPs: Accept, Decline, or Reschedule Interviews
Source: https://docs.talview.com/hiring-teams/recruiter/scheduling-and-interviews/how-tos/managing-interview-rsvps-accept-decline-or-reschedule-interviews
This article explains how candidates and interviewers can respond to interview invitations using the meeting status link available in the email body and calendar (.ics) file.
It outlines supported RSVP actions, time-based restrictions, meeting status behavior, and how declines and rescheduling are handled.
***
## Overview of RSVP Capabilities
Both candidates and interviewers can manage interview invitations by:
* Accepting the interview
* Declining the interview
* Marking the interview as Tentative
* Proposing a new interview time (with restrictions)
All RSVP actions can be performed directly from:
* The email body
* The attached calendar (.ics) file
***
## Who Can Perform RSVP Actions and Until When
### Candidate RSVP Rules
* Candidates can accept or decline the interview anytime until the meeting status changes to **No Show** or **Completed**.
* Candidates can propose a new time while the meeting status is **Scheduled** or **In Progress**, provided the newly proposed time is at least **4 hours ahead of the current time**.
> **Example:**\
> If the current time is 1:00 PM, the candidate cannot propose a new time between 1:00 PM and 5:00 PM.\
> The earliest selectable proposed time must be 5:00 PM or later.
### If a candidate declines the interview:
* The interview is automatically canceled.
* No further action is required from the recruiter.
***
### Interviewer RSVP Rules
* Interviewers can accept or decline the interview anytime until the meeting status changes to **No Show** or **Completed**.
* Interviewers can propose a new time while the meeting status is **Scheduled** or **In Progress**, provided the newly proposed time is at least **4 hours ahead of the current time**.
> **Example:**\
> If the current time is 1:00 PM, the interviewer cannot propose a new time between 1:00 PM and 5:00 PM.\
> The earliest selectable proposed time must be 5:00 PM or later.
### If an interviewer declines the interview:
* The interview is **not** canceled.
* The recruiter can:
* Change the interviewer
* Reschedule the interview
* Cancel the interview manually
***
## Providing Reasons While Declining
When declining an interview through the email body:
### Candidates:
* Can select or provide a reason for declining.
### Interviewers:
* Can provide a reason for declining.
* Can propose an alternate interviewer as part of the decline flow.
This information helps recruiters take faster and more informed follow-up actions.
***
## Meeting Status and Its Impact on RSVP
### Meeting Status Lifecycle
**Scheduled**\
Initial state after interview creation.
**In Progress**\
The meeting moves to this status as soon as any participant (candidate, interviewer, or organizer) joins the interview.
**Completed**\
The meeting moves to this status if any participant joins the interview and the session concludes.
**No Show**\
If no one joins, the meeting moves to **No Show**.
The meeting status automatically moves to **No Show** or **Completed** 35 minutes after the interview end time.
***
## RSVP Restrictions Based on Meeting Status
RSVP actions are allowed only when the meeting status is:
* Scheduled
* In Progress
No RSVP actions can be performed once the meeting status becomes:
* No Show
* Completed
***
## Canceling an Interview
A meeting can be canceled when the status is:
* Scheduled
* In Progress
Once the meeting moves to **No Show** or **Completed**, it can no longer be canceled or modified.
***
## Summary of Key Rules
* RSVP actions are available from both the email body and the .ics file.
* If a candidate declines → the interview is automatically canceled.
* If an interviewer declines → the interview remains active for recruiter action.
* Propose new time can be done until the meeting reaches No Show or Completed.
* Newly proposed time must be at least 4 hours ahead of the current time.
* No RSVP actions are allowed after the meeting reaches No Show or Completed.
* Meeting status auto-updates based on participant joins and time rules.
# Understanding Candidate and Interviewer RSVP Status (Accepted, Declined, Tentative)
Source: https://docs.talview.com/hiring-teams/recruiter/scheduling-and-interviews/how-tos/understanding-candidate-and-interviewer-rsvp-status-accepted-declined-tentative
This article explains how recruiters can view the RSVP status of candidates and interviewers for scheduled interviews. Recruiters can quickly check whether participants have responded *Invited*, *Accepted, Declined*, or *Tentative* by accessing the workflow, navigating to the interview step, and reviewing details either in the table view or side panel.
***
## Step-by-Step Walkthrough
### 1. Go to the Workflow
Login as a recruiter and navigate to the workflow where the interview is scheduled.
### 2. Choose the Interview Step
Select the interview step from the workflow to see all scheduled and past interviews.
### 3. Check RSVPs in the Table View
In the table view, hover over the avatars of the candidate and interviewer against each scheduled interview under the **Attendees** column. This will show you their RSVP status: *Invited, Accepted, Declined,* or *Tentative*.
### 3. View More Details in the Side Panel
If you need additional details, click on the interview card. This opens the side panel, where you can see the RSVP responses clearly listed for both the candidate and interviewer
If you notice that a candidate or interviewer has not RSVPed, it will appear as “*Invited*”, you may want to follow up with them directly.
***
# Why am I unable to access the evaluation form?
Source: https://docs.talview.com/hiring-teams/recruiter/screening/diagnostics/why-am-i-unable-to-access-the-evaluation-form
When using **Talview’s Workflow Tools**, evaluation forms play a critical role in capturing structured feedback from evaluators during hiring and assessment workflows.
If you notice that responses entered into an evaluation form are not being saved, it can interrupt the evaluation process and affect the accuracy of candidate data.
This article helps diagnose the issue and provides actionable steps to resolve it.
## 🔎 Troubleshooting Common Issues
| **What might be wrong** | **How to fix it** |
| :------------------------------------------------------------------------------------------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Unstable internet connection**: A poor or interrupted network may prevent form responses from syncing with the platform. | Ensure you have a stable internet connection before starting the evaluation. Refresh the page only after confirming connectivity. |
| **Form not submitted properly**: Simply entering responses does not save them; the evaluator must hit the “Save” or “Submit” button to confirm entries. | Double-check that you have clicked the “Save” or “Submit” button at the end of the evaluation form. Wait for the confirmation message that the form has been saved. |
| **Session timeout**: If the evaluator is inactive for too long, the session may expire, causing responses to be lost when trying to save. | Re-login to the platform if you have been inactive and enter responses within the active session limit. |
| **Form access permissions**: If your role does not have permission to submit or update evaluation forms, responses may not reflect in the system. | Contact your admin to confirm you have the right permissions to complete and save evaluation forms. |
| **Browser compatibility issues**: Older browser versions or unoptimized browsers may conflict with form functionality. | Use the latest version of Chrome or other supported browsers. Clear cache and cookies before retrying. |
| **Temporary platform outage**: Rarely, platform downtime or server glitches can prevent data from saving. | Check Talview’s status page or reach out to support for confirmation. Retry saving once the platform is fully operational. |
| **Multiple evaluators editing simultaneously**: If two users attempt to edit the form at the same time, one evaluator’s inputs may overwrite the others. | Coordinate with other evaluators and ensure that only one person fills in the evaluation form at a time. |
### **Additional Tips:**
* Always enter responses and save periodically instead of waiting until all fields are filled.
* Disable browser extensions (like ad blockers or autofill tools) that may interfere with form submission.
* If using VPN or proxy, try disabling it temporarily to ensure smooth data transmission.
* For recurring issues, capture error messages or take a screenshot and share it with the Talview support team for faster resolution.
# Why did my resume fail to parse during upload?
Source: https://docs.talview.com/hiring-teams/recruiter/screening/diagnostics/why-did-my-resume-fail-to-parse-during-upload
When a resume fails to parse on Talview’s Workflow Tools platform, candidates’ details may not automatically map into the system fields (like name, email, or experience).
This usually happens due to file format issues, document structure inconsistencies, or unsupported elements embedded within the resume.
Below are common causes and their respective fixes.
***
## 🔎 Troubleshooting Common Issues
| **What might be wrong** | **How to fix it** |
| :------------------------------------------------------------------------------------------------------------------------------ | :--------------------------------------------------------------------------------------------------------- |
| The resume is uploaded in an unsupported format (e.g., image, scanned PDF). | Ensure resumes are uploaded in supported formats: DOC, DOCX, PDF (text-based, not scanned images), or RTF. |
| The file is password-protected or encrypted. | Remove password protection or save an unprotected copy before uploading. |
| Resume contains excessive design elements (tables, graphics, charts, or multi-column layouts) that the parser cannot interpret. | Simplify the resume layout — use a clean, single-column design and avoid heavy use of graphics. |
| Resume text is embedded within an image scan, making it unreadable to parsing algorithms. | Use OCR-enabled PDF exports or retype the text into a Word (.docx) or text-based PDF. |
| File size is too large, causing parsing limits to fail. | Compress the file or reduce embedded graphics to bring it within recommended size (usually under 5MB). |
| The resume uses uncommon file extensions or corrupted files. | Save the document again in a supported format (.docx or text-based PDF) to ensure parsing compatibility. |
**Additional Tips:**
* Always encourage candidates to upload resumes in **DOCX format** for the most reliable parsing.
* If multiple parsing errors occur with the same candidate pool, share a **resume template guideline** that recommends simple layouts (avoiding headers, footers, and text boxes).
* Instruct candidates to avoid scanned resumes or image-only PDFs — these cannot be parsed reliably.
* Test parsing by re-uploading the resume after saving it in a fresh Word document.
# Why is the candidate’s profile not loading?
Source: https://docs.talview.com/hiring-teams/recruiter/screening/diagnostics/why-is-the-candidates-profile-not-loading
Candidate profile pages in **Talview Workflow Tools** may fail to load for many reasons — from simple browser issues to permission, network or backend service problems.
Use the table below to quickly diagnose common causes and apply targeted fixes.
***
## 🔎 Troubleshooting Common Issues
| **What might be wrong** | **How to fix it** |
| :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Temporary network or connectivity issue (slow or intermittent internet) | Reload the page; if that fails, switch networks, run a quick network speed test, and retry. If on VPN/proxy, try without it. |
| **Browser-related issues** including outdated browser versions, corrupted stored data (cache, cookies, local storage), or interference from extensions and blocking software that prevent proper page functionality | **Try browser troubleshooting:** 1. Use a hard refresh (`Ctrl/Cmd+Shift+R`) or clear Talview site cookies and cached data 2. Ensure you're using a supported browser (Chrome or Edge latest versions) and disable browser extensions (especially ad-blockers and privacy extensions). 3. Alternatively, open an incognito/private window to test with a clean browser environment that automatically disables extensions and uses fresh cache. |
| Browser compatibility or outdated browser | Confirm Talview-supported browsers and versions. Update the browser or try a supported browser (Chrome/Edge latest) and retry. |
| Browser extensions, ad-blockers, script blockers interfering with page scripts | Disable extensions (especially ad-blockers, privacy extensions) or try in an incognito window with extensions off. |
| Authentication or SSO token expired (user logged out or session timed out) | Log out and log back in. If using SSO, re-authenticate via the identity provider. Confirm session length policies with your admin. |
| Insufficient user permissions or role-based access preventing profile visibility | Check user role/permissions in the admin console. Ask an admin to confirm you have permission to view that candidate and the specific workflow/tool. |
| Large attachments or media on the candidate profile causing slow load or timeouts | Ask the hiring team to temporarily remove or minimize large attachments or try loading the profile with attachments disabled. Increase timeout only if platform admin can. |
| Security/firewall rules or corporate proxy blocking requests to Talview services | Work with IT to allowlist Talview endpoints and ensure SSL inspection is not breaking tokens. Test outside corporate network (e.g., mobile hotspot) to confirm. |
| Local device resource limits (memory/CPU) causing page to hang on heavy profile content | Close other tabs/apps, restart the browser |
**Summary of immediate actions:**
1. Try Incognito and a different browser (Chrome recommended).
2. Clear cache/cookies for Talview and disables extensions.
3. Try a different network (to rule out firewall/proxy).
4. If issue persists for multiple users, capture `HAR + console logs` and escalate with candidate IDs and timestamps.
# Why is the candidate’s resume missing or not visible?
Source: https://docs.talview.com/hiring-teams/recruiter/screening/diagnostics/why-is-the-candidates-resume-missing-or-not-visible
When a candidate’s resume is missing or not visible in **Talview Workflow Tools**, it delays screening and interview processes.
This article lists common causes and fixes to help recruiters, hiring managers, and admins to get access to the candidate’s missing resume.
***
## 🔎 Troubleshooting Common Issues
### Scenario 1: Candidate Applies Using the Resume
| **What might be wrong** | **How to fix it** |
| :------------------------------------------------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Candidate submitted unsupported file type (e.g., image, RTF, password-protected) | Instruct candidate to resubmit in**PDF** (text-based) |
| File size exceeds platform limits | Request candidate to compress or reformat resume under allowed size\_(\_ **typically 2–5MB**, although keeping resume files **under 1MB** is considered best practice to avoid upload issues.) |
| Resume upload incomplete, or error missed by candidate | Guide candidate to monitor for confirmation message after upload |
| Candidate skipped resume upload step | Prompt candidate to complete missing step via email |
| Resume corrupted during upload | Ask for a fresh upload, ensuring file integrity |
***
### Scenario 2: Resume File Comes in via ATS
| **What might be wrong** | **How to fix it** |
| :------------------------------------------------------------- | :-------------------------------------------------- |
| ATS integration with Workflow Tools is broken or misconfigured | Recruiters need to reach out to the admin. |
| Unsupported resume file imported | Recruiters need to reach out to the Admin / Support |
| Old versions or duplicates of resume linked to the candidate | Remove redundant docs and retain latest resume copy |
***
### Scenario 3: Recruiter Uploads the Resume
| **What might be wrong** | **How to fix it** |
| :------------------------------------------------------------------------------- | :-------------------------------------------------------------------- |
| Recruiter uploads unsupported file or by mistake chooses wrong candidate profile | Confirm correct file format and verify assigning to correct candidate |
| Duplicate resumes uploaded for same candidate | Delete older or redundant versions, keep only the latest |
| Resume upload not completed (incomplete process, no confirmation message) | Double-check for completion confirmation and re-upload if necessary |
***
### **Additional Tips:**
* Use supported formats like **PDF** to ensure compatibility.
* Upload resumes over a stable internet connection to prevent transfer interruptions.
* Keep file sizes within platform limits (usually **under 3 MB**) by compressing if needed.
* Always wait for confirmation of a successful upload and preview the resume if possible.
# Why is the Evaluation form not saving responses?
Source: https://docs.talview.com/hiring-teams/recruiter/screening/diagnostics/why-is-the-evaluation-form-not-saving-responses
The evaluation form in **Talview’s Workflow Tools** may fail to save responses for many reasons - from simple client-side problems (browser, connectivity) to server-side issues (validation, permissions, database).
The table below lists common causes and straightforward fixes to help you quickly diagnose and resolve the problem.
***
## 🔎 Troubleshooting Common Issues
| **What might be wrong** | **How to fix it** |
| :--------------------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------- |
| User session expired or user got logged out | Ask the user to refresh or re-login and retry. Make sure session timeouts are configured appropriately for long evaluations. |
| Browser incompatibility or outdated browser | Confirm the user is on a supported, up-to-date browser (Chrome/Edge/Firefox) and ask them to try again after updating. Test in an alternate browser. |
| Network interruptions or unstable connectivity | Check network connection: ask user to switch networks or use a wired connection. Implement/retry with exponential backoff for intermittent failures. |
| Form is in read-only/closed state or not published | Confirm the form is published and editable for the current user and evaluation instance. Re-open or publish the correct version if needed. |
| Autosave feature disabled or misconfigured | Check autosave settings; advise user to manually save and submit for now. Re-enable or fix autosave configuration. |
| Feature flags or rollout causing unexpected behavior | Check whether any feature flags are active for the org/environment and rollback or enable fixes as necessary. |
**Additional Tips:**
* Train evaluators to save frequently and avoid long idle periods.
* Use supported browsers (Chrome latest recommended) and keep them updated.
* Avoid using browser back/forward during saves; prefer explicit Save buttons.
* Keep attachments under platform limits and compress large files.
* Review release notes before deployments and test evaluation workflows after upgrades.
* Enable autosave/drafts where available so partial work is preserved.
* Maintain a checklist for required fields within each evaluation template to reduce validation-related failures.
# Why isn’t my submitted evaluation showing up?
Source: https://docs.talview.com/hiring-teams/recruiter/screening/diagnostics/why-isnt-my-submitted-evaluation-showing-up
If you submitted an evaluation in Talview Workflow Tools but it doesn't appear where you expect, several common causes can explain the missing entry. Below is a quick diagnostic checklist: likely issues in the left column and actionable fixes in the right column so you can find and resolve the problem quickly.
***
## 🔎 Troubleshooting Common Issues
| **What might be wrong** | **How to fix it** |
| :--------------------------------------------------------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Evaluation submission didn’t complete (network interruption or session timeout) | Refresh the page and check your browser’s network indicators. If you suspect the submit step failed, re-open the evaluation and try to submit again. Note any error messages. |
| You submitted from a different account (staging vs production) or another account | Confirm which account you were logged into, and which account you used. Log into the correct account. |
| You don’t have permission to see the completed evaluation (role/permission restrictions) | Ask your admin to verify your role and permissions. Admins can check visibility settings and assign appropriate access or retrieve the record for you. |
| Browser cache/cookies causing display issues or outdated page | Hard-refresh (`Ctrl/Cmd+Shift+R`) or clear cache and cookies. Alternatively, open an incognito/private window and log in again. |
| Browser or extension interference (pop-up blockers, ad blockers, outdated browser) | Disable interfering extensions, ensure pop-ups/third-party cookies are enabled for Talview, and use a supported browser version (Chrome/Edge/Firefox). Try incognito mode to test. |
| You’re searching by incorrect candidate details (typo, different candidate ID) | Confirm candidate name/ID and try alternate spellings or identifiers. Use search-by-job or evaluation ID if known. |
**Additional tips:**
* Always wait for a submit confirmation before closing the tab.
* If attaching large media, wait until the progress bar completes; consider compressing large files.
* Use a stable wired or strong Wi‑Fi connection for long video/audio uploads.
* Keep browser up to date and disable heavy extensions (ad-blockers can interfere).
* Export or take a screenshot of your evaluation summary (if available) after submitting, for your records.
# Gen AI Resume Fitment: Feature Overview
Source: https://docs.talview.com/hiring-teams/recruiter/screening/gen-ai-resume-fitment-feature-overview
***
### What is Gen AI Resume Fitment?
Gen AI Resume Fitment is Talview's AI-powered screening layer that automatically evaluates incoming candidate resumes against the specific competency and skill requirements of a workflow (job requisition) - and returns a structured fitment verdict with an evidence-backed explanation.
It is designed to remove subjectivity from early-stage screening, surface the right candidates faster, and give recruiters a consistent, auditable signal - at scale.
***
### How It Works
1. **Configure** - Recruiter or Master Recruiter sets Essential, Preferred, and Optional criteria against the workflow as per the job role requirements
2. **Parse** - System extracts structured data from each incoming resume across four dimensions:
| Dimension | What is Extracted | Used For |
| :---------------------------------- | :----------------------------------------------- | :---------------------------------------------------------------------------------------- |
| **Personal Information** | Name, contact details, location | Candidate identification and profile creation; not used in fitment scoring |
| **Education Details** | Degrees, institutions, years of completion | Evaluated against Essential criteria (e.g., minimum degree requirement) |
| **Experience Details** | Job titles, companies, tenures, responsibilities | Primary signal for Essential and Preferred criteria - seniority, recency, domain depth |
| **Qualifications & Certifications** | Listed certifications, professional credentials | Evaluated against Essential or Preferred criteria where specific credentials are required |
3. **Evaluate** - LLM-backed engine returns Strong / Potential / Low Fit with evidence-backed explanation, visible on the candidate card. Please check the ***demo*** below:
***
### Configuration Criteria
| Criteria Type | Definition |
| :--------------------------- | :---------------------------------------------------------------------- |
| **Essential** (Must-have) | Non-negotiable requirements the candidate must demonstrate |
| **Preferred** (Good-to-have) | Attributes that strengthen candidacy; not disqualifying if absent |
| **Optional** (Nice-to-have) | Supplementary signals that add positive weight; absence never penalises |
***Example - Senior Backend Engineer (5+ years)***
| Categories | Criteria |
| :------------ | :-------------------------------------------------------------------------------------------- |
| **Essential** | Java or Python, 5+ years backend, distributed systems, B.E./B.Tech, Tier-1 graduation college |
| **Preferred** | AWS/GCP, AI-led development, microservices, team leadership |
| **Optional** | Open-source contributions, fintech domain, product company background |
***
### Fitment Tier Definitions
| Tier | When It Applies |
| :---------------- | :------------------------------------------------------------------------------------------------------------------------------ |
| **Strong Fit** | All essentials fully met with recent, unambiguous evidence; most preferred met. Ready to contribute with minimal ramp-up. |
| **Potential Fit** | All essentials met (at most one partially); at least 40% of preferred met. Minor gaps addressable through interview. |
| **Low Fit** | One or more essentials not met, or two+ essentials only partially met. Material domain, seniority, or skill mismatch. |
***Example: Output - Candidate Level***
For a candidate evaluated against the *Senior Backend Engineer (5+ years)* workflow above, the system returns:
**Fitment:** Potential Fit
**Explanation:**
*Strengths:* Strong backend engineering foundation across Java and distributed systems with progression from associate to senior engineer roles.
*Gaps:* Explicit backend tenure of three years versus five-year requirement; no cloud platform or leadership evidence in resume.
*Verdict Rationale:* Essential experience requirement only partially met; warrants interview to validate cloud exposure and depth of backend ownership.
***
### What Makes Talview’s Resume Fitment Distinctive
| Capability | Generic AI Screeners | Talview Gen AI Resume Fitment |
| :------------------------ | :--------------------- | :------------------------------------------------------ |
| Customer-defined criteria | Pre-trained taxonomies | Per-workflow Essential / Preferred / Optional |
| Explainability | Score or summary | Evidence-traced verdict per criterion |
| Hallucination guardrails | Variable | Evidence-only; flags gaps over inflated scores |
| Bias controls | Often opaque | No protected attributes used; criteria-based evaluation |
| Compliance posture | Variable | Aligned to EU AI Act high-risk system requirements |
***
### Trust & Governance
* **Evidence-grounded** - No inferences beyond explicit resume content; if a criterion cannot be verified, the system states the gap rather than assuming
* **Bias-controlled** - Evaluates only against your configured criteria; protected attributes (gender, race, age, ethnicity, disability) are not used
* **Compliance-aligned** - Designed for EU AI Act high-risk system standards: transparent reasoning, configurable criteria, mandatory human oversight, and auditability
* **Human-in-the-loop** - The AI classifies and explains; recruiters and hiring managers retain full override authority
***
### Frequently asked questions
No. The AI classifies and explains; all shortlisting decisions are made by the hiring team.
Yes. Resumes can be uploaded individually or in bulk. Candidate profiles are auto created, and fitment runs automatically once criteria are configured.
Yes. Criteria can be updated at any time and re-applied to existing candidates in the workflow.
No. Talview does not use individual customer data for model training without explicit consent and appropriate anonymisation.
***
*For configuration support or fitment calibration queries, contact your Talview Customer Success Manager.*
# Bulk Actions: Scheduling, Inviting, or Updating Candidate Status
Source: https://docs.talview.com/hiring-teams/recruiter/screening/how-tos/bulk-actions-scheduling-inviting-or-updating-candidate-status
This article explains how recruiters can **use bulk actions** to efficiently schedule interviews, invite candidates, and update application status within **Talview's Workflow Tools platform.** Bulk actions enable you to manage high-volume recruitment by processing multiple candidates simultaneously saving time, ensuring consistency, and streamlining your hiring workflow.
## **Video Guide**
### **Navigate to the Workflow**
* Login as a Recruiter.
* Select the workflow that contains the candidates you want to manage.
* Switch to the **Resume Screening** tab to access bulk action options.
### **1. Bulk Scheduling Interviews for Existing Candidates**
Use this option when you have candidates already in your workflow who need interviews scheduled.
* Select the candidates you want to schedule by clicking the checkboxes next to their names.
* Click the **Schedule** button to begin setting up interviews for the selected candidates.
* In the schedule side panel, configure the following settings:
* **Workflow:** Choose the appropriate workflow from the dropdown to confirm the hiring pipeline.
* **Interview step:** Select the interview stage where candidates will be scheduled.
* **Duration:** Set the length of the interview (e.g., 30 minutes, 60 minutes).
* **Provider:** Choose the interview platform from the dropdown:
* Select **In-person** for on-site interviews
* Select an online platform (e.g., Zoom, Microsoft Teams) for virtual interviews
* **Interviewer:** Assign an interviewer from your team to conduct the interviews.
* **Date and Time:** Set a specific date and time for each candidate's interview to coordinate availability.
* Click **Schedule** to finalize and confirm the interview appointments.
* The system will send automated interview invitations to the selected candidates.
### **2. Bulk Scheduling: New candidates**
Use this option when importing new candidates with pre-determined interview schedules via CSV upload.
* Click the **Schedule** button to begin setting up interviews for new candidates.
* In the schedule side panel:
* Click **Download the template** to get the CSV file format.
* Open the downloaded template and fill in the required columns:
* **Candidate Name** (required)
* **Email Address** (required)
* **Phone Number** (required)
* **Interview Date** (format: DD/MM/YYYY)
* **Interview Time** (format: HH:MM)
* Any additional custom fields specific to your workflow
* Save the completed file in CSV format (not .xlsx).
* Click **Upload** and select your completed CSV file.
* Wait for the confirmation notification: **"File uploaded successfully"**.
* Verify the uploaded candidate data appears correctly in the panel.
* Configure the interview settings:
* **Workflow:** Choose the appropriate workflow from the dropdown.
* **Interview step:** Select the interview stage.
* **Duration:** Set the interview length.
* **Provider:** Choose the interview platform (In-person or online).
* **Interviewer:** Assign an interviewer (you can assign different interviewers per candidate if needed).
* Review all entries for accuracy.
* Click **Schedule** to create interviews for all uploaded candidates.
**Important:** If any errors occur during upload, the system will display an error report. Download it, correct the issues in your CSV file, and re-upload.
### **3. Bulk Inviting New Candidates to Assessments**
Use this option when adding multiple new candidates to an assessment or interview step without scheduling specific times.
* Click the **Invite** button to begin inviting new candidates.
* In the invite side panel:
* Click **Download the template** to get the CSV file format.
* Open the template and fill in the required columns:
* **Candidate Name** (required)
* **Email Address** (required)
* **Phone Number** (recommended)
* Any workflow-specific custom fields
* Save the completed file in CSV format.
* Click **Upload** and select your completed CSV file.
* Wait for the confirmation notification: **"File uploaded successfully"**.
* Verify the candidate list appears correctly.
* Configure the invitation settings:
* **Workflow:** Select the appropriate workflow from the dropdown.
* **Interview step:** Choose the assessment or interview step candidates will be invited to.
* **Time zone:** Adjust the time zone to ensure candidates receive invites in their local time.
* Review the candidate list for accuracy.
* Click **Invite** to send invitations to all uploaded candidates.
* Candidates will receive email invitations with instructions to complete their assessment or schedule their interview.
* Click on a candidate's name to view their application details.
### **4. Bulk Updating Candidate Status**
Use this option to move multiple candidates through your hiring pipeline stages simultaneously.
* Select the candidates whose status you want to update by clicking the checkboxes next to their names.
* Select **Change Status** dropdown menu.
* Choose the new status from the dropdown:
* **Selected:** Candidate is moving forward in the hiring process
* **Hold:** Candidate application is paused temporarily
* **Suspended:** Candidate application is on extended hold
* **Turned Down:** Candidate is rejected from the current position
**Note:** To update a single candidate's status, click on the candidate's name to open their profile side panel, then use the **Change Status** dropdown.
### **Best Practices:**
* Always double-check CSV formatting before uploading to avoid errors.
* Maintain accurate, up-to-date contact details for all candidates to prevent invitation failures.
* Use predefined templates for recurring recruitment drives to minimize setup.
* Regularly monitor bulk action outcomes for quality assurance and process optimization.
# How to Access and Navigate a Candidate’s Profile
Source: https://docs.talview.com/hiring-teams/recruiter/screening/how-tos/how-to-access-and-navigate-a-candidates-profile
This article explains how recruiters can Access and effectively navigate a candidate’s profile within **Talview’s Workflow Tools platform.** This brings together application details, assessment results, interview feedback, and communication logs which helps in boosting transparency, improving alignment, and supporting data-driven decisions.
## **Step-by-Step Guide**
### **1. Go to the Workflow**
* Login as a Recruiter.
* Select the workflow that contains the interviews and candidates you want to track.
### **2. Open the Interview Step**
* Inside the workflow, select the interview step that you want to track.
* This opens the **Interview Dashboard**, where all candidates for that step are listed.
### 3. Accessing a candidate’s profile
* Click on a candidate’s name or email to view and review their profile details.
* A side panel with candidate’s assessment details opens with tabs: **Overview, Form, Score, Evaluation and Call History.**
### 4. Navigating a candidate’s assessment details
* Under **Overview tab**:
* Open the **Assessment Details** section to see the candidate's assessment summary.
* Expand **Invitation Details** for more information about the candidate's assessment invitation.
* Play the candidate's **video response** to evaluate their answer to the interview question.
* Under **Form** tab:
* View the candidate's registration form
* Under **Score** tab:
* Review or assign the candidate's assessment score
* Under **Evaluation** tab:
* Add or view feedback for the selected candidate.
* Under **Call History** tab:
* View the communication history.
### **Tips for efficient navigation:**
* Use filters and bulk actions to manage high candidate volumes.
* Refer to the centralized interview feedback tab for aligned consolidated evaluator insights.
* View assessment videos and documents directly from the profile, no need to download externally.
# How to Delete an Uploaded Resume or Parsed Candidate
Source: https://docs.talview.com/hiring-teams/recruiter/screening/how-tos/how-to-delete-an-uploaded-resume-or-parsed-candidate
If a resume has been uploaded incorrectly or needs to be removed, you can delete it directly from the candidate's profile in the Resume Screening step. This article walks you through how to do that.
***
### Where to Find the Delete Option?
The option to delete an uploaded resume is available inside the candidate's profile, under the **Resume** sub-tab.
***
### Who Can Delete an Uploaded Resume?
| Role | Can Delete Resume |
| :--------------- | :---------------- |
| Master Recruiter | ✅ Yes |
| Recruiter | ✅ Yes |
| Evaluator | ❌ No |
***
### Steps to Delete an Uploaded Resume
**Step 1: Open the workflow**
Navigate to the relevant workflow from your dashboard.
**Step 2: Go to the Screening step**
Click on the **Screening** step within the workflow to view the list of candidates.
**Step 3: Open the candidate's profile**
Click on the candidate whose resume you want to delete.
**Step 4: Navigate to the Resume sub-tab**
Inside the candidate profile, go to the **Overview** tab and click on the **Resume** sub-tab. You will see:
* The uploaded resume file
* The **fitment label** (Low Fit, Potential Fit, or Strong Fit) and **reasoning summary** - these are only visible if the resume fitment feature has been enabled for your organization
**Step 5: Click the "✕" button**
On the top right corner of the resume file, click the "**✕"** button. This will delete the uploaded resume from the candidate's profile.
***
### What Happens After Deletion?
* The uploaded resume file is removed from the candidate's profile
* The fitment score and reasoning summary associated with that resume will no longer be available
* If you wish to re-evaluate the candidate, you will need to upload a new resume and allow the system to re-parse and regenerate the fitment score
***
**Important Notes**
* Deleting a resume is a **permanent action** - the file cannot be recovered once removed
* Deleting a resume does not remove the candidate from the workflow, only the resume file and its associated fitment score are deleted
* To upload a new resume for the same candidate after deletion, refer to [*How to Upload a Candidate Resume and Meet File Requirements*](https://docs.talview.com/hiring-teams/recruiter/screening/how-tos/how-to-upload-a-candidate-resume-and-meet-file-requirements)
# How to Submit an Evaluation for a Candidate as a Recruiter
Source: https://docs.talview.com/hiring-teams/recruiter/screening/how-tos/how-to-submit-an-evaluation-for-a-candidate-as-a-recruiter
This article explains how recruiters can **submit detailed evaluations for candidates within Talview's Workflow Tools platform.** Evaluations capture interview feedback, hiring recommendations, and decision rationale, helping align hiring teams and accelerate informed hiring decisions across the recruitment workflow.
## **Step-by-Step Guide**
### **1. Go to the Workflow**
* Login as a Recruiter.
* Select the workflow that contains the candidates and interviews you want to evaluate.
### **2. Open the Interview Step**
* Inside the workflow, select the **interview step** where you want to submit an evaluation for a candidate.
* Within the workflow, select the interview step where you want to submit a candidate evaluation.
### **3.** Submitting an evaluation for a candidate
* Click on a **candidate's name** to view their interview details and evaluation status.
* In the interview details side panel:
* Open the **Evaluation** tab to review or provide feedback on the candidate's interview.
* Expand the **Your Evaluation** dropdown to review or add evaluation feedback.
* Enter **detailed feedback** to support your evaluation decision.
* Click on ✔️Select/ ✖️Turned Down/ ⏸️Hold, based on your decision about the candidate.
> Upon a success notification, the evaluation is now submitted and accessible to hiring managers within the centralized workflow dashboard.
### **Tips for effective evaluations:**
* Review the candidate's assessment scores and video responses in the Overview tab before submitting your evaluation for complete context.
* Use the Hold status when you need additional information or want to discuss with the hiring team before making a final recommendation.
* Evaluations can be edited after submission—simply return to the Evaluation tab and update your feedback as needed.
# How to Upload a Candidate Resume and Meet File Requirements
Source: https://docs.talview.com/hiring-teams/recruiter/screening/how-tos/how-to-upload-a-candidate-resume-and-meet-file-requirements
When a candidate applies for a job, recruiters can upload their resume directly into a workflow. The system then parses the resume and automatically generates a fitment score based on pre-configured criteria, eliminating the need for manual screening at the top of the funnel.
***
### Step-by-step guide:
**Upload the Resume -**
There are two ways to upload a candidate's resume depending on where you are in the workflow.
* **Method 1: Using the Invite Button**
Use this method to upload a resume while adding a new candidate to the workflow.
1. Open the relevant workflow
2. Click the **Invite** button
3. Select the **Upload Resume** card
4. Choose the resume file from your device and upload it
* **Method 2: Using the Side Panel in the Screening Step**
Use this method to upload a resume for a candidate who is already in the workflow.
1. Open the relevant workflow
2. Navigate to the **Screening** step
3. Click on the candidate to open their side panel
4. Upload the resume file directly from the side panel
***
### File Requirements
| Requirement | Details |
| :---------------- | :----------------------------------- |
| Supported formats | PDF (.pdf), DOC (.doc), DOCX (.docx) |
| Maximum file size | 5 MB per resume |
| Upload limit | Bulk upload is available |
> Make sure the file is within the 5 MB size limit before uploading. If the file is too large, compress it or save it in a smaller format before trying again.
***
**Step 2: Let the System Process the Resume**
Once uploaded, the system automatically runs three steps in the background:
1. **Upload** - the file is successfully received
2. **Parse** - the system reads the resume and extracts key information, including:
* Name, email, contact number, and LinkedIn
* Education details
* Work experience
* Certifications and additional information
3. **Generate fitment** - the extracted details are compared against your configured criteria, and a fitment score with reasoning is produced
> Processing runs in the background. You can close the upload panel and continue other tasks in the workflow, just do not refresh the page until processing is complete.
***
**Step 3: View the Fitment Results**
Once processing is complete, navigate to:
**Resume Screening step → Candidate Profile → Overview tab → Resume sub-tab**
Here you will find:
* The **fitment label** (Strong Fit, Potential Fit, or Low Fit)
* A **reasoning summary** explaining why the candidate received that score
* The **resume file**, available to view, zoom in/out, and download
You can also view fitment scores directly from the list view in the **Screening** step and apply filters to sort candidates by their fitment label.
**Important Notes**
* The **5 MB file size limit** applies to each resume.
* Supported file formats are **PDF (.pdf)**, **DOC (.doc)**, and **DOCX (.docx).**
* If fitment criteria is not configured before uploading, **no fitment score will be generated.**
* Fitment criteria can be edited at any time from the **Configure Fitment** option in the workflow.
# How to use Resume Fitment to Prioritize Candidates
Source: https://docs.talview.com/hiring-teams/recruiter/screening/how-tos/how-to-use-resume-fitment-to-prioritize-candidates
Once resumes have been processed, Workflow Tools assigns each candidate a fitment based on how well their resume matches your configured criteria.
This article explains how to use the resume fitment to efficiently prioritize candidates and focus your attention where it matters most.
***
### Understanding Fitment Labels
Every processed resume is assigned one of three fitment labels:
| Fitment Label | What It Means |
| :---------------- | :---------------------------------------------------- |
| **Strong Fit** | The candidate closely matches the configured criteria |
| **Potential Fit** | The candidate meets some criteria but not all |
| **Low Fit** | The candidate does not meet most of the criteria |
These fitment levels are generated by AI based on how the candidate's resume compares against your **Essential**, **Preferred**, and **Optional** criteria - giving you an instant snapshot of candidate quality without having to read each resume manually.
***
### Step-by-Step Guide:
**Step 1: Navigate to the Screening Step**
Fitment labels are visible within the **Screening** step of the workflow as well as the **All** tab.
1. Open the relevant workflow
2. Go to the **Screening** step or the **All** tab
3. You will see all candidates listed along with their fitment labels in the list view
**Step 2: Filter Candidates by Fitment Label**
To quickly surface the most relevant candidates, use the **fitment filter** in the list view.
1. Click on the **filter** option in the list view
2. Select the fitment label(s) you want to focus on - for example, filter by **Strong Fit** to see only your top candidates
3. The list will update to show only candidates matching your selected filter
> This is especially useful when you have many applicants and want to quickly identify who to move forward with in the hiring process.
**Step 3: Review the Reasoning Before Making a Decision**
A fitment label alone is a starting point - the **reasoning summary** inside each candidate's profile gives you the full picture.
To view the reasoning:
1. Click on a candidate from the list
2. Go to the **Overview** tab → **Resume** sub-tab
3. Read the AI-generated reasoning that explains why the candidate was scored the way they were
This is particularly useful for **Potential Fit** candidates, where the reasoning can help you decide whether to move them forward or not based on which criteria they met and which they didn't.
**Step 4: Review the Resume Directly**
Alongside the fitment label and reasoning, the candidate's resume file is available in the same tab. You can:
* **View** it inline without leaving the platform
* **Zoom in or out** for easier reading
* **Download** it to your device if needed
This means you have everything in one place - the fitment, the reasoning, and the actual resume, to make a confident, informed decision.
***
### Who Can Use Fitment to Prioritize Candidates?
| Role | Can Filter by Fitment | Can View Reasoning | Can Evaluate |
| :--------------- | :-------------------- | :----------------- | :----------- |
| Master Recruiter | ✅ Yes | ✅ Yes | ✅ Yes |
| Recruiter | ✅ Yes | ✅ Yes | ✅ Yes |
| Evaluator | ✅ Yes | ✅ Yes | ✅ Yes |
**Note:**
Evaluators can use the fitment score and reasoning as a decision-making aid when assessing candidates assigned to them, but cannot modify configurations or settings.
# Screening call to a candidate
Source: https://docs.talview.com/hiring-teams/recruiter/screening/how-tos/screening-call-to-a-candidate
This article provides step-by-step instructions for placing screening calls to candidates using Talview's Workflow tools. Screening calls are essential for initial candidate evaluation and help streamline the recruitment process.
***
## Steps to Screen a Call
### 1. Access the workflow dashboard:
* Navigate to the **Workflows** section from the side navigation panel.
* Choose the appropriate workflow containing your candidate list.
* Select the **candidate** you want to screen a call with.
### 2. Viewing candidate’s profile:
* In the candidate’s profile, locate the **Call button** that’s right next to email button.
* Connect with the candidate directly by using the **Call button** to initiate a conversation.
### 3. Initiate the Screening call:
* Confirm to connect with the candidate, select **Yes Call** to start the conversation.
* Enable your **microphone** to effortlessly manage noise or to begin your conversation.
### **Before You Begin**
Ensure you have a stable internet connection and are logged into your Talview account with the necessary permissions to conduct screening calls.
# Sharing Candidate Profiles with Hiring Managers/ Evaluators
Source: https://docs.talview.com/hiring-teams/recruiter/screening/how-tos/sharing-candidate-profiles-with-hiring-managers-evaluators
This article explains how to assign an evaluator for a specific interview stage within a recruitment workflow, ensuring a streamlined, collaborative hiring process. Using **Talview Workflow Tools** centralized candidate data and automation features, recruiters can seamlessly facilitate evaluation and decision-making to enhance hiring efficiency and alignment.
## **Step-by-Step Guide**
### **1. Go to the Workflow**
* Login as a Recruiter.
* Select the workflow that contains the interviews and candidates requiring evaluation.
### **2. Open the Interview step**
* Inside the workflow, select the interview step where you want to assign an evaluator.
* This opens the **Interview Dashboard**, where all candidates for that step are listed.
### **3. Assigning an evaluator**
* Select a candidate from the Interview Dashboard to open their interview details side panel.
* Navigate to the **Evaluation** tab within the side panel.
* Under **Assign evaluator** panel, Click the dropdown to *add an evaluator.*
* Click **Assign** to save and finalize the assignment.
* The assigned evaluator will receive an email notification with direct access to the evaluation form.
### **Tips for efficient evaluator assignment:**
* Assign evaluators early in the interview process to avoid scheduling delays and ensure timely feedback.
* Use bulk actions to assign the same evaluator to multiple candidates at once.
* Evaluators receive instant email notifications with direct access to evaluation forms—no manual follow-up needed.
* Track evaluator activity in the Interview Dashboard to monitor completion status and send reminders if needed.
# Uploading a Resume Against the Candidate
Source: https://docs.talview.com/hiring-teams/recruiter/screening/how-tos/uploading-a-resume-against-the-candidate
Uploading a resume against a candidate in **Talview’s Workflow Tools** platform is a straightforward process designed to centralize candidate information and streamline recruitment efforts.
This feature allows recruiters to efficiently attach relevant resumes to a candidate’s profile, ensuring that all documents are securely stored and easily accessible for evaluation and decision making.
## **Step-by-Step Guide**
### **1. Go to the Workflow**
* Login as a Recruiter.
* Open the workflow to access and manage candidate's profile.
### **2. Open the Interview Step**
* Navigate to the **Screening** step to access the candidate's profile.
* Select a candidate, to view their profile.
### **3. Upload the resume**
* In the application side panel:
* Click on the Resume drop down to upload the candidate's **resume.**
* Click **Upload Resume** to add the candidate's resume file.
* Once you upload your resume, you’ll get a notification, **“Resume uploaded successfully”.**
* To the view the resume,
* Navigate to the **Resume Screening** interview step.
* Next to the candidate’s name click on **View Resume.**
**Note:**
1. The maximum file size for a resume is **typically 2–5MB**, although keeping resume files **under 1MB** is considered best practice to avoid upload issues.
2. The resume file must be in a **PDF** format.
# Viewing candidate’s call history
Source: https://docs.talview.com/hiring-teams/recruiter/screening/how-tos/viewing-candidates-call-history
When conducting screening calls through Talview's Workflow tools, recruiters and hiring managers often need to access a candidate's call history to review previous interactions, track communication patterns, and make informed decisions about the hiring process.
This article provides a comprehensive step-by-step guide to help you locate, view, and interpret candidate call history.
***
## Steps to view candidate’s call history
### 1. Access the workflow dashboard:
* Navigate to the **Workflows** section from the side navigation panel.
* Choose the appropriate workflow containing your candidate list.
* Select the **candidate**, whose call history you want to view.
### 2. Viewing the call history:
* In the candidate’s profile, locate the **Call History** option to review previous interactions and to make informed decisions about the hiring process.
* You can play the **Call recordings** to delve into the details of each discussion and assess the current status of every call.
# What should I do if the wrong evaluator is assigned?
Source: https://docs.talview.com/hiring-teams/recruiter/workflow-automation/diagnostics/what-should-i-do-if-the-wrong-evaluator-is-assigned
Evaluator auto-assignment is driven by **automation rules configured at the assessment step**. If an unexpected evaluator is assigned, it is usually due to rule configuration, evaluator selection logic, or timing of assignment actions.
***
## 🔎 Troubleshooting Common Issues
| **What might be wrong** | **How to fix it** |
| :--------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Wrong evaluator selected in the automation rule | Open the `assessment step → Automation side panel → edit the rule and verify the evaluators` selected under **Auto-assign evaluator**. |
| Automation rule applied to the wrong assessment step | Confirm the rule is created for the **correct assessment step**. Rules do not apply across steps. |
| Conflicting automation rules | Check **Current Automations** for multiple active rules that include evaluator assignment and deactivate unnecessary ones. |
| Evaluator manually changed after auto-assignment | Verify whether the evaluator was reassigned manually after the automation ran. |
| Candidate already had an evaluator assigned | If an evaluator was previously assigned, the rule condition **Evaluator not assigned** may not behave as expected. Remove existing assignments and retry. |
| Rule edited after assignment occurred | Automation rules do not retroactively update evaluator assignments. Changes apply only to future candidates or invites. |
| Assessment invite resent after rule update | Resending invites after modifying rules may trigger a different evaluator assignment if rule conditions differ. |
### Additional Tips
* **Review Current Automations regularly**
Always check the **Current Automations** section to ensure only the intended rules are active.
* **Test with a fresh candidate**
Add a new candidate to the assessment step and send the assessment invite to validate correct evaluator assignment.
* **Use clear naming or documentation**
When multiple recruiters manage the same workflow, document automation intent to avoid accidental evaluator changes.
* **Avoid overlapping rules**
Keep evaluator assignment logic simple to reduce unexpected behavior.
# Why are evaluators not auto-assigned to the assessment?
Source: https://docs.talview.com/hiring-teams/recruiter/workflow-automation/diagnostics/why-are-evaluators-not-auto-assigned-to-the-assessment
Talview allows recruiters to configure **automation rules** at the assessment step to automatically assign evaluators when candidates are added to the step.
If evaluators are not auto-assigned, it is usually due to rule configuration, trigger conditions not being met, or rule activation issues.
***
## 🔎 Troubleshooting Common Issues
| **What might be wrong** | **How to fix it** |
| :------------------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------- |
| Automation rule is not activated | Open the assessment step → Automation side panel → ensure the rule is visible in the current automations section in the side panel |
| Rule created for the wrong assessment step | Confirm the automation is configured for the **correct assessment step** in the workflow. Automations are step-specific. |
| Incorrect trigger selected | Ensure the trigger is set to **Assessment invite sent**. Other triggers will not auto-assign evaluators on candidate tagging. |
| Candidate assessment invite not sent | Auto-assignment works only when the **assessment invite is sent**. Send the invite to trigger the rule. |
| Rule created after candidates were added | Automation rules apply **only to future actions**. Re-add the candidate to the assessment step or resend the invite. |
| User does not have permission to assign evaluators | Ensure the logged-in user has recruiter-level permissions to configure and apply evaluator assignments. |
### Additional Tips
* **Check Current Automations**
Open the automation side panel and verify the rule appears under **Current Automations** for the assessment step.
* **Test with a new candidate**
Add a new candidate to the assessment step and send the assessment invite to confirm the rule is working as expected.
* **Avoid conflicting rules**
Ensure there are no multiple automation rules that may override or conflict with evaluator assignment behavior.
* **Refresh after activation**
Refresh the page after activating the rule to ensure it is fully applied.
# Assessment - Configuring Candidate Reminder Automation Rules
Source: https://docs.talview.com/hiring-teams/recruiter/workflow-automation/how-tos/assessment-configuring-candidate-reminder-automation-rules
This article explains how recruiters and master recruiters can create an automation rule in the **Assessment step** of a workflow to remind candidates to take their assessment after an invite has been sent.
It provides a clear step-by-step guide on configuring triggers, conditions, and actions using Workflow Automation.
***
## Step-by-step Guide
### Step 1: Access the Workflow and Assessment Step
From the main menu, navigate to the **Workflows** section.
Select the workflow where you want to configure candidate reminder automation.
Open the **Assessment** step within the workflow.
> Note: This automation is created only for the selected workflow-step and does not apply globally.
### Step 2: Open Workflow Automation Panel
In the Assessment step, locate the **Automation icon** placed beside the **Filters** option.
Click on the Automation icon to open the automation **side panel**.
### Step 3: Create a New Automation Rule
From the side panel, click **+ Create New** to begin setting up a new automation rule.
### Step 4: Configure Trigger (Start When)
Under **Trigger (Start When)**, select:
* **Candidate in invited status**
This trigger ensures the automation is evaluated for candidates who have been invited but have not yet started or completed the assessment.
### Step 5: Configure Condition (Check If)
Under **Conditions (Check If)**, select:
* **Time from invite sent**
From the list, choose one of the following intervals based on when you want the reminder to be sent:
* **24 hours**
* **48 hours**
* **72 hours**
This condition ensures reminders are sent only after the selected time has passed since the assessment invite was sent.
### Step 6: Configure Action (Do This)
Under **Actions (Do this)**, select:
* **Remind candidate via Email**
This action automatically sends an email reminder to the candidate, prompting them to complete the assessment.
### Step 7: Activate the Automation
Review the trigger, condition, and action to ensure all details are correctly configured.
Click **Activate** to enable the automation.
### Step 8: Verify Automation Creation
Once activated, the automation will appear under the **Current Automations** section within the Assessment step.
This confirms that the reminder rule is active and will run based on the configured time interval.
By enabling this automation, recruiters can improve assessment completion rates, reduce manual follow-ups, and ensure a smoother candidate experience.
***
# Assessment - Configuring Evaluator Reminder Automation Rules
Source: https://docs.talview.com/hiring-teams/recruiter/workflow-automation/how-tos/assessment-configuring-evaluator-reminder-automation-rules
This article explains how recruiters and master recruiters can create an automation rule in the **Assessment step** of a workflow to remind evaluators to complete evaluations after a candidate has completed an assessment.
It provides a clear step-by-step guide on configuring triggers, multiple conditions, and actions using Workflow Automation.
***
## Step-by-step Guide
### Step 1: Access the Workflow and Automation Step
From the main menu, navigate to the **Workflows** section.
Select the workflow where you want to configure the evaluation reminder automation.
Open the **Assessment** step within the workflow.
> Note: This automation is created only for the selected workflow-step and does not apply globally.
### Step 2: Open Workflow Automation Panel
In the Automation step, locate the **Automation icon** placed beside the **Filters** option.
Click on the Automation icon to open the automation **side panel**.
### Step 3: Create a New Automation Rule
From the side panel, click “**+ Create New”** to begin setting up a new automation rule.
### Step 4: Configure Trigger (Start When)
Under **Trigger (Start When)**, select:
* **Candidate assessment completed**
This trigger ensures the automation is evaluated once a candidate finishes their assessment.
### Step 5: Configure Conditions (Check If)
Under **Conditions (Check If)**, configure the following conditions:
1. Select the first condition:
* **Evaluation not completed**
2. Click **Add condition** to include an additional rule:
* **Time from assessment completion**
From the dropdown, choose one of the following intervals based on when you want the evaluation reminder to be sent:
* **24 hours**
* **48 hours**
* **72 hours**
These conditions ensure reminders are sent only when evaluations remain incomplete after the selected time interval from assessment completion.
### Step 6: Configure Action (Do This)
Under **Actions (Do this)**, select:
* **Remind evaluator via Email**
This action automatically sends an email reminder to the assigned evaluator to complete the pending evaluation.
### Step 7: Activate the Automation
Review the trigger, conditions, and action to ensure accuracy.
Click **Activate** to enable the automation.
### Step 8: Verify Automation Creation
Once activated, the automation will appear under the **Current Automations** section within the Automation step.
This confirms that the reminder rule is active and will execute based on the configured time intervals.
By using this automation, recruiters can proactively follow up on pending evaluations after assessments, ensuring faster decision-making and improved workflow efficiency.
***
# Assessment - Setting Up Auto-Assignment of Evaluators
Source: https://docs.talview.com/hiring-teams/recruiter/workflow-automation/how-tos/assessment-setting-up-auto-assignment-of-evaluators
This article explains how recruiters and master recruiters can create an automation rule in the **Assessment step** of a workflow to automatically assign evaluators to candidates when an assessment invite is sent.
It provides a clear step-by-step guide on configuring triggers, conditions, and actions using Workflow Automation.
***
## Step-by-step Guide
### Step 1: Access the Workflow and Assessment Step
From the main menu, navigate to the **Workflows** section.
Select the workflow where you want to configure evaluator auto-assignment.
Open the **Assessment** step within the workflow.
> Note: This automation is created only for the selected workflow-step and does not apply globally.
### Step 2: Open Workflow Automation Panel
In the Assessment step, locate the **Automation icon** placed beside the **Filters** option.
Click on the Automation icon to open the automation **side panel**.
### Step 3: Create a New Automation Rule
From the side panel, click **+ Create New** to begin setting up a new automation rule.
### Step 4: Configure Trigger (Start When)
Under **Trigger (Start When)**, select:
* **Assessment invite sent**
This trigger ensures the automation is evaluated as soon as an assessment invitation is sent to the candidate.
### Step 5: Configure Condition (Check If)
Under **Conditions (Check If)**, select:
* **Evaluator not assigned**
This condition ensures that the automation runs only for candidates who do not already have an evaluator assigned.
### Step 6: Configure Action (Do This)
Under **Actions (Do this)**, select:
* **Auto-assign evaluator**
From the evaluator dropdown, choose one or more evaluator(s) who should be automatically assigned.
> Tip: Selecting multiple evaluators helps distribute evaluations evenly and avoids overloading a single evaluator.
### Step 7: Activate the Automation
Review the trigger, condition, and action to ensure accuracy.
Click **Activate** to enable the automation.
### Step 8: Verify Automation Creation
Once activated, the automation will appear under the **Current Automations** section within the Assessment step.
This confirms that the rule is active and will execute automatically when assessment invites are sent.
By using this automation, recruiters can ensure evaluators are assigned at the right time, reduce manual intervention, and streamline the assessment evaluation process.
***
# How to configure auto-assign rules for Assessment steps?
Source: https://docs.talview.com/hiring-teams/recruiter/workflow-automation/how-tos/how-to-configure-auto-assign-rules-for-assessment-steps
Workflow Tools platform allows recruiters to configure **automation rules** at the assessment step level within a workflow. Using these rules, evaluators can be automatically assigned to candidates when specific conditions are met.
A common use case is **auto-assigning evaluators as soon as a candidate is tagged to an assessment step**, ensuring no candidate remains unassigned and evaluations start without delay.
Each automation rule consists of:
* **Trigger** – When the rule should run
* **Condition(s)** – Criteria that must be met
* **Action(s)** – What should happen when the trigger and conditions are satisfied
This article provides a step-by-step guide to automatically assign evaluators to candidates as soon as they are added to an assessment step, reducing manual effort and ensuring timely evaluations.
***
## Step-by-step Guide
### Step 1: Access the Workflow
* Navigate to the **Workflows** section from the main menu.
* Open the workflow where you want to configure the assessment automation.
### Step 2: Navigate to the Assessment Step
* Click on the relevant **Assessment step** within the workflow.
* In the assessment step view, locate and click on the Automation icon next to the **Filters** option to get started.
### Step 3: Create a New Automation Rule
* Click **Create New** to add a new rule.
* You will be prompted to configure the trigger, conditions, and actions.
### Step 4: Configure the Trigger
* In the **Trigger** section, select:
**Assessment invite sent**
This ensures the rule runs when a candidate is added to the assessment step and the assessment invite is sent.
### Step 5: Configure the Condition
* In the **Condition** section, select:
**Evaluator not assigned**
This ensures the rule applies only to candidates who do not already have an evaluator assigned.
### Step 6: Configure the Action
* In the **Action** section, select:
**Auto-assign evaluator**
* Search for and add one or more evaluator(s) from the list.
* These evaluators will be automatically assigned when the rule is triggered.
### Step 7: Activate the Rule
* Review the rule configuration.
* Click **Activate** to enable the rule.
Once activated, the rule is applied **only to this assessment step within the selected workflow**.
### Step 8: Viewing Created Automations
* Once the automation is created and activated, it will appear under the **Current Automations** section in the automation side panel.
* Recruiters can view, manage, or deactivate existing rules from this section at any time.
### How the Auto-Assign Rule Works
* A candidate is added to the assessment step.
* The **assessment invite is sent**.
* If **no evaluator is already assigned**, the rule triggers automatically.
* The configured evaluator(s) are assigned to the candidate without any manual intervention.
***
# How to Delete a Workflow Automation?
Source: https://docs.talview.com/hiring-teams/recruiter/workflow-automation/how-tos/how-to-delete-a-workflow-automation
This article explains how recruiters and master recruiters can delete an existing automation rule from a specific step within a workflow.
It provides a clear step-by-step guide to removing automations that are no longer required.
***
## Step-by-step Guide
### Step 1: Access the Workflow and Relevant Step
From the main menu, navigate to the **Workflows** section.
Select the workflow where the automation rule exists.
Open the workflow step (for example, Screening or Assessment) where the automation was created.
> Note: Automation rules are managed at the workflow-step level.
### Step 2: Open Workflow Automation Panel
In the selected step, locate the **Automation icon** placed beside the **Filters** option.
Click on the Automation icon to open the automation **side panel**.
### Step 3: Locate the Automation Rule
In the side panel, scroll to the **Current Automations** section.
Identify the automation rule you want to delete.
Each automation is displayed as a card with its trigger, conditions, and action summary.
### Step 4: Delete the Automation Rule
On the respective automation card, click the **three-dot menu**.
Select **Delete** from the available options.
### Step 5: Confirm Deletion
A confirmation prompt will appear.
Click **Confirm** again to confirm the action.
Once confirmed, the automation rule will be permanently removed from the selected workflow step.
### Step 6: Verify Automation Removal
After deletion, the automation will no longer appear under the **Current Automations** section.
This confirms that the rule has been successfully removed and will no longer execute for candidates in this step.
By deleting unused or outdated automation rules, recruiters can keep workflows clean, accurate, and aligned with current hiring requirements.
***
# Screening - Configuring Evaluator Reminder Automation Rules
Source: https://docs.talview.com/hiring-teams/recruiter/workflow-automation/how-tos/screening-configuring-evaluator-reminder-automation-rules
This article explains how recruiters and master recruiters can create an automation rule in the **Screening step** to send reminder emails to evaluators when an evaluation is not completed within a defined time period.
It provides a step-by-step guide on configuring triggers, multiple conditions, and actions using Workflow Automation.
***
## Step-by-step Guide
### Step 1: Access the Workflow and Screening Step
From the main menu, navigate to the **Workflows** section.
Select the workflow where you want to configure evaluator reminder automation.
Open the **Screening** step within the workflow.
> Note: This automation is created only for the selected workflow-step and does not apply globally.
### Step 2: Open Workflow Automation Panel
In the Screening step, locate the **Automation icon** placed beside the **Filters** option.
Click on the Automation icon to open the automation **side panel**.
### Step 3: Create a New Automation Rule
From the side panel, click “**+ Create New”** to begin setting up a new automation rule.
### Step 4: Configure Trigger (Start When)
Under **Trigger (Start When)**, select:
* **Evaluation not completed**
This trigger ensures the automation is evaluated when an assigned evaluator has not completed the screening evaluation.
### Step 5: Configure Conditions (Check If)
Under **Conditions (Check If)**, configure the following conditions:
1. Select the first condition:
* **Evaluation status is Pending**
2. Click **Add condition** to include an additional rule:
* **Time since evaluator added**
From the dropdown, choose one of the following intervals based on when you want the reminder to be sent:
* **24 hours**
* **48 hours**
* **72 hours**
These conditions together ensure reminders are sent only when evaluations remain pending beyond the selected time threshold.
### Step 6: Configure Action (Do This)
Under **Actions (Do this)**, select:
* **Remind evaluator via Email**
This action automatically sends an email reminder to the assigned evaluator to complete the pending evaluation.
### Step 7: Activate the Automation
Review the trigger, conditions, and action to ensure all details are correctly configured.
Click **Activate** to enable the automation.
### Step 8: Verify Automation Creation
Once activated, the automation will appear under the **Current Automations** section within the Screening step.
This confirms that the reminder rule is active and will run based on the configured time intervals.
By enabling this automation, recruiters can ensure timely evaluation completion, reduce manual follow-ups, and maintain consistent screening turnaround times.
***
# Screening - Setting up Auto-Assignment of Evaluators
Source: https://docs.talview.com/hiring-teams/recruiter/workflow-automation/how-tos/screening-setting-up-auto-assignment-of-evaluators
This article explains how recruiters and master recruiters can create an automation rule in the **Screening step** to automatically assign evaluators to candidates when they enter the screening stage within a workflow.
It provides a step-by-step guide on configuring triggers, conditions, and actions using Workflow Automation.
***
## Step-by-step Guide
### Step 1: Access the Workflow and Screening Step
From the main menu, navigate to the **Workflows** section.
Select the workflow where you want to configure evaluator auto-assignment.
Open the **Screening** step within the workflow.
> Note: This automation is created only for the selected workflow-step and does not apply globally.
### Step 2: Open Workflow Automation Panel
In the Screening step, locate the **Automation icon** placed beside the **Filters** option.
Click on the Automation icon to open the automation **side panel**.
### Step 3: Create a New Automation Rule
From the side panel, click “**+ Create New”** to begin setting up a new automation rule.
### Step 4: Configure Trigger (Start When)
Under **Trigger (Start When)**, select:
* **Candidate enters screening step – Evaluator Assignment**
This ensures the automation is initiated as soon as a candidate reaches the Screening step.
### Step 5: Configure Condition (Check If)
Under **Conditions (Check If)**, select:
* **Evaluator not assigned**
This condition ensures the automation runs only for candidates who do not already have an evaluator assigned.
### Step 6: Configure Action (Do This)
Under **Actions (Do this)**, select:
* **Auto-assign evaluator**
From the evaluator dropdown, choose one or more evaluator(s) who should be automatically assigned to eligible candidates.
> Tip: You can select multiple evaluators to distribute assignments evenly.
### Step 7: Activate the Automation
Review the configured trigger, condition, and action to ensure accuracy.
Click **Activate** to enable the automation.
### Step 8: Verify Automation Creation
Once activated, the newly created automation will appear under the **Current Automations** section within the Screening step.
This confirms that the rule is active and will execute for candidates entering this step.
By using this automation, recruiters can eliminate manual evaluator assignment in the Screening step, ensuring faster and more consistent candidate processing.
***
# Workflow Automation Rules Guide
Source: https://docs.talview.com/hiring-teams/recruiter/workflow-automation/how-tos/workflow-automation-rules-guide
This guide explains the available Automation rules in Workflow Tools. Use this when creating automation rules to understand trigger-condition-action combinations for each step.
***
### Rule Structure
Every automation rule requires:
* **1 Trigger** (unique per rule - when something happens)
* **1+ Conditions** (filters that must be met)
* **1+ Actions** (what happens automatically)
***
### Screening Step
| # | Trigger | Conditions | Actions | Use Case |
| :- | :-------------------------------- | :---------------------------------------------------- | :--------------------------- | :-------------------------------------------------------------- |
| 1 | Candidate added to screening step | Evaluator not assigned | Auto-assign evaluator | Ensure every candidate gets an evaluator immediately |
| 2 | Candidate added to screening step | Evaluation not completed + Time delay: 24/48/72 hours | Remind evaluator via email | Nudge evaluators who haven't completed screening evaluations |
| 3 | Candidate enters screening step | Assessment must be available in workflow | Auto-move to assessment step | Fast-track candidates to assessment without manual intervention |
***
### Assessment Step
| # | Trigger | Conditions | Actions | Use Case |
| :- | :---------------------------------------------- | :----------------------------------------------------- | :----------------------------- | :--------------------------------------------------- |
| 1 | Candidate assessment completed | Time from completion: 24/48/72 hours | Remind evaluator via email | Nudge evaluators to review completed assessments |
| 2 | Assessment invite sent (candidate reminder) | No response after selected invite time: 24/48/72 hours | Remind candidate via email | Nudge candidates who haven't started assessment |
| 3 | Assessment invite sent (evaluator assignment) | Evaluator not assigned | Auto-assign evaluator | Ensure evaluator is ready to review post-completion |
| 4 | Assessment invite sent (unresponsive candidate) | Assessment not completed + Time delay: 3/5/7 days | Update status to 'Turned Down' | Auto-reject candidates who don't complete assessment |
***
### Interview Step
**Post-Interview Evaluation**
| # | Trigger | Conditions | Actions | Use Case |
| - | :----------------------- | :------------------------------------------- | :------------------------- | :------------------------------------------------------ |
| 1 | Evaluation not completed | Time since interview ended: 6/24/48/72 hours | Remind evaluator via email | Nudge interviewers to submit post-interview evaluations |
**Pre-Interview Reminders**
| # | Trigger | Conditions | Actions | Use Case |
| :- | :----------------------------------- | :------------------------------------------------------------------------------------------------------------------- | :------------------------- | :--------------------------------------- |
| 1 | Pre-interview reminder - Interviewer | Interview status: Scheduled And RSVP status: No response/Propose new time/Tentative And Time before start: 24h or 1h | Remind evaluator via email | Notify interviewer of upcoming interview |
| 2 | Pre-interview reminder - Candidate | Interview status: Scheduled And RSVP status: No response/Propose new time/Tentative And Time before start: 24h or 1h | Remind candidate via email | Notify candidate of upcoming interview |
**Interview No-Show Escalations**
| # | Trigger | Conditions | Actions | Use Case |
| :- | :------------------------------ | :------------------------------------------------------------------------------------------------------------------------------------------------------- | :---------------------------------------------------- | :-------------------------------------------------------------------- |
| 1 | Interviewer joins the interview | Interview status is In Progress And Candidate RSVP Status: Propose New Time, Declined, Accepted, Tentative, No Response And Candidate has Not Joined | Remind candidate via Email / Remind candidate via SMS | Remind candidate to join when interviewer is already in the interview |
| 2 | Candidate joins the interview | Interview status is In Progress And Interviewer RSVP Status: Propose New Time, Declined, Accepted, Tentative, No Response And Interviewer has Not Joined | Remind evaluator via Email / Remind evaluator via SMS | Remind interviewer to join when candidate is already in the interview |
| 3 | Interview with no participant | Interview status is Scheduled And Time since interview started: 5/10 mins | Send escalation to organiser | Alert when no one joins scheduled interview |
**Post-Interview Notifications**
| # | Trigger | Conditions | Actions | Use Case |
| :- | :----------------------------------- | :------------------------------------------ | :--------------------------- | :-------------------------------------------------- |
| 1 | Interview ended - Notify organiser | Only 1 participant attended | Notify organiser via email | Alert when interview completes with 1 attendee only |
| 2 | Interview ended - Notify organiser | Candidate + at least 1 interviewer attended | Notify organiser via email | Confirm successful interview completion |
| 3 | Interview ended - Notify organiser | Both no-show | Notify organiser via email | Alert when neither party attends |
| 4 | Interview ended - Notify interviewer | Candidate status: Attended/No show | Notify interviewer via email | Inform interviewer of candidate attendance |
| 5 | Interview ended - Notify interviewer | Interviewer status: Attended/No show | Notify interviewer via email | Confirm interviewer's own attendance |
***
### Rule Management
Available across all steps (Screening, Assessment, Interview):
* **Edit:** Modify trigger, conditions, or actions
* **Disable:** Pause rule without deleting
* **Delete:** Permanently remove rule
***
### Upcoming Automations
Not yet available in production:
* **Registration form triggers:** Auto-move on form submission
* **Resume fitment-based routing:** Auto-move based on Strong/Potential/Low Fit scores
* **Evaluation recommendation sync:** Auto-update candidate status based on Select/Hold/Turn Down recommendations
# How to resolve issues with formatting in the JD editor?
Source: https://docs.talview.com/hiring-teams/recruiter/workflow-management/diagnostics/how-to-resolve-issues-with-formatting-in-the-jd-editor
When adding *Job Description (JD)* in **Talview’s Workflow Tools platform**, users may sometimes encounter formatting issues such as misplaced alignment, overlapping text, or loss of structure after pasting content. These problems typically arise from copying text from external sources or from using unsupported formatting styles.
The table below outlines common issues and quick ways to resolve them.
***
## 🔎 Troubleshooting Common Issues
| **What might be wrong** | **How to fix it** |
| :------------------------------------------------------------------------------------ | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Extra line breaks, blank spaces, or paragraph gaps appear | **To delete redundant line breaks manually:** Place your cursor at the beginning of the unwanted blank line and press` Backspace (Windows) or Delete (Mac)` until the gap closes. \*\*For controlled spacing: \*\* Use `Shift+Enter (Windows)` or `Shift+Return (Mac) `to create a single line break without adding extra paragraph spacing. |
| Bulleted or numbered lists do not appear correctly | Remove the copied list and recreate it using the editor’s inbuilt **bullet/numbered list tool** to ensure consistency with supported styles. |
| Fonts, colors, or font sizes look mismatched | Reset formatting using the toolbar and stick to the default font settings of the JD editor for a clean, professional look. |
| Heading levels don’t maintain hierarchy (all text looks like the same size) | Apply heading styles (H1, H2, H3) directly from the toolbar instead of relying on pasted formatting. |
| Content pasted from Word or PDF introduces background colors or tables that don’t fit | Paste content as **plain text** first, then reformat using the JD editor options. This prevents hidden styles from carrying over. |
### **Additional Tips**
* If formatting repeatedly fails, check your browser’s cache and refresh, as temporary glitches may affect how formatting is rendered.
* Stick to **simple structures** (headings, bullets, short paragraphs) for better readability and system compatibility.
* Always copy and paste content first into a **plain text editor (like Notepad/ TextEdit)** before adding it into Talview’s JD editor. This ensures no hidden formatting is carried over.
# Why are filtered results not matching with the expected candidates?
Source: https://docs.talview.com/hiring-teams/recruiter/workflow-management/diagnostics/why-are-filtered-results-not-matching-with-the-expected-candidates
The **All view** shows candidates across every step in a workflow and supports **step-level status filters**. Since these filters reflect a candidate’s **current step and current status only**, misunderstandings around filter scope or status behavior can lead to unexpected results.
***
## 🔎 Troubleshooting Common Issues
| **What might be wrong** | **How to fix it** |
| :------------------------------------------ | :---------------------------------------------------------------------------------------------------------------- |
| Incorrect workflow step selected in filters | Verify that the selected **step** matches where the candidate is currently placed in the workflow. |
| Step-level status misunderstood | Ensure the selected **status belongs to the chosen step**. Status options vary by step (assessment vs interview). |
| Candidate has moved to another step | Check the candidate timeline to confirm they haven’t progressed to a different step after filtering. |
| Multiple step filters applied together | Remove extra step selections and apply filters for **one step at a time** to validate results. |
| Expecting historical statuses | All view filters show **current status only**, not past or previous step statuses. |
| Recently updated candidate status | Refresh the page and reapply filters to ensure the latest status is reflected. |
| Filters not reset from previous search | Use **Reset/Clear filters** before applying a new filter combination. |
| Expecting Screening-only behavior | All view filtering logic differs from Screening step filters. Use step-specific views if needed. |
### Additional Tips
* **Validate candidate location first**
Search for the candidate by name and confirm their **current step and status** before applying filters.
* **Apply filters incrementally**
Start with a step filter, then add status filters to narrow down results gradually.
* **Understand step-specific statuses**
Interview steps focus on scheduling and attendance (Scheduled, No show, Completed), while assessment steps focus on progress and evaluation (Invited, In progress, Evaluated).
* **Refresh after bulk actions**
If candidates were recently moved, evaluated, or scheduled in bulk, refresh the All view before filtering.
# Why are Workflow templates not loading or unavailable?
Source: https://docs.talview.com/hiring-teams/recruiter/workflow-management/diagnostics/why-are-workflow-templates-not-loading-or-unavailable
Recruiters rely on workflow templates to quickly set up standardized hiring processes across multiple job roles, but occasionally these templates may fail to load or appear unavailable within the Workflow Tools platform.
This article helps recruiters identify the root causes of template loading issues and provides step-by-step solutions to restore access to workflow templates.
## 🔎 Troubleshooting Common Issues
| **What might be wrong** | **How to fix it** |
| :----------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Browser cache or session issues | Clear the browser cache and cookies, then log out and log back into the Workflow Tools platform. |
| Network connectivity problems | Test the internet connection stability and speed. Try refreshing the page or accessing the platform from a different network. If the issue persists, check with the IT team for firewall or proxy restrictions blocking template data. |
| Platform maintenance or service disruption | Check the Talview Help Center or contact support to confirm if scheduled maintenance or service issues are affecting template availability. Wait for the maintenance window to complete or for service restoration. |
| Corrupted template configuration | Report the specific template that fails to load to the Talview support team. |
### **Additional Tips**
* Refresh the browser page before attempting to load templates again, as temporary glitches may resolve with a simple refresh.
* Keep a record of which specific templates are failing to load, including template names and error messages, to provide detailed information when reporting to support.
* Ensure that the workflow being created aligns with the scope and type of templates available, as application-scoped workflows may only display compatible templates.
# Why is JD not visible after workflow creation?
Source: https://docs.talview.com/hiring-teams/recruiter/workflow-management/diagnostics/why-is-jd-not-visible-after-workflow-creation
After creating a workflow in **Talview’s Workflow Tools**, some recruiters may notice that the *job description (JD)* is not displayed. This issue can arise due to configuration settings, missing data, or visibility restrictions in the workflow.
Below is a quick diagnostic guide to help you identify the problem and resolve it efficiently.
***
## 🔎 Troubleshooting Common Issues
| **What might be wrong** | **How to fix it** |
| :--------------------------------------- | :-------------------------------------------------------------------------------------------------------------------- |
| Browser or cache-related display errors. | Clear browser cache, refresh the page, or try accessing Talview from a different browser to rule out display glitches |
| JD not visible after workflow creation | Always double-check that the JD is filled in before publishing a workflow. |
### **Additional Tip**
Use a standardized workflow template that includes mandatory components like JD fields for consistency.
# Why is the candidate filter not visible in “All” view?
Source: https://docs.talview.com/hiring-teams/recruiter/workflow-management/diagnostics/why-is-the-candidate-filter-not-visible-in-all-view
The **All view** in a workflow provides a consolidated list of candidates across all steps. It also supports **candidate filters**, including step-wise status filters. If the Filters option is not visible, it is typically due to permission settings, navigation context, or UI-related issues.
***
## 🔎 Troubleshooting Common Issues
| **What might be wrong** | **How to fix it** |
| :---------------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------- |
| User role does not have filter access | Ensure you are logged in as a **Recruiter** or **Master Recruiter**. Contact your Tenant Admin if filter access needs to be enabled. |
| Not inside the All view | Confirm that the **All** tab is selected within the workflow. Filters are not shown in step-specific views. |
| Workflow did not load completely | Refresh the page and wait for the candidate list to fully load before checking for filters. |
| Screen resolution or browser zoom hides filters | Reduce browser zoom, scroll horizontally/vertically, or switch to full-screen mode to locate the Filters option. |
| Temporary UI or cache issue | Clear browser cache and reload the workflow. |
| Unsupported or outdated browser | Use a supported browser (Chrome recommended) and ensure it is updated to the latest version. |
| Embedded or restricted workflow view | Open the workflow in a full view rather than an embedded or limited-access view. |
### Additional Tips
* **Compare with step views**
Filters in the **All view** are different from Screening or Assessment step filters. Ensure you are looking for **All-view–specific filters**.
* **Check role-based differences**
If other recruiters can see filters in the same workflow and you cannot, it likely indicates a role or permission issue.
* **Try another workflow**
Open a different workflow’s All view to determine whether the issue is workflow-specific or user-specific.
* **Re-enter the workflow**
Exit the workflow and reopen it to reinitialize the All view UI.
# Why is the candidate not appearing in the selected workflow?
Source: https://docs.talview.com/hiring-teams/recruiter/workflow-management/diagnostics/why-is-the-candidate-not-appearing-in-the-selected-workflow
When recruiting teams use Talview's Workflow Tools to manage their hiring process, they expect candidates to flow smoothly through designated job roles. However, there are instances where a candidate who should be visible in a specific workflow simply doesn't appear, disrupting the recruitment pipeline and causing confusion.
This article helps recruiters identify why candidates might be missing from their selected workflows and provides actionable solutions to resolve the issue quickly.
## 🔎 Troubleshooting Common Issues
| **What Might Be Wrong** | **How to Fix It** |
| :----------------------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------- |
| The candidate hasn't been added to the workflow yet | Navigate to the candidate's profile and manually assign them to the correct workflow. Verify the assignment is saved before exiting. |
| Candidate was added to a different workflow by mistake | Check other active workflows in your organization. Use the search function to locate the candidate and reassign them to the intended workflow. |
| Candidate profile is marked as inactive or archived | Check the candidate's profile status. If archived or inactive, restore the profile to active status before adding them to the workflow. |
| System sync delay between modules | Wait 2-3 minutes and refresh the workflow page. If the candidate still doesn't appear, log out and log back in to force a system sync. |
### **Additional Tips**
* Always double-check the workflow name before searching for candidates, as similar workflow titles can cause confusion.
* If the issue persists across multiple candidates, contact Talview support as it may indicate a system-level configuration problem.
# Why is the JD not updating after edits?
Source: https://docs.talview.com/hiring-teams/recruiter/workflow-management/diagnostics/why-is-the-jd-not-updating-after-edits
In **Talview’s Workflow Tools platform, e**diting the *Job Description (JD)* using the editor should immediately update the JD as seen on the platform. However, sometimes updates may not reflect due to various technical or permission-based reasons.
This article outlines the common causes and actionable solutions to restore JD updating functionality.
***
## 🔎 Troubleshooting Common Issues
| **What might be wrong** | **How to fix it** |
| :----------------------------------------------------------------------- | :------------------------------------------------------------------ |
| The editor changes were not properly saved | Click "Save" after editing and ensure confirmation of JD update |
| Browser or caching issues prevent changes from displaying | Clear browser cache and refresh the page or try a different browser |
| Platform glitches or unscheduled maintenance impact saving functionality | Check Talview status page; wait and retry after downtime |
### **Additional Tips**
* Always verify a successful “save” confirmation before exiting the JD editor.
* Use the platform’s built-in “Get Help❓” or support channels for persistent or unclear issues.
* Document any error messages or irregular behavior to expedite resolution when raising a support ticket.
# Why is the Registration link or QR code not generated after opening?
Source: https://docs.talview.com/hiring-teams/recruiter/workflow-management/diagnostics/why-is-the-registration-link-or-qr-code-not-generated-after-opening
When a workflow is opened for registration, Workflow Tools generates a **registration link and QR code** that candidates can use to register themselves.
If the link or QR code does not appear, it is usually due to workflow configuration, registration status, or UI-related conditions.
***
## 🔎 Troubleshooting Common Issues
| **What might be wrong** | **How to fix it** |
| :-------------------------------------------- | :------------------------------------------------------------------------------------------------------------------- |
| Workflow is not opened for registration | Confirm that the workflow is explicitly **opened for registration** and saved successfully. |
| Required workflow steps are incomplete | Ensure mandatory steps (such as Screening or Assessment setup) are properly configured before opening registration. |
| Registration changes not saved | After enabling registration, click **Save** and wait for confirmation before checking for the link or QR code. |
| Page not refreshed after opening registration | Refresh the workflow page after opening it for registration to allow the link and QR code to load. |
| Workflow opened recently | Wait a few seconds to a minute after opening registration, then refresh the page. |
| User does not have required permissions | Ensure you are logged in as a **Recruiter** or **Master Recruiter** with permission to manage workflow registration. |
| Browser or UI rendering issue | Refresh the page, clear browser cache, or try accessing the workflow in a supported browser (Chrome recommended). |
### Additional Tips
* **Reopen registration if needed**
Close and reopen registration, then refresh the page to regenerate the link and QR code.
* **Check in a new session**
Log out and log back in, then reopen the workflow to rule out session-related issues.
* **Avoid multiple rapid changes**
Allow the system a moment to process registration status updates before navigating away.
* **Verify with another user**
Ask another recruiter to open the same workflow and confirm whether the link or QR code appears.
# Why is the Registration not closing even after confirmation?
Source: https://docs.talview.com/hiring-teams/recruiter/workflow-management/diagnostics/why-is-the-registration-not-closing-even-after-confirmation
The registration window may occasionally remain open even after you confirm the Close Registration action. This issue is most often caused by configuration conflicts or synchronization delays.
This article covers the **most common causes** and how to quickly fix them.
***
## 🔎 Troubleshooting Common Issues
| **Issue** | **How to Fix It** |
| :-------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------- |
| **Backend update delay** | Refresh the page after *30–60 seconds*. Close registration once again if still visible. |
| **Another user opened or extended registration simultaneously** | Confirm that no other recruiter is editing the registration window at the same time. Action conflicts may prevent closure. |
| **Registration end date/time already in the future** | Ensure the window’s end time is not preventing it from closing. Update the end date to the current time and retry. |
| **Permissions mismatch** | Ensure the user has the correct role to close registration. Update permissions if needed. |
| **Incorrect system time on user device** | Rare scenario where local system time conflicts with server time. Sync your device time and retry. |
### **Additional Tips**
If closure continues to fail, record the exact time of action and share workflow ID with **Talview Support** for deeper investigation.
# Recruiter FAQs - Workflow Management
Source: https://docs.talview.com/hiring-teams/recruiter/workflow-management/faqs/recruiter-faqs-workflow-management
### Introduction
The **Workflow Management module** in Workflow Tools allows recruiters to create, customize, and manage hiring workflows tailored to each requisition.
Using standardized templates, recruiters can configure job descriptions, steps, and evaluation criteria to ensure consistent and efficient hiring across roles.
This article answers common questions about **creating, editing, and managing workflows** within the platform.
***
### 1. Creating a New Workflow
**Q1. How do I create a new workflow in Workflow Tools?**
To create a new workflow:
1. Log in to the **Workflow Tools** interface.
2. Click **“Create Workflow”** from the top-right corner of the dashboard.
3. Choose a **workflow template** from the available list configured by your organization.
4. Enter a **workflow name** and click **Next** to proceed with setup.
5. Add or edit your **Job Description (JD)**, update step names if needed, and click **Create Workflow** to finalize.
**Q2. What are workflow templates, and how do I choose one?**
Workflow templates are **predefined hiring structures** created for your organization to ensure consistency across roles and teams.
Each template includes standard steps such as **Screening, Assessment, and Interview**.
Choose the template that best matches your hiring requirement, e.g.:
* “Software Engineer”
* “Sales Manager”
**Q3. Can I create a workflow without using a template?**
No. All workflows must be created using **existing templates** defined by your organization.
However, once you select a template, you can **customize step names, job details, and the job description** to suit your hiring needs.
**Q4. How far in advance should I create a workflow for a new requisition?**
It’s best to create a workflow as soon as a **requisition or hiring need is approved**, giving enough time to finalize the JD, evaluators, and step configuration before candidate invitations begin.
***
### 2. Editing and Managing Workflow Details
**Q1. Can I edit the workflow name after selecting a template?**
Yes. After choosing a template, you can rename the workflow before creating it.
Example: Rename “Software Engineer” to “Software Engineer – Bangalore.”
**Q2. How do I edit or rename workflow steps?**
Once a template is selected, the default steps (e.g., “Screening,” “Interview,” “Evaluation”) appear in editable form.
Click the **edit icon** beside each step to rename the steps.
**Q3. Can I change the workflow template after creation?**
No. The **underlying template cannot be changed**.
**Q4. Can I duplicate an existing workflow?**
No, duplication of workflows is not supported.
**Q5. How do I delete a workflow I no longer need?**
You cannot delete workflows from the platform.
***
### 3. Adding Job Description (JD)
**Q1. How do I add a Job Description to the workflow?**
After naming your workflow and finalizing steps, scroll to the **Job Description (JD)** section.
You’ll find a **block-note style editor** where you can:
* Enter or paste JD content
* Use formatting options (bold, headings, bullet lists)
* Add hyperlinks or structured sections like “Responsibilities” and “Requirements”
All edits are **auto-saved**, and the JD appears for recruiters, evaluators, and (if configured) candidates.
**Q2. Can I use a pre-existing Job Description?**
Yes. If your organization maintains JD templates, they’ll appear in a dropdown within the JD editor.
Select one to auto-fill the section and make any required adjustments before saving.
***
### 4. Finalizing and Using Workflows
**Q1. What happens after I click “Create Workflow”?**
The workflow appears on your **Workflow Dashboard** and becomes available for use.
You can then:
* Add or import candidates
* Assign evaluators or interviewers
* Launch assessments or interviews
* Track progress across steps in real time
**Q2. Can I edit the workflow after creating it?**
Some edits are allowed.
You can update the **JD, recruiter assignments, and evaluator mapping** after creation.
However, structural changes like **template replacement or step deletion** are not permitted once candidates are added.
**Q3. How many candidates can I add to a single workflow?**
There’s **no strict limit** to the number of candidates you can add, however if you want to restrict it then the same can be done when you open the workflow for registrations.
**Q4. Who can view or manage the workflow after it’s created?**
All users with **Recruiter** or **Master Recruiter** access can view and manage workflows.
Other roles (Evaluators, Hiring Managers) can view only the workflows they’re **assigned to**.
**Q5. What should I do if I get an error while creating or editing the workflow?**
Common causes include:
* Missing required fields (Workflow Name, Template, JD)
* Network timeout or session expiry
* Template configuration errors
Refresh the page and retry. If the issue continues, contact your **Admin** or **Talview Support** with the workflow name and timestamp.
# Difference between Owner and Collaborator roles in a Workflow
Source: https://docs.talview.com/hiring-teams/recruiter/workflow-management/how-tos/difference-between-owner-and-collaborator-roles-in-a-workflow
Every workflow in Workflow Tools has an Owner and can have one or more Collaborators. In this article, you'll learn the difference between these two roles and how they affect what you can do within a workflow.
### Workflow Owner
The Owner is the person who created the workflow. When you create a new workflow, you automatically become its Owner. Each workflow has one Owner.
### Workflow Collaborator
A Collaborator is someone who has been given access to a workflow by the Owner or another user with access. Collaborators can be added from the **Workflow List View** by clicking on the **users** column for that workflow.
***
### Key differences between Owner and Collaborator
| Access and actions | Owner | Collaborator |
| :--------------------------------------- | :---- | :----------- |
| Created the workflow | Yes | No |
| Can view the workflow and its candidates | Yes | Yes |
| Can invite candidates | Yes | Yes |
| Can schedule interviews | Yes | Yes |
| Can upload resumes | Yes | Yes |
| Can assign evaluators | Yes | Yes |
| Can track candidate progress | Yes | Yes |
| Can place calls to candidates | Yes | Yes |
| Can add other Collaborators | Yes | Yes |
### How visibility works
* If you're a **Recruiter**, you can only see workflows where you are the Owner or a Collaborator. If you haven't been added to a workflow, it won't appear in your Workflow List View.
* If you're a **Master Recruiter**, you can see all workflows in the organisation regardless of whether you're an Owner or Collaborator.
**Additional tips**
* You become the Owner of a workflow automatically when you create it.
* If you're a Recruiter and can't find a workflow, ask the Owner to add you as a Collaborator.
* Collaborators can be added directly from the Workflow List View without needing to go inside the workflow.
# How to create a new Workflow with a Job Description(JD)?
Source: https://docs.talview.com/hiring-teams/recruiter/workflow-management/how-tos/how-to-create-a-new-workflow-with-a-job-description-jd
This article provides a step-by-step guide to help recruiters create a new workflow with a **Job Description (JD)** using a ready-to-use template within **Talview’s Workflow Tools.**
## Step-by-step Guide
### 1. Set up a new workflow
* Upon successful authentication, you will be redirected to the **Workflow Tools dashboard.**
* Click on **Create Workflow** button to customize a new hiring workflow.
* Select an appropriate job role template that matches the position you're hiring.
* To change the name or details of your job role, click the edit icon ✏️.
* To view the details of this Job role, click on **Details** that’s located in the right end corner.
* To add a detailed Job description (JD) for this job role, click on **Add Job Description**
* Here, you can manually write the Job description,
* Or click on ➕, scroll down **Media\
**Tip:**\
Using ready-to-use templates saves time and ensures that your hiring workflows follow a consistent and structured setup across roles.
# How to filter candidates in the "All" view?
Source: https://docs.talview.com/hiring-teams/recruiter/workflow-management/how-tos/how-to-filter-candidates-in-the-all-view
The **All view** in a workflow provides a consolidated list of candidates across every step in the hiring process. To efficiently manage and track candidates, recruiters can apply **step-wise status filters** to view candidates based on the workflow step they are currently in (for example, Screening, Assessment, Interview, etc.). This helps in monitoring pipeline health, identifying bottlenecks, and taking timely action.
This article explains how recruiters can filter candidates using the **"All" view** inside a workflow by applying **step-wise candidate status** filters.
It provides a step-by-step guide to help users quickly identify where candidates stand across different stages of the workflow.
***
## Step-by-step Guide
### Step 1: Access the Workflow
* From the main menu, navigate to the **Workflows** section.
* Select the workflow where you want to review candidates.
### Step 2: Navigate to the "All" View
* Inside the workflow, land on the **All** tab.
* This view displays candidates from all steps of the workflow in a single list.
### Step 3: Open Filters
* Locate the **Filter** option available in the candidate list view.
* Click on it to view the available filtering options.
### Step 4: Apply Step-wise Status Filter
* Select the **Step-wise Status** filter.
* Choose one or more workflow steps (for example, Screening, Assessment, Interview).
* The candidate list updates to show only candidates currently in the selected step(s).
### Step 5: View Filtered Candidates
* Review the filtered candidate list based on the applied step-wise status.
* You can modify or combine filters to further refine the results as needed.
***
# How to track candidates in Screening, Assessment, and Interview steps?
Source: https://docs.talview.com/hiring-teams/recruiter/workflow-management/how-tos/how-to-track-candidates-in-screening-assessment-and-interview-steps
**Talview’s Workflow Tools Platform** enables recruiters and hiring teams to efficiently track candidates throughout the **screening, assessment, and interview stages** — all within a unified workspace that streamlines hiring operations and enhances decision-making.
This article explains how to monitor candidate progress, review application details, and access interview evaluations at every stage of the workflow.
## Step-by-Step Guide
### 1. Access the workflow
* Log in as a **Recruiter**.
* Select the desired **workflow** to access and manage candidates across its interview steps.
### 2. Track candidates in each interview step
Inside the workflow,
* Within the selected workflow:
* Click the **All** tab to view every candidate in the workflow.
* Select specific steps such as **Screening**, **Video Interview**, or **Technical Interview** to focus on candidates at each stage.
#### **a. Screening Step**
* Click on a candidate’s **name** or **email** to open their interview details.
* In the **Application Details** side panel:
* Go to the **Overview** tab to view registration details, uploaded resume, and other associated workflows.
* Switch to the **Form** tab to review the candidate’s registration form.
#### **b. Video Interview Step**
* Click a candidate’s **name** or **email** to access their video interview details.
* In the **Assessment Details** side panel:
* **Overview:** View the candidate’s assessment summary, interview details, and responses.
* **Form:** Review the submitted registration form.
* **Score:** Check the total score and **Proctoring Index**.
* **Evaluation:** View evaluators’ feedback or ratings.
* **Call History:** Review communication logs with the candidate.
#### **c. Technical Interview Step**
* Click on a candidate’s **name** to explore their technical interview schedule.
* In the **Assessment Details** side panel:
* Under **Overview**, click **View Recording** to access completed interview sessions.
* Go to the **Form** tab to review or update candidate responses.
* Open the **Evaluation** tab to review evaluator feedback and final decisions.
# Understanding Step-level Status Filters in All View
Source: https://docs.talview.com/hiring-teams/recruiter/workflow-management/how-tos/understanding-step-level-status-filters-in-all-view
The **All view** in a workflow provides a unified list of candidates across all steps such as Screening, Assessments, and Interviews.
To make this view actionable, Workflow Tools platform supports **step-level status filters**, where the available statuses dynamically change based on the selected workflow step.
This ensures recruiters see **only relevant statuses** that apply to that specific step, avoiding confusion and improving pipeline visibility.
This article explains how **Step-Level Status Filters** work in the **All view** of a workflow and how recruiters can use them to accurately track candidates based on the status specific to each workflow step.
***
### **How Step-Level Status Filters Work**
* In the **All view**, recruiters can open **Filters** and select a specific **workflow step**.
* Once a step is selected, the system displays **only the statuses applicable to that step**.
* Recruiters can select one or more statuses and apply the filter to view matching candidates.
***
## Step-wise Status Definitions
### **1. Resume Screening / Assessment Steps**
For steps such as **Resume Screening** or **Technical Assessment**, the following statuses may be available:
* **Invited** – Candidate has been invited to the step but has not started yet
* **In progress** – Candidate has started the assessment or screening process
* **Completed** – Candidate has completed the step
* **Evaluated** – Candidate’s submission has been evaluated
* **Yet to evaluate** – Candidate has completed the step but evaluation is pending
* **Selected** – Candidate has been selected at this step
* **Hold** – Candidate is temporarily on hold
* **Suspended** – Candidate is suspended from the process
* **Turned down** – Candidate has been rejected at this step
These statuses focus on **candidate participation and evaluation progress**.
***
### 2. Interview Steps (Technical Interview / HR Interview etc.)
For interview-based steps, the statuses are aligned to **interview scheduling and attendance**:
* **Scheduled** – Interview has been scheduled
* **Cancelled** – Interview was cancelled
* **Draft** – Candidate is invited to book their interview slots
* **In progress** – Interview is currently ongoing
* **Completed** – Interview has been completed
* **No show** – Candidate did not attend the interview
These statuses help recruiters track **interview execution and outcomes**.
***
### Additional Tips
* Status options vary by step—this is expected behavior and ensures only valid statuses are shown.
* Combine step-level status filters with other filters (if available) for more precise results.
# Welcome to the Talview Help Center
Source: https://docs.talview.com/index
Your one-stop resource to deliver seamless recruitment and certification experiences. Find Step-by-step guides, diagnostic articles, release highlights, and developer documentation.
## Get Started by Role
Choose your role to quickly access guides, walkthroughs, and troubleshooting resources tailored to how you use Talview.
Join interviews and exams, complete system checks, submit assessments, and resolve common technical issues.
Set up exam centers, manage proctored sessions, monitor candidates, and handle incidents in real time.
Schedule and run interviews, manage candidate pipelines, review evaluations, and streamline hiring workflows.
Configure assessments, monitor live sessions, manage proctoring incidents, and generate certification reports.
***
## Latest Updates
### 🚀 August 2026 Release Highlights
The **August 2026 release** delivers enhancements across **Workflow Tools, Interview Rooms, Assessment Engine & Candidate Experience, and Admin**, introducing improved notification controls, expanded candidate visibility, new Form Builder capabilities, and platform reliability improvements.
***
**Workflow Tools Updates**
* **Notification Preferences:** Users can now control which notifications they receive and on which channel from a dedicated Notifications Preferences page under Settings.
* **Previous Assessment Attempts:** Recruiters can now review all previous assessment attempts for a candidate directly from the Assessment side panel.
* **Additional Fields & Column Picker:** Workflows now carry a wider set of structured fields with a column picker that saves per user and carries across workflows.
* **Global Candidate View:** Education, work experience, and Resume Fitment status are now available as columns in the Global Candidate View.
***
**Proctoring Updates**
* **Exam to Center and Schedule Mapping:** Centers can now be tagged to an assessment step with schedules and capacity defined per schedule.
* **Assessment List View:** Verification and Risk Index columns are now available in the Assessment List View.
* **Exam Security Configurations:** Flow Config has been renamed to Exam Security Configurations. Published configurations can now be edited directly, creating a new version and archiving the old one.
* **V8 Native Moodle Plugin Integration:** A fully redesigned Moodle integration with flow-based proctoring, automatic session end on submission, and one-click recording playback.
***
**Interview Rooms Updates**
* **Soniox Transcription Accuracy:** Resolved language identification hallucinations and addressed rate-limit and concurrency constraints.
***
**Assessment Engine & Candidate Experience Updates**
* **Exit Confirmation for Test Sessions:** Candidates now get a browser warning before accidentally leaving an active test.
* **Retakes Off by Default:** Question-level retakes are now disabled by default for new asynchronous assessment sections.
* **Editing Disabled for Published Assessments:** Assessments can no longer be edited once published.
***
[👉 View Full August 2026 Release Notes](https://docs.talview.com/releasenotes/q3-2026/august-2026-release-updates)
*See previous updates: [All Release Notes](https://docs.talview.com/releasenotes/q3-2026/august-2026-release-updates)*
***
## 🛠 Quick Access
Step-by-step How-Tos, troubleshooting and diagnostics articles to help recruiters, coordinators, and candidates.
Full developer documentation including API quick starts, integration guides, and reference materials.
Get started by signing up, logging in with your password or SSO and managing your account access.
# February 2024 Release Updates
Source: https://docs.talview.com/releasenotes/q1-2024/release-notes-feb-2024
Stay updated with the latest features and enhancements rolled out in Jan 2024 across Talview’s Orchestration Platform (TOP) – including Workflow Tools, Candidate Experience, Interview Rooms, and Proview (Proctoring)
## Workflow Tools Updates
**Unified evaluation candidate detailed views**
This feature introduces a holistic view for evaluators, enabling them to access and assess candidates' form details, resumes, resume scores, async interview responses with TBI data, as well as objective and external assessment scores and reports, all in one place. Evaluators can now efficiently evaluate candidates by filling out forms and adding comments directly within the unified view. This integration aims to streamline the evaluation process, making it more efficient and effective.
**Intelligent scheduling enhancements**
Our intelligent scheduling feature now includes two significant enhancements: the ability to configure slot booking timelines for improved interview management, and the integration of candidate authentication to ensure candidates are authenticated and verified before joining live interviews. These updates provide a more flexible and secure approach to scheduling interviews.
**Help center launch**
The support center has been upgraded to offer users an improved experience, with direct navigation to the Talview website, the ability to raise support tickets easily, and access to a comprehensive list of product lines along with their respective knowledge base articles. These enhancements ensure that users have quick and easy access to the support and resources they need.
## Interview rooms Updates
\
**Candidate Face not Detection with real-time notification**
* Real-time alerts for interviewers for undetected faces of candidates enable smooth adjustments and uninterrupted participation.
**Multi Face Detection with real-time notification**
* Immediate alerts for interviewers if extra faces on the candidate's side ensure interview integrity and privacy.
**Multi Audio Device Detection with real-time notification**
* Interviewers will receive an alert when the system detects the use of multiple audio devices by a candidate.
**Switch audio Device detection with real-time notification**
* Real-time alerts notify interviewers of candidates' audio device changes, enhancing authentication.
**Job description for Interviewers**
* Interviewers now can refer to the job description in the Interview Rooms.
**Feature Enhancements**
* Full-screen Resume view – Interviewers now enjoy a full-screen resume view for improved referencing during interviews.
* Enhanced messaging on the Candidate and Interviewer onboarding pages now addresses technical issues or voluntary departures by either participant.
**Bug Fixes**
We have focused on closing the high-priority bugs listed below:
* Upon joining or exiting, the participant list will be updated in real-time.
* The speaker list is shown in the device settings for mobile view.
## Proview (Proctoring) Updates
## Proctor NG
### **Raising flags through Advanced AI**
With this update, our Proctoring system now features automated monitoring that analyzes screen grabs and camera grabs in real-time. This ensures proctors can effectively identify and understand potential issues or irregularities during candidate proctoring sessions.
**Known issues:**
1. Alerts are also triggering in the pre-checks.
2. High number of false positives.
### **Enhanced Video Streaming: Start video streaming early**
In our latest update, we've improved the video streaming functionality to capture crucial moments right from the start. Now, once hardware checks are completed, both screen grabs and primary camera videos are immediately recorded.
**Note:** This feature has been rolled back after blocker issues were identified.
### **Storing the confidence level for all AI flags**
To enhance and improve AI flag capturing, our AI model will now show confidence levels for all AI flags. This helps in determining if any review is required of a certain flag and also supports further improvements of the AI flag detection system.
### **Bug Fixes**
1. **Sort candidates based on external ID**
* **Issue:** The candidates were sorted with sequential numbers and were jumbled with every new candidate joining the live proctored session.
* **Solution:** Sorting the candidates based on external ID, which is fixed to each candidate, avoids jumbling the candidate order during the live proctored session.
2. **Layout alignment issues for post session video player**
* **Issue:** UI issue in post session view layout.
* **Solution:** UI is fixed to align the designs.
# January 2024 Release Updates
Source: https://docs.talview.com/releasenotes/q1-2024/release-notes-jan-2024
Stay updated with the latest features and enhancements rolled out in Jan 2024 across Talview’s Orchestration Platform (TOP) – including Workflow Tools, Candidate Experience, Interview Rooms, and Proview (Proctoring)
## Workflow Tools Updates
📅 **Intelligent scheduling via Recruit and Branding updates**
Intelligent Scheduling (IS) has been activated within the Recruit platform, allowing current customers to begin utilizing IS simply by altering a setting (via Growthbook) at either the user or organization level. Recruiters and Master Recruiters can continue their usual process for organizing online interviews to seamlessly integrate this new feature.
Also, the scheduling emails can now be customized with the organization’s logo, enhancing brand presence and personalizing candidate and interviewer communication
🔎 **Unified evaluation list views**
The "Unified Evaluation View" streamlines the decision-making process for evaluators by offering a comprehensive view of candidates by providing access to key data like assessment scores, resumes, resume scores, and TBI recommendations enabling them to take bulk decisions on the candidates.
### **Who are the primary users of this feature?**
> The features mentioned above will provide the greatest benefit to the **Recruiters, Master Recruiters, Interviewers,** and the **candidates.**
***
## Interview rooms Updates
We are excited to announce the latest update to Interview Rooms with features and fixes, to enhance the interviewing experience for all participants!
### **What is in the release?**
**In-meeting view of submitted evaluation form**
* During the meeting, interviewers can review the evaluation form that has been submitted.
**Candidate Face AUTH details update in real-time**
* Interviewers are now equipped to view real-time facial authentication details of candidates, provided the candidate joins after the interviewer's entry.
**Candidate Profile Details**
* The interviewer can now conveniently access the candidate's basic information during a live interview, which has been updated in the platform or form prior to the discussion.
**Reference image Details**
* A timestamp is now provided for the captured reference image.
**In-Meeting candidate Verification**
* In-meeting candidate face authentication during live interviews is now active and available.
**Bug Fixes**
We have focused on closing the high-priority bugs listed below.
* View evaluation form in the recruit application
* If a candidate chooses not to record the session and if the interviewer joins prior to the candidate, a notification will now be displayed to the interviewers.
* Upon joining, the participant list will now reflect an update in candidate status from 'invited' to 'in-meeting’
* Fetch latest resume in real time.
* Browser permission denied alert update.
* Fix and questions upload in Code Solo- FE to share with Mozilla customer.
### **Who are the primary users of this feature?**
Candidates & Interviewer
***
## c
### ***Attendee EX***
### 1. Proview Keyboard Accessibility
The Proview screens have now been made keyboard accessible. The screens can be navigated using the keyboard.
### 2. Noise Detection
When noise has been detected in the test-takers environment a new alert called Noise detected (beta) gets triggered. The noise level has been fine-tuned to a level that can capture other voices in the room, loud sounds etc. This flag is not shown to the candidate and is currently only visible to the proctors and admins. Noise detected (beta) will not impact the Proview index calculation as it’s still a beta flag right now.
### 3. TSB enforcement & configurations
* TSB (Talview Secure Browser) can now be enforced from the client script. A redirection to specified URL option has also been set when the TSB has been enforced.
* Added configuration options to blacklist or whitelist software on Windows and Mac operating systems.
* Included a minimize option for the application window. When minimize is enabled users can navigate to the whitelisted applications.
### 4. Proview Branding Customisation
Customers will now be able to make certain branding customizations in the Proview screens. The following are the branding options that can be configured:
1. Add their logo in the top left section of the pre-flight screens.
2. Primary brand color will reflect in the top portion of the dialog box and the button colors across all screens.
**Note:**
1. The logo component is not responsive. Upon resizing the window, the logo will continue to remain in the same size and position.
2. The splash screen will change for all customers (irrespective of if co-branding is enabled or not).
3. Branding standardisations are done for all Proview screens: Title text color, sub-title color, color of the bulleted list, color of the globe near the language change drop down have been changed from the Proview green to a more neutral black color.
4. Buttons which indicate a state of failure will continue to remain in the red color.
### 4. Proview Branding Enhancement
1. If custom branding is enabled the ‘Powered by Talview’ logo will be removed across all screens.
2. Proview logo has been changed to a gray scale across all screens. Please note this will be standardised across all screens irrespective of if custom branding is enabled or not.
***
### Enhancements
### 1. Using the face-detection model in the browser to validate no face and multiple faces
Rather than making an API call to Azure face auth each time we are now using the face-detection model in the browser to validate the presence of a face or multiple faces during the pre-flight experience. Nothing changes from a test-taker point of view.
### 2. Updated the face detection model
We are now using the latest TensorFlow face detection model to improve performance and accuracy.
***
### Bug Fixes
### 1. Showing the right browser in the post session view
**Issue:** The user took an exam from TSB but it shows ’Chrome’.\
**Solution:** We have updated the logic to show the right user agent. Now the correct browser is getting displayed in the post session view.
### 2. The exam start time was sometimes not displayed for an exam attempt if the session joined alert is missing
**Issue:** If the exam attempt did not have the session joined alert the exam start time was not getting displayed.\
**Solution:** In an event where the Session Joined event is missing we have updated the logic to use the first alert ordered by timestamp to get the start time of the exam thereby the exam start time is now always getting logged.
### ***Proctor NG***
### Playback view enhancements
The alerts have been plotted on the unified timeline. Upon clicking any of the flags the seek bar navigates to that point in the timeline and the respective toast message is displayed.
### Moodle Plugin drop-down changes
The options presented in the drop-down for the proctoring settings has been updated.
The new options in the drop down will be as follows:
1. No proctoring
2. Recorded
3. Record and Review
4. Live Proctoring
# March 2024 Release Updates
Source: https://docs.talview.com/releasenotes/q1-2024/release-notes-mar-2024
Stay updated with the latest features and enhancements rolled out in March 2024 across Talview’s Orchestration Platform (TOP) – including Workflow Tools, Candidate Experience, Interview Rooms, and Proview (Proctoring)
**Evaluation 360 enhancements**
March update for Evaluation 360 views introduced features where the evaluators can view other evaluations for a comprehensive candidate assessment and can also keep the candidates on hold. Live interviews, including recordings, evaluations, and participant data, are now accessible. Seamless navigation between candidates has been introduced with the next and previous buttons. Evaluation forms are locked post-completion to ensure data integrity (this is based on org-level configuration).\
Async interviews come with transcripts and timestamp navigation (this can be enabled at an organizational level without TBI also). Evaluators can now set their availability for interviews directly from the Evaluation 360 views, which have been renamed for improved visibility.
**Intelligent Scheduler enhancements**
Intelligent scheduler (with Workflow Tools) now supports certification processes, allowing candidates to book and reschedule slots for certifications based on a configurable flag. Candidates receive notifications about their registration and slots through certification-specific email templates, with their country automatically filled based on location while registering.\
Additionally, candidate authentication is now supported for intelligent scheduler-scheduled interviews, ensuring secure and efficient interviewing.
Read about this more here: [Drive - Certification Support](https://www.notion.so/Drive-Certification-Support-a86e8fce196a418090f9a19a7c14a174?pvs=21)
**Recording flexibility on Recruit**
Recruit now offers enhanced recording flexibility for live interviews, empowering organizations to tailor their compliance and auditing requirements. This feature can be toggled on or off at both the organizational and individual recruiter levels, granting recruiters the discretion to decide whether to record interviews during the scheduling process.
## Interview rooms Updates
**Migration of video service provider from Twillio to Livekit**
* Upgraded our live video interview service provider by transitioning from Twilio to Livekit, ensuring a smoother and more reliable experience.
**Custom layout for recording screen**
* Our latest update enhances the screen recording layout by displaying participant names, roles, network and audio statuses, and prominently featuring the candidate in the center. For participants not on video, their initials will now be visible.
**Blur background for Interviewers**
* We've introduced a blur background feature for interviewers, ensuring a more focused and professional video interview environment.
**Switch to collaborative Coding - WIP**
* We are excited to announce that we can switch to a collaborative coding platform, currently under development, to enhance our teamwork and productivity.
1. Language selection dropdown with sync among participants
2. Editor sync among participants
**Feature Enhancements**
* Our job descriptions have been upgraded to include key highlights, making it easier to identify the most important aspects at a glance.
**Bug Fixes**
We have focused on closing the high-priority bugs listed below:
* Enabled copy chat text for candidates
* Midway faceauth
* Participant list update
* Fixes on UI post migration from Twillio to Livekit
## Proview (Proctoring) Updates
## Attendee Ex
### Enhanced Accessibility on the Attendee Platform
Following are some of the accessibility issues fixed on the platform:
1. Tab indexing on all screens
2. Adding alt text and tooltips to images and icons
3. Screen navigation improvement for screen reader compatibility
### Proview Wrapper
The latest update to our Proview Wrapper Proctoring system can seamlessly integrate and launch proctored sessions across any session type or just with a secure browser on assessment engines that cannot use the embedded approach to proctor assessments.
**Following are the updates:**
* Candidates can be verified through a unique signed link or by candidate entering the verification code in static page.
* Candidates will attend the assessments in the same tab or in a new one based on the configuration of assessment delivery platform.
* Attend assessment in a secure browser or other browsers with or without proctoring based on configuration.
**Known issues:**
* Proview wrapper not loading properly with Secure Browser (TSB) – Issue in loading assessment
* TSB enforcement is not mandatory and candidate is able to attend the assessment on normal browser if they click on cancel opening TSB
* Minor UI issues
### Candidate Feedback
With the latest update, the candidates attending a proctored session will be able to provide feedback of the session after both AI proctoring, Record and Review proctoring, and Live proctored sessions. This feature enables us to better understand the candidate experience and identify areas for enhancement.
In live proctored sessions, the candidate will also be able to provide feedback of the proctor, enabling proctor administrators to train and improve proctor quality.
### Storing the confidence level for all AI flags
To enhance and improve AI flag capturing, our AI model will now show confidence levels for all AI flags, which helps in determining if any review is required of a certain flag and also to help further improvements of the AI flag detection system.
### Store confidence level for Advanced AI flags
When advanced AI flags are triggered, the model's confidence level of the prediction and the file ID is now being stored in the database.
### Bug Fixes
1. **Screenshot being cropped at the top**
* **Issue:** The screenshots were getting cropped at the top portion making it difficult to see if other tabs are being viewed.
* **Solution:** The necessary fix has been made to ensure the full-size screenshots are visible.
***
## Proctor NG
### Raising flags through Advanced AI
With this update, our Proctoring system now features automated monitoring that analyzes screen grabs and camera grabs in real-time. This ensures proctors can effectively identify and understand potential issues or irregularities during candidate proctoring sessions.
**Known issues:**
1. Alerts are also triggering in the pre-checks.
2. High number of false positives.
### Search functionality in chat
Proctors have the convenience of sifting through long chat transcripts by utilizing the search bar to find specific keywords. The search feature not only reveals the total number of times the keyword appears but also offers navigational arrows to hop between instances of the keyword, which is also emphasized within the chat.
### Rich text support in proctor chat
Proctors now have the ability to use rich text in chat, allowing them to share bulleted lists, links, and apply formatting such as bold and italics. Only proctors can utilize rich text; this feature is not available to candidates.
**Note:** The formatting of copied text may not always appear the same in the destination as it does in the source. The destination formatting will be the same as the source formatting if text has been copied over from a Word Doc, Notion, or Slack.
### Mark as Reviewed
Record and Review sessions can now be reviewed from the new playback screen. Once a proctor has been assigned to review, they can add flags, reject flags and recalculate the Proview Index. The proctors can also manually override the index and once they are done with the review they can mark the session as ‘Reviewed’.
### Video Syncing on Livekit
Video syncing has been achieved using the new video streaming service Livekit. Videos from all 3 streams are synced to the unified timeline.
### Enhanced Video Streaming: Start video streaming early
In our latest update, we've improved the video streaming functionality to capture crucial moments right from the start. Now, once hardware checks are completed, both screen grabs and primary camera videos are immediately recorded.
### Flags can be added only within the session window
Reviewers can only assign new flags during the designated timeframe of the session. Selecting a time and date outside of this interval will result in an error message.
**Known issue:** In a live session when the proctor is trying to add flags, the system will consider the scheduled start and end time of the event and not the start time when the candidate has joined the session.
### Video auto-switching functionality update
Video auto-switching will only showcase streams that are configured for the account. For example, if a secondary camera is not configured for the account, the stream will not appear.
**Known issue:** In the global settings all three streams are visible. If a stream that is not configured for the session is clicked, a no feed error will appear in the main view.
### New playback view linked to old playback app
The new playback can now be accessed from the old playback app via the link provided.\
**Note:** This will be available only for V7+ sessions with Twilio video streaming and for all kinds of proctoring - R\&R, Live Proctoring.
### Approval History is now available in Summary Tab in playback view
Approvals have been housed under Summary in the live view. The history of all the approvals can be accessed from there.
### Chats synced to the timeline
The chat conversations during a live proctored session have been synced to the unified timeline.
**Known issue in chat:** The latest message shared by the attendee gets hidden behind the text field. The new message can be viewed by scrolling up.
### Bug Fixes
1. **Sort candidates based on external ID**
* **Issue:** The candidates were sorted with sequential numbers and were jumbled with every new candidate joining the live proctored session.
* **Solution:** Sorting the candidates based on external ID, which is fixed to each candidate, avoids jumbling the candidate order during the live proctored session.
2. **Layout alignment issues for post session video player**
* **Issue:** UI issue in post session view layout.
* **Solution:** UI is fixed to align the designs.
3. **Auth Error when opening LaunchNG**
* **Issue:** When proctors would click on LaunchNG an error page would appear which says Auth Error.
* **Solution:** The necessary fix has been implemented and now the proctors can navigate to LaunchNG seamlessly.
4. **Slider issue in alert timeline**
* **Issue:** The slider in the alert timeline would retain its position if the user switched to the event overview and came back to the playback video.
* **Solution:** A fix has been implemented which would start the slider from the beginning of the timeline once the user exits the playback view.
5. **Delay in showing screen grabs when navigating via serial numbers in the live view**
* **Issue:** When switching between different attendees by clicking on the serial numbers, the screengrabs would take time to load.
* **Solution:** The necessary fix has been made to ensure the screengrabs load as soon as an attendee is switched.
6. **Incorrect system information in Summary**
* **Issue:** The system information displayed under the Summary tab was inaccurate.
* **Solution:** The necessary fix has been made to display the correct information under System Information.
* **Note:**
1. This section will only display the last device the attendee used to complete their assessment.
2. Sessions taken on Windows 11 will erroneously show as 10 due to the shared kernel version.
3. Sessions taken on Windows 11 Edge will show as Chrome browser, because of the shared Chromium engine.
7. **Pre-check data saving issue**
* **Issue:** Precheck data was not getting saved when face match log was disabled.
* **Solution:** The required fix was made and now the precheck data gets saved irrespective of whether face verification is disabled or enabled.
# February 2025 Release Updates
Source: https://docs.talview.com/releasenotes/q1-2025/release-notes-feb-2025
Stay updated with the latest features and enhancements rolled out in Feb 2025 across Talview’s Orchestration Platform (TOP) – including Workflow Tools, Candidate Experience, Interview Rooms, and Proview (Proctoring)
## Workflow Tools Updates
**✉️ Assessment List Filters**
In the Workflow Tools UI, recruiters can filter candidates by **assessment score, invited by, and status** for **faster and more efficient shortlisting.**
**🎥 MS Teams with IS Enhancements**
Candidates can now **share their screen by default** in **MS Teams interviews** scheduled via IS without organizer approval, streamlining the interview process and reducing unnecessary delays.
**📝 Evaluation Display to Recruiters**
Recruiters can now **view evaluator recommendations and comments** in **interview and assessment steps** inside Workflow Tools, improving decision-making.
***
## Candidate Experience Updates
🔗 **Post Completion URL Redirection**
Candidates are now redirected to an organization-level configured URL after completing a step, ensuring a seamless journey.
📝 **Custom Instructions on SKU Details Page**
Candidates can now view **custom instructions** like the SKU-level accommodation rules or certification guidelines before they proceed with their slot booking and payment process.
💰 **Payment Refund Email on Slot Cancellation**
Candidates will receive an **automated refund email** upon slot cancellation with the refund details, ensuring transparency.
🔄 **Reschedule with Fee Payment**
Candidates can now **reschedule exam slots** with an applicable **fee**, based on SKU rules.
🎭 **Face Detection Before Capture**
Face authentication now includes a **pre-capture detection step** to enhance verification accuracy.
**Multi-Language Support Extension (attend-ng)**
Attend-ng experience now supports **French and Hindi**, enhancing accessibility for a diverse candidate base.
***
## Interview Room Updates
**📱 Secondary camera enhancement feature with person and screen detection**
An advanced secondary camera enhancement that intelligently detects people and screens for optimized framing and clarity. Ensures precise auto-framing, improves content capture by distinguishing between people and screens in real time.
***
## Proview (Proctoring) Updates
**🛬 Alvy will not flag test taker during the preflight checks**
Test takers will no longer be monitored and flagged during preflight checks, to avoid any false flags. Test takers may need additional assistance before they start their exam
**🛜 Handling streaming disconnection mid session**
If the test taker disconnects with the internet or with the video streaming provider, then a attempt to reconnect from the backend is made.
* Within 30 seconds of disconnection, the first reconnect attempt will be made.
* The second reconnect attempt will be made after 60 seconds of disconnection, when the first attempt fails.
* When both attempts to reconnect from backend fails, the candidate is presented with an error screen. Once they’ve resolved issues and the connection is restored, they click on “Refresh” button and can proceed from where they left off.
**Updated the test taker instructions**
The instructions displayed to the test taker has been updated to inform about closing online meeting applications.
# January 2025 Release Updates
Source: https://docs.talview.com/releasenotes/q1-2025/release-notes-jan-2025
Here’s what’s new across Workflow Tools, Candidate Experience, Interview Rooms, Admin, and Proctoring this month.
## Workflow Tools Updates
✉️ **Invite Email Enhancement**
A **confirmation link** has been added to interview invite emails, allowing interviewers to **confirm their attendance with a single click**. This helps recruiters track confirmations and manage scheduling more effectively.
🎥 **IR Playback View Integration with Workflow Tools**
Recruiters can now **access and playback Interview Rooms session recordings** directly within **Workflow Tools**. This integration enhances efficiency in reviewing completed interviews and streamlining evaluations.
📝 **Recruiter Evaluation**
Recruiters can now **submit structured evaluations** directly within the platform, ensuring **consistent and detailed feedback** for improved hiring decisions. This feature standardizes candidate assessments, enhancing feedback reliability and decision-making efficiency.
***
## Candidate Experience Updates
✉️ **Invite Email Enhancement to Include ‘Confirm’ Link**
A **confirmation link** in interview invite emails allows candidates to **confirm attendance with one click**, helping recruiters and hiring managers reduce no-shows and improve scheduling efficiency.
📅 **Multiple Slot Booking for Payment**
Candidates can now **book multiple slots** for the same certification or SKU without waiting for the previous slot to pass or be canceled. This enhances **scheduling flexibility** and reduces last-minute reschedule requests.
🌍 **Saving the Candidate Timezone Against the Slots**
The platform now **automatically detects and stores candidates' timezones**, ensuring interview schedules, assessments, and notifications are displayed in **local time**. This reduces scheduling errors, minimizes confusion, and decreases support requests related to timezone mismatches.
📜 **Showing Custom Terms and Conditions**
Organizations can now **dynamically display custom terms and privacy policy links** to candidates. This ensures compliance, enhances flexibility, and provides a seamless, consistent candidate experience.
🔗 **Standalone Form Using Public Link**
Candidates can now **apply through a public standalone form** without needing an invitation, allowing recruiters to **expand their talent pool** and streamline the application process.
***
## Interview Room Updates
**📲 Secondary camera**
Enhance live interviews with a secondary camera, providing additional visual perspectives to better assess the candidate’s environment or demonstrate specific tasks.
Interviewers can now use a **secondary camera** in live interviews and access the **job description** within the **Interview Room (WFT)**. The **video player** supports **MP4 track syncing**, **fast-forward, rewind, seek**, and a **buffering indicator** for smoother playback.
**📑 Display Job description in IR for WFT**
Interviewers now can refer to the job description in the Interview Rooms when scheduled from Talview Workflow Tools
**⏪ Video Player Enhancements**
The **video player** supports **MP4 track syncing**, **fast-forward, rewind, seek**, and a **buffering indicator** for smoother playback.
***
## Proview (Proctoring) Updates
### Attendee Experience
**⏯️ Pause and Resume a Proctored Session**
* When a proctor has paused a student’s proctored session, an appropriate message will appear on candidate's screen
* The student won’t be be able to access the exam window while their session is paused
* Along with the screen, an automatic message is also sent to the attendee in their chat.
🛜 **Resolving connectivity issues via speed test, diagnostics, and Refresh button**
* The error page displayed to candidate, when their internet connection is disrupted or if there is a disconnection with the video streaming provider has been updated.
* The page now contains links to test their [internet speed](https://speed.talview.com/) as well as [run video diagnostics](https://video-diagnostics.talview.org/).
* This page and the content within is translatable into proview supported languages
**💬 Updated disconnection error message when session is paused**
When a candidate’s session is paused by the proctor, but then faces streaming disconnection or internet connectivity errors, an appropriate message will now be displayed.
**🚩 AI flags to be paused when the session is paused**
Following flags will not be raised when the session is paused, avoiding the false flagging when the session is paused.
* Face not detected
* Mobile or Book detected
* Multiple people detected / Multiple faces detected
***
### Proctor Dashboard
**⏸️ Pause and Resume a proctored session**
* Proctors can now pause and resume an active session.
* Whenever the proctor pauses or resumes a session, that action will trigger a message to be sent to the student via chat.
* When the proctor/test admin performs the action of pausing or resuming a proctored session, the same will now get logged in the alerts section under **Debug**.
* When a proctor has paused a student’s proctored session, the camera and screen video streams will continue, but alerts will not get logged.
**🖇️ Add additional parameters when created a new wrapper link**
The wrapper link creation form has been updated to include the additional parameters.
* The accommodations in key value pairs can be specified at a session level.
* The additional properties in key value pairs can be specified at the attendee level.
***
### Integrations
**⌘ Integration with Thinkific and Cornerstone LMS**
Proview proctoring is now integrated with two new LMS platforms - Thinkific & cornerstone, following the browser extension approach.
**🈂️ Language selection for extension installation**
If a candidate hasn’t installed the proview browser extension, when they try to attempt a proctored quz in Canvas & Thinkific LMS, they are presented with a message.
* This message contains a warning as well as installation instructions for the extension.
* This installation message is now translatable into proview supported languages via its selection from the dropdown menu.
# March 2025 Release Updates
Source: https://docs.talview.com/releasenotes/q1-2025/release-notes-march-2025
We’ve rolled out key updates across Workflow Tools, Candidate Experience, Proview, and Interview Rooms to enhance efficiency and experience. Check out what’s new!
## Workflow Tools Updates
### **🔔 Notification Inbox – A Smarter Way to Track Workflow Updates**
We’ve launched a **new Notification module** in **Workflow Tools** to help recruiters stay on top of workflow updates effortlessly.
* **Inbox View** – Notifications are **grouped by candidates within workflows**, with expandable cards for better visibility of the conversation threads.
* **Detail View** – Displays the **full notification body**, making it easier to track and take action.
***
### **🎥 MS Teams Enhancements – Smoother Candidate Access**
Candidates can now **join MS Teams interviews without manual lobby approval**, eliminating delays and reducing interviewer effort. Secure access is ensured via predefined settings.
***
### **🔄 Interview Join Nudge to reduce no-shows**
To improve attendance and minimize no-shows, we’ve introduced **automated interview email notifications** to both interviewer and candidates. The notification will notify them when the other party joins the call.
***
## Candidate Experience Updates
### **📝 Long-Form Assessments – A More Intuitive Experience**
We’ve revamped the **Test Taker Interface** to improve long-form assessments:
* ✍ **Better Answer Writing** – A **block note-style editor** with formatting options.
* 💾 **Auto-Save Every 30 Seconds** – Ensures progress is never lost.
* 📎 **File Upload Support** – Candidates can attach and submit files as part of their responses.
***
### **🔗 Post-Completion URL Redirection – A Guided Exit Flow**
Organizations can now **set custom exit URLs and button labels** for candidates after completing a step, ensuring a smooth transition. Candidates are **automatically redirected** to a configured URL (e.g., a thank-you page).
***
### **💳 Payment Failure Notifications – Stay Informed, Retry Easily**
Users will now receive an **email notification** for failed payments, including:
* 📅 **Payment details** (date, amount, status).
* 🔄 **A "Start Again" button** to restart the process seamlessly.
***
### **📋 Pre-Assessment Form Integration – Collect Information Before Tests**
Candidates can now **fill out a form before starting an assessment**, ensuring structured data collection.
***
## Interview Rooms Updates
### **📀 Video support in Guide**
Organizations can now upload video guide for interviewers. Interviewer can view and play the video within the Interviewer guide.
***
### **🌏 360 degree environment check on interviewer request**
Enables interviewers to request a 360 degree environment check for candidates during interviews.
***
### **Restrict languages in Codesolo**
We can now restrict required languages in codesolo at assessment level.
***
## Proview (Proctoring) Updates
### Attendee Experience
* **Extended proctored session** : Proctor can now extend a session for a candidate on need basis. When the proctor extends a proctored session, the candidate receives a message in chat. This message includes the time in minutes the session has been extended by, and the reason for extension.
* **Custom streaming re-connection** : When test taker’s primary or secondary camera gets disconnected, usually due to bad network quality, our system automatically tries to reconnect within 1 minute. If reconnection fails within 1 minute, then error is shown to test taker. This helps in reducing disconnections unnecessarily and improve user experience.
* **Upload image on chat for assistance from Alvy (AI Proctor Agent)** : Test taker will now be able to upload images to chat window and get inputs from Alvy assist on preflight check issues they maybe facing.
* **Increased Maximum File Size for Photo ID**: The maximum file size for Photo ID uploads has been increased from **1MB to 3MB**, allowing users to upload higher-quality images.
* **New Configuration Option: Disable Face Detection Model**: A new configuration allows clients to disable the face detection model. By default, the model is enabled.
# February 2026 Release Updates
Source: https://docs.talview.com/releasenotes/q1-2026/february-2026-release-updates
🚀 **February was a build month.**\
While there were no external releases this month, our teams were focused on foundational enhancements and upcoming features.\
Exciting updates go live starting March - we can’t wait to share them.
# January 2026 Release Updates
Source: https://docs.talview.com/releasenotes/q1-2026/january-2026-release-updates
The January 2026 release delivers a set of targeted enhancements and fixes across **Interview Rooms and Proctoring** to improve reliability, consistency, and reviewer efficiency.
The updates address secondary camera behavior, browser compatibility, insights visibility, and candidate flow issues, while also introducing usability improvements in Secure Browser, Proctor NG workflows, and LMS integrations for a smoother end-to-end assessment and interview experience.
***
## **Candidate Experience Updates**
### ✅ New Feature: Payment Enhancements
**Description:**
We have refactored the scheduling flow where in the slot should only get confirmed once the payment has been received. Also, refactored the architecture to reduce the number of cases where the meeting stayed in draft state even after receiving the payment
**What’s New**
* Slot will not get scheduled if the payment goes in pending state. It will only get scheduled once the payment has been confirmed.
* Slot will change from draft to confirmed if the payment has been confirmed even when the candidate is not on the CX page.
* If the candidate abandons the flow and attempts to re-enter the flow, we will create a new transaction against the same order against their previously selected slot
* Candidate should be able to retry failed transactions against the same order
* If the transaction remains in pending state for very long, we will automatically cancel the transaction and allow them to pay again
**Benefit:** Reduce meeting in draft when payment has been confirmed scenarios, candidate UX improvements
***
## **Interview Rooms Enhancements**
### 🐞Bug Fixes
1️⃣ **Issue:** Secondary Camera request was auto-triggered after a **manually initiated** 360° environment check.
**Solution:** Updated the logic so the Secondary Camera auto-triggers **only when the 360° environment check is system-initiated**, not when requested manually by the interviewer.
2️⃣ **Issue:** When **GrowthBook (GB)** was enabled, all Insights tabs (Overview, Transcript, Speaker, etc.) were visible instead of restricting access.
**Solution:** Updated the Insights view to **show only the Verification tab along with video playback** and hide the **Overview, Transcript, and Speaker** tabs when GB is enabled.
3️⃣ **Issue:** Background Effects were not supported for interviewers using **Safari and Firefox** browsers.
**Solution:** Enabled **Background Effects support for interviewers** on **Safari and Firefox**, ensuring a consistent interview experience across browsers.
***
## **Proctoring Updates:**
### **1. Secure Browser**
### 🆕 Feature
*Improved Restricted Software Handling in Secure Browser for Mac OS*
With this update, Secure Browser now supports a more seamless experience in handling blocklisted applications on Mac OS as well.
* When restricted software is detected, Secure Browser temporarily exits kiosk mode without closing.
* The test taker can open Activity Monitor, close the restricted applications, and return to Secure Browser.
* Once resolved, Secure Browser automatically switches back to kiosk mode, allowing the test taker to resume the test without restarting.
**Note:** When restricted applications are detected and kiosk mode is exited, Secure Browser does not pause the exam timer.
***
### **2. Proctor NG \[V7+]**
### ⚙️ Enhancements
*Welfare-Related Dispositions for Proview Index Updates*
You can now select welfare-related dispositions when modifying a session’s Proview Index. This helps reviewers understand sensitive situations and take appropriate follow-up actions.
* **Proctor Welfare Concern:** Candidate made abusive or inappropriate remarks toward the proctor.
* **Candidate Welfare Concern:** Candidate showed signs of distress or potential risk and may require follow-up.
**📸 Reference:**
***
### **3. Integrations \[V7+]**
### ⚙️ Enhancements
*D2L LMS | Support for Apprentice Role as Test Taker*
* Apprentices can now attempt proctored quizzes, similar to Student and Learner roles.
* Apprentices are automatically included when syncing attendees from the LMS dashboard.
**📸 Reference:**
***
### **🐞 Bug Fixes**
**Secondary Camera Connection Screen Blocking Progress**
* **Issue:** Some candidates were unable to proceed after connecting their phone as a secondary camera during pre-flight checks.
* **Impact:** Candidates were blocked from starting their exams.
* **Fix:** Updated the LMS integration to correctly detect and validate secondary camera connections.
* **Result:** Candidates can now proceed smoothly once their phone is connected
# March 2026 Release Updates
Source: https://docs.talview.com/releasenotes/q1-2026/march-2026-release-updates
The March 2026 release delivers enhancements across **Workflow Tools & Scheduling, Assessment Engine & Candidate Experience, and Proctoring**, introducing AI-powered exam monitoring, smarter candidate communications, and reliability improvements across LMS integrations and proctoring workflows.
***
## Workflow Tools Enhancements
This month, we introduced enhancements focused on **improving candidate communication and reducing manual follow-ups across workflows**.
#### 🆕 Feature
**1. Assessment (Exam) - 48-Hour Reminder Email**
**Description:** Candidates scheduled for a certification exam now receive a 48-hour reminder email, consistent with reminder behavior across other interview types.
**What's New**
* Reminder email is automatically sent 48 hours before the scheduled exam.
* Consistent with existing reminder behavior for other interview types.
***
## Proctoring Updates
This month, we introduced enhancements focused on **strengthening LMS integrations and improving reliability across proctoring workflows**.
### Integrations (V7+)
#### 🆕 Feature
**Moodle 4.5 LMS - Plugin-Based Integration**
**Description:** Talview has moved from a browser extension-based integration to a plugin-based integration for Moodle 4.5 LMS.
**What's New**
* Previously, every student and administrator had to individually install a browser extension to access proctoring capabilities.
* With the new plugin-based approach, it is a one-time installation on the LMS server by the administrator.
* Once installed, all users on that LMS instance automatically get access to proctoring capabilities with no individual installation required.
For more information about the experience, refer to the [user guide](https://talview.notion.site/Moodle-4-5-LMS-User-Guide-Moodle-Plugin-Integration-32e3461472f3804c9099d8fd71f0dbf0?source=copy_link). For details on how to install it on a Moodle instance, refer to the [installation guide](https://talview.notion.site/Moodle-4-5-LMS-Installation-Guide-Moodle-Plugin-Integration-32e3461472f380759116d540a1dbcb33?source=copy_link).
***
#### 🐞 Bug Fixes
1️⃣ **Auto scroll issue in proctor chat**\
**Issue:** When a proctor had a chat open with a candidate and tried to scroll up to read older messages, they were automatically pulled back down to the latest message, making it impossible to review the chat history.
**Solution:** Proctors can now freely scroll through older messages without being auto-scrolled. The chat will only auto-scroll to the latest message when the proctor reaches the bottom of the thread or sends a reply.
2️⃣ **Cornerstone LMS - Unexpected Exits during proctored quiz**
**Issue:** Students taking a proctored quiz on Cornerstone LMS were being unexpectedly forced out of their exam by a "Leave Site" pop-up, even when they selected Cancel.
**Solution:** This has been fixed with an updated version of the browser extension, now published to the Chrome Store. Students will no longer be interrupted or forced out of their exam by this pop-up.
***
## Assessment Engine & Candidate Experience Updates
This month, we focused on **improving the accuracy and reliability of candidate-facing communications**.
### Enhancements
1️⃣ **Remove estimated duration from Assessment emails when value is undefined**
**Description:** The "Estimated Duration" section has been removed from assessment invite and reminder email templates when no `assessment_section_time` value is configured.
**What's New**
* Previously, this field was rendering as "undefined" in candidate-facing emails, causing confusion.
* Candidates now receive clean, accurate email communications without placeholder or undefined values appearing in assessment details.
***
# April 2024 Release Updates
Source: https://docs.talview.com/releasenotes/q2-2024/release-notes-april-2024
Welcome to the April release notes, where you can explore the most recent enhancements on TOP and Proctoring.
## Workflow Tools
### **Evaluation 360 enhancements**
This month, we've enhanced the Evaluation 360 module by introducing the **essay section** evaluation for detailed candidate response reviews, review of the **multi-interview sessions** in sequential order, allowing for tracking and evaluation of offline interviews, **expanding the async interview view** for improved response visibility and transcripts and implementing a **full-screen interview mode** for a superior evaluator experience.
### **Intelligent Scheduler enhancements**
This month, our Intelligent Scheduler has been upgraded to streamline the interview process by **restricting manual rescheduling** on the platform for IS-scheduled interviews and hence encouraging more RSVP-based negotiations, embedding essential **collaterals in scheduling emails** for better candidate preparation, and enhancing our **branding capabilities by displaying the organization's logo** throughout the interviewer and candidate experiences.
Check out the gif below where the ACME logo is configured against the organization in the test account via Growthbook.
**Who are the primary users of this feature?**
> The features mentioned above will provide the greatest benefit to the **recruiters, master recruiters, interviewers,** and the **candidates.**
**What are we working on next?**
1. Automatic meeting status change
2. Screening step integration
3. Recruiter digest emails
4. Offline interview with IS
5. Admin application MVP
6. SMS workflows for RSVP negotiations
**Are there any known issues (caveats)?**
* IS emails cannot be customized, only an external link can be added at an organizational level
* Remind, reschedule, and manage attendees features are disabled for IS scheduling with Recruit and Labs
## Interview Rooms
**Switch to collaborative CodeJam**
* We are excited to announce that we can switch to a collaborative codejam platform.
1. Language selection dropdown with sync among participants
2. Editor sync among participants
3. Run/Compiler sync among participants
4. Console sync with quick test & sample test.
5. Real-time code collaboration among participants with awareness
6. Reset code
7. Intellisense & Syntax highlighting based on language/Framework
**Pre-Join lobby**
* Pre-join lobby, available for both interviewers and candidates! Now you can easily enable or disable your video and audio, and select your preferred audio and video devices before joining, ensuring a seamless and personalized interview experience.
**Feature Enhancements**
**Blur background for Interviewers**
* We've increased the intensity of blur background for interviewers, ensuring a more focused and professional video interview environment. Identifying a 2nd person as an object and hiding is not implemented.
**Auto refresh when loading fails**
* If any critical API fails, the page will automatically refresh in 5 seconds.
**Bug Fixes**
We have focused on closing the high-priority bugs listed below
* Real-time notifications for candidate verification issues, such as detecting multiple faces, multiple cameras/Audio devices, Switch cameras/Audio devices or no face, will close only for the respective interviewer who clicks 'OK' or closes the notification, without impacting other interviewers in sessions with multiple participants
* Lazy loader to manage the loading states. \
**Who are the primary users of this feature?**
Candidates & Interviewer
These features are available in the Recruit production environment.
**What are we working on next?**
* Interview Builder- WIP
* Integration of Whiteboarding-WIP
## Proctoring
### Attendee Ex
**Features**
**Secure Browser** Talview Secure Browser(TSB) is now rebranded as Secure Browser and updated to be a white labelled platform. This is applicable for both Mac and Windows application of secure browser. What are the changes:
* Attendee screen recordings will be available in Proview enabled Secure Browser based assessments.
* White labelled application with updated to guidelines page. **Known issue:** Content protection is yet to be a configurable feature at account level for each customer using Secure Browser to enable or disable screen recording in Secure Browser.
**Multiple People Detected Flag** In this update, we're discontinuing the "Multiple Faces Detected" flag's role in severity and Proview Index calculation, and shifting to "Multiple People Detected" flag for improved accuracy. **Changes:**
* The system now marks the **flag severity as critical** for all exam stakes upon detecting **multiple people** during a proctored assessment.
* The flag is logged under the name "Multiple People Detected".
* Attendees in High, Medium, and Low stake exams will be prompted by the flag on each occurrence, with maximum occurrences set to 5 for Medium stakes and 1 for Low stakes. Candidates in No stake exams will not receive any warning notifications. Additionally, the "Multiple Faces Detected" flag will solely be logged without impacting the Proview index calculation, and no warning messages will be displayed to candidates. These adjustments aim to enhance flag accuracy in identifying additional individuals present in the candidate’s assessment environment.
1. **New languages on Proview Attendee** We've added Brazilian Portuguese and Spanish to Proview Attendee v7+, making it easier for more candidates to navigate and use the platform in their preferred language.
**Bug fixes**
1. **Updates to existing French language** French language strings were update as per language expert advice. These adjustments aim to enhance accuracy and user experience.
2. **Enhanced configuration check - UI updates** **Problem**: Photo ID and Environment check approval pages had infinite loading when those checks are disabled. **Solution**: Approval for ID and environment checks, video recording, screen and camera grabs, and ID card presence are now conditional, displaying only if configured, both to candidates and proctor admins.
3. **Error when Proview session is refreshed** **Issue**: When the Proview session is refreshed, either when the attendee reloads or when their session is disconnected, an error saying VPN error was thrown. **Solution**: We’ve modified error message to guide the user on action to be done saying Proview session needs to be refreshed when the session get’s interrupted due to disconnection in the session.
### Proctor NG
**Feature**
1. **Proctor Comments & timestamp of the manual override** When a proctor adjusts the system-generated Proview index, the time of this change will be displayed, and the reason for the modification will be listed beneath the generated index.
2. **Enlarged view of screenshots & camera grab in playback view** Users now have the ability to click on images within the 'Images & Screenshots’ section to view them in an expanded format, allowing for detailed examination.
3. **Faster playback speed** Videos now support playback speeds of 2x, 4x, and 8x for quicker review. Currently, all three speed options are accessible when using Twilio. For Livekit, playback is limited to 1x and 2x speeds currently.
Please be aware of a known issue with Livekit: if the internet connection is weak, videos may take a significant amount of time to load. Additionally, faster playback speeds in Livekit have been found to cause synchronization problems and we are working on a fix for that.
4. **Critical filter in Proctor NG playback and live view** A critical filter will be made available in the alert tab. When this filter is applied the alert tab and the timeline will only show the alerts that impact the Proview Index and a few other standard alerts such as: Session Joined Precheck Approved Precheck Rejected Primary Recording Started Secondary Recording Started Screen Recording Started Primary Recording Stopped Secondary Recording Stopped Screen Recording Stopped Session Completed
Note: The critical filter must be used independently and cannot be activated simultaneously with public and debug filters.
**Enhancements**
1. Attendee download Attendees' lists for each quiz can be downloaded by users directly at the quiz level.
2. TSB validation at quiz level A new row labelled "TSB" will be added to quizzes to indicate whether a quiz is enabled with TSB or not.
3. **Summary tab - Proview alerts** In the playback view, under the 'Summary Tab', all flags contributing to the Proview index will be displayed. This section will also show the number of these flags and whether they have been dismissed.
4. **Confirmation modal for Re-Sync in LMS dashboard** A confirmation pop-up will be implemented to seek user confirmation before proceeding with a Re-Sync of attendees, ensuring that accidental clicks are prevented. Proctors now have the ability to conduct searches within chat logs. The search output will indicate the frequency of the searched keyword's occurrence within the chat, and proctors can move through each instance using the upward and downward navigation keys.
5. **Chat log search**
6. **Dashboard - Email ID truncation** If a proctor's email ID was too lengthy, it would get cut off, making it difficult for viewers to see the entire address. We've enhanced the system to display the full email ID when you hover over long email IDs.
7. **Unapproved state of the pre-checks** For live proctored sessions, if a candidate submits pre-checks and the proctor has not reviewed them until the completion of the session, we will add an 'Unapproved' label beneath each item in the approvals section of the post-session view.
8. **Playback view redirection based on a configuration** The new playback view can be made as a default by enabling the configuration at an account level. Redirection will be enabled in the following locations: In proview live proctor for test admin role(for completed events only):
1. Events Tab > Candidates
2. Candidates Tab > Profiles
3. Candidates Tab > Record & Review In proview live proctor for proctor role(for completed events only):
4. Events Tab > Live proctoring
5. Events Tab > Candidate report
6. Candidate Tab In Proview Admin
7. Profiles
9. **‘Added’ tag in the alert logs when reviewer manually adds a flag** A tag called ‘Added’ is introduced to identify the manually added flags. Upon hovering over the tag the timestamp of when the flag was added gets displayed.
**Bug fixes**
1. **Proctor filter selection - Monitoring Dashboard** **Issue:** Filtering the attendees based on proctors would not show accurate results. **Solution:** The necessary changes have been implemented and the attendees can be viewed based on proctor filter.
Note: By default, no proctors will be selected. To view data, proctor has to be selected and then the list of attendees assigned to the proctor will get displayed.
2. **Timestamps shown incorrectly in chat box** **Issue**: Timestamps associated with the chat logs showing up incorrectly. **Solution**: This issue has been fixed. The chat messages will show in the correct order.
3. **Custom Flags issue** **Issue**: When custom flags were by added by proctor it would display as custom event in the alert log. **Solution**: We have made the necessary changes to show the name of the flag chosen during the custom flag selection.
4. **Proctor online/offline status in dashboard - Monitoring Dashboard** **Issue:** Online proctor count was inaccurate. **Solution:** Proctor presence can now be viewed from the live monitoring dashboard. Proctor online count, which was inaccurate previously will represent the correct count after this enhancement.
5. **Issue with Chat Display** **Issue:** Extended messages are truncated on the right, preventing attendees from reading the full message. **Solution:** Adjustments have been implemented to ensure comprehensive messages are appropriately wrapped, allowing candidates to see the entire message content.
6. **Adding flag within the session window** **Issue:** When adding flags the proctor could add flags outside of the window. **Solution**: With the fix that has been introduced the proctor will be able to add flag for a proctored session only between the ‘Session Joined’ and ‘Session Completed’ timestamps in the playback view. In Live view, when the proctor adds a flag, it will automatically pick the current system time.
7. **Dashboard - Primary video status is not getting updated** **Issue**: The primary camera status in the monitoring dashboard was not updating in real-time. **Solution**: We have implemented a fix to ensure that the status of both the primary and secondary cameras is accurately displayed in real time.
8. **Livekit video - Unmuting issue** **Issue**: Even though a candidate's audio was muted the user was able to hear the audio **Solution**: The audio will be heard only if the video has been unmuted.
9. **Icons in Launch NG global actions** **Issue**: The icons of the different feeds available in the global actions in Launch NG was not according to configuration. **Solution**: We have fixed this to display only those feeds that have been configured for the session
10. **Adding flag in Live view** **Issue:** When adding a new flag, it would take the event start time and not the session joined time. **Solution:** Session joined time is now considered when adding a new flag manually
11. **Date and time vanishing in playback view upon refresh** **Issue:** Event details such as date & time from the title would disappear upon refresh. **Solution:** The fix has been made to ensure the title does not disappear after a page refresh.
12. **Preflight checks configuration approval** **Issue**: When Preflight checks were not configured for a Proview session, the proctor was still able to view preflight checks with random images and always on ‘Waiting for approval’ status for attendee, interrupting attendees to continue with the session. **Solution**: With the current fix, both attendee and proctor will only be able to view the relevant preflight checks and non-configured preflight checks will not be part of the workflow.
13. **Camera grabs are not triggering for Primary camera** **Issue**: Camera grabs were not getting triggered for sessions. **Solution**: Attendee screen grabs are now visible in the playback view.
14. **Primary camera audio is muted** **Issue:** The proctors were not able to mute attendees’ audio during live proctoring sessions leading to confusion due to multiple audios streamed from all the attendees. **Solution:** With this fix, the attendees audios can be muted by the proctor enabling them to listen to the audios which they want to and mute the other videos.
# June 2024 Release Updates
Source: https://docs.talview.com/releasenotes/q2-2024/release-notes-june-2024
Welcome to the June release notes, where you can explore the most recent enhancements on TOP and Proctoring.
## Workflow Tools & Candidate Experience
### **Intelligent Scheduler enhancements**
1. **[Automatic Status Change of Interviews](https://portal.productboard.com/ds8uersvkfqrlqmyubqxam75/c/70-automatic-status-change-of-the-meetings?\&utm_medium=social\&utm_source=starter_share):** Automates the status updates for meetings, candidates, and interviewers based on interview events such as joining, completion, and no-shows, ensuring real-time accuracy and improved tracking.
2. **[Allow Only Interviewers to Perform RSVP Actions](https://portal.productboard.com/ds8uersvkfqrlqmyubqxam75/c/71-allow-only-interviewer-rsvp-actions?\&utm_medium=social\&utm_source=starter_share):** Restricts RSVP actions to interviewers via the ICS file and email, and ensures interviews appear on interviewers' calendars, enhancing scheduling control and clarity.
3. **[Inclusion of Join Links in ICS Files](https://portal.productboard.com/ds8uersvkfqrlqmyubqxam75/c/73-include-join-link-in-the-ics-file?\&utm_medium=social\&utm_source=starter_share):** Integrates join links for online interviews and location links for offline interviews directly into calendar invites, enabling participants to access interview details from their calendars easily.
4. [**Adding a Static Link in Interviewer Email:**](https://portal.productboard.com/ds8uersvkfqrlqmyubqxam75/c/74-include-static-link-in-interviewer-email?\&utm_medium=social\&utm_source=starter_share) Inserts a static link in interviewer emails based on the Growthbook flag, directing them to additional external resources to support interview preparation and performance.
### **Screening enhancements**
**[Resume Upload and Viewing in Workflow Tools](https://portal.productboard.com/ds8uersvkfqrlqmyubqxam75/c/72-allow-resume-upload-by-recruiters?\&utm_medium=social\&utm_source=starter_share):** Allows recruiters to upload candidate resumes and view them with zoom options from the Workflow Tools interface during the screening step, streamlining document management and evaluation.
### **Candidate experience**
\*\*New test taker experience: \*\*This update enhances the candidate's experience during assessments by
1. Providing immediate feedback on correct or incorrect post-question submission
2. Score visibility at the end of the assessment
3. Allow assessment reattempt
4. Provide detailed feedback opportunities
5. Comprehensive assessment pre-instructions before starting the assessment. Check out the below flow:
**Who are the primary users of this feature?**
> The features mentioned above will provide the greatest benefit to the **tenant admins**, **recruiters, master recruiters, interviewers,** and the **candidates.**
**What are we working on next?**
1. Screening step integration with WFT
2. Assessment step integration with WFT
3. Recruiter digest emails
4. Test taker experience enhancements - Async and skip-enabled workflows, LTI integration
5. SMS workflows for RSVP negotiations
6. Evaluator workflow on WFT
**Are there any known issues (caveats)?**
* IS emails cannot be customized, only an external link can be added at an organizational level
## Interview Rooms
**Switch themes Light & Dark Mode**
* **Description**: Light and dark mode options in live interviews enhance user experience by providing visual comfort and adaptability to different lighting conditions
* **Benefits**: User Preference, Enhanced Visibility.
**Guide-Interview Builder - (WIP)**
* **Description**: Streamline your live interviews with an Interview Builder, enabling customizable and structured question sets for a seamless and efficient interview process.
* **Benefits**: Consistency and Fairness, Efficiency, Customization, Improved Candidate Experience, Enhanced Decision-Making.
**Effects- Organization background branding**
* **Description**: Enhance your live interviews with Organization background branding for a polished and professional appearance.
* **Benefits**: Increased Brand Visibility, Professionalism, Engagement, Marketing Opportunity, Consistency.
**Private Chat**
* **Description**: Interviewers' chat during live interviews facilitates real-time collaboration and seamless communication between interviewers.
* **Benefits**: Real-time Collaboration, Seamless Communication, Confidentiality, Efficiency, Coordination.
**Minimum interview duration Notification**
* **Description**: Interviewers receive alerts for interviews to meet the minimum duration requirement.
* **Benefits**: Compliance, consistency
### **Feature Enhancements**
* Added 'Recording Disabled' notification to panel based on candidate consent.
* Added code block, link and attachment in Chat & Private chat
### **Bug Fixes**
We have focused on closing the high-priority bugs listed below
* Bugs on Interview Builder
* Chat message notifications
* Candidate consent flag check consent notification to interviewer on no recording
* Feedback UI for Mobile
* Fixed Device settings modal for mobile
**Who are the primary users of this feature?**
Candidates & Interviewer
To Explore the platform
These features are available in the Recruit production environment.
**What are we working on next?**
* Interview Builder - WIP
* Interview Insights with Advanced Recording
## Proctoring
### Attendee Ex
1. **Face Detection Alert logging** Face detection alert now logs only when there is Face not detected in an interval of 10 seconds, reducing false trigger of alerts within short time duration.
2. **Mobile Supported Browsers** Proview is now supported on mobile devices running Android and iOS, specifically on Chrome and Edge browsers. If an attendee attempts to use any other browser, such as Safari, they will receive an error message indicating that the browser is not supported and will be prompted to switch to one of the supported browsers
**Bug fixes**
1. Default branding color and logo removed from error screens when organization branding and logo is enabled in order to maintain the brand theme even when API fails and brand colour and logo are not available.
2. The assessment continues from the point of disconnection when the secondary camera reconnects instead of restarting from preflight checks all over again.
3. When network disconnects, the candidates are asked to manually refresh the page. This will avoid the loss of video which was happening earlier.
4. The error message for Proview loading now indicates an issue with video or audio stream availability and suggests refreshing the page, clarifying the next steps to attendee.
5. Attendees can proceed without needing to grant notification permissions if notifications are blocked.
6. The "Primary camera recording stopped" alert is now triggered immediately upon disconnection.
### Proctor NG
**Enhancements**
1. **Proview configurations for AI Lite** Video recording and Screen recording are now configurable flags enabling the clients to proctor attendees and get only screen grabs and camera grabs, while generating all flag as usual. Video recording and screen recording will not be available.
Note: For clients who want to use AI Lite, disable both video recording and screen recording flags for that particular Proview token through API.
**Known issue:** If video recording is OFF and screen recording is ON, currently screen recording also is not available. This will be picked in the next iteration.
2. **LMS Dashboard - Date filter** Users can now filter quizzes based on the event dates that have been set for the quizzes.
3. **LMS Dashboard - Syncing candidate details across quizzes** It’s now possible to multi select quizzes and sync the attendee details in one shot.
4. **Alert name & Description in the alert logs** For advanced AI alerts, we now generate an alert with a short description of the potential issue. This information can be viewed in the alert logs. Note that the advanced AI alerts can only be viewed in the ‘Debug’ section currently.
5. **Restrict Username Login for SSO-Enabled Accounts** For accounts configured with Single Sign-On (SSO), a new setting is available to prevent users from logging in with a username and password. To enable this feature, include the following parameter in the user creation API: `"is_sso_only_user": true`
**Known Issue**: Users in SSO-enabled accounts with the above configuration are currently shown an incorrect error message when attempting to log in using a username and password.
**Bug fixes**
**Not getting alert "Candidate on Good Bandwidth"**
**Issue:** In Livekit, Candidate on Good Bandwidth alert is not triggering.
**Solution:** We have made the necessary fix to ensure the debug alert ‘Candidate on Good Bandwidth’ triggers whenever the candidate is on good bandwidth.
### Proview Console V8
1. **Project Dashboard** After creating a project, tenant admins can view and edit project details and access all configured flows (onboarding experience for attendees). The dashboard provides a concise summary, including the hosting location and a short project description. **How is this beneficial to the customer?** The lack of a consolidated project dashboard results in increased administrative overhead, reduced productivity, and a higher dependency on our tech support team. This inefficiency negatively affects project management and oversight, potentially impacting the overall effectiveness and satisfaction of the customer. By providing an interface for customers they become self-sufficient to create and set up different projects and flows as per their need.
**Note**: Project creation workflows are expected as part of the next release.
2. **Flow Creation** Tenant admins have three options for configuring flows within a project: creating a new flow from scratch, using a template, or duplicating an existing flow. **How is this beneficial to the customer?** Flows define the onboarding experience for test-takers. With this configurable interface, customers can tailor the onboarding process to meet the specific needs of different exams, eliminating the need to rely on our tech support team for setup. This autonomy enhances efficiency and flexibility, allowing customers to quickly adapt to varying requirements.
Note: Flow configurations will be part of the next release.
3. **Flows List Table** All flows created under a project can be accessed in the flows list table. This table includes information on who last updated the flow and when, the version, and the status. Users can access a specific flow by clicking on its name. **How is this beneficial to the customer?** Customers can easily get an overview of all flows configured under a project. These flows can be assigned to different exams based on the specific requirements of each exam, providing flexibility and streamlined management.
# May 2024 Release Updates
Source: https://docs.talview.com/releasenotes/q2-2024/release-notes-may-2024
Welcome to the May release notes, where you can explore the most recent enhancements on TOP and Proctoring.
## Workflow Tools
### **Unforking account changes**
This release introduces several new features in the Recruit and Labs applications to help unfork the current customer accounts and bring them all to Recruit. These features are controlled via different Growthbook feature flags that can be enabled or disabled at an organizational level.
* [**Permission to Edit Section Status for Recruiters and Master Recruiters**](https://talview.productboard.com/portal/4-top-roadmap/tabs/0ae6dd5d-94ea-4f84-bd11-531dfe54086a/features/27014895/detail/expanded) Recruiters and Master Recruiters now have permission to edit the status of sections within the recruitment process. This enhancement allows for greater flexibility and control over candidate management.
* [**Ability to Reschedule a Cancelled Interview**](https://talview.productboard.com/portal/4-top-roadmap/tabs/0ae6dd5d-94ea-4f84-bd11-531dfe54086a/features/27103677/detail/expanded) Users can now reschedule interviews that were previously canceled. This feature helps better handle scheduling conflicts and ensures that candidates have another opportunity to attend their interviews.
* [**Display of Consent Message for Candidate Consent Enabled Live Interviews**](https://talview.productboard.com/portal/4-top-roadmap/tabs/0ae6dd5d-94ea-4f84-bd11-531dfe54086a/features/27103653/detail/expanded) For live interviews where a candidate consent message is enabled, a consent message will be displayed to Recruiters, Master Recruiters, and Evaluators after the interview. This ensures transparency and compliance with consent requirements.
* [**Unified Evaluation Button**](https://talview.productboard.com/portal/4-top-roadmap/tabs/0ae6dd5d-94ea-4f84-bd11-531dfe54086a/features/27042523/detail/expanded) The UI now features a unified evaluation button instead of separate "Select," "Reject," and "Hold" buttons. This change has been implemented on both mobile and web platforms, streamlining the evaluation process.
### **Intelligent Scheduler enhancements**
This release introduces several enhancements to the Intelligent Scheduler (IS) to improve the scheduling and interview process. These features are designed to offer more flexibility, branding, and customization options for our users.
* [**Cancellation of IS Interviews**](https://talview.productboard.com/portal/4-top-roadmap/tabs/0ae6dd5d-94ea-4f84-bd11-531dfe54086a/features/25788561/detail/expanded) Users can now cancel IS interviews directly from both Labs and Recruit. This enhancement allows for greater flexibility in managing interview schedules, ensuring that changes can be made swiftly and efficiently.
* [**Configurable RSVP Buttons**](https://talview.productboard.com/portal/4-top-roadmap/tabs/0ae6dd5d-94ea-4f84-bd11-531dfe54086a/features/27349217/portal/expanded) The ability to turn on or off RSVP buttons in the UI from both the ICS file and the body of the email is now available. This feature is controlled by a Growthbook flag, allowing organizations to customize the RSVP process according to their needs.
* [**Offline Interviews with Workflow Tools**](https://talview.productboard.com/portal/4-top-roadmap/tabs/0ae6dd5d-94ea-4f84-bd11-531dfe54086a/features/26625689/detail/expanded) Users can now schedule offline interviews with workflow tools that include Google Maps links. This enhancement facilitates better coordination and location sharing for in-person interviews, improving the overall candidate experience.
* [**Configurable Custom Domain**](https://talview.productboard.com/portal/4-top-roadmap/tabs/0ae6dd5d-94ea-4f84-bd11-531dfe54086a/features/27349237/detail/expanded) Organizations can now configure a custom domain for the candidate experience to reflect their brand value. This feature ensures that the candidate's interaction with the recruitment process is consistent with the organization's branding and professional image.
* [**Customer SMTP Integration**](https://talview.productboard.com/portal/4-top-roadmap/tabs/0ae6dd5d-94ea-4f84-bd11-531dfe54086a/features/16963443/detail/expanded) The IS emails can now be sent from the customer’s email address through customer SMTP integration. This enhancement allows for better email deliverability and consistency, ensuring that communication with candidates is seamless and branded.
### **Evaluation 360 updates**
This release introduces new features in the Evaluation 360 module to enhance the interview management and evaluation processes. These features are designed to provide more control and customization options for our users.
* [**Interview Filters**](https://talview.productboard.com/portal/4-top-roadmap/tabs/0ae6dd5d-94ea-4f84-bd11-531dfe54086a/features/26759803/detail/expanded) Users can now filter out the assigned interviews using the new interview filters. This enhancement allows evaluators to easily manage and organize their interview assignments, ensuring a more efficient evaluation process.
* [**Restricting Evaluation on Detailed View**](https://talview.productboard.com/portal/4-top-roadmap/tabs/0ae6dd5d-94ea-4f84-bd11-531dfe54086a/features/27268745/detail/expanded) Evaluation of the detailed view can now be restricted to customers using an evaluation form. This feature is controlled by a Growthbook flag, allowing organizations to enforce structured evaluations while maintaining flexibility for those organizations who do not require this restriction.
### **Candidate experience**
This release introduces several enhancements to the candidate experience, focusing on privacy, mobile responsiveness, and proctoring support. These updates aim to improve the overall candidate journey and ensure a seamless and secure experience.
* [**New Consent Workflow**](https://talview.productboard.com/portal/4-top-roadmap/tabs/0ae6dd5d-94ea-4f84-bd11-531dfe54086a/features/27349229/detail/expanded) A new consent workflow has been implemented to collect candidate consent for the privacy policy and terms and conditions before proceeding with face capture for authentication and recorded interviews on Interview Rooms. This ensures compliance with privacy regulations and provides transparency to candidates about data usage.
* **Mobile Responsiveness Fixes on attend-ng:**
* The mobile responsiveness issues in the attend-ng (candidate experience) have been resolved. This ensures a consistent and user-friendly experience across all devices.
* [**Proctoring Support with V7+:**](https://portal.productboard.com/ds8uersvkfqrlqmyubqxam75/c/53-proctoring-v7-integration-with-attend-ng?\&utm_medium=social\&utm_source=starter_share)
* Proctoring support with V7+ is now in place in the attend-ng candidate experience.
### **Admin app enhancements**
This release introduces a new feature for tenant admins, enhancing the administrative capabilities of the Intelligent Scheduler. Tenant admins can now track all notifications sent for the Intelligent Scheduler in a comprehensive list view, with advanced search and filter options.
[**Notification logs with filter and search**](https://talview.productboard.com/portal/4-top-roadmap/tabs/0ae6dd5d-94ea-4f84-bd11-531dfe54086a/features/18491457/detail/expanded)
* Tenant admins can now track all notifications sent for the Intelligent Scheduler on the admin app in a list view. This feature allows tenant admins to have a detailed overview of all the notifications sent, improving transparency and accountability.
* The list view includes advanced search and filter options, enabling tenant admins to easily find specific notifications based on various criteria.
**Who are the primary users of this feature?**
> The features mentioned above will provide the greatest benefit to the **tenant admins**, **recruiters, master recruiters, interviewers,** and the **candidates.**
**What are we working on next?**
1. Automatic meeting status change
2. Screening step integration with WFT
3. Recruiter digest emails
4. Test taker experience MVP
5. Admin application MVP
6. SMS workflows for RSVP negotiations
7. Evaluator workflow on WFT
**Are there any known issues (caveats)?**
* IS emails cannot be customized, only an external link can be added at an organizational level
* Remind, reschedule, and manage attendees features are disabled for IS scheduling with Recruit and Labs
## Interview Rooms
**Switch to Whiteboarding**
* **Description**: Whiteboarding in live interviews allows candidates to visually present their thought processes and solutions in real-time.
* **Benefits**: Enhances interactive problem-solving and clearly demonstrates candidates' analytical and organizational skills.
**Enhancement in Pre-Join Lobby**
* Allow the browser/system access to the camera and microphone to join the meeting.
* Interviewers can opt to blur their background in the pre-join lobby before entering the meeting.
* Shows the number of participants already in the meeting.
**Feedback collection Interviewers/Candidates**
* Enabled a streamlined process for interviewers and candidates to provide feedback about the session in platform.
**Basic video playback recording**
* Basic playback view for recorded interviews where users can easily review and evaluate candidate performances.
**Bug Fixes**
We have focused on closing the high-priority bugs listed below
* Failing to connect on Auto fallback of service provider
* Resume view pages UI fix
* Fix on Multiple Camera device notification \
**Who are the primary users of this feature?**
Candidates & Interviewer
To Explore the platform
These features are available in the Recruit production environment.
**What are we working on next?**
* **Interview Builder- WIP**
* Streamline your live interviews with an Interview Builder, enabling customizable and structured question sets for a seamless and efficient interview process.
* **Light Mode - WIP**
* Enhance your live interviews with customizable light and dark modes for an optimal viewing experience.
## Proctoring
### Attendee Ex
**Bug fixes**
1. **Error in loading Proview error for attendees** **Issue:** Candidates were getting ‘error in Proview loading’ screen when their session got disconnected because of low network bandwidth. **Solution**: Now the candidate is shown an appropriate message suggesting the next steps - To reload the page to continue
2. **Window Focus Out Alert Trigger** **Issue:** The window focus out alert was being triggered when users clicked on an iframe embedded within the exam screen, causing unnecessary interruptions during the exam. **Solution:** The system has been updated to recognize iframe interactions on the exam screen as valid, preventing the window focus out alert from being triggered. This ensures a smoother exam experience without unnecessary alerts.
3. **UI copy enhancements on attendee** The proctoring attendee platform on V7+ has updated the UI copy for following buttons: Proceed to exam: Proceed ahead Start Test: Start environment check
4. **Multiple People Detected inaccuracy** The "Multiple People detected" alert has been improved to enhance the accuracy of its detection. Previously, the AI model checked for a people and logged the flag even when the confidence was 50% , which led to an increased likelihood of false positives. We have adjusted this confidence index to 0.72 seconds, thereby improving the efficiency of the alert.
Note: A small percentage of false alerts may still occur, as the AI model does not achieve 100% accuracy.
5. **Face Not Detected inaccuracy** The "Face Not Detected" alert has been improved to enhance the accuracy of its detection. Previously, the AI model checked for a face every 40 milliseconds, which led to an increased likelihood of false positives. We have adjusted this interval to 0.5 seconds, thereby improving the efficiency of the alert.
Note: We are monitoring this flag to improve the efficiency further, however AI model does not achieve 100% accuracy.
### Proctor NG
**Enhancements**
1. **Livekit SDK Upgrade** The Livekit SDK has been upgraded to the most recent version. This update resolves the compatibility issues previously experienced with the latest versions of the Chrome Browser.
2. **Fullscreen Mode in Embedded Playback** Customers utilizing V7+ with Livekit streaming will notice an enhancement in the embedded playback feature. While the modal pop-up does not support fullscreen viewing, users can now open the video in a new tab to access fullscreen mode. This allows for an expanded view and more immersive playback experience directly from the new tab.
**Bug fixes**
1. **Camera Switching Automatically with Multiple Cameras Available** **Issue:** When multiple cameras are connected to the system, the camera was switching unexpectedly, resulting in the video feed being sourced from an external camera. **Solution**: The issue with automatic camera switching has been resolved. The video feed and camera captures will now consistently originate from the same camera.
Note: In Edge and Chrome browsers, the default behaviour is to stream from the device's primary camera. Conversely, in Firefox browser the video streams and camera captures are from an external camera. This behaviour will be standardized across all browsers in the upcoming release.
2. **Call Duration Not Displayed in Chat Logs** **Issue**: The call duration was missing from the chat logs. **Solution**: The issue has been addressed, and the call duration will now be correctly displayed in the chat logs.
3. **Slot Timings Repeating in Event Title** **Issue**: The slot timings were appearing multiple times in the event title. **Solution**: The issue has been resolved, and slot timings will now display only once in the event title.
4. **Candidate external ID not disappearing in the event title in live view** **Issue**: When navigating from the tile view to the detailed view and back, the appended candidate external ID in the event title would persist. **Solution**: This issue has been resolved. The candidate external ID will now only be displayed when in the detailed view.
5. **Chats displayed out of order after the session** **Issue**: The messages in the chat log were being displayed out of order after the session. **Fix**: We have implemented the required fix to ensure that chats are shown in the correct sequence.
6. **Filters malfunctioning in AI\&RR accounts** **Issue**: The filters in AI\&RR accounts were not working correctly. **Fix**: Users are now able to seamlessly filter and review sessions.
Known issue: If a user adds a filter and then uses the search bar, pressing backspace instead of clicking ‘X’ to clear the search bar results in filters not producing accurate results.
7. **Approval history data absent in the embedded view** **Issue**: When viewing the Summary tab in the embedded view, the approval history was missing. **Fix**: We have implemented the necessary corrections to ensure that all approval history data is visible in the embedded view.
# April 2025 Release Updates
Source: https://docs.talview.com/releasenotes/q2-2025/release-notes-april-2025
Stay updated with the latest features and enhancements rolled out in May 2025 across Talview’s Orchestration Platform (TOP) – including Workflow Tools, Candidate Experience, Interview Rooms, and Proview (Proctoring).
## 🔧 Workflow Tools & Candidate Experience Updates
### **Workflow Tools**
1. **Long Form Display**
Recruiters can now view candidates’ **long-form responses** directly in the platform and download the attachments from submissions, enabling faster and more informed hiring decisions.
🔗 [More details](https://portal.productboard.com/ds8uersvkfqrlqmyubqxam75/c/193-display-the-long-form-assessment-response?\&utm_medium=social\&utm_source=starter_share)
2. **Evaluator & Recruiter Form Fill**
Recruiters and evaluators can now **fill and submit structured evaluation forms** (created using form builder) to capture consistent feedback during assessments and interviews.
🔗 [Evaluator Form Fill](https://portal.productboard.com/ds8uersvkfqrlqmyubqxam75/c/195-fill-evaluation-form?\&utm_medium=social\&utm_source=starter_share)
🔗 [Recruiter Form Fill](https://portal.productboard.com/ds8uersvkfqrlqmyubqxam75/c/196-recruiter-fill-evaluation-forms?\&utm_medium=social\&utm_source=starter_share)
3. **New Async Playback View**
Recruiters and hiring managers can now **review a candidate’s asynchronous interview responses** faster with timestamps, prompts, and navigation controls in async video playback.
🔗 [More details](https://portal.productboard.com/ds8uersvkfqrlqmyubqxam75/c/194-async-playback-view-for-recruiters-and-hms?\&utm_medium=social\&utm_source=starter_share)
4. **Guest Interviewer Workflows**
You can now **add guest interviewers from whitelisted domains** to interviews (in-meeting), allowing secure access without full user accounts. The whitelist can be added at a tenant level from the backend (via a firecall ticket).
🔗 [More details](https://portal.productboard.com/ds8uersvkfqrlqmyubqxam75/c/197-add-a-new-guest-user-as-an-interviewer-whitelisted-users-?\&utm_medium=social\&utm_source=starter_share)
5. **No Show Reminders**
**Automated interview reminders** are now sent to participants who haven’t RSVPed or marked themselves as Tentative, based on smart timing logic to reduce no-shows, keeping notification fatigue in mind.
Recruiters (organizers) now receive a **"Possible No-Show" email alert** if one or no participants join an Interview Rooms session within 5 minutes, enabling timely intervention and reducing interview drop-offs.
🔗 [More details](https://portal.productboard.com/ds8uersvkfqrlqmyubqxam75/c/198-pre-interview-join-reminder?\&utm_medium=social\&utm_source=starter_share)
6. **SMS Workflows**
**Interview invite SMS** **with join links** is now sent to candidates and interviewers with valid phone numbers for online interviews scheduled via Intelligent Scheduler.
🔗 [More details](https://portal.productboard.com/ds8uersvkfqrlqmyubqxam75/c/199-sms-without-rsvp?\&utm_medium=social\&utm_source=starter_share)
7. **Notification Inbox Enhancements**
You can now **reply, forward, and mark notifications as read or unread** directly from the Notification Inbox for faster, more efficient candidate and evaluator communication.
📽️ Check out the video below -
[https://app.arcade.software/share/x6GIhQV8oz1H3Q0vPkz7](https://app.arcade.software/share/x6GIhQV8oz1H3Q0vPkz7)
### **Candidate Experience**
1. **Payment Completion Invoice**
An itemized, mobile-friendly invoice is now generated and shared via the UI and confirmation email post-payment, detailing SKU, amount paid, discounts, taxes, and final amount.
2. **Bug Fixes & UI Improvements**
Addressed critical bugs and made minor UI enhancements in the payment flow based on customer feedback.
3. **Candidate Timezone Detection**
Candidate timezones are now automatically detected and stored to display all schedules and notifications in their local time, reducing confusion and missed sessions.
## 🎤 Interview Rooms Updates
1. **Invite non-registered users on the fly (WFT)**
**Description**: Instantly invite non- registered users to join live video interviews with a single click, ensuring seamless interview experience.
**Benefits**:
* **Flexibility:** Accommodate additions to the interview panel during the meeting
* **Increased Efficiency:** Streamline interview operations by enabling real-time participation of non-registered users.
**Interviewer inviting non-registered users flow**
**Non-registered users join flow**
2. **In-meeting Diagnostics-WIP**
**Description**: In-meeting diagnostics now show camera list dropdown with preview, mic and speaker dropdowns, and an audio output bar to help with easier troubleshooting.
**Benefits**:
* Quickly identify and switch between connected devices without leaving the meeting
* Troubleshoot audio/video issues on the spot, reducing downtime
* Monitor mic and speaker performance with real-time indicators
**Device**
**Feature Enhancements**
1. \*\*Sound Notifications for New chat: \*\*Sound notifications alert users instantly when a new chat message is received and chat tab is not in focus.
\*\*Participant Join/Leave Audio alerts: \*\*Plays a subtle audio cue when a participant joins or leaves an interview session to confirm their entry or exit.
🐞 **Bug Fixes**
We have focused on closing the high-priority bugs listed below
* Fixed an issue where users were unable to take actions on notifications in the mobile app.
* Updated the network indicator icons displayed in the video tile tags for improved clarity and consistency.
* Added support for Secondary Camera in the Recruit flow.
## 👥 Proview (Proctoring) Updates
### **Attendee Experience**
### **🆕 Feature**
1. **Alvy Monitoring on Secondary Camera**
Alvy now supports monitoring through a mobile phone as a secondary camera, providing a wide-angle view of the test taker’s surroundings. This enhancement improves exam security by offering better visibility and enabling the detection of any suspicious activities.
**Note**: Enhancements are being done on some of the known observations on Alvy monitoring currently. This feature will be available to use from next week.
**Attendee interface is now available in German Language**
Test takers in proctored sessions can now switch to German language from the dropdown and continue to use the platform in German language if the language is configured for the organization.
**Enhancements**
1. **Handling Unsupported Network Error Message**
A network connection not supported for proctoring was leading to loss of audio and video. With this update, test taker’s network will be checked at the beginning of the session and stopped them from moving further if the network is not supported. **The test taker should switch to a different network in order to proceed with the test.**
**🐞Bug Fixes**
1. **Audio check set to be true by default**
**Issue:** If audio\_check setting is not configured for the token then by default value of audio\_check was being set to false. **Solution:** With this update if audio check is not configured, default audio check will be configured to TRUE for that token.
2. **Unable to type while uploading an image in chat**
**Issue:** When an image is being uploaded, candidate wasn’t able to type anything in chat.
**Solution**: Now the image once uploaded can’t be sent unless and until text is entered in the chat. The send button only comes into enabled state when text is entered for the corresponding image.
This text description is helpful in providing context to Alvy for better understanding.
### **Proctor NG**
### **🆕 Feature**
1. **Alvy - Reject functionality for Proctor**
Along with Accept and Edit, Reject is now added to the actions proctor can perform on Alvy generated messages.
Rejected messages will not be sent to test taker but proctor or admin can view them in playback view.
**Photo ID check with Alvy**
In a live proctored session, test taker’s photo ID is compared with the base image available and Alvy sends a message on success or failure ID card check. An alert ‘AlvyIDCardCheck’ is logged with description of the result.
**💡Enhancements**
1. **Updated dispositions for modifying proview index**
The dropdown has been updated to include new dispositions for modifying proview index.
Hovering over a disposition will highlight what it means.
[updated-dispositions.mov](http://updated-dispositions.mov)
2. **Updated tile status after student’s disconnection**
When the candidate has gone offline and an attempt is being made to reconnect with the video streaming provider, then the proctor is notified about that candidate’s state via the label “Reconnecting”.
The label will also appear on the secondary camera stream.
3. **Alert Name Update: Low bandwidth to Poor Network Quality.**
This is being done to clearly call out when network quality is poor even though the bandwidth might be above required value.
We have four different flag names impacting with this update:
1. Primary Device Good Network Quality
2. Primary Device Poor Network Quality
3. Secondary Device Good Network Quality
4. Secondary Device Poor Network Quality
4. **Alvy Monitoring - Flag configurations**
Alvy flags are now configurable to display only limited number of times to the proctor and candidate, based on prompt\_min\_occurence value set.
**Note:** Proview Index is not impacted for these flags where severity set to None. If Severity is set to Critical, High, Medium or Low, then Proview Index is impacted accordingly.
5. **Alvy - Browser specific responses**
Alvy assisting agent now picks browser details of the test taker and gives browser specific instructions and answers helping test taker resolve issues step by step.
6. **Secondary camera grabs are now configurable**
When a secondary camera is enabled for a session, Secondary camera grabs can be enabled or disabled. The grabs will be disabled by default.
**How to enable:**
Pre requisite: Enable Secondary camera configurations
7. **Updated proctor approval checks in alert logs**
When a candidate submits a pre check for approval, the proctor’s action will now contain description in the alert log.
For eg: When candidate submits photo ID pre check, when the proctor approves it, the alert generated will say - Precheck Approved, with description - ID Validation.
This description will help in distinguishing between the type of validation that was approved/rejected by the proctor.
> The alert description will only be displayed in the playback view - post session completion and not in the live monitoring view.
8. **Filter to only view “Added” flags in alert logs**
A new “Added” filter has been added, by which a user will be able to see only the manually added flags in the alert logs.
9. **New precheck flags for manual addition**
The following flags are now available in the drop down for manual addition:
* Precheck Approved - ID Validation
* Precheck Rejected - ID Validation
* Precheck Approved - Environment Validation
* Precheck Rejected - Environment Validation
These flags are useful when a proctor has to validate the candidate’s ID or environment check submission when taken in Record & Review proctoring.
10. **Update messaging in playback view for AI lite**
When a reviewer accesses the playback of a session taken in AI lite, then the following message will be shown, avoiding confusion over video availability.
11. **Secure Browser Default Blacklisting applications**
With the latest update, we have updated the default blacklisted applications for all users, ensuring any sort of Web Browsers, Communication Tools, Screen Recording and Screenshot Tools or Remote Desktop Applications are blocked for accessing during the proctored session. **Note:** This list will be constantly updated. Please reach out if you have any suggestions for applications that needs to be blacklisted.
### **🐞Bug Fixes**
1. **Image of validation checks wasn’t being displayed in forwarded chat message**
**Issue:** The image submitted for approval wasn’t displayed in the chat on proctor’s side when forwarded to candidate
**Solution:** The issue has been resolved. When candidate uploads a validation check image for approval, the message sent from proctor will have both - Alvy’s comments and the evidence image.
2. **Multiple events getting triggered for “Terminate” and “Extend” session actions**
**Issue:** When the user would perform an action - “Terminate” or “Extend” session one time, the corresponding event was getting triggered multiple times.
**Solution:** The issue has been resolved now, and an event is logged only once for each action.
***
### **Proview Console (V8)**
### **🆕 Feature**
1. **Added filters on Proview Assessment Table**
Added option to filter by
* Attendee
* Session rating
* Accommodations
* Status
* Completed on
2. **Edit Assessment + Side Panel for Proview Assessments**
Have introduced a side panel which loads on clicking the Edit button on Proview Assessments
3. **Option to view External assessments list on the console**
Coordinators will be able to view list of all the exams/courses configured along with the configured workflows for each of the exams
1. Add link to exams view in navigation menu
2. Exam view is integrated with workflows (Each exam can have multiple workflows)
3. Added breadcrumb navigation on drilldown from one screen to the other for the user to be able to navigate back (Exams > Workflows > Candidate view)
### **💡Enhancements**
1. **UX changes on Save Changes button in flow Configuration**
Under Flow Configuration > custom branding, “Save changes” button would disappear when no changes were made. To keep it consistent, the “Save changes” will always exist. If there are no changes to be made, it will be disabled, for now.
2. **Flow Configurations - Ability to upload company logo for custom branding**
We have added the option on the console for the client to upload the logo for custom branding
[https://app.arcade.software/share/v4P6VqAXRIn3ZzJmf96Y](https://app.arcade.software/share/v4P6VqAXRIn3ZzJmf96Y)
3. **Redirection from Workflow table to attendee view**
We have linked the workflow table to the attendee table, where in you will be able to view the list of attendees applicable to the workflow
4. **Updated the permissions for Tenant Admin and Coordinator**
The read, write, and delete permissions have been updated for the tenant admin and tenant coordinator roles based on the matrix [here](https://www.notion.so/1d53461472f38068a0acc8b05f7351c4?pvs=21).
5. **Updated the navigation menu on Console**
Hidden Sessions, events, notification and help center from the menu. These options will be brought back whenever the respective modules are ready.
### **Integrations (V7+)**
### **🆕 Feature**
1. **Self onboarding form for Thinkific & Cornerstone LMS**
Administrators using Thinkific or Cornerstone LMS can now follow these steps to complete & authenticate their installation from the LMS dashboard without having to sharing their admin credentials.
* Log into the LMS dashboard
* Click on LMS configuration button.
* Fill in the fields - Proview username, password, Redirect URL & Name(optionally).
* Once credentials are verified successfully, click on the **Update Configuration** button.
Screen Recording 2025-04-15 at 2.05.17 [PM.mov](http://PM.mov)
2. **Docebo LMS integration**
Proview is now integrated with Docebo LMS via the browser extension. A user can:
* Configure proctoring (Recorded, R\&R)
* Attempt a proctored test
* View playback of the proctored test
\
3. **Self onboarding form for Docebo LMS**
Administrators using Docebo LMS can now follow these steps to complete & authenticate their installation from the LMS dashboard without having to sharing their admin credentials.
* Log into the LMS dashboard
* Click on LMS configuration button.
* Fill in the fields - Name, Proview username, password & Redirect URL.
* Once credentials are verified successfully, click on the **Update Configuration** button.
4. **Self-onboarding form for Moodle LMS**
Administrators using Moodle LMS can now follow these steps to complete & authenticate their installation from the LMS dashboard without having to sharing their admin credentials.
* Log into the LMS dashboard
* Click on LMS configuration button.
* Fill in the fields - Name, Web service function, Web service token, Web service URL.
* Once the fields are filled, click on Verify button. In the modal, enter a valid course ID.
* Upon successful verification, click on the **Update Configuration** button.
### **🐞Bug Fixes**
1. **Candidate is able to bypass proctoring in Docebo LMS**
**Issue:** In docebo LMS, because proctoring loads in another tab, student was previously able to copy the test URL, and paste it in a new window. This would allow them to bypass the proctoring and give the test unmonitored. **Solution:** The issue has been resolved. Proctoring will now load in an iframe on the same tab the test is being give on.
# June 2025 Release Updates
Source: https://docs.talview.com/releasenotes/q2-2025/release-notes-june-2025
Stay updated with the latest features and enhancements rolled out in June 2025 across Talview's Orchestration Platform (TOP) – including Workflow Tools, Candidate Experience, Interview Rooms, and Proview (Proctoring).
## 🔧 Workflow Tools & Candidate Experience Updates
### **Workflow Tools -**
1. **Notification Inbox Enhancements**: Added a keyword search bar atop the Notifications Inbox that surfaces matching notifications in real time as you type. Matched terms are highlighted in each result, letting recruiters and master recruiters pinpoint and act on relevant alerts immediately.
Check the video below -
2. **Candidate Status Updates:** Recruiters can update candidate workflow statuses to Selected, Turned Down, or On Hold via single-click actions in the candidate profile or bulk updates from the candidate list in any step inside the workflow. All changes sync immediately to the workflow dashboard for up-to-date pipeline visibility.
Check the video below -
3. **Recruiter Summary Email:** An automated summary email is now sent to the meeting organizer immediately after each interview, listing all attendees and indicating whether the candidate consented to recording. This gives the recruiters accurate visibility into attendance and consent without any manual tracking.
***
### Candidate Experience -
1. **Ivy AI Interviewer Enhancements**
* **AI-Based Competency Scoring:** Automatically evaluates conversational interview responses against pre-configured competencies and rubrics (via backend - providing objective, consistent scores.
* **Saving the Transcript and Visual Analysis data for report:** Securely store all conversation transcripts coming in from Tavus with each candidate's profile for easy retrieval, audit compliance.
Save Tavus-derived non-verbal insights (facial expressions, engagement, sentiment) alongside transcripts, ensuring recruiters and hiring managers retain critical context throughout the hiring process.
This will be published in the reports in the upcoming release.
2. **CleverBridge Payment Integration**: CleverBridge is now available as a payment provider supporting both Book & Pay and Pay & Book flows directly within the candidate experience. It can be enabled at the workflow level, with all transactions synced to the billing records.
3. **External Assessment iFrame Integration**: Vendor-hosted assessments (e.g., Tavus) can now be embedded directly into the new candidate experience via a secure iframe, configurable at the workflow level, with results auto-syncing to candidate profiles.
Candidates complete assessments in-platform without redirection, and recruiters & evaluators access consolidated results natively within Talview.\
Check the video below -
## 🎤 Interview Rooms Updates
### Feature Enhancement -
**COBOL Language Support in Codesolo & Codejam:** Added COBOL as a supported language in Codesolo and Codejam coding environments.
This enables solving problems in COBOL, expanding language options for diverse technical assessments.
### Bug Fixes -
We have focused on closing the high-priority bugs listed below
* Fixed issue where on-the-fly invited users were not showing under the *Other Invited* section
* Resolved problem preventing the *Environment Check* from launching via the **View** button in the notification
* Fixed broken effect images in *Pre-Join Lobby* and *In-Meeting* screens
* Resolved bug where clicking *Codejam* led to unexpected session exit for candidate/interviewer
* Fixed issue preventing 360 environment captured images from displaying *In-Meeting*
* Addressed issue with 360° environment images showing incorrect uniform timers; timers now reflect individual captures
* Fixed issue causing user termination when clicking the *Evaluate* button during a meeting
* Addressed the VOIP bug showing "Call is in progress" instead of connecting the call
* Resolved bug causing recording to start even when candidate consent was not provided
* Resolved inconsistency showing *Sample Test* for candidates and *Quick Test* for interviewers in Codejam
* Fixed issue where enabling echo cancellation or noise suppression caused sound echoing for both participants
* Fixed issue where the VOIP call pop-up did not display the phone number in encrypted format
* Addressed visibility problem with noise suppression and echo cancellation labels in light mode
***
## 👥 Proview (Proctoring) Updates
### **Attendee Experience**
* **Safe Exam Browser Support (Windows Only)**: Safe Exam Browser (SEB) is now available on Windows as an alternative secure exam environment, configurable per domain.
* **Clearer Error Messages for Session Issues**: Updated system messages now provide specific guidance when candidates try to rejoin completed, terminated, or expired sessions.
***
### **Proctor NG**
* **Standardized Alvy Alert Labels**: Unified labeling for Alvy-detected behaviors ensures consistent messaging for both candidates and proctors.
* **Confidence Levels for Integrity Flags:** Alvy-generated flags in the integrity report now show High, Medium, or Low confidence levels for better evaluation context.
* **Expanded Integrity Report Coverage:** Integrity reports now include both Alvy and system-generated critical flags, categorized as Critical Violations and Supporting Observations.
* **Alvy Chat Pop-Up Fix:** Resolved an issue where messages from Alvy weren't triggering the candidate chat window during sessions.
***
### **Proview Console (V8)**
* **Multi-SKU Voucher Association:** Coordinators can now link multiple SKUs to a single voucher during creation for broader applicability.
***
### **Integrations (V7+)**
* **Removed Secure Browser Options from Unsupported LMSs**: Secure Browser settings have been removed from LMS platforms (Cornerstone, Docebo, Thinkific) where the feature is not supported, reducing setup confusion.
***
# May 2025 Release Updates
Source: https://docs.talview.com/releasenotes/q2-2025/release-notes-may-2025
Stay updated with the latest features and enhancements rolled out in May 2025 across Talview’s Orchestration Platform (TOP) – including Workflow Tools, Candidate Experience, Interview Rooms, and Proview (Proctoring).
## 🔧 Workflow Tools & Candidate Experience Updates
### **Workflow Tools**
1. **Pre-assessment & Pre-interview forms**
**What’s New:**
Candidates can now fill out pre-assessment or pre-interview forms to submit additional details before their assessments or interviews.
Recruiters and Evaluators can view submitted forms directly in the Workflow Tools platform, ensuring they’re better prepared for interactions. This leads to more informed evaluations.
2. **Interview notification enhancements (Post-Interview Notifications)**
**What’s New:**
Automated notifications are now sent to both candidates and interviewers once an interview concludes. These can include thank-you messages, attendance status, and help maintain engagement post-interview.
**Value Addition:**
Reduces manual follow-ups by recruiters, improves candidate experience, and supports a smoother end-to-end interview lifecycle.
3. **"Running Late" Status Option**
**What’s New:**
Candidates and interviewers now have the option to indicate they are "Running Late" directly from the interview join reminder. Upon selecting this option:
* They are redirected to a page to confirm the delay
* They can add an optional message (e.g., “Stuck in a meeting”)
* The message is instantly shown in the Interview Room UI to the participant who has already joined.
4. **SMS Notifications to candidates and interviewers**
**What’s New:**
SMS notifications can now be automatically triggered to both candidates and interviewers for critical scheduling actions through the **Intelligent Scheduler**, including:
* Scheduling online or in-person interviews
* Rescheduling online or in-person interviews
* Informing a participant when the other has joined
**Value Addition:**
Improves real-time coordination, ensures higher attendance rates, and supports users with limited email access.
5. **Notification Inbox Enhancements**
**View Notification Status**
**What’s New:**
Users can now view the delivery and interaction status of all notifications (Email, SMS) sent through the platform, such as: Delivered, Read, Unsubscribed, Failed etc.
**Value Addition:**
Brings transparency and helps recruiters and admins assess message effectiveness or troubleshoot communication issues.
**Track SMS Sent to Participants**
**What’s New:**
All SMS messages sent to candidates or interviewers - are now logged in the **Notification Inbox**. Users can see full message content, timestamps, and recipient details.
### **Candidate Experience**
1. **Refund invoice**
**What’s New:**
Users receiving a refund now get an **auto-generated invoice** with complete transaction details, including: Refund amount, Transaction ID, Timestamp. The invoice is available in the UI and will be sent via email (*in the next release*).
2. **Configure Visibility of Reschedule & Cancel Links**
**What’s New:**
Platform Admins now have granular control over whether **Reschedule** and **Cancel** links are visible to candidates after they book a slot.
**Value Addition:**
Empowers organizations to enforce **stricter scheduling policies** or meet **compliance needs** by restricting post-booking changes when required.
3. **Set Cut-off Time for Slot Reschedule & Cancellation**
**What’s New:**
Admins can now define **cut-off thresholds (in hours)** before a scheduled slot, after which the **Reschedule** and **Cancel** actions will be restricted for candidates.
**Value Addition:**
Enables organizations to reduce **last-minute disruptions**, improve **interviewer preparedness**, and align scheduling flexibility.
4. **Slot Display & Update Before Payment**
**What’s New:**
Candidates in the **Book & Pay** workflow can now:
* **Review** their selected slot
* **Modify** it before proceeding to payment
5. **Proctoring V7+ Integrated with New Test-Taker Experience**
**What’s New:**
**Proctoring V7+** is now seamlessly integrated with the **CX 3.0 test-taking experience**, allowing candidates to:
* **Record and submit** their pre-flight checks
* **Complete assessments smoothly** with fewer disruptions
### **Bug fixes and minor enhancements in the payment flow**
* The refund amount now correctly shows as **zero** when a **100% coupon** is applied.
* **Unavailable dates** are now clearly greyed out in the calendar view.
* Candidates can now **seamlessly complete slot booking** via the *Pay and Book* flow when payment is successful, but booking fails in *Book and Pay* scenarios.
* **The slot order** is now displayed in proper **serial sequence**.
* **Duplicate slots** have been removed; only **unique time slots** are shown.
* **Refund amounts** for rescheduling and cancellations are now **rounded off** to the nearest whole number.
* A **tax disclaimer** is now shown to candidates **before proceeding** with payment - check out the screenshot
* **Refund display issues** in the cancellation flow have been fixed.
* **The browser back button** now works as expected and redirects to the configured **returnURL** in the parent application, if set.
## 🎤 Interview Rooms Updates
1. **360 degree environment check on interviewer request**
* **Description**: Enables interviewers to request a 360-degree environment check for candidates during interviews.
* **Benefits**: Enhances transparency, ensures a distraction-free setting, and improves interview integrity.
### **Interviewer View**
### **Candidate Web View**
### **Candidate Mobile View**
2. **Wait notification- Decline from email status visibility in Interview Rooms**
* **Description**: Introduced support to reflect meeting declines from email directly in the live session view for other participants.
* **Benefits**: Improves visibility into participant availability, helping others manage expectations and reduce wait time during sessions.
3. **Noise Suppression in Interview Rooms**
* **Description**: Enabled noise suppression to automatically filter out background disturbances during live sessions.
* **Benefits**: Delivers clearer audio, minimizes distractions, and enhances overall communication quality for all participants.
4. **Echo Cancellation in Interview Rooms**
* **Description**: Implemented echo cancellation to eliminate audio feedback and echo during live sessions.
* **Benefits**: Ensures smooth, interruption-free conversations with improved audio clarity for all participants.
5. **Sound Notifications on Call disconnection**
* **Description**: Sound notifications alert users when a call gets disconnected.
* **Benefits**:
* Helps users quickly recognize disconnections
* Reducing confusion and enabling faster rejoining or follow-up
### **Bug Fixes**
We have focused on closing the high-priority bugs listed below
* Enabled copy paste in codejam for interviewers
* Fix on generation of guide for IR recruit
* Disabled the evaluate tab for non-registered guest users
## 👥 Proview (Proctoring) Updates
### **Attendee Experience**
* **Broken Logos on Network Disconnection:** Fixed an issue where logos were not displaying correctly if the test taker lost internet connection. Logos now load seamlessly on UI recovery.
* **Alvy AutoPilot Mode:** Alvy can now fully manage live proctored sessions autonomously—handling ID checks, environment scans, behavior monitoring, issuing warnings, and generating summaries - without a human proctor.
### **Proctor NG**
* **Pre-Flight Pause Disabled:** The pause option is now disabled during pre-flight checks and only becomes available once the test begins.
* **Secondary Camera Reconnection Indicator:** When a candidate’s secondary camera disconnects, a "Reconnecting" label is now shown on the proctor’s view for better visibility.
### **Proview Console (V8)**
* **Coordinator Transactions Report:** Coordinators can now view and export financial transaction data related to assessments directly from the dashboard. Fields include transaction ID, candidate email, status, and date.
* **Voucher Management Improvements:**
* SKU selection is now mandatory when creating vouchers.
* External workflow IDs are shown alongside names to reduce confusion in case of duplicates.
### **Integrations (V7+)**
* **Canvas & D2L:** Passwords are auto-injected into secure browser (SB) sessions, preventing access via dev tools and ensuring secure quiz entry.
* **Cornerstone LMS – Multi-Attempt Support:** Admins can now configure up to 6 attempts per quiz using the LMS dashboard.
* **Thinkific LMS – In-Quiz Alert Display:** Candidates now receive real-time alerts like “Face Not Detected” or “Multiple People Detected” directly in their quiz tab.
* **CSOD – Post-Quiz Candidate Data in Console:** Candidate details (name, ID, session data) are now shown in the Proview Console after both AI proctored and R\&R quizzes.
* **LMS Dashboard – Rich Text in Instructions:** Instruction fields now support rich text formatting, including bold, italics, bullet lists, and hyperlinks.
### **Alvy**
* **Alvy on AutoPilot Mode:** Alvy now manages full proctored sessions without proctor involvement.
* **Alvy Screen Monitoring Fix:** Improved Alvy to ignore inactive or Talview-required apps during screen monitoring.
# April 2026 Release Updates
Source: https://docs.talview.com/releasenotes/q2-2026/april-2026-release-updates
The April 2026 release delivers enhancements across **Workflow Tools, Interview Rooms, Assessment Engine & Candidate Experience, and Proctoring**, introducing improved candidate readiness checks, richer interview insights, expanded assessment reporting, and reliability improvements across workflows, sessions, and proctoring.
***
## Workflow Tools Enhancements
This month, we introduced enhancements focused on **improving candidate readiness, platform stability, and scheduling reliability**.
#### 🆕 Feature
**1. System Check Embedded in Candidate Emails**
**Description:** Candidates now see a device and connectivity check prompt embedded directly below the CTA in their Talview emails, guiding them to verify their system setup before an interview or assessment.
**What's New**
* System check prompt rendered below the primary CTA in all candidate email templates.
* Covers browser compatibility, camera, microphone, and network checks.
* No action required from Recruiters - applies automatically to all outgoing emails.
***
#### 🐞 Bug Fixes
1. **Workflow Tools - Platform Stability**
* Evaluator reminder emails not triggering for pending evaluations.
* Candidate invitation emails failing to send after an invite action.
* New notifications not appearing without a page refresh, now appear in real time.
* Unified assessment steps incorrectly marked as "Completed" after the first section.
* Ivy AI total score displaying as 0 in the score side panel.
* Proview index not visible in tabular view and side panel.
* Candidate list not loading for Evaluators.
* Time slab display breaking for slots ending at 12:00 AM.
2. **Scheduler - Payment, Booking & Notification**
* Sessions scheduled despite failed payments.
* Candidates unable to retry after a failed transaction.
* Incorrect redirect from the payment gateway back button.
* Sessions incorrectly scheduled 14 days out.
* Slots not appearing when refreshing the booking page mid-flow.
* Slots incorrectly marked as holidays when another interviewer was available.
* Reminder emails incorrectly triggering for Intelligent Scheduling users.
***
## Proctoring Updates
This month, we introduced enhancements focused on **improved session management, candidate-level actions, and LMS integration upgrades**.
### Attendee Experience (V8)
#### ⚙️ Enhancements
1️⃣ **ID Verification Enhancements** \
**Description:** Improved ID verification now checks for document expiry, date-of-birth anomalies, and validates that the captured ID matches the intended document.
2️⃣ **Consent Data Shown Based on Configurations** \
**Description:** The consent page now shows only relevant Terms and Conditions content based on what is configured, ensuring candidates see accurate information when camera and screen sharing are disabled.
#### 🐞 Bug Fixes
* Disabling microphone was also disabling camera permissions.
* Incidents not triggering consistently.
* Floating widget overlapping exam MCQ sections.
* Camera and audio monitored after session completion.
***
### Center Management (V8)
#### 🆕 Features
**1. Suspend a Candidate's Session** \
**Description:** Proctors can now terminate a candidate's session directly from the monitoring dashboard when a serious violation is detected.
**What's New**
* A reason for suspension must be selected before confirming.
* The candidate is immediately shown a session terminated screen upon suspension.
**2. Add Note to a Candidate's Session** \
**Description:** Proctors can now add internal notes to a candidate's session at any point during onboarding or the exam.
**What's New**
* Notes can be added using the "Add Note" option in the dock.
* Notes are visible only to the proctor and their organisation and can be referenced when reviewing completed sessions.
**3. Visualization of Events on Incident Timeline** \
**Description:** Hovering over an incident marker on the session timeline now reveals a pop-up showing all flagged events grouped to form that incident.
**What's New**
* Pop-up shows all events flagged and grouped to form that incident, along with their individual timestamps.
* Helps proctors and reviewers quickly understand what occurred during a suspicious moment without scrubbing through the recording.
**4. Candidate Session Profile in Center Console** \
**Description:** Center admins can now click on any candidate in the candidate list to view a detailed profile of that candidate's session.
**What's New**
* Shows registration details, check-in information, and captured submissions with match and mismatch indicators.
* Displays a chronological timeline of key events including incidents and exam milestones.
**5. Candidate Level Actions in Center Console** \
**Description:** Center admins can now take candidate-level actions directly from the console.
**What's New**
* **Report Incident:** Center admins can report an incident against a candidate with a description and action taken.
* **Mark Absent:** Center admins can mark a candidate as absent when they fail to show up for their exam.
* **Decline Booking:** Center admins can decline a candidate's exam booking before they have appeared for the exam.
#### ⚙️ Enhancements
1️⃣ **Video Evidence for Incidents in Summary Report** \
**Description:** Each incident in the session summary report now includes video evidence captured at the time of the incident.
**What's New**
* Reviewers can watch relevant video clips directly within the report.
* Makes it easier to assess incidents without scrubbing through the full session recording.
#### 🐞 Bug Fixes
* Clicking within an incident region always jumped to the start - now seeks to the exact point clicked.
***
### Integrations (V7+)
#### 🆕 Feature
**Upgraded Moodle LMS to Version 5.1** \
**Description:** Talview now supports Moodle version 5.1, with all proctoring types and secure browser capabilities.
***
## Interview Rooms Enhancements
This month, we introduced enhancements focused on **improving code execution reliability, session recording, and session stability**.
#### ⚙️ Enhancements
1️⃣ **CodeJam - Migrated to Judge0 Execution Engine**\
**Description:** CodeJam code execution now runs on Judge0, replacing the previous JDoodle integration for more reliable and faster results.
2️⃣ **VR Session Recording Report**\
**Description:** A dedicated recording report is now available for Video Room sessions.
***
#### 🐞 Bug Fixes
* Face auth image corrupted in playback, causing incorrect verification status.
* Face auth image broken after completing a live session.
* Candidates stuck on loading screen after face authentication.
* Interviewers intermittently unable to join live sessions.
* CodeJam sync broken for ACS sessions.
* Post-session feedback page stuck loading after leaving a session.
* Incorrect authentication URL redirect when joining a live session.
* Secondary camera feed not visible in portrait mode.
***
## Assessment Engine & Candidate Experience Updates
This month, we focused on **improving the accuracy and reliability of candidate-facing communications**.
#### ⚙️ Enhancements
1️⃣ **Cleaner Assessment Emails** \
**Description:** The "Estimated Duration" field no longer appears in assessment invite and reminder emails when no duration value is configured, ensuring candidates receive accurate communications.
***
# June 2026 Release Updates
Source: https://docs.talview.com/releasenotes/q2-2026/june-2026-release-updates
The June 2026 release delivers enhancements across **Workflow Tools, Proctoring, Interview Rooms, and Assessment Engine & Candidate Experience**, introducing improved user onboarding, expanded session review capabilities, new CodeJam language support, and platform-wide assessment controls.
***
### Workflow Tools Enhancements
This month, we introduced enhancements focused on **improved user onboarding and platform reliability**.
#### 🆕 Feature
1️⃣ **User Onboarding: Welcome Email**
**Description:** New users invited to Talview now receive a structured welcome email containing login instructions and getting-started resources.
**What's New**
* Templated welcome email triggered on user invite.
* Links to relevant getting-started resources included in the email.
***
#### 🐞 Bug Fixes
1️⃣ **Workflow Tools: Platform Stability**
* Candidate side panel issues including white-page errors and exam name not persisting.
* Ivy Call session status not updating on session end, and Ivy video and report generation failures.
* Delays in voucher generation and intermittent assessment invite email failures.
* Duplicate automation triggers causing repeat notifications.
2️⃣ **Scheduler: Payment, Booking & Notification**
* Resume parsing reliability issues including slow parsing and stuck-in-pending states.
* OTP delivery delays, self-scheduling confirmation emails, and no-show reschedule flow issues.
* Candidate experience UX bugs including blank page on enrollment retry and duplicate India entry in the country picker.
* Slot management fixes including cancel slot and assessment invite send failures.
***
### Proctoring Updates
This month, we introduced enhancements focused on **expanded session review capabilities, proctor visibility, and coordinator access**.
#### Center/Proctor Management (V8)
#### 🆕 Features
1️⃣ **Submissions & Evidence in Summary Report**
**Description:** The session summary report now includes candidate submissions and incident video evidence.
**What's New**
* Face Capture and ID Verification results with pass/fail statuses now visible in the report.
* Each incident displays video clips captured at the time, viewable inline or in a full-screen modal.
2️⃣ **New Panes in the Video Player**
**Description:** The video player now includes five new panes for quick access to session context without leaving the playback view.
**What's New**
* Covers candidate details, onboarding checks, incidents, exam rules, and candidate chat history.
3️⃣ **Review Actions in the Video Player**
**Description:** Reviewers can now take structured actions on incidents directly within the video player.
**What's New**
* Acknowledge, dismiss, modify severity, and recalculate the risk index outcome directly from the player.
4️⃣ **Activity Playback in the Video Player**
**Description:** A new Activity Playback tab lets reviewers replay the candidate's screen activity.
**What's New**
* Playback controls and a skip inactive toggle to move through recordings efficiently.
5️⃣ **List View of Live and Upcoming Sessions for a Proctor**
**Description:** Proctors now see a sessions screen on login showing all live and upcoming slots assigned to them.
**What's New**
* Slot cards show schedule details, proctoring type, and candidate accommodations.
* Online sessions show a Join Now button; in-center sessions show a Start Session button.
6️⃣ **Add Event to an Incident in the Video Player**
**Description:** Reviewers can now manually add events to an existing incident from the Incidents pane.
**What's New**
* Select an event type and confirm the timestamp.
* Manually added events shown with a blue dot and factored into risk index recalculation.
7️⃣ **Report a New Incident in the Video Player**
**Description:** Reviewers can now manually report a new incident not detected by the system, directly from the video player.
**What's New**
* Fill in timestamp, event type, severity, and description.
* New incident factored into the risk index outcome recalculation.
***
#### ⚙️ Enhancement
1️⃣ **360 Environment Scan in Session Summary Report**
**Description:** The session summary report now includes the candidate's 360 environment scan submission, viewable via an image carousel.
**What's New**
* Previous submissions accessible via a View previous submissions toggle if the candidate rejoined.
***
#### 🐞 Bug Fixes
* "Feed unavailable" message incorrectly appearing across different stream states. Each scenario now shows an accurate message with a timestamp or retry option where relevant.
***
#### Coordinator Console (V8)
#### 🆕 Features
1️⃣ **Enrollments List**
**Description:** Coordinators can now view candidates invited to enroll for an exam, with access to registration details through the timeline view.
2️⃣ **Exam Results**
**Description:** Coordinators can view all candidates who have completed exams, including risk index, exam score, session summary report, playback, and ID verification result.
3️⃣ **Candidate Profile: Timeline**
**Description:** Clicking on any candidate displays a detailed profile covering session summary, registration details, exam scores, ID verification, and guardian consent information.
**What's New**
* Access session summary report, playback, registration details, exam scores, ID verification, and guardian consent.
***
### Interview Rooms Enhancements
This month, we introduced enhancements focused on **expanded language support, code execution improvements, and session stability**.
#### 🆕 Features
1️⃣ **CodeJam: Perl Language Support**
**Description:** Perl is now available as a supported programming language in CodeJam, allowing candidates to write, run, and test Perl code directly within live interview sessions.
**What's New**
* Perl is supported on both Judge0 and JDoodle execution engines, with JDoodle as the fallback.
2️⃣ **CodeJam: Language Version Display Updated**
**Description:** Programming language version numbers shown in CodeJam now reflect the actual compiler versions deployed on Judge0.
**What's New**
* Candidates and interviewers see accurate, up-to-date version labels for Python, JavaScript, Java, C++, and others.
***
#### ⚙️ Enhancements
1️⃣ **Judge0 as Default Execution Engine**\
Judge0 is now the default code execution engine in CodeJam, with JDoodle as the fallback.
2️⃣ **Playback: Blank Screen at Recording Start Fixed**\
The player now starts rendering immediately when opening session playback, instead of showing a blank screen.
3️⃣ **Login: Temporary Redirect Flash Fixed**\
Users are no longer briefly redirected back to the login page after entering their password.
4️⃣ **360 Room Scan: Promotional UI Removed**\
The "New" badge and feature guide popup for 360 Room Scan have been removed now that the feature is stable.
***
#### 🐞 Bug Fixes
* Session join issues including mobile app authentication errors, camera access errors, and incorrect invite redirect flows.
* Null meeting URL issue for invite flows preventing users from joining sessions.
* Incomplete transcript issue for a staging session.
***
### Assessment Engine & Candidate Experience Updates
This month, we focused on **improved assessment authoring capabilities and platform-wide default changes**.
#### 🆕 Features
1️⃣ **Skill Creation and Management**
**Description:** Skills can now be created, organised, and tagged directly in the Assessment Engine via a dedicated side panel, with search, pagination, edit, and delete support.
**What's New**
* Add skills with a name and optional description, with instant validation to prevent duplicates.
* View all skills in a paginated table showing skill name, description, and creator.
* Edit or delete skills as needed. Skills linked to questions are protected from accidental deletion.
* Search skills by name, with 10 skills displayed per page.
2️⃣ **Section-Level Timer in Assessment Setup**
**Description:** The timer field in assessment setup now clearly accepts a total section duration, matching how time limits actually work when candidates take the assessment.
**What's New**
* The field is now labelled "Section time (mins)" and accepts the total time for the entire section.
* The total time shown on the assessment overview page updates automatically based on the new model.
***
#### 🐞 Bug Fixes
* Long-form editor slash menu closing automatically, preventing candidates from inserting content blocks.
* Code snippet option cards rendered in a narrow container, cutting off answer content with no scroll indicator.
* Ivy Avatar Builder illustration showing a loader indefinitely instead of the correct image.
***
# May 2026 Release Updates
Source: https://docs.talview.com/releasenotes/q2-2026/may-2026-release-updates
The May 2026 release delivers enhancements across **Workflow Tools, Interview Rooms, and Proctoring**, introducing automated evaluator reminders, data-driven candidate shortlisting, improved code execution reliability, and LMS integration improvements.
***
## Workflow Tools Enhancements
This month, we introduced enhancements focused on **automated evaluator reminders and data-driven candidate shortlisting**.
#### 🆕 Feature
1️⃣ **Workflow Automation: Auto-Remind Evaluators**
**Description:** A new automation rule sends scheduled email reminders to evaluators who have not completed their evaluation after a candidate is assigned.
**What's New**
* Automated evaluator reminder emails sent at 24h, 48h, and 72h after candidate assignment if evaluation remains incomplete.
* Applies across all steps: Screening, Assessment, and Interview, within a workflow.
2️⃣ **Assessment: Section-Level Score Columns and Filters**
**Description:** Recruiters and Master Recruiters can now view and filter candidates by individual section scores within the Assessment step, enabling faster, data-driven shortlisting for multi-section assessments.
**What's New**
* Dynamic section columns appear in the Assessment step candidate list, one column per section, visible only when the assessment contains multiple sections.
* Supports both numeric scores and categorical scores.
* Section-level filters: range/between and greater/less than for numeric scores; multi-select for categorical scores.
***
#### 🐞 Bug Fixes
1️⃣ **Workflow Tools: Platform Stability**
* Evaluator reminder emails not triggering; candidate invitation emails failing to send.
* New notifications not appearing without a page refresh.
* Unified assessment steps incorrectly marked as "Completed"; Ivy AI scores displaying as 0.
* Proview index not visible in tabular view; candidate list not loading for Evaluators.
* Time slab display breaking for slots ending at 12:00 AM.
2️⃣ **Scheduler: Payment, Booking & Notification**
* Sessions scheduled despite failed payments; incorrect redirect from payment gateway.
* Slots not appearing on page refresh; slots incorrectly marked as holidays.
* Reminder emails incorrectly triggering; OTP verification error during offline drive check-in.
* Improved drive slot API load time.
***
## Proctoring Updates
This month, we introduced enhancements focused on **improved LMS integration reliability**.
### Integrations: Moodle Native Plugin (V7+)
**You can download the latest version of moodle plugin [here](https://github.com/talview/moodle-quizaccess_v7_proview/releases).**
#### ⚙️ Enhancements
1️⃣ **Sentry Initialization for proctored sessions only**
**Description:** Previously, Sentry was initialized for non proctored quizzes as well. Now it is deferred until the check confirming that Proview is explicitly configured and enabled for the quiz in question. For any quiz where Proview proctoring is not active, Sentry will not initialise. Sentry's role in the plugin is only for error monitoring of proctoring session failures; it is scoped to proctoring-active quiz only.
2️⃣ **Enable Password Injection Setting**
**Description:** A new **Enable Password Injection** checkbox is now available in the Proview Proctoring Settings section of the quiz settings page. With this setting enabled, the plugin now handles password injection automatically, removing the need for any manual password sharing outside of Moodle.
***
#### 🐞 Bug Fixes
* **API data exposed in browser console** API responses were being injected into the browser console during production quiz sessions, potentially exposing session, quiz identifiers to any authenticated user via browser dev tools. This has been resolved - API response payloads are no longer sent to the browser console.
* **Quiz password bypass via direct URL access** Students could bypass a quiz password by navigating directly to `frame.php`, which was unconditionally marking the password as satisfied without validating it. Password validation is now properly enforced through Moodle's standard access flow before the Proview session can be initiated.
* **Unenrolled users could access Proview flow** Any authenticated Moodle user could access `frame.php` for any proctored quiz, regardless of course enrolment. The page now enforces course enrolment and quiz access capability checks before initiating the Proview session - unenrolled or unauthorised users are blocked before the proctoring flow begins.
* **Proview Recordings list capped at 100 sessions** The Proview Recordings page was limiting the display to a maximum of 100 sessions with no option to paginate further. Reviewers were unable to access or view recordings beyond the first 100 sessions. This has now been resolved - pagination is supported, allowing reviewers to navigate through all sessions regardless of count.
***
## Interview Rooms Enhancements
This month, we introduced enhancements focused on **improved code execution reliability, session playback, and session stability**.
#### ⚙️ Enhancements
1️⃣ **Code Runner: JDoodle Fallback**
**Description:** CodeJam code execution now falls back to JDoodle if the primary Judge0 engine is unreachable, ensuring uninterrupted code execution for candidates.
2️⃣ **Code Runner: Compiler Version Upgrade**
**Description:** The Judge0 code execution environment has been updated to the latest compiler and interpreter versions across all supported languages including GCC, Python, Node.js, and Java.
3️⃣ **In-Progress Session Playback**
**Description:** Recruiters and coordinators can now view a session recording while it is still in progress, not just after it has ended.
4️⃣ **ACS Face Captures**
**Description:** In-meeting face capture images now appear correctly in the Verification tab for ACS-based sessions.
5️⃣ **ACS Session Timer**
**Description:** The in-meeting timer now displays correctly for both interviewer and candidate in ACS sessions.
6️⃣ **Screen Recording Quality**
**Description:** Screen recording resolution has been increased for V8 sessions, ensuring recordings at high-resolution displays render at the correct quality.
***
#### 🐞 Bug Fixes
* Resolved Insights issues including transcript unavailability and workflow failures during candidate performance save.
* Fixed cross-tenant data issues, partial video in Persistent sessions, and session join errors.
* Resolved screen recording quality, CodeJam UI, and app loading issues.
* Fixed camera preview rendering incorrectly on iOS devices in the pre-join lobby.
***
# August 2024 Release Updates
Source: https://docs.talview.com/releasenotes/q3-2024/release-notes-aug-2024
Stay updated with the latest features and enhancements rolled out in August 2024 across Talview’s Orchestration Platform (TOP) – including Workflow Tools, Candidate Experience, Interview Rooms, and Proview (Proctoring)
## Workflow Tools Updates
**Add JD during Workflow creation**
The new plain text editor in Workflow Tools allows recruiters to easily add and share job descriptions during workflow creation, ensuring clear communication of roles and access to job details throughout the hiring process.
**Intelligent Scheduling enhancements**
1. **MS Teams Integration with Intelligent Scheduler:** Enables recruiters to schedule IS interviews using MS Teams, allowing candidates and interviewers to join directly through the platform.
2. **Offline Interview with IS via Recruit:** Allows recruiters to schedule and conduct offline interviews seamlessly using Intelligent Scheduler.
3. **Interview join reminder for candidates and interviewers:** A 10-minute interview reminder to the candidates and interviewers in Intelligent Scheduling email notifications improves punctuality and reduces no-shows by alerting the participants shortly before their scheduled interviews.
4. **New unauthorized page:** An unauthorized access page in the login flow helps evaluators manage multiple accounts by displaying the current account and offering a log-out option, reducing confusion and ensuring correct account usage for interviews and related activities.
**MCA Attempt in Test taker experience**
This feature enables candidates to answer multiple correct answer (MCA) questions without skipping, enhancing assessment accuracy and engagement by requiring comprehensive evaluations, with success measured by higher completion and engagement rates.
## Interview rooms Updates
**Invite registered users on the fly (WFT)**
* **Description**: Instantly invite registered users to join live video interviews with a single click, ensuring seamless interview experience.
* **Benefits**:
* **Flexibility**: Accommodate additions to the interview panel during the meeting.
* **Increased Efficiency**: Streamline interview operations by enabling real-time participation of registered users.
**Switch Tab with windows focus out notification**
* **Description**: Enable real-time alerts to notify interviewers if candidates switch tabs or windows, and remain away from the interview screen for more than 30 seconds during the session.
* **Benefits**:
* **Integrity**: Maintains fairness by discouraging external assistance.
* **Data-Driven Insights**: Provides actionable data for post-interview analysis regarding candidate behavior.
**Capture no face and multiple face in verification tab during the meeting**
* **Description**: Capture no face or multiple faces in the verification tab to ensure accurate identity validation during the live video interview.
* **Benefits**: Enhances security and accuracy by ensuring only the correct individual is verified during live video interviews.
**Feature Enhancements**
* **Enhanced feedback collection page for interviewers and candidates**
* **Description**: Collect feedback from participants directly on the platform to gauge satisfaction and improve future experiences.
* **Benefits**: Provides valuable insights for continuous improvement, enhances participant engagement, and helps tailor the platform to user needs.
* Livekit self-hosted service provider is released.
**Bug Fixes**
We have focused on closing the high-priority bugs listed below:
* Participant video stretch.
* Fallback video provider order update to Livekit → Livekit self-hosted → Twilio.
* Removed the notifications for candidate “face not detected” and “multi-face detected”.
## Proview (Proctoring) Updates
### Attendee Ex
### Feature
1. **New Flag: Partial Face Detected**
* **Flag Name:** Partial Face Detected
* **Flag ID:** 226
* **Flag Type:** Debug Alert
A new flag, Partial Face Detected, has been added to all proctoring sessions. This flag will be triggered when a test taker’s face is only partially visible on the screen. Common scenarios include the test taker looking down to use a calculator or placing a hand on their face.
**Note:** When the face is not fully present in the camera view and only half or lesser face is visible, it is still considered as Face not detected.
### Enhancements
1. **Alvy Prompt update: Released**\
Alvy prompt is now updated to improve the accuracy and avoid false flags when the test taker is present in the screen.
2. **French language updates (Not released – To be updated next week)**\
French strings are updated in V7+ to improve accuracy.
3. **Face Not Detected flag update**\
The Face Not Detected flag has been updated to trigger if the candidate’s face is completely or predominantly not visible on the screen for more than 7.5 seconds, avoiding unnecessary flagging during the session in a small timeframe.
4. **Multiple Face Detected flag update**\
The Multiple Face Detected flag has been updated to trigger if more than one person is present in the test premises and visible on the screen for more than 5 seconds, avoiding unnecessary flagging in small timeframes.
5. **Update in name of Object detection flags**\
The names of the object detection flags have been revised to clarify that the detected objects may resemble a book or mobile device but are not necessarily those items.
* Book like object detected
* Mobile like object detected
6. **Refresh confirmation removed in Secure Browser**\
In the latest update, the confirmation prompt when refreshing the Secure Browser has been removed. The session page will now reload automatically when the refresh button is clicked.
7. **Secure Browser version auto update**\
When a new version of Secure Browser is available, and if the user is using an older version, a pop-up confirmation is shown to the candidate asking them to update. This applies to all previous versions of secure browsers including Talview Secure Browser.
**Note:** If there are clients still using Talview Secure Browser actively and haven’t migrated, it might cause issues in using the latest Secure Browser.
8. **Deprecation update: Done**\
Whitelist software option in Secure Browser configurations in LMSs is now removed since the feature is not available. Only blacklisting software is allowed.
### What’s coming next
* V7+: Proview stakes update
* V8: Proview attendee experience revamp WIP
***
### Proctor NG
### Enhancements
1. **Limiting proctor to candidate ratio to 1:9**\
Previously, while setting up an event the default value mentioned was 1:40. This has been updated to 1:9. One cannot schedule an event with a proctor to candidate ratio more than 1:9.
2. **Test-admin permissions enhanced to approve/reject pre-checks**\
Test-admins now have the permission to approve or reject pre-checks during a live session. Previously this was limited only to proctors.
### Bug Fixes
1. **Invalid Access Token error in Live Proctor app**
* **Issue:** When logging into the proctor app, users were confused by a toast message displaying an 'Invalid Access Token' error.
* **Solution:** A fix has been implemented to prevent the incorrect display of this error message.
### What’s coming next
* Ability for test-admin to override the system-generated Proview Index
***
### Integrations
### Feature
1. **Secure Browser now supports Proview proctoring for Canvas quizzes**\
Instructors can now configure Secure Browser for their Canvas quizzes. This ensures a secured testing environment, restricting access to other applications and websites.
2. **Secure Browser only Moodle plugin**\
Instructors can now configure their Moodle quizzes to launch in a Secure Browser environment without the need to enable proctoring. This allows test takers to complete their quizzes securely in a non-remote proctored setting.
### Enhancements
1. **Increased limit for live proctoring bulk bookings**\
For live proctoring bookings, the limit per bulk booking request has been increased from 100 to 500, making it easier to handle large batches.
2. **Proview tokens displayed as names instead of alphanumeric strings**\
Proview tokens are now displayed as descriptive names across all views: list view, detail view, link creator, and filter.
3. **Updated playback view to load data only for selected candidate**\
In Canvas and D2L LMS, you can now view a student's proctored session attempts by clicking the playback details button next to their name.
### Bug Fixes
1. **Reference link button not displayed**
* **Issue:** The reference link button was not appearing during the assessment when a wrapper link with reference links was generated.
* **Solution:** The reference link button is now displayed, allowing the test taker to access whitelisted reference links.
2. **Incorrect title displayed during token generation in LMS dashboard**
* **Issue:** When generating a token, the Proctoring dashboard title was incorrectly displayed instead of the LMS dashboard title.
* **Solution:** The issue has been resolved to ensure the correct LMS dashboard title is consistently visible.
3. **Missing prompt for Proview browser extension installation**
* **Issue:** Students were not prompted to install the Proview browser extension before starting exams.
* **Solution:** An error message has been added to ensure students are prompted to install the extension before continuing.
4. **Copy quiz description text in Canvas LMS**
* **Issue:** Instructors could forget to paste required text into the quiz instructions box, leaving students uninformed about the extension download.
* **Solution:** The UI now enforces that instructions are pasted before the Save button is enabled.
5. **Updated support communication for test takers using browser plugin**
* **Issue:** With the removal of Freshchat, students had no direct way to contact support.
* **Solution:** A message has been added to guide students on how to contact technical support.
6. **Candidate's ID overlapping close icon in session playback view in LMS application**
* **Issue:** The candidate’s ID overlapped the close icon, preventing users from closing the playback view.
* **Solution:** The plugin has been updated so that IDs no longer overlap with the close button.
***
# July 2024 Release Updates
Source: https://docs.talview.com/releasenotes/q3-2024/release-notes-july-2024
Stay updated with the latest features and enhancements rolled out in July 2024 across Talview’s Orchestration Platform (TOP) – including Workflow Tools, Candidate Experience, Interview Rooms, and Proview (Proctoring)
## Workflow Tools Updates
**Candidate calling feature**
Recruiters can now make and record screening calls directly from the candidate profile in Workflow Tools, with automatic recording, status tracking, and playback options. This update streamlines candidate screening and enhances efficiency.
**Assessment invitation from Workflow Tools**
Recruiters can invite candidates to the assessment step directly from Workflow Tools, and an invitation email will be sent to the candidate. This feature is integrated with the new test-taker experience. Please note that candidates will be able to attend the assessment starting with the August release.
**Candidate experience**
We’ve made a bunch of updates to the candidate (attendee) experience in this release, some of the key items are as below:
1. Disable copy-paste: To enhance assessment security and integrity, we have introduced a feature that prevents candidates from copying and pasting content during assessments. This reduces plagiarism, ensures original responses, and can be customized by organizations as needed.
2. Watermark for content protection: Watermark protection is now enabled in this release for the new test-taker experience. Enabling the watermark enhances content protection by making it easier to trace unauthorized sharing of assessment content. It also promotes accountability by embedding unique candidate IDs.
3. Bypass verification code for consent workflows: Candidates can bypass the verification code page in the [attend.talview.com](http://attend.talview.com) platform and go directly to the interview instructions page when the candidate consent workflow is enabled, streamlining the authentication and consent process. This update simplifies the process and improves the candidate experience by reducing the number of steps.
## Interview rooms Updates
**Guide - Interview Builder**
* **Description**: Streamline your live interviews with an Interview Builder, enabling customizable and structured question sets based on job description for a seamless and efficient interview process.
* **Benefits**: Consistency and Fairness, Efficiency, Customization, Improved Candidate Experience, Enhanced Decision-Making.
**Face Verification Status view**
* **Description**: Overall Verification Status in live interviews provides real-time authentication and validation of candidates as passed or failed.
* **Benefits**: Ensures real-time verification, reduces the risk of fraud and misrepresentation, speeds up the verification process for quicker onboarding.
**Interviewer Alert: Candidate Verification Notification**
* **Description**: Interviewers can confirm that candidates have completed pre-interview verifications and receive updates upon their session start.
* **Benefits**: Confirms consistency, reduces fraud, maintains integrity.
**Notify participants on switching to Codejam & Whiteboarding**
* **Description**: Notifications when switching to codejam and whiteboarding session with bubble highlighting for enhanced clarity and focus.
* **Benefits**: Improved focus and enhanced clarity for collaboration.
**Recording Hard stop/ auto disconnect post 30 minutes of scheduled time**
* **Description**: A recording hard stop/auto-disconnect feature automatically ends live interviews after 30 minutes if only one participant remains and forgets to leave the call after the discussion.
* **Benefits**: Prevents unnecessary recording and storage of idle time, saves server and storage resources by ending inactive sessions, helps maintain privacy by disconnecting unattended calls.
**Feature Enhancements**
* Notification of new private chat
* Added whiteboard side toolbar
**Bug Fixes**
We have focused on closing the high-priority bugs listed below:
* Bugs on Interview Builder
* Fix on virtual camera notifications
* Fix on effects branding image
* Request video feature for WFT
## Proview (Proctoring) Updates
### Attendee Ex
### Enhancements
**Alvy (advanced AI) alerts can now be configured to impact the Proview Index**\
Previously, Alvy alerts were classified as a debug flag. They have now been reclassified as a 'Warning' flag, allowing the assignment of a 'Severity' level to these alerts, which will affect the Proview index. By default, the 'Severity' of these flags is set to 'none'.
**Note:** Alvy alerts will now be visible under the public filter in the playback view.
**Updated Japanese translations in v7+**\
Japanese language translations are updated for better language accuracy in Proview Attendee V7+.
### Bug Fixes
**When screen share was stopped for the second time prechecks were initiated from the start**
* **Issue:** As a user taking an exam if I stopped the screen share once I could resume the session by sharing screen again. If I stopped it for a second time, I was asked to start the pre-checks from the start.
* **Solution:** Irrespective of how many times the screen share is stopped, when the screen share is started again, I will be able to resume the exam without having to do the pre-checks again.
**Battery draining and secondary device heating issue**
* **Issue:** In a proctored session using Livekit video service, the user's battery was draining very quickly and heating up the device.
* **Solution:** We have defined a set of video presets with varying resolutions, bitrates, and frame rates for use in secondary video streaming. These presets allow the application to adapt the video quality to different network conditions and device capabilities by switching between different video presets. Previously there was no upper limit set which meant the videos were streaming in HD or higher quality based on the network of the student thereby draining the battery.
**Empty space removed from the bottom while scrolling**\
In a proctored session, the attendee was able to view background applications below, leading to UI issues. With the current fix, this issue is resolved, which was observed in older Moodle version.
**Progress bar removed from toaster**\
The flags warning toaster message was showing some number percentage, breaking the UI. This issue is now fixed, which was observed in older Moodle version.
**French Subtitles for Environment test demo video**\
When the user switches the platform language to French and wants to view the demo video, the demo video is now available with subtitles for the user to follow the steps.
**Links and content opening in new tab in Secure Browser**\
Secure browser is now enhanced to support links opening in a new tab or same tab from within the assessment. While this feature existed before, there are enhancements done to support this in multiple assessment engines where it wasn’t supported earlier due to technical limitations.
### What’s coming next
* Exploring options to support Proview Plugin in Secure Browser.
* Proview attendee v8 functionalities.
* Proview Index and Violation flagging logic update in V7+.
***
### Proctor NG
### Enhancements
1. **Session Rating filter in R\&R account**\
Users can now locate specific sessions based on the index by filtering the sessions list using the session rating filter.
2. **Upper limit for primary video streaming**\
To optimize the rendering of multiple video streams and reduce the load on the proctor's device during live monitoring sessions, we have established an upper limit (960x540) on the quality of the live video stream. This limit applies regardless of the test-taker's device capability to send HD or higher-quality video streams.
### Bug Fixes
1. **Video getting stuck in the playback**
* **Issue:** When user navigates the playback recording by using the next alert button the video would get stuck, but the timeline would be playing.
* **Solution:** We have made the necessary fix to ensure the video plays seamlessly when user navigates using the next alert button.
2. **External attendee ID was not available in the playback**
* **Issue:** Candidate’s external attendee ID was missing in the header of the playback and the embedded playback screens.
* **Solution:** The attendee ID will now appear in the header for all sessions.
3. **Alvy alerts (advanced AI) displaying the description in the toast messages**
* **Issue:** The long descriptions of Alvy alerts were being displayed rather than the alert name in the main feed.
* **Solution:** We have made the necessary changes to display the alert name and not the description in the video feed.
4. **Alvy (advanced AI) alerts not in sync in the video timeline**
* **Issue:** Alerts generated by Alvy were not in sync in the video timeline. There used to be a 15–30 second delay.
* **Solution:** We have made the necessary fix to sync the events triggered by Alvy to the video timeline.
5. **Sorting issue in R\&R accounts**
* **Issue:** Sessions in R\&R accounts were sorted randomly, making it difficult to locate sessions.
* **Solution:** The sorting has been fixed to display sessions in a descending order based on the ‘Status Updated’ value. The latest session will be at the top.
***
## Proview Console \[V8]
### Feature
1. **Shareable searches and applied filters**\
Coordinators can share specific search or filter operations they have performed in the flow list table by sharing the URL. Users with the appropriate roles can access the same view as was shared.
2. **User profile section**\
Users can view and manage various user details from account settings. They can view their role, organisation, application version, and last login time. They can update their profile photo, language preference, and phone number.
### What’s coming next
1. Browser configurations for the onboarding
2. Configuring apps to be blacklisted in the secure browser
3. Flow version log
4. Time zone preference settings in the user profile
***
### Integrations
### Feature
1. **Wrapper Links List**\
Provides a detailed and organized interface for viewing and managing Proview Web Wrapper links, with features like a tabular list view, search and filter options, detailed link information, and a link generation form with specific attributes and proctoring and secure browser configurations.
2. **Canvas Browser Plugin for Classic and New quizzes**\
Integrates Proview proctoring into Canvas LMS via a browser plugin, allowing for varied proctoring options within New and Classic quizzes. Features include proctoring configuration through course settings, preflight system checks, secure password injection, and session playback access directly from Canvas.
### Enhancements
1. **API for Attendee Amendments**\
Provides the capability to update attendee details such as email address, first name, and last name via an external identifier.
2. **API for Booking Schedule**\
Enables the creation of new bookings for candidates individually or in bulk by specifying session and attendee details.
3. **API for Booking Cancel**\
Allows clients to cancel existing bookings or specific attendees within a booking using various identification parameters.
4. **API for Getting Availability**\
Checks current booking status within a specified period to determine the number of slots already booked and those still available.
5. **Scheduling from LMS dashboard has been enabled for Inspera**\
Synchronizes tests created on Inspera with the LMS dashboard, allowing scheduling of live proctored sessions from within the LMS interface.
6. **Org configuration setting to enable self onboarding in LMS Dashboard**\
Admins can now provide integration details (Client ID, Redirect URI, Scope, and Client Secret) through a form in the LMS dashboard, enabling authentication without sharing admin credentials. After form submission, users are redirected to the LMS login page. Upon successful authentication, fields including LMS URL, Proview admin username, Proview admin password, refresh token, and app ID are automatically populated, and the refresh token is securely stored in our database.
***
# September 2024 Release Updates
Source: https://docs.talview.com/releasenotes/q3-2024/release-notes-sept-2024
Stay updated with the latest features and enhancements rolled out in September 2024 across Talview’s Orchestration Platform (TOP) – including Workflow Tools, Candidate Experience, Interview Rooms, and Proview (Proctoring)
## Workflow Tools Updates
**Basic Pre-interview dashboard**
Interviewers often lack easy access to key candidate and job details, leading to inefficiencies. The new Pre-Interview Dashboard addresses this by providing interview, candidate and workflow fields, and job descriptions directly within Intelligent Scheduling emails, improving interview preparation and decision-making efficiency.
**Evaluator enhancements in WFT**
Recruiters can now assign evaluators to candidates directly through the platform, with evaluators receiving email notifications and viewing assigned candidates in list and detail views. This streamlines the evaluation process and improves engagement and efficiency.
**Pay and Book Workflow**
Candidates need a simplified and integrated process to pay for their exams and book exam slots, reducing manual coordination and delays in exam scheduling. The new Pay and Book Workflow allows candidates to seamlessly pay for their exams and book available exam slots in one unified experience.
**Async interviews with the Test taker experience**
Candidates face difficulties completing async interviews due to a lack of onboarding and technical setup, leading to delays and incomplete interviews. The new Async Interview workflow addresses this by providing guided onboarding with step-by-step browser permissions, hardware checks, the ability to hide video previews, configurable preparation time, and reattempt options. This improves completion rates, enhances the candidate experience, and reduces technical support queries.
## Interview rooms Updates
### **What is in the release?**
**Add question for Codejam**
* **Description**: You can now effortlessly add questions to CodeJam sessions directly within Interview Rooms, ensuring a more integrated technical assessment experience.
* **Benefits**:
* Streamlined question management during interviews.
* Greater flexibility for interviewers to assess coding skills in real-time.
**Select from multiple images for background**
* **Description**: Ability to select from multiple background images, allowing interviewers to customize their interview space visually.
* **Benefits**:
* Enhances professionalism with tailored backgrounds.
* Gives a personal touch to the interview environment
**Drop alert after 10 minutes of No-Show**
* **Description**: Get notified to exit the interview if the other participant hasn’t joined within 10 minutes, saving time and avoiding unnecessary waiting.
* **Benefits**:
* Reduces frustration by setting clear boundaries.
* Encourages punctuality and accountability.
* Enhances user experience with proactive notifications.
**Low bandwidth self notification**
* **Description**: Both interviewers and candidates will now receive notifications if their bandwidth is running low, helping them troubleshoot connectivity issues proactively.
* **Benefits**:
* Enhances interview quality by preventing disruptions due to poor connection.
* Provides real-time feedback for better session performance.
**Service Provider Fallback Notification**
* **Description**: When the system automatically switches to a backup service provider, the other participant will now receive a notification.
* **Benefits**:
* Ensures smoother transitions when connectivity issues arise.
* Keeps both interviewers and candidates informed about potential delays or changes.
**Bug Fixes**\
We have focused on closing the high-priority bugs listed below:
* Clicking on enter after typing in Ask AI sends the response.
* Candidate unable to join the session in iOS mobile application and in mobile browser.
* Scroll bars were visible in the chat box for IR with IS.
## Proview (Proctoring) Updates
## Proctor NG
### Enhancements
1. **Test admin can update Proview Index**\
Test admins now have the ability to manually override the Proview Index. In the past, only the Proctor role had this permission.
2. **Proctor Buffer Time description**\
Users creating an event lacked clear guidance on the meaning of the proctor buffer time and were unaware of the default start buffer time. To eliminate any confusion, a brief explanation about the default start buffer time has been added.
### Bug Fixes
1. **Wrapper Form – UI issue**
* **Issue:** Long redirect URL would not get truncated.
* **Solution:** The necessary fix has been implemented to truncate long redirect URLs.
2. **Proctor app – UI issue**
* **Issue:** Misalignment in the candidate table.
* **Solution:** The UI has been fixed to correctly align the columns and the data in the table.
3. **Face verification dependent on ID verification setting**
* **Issue:** Disabling the `id_verification_check` setting would prevent face capture from appearing in the approvals section during playback.
* **Solution:** ID and face verification can now be enabled or disabled independently.
***
## Integrations
### Enhancements
1. **Changes for proctoring configurations and playback view in browser plugin integration (Canvas & D2L LMS)**\
Proctoring and secure browser configurations are now housed within the Proview proctoring icon. Proctoring configurations and playback view are organized into separate tabs within a single side panel.
***
## Admin Updates
We are excited to announce the launch of our new Form Builder within the admin application. This tool is designed to streamline the creation and management of forms, enabling the admin to build registration, evaluation and consent forms tailored to their organization’s needs
### **Key Features:**
**Form Builder Interface**
* **Block-Based Editor:** Utilize a powerful drag-and-drop interface to add and arrange blocks that represent different input types.
* **Input Field Types:** Include diverse fields in your forms:
* Short Text
* Long Text
* Multiple Choice
* Checkboxes
* Dropdown
* File Upload
* Number
* Email
* Date
* **Layout Customization:** Organize blocks into 1, 2, or 3 grid layouts, allowing for aesthetic arrangement of form elements.
* **Conditional Logic Block:** Enhance form interactivity by showing or hiding certain blocks based on respondents' answers to choice-based input fields. This allows for dynamic forms that adapt to user input, improving respondent experience and data relevance.
* **Form Preview:** Simulate and test each form created in the builder to see how the form instance will appear to respondents.
**Form Library**
* **Manage Forms:** Access and manage a centralized library of all created forms, enabling easy reuse and modification.
**Responsive Rendering**
* **Dual View Compatibility:** Forms designed with the Form Builder can be rendered for both web and mobile views. The preview feature allows users to see how forms will appear on both platforms.
* Web view:
* Mobile view:
# August 2025 Release Updates
Source: https://docs.talview.com/releasenotes/q3-2025/release-notes-aug-2025
Stay updated with the latest features and enhancements rolled out in August 2025 across Talview’s Orchestration Platform (TOP) – including Workflow Tools, Candidate Experience, Interview Rooms, and Proview (Proctoring)
## 🔧 Workflow Tools & Candidate Experience Updates
### **Workflow Tools**
1. **Viewing the Proview video and index**
Recruiters and hiring managers (evaluators) can now view **Proview session ratings and playback** within Workflow Tools, enabling them to review candidate behavior during proctored assessments. This added visibility ensures fair evaluations, strengthens assessment integrity, and supports more informed hiring decisions.
Check it out below:
**Recruiter experience:**
**Evaluator experience**:
### **Candidate Experience**
1. **Pre-Assessment Candidate Authentication**
We’ve introduced **face capture and authentication** before candidates begin their assessments in the new test-taker experience, ensuring that face authentication is done before the candidate starts the assessment. This enhancement strengthens assessment integrity, prevents impersonation risks, and gives recruiters and evaluators greater confidence in the authenticity of results, all while keeping the candidate experience smooth and secure.
Check it out below:
2. **Payment Enhancements:**
\*\*Change meeting status to confirmed before payment is completed \*\*
1. To address the issue of payment completed but meeting status not confirmed, we will be saving the meeting status in the system even before the payment is completed
2. The appointment confirmation notification will only be sent to the candidate when the transaction is complete
**Auto-cancel when payment is not confirmed and the slot is in \<24 hours**
1. When the time to slot ≤ 24 hours, and the payment is not yet confirmed, the slot will be auto-cancelled by the system, and the candidate will be notified
2. If the payment is received after the cancellation, the amount will be refunded to the candidate
## 🎤 Interview Rooms Updates
### Feature Enhancement
**Request Recording Consent from Candidates**
**Description**: Enable interviewers to request and capture candidates’ consent before starting a recording, ensuring transparency and compliance.
**Benefits**:
* Builds trust by keeping candidates informed
* Ensures compliance with data privacy and legal standards
* Reduces the risk of disputes regarding recording usage
* Provides clear documentation of candidate consent
**Recording Consent Disabled by Organization Policy**
**Description**: When organizational policy restricts recordings, candidates & interviewers are notified that recording is disabled for their interview.
**Benefits**:
* Ensures adherence to company and regulatory policies
* Provides transparency to candidates upfront
* Prevents unauthorized or accidental recordings
* Reinforces candidate trust and organizational credibility
***
## Assessment Engine Updates
### 1. CodeSolo Programming Integration
The Assessment Engine now seamlessly integrates with CodeSolo programming assessments. This allows coding tests to leverage the full library of coding questions within the Assessment Engine’s CodeSolo section. Previously, engineers manually added questions to the backend, which was time-consuming. Now, content managers can directly upload questions and test cases, simplifying the workflow and reducing setup time.
**Benefits**:
* Empowers content managers with greater control and flexibility.
* Accelerates question creation and reduces dependency on engineering resources.
### 2. Real-Time Filter List Enhancements - Question Bank Management
The Question Bank Management system now features real-time filter updates. Previously, users had to manually clear filters to reflect changes in the question bank. This improvement ensures that filters (e.g., question status, category, or difficulty) update instantly, providing a smoother and more efficient user experience.
**Benefits**:
* Saves time by eliminating manual filter resets.
* Enhances usability with immediate visibility of changes.
***
## 👥 Proview (Proctoring) Updates
### **Attendee Experience**
**Arabic is now supported for test takers on v7+**
* Test takers can now select Arabic as their preferred language in a proctored session.
***
### **Integrations (V7+)**
1. **Moodle LMS 4.5 | Support for Secure Browser**
Configuring Secure Browser for a quiz in Moodle LMS 4.5 is now supported via the browser extension. Additionally, even screen minimizing and screen protection, sub-features of SB can now be enforced.
**Bug Fixes**
1. **Moodle LMS | Error thrown in the instructions editor**
**Issue:** The instructions editor would display the following error message in La Trobe’s moodle instance i.e version 4.2.
**Solution:** The `quizaccess_proctor` plugin, the plugin responsible for proctoring configurations in the instance has been updated by which this issue has been resolved. The new version (1.5.2) of the plugin can be installed from [here](https://github.com/talview/moodle-quizaccess_proctor/releases/tag/v1.5.2-Quiz_Access_Proctor).
2. **Moodle LMS | Enrollment sync issue**
**Issue:** An issue was faced by BGP team where the students’ data wasn’t being displayed in the LMS dashboard even after performing candidate enrollment sync.
**Solution:** This issue has been resolved. The "Student” role type configuration has been updated and the dashboard will display the ID, name and email of the enrolled students for that particular quiz.
# July 2025 Release Updates
Source: https://docs.talview.com/releasenotes/q3-2025/release-notes-july-2025
Stay updated with the latest features and enhancements rolled out in July 2025 across Talview’s Orchestration Platform (TOP) – including Workflow Tools, Candidate Experience, Interview Rooms, and Proview (Proctoring)
## 🔧 Workflow Tools & Candidate Experience Updates
### **Workflow Tools**
1. **Ivy AI Playback and Report:** Recruiters can now access a unified Ivy playback view with video and transcript for each completed assessment. Along with this, they can also view the assessment report in the side panel. This enables faster, more consistent, and in-depth candidate evaluations.
Check it out below:
2. **Candidate Verification Display:** Recruiters can now view candidate face authentication details for completed assessments and interviews directly from the side panel in Workflow Tools. This improves transparency, enhances identity verification, and supports more confident hiring decisions.
Check it out below:
### **Candidate Experience**
1. **Ivy AI Interviewer Enhancements:** Recruiters now get access to a structured Ivy Assessment Report with competency scores, overall score, visual cues, and full transcript. This enables faster, more consistent, and transparent evaluation of AI-led interviews.
2. **Payment Enhancements:**
**\[Bug Fix] Display Decimal Values in Fee Calculations**
Previously, fee amounts were displayed as whole numbers in price calculations. This issue has been resolved. All fee amounts are now consistently shown with up to two decimal places, providing more accurate pricing details.
**\[Enhancement] Updated Messaging for Payments with ‘Pending’ Status** We have improved the user experience when a payment attempt results in a status of “Pending.”
* Candidates redirected to the platform following a payment attempt will now see updated messaging reflecting the pending status.
* A clear and explicit payment processing notice is displayed on the payment summary page to keep candidates informed.
**\[Enhancement] Auto-Cancellation of Slots with Pending Payments 24 Hours Prior to Start Time**
To optimize scheduling:
* If a candidate’s payment remains unconfirmed 24 hours before their booked slot starts, the slot will be automatically canceled.
* The candidate will receive an email notification notifying them of the cancellation.
**\[Enhancement] Standalone Payment Links for Retry Payment Attempts**
To improve payment retry options for candidates:
* We have introduced the ability to generate standalone payment links for orders where previous payment attempts failed.
* Currently, these links are generated manually as a temporary solution.
* Going forward, payment links will be automatically generated and sent via email to candidates based on scheduling logic.
3. **Objective with skip workflows:** Candidates can now skip MCQ questions and return to them later in the new test taker experience with an enhanced question playlist, giving them greater control over time and stress during assessments. They can also mark a question for review. This improves completion rates and supports a more candidate-friendly experience.
Check it out below:
5. **Display the correct answer -** Candidates can now view the correct answers right after attempting each MCQ or MCA question, if enabled by the assessment creator. This real-time feedback supports learning during the assessment.
6. **Multiple questions in the Long-form assessment -** Candidates can now respond to multiple related questions within a single long-form section, creating a smoother and more cohesive assessment experience. This allows for deeper evaluation while reducing context switching and cognitive load.
## 🎤 Interview Rooms Updates
### Feature Enhancement
**Recording Consent Management**: Candidates in optional recording regions can now withdraw their recording consent during live interviews, giving them more control and transparency. Real-time updates and streamlined UI ensure minimal disruption while staying compliant with regional policies.
### Bug Fixes
We have focused on closing the high-priority bugs listed below
* Default **noise suppression and echo cancellation** improve call audio quality.
* Clear messaging and disabled join button when mic/camera are in use by other apps.
* Fixes include panel invite email issues, environment check errors, guest interviewer additions, and Codejam question visibility.
***
## 👥 Proview (Proctoring) Updates
### **Attendee Experience**
* Candidates now see descriptions for Alvy toaster alerts to better understand and resolve violations.
* Secure Browser application blacklist updated and verified, with improved error messaging when required apps cannot be closed.
* Bug fixes include resolution for blank page issues, secondary camera blank screen, and QR scan issues during launch.
***
### **Secure Browser**
* **New Feature (Mac Only)**: Candidates are warned if spell correction is enabled and asked to disable it before proceeding.
* Enhanced blacklist warning messages guide users to manually close blocked apps.
* Screen protection behavior updated on Mac - Proview will not access screens if protection is enabled.
* Drag-and-drop issue for Inspera assessments is now resolved.
***
### **Proview Console (V8)**
* Voucher code rules expanded—now support up to 25-character codes, including special characters, for better flexibility in test distribution.
***
### **Integrations (V7+)**
* **New**: Moodle LMS 4.5 is now fully supported with the Proview Chrome extension.
* Bug fixes for Moodle and Cornerstone (CSOD) ensure proctoring loads reliably with updated LMS features.
# September 2025 Release Updates
Source: https://docs.talview.com/releasenotes/q3-2025/release-notes-september-2025
## Workflow Tools Updates
This month, the team focused on **bug fixes and platform stabilization** to deliver a smoother experience across key workflows.
### 🔧 Fixes & Improvements
1. **Dynamic SMS Interview Reminders:** Introduced SMS reminders for candidates and interviewers - sent **24 hours or 1 hour before** based on the interview scheduled time, ensuring timely participation and reduced no-shows.
2. **Session Stability:** Resolved sudden logout issues to ensure uninterrupted usage. Now, users on the platform will not be logged out until they click the **Logout button.**
3. **Analytics Coverage:** Expanded Mixpanel tracking to cover core actions such as **invite, reply, and forward**.
4. **Candidate Experience:** Fixed display issues for **long-form candidate responses**.
5. **Intelligent Scheduling:** Addressed multiple issues impacting scheduling reliability:
* Email delivery inconsistencies
* Availability addition
* ICS file RSVP actions
6. **Notification Inbox:** Corrected **status update issues** (from other statuses to “Read”) to improve real-time visibility.
## Candidate Experience Updates
* **Phone Number Field with Country Code in Forms:** To improve data accuracy and global communication, a new phone number field with a country code selector has been added to data collection forms. This solves the issue of inconsistent or invalid contact information.
* **UX Improvement on Mobile Device for Slot Booking:** When a candidate is initiating a booking on mobile device, we have introduced an auto scroll on the screen on slot booking page. As and when the candidate selects a date, they will be auto scrolled and displayed the available slot timings for the corresponding date.
### Payment Enhancements
1. **Meeting Status set to “Scheduled” earlier in the booking flow**
* The meeting status will now be set to **Scheduled** in the database as soon as a candidate selects a slot and proceeds to payment.
* Previously, the status was updated only after payment was successfully completed, which sometimes caused issues when candidates dropped off after confirming payment but before final processing. *This change ensures that:*
* Slots are reserved immediately, preventing double-booking.
* Candidates who drop off during payment can resume their booking without losing their slot.
2. **New “Initiated” status for transactions**
* We have introduced a new transaction status: **Initiated**.
* Previously, transactions were directly marked as **Pending** once candidates proceeded to pay. *Now:*
* **Initiated** indicates that the candidate has started the payment process but has not yet attempted the transaction.
* From this state, the transaction can move to **Pending**, **Success**, or **Failed**, based on responses from the payment provider.
* For example, a transaction may remain in **Pending** if a candidate has attempted payment but it is still being processed by the provider.
### **Who are the primary users of this feature?**
> The features mentioned above will provide the greatest benefit to the **recruiters, evaluators** and the **candidates.**
### **What are we working on next?**
**Workflow Tools**
1. Stack ranking on Ivy assessment with score display in the list view
2. Drive management module rollout
3. CodeSolo integration
4. Registration workflow
5. Resume scoring
**Candidate Experience**
1. Post assessment and interview forms
2. Payment enhancements to send reminders and allow invoicing for companies.
## Interview Rooms Updates
* **Splash screen for introducing 360 Environment Scan**
A guided splash screen introducing 360 environment scan in live interviewing, helping users quickly understand its benefits and usage
* **Benefits**:
1. Instant Familiarization
2. Smooth Onboarding
3. Improved Efficiency
4. Seamless User Experience
## Assessment Engine Updates
**Assessment Playlist Configuration:**
* You can now **seamlessly control question randomization, skip, and review flows** for test takers while setting up assessments directly in the **Assessment Engine**.
* Previously, this control was available only through a **GB Flag**, but it has now been moved to **Assessment-level configuration**, giving users greater flexibility to decide **how questions are presented to test takers**.
## What's Next?
* **Ivy Persona Builder**: We are developing a feature that will allow content managers to efficiently manage Ivy from Assessment Engine Itself. Expected in Q4 2025, this feature will further streamline workflows.
* **Migration of CodeSolo Score Computation and Reports**: We are transitioning CodeSolo’s score computation and reporting functionalities from the legacy system to the Assessment Engine. This migration, targeted for Oct 2025, will improve performance, reporting accuracy, and system consistency.
## Secure Browser Updates
1. **In Production:** Windows store: 2.0.12 | Mac: 2.0.10
2. **Confirmation modal on exit:** When a user attempts to close **the Secure Browser**, a confirmation modal now appears. This prevents accidental closure and avoids unnecessary disruption to the exam flow.
3. **Mac feature updates (parity with Windows)**
* **Clipboard clearing**:` Copy-paste` actions from/to Secure Browser are blocked.
* **Restricted software alerts**: A persistent message is shown until the conflicting application is closed.
4. **Detection of screen lock & user switch (Windows):** Secure Browser now detects when a *user switches accounts or locks the screen during an exam*. Such actions are logged, and the browser must be closed and relaunched to continue.
5. **Updated blocklist applications:** We’ve refreshed the blocklist of restricted applications.
## Integrations \[V7+] Updates
* **Confirmation modal pops up when “Stop Proctoring” is clicked:**
When a candidate clicks **Stop Proctoring** during an LMS quiz, a confirmation modal appears warning them of the consequences. Confirming this action ends the proctoring session and marks the quiz attempt as submitted.
# August 2026 Release Updates
Source: https://docs.talview.com/releasenotes/q3-2026/august-2026-release-updates
The August 2026 release delivers enhancements across **Workflow Tools, Interview Rooms, Proctoring, Assessment Engine & Candidate Experience, and Admin**, introducing improved notification controls, expanded candidate visibility, new Form Builder capabilities, and platform reliability improvements.
***
### Workflow Tools Enhancements
This month, we introduced enhancements focused on improved notification control, candidate assessment history, expanded workflow fields, and global candidate visibility.
#### 🆕 Features
**1️⃣ Notification Preferences**
**Description**: Users can now control which notifications they receive and on which channel from a dedicated Notifications Preferences page under Settings.
**What's New**
* Notification categories listed with a short description of what each one covers.
* Per-category channel selection, check or uncheck each channel individually.
* Email and In-App available for all users; SMS available to users with a phone number on their profile.
* Preferences enforced on the backend send path, so an unselected channel is skipped at delivery. Preference changes save immediately with no separate save action.
**2️⃣ Previous Assessment Attempts**
**Description**: Recruiters can now review all previous assessment attempts for a candidate, not just the most recent one.
**What's New**
* Activity History entry in the Assessment side panel kebab menu.
* Previous attempts list with one card per attempt.
* Attempt detail view showing overview and score, with back navigation. Preview of previous assessment responses.
**3️⃣ Additional Fields & Column Picker**
**Description**: Workflows now carry a wider set of structured fields, and recruiters can choose which fields appear as columns in their candidate lists.
**What's New**
* New workflow fields across Job Classification, Skills, Location, Hiring Timeline, and Project and Contract flags.
* Column picker on the candidate list, with selections saved per user and applied across workflows. Search extended to cover the additional candidate fields.
**4️⃣ Global Candidate View: Candidate Profile Columns**
**Description**: The Global Candidate View now includes education, work experience, and Resume Fitment status as columns.
**What's New**
* Education and Resume Fitment status columns added to the candidate table.
* Work experience sourced from the structured candidate record, covering designation, organization, start and end dates, and current-role flag.
* Experience data now visible to Hiring Managers, Collaborators, Evaluators, and External Evaluators.
***
#### 🐞 Bug Fixes
**Workflow Tools: Candidate Lists, Evaluation & Workflow Setup**
* Restored global search, advanced filters, quick actions, and bulk actions across Workflow Tools.
* Fixed Resume Fitment defects, assessment scoring errors, and evaluation flow issues.
* Fixed workflow setup problems, public registration form rendering, and broken empty states.
**Notifications & Screening: Email Delivery, Parsing & Ivy**
* Fixed interview invitation, assessment reminder, and technical assessment emails not triggering.
* Fixed incorrect scheduling links and interview dates sent to candidates.
* Fixed Ivy call transcription unavailability and Potential Fit candidates incorrectly assigned Turn Down status.
* Improved resume parsing performance.
***
### Proctoring Updates
This month, we introduced enhancements focused on expanded coordinator tools and a new native Moodle integration.
#### Proview Console (V8)
#### 🆕 Features
**1️⃣ Exam to Center and Schedule Mapping**
**Description**: One or more centers can now be tagged to an assessment step in an exam, with coordinators able to define schedules and capacity per schedule.
**What's New**
Virtual or physical centers can be tagged to an assessment step. Coordinators can define schedules and capacity per schedule under the respective assessment tab. Enables slot management and center assignment for bookings.
**2️⃣ Assessment List View: Verification & Risk Index Columns**
**Description**: A Verification column showing ID and face-auth results has been added to the Assessment List View, with click-through to the timeline view.
**3️⃣ Rename Flow Config to Exam Security Configurations**
**Description**: Flow Config has been renamed to Exam Security Configurations throughout the UI. This is a naming-only change with no functional or behavioral changes.
**Enabled Editing Published Exam Security Configurations**
**Description**: Coordinators, platform admins, and tenant admins can now edit a published Exam Security Configuration directly.
**What's New**
Editing creates a new version and archives the old one instead of blocking the edit entirely.
***
#### Integrations (V8)
#### 🆕 Feature
**V8 Native Moodle Plugin Integration**
**Description:** The new integration is delivered as a native Moodle quiz plugin, introducing a fully redesigned experience for instructors, candidates, and reviewers.
**What's New**
* Flow-based proctoring configuration for instructors directly from the quiz settings page.
* Automatic proctoring window set from quiz open and close dates.
* Proctoring session ends automatically on candidate quiz submission.
* One-click recording playback via a View recordings button on the quiz page.
***
#### 🐞 Bug Fixes
* Base reference image not displaying in the checks pane.
* Photo ID check displaying when ID verification was disabled for the exam.
* Hyperlink and numbered-list formatting not preserved when sending a message to a candidate.
* Alvy's automated responses not appearing in the proctor's individual chat view.
* Messages sent through individual chat not being received by the candidate.
***
### Interview Rooms Enhancements
This month, we introduced enhancements focused on improved transcription accuracy.
#### ⚙️ Enhancements
**1️⃣ Soniox Transcription Accuracy**
Resolved language identification hallucinations in Soniox via English language hints and strict LID mode. Rate-limit and concurrency constraints have also been addressed.
***
#### 🐞 Bug Fixes
* Fixed an intermittent transcription failure.
***
### Assessment Engine & Candidate Experience Updates
This month, we focused on improved candidate experience controls and assessment authoring.
#### 🆕 Features
1️⃣ **Exit Confirmation for Test Sessions**
**Description**: Candidates now get a browser warning before accidentally leaving an active test.
**What's New**
Native browser confirmation prompt appears if a candidate tries to close or refresh the tab during an active test. Applies only while a test is in progress, not on instruction, hardware-check, or post-submission pages.
***
#### ⚙️ Enhancements
1️⃣ **Skill ID Now Visible in Skill List**
The skill list now displays each skill's ID, making it faster to find and reference the right skill.
2️⃣ **Retakes Off by Default for New Async Assessment Sections**
Question-level retakes are now disabled by default when creating a new asynchronous assessment section. Existing assessments are unaffected.
3️⃣ **Editing Disabled for Published Assessments**
Assessments can no longer be edited once published, preventing accidental changes after approval.
***
#### 🐞 Bug Fixes
Fixed an issue where only multiple-choice questions could be added to an assessment from a skill, even when other published question types were available.
***
### Admin (Forms) Updates
This month, we focused on **improving form reliability**.
#### 🐞 Bug Fixes
* Incorrect form status color in the Form List view.
* Hidden field rendered without meeting its conditional logic.
* Unable to enter details in Preview Mode.
* Unable to upload a PDF file in the File Upload field, blocking form submission.
* Long text input overflowing outside the form instead of wrapping correctly.
* Download failing after form submission with a "File data not found" error.
* Phone number text not visible due to low contrast in the Phone Number field.
***
# July 2026 Release Updates
Source: https://docs.talview.com/releasenotes/q3-2026/july-2026-release-updates
The July 2026 release delivers enhancements across **Workflow Tools, Interview Rooms, Proctoring, Assessment Engine & Candidate Experience, and Admin**, introducing improved candidate visibility across workflows, expanded session review tools, new Form Builder capabilities, and platform reliability improvements.
***
### Workflow Tools Enhancements
This month, we introduced enhancements focused on **improved candidate visibility across workflows and Ivy Call transcription**.
#### 🆕 Feature
1️⃣ **"All" View Candidate Side Panel**
**Description:** Recruiters can now view a candidate's entire workflow journey across Screening, Assessment, and Interview in a single unified side panel from the All tab.
**What's New**
* Consolidated candidate header, Resume Fitment sub-card, and step-wise accordion cards with per-step states.
* Activity timeline showing full candidate history in one vertical feed.
* Sticky footer with Schedule and Invite actions available directly from the All view.
* Grouped column headers and per-step filter grouping on the candidate table.
2️⃣ **Ivy Call Transcription in Call History**
**Description:** Recruiters can now read a full transcript of Ivy AI calls directly from the Call History tab, alongside existing audio playback.
**What's New**
* Transcript link on the call history card, shown only when transcript data is available.
* Transcript modal displaying conversation segments in chronological order.
***
#### 🐞 Bug Fixes
**Workflow Tools: Platform Stability**
* Search and filters not functioning across All, Screening, and Assessment tabs.
* Resume Fitment, Score, and Proctoring column display errors.
* Schedule validation gaps and overlapping interview slot conflicts not flagged.
* Resume upload issues in the Invite Candidate flow and bulk uploads.
* Recruiter Dashboard and Inbox stuck on blank or loading state.
* Password reset emails not containing a working link.
**Scheduler: Payment, Booking & Notification**
* Payment issues including incorrect tax deduction and duplicate rescheduling fees.
* Resume parsing reliability issues including slow parsing and bulk upload failures.
* Candidates not receiving assessment invite and slot confirmation emails.
* Stale OTPs and Microsoft Teams redirection failures.
***
### Proctoring Updates
This month, we introduced enhancements focused on **expanded session review capabilities, proctor visibility, and coordinator tools**.
#### Proctor/Center Management (V8)
#### ⚙️ Enhancements
1️⃣ **Session Timeline in Session Summary Report**
**Description:** The session summary report now includes a session timeline showing session start and end times upfront, with a "View full timeline" link to expand and view all key events in between.
**What's New**
* Key events include pauses, extensions, suspensions, disconnections, and more.
2️⃣ **Proctor Lead Session Entry**
**Description:** Proctor leads can now join their active slots directly from their sessions screen.
**What's New**
* Clicking Join Now takes the proctor lead straight into the candidate list view for that slot to begin managing proctor allocation and overseeing candidates.
***
#### 🐞 Bug Fixes
* Candidates joining from a secondary device appeared as two separate tiles in the monitoring grid.
* Switch/Replace button incorrectly appearing on the Secondary Feed tile.
* Inconsistent feed layout across candidate tiles depending on the order participants joined.
* Activity Playback clipped and not fully visible from the candidate monitoring view.
* Broadcast Chat not resetting when switching from Grid View to Individual Candidate view.
***
#### Coordinator Console (V8)
#### 🆕 Features
1️⃣ **Calendar View in Assessment Tab**
**Description:** Coordinators can now switch between a candidate view and a calendar view within a fixed slot assessment step tab.
**What's New**
* The calendar view shows scheduled slots grouped by date with capacity and booking information.
* Coordinators can add or delete schedule slots directly from the same tab.
* Only available for steps configured with drive schedule.
***
#### ⚙️ Enhancements
1️⃣ **Guardian Consent Status in Candidate Profile**
**Description:** Coordinators can now see the guardian consent status directly within a candidate's profile.
**What's New**
* A Guardian Consent event appears in the candidate's timeline showing consent status, guardian's email address, and timestamp of when the request was sent.
2️⃣ **Filters and Search in Enrollment List**
**Description:** Coordinators can now search and filter the enrollment list view to quickly find specific candidates.
**What's New**
* Search by name, email, or external ID.
* Filters available across enrollment status, current step, payment status, exam center, accommodations, invited by, and date ranges.
3️⃣ **Filters in Voucher Management**
**Description:** Coordinators can now search and filter the voucher management view to quickly locate specific vouchers.
**What's New**
* Filters available for discount value, expiry date, and creation date.
4️⃣ **Deepfake Detection Configuration in Flow Config**
**Description:** Coordinators can now enable deepfake detection when creating or updating an onboarding flow.
**What's New**
* When enabled, deepfake detection runs automatically during the face capture step of the candidate's onboarding.
***
### Interview Rooms Enhancements
This month, we introduced enhancements focused on **improved session reliability and transcription accuracy**.
#### 🆕 Features
1️⃣ **Auto Screen Share Conflict Resolution** When a new participant starts sharing their screen, the previous participant's share now stops automatically.
2️⃣ **Insights Workflow Stability** Resolved timeout failures in the insights workflow at the candidate performance save step.
3️⃣ **Soniox Transcription Accuracy** Improved transcript accuracy for sessions with non-English speech.
***
### Assessment Engine & Candidate Experience Updates
This month, we focused on **improving assessment reliability and candidate experience accuracy**.
#### 🐞 Bug Fixes
* Assessment duration mismatch between the Library overview page and actual configuration.
* Longform section timer starting with less time than configured.
* Published persona changes not reflecting on the dashboard immediately.
* Broken, oversized, or incorrectly oriented question images.
* Browser back button allowing candidates to re-open a submitted assessment.
***
### Admin (Forms) Updates
This month, we introduced enhancements focused on **new Form Builder capabilities across list management, response handling, and version control**.
#### 🆕 Features
1️⃣ **Forms List**
**Description:** A dedicated forms list is now available with navigation, search, and filter support.
**What's New**
* View all forms in a table with search and filter options.
* Navigate directly to any form from the list.
2️⃣ **Form Responses**
**Description:** Candidate form responses can now be viewed and managed directly from the platform.
**What's New**
* Search, filter, sort, and paginate through responses.
* View individual responses in detail.
* Download a form response as a PDF.
3️⃣ **Version History**
**Description:** Form editors can now view, preview, and restore previous versions of a form.
**What's New**
* Access full version history for any form.
* Preview and restore earlier versions as needed.
4️⃣ **New Form Creation**
**Description:** Users can now create a new form from scratch directly within the platform.
***
#### **⚙️ Enhancements**
1️⃣ **Inline Form Title Renaming** Form titles can now be renamed inline with duplicate-name validation to prevent conflicts.
***
#### 🐞 Bug Fixes
* Form data not retrieved when duplicating a form.
* Form renaming not working correctly.
* Duplicated forms not appearing without a page refresh.
* Search bar not functioning in the forms list.
* Avatar image not displaying correctly.
* Number values stored as strings not rendering correctly.
* Radio button highlighting entire field instead of selected option.
***
# December 2024 Release Updates
Source: https://docs.talview.com/releasenotes/q4-2024/release-notes-dec-2024
Welcome to the November release notes, where you can explore the most recent enhancements on TOP and Proctoring.
## Workflow Tools & Candidate Experience
### **Workflow Tools Enhancements**
* **Evaluator list view filters:** Evaluators can now filter their assigned candidate list based on workflow, status, and assessment score, making it easier to prioritize key candidates, access relevant records quickly, and streamline the overall evaluation process. Check out more details here: [https://portal.productboard.com/ds8uersvkfqrlqmyubqxam75/c/150-list-view-of-the-evaluations-with-filters-and-sorting?\&utm\_medium=social\&utm\_source=starter\_share](https://portal.productboard.com/ds8uersvkfqrlqmyubqxam75/c/150-list-view-of-the-evaluations-with-filters-and-sorting?\&utm_medium=social\&utm_source=starter_share)
* **Candidate name in IS interviewer email :** Interview invitations, rescheduling, and RSVP emails to the interviewers now include the candidate's name in the subject line, enabling them to quickly identify relevant details, reduce confusion, and ensure timely interview participation. Check out more details here:[https://portal.productboard.com/ds8uersvkfqrlqmyubqxam75/c/149-add-candidate-name-in-the-interviewer-email-subject?\&utm\_medium=social\&utm\_source=starter\_share](https://portal.productboard.com/ds8uersvkfqrlqmyubqxam75/c/149-add-candidate-name-in-the-interviewer-email-subject?\&utm_medium=social\&utm_source=starter_share)
### **Candidate Experience Enhancements**
* **Cancel and Refund rules for exam slot booking:** Candidates can now cancel their booked exam slots and receive refunds based on configurable organizational policies, improving clarity, flexibility, and overall satisfaction with booking management. Learn more here: [https://portal.productboard.com/ds8uersvkfqrlqmyubqxam75/c/135-cancel-and-refund-policies?\&utm\_medium=social\&utm\_source=starter\_share](https://portal.productboard.com/ds8uersvkfqrlqmyubqxam75/c/135-cancel-and-refund-policies?\&utm_medium=social\&utm_source=starter_share)
* **Multicurrency support for Payment:** Multi-currency support now allows candidates to pay in their preferred currencies, such as Euros or GBP, while organizations can configure currency options at the SKU level, enhancing global payment flexibility and reducing drop-offs. Check out more details here: [https://portal.productboard.com/ds8uersvkfqrlqmyubqxam75/c/151-multicurrency-support-for-payment?\&utm\_medium=social\&utm\_source=starter\_share](https://portal.productboard.com/ds8uersvkfqrlqmyubqxam75/c/151-multicurrency-support-for-payment?\&utm_medium=social\&utm_source=starter_share)
* **Integration of Standalone forms:** Organizations can now integrate standalone forms into the candidate journey, enabling seamless data collection at any workflow step and improving efficiency and the overall candidate experience. Learn more: [https://portal.productboard.com/ds8uersvkfqrlqmyubqxam75/c/152-integration-of-standalone-forms-with-candidate-experience?\&utm\_medium=social\&utm\_source=starter\_share](https://portal.productboard.com/ds8uersvkfqrlqmyubqxam75/c/152-integration-of-standalone-forms-with-candidate-experience?\&utm_medium=social\&utm_source=starter_share)
**Who are the primary users of this feature?**
> The features mentioned above will provide the greatest benefit to the **evaluators** and the **candidates.**
**What are we working on next?**
1. Test taker experience enhancements - Skip-enabled workflows
2. SMS workflows for RSVP negotiations
3. Unified notification inbox - WIP
4. No-show enhancement notifications - WIP
5. Self-scheduling cancellation for candidate slot booking - WIP
**Are there any known issues (caveats)?**
* IS emails cannot be customized, only an external link can be added at an organizational level.
* Test taker can be used as an external assessment inside attend-ng.
* Async videos (using the new test taker) are unavailable for review.
## Interview Rooms
### New Features
**In meeting diagnostic**
* **Description**: A semi-transparent diagnostics tab, activated in-meeting with Shift+D, monitors bitrate, packet loss, resolution, and FPS to ensure clear audio, smooth video, and seamless screensharing quality.
* **Benefits**:
* **Real-time Issue Detection:** Identify video, audio, or screen-sharing issues instantly, ensuring a smoother interview experience.
* **Improved Troubleshooting:** Provides immediate insights into performance metrics, enabling quick resolution of technical problems during the session.
**Seamless Reconnect for Offline Room Sessions**
* **Description**: Ensure uninterrupted experience with clear error messages and a simple rejoin option when network issues occur.
* **Benefits**:
* **Enhanced User Clarity:** Instantly informs users about network disruptions with a clear error message.
* **Streamlined Recovery:** Offers a convenient "Rejoin" button to resume sessions quickly.
* **Minimized Downtime:** Saves time by allowing users to rejoin without restarting the application.
### Enhancements
**Hide Sample Run in CodeJam When Sample Input is Unavailable**
* **Description**: Automatically hides the sample run section in CodeJam for questions lacking sample input or entirely missing the question.
* **Benefits**:
* **Improved Clarity**: Avoids confusion for users when no sample input is provided.
**Execute Code in Quick Test Without Input**
* **Description**: In codejam run and test code seamlessly in Quick Test mode even when no input is provided.
* **Benefits**:
* **Enhanced Flexibility**: Allows users to test code without requiring predefined input, accommodating broader use cases.
* **Faster Debugging**: Facilitates quick iterations and testing of code logic without additional setup.
* **Improved Accessibility**: Makes Quick Test more intuitive and user-friendly for a wide range of coding scenarios.
### **Bug Fixes**
We have focused on closing the high-priority bugs listed below
* After the video service provider fallback, the interviewer’s landing page showed the candidate as left, though they were in the meeting, with a small tile.
* Fixed meeting and section names in meeting when scheduled from WFT.
**Who are the primary users of this feature?**
Candidates & Interviewer
**To Explore the platform**
These features are available in the Recruit production environment. & WFT production account [wt.talview.com](http://wt.talview.com))
**What are we working on next?**
* **Interview insights - WIP**
* Playback of chat is released
* **Secondary camera on interviewer request-** **WIP**
* **360 degree environment check on interviewer request-** **WIP**
## Proctoring
### Proctor NG
**Enhancements**
1. **Redirecting users to the new playback view** “is\_ng\_redirect” flag has been added, which if enabled as “true”, will redirect the users to the new playback view, without needing to check for the video streaming provider.
**Bug Fixes**
1. **Twilio reconciliation fix** **Issue:** The Twilio Retrigger API is unable to process sessions exceeding its 27-track limit, resulting in missing tracks and failure to trigger compositions. **Solution:** To address this, tracks with no duration will be omitted from the composition request. Additionally, the API now requires 4 parameters to trigger the composition: `session_uuid`, `room_sid`, `is_talview_composition`, and `device_type`
* The `is_talview_composition` field determines whether Talview's composition engine or Twilio's default composition engine will be used.
* The `device_type` field distinguishes between primary and secondary devices in the session. For more details about the API change, refer to [this document](https://www.notion.so/Changes-to-the-Twilio-Retrigger-API-15f3461472f380ada55ed2562aacde4a?pvs=21)
### **Attendee Ex**
**Enhancements**
1. **Retry logic on streaming disconnection**
* The candidate will be presented with the “Retry Connection” page after being disconnected with video streaming provider.
* The candidate will only be allowed to click on the “Retry Connection” button a maximum of 3 times. If this reconnection attempts fails, their browser will refresh and the candidate is made to restart the pre flight checks.
**Important note:**
In case of unstable internet connection, a candidate can proceed with giving their proctored exam, but the twilio videos might get missed.
Few sessions that have audio missing is being checked with livekit team.
## Admin
### **UI Enhancements**
1. **Upgraded Typography and Padding** Enhanced typography and updated padding provide a cleaner and more user-friendly interface for forms.
2. **Row Span for Photo Capture Field** The photo capture field now supports a row span feature, enabling dynamic size adjustments for improved layout flexibility.
### **New Features and Functionality**
1. **“Photo” File Type in File Upload Block**
* A new file type for the file upload block accepts **JPG, JPEG, and PNG formats** and validates uploads based on face detection.
* Includes a **face authentication option**, offering enhanced verification capabilities similar to the photo capture field.
2. **Conditional Logic for Groups and Sections** Conditional logic can now be applied to entire groups or sections of fields in a single action, eliminating the need to configure individual fields separately.
# November 2024 Release Updates
Source: https://docs.talview.com/releasenotes/q4-2024/release-notes-nov-2024
Welcome to the November release notes, where you can explore the most recent enhancements on TOP and Proctoring.
## Workflow Tools & Candidate Experience
### **Workflow Tools Enhancements**
Evaluators can now add their [**recommendations**](https://portal.productboard.com/ds8uersvkfqrlqmyubqxam75/c/145-evaluators-can-now-add-their-recommendation-against-a-candidate-via-workflow-tools?\&utm_medium=social\&utm_source=starter_share) and [**comments**](https://portal.productboard.com/ds8uersvkfqrlqmyubqxam75/c/144-evaluators-can-now-add-their-feedback-against-a-candidate-via-workflow-tools?\&utm_medium=social\&utm_source=starter_share) about a candidate and join interviews from the side panel \*\*in Workflow Tools. Check out the below gif:
### **Candidate Experience Enhancements**
* **Attend-ng updates:**
* **[Mobile Assessment Support](https://portal.productboard.com/ds8uersvkfqrlqmyubqxam75/c/141-support-external-assessments-on-mobile-with-attend-ng?\&utm_medium=social\&utm_source=starter_share):** This feature ensures candidates can complete external assessments seamlessly on mobile devices, improving the experience and reducing drop-offs.
* **[Post-Assessment Redirection](https://portal.productboard.com/ds8uersvkfqrlqmyubqxam75/c/142-post-assessment-url-support-with-attend-ng?\&utm_medium=social\&utm_source=starter_share):** Guides candidates to a predefined URL after assessment completion, reducing confusion and improving engagement.
* **CX 3.x updates:**
* **[Payment Integration](https://portal.productboard.com/ds8uersvkfqrlqmyubqxam75/c/148-integration-with-lemon-squeezy?\&utm_medium=social\&utm_source=starter_share):** Integrates **Lemon Squeezy** payment provider to provide candidates with diverse payment options, reducing drop-offs and enhancing transaction success rates.
* **[Assessment Time Tracking](https://portal.productboard.com/ds8uersvkfqrlqmyubqxam75/c/147-store-time-taken-to-complete-an-assessment?\&utm_medium=social\&utm_source=starter_share):** Captures and stores the time taken by candidates to complete an assessment step, aiding analysis for completed and dropped assessments.
* **[Customizable Registration Form](https://portal.productboard.com/ds8uersvkfqrlqmyubqxam75/c/143-candidate-registration-form-integration-via-feature-flag-for-drive-workflow?\&utm_medium=social\&utm_source=starter_share):** Introduces a configurable **registration form** during drive sign-up, enabling organizations to collect tailored candidate data, with pre-filled fields for returning users to improve efficiency.
**Who are the primary users of this feature?**
> The features mentioned above will provide the greatest benefit to the **evaluators** and the **candidates.**
**What are we working on next?**
1. Test taker experience enhancements - Skip-enabled workflows
2. SMS workflows for RSVP negotiations
3. Unified notification inbox - WIP
4. No-show enhancement notifications - WIP
5. Self-scheduling cancellation for candidate slot booking - WIP
6. Recruiter calendar flows
**Are there any known issues (caveats)?**
* IS emails cannot be customized, only an external link can be added at an organizational level.
* Test taker can be used as an external assessment inside attend-ng.
* Async videos are not available for review.
## Interview Rooms
### New Features
**Voip call the candidate from Interview Rooms (WFT)**
* **Description**: Initiate VoIP calls to candidates directly from the interviewer landing page to reduce no shows, ensure seamless communication and interview flow.
* **Benefits**:
* **Quick Candidate Contact**: Reach out to candidates who haven’t joined the session with a single click, improving punctuality and attendance.
* **Seamless Interview Experience**: Conduct interviews without needing to switch platforms, reducing friction and keeping the process efficient.
* **Enhanced Communication**: Stay connected with candidates directly through the interview platform, ensuring clear and uninterrupted conversations.
**Session Recording Notification**
* **Description**: Notify participants (Interviewers/Candidates) with notification “The interview is being recorded” when a session is being recorded to ensure transparency and compliance
* **Benefits**:
* Keep participants informed with session recording notifications.
* Ensuring transparency and enhancing trust
### **Feature Enhancements**
**Interview guide error state**
* **Description**: If fetching the interview guide based on the job description fails, a "Failed to generate guide" notification with a retry option is shown
* **Benefits**:
* Improved User Experience
* Faster Recovery from Failures
### **Bug Fixes**
We have focused on closing the high-priority bugs listed below
* Handling refresh on feedback page
* Handling refresh on evaluation page
* The recording indicator color does not change when the candidate rejoins the session with recording consent
**Who are the primary users of this feature?**
Candidates & Interviewer
**To Explore the platform**
These features are available in the Recruit production environment. & WFT production account [wt.talview.com](http://wt.talview.com))
**What are we working on next?**
* **Interview insights - WIP**
* **Secondary camera on interviewer request-** **WIP**
* **360 degree environment check on interviewer request-** **WIP**
## Proctoring
### Attendee Ex
**Enhancements**
1. **Performance optimization of attendee V7+** The interval at which the alert to detect object and face has been increased. This will reduce the usage of CPU, thereby improving device performance. This has been deployed to Cambridge’s pre prod. Drawing of the face inside the camera thumbnail has also has been removed.
2. **Camera preview is hidden by default during session recording** When the pre flight checks are initiated for the attendee, their camera’s preview will be hidden by default. The attendee will be informed via a tooltip that that they can maximize the camera preview by hovering over the camera thumbnail.
3. **Updated message to test takers for hardware audio test** The text displayed to the test taker during the hardware audio check has been updated. This prevents confusion on whether the they have successfully completed this check.
**Bug Fixes**
1. **Attempt to retry connecting with streaming after session completion** **Issue:** Attempt to retry connecting with both streaming service providers- Twilio and Livekit was appearing after proctored session was completed. The retry connection attempt is only supposed to appear when proctored session is active **Solution:** The issue has been resolved, and the streaming connection retry attempt wont appear unless the error is encountered during an active proctored session.
2. **White screen issue faced while attending a quiz** **Issue:** There was a white/blank screen appearing when attendee was giving a quiz. **Solution:** This was caused by special characters being provided in the instructions box. The issue has been resolved. Special characters as well as rich text instructions is now allowed and can be provided.
### Proctor NG
**Bug Fixes**
1. **Proctor and candidate instruction not showing on Embedded playback view** **Issue:** An assessment created in Recruit, with proctor & candidate instructions provided was not appearing in the embedded playback view. **Solution:** The issue has been resolved, and the respective instructions will now appear in the embedded view.
### Integration
**Enhancements**
1. **Restricting quiz availability time to 48 hours ahead** To allocate sufficient time for proctoring resources, admins will now need to set the quiz open time at least 48 hours from the current date and time. This enhancement includes displaying a warning message if the user attempts to set an earlier open time. Additionally, the "Save" button will be disabled until an appropriate date and time is set according to this rule, ensuring compliance.
2. **Differentiation between drive and self-scheduled events in Proview** Slots that have been booked via self scheduling will now follow the following naming convention: \[**Self-proctoremailid-Day, Event Date and Time in UTC format]** for example: **[Self-sagar@talview.com](mailto:Self-sagar@talview.com), Thu 19 Nov, 16:00:00 UTC**
3. **Validation for quiz open/close times on individual student assignments** The system can now validate the quiz open and close times for quizzes individually assigned to specific candidates.
**Bug Fixes**
1. **Minutes label was missing in booking page** **Issue:** The minutes label was missing from the time limit in the quiz details on the booking page, potentially leading to confusion. **Solution:** Now when the candidate views the booking page, the time limit displayed contains the minute count along with the label
2. **Scrollable bars in the booking calendar** **Issue:** There were two scroll bars - one horizontal and one vertical on the booking calendar displayed to the candidate. minutes label was missing from the time limit in the quiz details on the booking page, potentially leading to confusion. **Solution:** These scrollbars have now been disabled.
3. **Slots were not correctly displayed against the proctor’s availability** **Issue**: When the candidate views the CX calendar, slots were being displayed even after the last slot of the proctor’s availability. **Solution**: The issue has been fixed, now if the **"last slot BE to\_date"** is the lesser of the attributes, then the candidate will only see slot up to there.
## Admin
1. **Photo Capture Field** Respondents can now capture their photo directly within the form using their device's camera.
This feature includes:
* **Face Detection**: Ensures there’s a straight face detected in the camera before allowing to capture the image. Available for both photo capture and image upload fields.
* **Preview**: allowing respondents to verify their image before submission.
2. **Prefill Fields with Respondent Data** To streamline the form-filling process, fields can now be pre-filled with the respondent's previously known data. This reduces redundancy and ensures a smoother experience when respondents fill out a form for the first time.
3. **Field Grouping with Visual Sections**
* You can now group multiple fields into **sections** within a form, making it easier to organize related fields.
* Each section can include **visual borders**, providing a structured layout for respondents.
4. **Regex Validation for Short Text Fields**
* Implement regex (regular expressions) for short text fields to enforce specific input formats (e.g., email addresses, phone numbers).
* Add **custom validation messages** to guide respondents when their input does not meet the required format.
# October 2024 Release Updates
Source: https://docs.talview.com/releasenotes/q4-2024/release-notes-oct-2024
Welcome to the October release notes, where you can explore the most recent enhancements on TOP and Proctoring.
## Workflow Tools & Candidate Experience
### **IS enhancements to support the certification use case**
* **[Slot Booking for Live proctored exams](https://portal.productboard.com/ds8uersvkfqrlqmyubqxam75/c/138-slot-booking?\&utm_medium=social\&utm_source=starter_share):** Candidates can now book exam slots directly through the LMS platform with automatic time zone adjustments, ensuring a seamless scheduling experience in their local time.
* **[Flexible Rescheduling](https://portal.productboard.com/ds8uersvkfqrlqmyubqxam75/c/139-reschedule-slots?\&utm_medium=social\&utm_source=starter_share):** Candidates may reschedule their live proctored exam slots until the scheduled start time, allowing for greater flexibility and improved attendance.
* **[Extended Booking Window](https://portal.productboard.com/ds8uersvkfqrlqmyubqxam75/c/140-slot-booking-based-on-quiz-time?\&utm_medium=social\&utm_source=starter_share):** The slot booking process now includes a designated booking window from the exam's start to end dates, giving candidates ample time to select a suitable slot without confusion.
**Who are the primary users of this feature?**
> The features mentioned above will provide the greatest benefit to the **proctor management team** and the **test takers.**
**What are we working on next?**
1. Test taker experience enhancements - Skip-enabled workflows
2. SMS workflows for RSVP negotiations
3. Unified notification inbox - WIP
4. No-show enhancement notifications - WIP
5. Self-scheduling cancellation for candidate slot booking - WIP
6. Recruiter calendar flows
**Are there any known issues (caveats)?**
* IS emails cannot be customized, only an external link can be added at an organizational level.
* Async videos are not available for review.
## Interview Rooms
**Grouping of IR alerts (Unified Alert Acknowledgment)**
* **Description**: Consolidate redundant notifications for evaluators into a single alert with an occurrence count, simplifying acknowledgment.
* **Benefits**:
* **Reduced Notification Overload**: Evaluators receive a single grouped alert instead of multiple identical ones.
* **Efficient Acknowledgment**: Acknowledge all repeated notifications in one click, saving time and effort.
* **Enhanced User Experience**: Streamlined notifications reduce clutter, improving focus during evaluations.
### **Feature Enhancements**
**Focused view**
* **Description**: Automatically close the chat window when an interviewer opens the full view of evaluation or resume for a distraction-free experience.
* **Benefits**:
* **Enhanced Focus**: Prevents distractions by closing the chat window when the full view of critical documents is opened.
* **Cleaner Workspace**: Maintains an uncluttered interface, helping users concentrate on the evaluation or resume content.
* **Better Experience for Interviewers**: Enables smoother transitions between different tools without manual window management.
### **Bug Fixes**
We have focused on closing the high-priority bugs listed below
* Retain the guide content on refresh
* Fix on components render in white mode css, when theme switched to dark
* Fix on candidate name showing as interviewer in video tile in WFT
* Update video service provider list fetch from gb
**Who are the primary users of this feature?**
Candidates & Interviewer
To Explore the platform
These features are available in the Recruit production environment.
**What are we working on next?**
**Voip call the candidate from Interview Rooms - WIP**
* **Description**: Initiate VoIP calls to candidates directly from the interviewer landing page to reduce no shows, ensure seamless communication and interview flow.
* **Benefits**:
* **Quick Candidate Contact**: Reach out to candidates who haven’t joined the session with a single click, improving punctuality and attendance.
* **Seamless Interview Experience**: Conduct interviews without needing to switch platforms, reducing friction and keeping the process efficient.
* **Enhanced Communication**: Stay connected with candidates directly through the interview platform, ensuring clear and uninterrupted conversations.
## Proctoring
### Attendee Ex
**Enhancements**
1. **Configurable links in Terms and Conditions page** With the latest update following are configurable at tenant level
* Privacy policy
* Terms and conditions
* Support link
* Support email
2. **Error handling for internet connectivity issues/ video streaming disconnection** When a test taker's internet connection is disrupted or if there is a disconnection with the video streaming provider, then the system will display an error page. This page and the content within is translatable into proview supported languages
* If the video streaming provider is “**Livekit**”, then the test taker is presented with an appropriate error message along with instructions to perform a refresh.
* If the video streaming provider is “**Twilio**”, then the test taker is presented with a “**Retry Connection**” button. By clicking this, an attempt will be made to reconnect with Twilio video streaming.
**Bug Fixes**
1. **Proctor to candidate chat in platform streaming** **Issue:** If the service provider is Platform streaming, the chat by proctor was not visible to test taker. **Solution:** With this update the test taker will be able to see the chat messages sent by the proctor.
2. **Environment test multiple submissions issue** **Issue:** Due to internet issues during the pre-flight checks, test takers were able to click the “Submit” button multiple times after recording their environment video. This caused multiple environment test submissions to be displayed to the proctor for approval. **Solution:** The issue has been resolved and multiple submissions are prevented.
### Proctor NG
**Enhancements**
1. **Manually added description by the reviewer** When manually adding flags, reviewers will now also have an option to add a description. This description will now also be displayed in the alert logs.
2. **Updated ‘Completion time’ to ‘End time’ in Summary tab of playback** The verbiage has been changed from ‘Completion time’ to ‘End time’ to accommodate for scenarios where the reviewer has terminated the session manually.
3. **Adding pre-defined reason for manual Proview Index change** When reviewers (proctor/test admin) update the index manually they will be required to select a reason from the dropdown. Additionally, they can also add a short description. These changes will also be visible in the summary tab.
4. **Session completed API enhancements** Integrating systems can manually close open sessions using the */v1/session/completed* API. This API was only accepting session IDs in the past. Users can now also pass session UUID’s to manually close open sessions.
### Integrations
**Feature**
1. **Drive scheduling workflow is now available**
* If **Live Proctoring** is selected, a scheduling dropdown will appear. **Drive** can now be chosen as a **scheduling type** from the available options.
* On the test taker’s side, if the quiz is live proctored, a side panel will open with a message informing you that they’ll need to book a slot before starting the quiz.
* Upon clicking the **Manage Booking** button, a calendar will open where the available dates and times can be viewed.
**Enhancements**
1. **Browser plugin supports Secure Browser only use case** Canvas and D2L LMS instructors will now be allowed to enable the Secure Browser for quizzes without the need to enable proctoring.
2. **Proview index rating is displayed in playback list view**
* The Proview Index rating (high/medium/low) is now visible in the Proview playback list, allowing users to quickly identify and review high-risk sessions without extra clicks.
* Only test takers that have completed attempting their proctored session will have their playback details appear here. This is irrespective of role- student and learner are both encompassed.
* Search can be performed by the attributes- User ID, Full name, Email, Rating
3. **Enrollment sync for test takers in “Learner” role from D2L** Previously, test takers that are going to attempt quiz in “Learner” role weren’t appearing when user would perform enrollment sync in the LMS dashboard for bulk scheduling. Now that limitation has been addressed.
4. **Slot availability for self-scheduling based on quiz and proctor availability** Candidates will be able to book exam slots that align with both the quiz's opening/closing times and the proctor’s availability, candidates can only book within a timeframe that fits both the exam and the proctor’s schedule.
**Bug Fixes**
1. **Proview browser extension installation message** **Issue:** Test takers were prompted to install the Proview browser extension even when no proctoring was configured. **Solution:** The installation message will now only appear when proctoring is configured, allowing non-proctored quizzes to proceed without interruption. The validation script has been updated [here](https://www.notion.so/Canvas-LMS-Installation-Guide-6c1ae07342d3407aa46ee25b28094280?pvs=21)
2. **Minutes label missing in quiz details** **Issue:** The minutes label was missing from the time limit in the quiz details on the booking page. **Solution:** The issue has been resolved. When the test taker clicks on the “manage booking” button and views the quiz’s details, the time limit now displays the count along with “minutes” label avoiding any confusion.
3. **Candidate/proctor instructions & reference links were not displayed** **Issue**: Candidate and proctor instructions as well as the reference links were not getting displayed in Proview proctor app, even if the instructor had provided them when configuring a quiz. **Solution**: The issue has been resolved, and this information will now appear.
4. **Proctor was not getting added to the event in Proview** **Issue**: When a candidate books a slot against a proctor’s availability, the live proctored event is automatically created in proview. The proctor was not getting added automatically to the event in draft status in proview. The test admin would have to manually add the proctor once more before scheduling and publishing the event. **Solution**: The issue has been resolved. Now, when a candidate books a slot, and the event is created in proview, the proctor is automatically added to the event.
## Admin
### New Features
1. **Add Image:** Users can now embed images directly into forms, including branding elements like customer logos, instructional images, or visuals that enhance form context. This feature supports brand consistency and creates a more cohesive user experience.
2. **Auto-Save:** Auto-save has been added for all form edits. Changes in the form builder are now saved in real-time, securing progress and eliminating the need to worry about lost updates.
3. **Dependent Dropdowns:** This feature allows certain dropdown fields to adjust based on a preceding dropdown selection. For example, selecting a country in country dropdown will dynamically filter options in the “State” dropdown.
4. **Disabled Fields:** Admins can now disable specific fields within a form. Disabled fields appear but cannot be edited by respondents, making them ideal for informational content or static placeholder text.
### Enhancements
1. **Regex for Text Input:** Regex support for text input blocks allows to enforce specific formats for inputs, such as validating text or phone number formats at the entry level to ensure data accuracy.
2. **Duplicate Block:** Building large forms with repetitive fields is now easier with the "Duplicate Block" feature. Users can quickly create copies of any block, streamlining the construction of forms with multiple similar fields.
# December 2025 Release Updates
Source: https://docs.talview.com/releasenotes/q4-2025/release-notes-dec-2025
The December 2025 release introduces a range of enhancements and fixes designed to **streamline recruiter workflows, improve interview reliability, and strengthen proctoring integrations**. These updates set the foundation for a more execution-driven 2026, with continued focus on quality, accountability, and customer outcomes.
## Workflow Tools Enhancements
### ✅ **New Features:**
### 1. Candidate Filtering in “All” View
**Description:**
You can now filter candidates directly in the **All** view for faster navigation across high-volume workflows.
**What’s New**
* Filter by **step-level status** to quickly locate candidates.
* Narrow search across all workflow stages without manual scanning.
* Improves navigation and reduces time spent searching.
**Internal Notes:** Feature is Beta; enable via GrowthBook flag per tenant.
**Demo:**
### 2. Enhanced Public Registration Flows
**Description:**
Better control and visibility for public registrations.
**What’s New**
* Set **start/end dates** for registration windows.
* Instant access to **QR code + registration link** from Edit Registration.
* **Unpublish** action moved to tertiary button for clarity.
**Internal Notes:** Feature accessible from Public Registration settings.
**Demo:**
### 3. Advanced Filters in Screening Step
**Description:**
New filters inside the Screening step help recruiters locate the right candidates without scrolling through full lists.
**Available Filters**
* **Candidate Status:** Invited, In Progress, Completed, Evaluated, Selected, On Hold, Turned Down
* **Evaluation Status:** Not Evaluated, Select, Turn Down, Hold
* **Added Date:** Choose a specific date or a custom range
**Benefit:** Faster review, quicker decisions, reduced manual scanning.
**Demo:**
***
## Interview Rooms Enhancements
### **🐞Bug Fixes**
1️⃣ **Issue:** Ask AI prompts in Interview Builder were generated in JSON format instead of readable text
**Solution:** Updated the system prompt so Ask AI prompts in Interview Builder are now generated in a proper, human-readable format
2️⃣ **Issue:** Incorrect toaster message **“Environment check incomplete”** was displaying in the meeting environment for interviewer while the 360 environment check was in progress
**Solution:** Updated the toaster messaging logic to show the correct status when the **"Environment check progress”**
3️⃣ **Issue:** Tooltip was not displayed when hovering over the 360° button in recording section in work flow tools when no images were captured
**Solution:** Added a tooltip that displays “No images captured” when hovering over the 360° button recording section in work flow tools
4️⃣ **Issue:** Whiteboard collaboration was not working in-meeting when adding images using the Image tool
**Solution:** Fixed the issue to ensure whiteboard collaboration works correctly when images are added via the Image tool during meetings
***
## Proctoring Updates: Integrations \[V7+]
### **⚙️ Enhancements**
1. **Moodle 4.5 LMS | Extension Installation Validation**
* Students are now **prevented from accessing exams** unless the Proview extension is installed.
* A clear warning is displayed explaining the requirement.
* A dedicated button takes students directly to the [**Chrome Web Store download page.**](https://chromewebstore.google.com/detail/proview-proctoring/doblkllolfingbjkbmelgiepdggnbmhi)
* Once installed, students simply refresh the page to continue.
* Full student experience is documented in the [linked Moodle User Guide](https://www.notion.so/2403461472f380b99cb9c0f66bc07731?pvs=21).
> ⚠️ Requires adding a custom validation script. Implementation guide available [here](https://www.notion.so/Moodle-LMS-4-5-Installation-Guide-2403461472f3800e800bcb1860ece3d1?pvs=21):
**📸 Reference**:
### **🐞 Bug Fixes**
**Moodle 4.5 LMS | Missing Student Details in Playback (Live Proctoring)**
* **Issue:** Student name and email were not appearing in playback for Live Proctoring attempts.
* **Impact:** Admins and reviewers could not identify candidates in playback records.
* **Fix:** Updated integration parameters to correctly fetch candidate details.
* **Result:** All session playback tables now show complete candidate information across **all proctoring types**.
# November 2025 Release Updates
Source: https://docs.talview.com/releasenotes/q4-2025/release-notes-nov-2025
We’ve shipped key enhancements across **Workflow Tools, Interview Rooms, and Proview** this month. These updates enhance scheduling intelligence, workflow customization, interview integrity, and overall platform reliability.
## Workflow Tools Enhancements
This month, we introduced targeted improvements to make workflow creation smoother and more aligned with each organization’s hiring process.
### *1. Organization-Specific Workflow Templates*
**What’s new:**
Tenant Admins can now create and publish **custom workflow templates** using any combination of Screening, Assessment, and Interview steps, fully tailored to their organization’s hiring workflows.
**Why it matters:**
No more one-size-fits-all templates. Recruiters get workflows that match their internal processes, reducing manual edits and speeding up setup.
**How it works:**
* When enabled, org-specific templates are displayed.
* When disabled, default global templates continue to load as usual.
***
## Payment Enhancements
### *1. Appointment reminder emails to candidates*
**What’s new:**
We have introduced an email notification to candidates to remind them of their upcoming booked appointment/slot. They will receive a notification 24 hours before the start time
**Why it matters:**
This will help us reduce the no-shows and reschedule requests by the candidates who booked an appointment months in advance.
**How it works:**
* If enabled for a drive, email will be triggered to the candidates who have a slot confirmed
* The email notification will be sent 24 hours before the slot start time
### *2. SMS Notifications for booking and payments*
**What’s new:**
We can now trigger SMS notification to candidates in the pay and book flow when they complete the payment with a link to select the slot
**Why it matters:**
Sending additional notifications for key steps in the flow helps ensure candidates are informed of the next expected step
**How it works:**
* If SMS are enabled for a drive and
* Candidate has provided their phone number
* When the candidate completes the payment, we will send an SMS notification apart from the email with link to select slot
***
## Interview Rooms Enhancements
### Display Captured Environment Check Images in Interview Insights
* **Description**: Shows the 360° Environment Scan images inside Interview Insights for quick post-session verification.
* **Benefits**:
* Improved Post-Session Verification
* Easy Access to Environment Evidence
* Strengthened Fraud Detection
* Enhanced Transparency for Reviewers
**Bug Fixes**
We have focused on closing the high-priority bugs listed below
* Fixed an issue where the Interview Guide (AI-generated) would load even when the Job Description wasn’t updated.
* Fixed issues on auto-trigger 360° environment scan & secondary camera on candidate join
***
## Proctoring Updates
### Feature - Diagnostics for Blocklisted softwares in Secure Browser
Test takers can now launch the Secure Browser and test for any warnings on blocklisted apps before the actual test. During diagnostics, any blocklisted applications will be closed automatically. If an application cannot be closed, the test taker will see a message along with the diagnostics completion status to close the applications manually.
***
### **💡 Changes**
1. **Updated Blocklisted Application Handling**
Blocklisted applications are now closed as soon as the Secure Browser launches. After 1 minute, a restricted software pop-up appears for apps that couldn’t be killed. If a blocklisted app is opened after that point, no warning message will be displayed to the test taker.
2. **Applying blocklist for all customers**
We're removing domain based blacklist and applying blacklist for all customers.
***
### **🐞Bug Fixes**
1. **WhatsApp removed from blocklist**
WhatsApp was triggering an incorrect blocklisted application open error even when not running. To fix this, it has been temporarily excluded from the blocklist.
2. **Network throttling updates**
Network throttling on Windows Secure Browser has been significantly improved. Test takers should now experience network speeds closer to what they see on regular browsers.
3. **Windows store app blocklisting handling**
Windows Store applications were not being terminated earlier, causing repeated warning pop-ups. This has now been resolved.
***Known Issues -*** We’re working with Vendor to check these and resolve
1. Refresh pop up coming multiple times on click of stay/ leave
2. Double tap on video player to maximize/minimize video is causing SB to minimize
***
## Integrations \[V7+]
⚡The following enhancements are available with the new version of proview browser extension (1.5.2)
### 💡Enhancements
1. **Moodle 4.5 LMS | Notifying students about successful password injection**
Upon accessing a proctored quiz, the browser extension handles injecting the password into the field.
Now, when students click on the Attempt quiz button, a modal appears - notifying the student about successful password injection. Clicking the Start attempt button will initiate proctoring pre checks.
2. **Moodle 4.5 LMS | Ending proctoring upon clicking “Submit all & finish”**
Proctoring sessions in Moodle 4.5 now end automatically when students click **“Submit All and Finish.”**
With this update, all proctoring types (AI, R\&R, Live) close immediately after quiz submission, ensuring improved student experience.
For this to be implemented - a custom code snippet needs to be added. Follow [**these steps in the installation guide.**](https://docs.talview.com/integrations/lms-integrations/client-admin/moodle_4.5/moodle_4.5-installation-guide#add-custom-script-to-end-proctoring-upon-quiz-submission)
3. **Moodle 4.5 LMS | Redirecting student to SB completion page**
This is applicable only to no proctoring, SB only use case. \
For this to be implemented - a custom code snippet needs to be added.\
Follow [these steps in the installation guide.](https://www.notion.so/Moodle-LMS-4-5-Installation-Guide-2403461472f3800e800bcb1860ece3d1?pvs=21)
Suppose a student is taking a non proctored quiz in secure browser, then upon quiz submission and clicking finish review - the student will be directed to the [following page](https://pages.talview.com/proview-submission/).
4. **Moodle 4.5 LMS | Removed 48 hour restriction for live proctoring + bulk scheduling**
Instructors are now allowed to configure Live Proctoring with Bulk Scheduling without the mandatory 48-hour advance window.
When Bulk Scheduling is selected, the Save button remains enabled regardless of how soon the quiz begins.
The 48-hour validation continues to apply for **Self** and **Drive** scheduling types.
5. **Moodle 4.5 LMS | Removed time limit validation for live proctoring + bulk scheduling**
The formerly mandatory Time Limit field is no longer required for Bulk Scheduling scenarios, and instructors can save proctoring settings without specifying a duration.
The Time Limit requirement continues to apply for **Self** and **Drive** scheduling types.
### **Bug Fixes**
1. **Moodle 4.5 LMS | Resolved post-review looping issue in Secure Browser.**
After completing and reviewing a quiz launched in Secure Browser without proctoring configured, students will now be redirected to the course page instead of being redirected back into the same quiz.
2. **Incorrect message shown upon accessing an expired proview wrapper link**
Previously, when one would access an expired proview wrapper link, an incorrect error message would appear, stating: “Invalid verification code”. This has now been updated to notify the status of the wrapper link correctly.
# October 2025 Release Updates
Source: https://docs.talview.com/releasenotes/q4-2025/release-notes-oct-2025
We’re excited to share our October 2025 updates! This release focuses on **AI-powered evaluation enhancements**, **workflow automation**, **external assessment integration**, and **scheduling improvements** - all designed to improve speed, visibility, and efficiency for recruiters, evaluators, and candidates.
***
## 🛠️ Workflow Tools Enhancements
### Ivy Playback View with Scores
Evaluators can now review candidate responses and scores within a unified Ivy Playback interface. This includes:
* Seamless playback of candidate recordings
* Inline scoring fields
* Streamlined navigation for faster evaluations
**Check it out here:**
***
### Ivy Summary View
Recruiters and hiring managers can now see **AI-generated summaries** of Ivy interviews, highlighting:
* Key conversation themes
* Candidate strengths
* Areas for improvement
This accelerates decision-making without the need to replay full interviews.
**Check it out here:**
***
### Public Registration Workflows
Recruiters can now:
* Open workflows for **public candidate registration** via a unique link or QR code
* Close or reopen registrations anytime to manage volume and control flow
This enables **self-registration**, eliminates manual entry, and improves onboarding visibility.
**Check it out here:**
***
## 📲 Scheduling Enhancements
### Guest Interviewer Scheduling (Whitelisted Domains)
Recruiters can now schedule interviews with **external evaluators** using approved domains. Features include:
* Auto-creation of guest profiles
* Calendar invites with secure access
* View of candidate profiles and comment-based evaluations
***
### Automated Scheduler Selection
When using Intelligent Scheduler:
* **“Notify Everyone” enabled** → triggers intelligent notifications to all participants
* **Disabled** → defaults to regular scheduler (no alerts)
***
### Resume Access in Scheduling Emails
Evaluators can now **view candidate resumes directly** from interview invite emails, improving pre-interview preparation without needing platform logins.
**Check it out below:**
***
## 🧑💼 Interview Rooms Enhancements
### Auto-Trigger 360° Environment Scan + Secondary Camera \[Alpha]
* Auto-launch of candidate verification steps (360° scan + secondary camera)
* Improves session readiness and reduces setup delays
***
### Integrated Evaluation in Interview Rooms \[Alpha]
* Evaluations can now be tracked directly in Interview Rooms for interviews scheduled via Workflow Tools
* Enables consistent feedback capture without switching tools
***
## 📊 Assessment Engine Updates
### Ivy Report Enhancements
The Ivy Report now includes:
* AI-generated conversation summary
* Candidate strengths, concerns, and communication style
* Final evaluation notes
This provides full context in a single view — no replays required.
***
## 🔐 Proctoring Enhancements
### Secure Browser Blocklist Updates
New applications added to the blocklist:
* **Windows**: TechSmith Relay Recorder
* **macOS**: Camtasia, Icecream Screen Recorder
Also, **.exe download instructions** on Talview pages are now less prominent.
***
## ⚙️ LMS Integrations (Browser Extension v1.5.0)
### Totara LMS Integration with Proctoring
Proview Proctoring is now fully integrated with Totara LMS:
* **Configure proctoring for SCORM**
* **View session recordings**
* **Candidates can attempt proctored SCORM packages**
***
### Moodle LMS 4.5 – Secure Browser Support
Coordinators can now enable **Secure Browser** for quizzes **without selecting a proctoring type** in Moodle 4.5.
***
### AU Region Support for Browser Extension
Proview browser extension now supports **Australia (AU) region deployments**, enabling use for partners like **La Trobe University**.
***
## 🧾 Payment Enhancements
### Invoice Updates
Invoices now include the **company name in billing details**, simplifying reimbursement processes for candidates.
***
Thanks for reading the **October 2025 release notes**!
# Form
Source: https://docs.talview.com/sdk/forms
Dynamic form loading and submission with the Proview SDK
## What is Form module
The Form module is part of the Proview SDK, exposed as `Proview.form`. It provides a complete solution for loading, rendering, and managing dynamic forms with integrated authentication.
Once initialized, it lets your application:
* **Load forms** — render forms dynamically by form ID.
* **Submit forms** — handle form submission and validation automatically.
* **Mount UI** — display forms in `sidepanel`, `popup`, or `inline` layout modes.
* **React to events** — subscribe to ready, submitted, and error events.
***
## Quickstart
### 1. Load the SDK
Ensure the Proview SDK script is loaded (see [Getting Started](/sdk/getting-started)).
```html theme={null}
```
### 2. Initialize credential
The SDK supports Firebase as a credentialing provider for authentication.
```javascript theme={null}
const firebaseCredential = Proview.auth.FirebaseAuthStrategy({
token: 'your-firebase-auth-token',
});
```
### 3. Initialize form module
Initialize the form module with the Firebase credential.
```javascript theme={null}
const form = Proview.form.init({
dsn: 'project-dsn',
projectId: 'project-123',
credential: firebaseCredential,
});
```
### 4. Access user object
Once initialized, the user object becomes available globally at `Proview.user` and is Firebase-compatible with `getIdToken()` method.
```javascript theme={null}
const user = Proview.user;
console.log(user.uid, user.email, user.displayName);
// Get ID token when needed
const idToken = await user.getIdToken();
```
### 5. Mount UI
Mount the form UI into a container element.
```javascript theme={null}
const mounted = form.mount({
formId: 'form-123',
containerId: 'form-container',
mountMode: {
mode: 'sidepanel', // or 'popup' or 'inline'
},
});
```
### 6. Open form
Open the form to load data and display the UI.
```javascript theme={null}
const formInstance = await form.open();
```
### 7. Subscribe to events
Listen to form lifecycle events.
```javascript theme={null}
formInstance
.on('ready', () => {
console.log('Form is ready for user input');
})
.on('submitted', () => {
console.log('Form submitted successfully');
})
.on('error', ({ message }) => {
console.error('Form error:', message);
});
```
### 8. Teardown
When done, unmount the UI.
```javascript theme={null}
mounted.unmount();
```
***
## API Reference
### `Proview.form.init(options)`
Creates a form module instance with integrated authentication.
**Input**
```javascript theme={null}
type FormInitOptions = {
dsn: string; // Required: Project DSN
projectId: string; // Required: Project ID
credential: Credential; // Required: Authentication credential (e.g., FirebaseAuthStrategy)
};
```
**Returns** — `FormModule`
```javascript theme={null}
type FormModule = {
mount(options: MountOptions): MountedFormUi;
open(): Promise;
};
```
The authenticated user is available globally at `Proview.user` after initialization.
***
### `form.mount(options)`
Mounts the form UI into a container element.
| | |
| ----------- | --------------- |
| **Input** | `MountOptions` |
| **Returns** | `MountedFormUi` |
**MountOptions**
```javascript theme={null}
type MountOptions = {
formId: string; // Required: Form ID to load
containerId: string; // Required: DOM element ID
mountMode: {
mode: 'sidepanel' | 'popup' | 'inline'; // Required: Layout mode
};
};
```
**MountedFormUi**
```javascript theme={null}
type MountedFormUi = {
unmount(): void; // Removes UI from DOM
};
```
**Example:**
```javascript theme={null}
const firebaseCredential = Proview.auth.FirebaseAuthStrategy({
token: 'your-firebase-auth-token',
});
const form = Proview.form.init({
dsn: 'project-dsn',
projectId: 'project-123',
credential: firebaseCredential,
});
const mounted = form.mount({
formId: 'form-123',
containerId: 'form-container',
mountMode: {
mode: 'popup',
},
});
// Later, when done
mounted.unmount();
```
***
### `form.open()`
Loads form data and displays the form UI. Uses the formId specified in mount().
| | |
| ----------- | ----------------------- |
| **Input** | None |
| **Promise** | `Promise` |
| **Async** | Yes, requires await |
**FormInstance**
```javascript theme={null}
type FormInstance = {
on(event: FormEventName, handler: (payload?: any) => void): FormInstance;
submit(): Promise;
};
```
**Example:**
```javascript theme={null}
const form = Proview.form.init({
dsn: 'project-dsn',
projectId: 'project-123',
credential: firebaseCredential,
});
form.mount({
formId: 'form-123',
containerId: 'form-container',
mountMode: { mode: 'sidepanel' },
});
const formInstance = await form.open();
formInstance
.on('ready', () => console.log('Form ready'))
.on('submitted', () => {
console.log('Form submitted');
// Handle success
})
.on('error', ({ message }) => {
console.error('Form error:', message);
});
```
***
## User Object
After initializing the form module, `Proview.user` provides a Firebase-compatible user object accessible globally.
**User Interface**
```javascript theme={null}
type User = {
uid: string; // User's unique ID
email: string | null; // User's email address
displayName: string | null; // User's display name
emailVerified: boolean; // Email verification status
isAnonymous?: boolean; // Is anonymous user
metadata?: UserMetadata; // Creation and last sign-in time
providerData?: ProviderData[]; // Provider-specific info
// Methods
getIdToken(forceRefresh?: boolean): Promise;
getIdTokenResult(forceRefresh?: boolean): Promise;
};
```
**Example:**
```javascript theme={null}
const firebaseCredential = Proview.auth.FirebaseAuthStrategy({
token: 'your-firebase-auth-token',
});
const form = Proview.form.init({
dsn: 'project-dsn',
projectId: 'project-123',
credential: firebaseCredential,
});
// Access user properties globally
const user = Proview.user;
console.log(user.uid);
console.log(user.email);
console.log(user.displayName);
console.log(user.emailVerified);
// Get ID token
const idToken = await user.getIdToken();
// Force refresh token
const freshToken = await user.getIdToken(true);
```
***
## Firebase Authentication
### `Proview.auth.FirebaseAuthStrategy(config)`
Creates a Firebase authentication credential for use with the Proview SDK modules.
**Input**
```javascript theme={null}
type FirebaseAuthStrategyConfig = {
token: string; // Required: Firebase authentication token
};
```
**Returns** — `FirebaseAuthStrategy`
A credential object that can be passed to any Proview SDK module initialization.
**Example:**
```javascript theme={null}
// Initialize Firebase credential with token
const firebaseCredential = Proview.auth.FirebaseAuthStrategy({
token: 'eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...',
});
// Use with form module
const form = Proview.form.init({
dsn: 'project-dsn',
projectId: 'project-123',
credential: firebaseCredential,
});
```
***
## Form Events
The `FormInstance` emits events that you can subscribe to using the `on()` method.
**Event names and payloads**
| Event | Payload | Description |
| ----------- | --------------------- | --------------------------- |
| `ready` | `void` | Form loaded and ready |
| `submitted` | `void` | Form submitted successfully |
| `error` | `{ message: string }` | Error occurred |
**Example:**
```javascript theme={null}
form
.on('ready', () => {
// Form is ready for input
})
.on('submitted', () => {
// Form was submitted successfully
})
.on('error', ({ message }) => {
// Handle form error
alert(`Error: ${message}`);
});
```
***
## Mount Modes
The form module supports three layout modes for the form UI.
| Mode | Value | Behavior |
| ------------- | ------------- | ------------------------------- |
| **Sidepanel** | `'sidepanel'` | Slides in from side of viewport |
| **Popup** | `'popup'` | Centered modal overlay |
| **Inline** | `'inline'` | Embedded in the page flow |
**Example:**
```javascript theme={null}
// Sidepanel mode
const mounted1 = form.mount({
formId: 'form-123',
containerId: 'form-container',
mountMode: {
mode: 'sidepanel',
},
});
// Popup mode
const mounted2 = form.mount({
formId: 'form-123',
containerId: 'form-container',
mountMode: {
mode: 'popup',
},
});
// Inline mode
const mounted3 = form.mount({
formId: 'form-123',
containerId: 'form-container',
mountMode: {
mode: 'inline',
},
});
```
***
## Error Handling
Form errors follow a consistent structure.
**Error Structure**
```javascript theme={null}
type FormError = {
code: string; // Error code for programmatic handling
message: string; // Human-readable error message
};
```
**Common Error Codes**
| Code | Description |
| ----------------- | ------------------------------- |
| `FORM_LOAD_ERROR` | Failed to load form |
| `PANEL_ERROR` | Panel rendering error |
| `TOKEN_INVALID` | Authentication token is invalid |
| `TOKEN_EXPIRED` | Session token expired |
| `AUTH_FAILED` | Authentication failed |
| `FETCH_FAILED` | Network or API request failed |
**Example:**
```javascript theme={null}
try {
const firebaseCredential = Proview.auth.FirebaseAuthStrategy({
token: 'your-firebase-auth-token',
});
const form = Proview.form.init({
dsn: 'project-dsn',
projectId: 'project-123',
credential: firebaseCredential,
});
const mounted = form.mount({
formId: 'form-123',
containerId: 'form-container',
mountMode: {
mode: 'popup',
},
});
const formInstance = await form.open();
formInstance.on('error', ({ message }) => {
console.error('Form error:', message);
// Handle error in UI
});
} catch (error) {
switch (error.code) {
case 'AUTH_FAILED':
alert('Authentication failed. Please log in again.');
break;
case 'TOKEN_INVALID':
alert('Invalid authentication token.');
break;
case 'TOKEN_EXPIRED':
alert('Session expired. Please log in again.');
break;
case 'FORM_LOAD_ERROR':
alert('Failed to load form. Please try again.');
break;
case 'PANEL_ERROR':
alert('Failed to render form panel. Check your page setup.');
break;
case 'FETCH_FAILED':
alert('Network error. Please check your connection.');
break;
default:
alert(`Error: ${error.message}`);
break;
}
}
```
# Getting Started
Source: https://docs.talview.com/sdk/getting-started
Welcome to the Proview SDK. Follow these steps to embed the latest SDK in your application.
## Prerequisites
* Talview-provisioned tenant + project DSN (customer success or [Talview Sales](https://www.talview.com/request-a-demo) can help).
* Modern browser with WebRTC support and HTTPS hosting for your delivery app.
* Ability to add a script tag and a small bootstrap snippet wherever proctoring needs to run.
### Content Security Policy (CSP)
If your application enforces CSP headers, allow the domains and inline resources required by the SDK:
```
Content-Security-Policy:
script-src 'unsafe-inline' https://*.tlv.io;
style-src 'unsafe-inline';
connect-src 'self' https://*.googleapis.com https://*.tlv.com wss://*.tlv.com https://*.talview.com wss://*.talview.com;
img-src 'self' https://*.tlv.io;
```
## Installation
### Script tag
Place the loader as the **last script** on any page that needs Proview SDK. The loader attaches itself globally as `window.Proview`.
```html theme={null}
```
## Initialize
Define `window.proviewOnLoad` before loading the script. The SDK fires this callback when it is ready. Call `Proview.init` inside the callback to bootstrap the SDK.
```html theme={null}
```
## Interfaces
The Proview SDK is composed of the following modules:
* `form` – enables dynamic form loading and submission with integrated authentication. See the [Form](/sdk/forms) guide for details.
* `scheduler` – manages interview scheduling, RSVP, and availability with integrated authentication. See the [Scheduler](/sdk/scheduler) guide for complete API reference.
* `session` – enables remote proctoring with session management, media capture, and real-time monitoring. See the [Proctoring](/sdk/proctoring/getting-started) guide for complete setup instructions.
* `session-playback` – enables embedding and playback of recorded proctoring sessions. See the [Session Playback](/sdk/session-playback/getting-started) guide for integration details.
## Global Error Handling
Register a global error hook after the loader runs to observe failures from any Proview module:
```js theme={null}
Proview.onError((module, error) => {
if (module === 'form') {
console.error('Form module failed', error);
} else if (module === 'scheduler') {
console.error('Scheduler module failed', error);
} else if (module === 'proctoring') {
console.error('Proctoring module failed', error);
} else {
console.error(`Module ${module} failed`, error);
}
});
```
# Best Practices
Source: https://docs.talview.com/sdk/proctoring/best-practices
Recommended practices for implementing the Proview SDK effectively and securely
This guide outlines recommended practices for implementing the Proview SDK to ensure optimal performance, reliability, and user experience.
## Error Handling
**Important:** When errors thrown by callback functions are not handled by the parent application, Proview will swallow these errors to prevent disruption of the SDK's core functionality. Always implement proper error handling within your callback functions.
### Callback Error Management
When implementing callback functions for session hooks or API methods, always include proper error handling:
```jsx theme={null}
// Good - Handle errors in callbacks
Proview.session.onSessionPause("User requested break", function (sessionStateOutput, err) {
try {
if (err) {
console.error('Hook error:', err);
return;
}
console.log('Session paused. Reason:', sessionStateOutput.reason);
console.log('Session state:', sessionStateOutput.state);
// Your custom logic here
saveUserProgress();
showPauseUI();
} catch (error) {
console.error('Error in pause handler:', error);
// Handle the error appropriately
}
});
// Bad - Unhandled errors
Proview.session.onSessionPause("User requested break", function (sessionStateOutput, err) {
// If this throws an error, Proview will swallow it
riskyOperation(); // Could throw an error
});
```
### Global Error Handler
Register a global error handler to catch SDK-level errors:
```jsx theme={null}
Proview.onError((err) => {
console.error('Proview SDK Error:', err);
// Log to your monitoring system
if (err.type === 'critical') {
logCriticalError(err);
}
// Show user-friendly message for critical errors
if (err.type === 'critical') {
showUserNotification('A technical issue occurred. Please contact support.');
}
});
```
# Event Callbacks
Source: https://docs.talview.com/sdk/proctoring/callbacks
The SDK supports several lifecycle callbacks to handle different events:
### onConnected
Called when the proctoring session successfully connects.
```javascript theme={null}
callbacks: {
onConnected: (api) => {
console.log('Session connected');
// api object provides additional methods (implementation pending)
}
}
```
### onDisconnected
Called when the proctoring session disconnects.
```javascript theme={null}
callbacks: {
onDisconnected: () => {
console.log('Session disconnected');
// Handle disconnection logic
}
}
```
### onError
Called when an error occurs during the proctoring session.
```javascript theme={null}
callbacks: {
onError: (error) => {
console.error('Proctoring error:', error);
// Handle error logic
}
}
```
### Complete Callback Example
```javascript theme={null}
const config = {
projectSecret: 'your-project-secret',
candidate: {
externalId: 'candidate-123'
},
workflow_step: {
proctoringType: 'remote_invigilation'
},
callbacks: {
onConnected: (api) => {
console.log('✅ Proctoring session started');
// Show success message to user
document.getElementById('status').textContent = 'Proctoring Active';
},
onDisconnected: () => {
console.log('❌ Proctoring session ended');
// Update UI to reflect disconnected state
document.getElementById('status').textContent = 'Proctoring Inactive';
},
onError: (error) => {
console.error('🚨 Proctoring error:', error);
// Show error message to user
alert('Proctoring error: ' + error.message);
}
}
};
```
# Interfaces
Source: https://docs.talview.com/sdk/proctoring/configuration
The Proview SDK composed of the following modules:
* root: the global module that exposes initialization, global configuration, and other cross-cutting or non‑module-specific features.
* session: the module that manages proctored session lifecycle operations such as register, start, stop, and complete.
## Global Module:
### init
The Proview root module is added via a loader script or imported. Proview becomes usable only after initialization using `Proview.session.init(initOptions)`. The `options ` parameter is a configuration object .
**Function Type:** Synchronous
Only when the Proview root module is initialized, other features and modules are accessible.
```jsx theme={null}
function session.init(initOptions: InitOptions): void;
```
| Attribute | Type | Description | Default |
| ---------------- | ----------------------- | ----------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
| dsn | `string` | The DSN tells the SDK where to send the events. If this is not set, the SDK will not send any events. | |
| container\_id | `string` | The ID of the HTML element where the Proview SDK will be rendered. | |
| identifier\* | `string` | Value that can identify the proctored session in the source platform. | |
| attendee\* | `Attendee` | Attendee object containing candidate details. See [Attendee Attributes](#attendee-attributes). | |
| workflow\_step\* | `Workflow` | Workflow object containing exam/workflow details. See [Workflow](#workflow). | |
| limit\_languages | `[locale.languages]`\[] | This will limit language options for users to select from the supported list | All supported languages |
| language | `string` | Explicitly set the SDK language | Browser default if its not supported then fallback to English (`en-US`). |
### onError
Register a global error handler to receive notifications whenever the SDK encounters an error or warning. Proview supports only a single handler — registering a new handler replaces the previously registered one.
**Function Type:** Asynchronous\
**Input:** A function that receives an error object as parameter describing the problem and returns void. Any error in error handler will be logged in console but not be escalated.
```jsx theme={null}
function onError(errorHandler: ErrorObject): void;
```
| Attribute | Type | Description | Default |
| ---------------- | ------------------- | -------------------------------------------------------------------------------------------------------------------------- | ------- |
| code | `string` | This will identify predefined error by code. Ref Error Code section | |
| message | `string` | Message will contain reason for the error. | |
| type | `enum` | Error could be of type warning or critical. When critical error is raised it will impact core proctoring feature delivery. | |
| validationErrors | `validationError[]` | | |
```jsx theme={null}
```
### getLanguages
Get all supported language codes.
Language code in [BCP‑47](https://developer.mozilla.org/en-US/docs/Glossary/BCP_47_language_tag) format
(examples: "en", "en-US", "fr", "fr-CA"). The language subtag typically follows [ISO 639-1](https://en.wikipedia.org/wiki/ISO_639-1) (e.g., "en"), and the optional region subtag follows [ISO 3166-1 Alpha-2](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2) (e.g., "US").
**Function Type:** Synchronous
```jsx theme={null}
function getLanguages(): string[];
```
### setLanguage
Set the SDK’s language/locale used for localization (UI text, formatting hints, etc.).
Accepts a language tag in [BCP‑47](https://developer.mozilla.org/en-US/docs/Glossary/BCP_47_language_tag) format (examples: "en", "en-US", "fr", "fr-CA"). The language subtag typically follows [ISO 639-1](https://en.wikipedia.org/wiki/ISO_639-1) (e.g., "en"), and the optional region subtag follows [ISO 3166-1 Alpha-2](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2) (e.g., "US").
**Fallback rules**
* If the provided language tag is supported, the SDK applies it and returns the applied tag.
* If the provided dialect/region is not supported but the base language is, the SDK falls back to an available variant for that language (for example, "en-GB" → "en").
* If the provided language is not supported at all, the SDK attempts to fall back to the browser default locale (if available).
* If no suitable browser default is available, the SDK falls back to English ("en").
* The function updates the SDK’s language setting immediately and returns the effective language code.
**Function Type:** Synchronous\
**Input:** language code
```jsx theme={null}
function setLanguage(language: string): string;
```
```jsx theme={null}
// Set French (generic)
const applied = Proview.locale.setLanguage('fr');
console.log('Language set to:', applied); // e.g. "fr"
// Set English (United States)
Proview.locale.setLanguage('en-US');
// If unsupported, SDK falls back (browser default or 'en')
const applied2 = Proview.locale.setLanguage('xx-YY');
console.log(applied2); // e.g. "en" or browser default
```
[//]: # "### limitLanguages"
[//]: #
[//]: # "Limit which languages the SDK will offer or accept. Use this to restrict available languages to a specific subset required by your application."
[//]: #
[//]: # "- After calling this function, the SDK will only permit languages in the provided list. Any attempts to set or infer a language that is not in the allowed list will result in a fallback (for example, to the browser default or to a configured default)."
[//]: # "- Call this early (typically during initialization) to ensure the SDK does not briefly expose unsupported languages."
[//]: #
[//]: # "**Function Type:** Synchronous "
[//]: # "**Input:** An array of language identifiers (either BCP‑47 strings like \"en-US\" / \"fr\" or constants from Proview.Constant.Language)."
[//]: #
[//]: #
[//]: # "```jsx"
[//]: # "function limitLanguages(languages: string[]): void;"
[//]: # "```"
[//]: #
[//]: # ""
[//]: # " "
[//]: # " ```jsx"
[//]: # " Proview.locale.limitLanguages(['fr', 'en-us']);"
[//]: # " ```"
[//]: # " "
[//]: # ""
### getAttendee
Retrieve current attendee attributes.
**Function Type:** Synchronous
```jsx theme={null}
function getAttendee(): Attendee | undefined ;
```
| Attribute | Type | Description | Default |
| ------------- | ------------- | --------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
| identifier\* | `string` | unique user identifier from the source system. It will be the external id in the Talview platform. | |
| first\_name | `string` | First name of the attendee/candidate | |
| last\_name | `string` | Last name of the attendee/candidate | |
| middle\_name | `string` | Middle name of the attendee/candidate | |
| email | `string` | Email address of the attendee/candidate | If not passed then system will generate email based on identifier. e.g: [Att0001@dnd.talview.com](mailto:Att0001@dnd.talview.com) |
| country\_code | `string (3)` | [ISO country code](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-3#Officially_assigned_code_elements) | |
| country | `string` | Country code is passed then system will auto identify the country otherwise system will identify country code from country. | |
| phone | `string (15)` | E164 format phone number of the attendee/candidate | |
| id | `int` | Talview unique id generated for the course | |
```jsx theme={null}
// Get the current attendee information
const attendee = Proview.getAttendee();
if (attendee) {
console.log('Attendee identifier:', attendee.identifier);
console.log('Full name:', `${attendee.first_name} ${attendee.last_name}`);
console.log('Email:', attendee.email);
console.log('Country:', attendee.country);
console.log('Phone:', attendee.phone);
} else {
console.log('No attendee information available');
}
```
### getWorkflow
Retrieve the current workflow attributes used by the SDK.
* Call this after the Proview root module has been initialized and any workflow has been configured or loaded.
* If no workflow is set, the function may return null or undefined — handle that case in your code.
**Function Type:** Synchronous
```jsx theme={null}
function getWorkflow(): Workflow | undefined;
```
| Attribute | Type | Description | Default |
| ------------ | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------ |
| identifier\* | `string` | Unique identifier for the exam from the calling application. It will be the external id in the Talview platform. | |
| name | `string` | Name of the exam | If name is not passed then external id will be used. |
| flow\_id | `int` | This is the proctor session onboarding flow identifier. | if not passed then detail flow will be mapped based on project DSN |
| flow\_uuid | `string` | Proctoring configuration identifier for the provided `dsn`. If the workflow step is already created with a flow, this will not override it. | |
| duration | `int` | duration of the exam in min | |
| resource | `[{string,string}]` | Array of key value pair to persist additional info related to exam. | |
| course | `[Course]` | | |
| id | `int` | Talview unique id generated for the course | |
```jsx theme={null}
// Get the current workflow information
const workflow = Proview.getWorkflow();
if (workflow) {
console.log('Workflow identifier:', workflow.identifier);
console.log('Workflow name:', workflow.name);
console.log('Duration:', workflow.duration);
} else {
console.log('No workflow information available');
}
```
### getLocale
Returns the SDK's current locale as an object with language, timezone, and currency. The timezone and currency fields are used only for scheduling- and payment-related features which will be supported in furture.
**Function Type:** Synchronous
```jsx theme={null}
function getLocale(): Locale
```
| Attribute | Type | Description | Default |
| ------------ | -------- | ---------------------------------------------------------- | --------------------- |
| language | `string` | Language code in BCP-47 format (e.g., "en", "en-US", "fr") | based on browser info |
| ~~currency~~ | `string` | ISO 4217 currency codes | based on browser info |
| ~~timezone~~ | `string` | Timezone | based on browser info |
### getVersion
Return the SDK's current version string. The SDK follows Semantic Versioning: Major,Minor,Patch. If you only need the version after initialization, call it after Proview\.session.init.
**Function Type:** Synchronous
**Output:** string (Semantic Versioning, e.g. "1.2.3").
```jsx theme={null}
function getVersion(): String ;
```
## Session Module
### getState
Return the current state of the proctoring session.
**Function Type:** Synchronous
```jsx theme={null}
function getState(): SessionState ;
```
Its of type enum which contains following values.
* `INITIALISED`
* `ONBOARDING_IN_PROGRESS`
* `MONITORING_IN_PROGRESS`
* `PAUSED`
* `SUSPENDED`
* `STOPPED`
* `COMPLETED`
* `TERMINATED`
### register
Register attendee and workflow with the backend.You can optionally call register beforehand to optimize the workflow and improve overall process performance.
**Function Type:** Asynchronous
```jsx theme={null}
function register(callback: (sessionOutput: SessionOutput | null, err: Error | null) => void): void;
```
| Attribute | Type | Description | Default |
| -------------- | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
| uuid | `GUID` | Reference Talview identifier for client application to track. | |
| state | `session.states` | Current state of the session (INITIALISED, ONBOARDING\_IN\_PROGRESS, MONITORING\_IN\_PROGRESS, PAUSED, SUSPENDED, STOPPED, COMPLETED, TERMINATED) | |
| attendee | `Attendee` | Object containing attendee information | |
| workflow\_step | `Workflow` | Object containing workflow information | If not passed then system will generate email based on identifier. e.g: [Att0001@dnd.talview.com](mailto:Att0001@dnd.talview.com) |
| identifier | `string` | unique session identifier from the source system. It will be the session external id in the Talview platform. | |
[//]: # "### registerHook"
[//]: #
[//]: # "Register an event listener for specific session events. This allows you to execute custom code when certain session state changes or events occur during the proctoring workflow."
[//]: #
[//]: # "**Function Type:** Synchronous"
[//]: #
[//]: # "**Input:**"
[//]: # "- hookType: The type of hook to register (e.g., `Proview.Hooks.onRegister`, `Proview.Hooks.onSessionStateChange`)"
[//]: #
[//]: # "```jsx"
[//]: # "function registerHook(hookType: HookType, callback: Function): void;"
[//]: # "```"
[//]: # ""
[//]: # " "
[//]: #
[//]: # " ```jsx"
[//]: # " try {"
[//]: # " Proview.session.registerHook(Proview.Hooks.onSessionPause, function (sessionStateOutput) {"
[//]: # " console.log('Session paused. Reason:', sessionStateOutput.reason);"
[//]: # " console.log('Session state:', sessionStateOutput.state);"
[//]: # " });"
[//]: # " }"
[//]: # " catch (error) {"
[//]: # " console.error('Failed to register hooks:', error);"
[//]: # " }"
[//]: # " ```"
[//]: #
[//]: # " "
[//]: # ""
### start
Begin the proctoring session for the configured attendee and workflow. This starts whatever proctoring mode was requested (for example, recorded or live).
* The Proview root module must be initialized.
* Either an attendee (or attendee identifier) and workflow (or workflow identifier) must be set or the session must already be in registered state. If required identifiers are missing, the call will fail.
* If `register` is not called beforehand, it will be executed as part of the start process.
**Function Type:** Asynchronous
[//]: # "**Error / Warning Codes:**"
[//]: #
[//]: # "- PV/Common/Err0001 - Unable to connect to server, Could be internet connection or network block (restricted office environment)."
[//]: # "- PV/Validation/Err00001 - Missing Required field"
[//]: # "- PV/Validation/Err00002 - Invalid type"
```jsx theme={null}
function start(): Promise;
//or
function start(callback: (sessionOutput: SessionOutput, error: Error) => void): void;
```
| Attribute | Type | Description | Default |
| -------------- | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
| uuid | `GUID` | Reference Talview identifier for client application to track. | |
| state | `session.states` | Current state of the session (INITIALISED, ONBOARDING\_IN\_PROGRESS, MONITORING\_IN\_PROGRESS, PAUSED, SUSPENDED, STOPPED, COMPLETED, TERMINATED) | |
| attendee | `Attendee` | Object containing attendee information | |
| workflow\_step | `Workflow` | Object containing workflow information | If not passed then system will generate email based on identifier. e.g: [Att0001@dnd.talview.com](mailto:Att0001@dnd.talview.com) |
| identifier | `string` | unique session identifier from the source system. It will be the session external id in the Talview platform. | |
[//]: # ""
[//]: # " "
[//]: # " | Attribute | Type | Description | Default |"
[//]: # " | --- | --- | --- | --- |"
[//]: # " | attendee_identifier | `string` | Value that can identify the user in the source platform. | |"
[//]: # " | workflow_identifier | `string` | Value that can identify the exam in the source platform. | |"
[//]: # " | session_identifier | `string` | Value that can identify the proctored session in the source platform. If not passed will use workflow_identifier as default. | |"
[//]: # " | type | `string` | The type of the Proctored Session | |"
[//]: # " | durtion | `number` | Total allotted time (In minutes) for the proctored session. . | |"
[//]: # " | remaining_duration | `number` | Remaining time for(In minutes) the ongoing proctored session. | |"
[//]: # " "
[//]: # ""
| Attribute | Type | Description | Default |
| ---------------- | ------------------- | -------------------------------------------------------------------------------------------------------------------------- | ------- |
| code | `string` | This will identify predefined error by code. Ref Error Code section | |
| message | `string` | Message will contain reason for the error. | |
| type | `enum` | Error could be of type warning or critical. When critical error is raised it will impact core proctoring feature delivery. | |
| validationErrors | `validationError[]` | | |
```jsx theme={null}
Proview.session.start((sessionOutput, err)=>{
if (err) {
console.error('Failed to start session:', err);
return;
}
console.log('Session state:', sessionOutput.state);
console.log('Session uuid:', sessionOutput.uuid);
});
// or
try
{
const sessionOutput = await Proview.session.start();
} catch (err) {
console.error('Failed to start session:', err);
}
```
### stop
Stop the currently active proctoring session. If no session is active, the call will fail with an error.
* Attempts to stop the active session on the server and update the SDK’s session state ("stopped").
* If no session is currently active, the call rejects or returns an error indicating that there is no session to stop.
* Perform any necessary cleanup or finalization needed (stop recording, flush artifacts, etc.) as part of stopping the session.
**Function Type:** Asynchronous
```jsx theme={null}
function stop(): Promise;
//or
function stop(callback: (sessionOutput: SessionOutput | null, err: Error | null) => void): void;
```
[//]: # "**Error / Warning Codes:**"
[//]: #
[//]: # "- PV/Common/Err00002 - Operation not allowed. In this case stop is not support since the session is not running."
| Attribute | Type | Description | Default |
| -------------- | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
| uuid | `GUID` | Reference Talview identifier for client application to track. | |
| state | `session.states` | Current state of the session (INITIALISED, ONBOARDING\_IN\_PROGRESS, MONITORING\_IN\_PROGRESS, PAUSED, SUSPENDED, STOPPED, COMPLETED, TERMINATED) | |
| attendee | `Attendee` | Object containing attendee information | |
| workflow\_step | `Workflow` | Object containing workflow information | If not passed then system will generate email based on identifier. e.g: [Att0001@dnd.talview.com](mailto:Att0001@dnd.talview.com) |
| identifier | `string` | unique session identifier from the source system. It will be the session external id in the Talview platform. | |
| Attribute | Type | Description | Default |
| ---------------- | ------------------- | -------------------------------------------------------------------------------------------------------------------------- | ------- |
| code | `string` | This will identify predefined error by code. Ref Error Code section | |
| message | `string` | Message will contain reason for the error. | |
| type | `enum` | Error could be of type warning or critical. When critical error is raised it will impact core proctoring feature delivery. | |
| validationErrors | `validationError[]` | | |
```jsx theme={null}
Proview.session.stop((sessionOutput, err) => {
if (err) {
console.error('Failed to stop session:', err);
return;
}
console.log('Session state:', sessionOutput.state);
});
// or
try {
const sessionOutput = await Proview.session.stop();
console.log('Session state:', sessionOutput.state);
} catch (err) {
console.error('Failed to stop session:', err);
}
```
### complete
Mark the current proctoring session as completed. Completion is an end state — Session that are not in end state can be marked as completed, completed sessions cannot be restarted or resumed for proctoring
* Transitions the session to the "completed" state on the server and updates the SDK state locally.
* Once completed, the session is final and cannot be started or resumed.
* If the session is scheduled then it will be auto completed at the session end time + buffer time
* The call should be idempotent: repeated attempts to complete an already-completed session should either succeed silently.
* Perform any finalization needed (e.g., flush pending artifacts, stop recordings) before calling complete to ensure all data is preserved and release device connection and access.
**Function Type:** Asynchronous
```jsx theme={null}
function complete(callback:(sessionOutput: SessionOutput | null, err: Error | null) => void): void;
```
| Attribute | Type | Description | Default |
| -------------- | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
| uuid | `GUID` | Reference Talview identifier for client application to track. | |
| state | `session.states` | Current state of the session (INITIALISED, ONBOARDING\_IN\_PROGRESS, MONITORING\_IN\_PROGRESS, PAUSED, SUSPENDED, STOPPED, COMPLETED, TERMINATED) | |
| attendee | `Attendee` | Object containing attendee information | |
| workflow\_step | `Workflow` | Object containing workflow information | If not passed then system will generate email based on identifier. e.g: [Att0001@dnd.talview.com](mailto:Att0001@dnd.talview.com) |
| identifier | `string` | unique session identifier from the source system. It will be the session external id in the Talview platform. | |
| Attribute | Type | Description | Default |
| ---------------- | ------------------- | -------------------------------------------------------------------------------------------------------------------------- | ------- |
| code | `string` | This will identify predefined error by code. Ref Error Code section | |
| message | `string` | Message will contain reason for the error. | |
| type | `enum` | Error could be of type warning or critical. When critical error is raised it will impact core proctoring feature delivery. | |
| validationErrors | `validationError[]` | | |
```jsx theme={null}
Proview.session.complete((sessionOutput, err) => {
if (err) {
console.error('Failed to complete session:', err);
return;
}
console.log('Session state:', sessionOutput.state);
});
// or
try {
const sessionOutput = await Proview.session.complete({
score: 87,
finishedAt: new Date().toISOString()
});
console.log('Session state:', sessionOutput.state); // "completed"
} catch (err) {
console.error('Failed to complete session:', err);
}
```
### pause
This will allow application to pause running proctored session.
**Function Type:** Asynchronous
**Input:** reason a string value, Void function that takes Session State, uuid (Proview session unique ID) and Error as parameter.
```jsx theme={null}
function pause(reason: string, callback: (output: sessionStateOutput, err: Error | null) => void): void;
```
```jsx theme={null}
SessionStateOutput = {
state: Session State
reason: string
}
```
Session State is of type enum which contains following values.
* `INITIALISED`
* `ONBOARDING_IN_PROGRESS`
* `MONITORING_IN_PROGRESS`
* `PAUSED`
* `SUSPENDED`
* `STOPPED`
* `COMPLETED`
* `TERMINATED`
```jsx theme={null}
// Pause the current proctoring session
Proview.session.pause("User requested break", (sessionStateOutput, err) => {
if (err) {
console.error('Failed to pause session:', err);
return;
}
console.log('Session paused:', sessionStateOutput.state); // "paused"
});
```
### resume
This will allow application to resume a paused proctored session.
**Function Type:** Asynchronous
**Input:** reason a string value, Void function that takes Session State Output, uuid (Proview session unique ID) and Error as parameter.
```jsx theme={null}
function resume(reason: string, callback: (output: sessionStateOutput, err: Error | null) => void): void;
```
```jsx theme={null}
SessionStateOutput = {
state: Session State
reason: string
}
```
Session State is of type enum which contains following values.
* `INITIALISED`
* `ONBOARDING_IN_PROGRESS`
* `MONITORING_IN_PROGRESS`
* `PAUSED`
* `SUSPENDED`
* `STOPPED`
* `COMPLETED`
* `TERMINATED`
**Client Usage (Function):**
```jsx theme={null}
// Promise-based
try {
const sessionOutput = await Proview.session.resume("Break time over");
console.log('Session resumed:', sessionOutput.state);
} catch (err) {
console.error('Failed to resume session:', err);
}
// Callback-based
Proview.session.resume("Break time over", (sessionStateOutput, err) => {
if (err) {
console.error('Failed to resume session:', err);
return;
}
console.log('Session resumed:', sessionStateOutput.state);
});
```
[//]: # "### suspend"
[//]: #
[//]: # "This will allow application to suspend a started session that is not completed/terminated."
[//]: #
[//]: # "**Function Type:** Asynchronous"
[//]: #
[//]: # "**Input:** reason a string value, Void function that takes Session State Output, uuid (Proview session unique ID) and Error as parameter."
[//]: #
[//]: # "```jsx"
[//]: # "function suspend(reason: string, callback: (output: sessionStateOutput, err: Error | null) => void): void;"
[//]: # "```"
[//]: #
[//]: # ""
[//]: # " "
[//]: #
[//]: # " ```jsx"
[//]: # " SessionStateOutput = {"
[//]: # " state: Session State"
[//]: # " reason: string"
[//]: # " }"
[//]: #
[//]: # " ```"
[//]: # " Session State is of type enum which contains following values."
[//]: #
[//]: # " - `init`"
[//]: # " - `registered`"
[//]: # " - `running`"
[//]: # " - `paused`"
[//]: # " - `suspended`"
[//]: # " - `terminated`"
[//]: # " - `stopped`"
[//]: # " - `completed`"
[//]: #
[//]: # " "
[//]: # ""
[//]: #
[//]: # ""
[//]: # " "
[//]: #
[//]: # " **Client Usage (Function):**"
[//]: # " ```jsx"
[//]: # " // Promise-based"
[//]: # " try {"
[//]: # " const sessionOutput = await Proview.session.suspend(\"Violation detected\");"
[//]: # " console.log('Session suspended:', sessionOutput.state);"
[//]: # " } catch (err) {"
[//]: # " console.error('Failed to suspend session:', err);"
[//]: # " }"
[//]: #
[//]: # " // Callback-based"
[//]: # " Proview.session.suspend(\"Violation detected\", (sessionStateOutput, err) => {"
[//]: # " if (err) {"
[//]: # " console.error('Failed to suspend session:', err);"
[//]: # " return;"
[//]: # " }"
[//]: # " console.log('Session suspended:', sessionStateOutput.state);"
[//]: # " });"
[//]: # " ```"
[//]: #
[//]: # " "
[//]: # ""
[//]: #
[//]: # "### terminate"
[//]: #
[//]: # "This will allow application to suspend a started session that is not completed."
[//]: #
[//]: # "**Function Type:** Asynchronous"
[//]: #
[//]: # "**Input:** reason a string value, Void function that takes Session State Output, uuid (Proview session unique ID) and Error as parameter."
[//]: #
[//]: # "```jsx"
[//]: # "function terminate(reason: string, callback: (output: sessionStateOutput, err: Error | null) => void): void;"
[//]: # "```"
[//]: #
[//]: # ""
[//]: # " "
[//]: #
[//]: # " ```jsx"
[//]: # " SessionStateOutput = {"
[//]: # " state: Session State"
[//]: # " reason: string"
[//]: # " }"
[//]: #
[//]: # " ```"
[//]: # " Session State is of type enum which contains following values."
[//]: #
[//]: # " - `init`"
[//]: # " - `registered`"
[//]: # " - `running`"
[//]: # " - `paused`"
[//]: # " - `suspended`"
[//]: # " - `terminated`"
[//]: # " - `stopped`"
[//]: # " - `completed`"
[//]: #
[//]: # " "
[//]: # ""
# Session Hooks
Session hooks allow you to register event listeners that get triggered when specific session state changes occur. Use the simple `Proview.session.on()` syntax to listen for events.
```jsx theme={null}
Proview.session.on(eventName, callback);
```
### Pause
Triggered when a proctoring session is paused.
```jsx theme={null}
Proview.session.on('Pause', (sessionStateOutput) => {
// Handle session pause
});
```
```jsx theme={null}
Proview.session.on('Pause', (sessionStateOutput) => {
console.log('Session paused:', sessionStateOutput.state);
console.log('Pause reason:', sessionStateOutput.reason);
});
```
```jsx theme={null}
SessionStateOutput = {
state: SessionState,
reason: string
}
```
**Session State** enum values:
* `INITIALISED` - Session initialized
* `ONBOARDING_IN_PROGRESS` - Onboarding in progress
* `MONITORING_IN_PROGRESS` - Monitoring in progress
* `PAUSED` - Session paused
* `SUSPENDED` - Session suspended
* `STOPPED` - Session stopped
* `COMPLETED` - Session completed
* `TERMINATED` - Session terminated
### Resume
Triggered when a paused proctoring session is resumed.
```jsx theme={null}
Proview.session.on('Resume', (sessionStateOutput) => {
// Handle session resume
});
```
```jsx theme={null}
Proview.session.on('Resume', (sessionStateOutput) => {
console.log('Session resumed:', sessionStateOutput.state);
console.log('Resume reason:', sessionStateOutput.reason);
});
```
```jsx theme={null}
SessionStateOutput = {
state: SessionState,
reason: string
}
```
**Session State** enum values:
* `INITIALISED` - Session initialized
* `ONBOARDING_IN_PROGRESS` - Onboarding in progress
* `MONITORING_IN_PROGRESS` - Monitoring in progress
* `PAUSED` - Session paused
* `SUSPENDED` - Session suspended
* `STOPPED` - Session stopped
* `COMPLETED` - Session completed
* `TERMINATED` - Session terminated
### Suspend
Triggered when a proctoring session is suspended due to violations or technical issues.
```jsx theme={null}
Proview.session.on('Suspend', (sessionStateOutput) => {
// Handle session suspension
});
```
```jsx theme={null}
Proview.session.on('Suspend', (sessionStateOutput) => {
console.log('Session suspended:', sessionStateOutput.state);
console.log('Suspension reason:', sessionStateOutput.reason);
});
```
```jsx theme={null}
SessionStateOutput = {
state: SessionState,
reason: string
}
```
**Session State** enum values:
* `INITIALISED` - Session initialized
* `ONBOARDING_IN_PROGRESS` - Onboarding in progress
* `MONITORING_IN_PROGRESS` - Monitoring in progress
* `PAUSED` - Session paused
* `SUSPENDED` - Session suspended
* `STOPPED` - Session stopped
* `COMPLETED` - Session completed
* `TERMINATED` - Session terminated
### Terminate
Triggered when a proctoring session is terminated.
```jsx theme={null}
Proview.session.on('Terminate', (sessionStateOutput) => {
// Handle session termination
});
```
```jsx theme={null}
Proview.session.on('Terminate', (sessionStateOutput) => {
console.log('Session terminated:', sessionStateOutput.state);
console.log('Termination reason:', sessionStateOutput.reason);
});
```
```jsx theme={null}
SessionStateOutput = {
state: SessionState,
reason: string
}
```
**Session State** enum values:
* `INITIALISED` - Session initialized
* `ONBOARDING_IN_PROGRESS` - Onboarding in progress
* `MONITORING_IN_PROGRESS` - Monitoring in progress
* `PAUSED` - Session paused
* `SUSPENDED` - Session suspended
* `STOPPED` - Session stopped
* `COMPLETED` - Session completed
* `TERMINATED` - Session terminated
### StateChange
Triggered whenever the session state changes.
```jsx theme={null}
Proview.session.on('StateChange', (sessionStateOutput) => {
// Handle any state change
});
```
```jsx theme={null}
Proview.session.on('StateChange', (sessionStateOutput) => {
console.log('Session state changed:', sessionStateOutput.state);
console.log('State change reason:', sessionStateOutput.reason);
});
```
```jsx theme={null}
SessionStateOutput = {
state: SessionState,
reason: string
}
```
**Session State** enum values:
* `INITIALISED` - Session initialized
* `ONBOARDING_IN_PROGRESS` - Onboarding in progress
* `MONITORING_IN_PROGRESS` - Monitoring in progress
* `PAUSED` - Session paused
* `SUSPENDED` - Session suspended
* `STOPPED` - Session stopped
* `COMPLETED` - Session completed
* `TERMINATED` - Session terminated
### NetworkStatusChanged
Use this hook to react whenever the candidate's device goes offline or comes back online. The payload includes the normalized network status, so you can surface diagnostics or pause downstream uploads.
```jsx theme={null}
Proview.session.on('NetworkStatusChanged', ({ status }) => {
if (status === 'offline') {
console.warn('Network connectivity lost — show retry UI');
} else {
console.log('Network restored, resume streaming');
}
});
```
```ts theme={null}
type NetworkStatusPayload = {
status: 'online' | 'offline';
};
```
* Emitted on every browser online/offline transition detected by Proview.
* Invalid or missing payloads automatically normalize to `{ status: 'offline' }`.
### StreamingStatusChanged
Listen for changes in the underlying media streaming connection (different from coarse session states). This hook fires as the media pipeline connects, reconnects, or disconnects so that you can show precise UI copy or log telemetry.
```jsx theme={null}
Proview.session.on('StreamingStatusChanged', ({ status, data }) => {
switch (status) {
case 'connected':
toast.success('Streaming live');
break;
case 'reconnecting':
toast.info('Trying to restore streaming…');
break;
case 'disconnected':
toast.error('Streaming stopped', data);
break;
default:
break;
}
});
```
```ts theme={null}
type StreamingStatusPayload = {
status: 'connected' | 'disconnected' | 'reconnecting' | 'reconnected';
data?: Record;
};
```
* Events are emitted from the live room lifecycle (`connected`, `disconnected`, `reconnecting`, `reconnected`).
* Payloads missing a `status` field normalize to `{ status: 'disconnected' }`.
## Removing Event Listeners
Use the `off` method to remove event listeners:
```jsx theme={null}
// Remove specific listener
Proview.session.off(eventName, callback);
```
```jsx theme={null}
// Create handler function
const handleSessionPause = (sessionStateOutput) => {
console.log('Session paused:', sessionStateOutput.state);
};
// Add the listener
Proview.session.on('Pause', handleSessionPause);
// Later, remove the specific listener
Proview.session.off('Pause', handleSessionPause);
```
```jsx theme={null}
SessionStateOutput = {
state: SessionState,
reason: string
}
```
**Session State** enum values:
* `INITIALISED` - Session initialized
* `ONBOARDING_IN_PROGRESS` - Onboarding in progress
* `MONITORING_IN_PROGRESS` - Monitoring in progress
* `PAUSED` - Session paused
* `SUSPENDED` - Session suspended
* `STOPPED` - Session stopped
* `COMPLETED` - Session completed
* `TERMINATED` - Session terminated
# Getting Started
Source: https://docs.talview.com/sdk/proctoring/getting-started
Welcome to the Proview SDK (v8). Follow these steps to embed the latest SDK in your application.
## Prerequisites
* Talview-provisioned tenant + project DSN (customer success or [Talview Sales](https://www.talview.com/request-a-demo) can help).
* Modern browser with WebRTC support and HTTPS hosting for your delivery app.
* Ability to add a script tag and a small bootstrap snippet wherever proctoring needs to run.
### Content Security Policy (CSP)
If your application enforces CSP headers, allow the domains and inline resources required by the SDK:
```
Content-Security-Policy:
script-src 'unsafe-inline' https://sdk.tlv.cx;
style-src 'unsafe-inline';
connect-src 'self' https://*.googleapis.com https://*.talview.com wss://*.talview.com;
img-src 'self' https://sdk.tlv.cx;
```
## 1. Load the SDK once
Place the loader as the **last script** on any page that needs proctoring. The loader attaches itself globally as `window.Proview` and fires `window.proviewOnLoad` when ready.
```html theme={null}
```
> Use the environment-specific loader URL shared during onboarding (dev / staging / prod). The example above targets the production CDN.
## 2. Initialise once per page view
Call `Proview.session.init` after the loader fires. All options are optional; identifiers can be supplied now or later via `Proview.session.start`.
```html theme={null}
```
> `workflow_step.flow_uuid` *(optional)* is the proctoring configuration identifier for the provided `dsn`.
>
> **Please note:** if the workflow step is already created with a flow, this will not override it.
### Host checklist
* Ensure `dsn` is set; `session.init` rejects with `Missing DSN` otherwise (see `InitConfigSchema` in the SDK).
* Provide `attendee` (with `identifier`), `workflow_step` (with `identifier`), and a top-level `identifier` — all required — during `session.init`.
* Do **not** gate your own UI on the loader script—wait for the session to enter the `MONITORING_IN_PROGRESS` state (next section).
## 3. Start the proctoring session before showing the assessment
Trigger the session start from your own UI (for example, a “Start Exam” button) once the candidate is ready. Wait for the promise to resolve before displaying your assessment content.
```html theme={null}
```
## 4. Stop / complete / pause / resume
The session module mirrors the methods listed in `/sdk/proctoring/configuration`:
```js theme={null}
// Stop without submitting the exam
await Proview.session.stop();
// Mark exam as completed (idempotent)
await Proview.session.complete();
// Pause with a reason (required)
await Proview.session.pause('Scheduled break');
// Resume after a break
await Proview.session.resume('Break over');
```
All operations update the local session context and invoke your `onError` handler on failure. When rolling out pause/resume, consider mapping them to your own assessment timers as well.
## 5. Troubleshooting quick tips
* **`Missing DSN`**: confirm the value passed into `Proview.session.init`. The SDK validates the configuration and rejects empty strings.
* **No UI rendered**: ensure `Proview.session.start()` ran successfully and that a valid attendee/workflow identifier exists in context.
* **Permission prompts not appearing**: the host page must not override camera/mic permissions (see best practices). Verify using your browser’s developer tools.
* **Network disconnects**: listen for your own connectivity changes and optionally call `Proview.session.pause()` so the candidate is aware.
# Loader Script
Source: https://docs.talview.com/sdk/proctoring/installation/loader-script
The Loader Script is the easiest way to initialize the Proview SDK. The Loader Script also automatically keeps your Proview SDK up to date and offers configuration for different Proview proctoring features.
The Loader Script is the easiest way to initialize the SDK. The Loader Script also automatically keeps your SDK up to date.
### Using the loader
To use the loader, Copy the script tag provided in the below section and include it as the last script on your page.
```jsx theme={null}
```
While the Loader Script will load the Proview script, but configuration has to be set by your application according to your needs. using the init function you can initialize the SDK.
💡 The proviewOnLoad hook get attached to window when the loader script loaded successfully into the page.
```jsx theme={null}
```
# NPM
Source: https://docs.talview.com/sdk/proctoring/installation/npm
Learn about installing with NPM
The [npm package](https://www.npmjs.com/package/@talview/sdk) for Proview offers several advantages for specific use cases:
* **Version control**: Installing via npm enabling you to manage updates and ensure compatibility with your project.
* **Build process integration**: Using the npm package allows for better integration with your build process and bundling tools.
```jsx theme={null}
# Install the package
npm install @talview/atx-embedded --save
```
# Installation Methods
Source: https://docs.talview.com/sdk/proctoring/installation/overview
Review our alternate installation methods.
* [Loader Script](/sdk/proctoring/installation/loader-script)
* Learn about the proview JavaScript Loader Script
* [NPM](/sdk/proctoring/installation/npm) (Not yet launched)
* Learn about installing with NPM.
## How to Decide which installation method to use
Depending on the concrete needs of your application, you may wonder which installation method you should use.
### **Why Choose the Loader Script Over NPM**
Using the Loader Script is the easiest way to start using proview. Add a script tag to your application, and we'll take care of setting everything else up correctly for you.
* **Easy to set up**: Just [add a script tag](/sdk/proctoring/installation/loader-script) to your application.
* **Easy to upgrade**: We'll take care of always shipping the latest version of the SDK to your users. No action's needed from you. This ensures you'll always get the latest features and bug fixes of the proview SDK.
* **Easy to add additional configuration**: You can [configure the SDK](/sdk/proctoring/configuration) to your liking via `window.proviewOnLoad`.
### **Why Choose NPM Over the Loader Script (Yet to be launched)**
While using the Loader Script has definite advantages, it also comes with some drawbacks. In these scenarios, using the npm package is the better choice:
* **Framework-specific initialization**: As of now, the Loader Script only provides generic Browser JavaScript instrumentation. This means that you won't get any React, Vue, or similar framework-specific features for proview. To get these features, you'll need to install the framework SDK (e.g. `@talview/atx-embedded-app`) via npm.
* **Full control over the SDK version**: If you need full control over the SDK version, you'll need to install the SDK via npm.
# Proview SDK — v7 to v8 Migration Guide
Source: https://docs.talview.com/sdk/proctoring/migrations/v7-to-v8
Client-side Proview SDK migration: v7 → v8 · Script: `https://sdk.tlv.cx/session/init.js`
**Official v8 docs:** [Getting Started](/sdk/proctoring/getting-started) · [Full API Reference](/sdk/proctoring/configuration) · [Session Playback](/sdk/session-playback/getting-started)
This guide covers migration-specific changes and before/after code only. Refer to the official docs links above for complete API reference, parameter defaults, and current examples.
## Breaking changes
All changes below require code modification. Severity indicates what breaks without the fix.
### 🔴 Critical — the integration will not load without these
**Script URL has changed.** Update the loader on every page that runs proctoring.
```html theme={null}
```
**Global namespace renamed: `ProctorClient3` → `Proview`.** `window.ProctorClient3` no longer exists. All method calls move under `Proview.session.*`.
```js theme={null}
// v7
window.ProctorClient3.start();
window.ProctorClient3.stop();
window.ProctorClient3.on(/* ... */);
// v8
Proview.session.start();
Proview.session.stop();
Proview.session.on(/* ... */);
```
**Authentication credential changed: `proctor_token` → `dsn`.** v7 used a per-session `proctor_token` UUID. v8 uses a project-level Data Source Name (DSN). Contact Talview support to provision your DSN.
**Initialization pattern changed: command queue → `proviewOnLoad` callback.** v7 used a command queue (`window.tv`). v8 requires `window.proviewOnLoad` to be defined **before** the script tag; the `Proview` global is available inside the callback.
```js theme={null}
// v7
window.tv = window.tv || function () { (tv.q = tv.q || []).push(arguments); };
// v8
window.proviewOnLoad = async function () {
// Proview global is available here
const success = await Proview.session.init({ /* ... */ });
if (!success) return;
};
```
### 🟠 High — behavioral breakage
**Session start is now a Promise, not a callback.** `initCallback(err, uuid)` is removed. `session.start()` returns a Promise that resolves with a `SessionOutput`.
```js theme={null}
// v7
tv('init', token, {
initCallback: function (err, uuid) {
if (err) return;
ProctorClient3.start();
},
});
// v8
const output = await Proview.session.start();
console.log('Session UUID:', output.uuid);
```
**Client-side alert events removed — monitoring is now server-side via webhooks.** v7 fired per-alert events via numeric IDs (`ProctorClient3.on('log:event:type:16', cb)`). v8 has **no client-side alert events**. All monitoring happens server-side and is delivered as structured **incidents** to your registered webhook endpoint. The only suspension signal visible client-side is the `Suspend` hook. See [Webhooks overview](/graph-api-reference/webhooks/overview).
**Error handling is now global, not per-init.** Register `Proview.onError(handler)` once **before** calling `session.init()`. The per-init `errorCallback` is removed.
```js theme={null}
Proview.onError(function (err) {
// err.code, err.message, err.type: 'warning' | 'critical'
});
```
**Network events are now object-based, not a single callback.** `networkDisconnectionCallback` is removed. Use the `NetworkStatusChanged` hook. The callback receives an object `{ status: 'online' | 'offline' }`, not a string.
```js theme={null}
Proview.session.on('NetworkStatusChanged', function ({ status }) {
if (status === 'offline') showBanner();
if (status === 'online') hideBanner();
});
```
**Webhook payload format has changed.** The v7 `rating_callback_url` flat payload is replaced by a typed, versioned JSON envelope. See [Webhooks overview](/graph-api-reference/webhooks/overview) and [Subscribing to webhooks](/graph-api-reference/webhooks/subscribing).
### 🟡 Medium & Low — parameter renames and removals
All renamed and removed parameters are listed in the [Parameter reference](#parameter-reference-v7-v8-changes) table below.
## Before you start
* **DSN** — Contact Talview to provision DSNs for staging and production. Treat it as a secret; never commit it or expose it in source maps.
* **Workflow step identifiers** — Session type is no longer passed in code; it is dashboard-configured. Confirm your `workflow_step.identifier` UUIDs with Talview before writing code.
* **Webhook endpoint** — Provide your HTTPS endpoint URL to Talview support; they configure which event types are delivered. The endpoint must accept `POST`, respond `HTTP 200` within 10 seconds, and be publicly reachable.
## SDK migration
### Script loading
Define `window.proviewOnLoad` before the script tag. The `Proview` global is available inside the callback.
```html theme={null}
```
### Initialization
```js theme={null}
// v7
tv('init', 'xxxxxxxx-proctor-token-xxxx', {
profileId: 'candidate-user-id',
session: 'session-uuid',
session_type: 'record_and_review',
sessionTitle: 'Technical Interview',
firstName: 'Jane',
lastName: 'Doe',
email: 'jane@example.com',
initCallback: function (err, uuid) {
if (err) return;
ProctorClient3.start();
},
errorCallback: function (err) { console.error(err); },
networkDisconnectionCallback: function () { showOfflineBanner(); },
});
```
```js theme={null}
// v8
window.proviewOnLoad = async function () {
// 1. Register the global error handler before init()
Proview.onError(function (err) {
// err.code, err.message, err.type: 'warning' | 'critical'
console.error('[Proview]', err.code, err.message);
});
// 2. Register session hooks before init()
Proview.session.on('NetworkStatusChanged', function ({ status }) {
if (status === 'offline') showOfflineBanner();
if (status === 'online') hideOfflineBanner();
});
Proview.session.on('Suspend', function ({ state, reason }) {
console.log('Session suspended:', reason);
});
Proview.session.on('StateChange', function ({ state, reason }) {
console.log('State →', state, reason);
});
// 3. Initialize — returns Promise
const success = await Proview.session.init({
dsn: 'YOUR_DSN_HERE',
identifier: 'session-uuid-from-your-backend',
attendee: {
identifier: 'candidate-user-id',
first_name: 'Jane',
last_name: 'Doe',
email: 'jane@example.com',
},
workflow_step: {
identifier: 'workflow-step-uuid-from-your-backend',
name: 'Technical Interview',
duration: 60,
},
});
if (!success) {
console.error('Proview failed to initialize');
return;
}
};
```
Start the session on a user action (for example, an "Start Exam" button click):
```js theme={null}
// v8 — start on user action
document.getElementById('start-exam').addEventListener('click', async function () {
try {
const output = await Proview.session.start();
// output.uuid, output.state, output.attendee, output.workflow_step
console.log('Session started:', output.uuid);
} catch (err) {
console.error('Unable to start proctoring', err);
}
});
```
### Stop and complete
```js theme={null}
// Normal completion — candidate reached the end of the assessment
await Proview.session.complete();
// Abnormal stop — timed out, navigated away, or terminated early
await Proview.session.stop();
```
### Pause and resume
**`reason` is required** for both `pause()` and `resume()`. The SDK throws if the string is empty.
```js theme={null}
// v7
ProctorClient3.pause();
ProctorClient3.resume();
// v8
await Proview.session.pause('Scheduled break');
await Proview.session.resume('Break over');
```
## Session hooks
`Proview.session.on(eventName, callback)` replaces v7's numeric alert IDs. `session.on()` returns an unsubscribe function, or use `session.off(eventName, namedCallback)` to remove a specific listener.
| Event | Payload shape | When fired |
| ------------------------ | ------------------------------------------------------------------------------------- | ----------------------------------------------- |
| `Suspend` | `{ state, reason }` | Session auto-suspended by the monitoring system |
| `Terminate` | `{ state, reason }` | Session ended by the system due to violations |
| `Pause` | `{ state, reason }` | Session paused (mirrors `session.pause()`) |
| `Resume` | `{ state, reason }` | Session resumed (mirrors `session.resume()`) |
| `StateChange` | `{ state, reason }` | Any session state transition |
| `NetworkStatusChanged` | `{ status: 'online' \| 'offline' }` | Network connectivity changes |
| `StreamingStatusChanged` | `{ status: 'connected' \| 'disconnected' \| 'reconnecting' \| 'reconnected', data? }` | Media stream quality changes |
**No client-side alert events in v8.** The v7 numeric alert IDs (`ProctorClient3.on('log:event:type:N', cb)`) do not exist in v8. All monitoring happens server-side and is delivered as structured incidents to your webhook endpoint.
## Session states
`SessionOutput.state` (and the `state` field in hook payloads) uses the SDK `SessionState` enum. These are the same eight uppercase values documented in [Configuration](/sdk/proctoring/configuration).
| State | Meaning | How reached |
| ------------------------ | ---------------------------------------------- | ----------------------------------- |
| `INITIALISED` | SDK loaded, before `session.init()` completes | SDK ready |
| `ONBOARDING_IN_PROGRESS` | Candidate is in the precheck / onboarding step | After `session.start()` resolves |
| `MONITORING_IN_PROGRESS` | Active — candidate is being monitored | After onboarding completes |
| `PAUSED` | Temporarily halted by your code | `session.pause(reason)` |
| `SUSPENDED` | Auto-paused by monitoring due to a violation | System — fires the `Suspend` hook |
| `STOPPED` | Interrupted before completion | `session.stop()` |
| `COMPLETED` | Candidate finished legitimately | `session.complete()` |
| `TERMINATED` | Ended by the system due to violations | System — fires the `Terminate` hook |
**Webhook `payload.status` is a separate, server-side vocabulary** — `CREATED`, `IN_PROGRESS`, `PAUSED`, `SUSPENDED`, `STOPPED`, `COMPLETED`, `TERMINATED`. It is delivered in webhook events and is **not** the same set as the SDK `state` above (for example, server-side `IN_PROGRESS` corresponds to the SDK's `MONITORING_IN_PROGRESS`). Don't map the two one-to-one. See [Webhooks overview](/graph-api-reference/webhooks/overview).
## Parameter reference: v7 → v8 changes
| v7 | v8 | Change |
| ------------------------------ | ------------------------------------------------- | ------------------------------------------------------------------------------------------------- |
| `proctor_token` | `dsn` | Renamed + format changed — DSN is project-level, not per-session |
| `session` | `identifier` | Renamed only |
| `profileId` | `attendee.identifier` | Moved into the nested `attendee` object |
| `firstName` / `lastName` | `attendee.first_name` / `attendee.last_name` | Snake\_case + nested in `attendee` |
| `email` | `attendee.email` | Nested in `attendee` |
| `session_type` | — | Removed — configure per workflow in the Proview dashboard |
| `sessionTitle` | `workflow_step.name` | Moved into the `workflow_step` object |
| `initCallback(err, uuid)` | `await Proview.session.start()` → `SessionOutput` | Replaced — start is now a separate Promise-based call, not a callback passed to init |
| `errorCallback(err)` | `Proview.onError(handler)` | Replaced — errors handled via a global `Proview.onError()` call made once before `session.init()` |
| `networkDisconnectionCallback` | `session.on('NetworkStatusChanged', cb)` | Replaced — network events are a session hook; payload is `{ status }` (object, not string) |
For the full `session.init()` options and the `attendee`, `workflow_step`, and `SessionOutput` object shapes, see [Configuration](/sdk/proctoring/configuration) and [Types](/sdk/proctoring/types).
## Rollout checklist
**Code changes**
* [ ] Script URL updated to `https://sdk.tlv.cx/session/init.js`
* [ ] `window.proviewOnLoad = async function () { ... }` defined before the script tag
* [ ] All `ProctorClient3.*` calls replaced with `Proview.session.*`
* [ ] `Proview.onError(handler)` registered before `session.init()`
* [ ] `session.init()` return value checked: `const success = await Proview.session.init(...); if (!success) return;`
* [ ] `session.on()` listeners use the event names from the [Session hooks](#session-hooks) table
* [ ] `NetworkStatusChanged` handler reads `{ status }` (object, not a string)
* [ ] `pause()` and `resume()` calls pass a non-empty reason string
* [ ] `attendee.first_name` / `attendee.last_name` used (not `name`)
* [ ] Webhook handler updated for the v8 envelope format
* [ ] Session / incident storage updated for v8 fields (`uuid`, `integrity`, `score`)
* [ ] Session playback updated to `Proview.session.playback({ dsn, uuid, root })`
**Staging validation**
* [ ] Full lifecycle: `init()` → `start()` → `complete()` → webhook received
* [ ] Session and incident webhook payloads received and stored correctly
* [ ] `Suspend` hook fires and is handled
* [ ] `NetworkStatusChanged` payload handled as a `{ status }` object
* [ ] Pause / resume tested end-to-end with non-empty reason strings
* [ ] Session playback loads
* [ ] Error handler fires on an invalid DSN
* [ ] Browser console: no CSP violations, no 404s from the old domain
**Production cutover**
* [ ] DSN swapped to the production value
* [ ] CSP updated in production (including `'unsafe-inline'` directives)
* [ ] Webhook endpoint registered for production with Talview support
## Troubleshooting
`proviewOnLoad` was not defined before the script tag, or the SDK script failed to load. Ensure `window.proviewOnLoad = async function () {...}` is in a `
```
## `session.playback` Options
Pass a configuration object when invoking `session.playback()`. Each field is required unless noted otherwise.
* `dsn` – Talview Data Source Name that links the player to your Talview account or environment.
* `uuid` – Identifier of the session (for example, `session-123`) you want to play back.
* `root` – DOM element id where the player mounts when `target` is `"embed"`; the element must exist before you initialize playback. Not used when `target` is `"popout"` or `"newtab"`.
* `target` *(optional)* – Where the playback opens. Defaults to `"embed"`. Accepted values:
* `"embed"` – renders the player inside the current page, mounted into `root`. Use `wrapper` to control the in-page layout.
* `"popout"` – opens the player in a separate popup browser window.
* `"newtab"` – opens the player in a new browser tab.
* `wrapper` *(optional)* – In-page layout for an embedded player. Only applies when `target` is `"embed"`; it is ignored for `"popout"` and `"newtab"`. Defaults to `"inline"`. Accepted values:
* `"inline"` – mounts in the normal document flow inside `root`.
* `"sidepanel"` – slides in as a panel from the side of the viewport.
* `"modal"` – opens as a centered overlay dialog.
* `player_config` *(optional)* – Object grouping the player's sizing options:
* `width` *(optional)* – Width of the player. Accepts a CSS length string (`"800px"`, `"90%"`, `"80vh"`) or a number, which is treated as pixels. Its effect depends on `target`/`wrapper` — see [Dimensions](#dimensions). Ignored when `target` is `"newtab"`.
* `height` *(optional)* – Height of the player. Same value format as `width`. Ignored for `wrapper: "sidepanel"` (a side panel always spans the full viewport height) and when `target` is `"newtab"`. See [Dimensions](#dimensions).
* `session_config` *(optional)* – Object grouping authentication and view options for the playback session:
* `token` *(optional)* – JWT authentication token. When provided, it is used in place of the standard Firebase auth flow and is propagated through all internal navigations so authentication is preserved across view transitions.
* `report` *(optional, boolean)* – Controls whether the session report is shown on mount. Defaults to `true`. When `false`, the report is skipped and the player opens directly on the playback dashboard; the report is then unreachable (there is no "Back to Report" button).
### Placement: `target` vs `wrapper`
`target` and `wrapper` control two independent things:
* `target` decides **where** the player opens — inside the current page (`"embed"`), in a popup window (`"popout"`), or in a new tab (`"newtab"`).
* `wrapper` decides the **in-page layout** of an embedded player (`"inline"`, `"sidepanel"`, or `"modal"`), and therefore only has an effect when `target` is `"embed"`.
The player is always rendered inside an iframe — that is the delivery mechanism, not a configurable option, so there is no `"iframe"` value on either field. An embedded `"modal"`, for example, is a modal dialog whose contents are the player iframe.
### Dimensions
`width` and `height` (both under `player_config`) set the size of the player. Both are optional; when omitted the SDK falls back to sensible defaults for the chosen placement (auto-resizing to content or fitting the viewport). What each value controls depends on `target` and `wrapper`:
| `target` / `wrapper` | `width` | `height` |
| --------------------- | ---------------------------------------------- | --------------------------------------------------------------------------------------------- |
| `embed` + `inline` | Width of the mounted player | Height of the mounted player. You can also size the `root` element yourself with CSS instead. |
| `embed` + `sidepanel` | Width of the side panel | Ignored — the panel always spans the full viewport height. |
| `embed` + `modal` | Preferred dialog width, capped to the viewport | Preferred dialog height, capped to the viewport. |
| `popout` | Popup window width | Popup window height. |
| `newtab` | Ignored | Ignored. |
Notes:
* A number is treated as pixels (`player_config.width: 800` ≡ `player_config.width: "800px"`).
* `popout` opens a real browser window via `window.open`, whose size can only be expressed in pixels. Percentage or viewport units (`"90%"`, `"80vh"`) are ignored for `popout` and fall back to the default window size — pass pixel values instead.
## Ready Callback
The factory exposes an `onReady` helper so you can attach logic once the iframe player is bootstrapped:
```js theme={null}
const playback = Proview.session.playback(options);
playback.onReady(() => {
console.log('Playback ready');
});
```
Handle errors through the global `Proview.onError` hook described in the main getting-started guide.
## Examples
### Embed with token auth
```js theme={null}
const playback = Proview.session.playback({
dsn: 'dsn',
uuid: 'uuid',
root: 'playback-root',
session_config: {
token: 'session-jwt',
},
});
```
### Open directly on the playback dashboard
Skips the report and opens the playback dashboard on mount. The report is not reachable.
```js theme={null}
const playback = Proview.session.playback({
dsn: 'dsn',
uuid: 'uuid',
root: 'playback-root',
session_config: {
report: false,
},
});
```
### Embed with custom dimensions
Sizes the embedded player via `player_config`.
```js theme={null}
const playback = Proview.session.playback({
dsn: 'dsn',
uuid: 'uuid',
root: 'playback-root',
player_config: {
width: '800px',
height: '600px',
},
});
```