# Reassigning Participants

Source: https://docs.astalty.com.au/guide/users/reassigning-participants

> Move every Participant assigned to one coordinator onto another in a single action from the More tab of their profile.

## Overview

When a coordinator goes on leave or leaves your organisation, **Reassign Participants** moves their whole case load onto whoever is covering in one action, rather than editing each Participant individually. It sits on the **More** tab of that user's profile.

> **Available on the Professional plan**
>
> Reassigning Participants is included on the **Professional** plan and above. The Account Owner can review your options on the [Billing](https://docs.astalty.com.au/guide/billing) page.

> **Who Can Reassign Participants?**
>
> Only **Admins** can reassign a case load, and it can't be switched on for other roles. The **More** tab also only appears on a **Standard User**'s profile - see [Converting User Types](https://docs.astalty.com.au/guide/users/converting-user-types).

## Opening Reassign Participants

1. From the [Users](https://app.astalty.com.au/users) page, open the coordinator whose Participants you want to move.
2. From the left-hand menu, select **More**.
3. Next to **Reassign Participants**, select **Reassign**.

![The More tab of a user's profile, with an arrow pointing to the highlighted Reassign Participants row and its Reassign button](https://docs.astalty.com.au/assets/users-reassign-participants-more-tab.png)

If the user isn't the Primary or Service Coordinator for anyone, the drawer shows **No participants assigned** instead of a list.

## Choosing Which Assignments Move

Under **Assignments to reassign**, choose which of the two coordinator roles moves. Each option shows how many Participants it covers.

| Option                       | What moves                                            |
| ---------------------------- | ----------------------------------------------------- |
| **Primary Coordinator only** | The Primary Coordinator on the Participant's profile. |
| **Service Coordinator only** | The Service Coordinator on each of their Services.    |
| **Both roles**               | Both of the above. Selected by default.               |

Switching between these resets your search and re-ticks everyone in the new scope, so choose the scope before you start unticking people.

For the difference between the two roles, see [Primary vs Service Coordinators](https://docs.astalty.com.au/guide/participants/core-concepts/primary-vs-service-coordinators).

## Selecting the Participants

Everyone in scope is ticked when the drawer opens. Untick anyone who should stay with the current coordinator.

![The Reassign Participants drawer with Both roles selected under Assignments to reassign, the highlighted Participants list showing 21 of 21 selected with Primary and Service chips on each row, the New Coordinator field and the Email the New Coordinator checkbox](https://docs.astalty.com.au/assets/users-reassign-participants-form.png)

- Use **Search by name or NDIS number** to narrow the list.
- **Select all** ticks everyone. While you're searching it becomes **Select shown** and ticks only the rows matching your search; **Clear** unticks those same rows.
- The **Primary** and **Service** chips on each row show which of the two assignments that person is there for.

The list covers Participants the user is Primary Coordinator for, plus Participants with a Service they coordinate that hasn't ended yet. Archived Participants are never listed, and a Service whose end date has passed stays with the original coordinator.

## Choosing the New Coordinator

Select the incoming person in **New Coordinator**. Any active or invited Standard User can be chosen whatever their role - they don't need to be an Admin. You can't select the coordinator who already holds the case load.

Tick **Email the New Coordinator** to send them a single email, subject *"A case load has been assigned to you"*, listing everyone they've been given. Leave it unticked and nobody is notified. That email is the only list of who moved in a single reassignment, so tick it if you might need to reverse one.

## Confirming the Reassignment

Type the incoming person's name into **Type the new coordinator's name to confirm** - it has to match exactly - then select **Reassign \[number] Participants**.

> **A Reassignment Can't Be Undone From This Screen**
>
> There's no undo. Running **Reassign Participants** in the opposite direction opens the new coordinator's whole case load with everyone ticked, including the Participants they already held - untick those before you reassign, or change each Participant and Service back by hand.

## What Changes

Reassigning writes two things: the **Primary Coordinator** on the Participant's profile, and the **Service Coordinator** on their Services. The incoming coordinator can see those Participants' notes, records and plans as soon as the reassignment runs.

It doesn't follow that the original coordinator loses sight of them. Admins and Managers can see every Participant whoever coordinates them, and so can Team Members with **View all Participants** switched on - the default. Only a Team Member with it switched off is held to their own case load and loses the Participants they've handed over, see [Roles & Permissions](https://docs.astalty.com.au/guide/users/roles-permissions#participants).

Both changes are recorded against the Participant and the Service, so the move shows in the Audit Trail - as a separate entry per record, not as one reassignment.

> **Tasks Stay With the Original Coordinator**
>
> Reassigning a case load does not move tasks. Anything already assigned to the original coordinator - including tasks dated in the future - stays with them. Move those separately, as covered in [Assigning and Reassigning Tasks](https://docs.astalty.com.au/guide/tasks/assigning-and-reassigning-tasks).

Nothing else moves either: shifts, invoices, service agreements, notes and documents stay exactly as they were.

## Reassigning Before You Deactivate Someone

Deactivating a user removes them as Primary and Service Coordinator without putting anyone in their place, which leaves those Participants and Services unassigned. Reassign their case load first, then deactivate them - see [Restricting, Deactivating and Reactivating Users](https://docs.astalty.com.au/guide/deactivating-and-reactivating-users).
