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

# Understand Staff device-list access

> Understand why Staff can be authorized to read store devices while management navigation remains hidden.

Device access has an intentional distinction between backend read permission and supported management navigation. The API allows Owner, Manager, and Staff roles to list store devices and POS targets, but current web and native management screens expose the store-device list only to Owners and Managers.

## Who can do this?

Owners and Managers and Staff can use the parts described here. Store-wide management of other devices remains limited to Owners and Managers; self-service for the current device and read-only list access have different scopes. API authorization is authoritative.

## Where

Owners and Managers use **Devices** in web Admin or Store devices in native Settings. Staff do not see those management links and receive a restricted message if they reach the web route. Staff-facing operational flows can still query POS-device targets where needed.

## Steps

1. Treat the API rule as the authorization truth: Staff store membership permits list reads.
2. Treat the UI rule as the supported product experience: Staff are not offered general device management.
3. Staff may update or delete their own registered device through self-service endpoints, but cannot use manager operations on arbitrary team devices.
4. Owners and Managers can list, mark POS state, and remove store devices through the management UI.
5. Document or report the navigation/API mismatch rather than promising Staff a hidden management page.

## Platform notes

Web sidebar filtering and the web Devices route both gate management to Owner/Manager. Native profile navigation also hides Store devices for Staff, and its screen renders a restricted state without management role. The underlying GET endpoints remain accessible to Staff so POS selection and other operational consumers can obtain targets.

## Market notes

The distinction is identical for GB and DE and is role-based, not country-based. Changing language or shop market does not expose the management screen.

## Troubleshooting

If Staff need an operational target but none appears, verify device registration, POS flag, selected shop, and app connectivity. Do not instruct Staff to bypass hidden navigation. If a legitimate workflow requires broader UI access, raise a product issue; until then, an Owner or Manager should perform management changes.

## Related articles

* [View devices and last seen](/en/devices/view-devices-and-last-seen)
* [Mark a device for POS](/en/devices/mark-pos-device)