---
module: fleet.task-permissions
title: Task Permissions Guide
tab: Customer
order: 10
audience: customer
---

Which commands each institution's customer users may send to their own devices.

## 🔐 What Task Permissions Do
1. A fleet task is a command sent to a real ATM — a reboot is a machine out of service for minutes.
2. By default a customer user can send **nothing**. Permission does not exist until you grant it.
3. A grant is per **institution** and per **command**: "Customer 1 may reboot", not "customers may reboot".
4. A customer can only ever target devices belonging to their own institution. Granting Reboot to one institution gives them no reach into another.

> **Nothing is permitted until you grant it.** An institution with no ticks can push no commands at all — that is the safe default, and it is where every institution starts.

## ✅ Grant a Command
1. Find the institution's row. The name is shown with its **institution key** underneath.
2. Tick the box under the command you want to allow.
3. The change saves immediately — a green confirmation names the institution.

There is no Save button and no undo. Ticking a box grants the permission the moment you click it, and unticking revokes it just as fast.

## 🚫 Revoke a Command
1. Untick the box.
2. The permission is gone immediately. The next time that customer tries the command they are told they lack permission.

> Revoking does **not** cancel tasks already in flight. A reboot that was already accepted will still run.

## 🧭 Which Commands Can Be Granted
Only two commands can be granted to a customer at any setting:

| Command | What it does |
|---|---|
| **Reboot** | Restarts the ATM |
| **Restart Agent** | Restarts the HiveIQ agent process on the ATM |

These are the operations on the device Command Center. Everything else — configuration changes, module installs, agent updates, packet capture — is an operator power and is never offered here, no matter what you tick. If a command you expect is missing from this page, it is missing by design.

## 👤 Who Can See This Page
Task Permissions is visible only to **MSP admins** and **BCOS admins**. Customer users never see the page, and cannot grant themselves anything.

Your own admin users are not affected by these settings. Only customer users are gated — an admin keeps the full command set regardless of what is ticked here.

## ❓ A Customer Says They Cannot Reboot
1. Check this page: does their institution have **Reboot** ticked?
2. If it is ticked and they still cannot, confirm the device belongs to their institution — a customer cannot command another institution's machines.
3. The error they see names the missing permission: *"Your institution is not permitted to push 'REBOOT'. Ask your service provider to enable it."*
