Account settings

Overview

Account settings is where signed-in dashboard users manage their own Mallard Bay user profile and choose how they want to be notified while working in the outfitter dashboard. You open it from /account-settings in the admin dashboard. The page title in the UI is Account Settings and two areas are grouped there: Profile and Notification Preferences.

Notification choices are tied to the outfitter you currently have selected (your business context): the app loads and saves preferences for that outfitter together with your user account, not globally for every business in isolation.

Changing your Mallard Bay subscription, opening Stripe for payouts, switching portal type, or signing out stays in the profile menu in the header. Those flows are intentionally separate links from Account settings itself.

Prerequisites

• You must be signed in to the Mallard Bay admin dashboard.

• To load or edit notification preferences, the dashboard needs an active outfitter context (a selected outfitter). The preference query runs with that outfitter id; behavior when no outfitter is available is driven by routing and loaders in this codebase and is worth confirming in-product if anything looks stuck loading.

Step-by-step: Open Account settings

1. In the top header, open your profile menu (your account control on the main bar—not the sidebar).

2. Choose Account settings. You land on /account-settings.

Profile

The Profile section shows a guided form backed by Mallard Bay’s outfitter-profile configuration: your current user fields load into the form, you edit what you’re allowed to change, then confirm with Save.

From automated tests covering this surface, confirmed fields today include:

• Photo

• First name and last name

• Phone number

• Years of experience (stepper control)

• Bio

The exact widget layout may change with shared components; anything beyond those fields depends on @mallardbay/lib-shared-helpers (getOutfitterUserProfileFormConfig), which lives outside this dashboard repo—I did not enumerate every optional field here.

Saving runs the standard update user flow: a successful save shows Mallard Bay’s generic user update success toast; failures surface an error toast so you can retry.

Not verified on this page (do not expect it here): Email used to sign in, password changes, two-factor authentication, and other account-security controls are not implemented in src/pages/account-settings.tsx or profile-section.tsx in this repository. They may exist in other Mallard Bay apps or flows; if you need them, use your organization’s normal support or security path.

Notification Preferences

The Notification Preferences section lists topics in rows and channels (such as Email, SMS, Push, and Inbox) in columns.

• Row labels, optional descriptions, and which channel is available per topic come from a server-side catalog, not hard-coded copy in the dashboard—so you may see different topics over time without a dashboard update.

• If a topic does not support a channel, that cell is blank (no checkbox).

• SMS is labeled SMS in the header; other channel names are shown in title case (for example Email, Push, Inbox).

How to change a preference: Check or uncheck the box for that topic and channel. There is no separate Save control in this section; each toggle triggers an update to your notification settings (the UI uses optimistic updates so it should feel immediate, with errors reported if the server rejects the change).

How this connects to your work: Topics in the GraphQL layer include areas such as booking requests, booking updates, payments, payment reminders, leads, quote requests, form submissions, reviews, mentions, weekly digest, and system messages. The names you see in the table are the catalog labels returned for your account, which should map to those operational areas (bookings, leads, quotes, forms, payments, etc.).

Layout, navigation, and deep links

• The two sections use a responsive navigator with a section list and main content. On wide screens the section list is on the right.

• URL hashes select a section directly:

  • #profile — Profile

  • #notification-preferences — Notification Preferences

  Example: https://<your-dashboard-host>/account-settings#notification-preferences

Common pitfalls

• Looking for subscription or Stripe here: Request subscription changes and Stripe dashboard are profile menu items, not part of the Account settings page code path in this repo.

• Expecting profile to change the business or team: Profile updates your user record (the person signed in). Team membership, roles, and outfitter-level configuration live in other settings and flows.

• Notification matrix looks sparse: A blank cell means that channel is not offered for that topic in the catalog—not a bug in the table.

• SMS or email not arriving: This screen only sets whether you want that channel for a topic. Deliverability still depends on Mallard Bay’s routing, your contact information, and integrations such as SMS or custom email domain elsewhere in the dashboard. This repository does not document server rules for when SMS is allowed if SMS is not connected.

• Multiple businesses: Because preferences are stored per outfitter context, if you manage more than one outfitter and switch between them, re-check notification preferences for each business if you want them aligned.

Related workflows

• Bookings, quotes, leads, forms, payments: Notification topics are aligned with these operational areas; tightening noise here reduces alerts from those workflows without turning off the underlying features.

• Integrations (SMS, custom email domain): If you use those features, they support how Email or SMS notifications can be delivered in practice.

• Team members: Each team member maintains their own profile and own notification matrix for a given outfitter—useful when only some people should get booking or payment alerts.

What this article did not verify from the repo alone

• The full profile field list from @mallardbay/lib-shared-helpers beyond what tests exercise.

• Business rules for which notification topics appear, when SMS is allowed, or how Push vs Inbox map to concrete client apps or in-product notifications—that logic is enforced by Mallard Bay’s backend and catalogs.

• Login credentials management (email, password reset, SSO): not implemented under account-settings in this codebase snapshot.