> ## Documentation Index
> Fetch the complete documentation index at: https://docs.talview.com/llms.txt
> Use this file to discover all available pages before exploring further.

# 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 |

<Tip>
  **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.
</Tip>