How to manage profile and account preferences

Documentation
, , , ,
1

How to manage profile and account preferences

This guide explains how to maintain profile details and communication preferences so account ownership and notifications stay reliable.

Required access: Authenticated customer account.

When to update account preferences

Update these settings when ownership changes, team contacts change, or you want to adjust communication noise and operational alerts.

How to manage profile details

  1. Open dashboard profile settings.
  2. Verify display name and contact details.
  3. Save updates and refresh to confirm persistence.
  4. Recheck that account identity is clear for support and billing actions.

How to manage email preferences

  1. Open dashboard preferences.
  2. Review available email categories.
  3. Enable required operational notifications.
  4. Disable low-value notifications to reduce noise.
  5. Save changes and verify with a test notification where possible.

Verification checklist

Confirm:

  • Profile details are current
  • Notification settings match your team workflow
  • Critical account/billing notifications remain enabled
  • Preference changes persist after logout/login

Related guides

  • How billing and subscription management works
  • How to use support tickets

Exact route paths

  • /dashboard/profile
  • /dashboard/preferences
  • /dashboard/settings

Expected UI state after each step

  • Step 1: Profile page shows current account metadata.
  • Step 2: Preference toggles can be changed and saved.
  • Step 3: Updated values persist after reload.
  • Step 4: Notifications align with selected preferences.

Screenshot map (step-level)

  1. Profile and settings context

  2. Preference and operations overview

Operational objective

Complete the “How to manage profile and account preferences” workflow with predictable outcomes, clear auditability, and repeatable execution quality across team members and projects.

Acceptance criteria (all must pass)

  • The workflow can be completed without missing permissions or blocked route access.
  • All required dashboard routes load successfully for the active account.
  • The expected UI states are visible in the same order as documented.
  • At least one end-to-end validation confirms the process works in practice.
  • Evidence artifacts are captured for support and audit handoff.

Routes that must be reachable during validation:

  • /dashboard/profile
  • /dashboard/preferences
  • /dashboard/settings

Failure modes and exact remediation

  • Permission failure: Recheck plan/license entitlements and retry after session refresh.
  • Route loads but action is missing: Confirm feature flags/plan gates and selected context (site/license).
  • Action runs but state does not update: Refresh, re-open the relevant page, and verify from history/log view.
  • Partial success in multi-step operations: Retry only failed sub-steps and preserve successful state.
  • Cross-page mismatch: Reconcile with dashboard history and capture timestamps before escalation.
  • Persistent failure after one controlled retry: Open support ticket with full evidence package.

Evidence package for support escalation

Collect all items before escalating:

  • Account email and user role
  • Affected route path and exact action taken
  • Site URL, product/license identifier (if relevant)
  • Timestamps for first failure and latest retry
  • Expected result vs actual result
  • Screenshot set listed below

Screenshot evidence checklist

  • Step 1: Profile and settings context
  • Step 2: Preference and operations overview
  • One screenshot with visible timestamp (system clock/browser tab)
  • One screenshot showing route context or breadcrumb
  • One screenshot showing final persisted result
  • Replace any generic placeholder/demo visuals with real environment captures

FAQ

Can I skip steps if I already know this workflow?

Skip only after all acceptance criteria still pass. If any criterion fails, run the full sequence exactly as documented.

Should I run this in production first?

Use staging first for medium/high-impact changes. Promote to production only after validation evidence is complete.

What if my screen does not match the guide exactly?

UI can vary by plan and feature access. Validate route access, plan gates, and expected state outcomes instead of pixel-perfect layout.

How many retries should I perform before escalation?

Run one controlled retry after checklist validation. If failure persists, escalate with full evidence to avoid hidden side effects.

Who owns this guide operationally?

Customer Success owns this guide and its periodic review cycle.

Guide metadata

  • Difficulty: Beginner
  • Estimated completion time: 10-15 minutes
  • Owner: Customer Success
  • Last reviewed: 2026-03-18