# Folder navigation, Recents and pins

Personal Admin UI shortcuts for Devices, Contents and Files (separate budgets per resource area).

| Mechanism | Behavior | Lifetime / limit |
|---|---|---|
| Last-folder memory | Per main-menu remembered folder during navigation | In-memory; clears on full reload, customer change or logout |
| Recent folders | Folders recorded by supported selections/actions (not ordinary browse alone); MRU, deduped | User preferences; 10 folders per customer per area; 5 customer buckets per area |
| Pins | Shortcuts to folders **and** individual files, contents or devices | User preferences; 100 pins per resource area across all customers |

Hard limits and landing:
- Recents = folders only. Pins = folders + resources (UI title **Pinned folders** / "100 pinned folders" is misleading).
- Default card/list menu entry restores last-folder; else root (**My devices** / **My contents** / **My files**). Default **table** navigation opens root page 1, page size 50. Devices **map** has no folder segment. Table and map do not restore last-folder. Recents is not the default landing.
- Selectors keep separate nav state. Files **Branding** is outside Recents/Pins.
- Pinned bar at root (no active search) in supported card/wide-card management and selector views; **Manage pins** lists folders and resources.

Recording and management:
- Recents triggers: supported selections, drag flows, successful management actions, uploads, folder create — not universal visit logging. Root folders excluded. Sixth customer bucket evicts least-recently-modified. No time-based expiry. **Clear** = current customer/area only.
- Pin/unpin on folders and resources; folder-create dialogs can optionally pin. Unresolved pins still count toward 100. Clear-all pins = that area across customer buckets.

Boundaries:
- Personal preferences; read-only users can save their own. Pinning grants no rename/delete/share rights. Customer/team visibility still applies when resolving IDs.
- View As impersonation: edits stay local unless Save-to-user preference consent; updating another user still needs admin authorization.
- Requires a real selected customer. Does not move/delete resources, change scheduling/playback, or send device commands.