Privoro

Problem — Administrators needed to understand fleet condition and configuration across users, protected devices, groups, policies, and alerts without inspecting records one by one.

Decision — Establish a clear operational model for monitoring, bulk administration, organizational structure, and policy configuration—then reuse the same interaction language across the system.

Result — Core administrative workflows were approved and implemented. The more ambitious cluster-based Monitoring direction was well received as an exploration, but the table remained the pragmatic path for detailed monitoring.

Privoro’s SafeCase hardware protected mobile devices; Fulcrum was the administrative layer behind the fleet.

As the sole Product Designer on the product, I worked directly with Privoro stakeholders and the implementation engineer to translate the underlying model into something administrators could operate: people, devices, assignments, groups, policies, alerts, and system state had to remain connected without exposing unnecessary technical complexity.

The design principle was consistent throughout the product: show enough structure to support a decision, then reveal detail when the administrator needs to act.

A table is effective for inspecting individual records but weak at communicating the condition of a large fleet as a whole.

Inspired by infrastructure observability tools, I explored a cluster-based Monitoring view where a cell could represent a device—or a group of devices depending on scale. Semantic state made healthy, warning, and critical conditions visible as patterns before the administrator drilled into a specific record.

Stakeholders responded positively to the concept. Its visual and engineering complexity, however, made it difficult to prioritize with the resources available. The table remained the practical direction for detailed monitoring.

That trade-off matters: the exploration clarified the operating model even though the ambitious visualization itself was not the implementation target.

Fulcrum also had to support administration beyond one record at a time.

The bulk workflows accounted for selection state, mixed values, filtering, batch edits, long-running updates, and completion feedback. Large operations stayed visible while they were happening instead of disappearing behind a modal and forcing administrators to guess whether the system had accepted the change.

The same pattern applied to high-volume imports: progress and estimated duration remained part of the interface because, at fleet scale, system state is part of the user’s task.

Groups were not just labels. They became reusable structures connecting people and policy assignment across the organization.

Policies then translated security intent into configurable behavior: an administrator could assign a group, use predefined rules, or create custom conditions and resulting actions. New policies remained inactive by default so unfinished configuration could not affect the fleet accidentally.

Together, groups and policies turned organizational structure and security rules into a model administrators could reuse instead of recreating configuration record by record.

Privoro already had a Bootstrap-based foundation. I extended it into a clearer product language for navigation, tables, filters, forms, semantic status, empty states, progress, success feedback, and contextual guidance—patterns grounded in what Engineering could realistically implement.

Core administrative workflows across users, devices, assignments, groups, policies, alerts, reports, onboarding, and roles were approved and implemented.

Strict NDA conditions prevent meaningful customer metrics from being shared. The strongest evidence is therefore the breadth of the delivered system, the implemented Fulcrum interface later visible in Privoro’s public material, and the underlying workflows preserved in the project artifacts.

Every screen shown here is a recreation, rebuilt from the workflows and interaction patterns designed during the engagement rather than captured from a running system.