# Editing an employee

> **You need:** *Employees — edit*.

Editing updates an existing employee's details, their hub, and — for drivers — how the dispatcher treats them.

## Changing details

Open the employee and change what needs changing. The record is the single source for who this person is, so keeping it accurate matters beyond this screen: reports group by hub, and the dispatcher reads driver configuration from here.

## Moving someone between hubs

Changing an employee's hub moves them between operations.

> This changes which operation they count towards from now on. Historical data is not retrospectively re-filed, so a mid-period move shows the person's work split across both hubs for that period. That is correct, and worth knowing before someone asks why a hub's numbers look odd.

Move people at a period boundary where you can.

## Driver configuration

For employees who drive, the record carries the configuration the dispatcher uses — including their driver type, which decides how they rank against others.

Two things follow from that, both explained in [Driver classification and priority](/books/console-yF7/page/driver-classification-and-priority):

- **Internal drivers outrank contracted ones.** Changing someone's type changes who wins when both are candidates for an order.
- **Type also decides what they can be given.** A zone that allows only certain own-driver types will skip anyone else.

So a driver who is "never getting orders" is often a type question rather than an availability one — check the zone's allowed types in [Delivery zones](/books/console-yF7/page/delivery-zones) as well.

## What editing does not change

| Not changed here | Change it in |
|---|---|
| What they can do in the console | [Managing roles from the console](/books/console-yF7/page/managing-roles-from-the-console) |
| What data they can see | [Setting an employee's scope](/books/console-yF7/page/setting-an-employees-scope) |
| Their password | [Employees - Password](/books/console-yF7/page/employees-password) |

Updating someone's job does not update their console access. If a person changes role in the business, all three need attention, and it is easy to do one and forget the others.

## After a change that matters

For a driver, confirm the change had the effect you intended by watching whether the dispatcher starts using them as expected on the next cycle — no more than 60 to 300 seconds away. See [The assignment cycle, step by step](/books/console-yF7/page/the-assignment-cycle-step-by-step).