Besar Shabani
Work  /  Control Seven

Control Seven

A mobile device management platform for monitoring, controlling, and securing company devices.

Client
Control Seven
My role
UX/UI and product design
Platform
Web app
Industry
Mobile device management
Type of work
Product design
Timeline
5 weeks
Control Seven device dashboard on a tablet

In short

  • Device management tools bury administrators in dense data, security settings, and layers of menus.
  • I designed a platform that keeps the overview apart from the detail and groups controls by task.
  • Critical actions such as locking a device or pushing an update ask for confirmation, so mistakes are harder to make.
4core management areas
31%faster device lookup
94%admin task success rate
5weeks of design work
01

Overview

Device management that feels under control.

Control Seven helps organizations manage their company mobile devices. Administrators see device status, manage configurations, enforce security policies, and monitor usage from one place.

The goal was an interface that keeps the operational depth of a device management tool and stays clear enough to use every day.

Control Seven dashboard with profiles, users, registered and enrolled devices, and distribution charts
02

The problem

Powerful tools that are hard to steer.

  • Dense by nature

    Device management holds dense data, security settings, and several administrative layers. It gets hard to navigate quickly.

  • Modules that have to cooperate

    Device monitoring, policy configuration, user management, and reporting had to work together without friction.

  • Live data

    Real-time device information had to stay readable, with a clear hierarchy.

  • Actions with consequences

    Locking a device, pushing an update, or changing a configuration has to feel intentional and safe, to reduce the risk of user error.

The system also had to stay open to new features and enterprise growth.

03

Process

From administrative workflows to a design system.

  1. Map the workflows

    I mapped the administrative workflows and identified the most frequent actions: monitoring device health, applying security policies, and managing user access.

  2. Separate the levels

    The information architecture keeps high-level dashboards apart from detailed configuration views.

  3. Wireframe

    Wireframes group related controls and present device data in structured layouts, to reduce cognitive load.

  4. Build the system

    A modular design system for dashboards, tables, status indicators, and control panels, with clear states for every device.

04

Architecture

Overview first, detail on request.

An administrator starts with the whole fleet and narrows down: from the dashboard to a list, from the list to one device, and from the device to an action. Each level shows only what that decision needs.

  1. DashboardThe fleet at a glance
  2. Device listSearch, filter, group
  3. DeviceEight tabs of detail
  4. ActionLock, update, configure
  5. ConfirmationBefore it happens

Four areas, one structure

  • Devices

    Status, model, and last contact for every enrolled device.

  • Profiles and policies

    Security profiles with management mode, geolocation, Play Store, and kiosk settings.

  • Users

    Access for administrators and their organizations.

  • Reporting

    How versions, profiles, and device activity are distributed across the fleet.

06

Design system

One blue, and status you can read at a glance.

White surfaces on a light grey canvas, one strong blue for actions and data, and a small status marker on every row: enrolled, restricted, enabled, disabled. Tables and charts share the same spacing and type, so a new screen looks familiar right away.

Core palette

  • Primary#0074FC
  • Primary light#98C8FC
  • Canvas#ECECF0
  • Surface#FFFFFF

Typography

FigtreeOne typeface for headings, tables, and labels
  • Regular
  • Medium
  • Bold

List of Devices

Company Devices · Field Teams · Technicians

A clean geometric sans that stays readable in dense tables, small labels, and long device lists.

07

Interface

One device among many

The device list is built for scanning: serial number, name, IMEI, profile, model, state, and last contact in one row, with a group tree on the left. The map shows where the fleet is.

Key features

  • A group tree for organizations and device groups
  • Filter, column settings, and bulk actions above the table
  • Map and satellite view of device locations
Control Seven device list with a group tree and table of devicesControl Seven devices map

Everything about one device

A device page starts with identity and status, then splits the rest into tabs: information, applications, logs, usage, events, remote controls, and files. Memory and storage are shown as bars.

Key features

  • Status and management mode in the header
  • Eight tabs in a fixed order
  • RAM and storage as progress bars
Control Seven device detail page with tabs and storage bars

Policies as readable rows

Security profiles are listed with their mode and the settings that matter most: geolocation, Play Store mode, and kiosk. Each setting is a labelled state, so the difference between two profiles shows up while scanning a column.

Key features

  • Three management modes: company owned, personally owned, fully managed
  • Settings shown as state markers
  • Create and filter from the same bar
Control Seven list of security profiles with mode and settings

Remote control, with care

An administrator can open a live view of a device, start a session, send a notification, or power it off. The controls sit in a modal on top of the list, so it is always clear which device is being touched.

Key features

  • A live screen of the device
  • A session timer
  • View, session, notification, and power off in one row
Control Seven remote control modal showing a live device screen
08

Critical actions

Actions that ask before they act.

Locking a device, pushing an update, or changing a configuration affects someone's working phone. Security-related actions ask for confirmation and say exactly what will happen, so administrators stay confident when they make system-level changes.

Delete Folder dialog with the Delete button disabled until the confirmation is tickedDelete Folder dialog with the confirmation ticked and the Delete button active

Deleting a folder is the clearest example: the Delete button stays grey until the administrator confirms, and only then turns blue.

09

Outcome

Complex administration, made clear.

The result is a structured management platform where complex administrative work is clear and efficient to carry out.

The design system gives the product a base for enterprise growth and new modules.

What I delivered

  • Workflow mapping
  • Information architecture
  • Wireframes
  • Interface design
  • Design system

Screens

  • Dashboard
  • Device list and map
  • Device detail
  • Profiles
  • Remote control