Designing Settings as a System Control Layer

UX Architecture for Complex, Data-Dense Systems

Overview

In complex systems, settings are often treated as an afterthought —
a fragmented collection of options disconnected from how the system actually works.

In this project, settings were redesigned as a system control layer —
a structured interface that allows users to manage behavior, preferences, and system logic across multiple domains.

Problem

The product operates in a data-dense environment, where users:

  • work across multiple modules simultaneously
  • rely on consistent system behavior
  • need fine-grained control over execution, notifications, and visibility

The existing approach to settings created several issues:

  • lack of structural consistency across configuration areas
  • limited control over system behavior (especially notifications)
  • poor discoverability of key settings
  • no clear relationship between settings and system outcomes

Settings existed as UI — not as part of the system architecture.

Challenge

Design a scalable settings architecture that:

  • supports multiple system layers (navigation, notifications, user preferences)
  • enables granular control without overwhelming users
  • integrates with the rest of the system (not isolated)
  • remains usable in a high-density, professional environment

Approach

1. Treating Settings as a System Layer

Instead of designing a single “settings page”,
settings were defined as a control layer affecting:

  • navigation behavior
  • notification delivery
  • user-level customization
  • system-wide logic

This shifted the role of settings from passive configuration to active system control.

2. Defining Entry Points

Settings were made accessible through two key entry points:

  • Top Navigation — fast, global access
  • User Panel — contextual, user-specific control

This dual-entry model ensures:

  • quick adjustments during workflow
  • deeper configuration when needed

User Profile
Profile info

3. Modular Architecture

The system was divided into clearly defined configuration modules:

  • Profile — identity and account-level data
  • Notifications — system feedback control
  • Navigation — interface behavior and structure
  • System / Dashboard Settings — operational preferences

Each module represents a domain of control, not just a UI section.

4. Structural Layout

The layout follows a consistent pattern:

  • Left panel → structural navigation
  • Main workspace → configuration content

This separation ensures:

  • fast orientation
  • reduced cognitive load
  • scalability for additional modules
Navigation Settings
Notifications Settings

5. Granular Control Model

One of the key design challenges was enabling multi-channel control.

Users can configure notifications per type across channels:

  • System (in-app)
  • Email
  • Desktop

This creates a matrix of control:

  • what events trigger notifications
  • where they are delivered
  • how users are informed

The goal was to balance:

  • flexibility
  • clarity
  • speed of interaction

6. Interaction Model

The interaction model was designed to:

  • minimize friction (toggles, inline actions)
  • support quick scanning
  • avoid modal-heavy workflows

Key principles:

  • direct manipulation over multi-step flows
  • consistent patterns across modules
  • immediate feedback for changes

7. Relationship to Other Systems

Settings are tightly connected to:

  • Navigation system → affects visibility and structure
  • Notification system → defines feedback logic
  • User panel → central access layer

This ensures settings are not isolated —
they actively shape system behavior.

Favourites

Key Design Decisions

  • Treat settings as system architecture, not UI
  • Use modular domains instead of long forms
  • Enable granular control without fragmentation
  • Maintain consistency across all configuration areas
  • Integrate settings with core system flows

Design Principle

Settings are not a place.
They are the interface through which users control the system.

Outcome

The redesigned settings system:

  • provides clear and structured control over system behavior
  • reduces cognitive load in complex environments
  • enables scalable expansion of configuration features
  • aligns settings with real system logic and workflows

Most importantly, it transforms settings from a passive UI into a functional control layer.

 

System Context

This notification system is part of a larger UX architecture including:

  • top navigation (control layer)
  • side navigation (system structure)

Together, they create a cohesive system that supports both orientation and decision-making.

 [See Figma Link]

What This Case Demonstrates

  • system-level UX thinking
  • architecture design for complex products
  • ability to structure large-scale configuration systems
  • integration of UI, behavior, and system logic

© Zofia Szuca 2024
Brand and product designer