Why a Tablet and Not Just a Phone
A phone is a personal device. A tablet is a work device. The moment your server has businesses that manage inventory, security firms that coordinate patrols, or logistics companies that track deliveries, you need a bigger screen and purpose-built tools. Agency-Pad fills that gap.
Built-In Business Apps
Out of the box: inventory manager, employee scheduler, client database, invoice builder, security camera viewer, patrol dispatcher, delivery tracker. Each app is framework-agnostic and hooks into job data. Shop owners see inventory. Security companies see camera feeds. Taxi services see live rides. The data pipes are different, the experience is consistent.
Multi-User Sessions
A tablet can be shared. Multiple players can log in as different employees of the same business without conflict — the UI state is per-user but the underlying data is shared. This is critical for RP where the same tablet device might pass through many hands during a shift.
Permissions Done Right
Job ranks map to feature access. A security firm's junior guard sees camera feeds; senior management sees payroll and scheduling. Configuration per business per rank takes about five minutes. This granularity is what makes the tablet actually usable in serious RP settings.
Design Sibling to Agency-Phone
Agency-Pad shares visual language and component library with Agency-Phone. Players who know one immediately understand the other. That consistency is the kind of thing that elevates a script suite from "collection of tools" to "coherent platform."