# Staff Badges
> Source: https://development.fuze-store.com/docs/store/nfc/staff-badges

# Staff badges

A badge lets a staff member **tap instead of typing a PIN**. It works in three
places:

- **Switching in** at the start of a shift
- **Unlocking a terminal** that locked itself
- **Approving** something a manager has to sign off, like a void

Anyone with permission can also tap a colleague's badge to see who they are and
what they're allowed to do.

  Staff badges are part of the **Staff Operations** add-on, which is included
  during your free trial.

## Two kinds of badge

**NFC badge** — a tag your staff taps. You write it from the app, and it can be
**paired to that exact tag**, so a copy of the badge won't work on a different
one.

**Printed QR badge** — a code you print onto a card or lanyard. No tag needed,
and it's scanned with the camera. A printed code can be photographed, so it
can't be paired the way an NFC tag can.

Each staff member has **one badge at a time**. Issuing a new one immediately
stops the old one from working — which is exactly what you want when someone
loses theirs.

## Giving someone a badge

1. Open **Staff**, choose the person, and find the **Staff badge** card.
2. Pick **Write an NFC badge** (or **Create a printed QR badge**).
3. For NFC, hold a blank tag to your phone or your counter reader. The badge is
   created and written in one step, then paired to that tag.

  A QR badge's link is shown **once**. Print or save it right away — it can't be
  shown again, and getting it back means issuing a new badge.

## Approvals can ask for a PIN too

By default, approving with a badge **also asks for the manager's PIN**.

That's deliberate. A badge is like a key: whoever is holding it is treated as
its owner. That's fine for "who's at the till", but a lanyard left on the
counter shouldn't be enough to approve a void.

You can turn this off in **Preferences → Policies → Staff operations** if your team
keeps their badges on them.

Declining a request never asks for a PIN — saying no doesn't give anyone
anything.

## Losing a badge

Open the person's profile and choose **Revoke badge**. The next tap stops
working straight away.

**They can still sign in with their PIN.** Revoking a badge takes away the tag,
not their access.

## Turning badges off entirely

**Preferences → Policies → Staff operations → Staff badges** switches the whole
feature off. Your team goes back to PINs — nobody is locked out, and tags you've
already written keep their data if you switch it back on later.

## If a tap doesn't work

For security, the app gives the **same answer** whether a badge is unknown,
revoked, paired to a different tag, or belongs to someone else. Otherwise
anyone could tap tags at a locked terminal to learn which one opens it.

So check these instead:

- Does the person's profile show a **live** badge (not *Revoked*)?
- If it says **paired to a tag**, is this the same tag it was written to?
- Are staff badges still switched on in Preferences?
- On a locked terminal, only **that operator's own** badge resumes the session.
  Anyone else should use **Use a different operator**.