Settings Page Architecture and UX

You are a settings UX designer who has redesigned settings for products used by millions, reducing settings-related support tickets by 70%.

Product type: [SAAS/MOBILE APP/DESKTOP APP/BROWSER EXTENSION]
User roles: [SINGLE ROLE/ADMIN+MEMBER/MULTI-ROLE HIERARCHY]
Settings categories: [LIST MAJOR SETTINGS AREAS]
Current problem: [USERS CAN'T FIND SETTINGS/TOO COMPLEX/NO ORGANIZATION]
Platform: [WEB/IOS/ANDROID/DESKTOP]

Design a complete settings architecture:

**1. Information Architecture**
- Settings categories (logical grouping, not feature-based)
  - Account & Profile
  - Appearance & Display
  - Notifications
  - Privacy & Security
  - Integrations & Connected Apps
  - Billing & Subscription
  - Team & Permissions (if multi-user)
  - Data & Storage
  - Advanced / Developer
- Category icons and descriptions
- Navigation pattern (sidebar, tabs, or sectioned page)

**2. Settings Page Layout**
- Navigation sidebar (persistent, collapsible on mobile)
- Content area with section headers
- Setting item layout: label, description, control, current value
- Search within settings (for products with 50+ settings)
- Breadcrumb for deep settings pages

**3. Control Types and When to Use Each**
- Toggle: binary on/off (instant save)
- Radio group: mutually exclusive options (2-5 choices)
- Dropdown/select: many options (6+)
- Text input: freeform values (with validation)
- Slider: range values (volume, threshold)
- Color picker: theme customization
- File upload: avatar, logo
- Multi-select: selecting from a list

**4. Save Behavior Strategy**
- Auto-save (instant): for toggles, dropdowns, non-destructive changes
- Explicit save (save button): for forms, multi-field changes
- Confirmation dialog: for destructive or high-impact changes
- Undo option: for accidental changes (toast with "Undo")
- Changed indicator: visual cue when unsaved changes exist
- Leave page warning if unsaved changes

**5. Dangerous Actions Section**
- Visual separation (red zone, warning border)
- Actions: delete account, reset data, revoke access, change ownership
- Confirmation pattern: type to confirm ("type DELETE to confirm")
- Cool-down period information
- What will be lost (explicit data impact)
- Alternative suggestion before destructive action

**6. Permission-Based Visibility**
- Which settings each role can see
- Which settings each role can modify
- Read-only state for visible but non-editable settings
- Admin override indicators
- Locked settings with "contact admin" message

**7. Mobile Settings Adaptation**
- iOS-style grouped tables or Material cards
- Navigation: drill-down stack (not sidebar)
- Native controls (system toggles, pickers)
- Biometric confirmation for security settings
- Deep link support (link directly to a specific setting)

**8. Help and Context**
- Inline help text under each setting
- Tooltip for complex settings
- "Learn more" links to documentation
- Default value indication ("Recommended" badge)
- What this setting affects (impact description)

Provide exact layout specs, control selections for each setting type, and copy for labels, descriptions, and confirmation dialogs.