Reference (partial) — Keys below are traced from the member app and availability jobs (October 2026). Rows marked verified have a clear member or matching effect. Other keys may appear from brand-specific Add user setting flows — treat unknown keys as TBD until you confirm with engineering.

Overview

Each end user has a small settings map on their profile: string, number, or boolean flags the member app or staff tools save. On view introduction, you see a read-only snapshot for the initiator and responder at page load — useful when a ticket mentions premium preferences or introduction limits.

These keys are not questionnaire answers. They live beside bio/pref attributes and can still affect matching, comms language, pre-validation, and some member-app screens.

The full editable table (add, update, delete any key) is on View end user → Profile settings. Introduction detail only exposes delete per row for support cleanup — there is no Add user setting button on the introduction page.

Where Admin shows settings

ScreenSectionEditable?
View introduction First Asked Settings and Responder's Settings (below decline history) Delete row only — removes that key from the member profile immediately
View end user Settings card Add/Update Setting (pick from the setting attribute group) plus delete per row

Column labels: Key (Title Case in the grid), Value (stored text), Actions (delete).

What staff can change

ActionEffectCaution
Delete on introduction detail Removes one key from that member’s profile (not from the introduction row). Page refresh shows the key gone. Member can set the preference again in the app. Use only when ops intentionally clear a bad value.
Add/Update Setting on end-user profile Writes or overwrites a key from your brand’s setting attribute catalog. May gate pre-validation when rules reference that key. Does not replace bio/pref answers.
Member My account premium toggles Member saves keys such as numberOfMatches or whosFirst through the app; Admin mirrors the stored value. Some chat features still check subscription plan features — see catalog notes for readReceipts / sendMedia.

Common keys

Exact spelling in the Key column (camelCase). Your brand may show additional keys from custom setting attributes.

Key (verified spelling)Typical valueMember / matching effectSupport notes
numberOfMatches Integer (for example 3, 8) verified — Raises or lowers how many open introductions count against the member’s Available Introductions on the profile (overrides plan default when set). Recalculated when the member saves the preference. Compare with App Settings max-introduction limits. Tooltip reason codes on the profile still apply for other blockers — see no new suggestions.
whosFirst first, second, random, or premium chip values me / other verified — Member premium preference for who should act first on a suggestion; may show a chip on the partner profile when reveal who first is enabled. Staff Swap Direction on pending approval only warns for first on initiator or second on responder — not for me / other. See Whos First.
hidePartnerImage true / false (sometimes stored as string "true") verified — When true, the member app hides the partner’s photo on the public profile view for that user. On Shidduch request detail, the image-policy chip above the other person’s avatar may read as will be shared (staged reveal) because the viewer turned off partner photos — not because the photo owner blocked sharing. Does not remove photos from Admin score tables.
feelBrave Small integer (for example 2) verified — When your brand enables feel brave and sets a non-zero brave factor in Algorithm settings, the matcher lowers that member’s personal bio-score floor by feel brave × brave factor when deciding in-app suggestions (veteran rules still apply separately). Not shown as its own column on potential match scores — compare stored bio % with Algorithm minimums and this key when a member is “just below” the cutoff. Deleting the key restores the default floor on the next suggestion run.
walkthroughState JSON map of tutorial flags (for example {"homeTab": true}) verified — Member app stores which in-app coach marks / walkthroughs the user already saw; syncs across devices when they log in again. Rare on introduction tickets. Safe to leave alone unless support resets onboarding UX — clearing local app cache does not reset server flags.
language Language code (for example en, he) verified — Used when the system picks notification / comm language for that profile. Changing in Admin is rare; confirm brand locale policy before editing.
readReceipts true / false Stored when the member toggles read receipts in premium account settings. verified — Matched chat UI gates read-receipt display on subscription plan features, not this stored flag alone. If ticket says receipts missing but key is true, check plan tier and read receipts app feature — not only party settings.
sendMedia true / false Persisted from premium toggles. verified — Chat media upload in matched conversations is allowed when plan includes send media (customer-support chat always allows upload). Same plan-vs-stored caveat as read receipts.
deleteMessages true / false Persisted from premium toggles. verified — Delete-message actions in chat require plan feature delete messages. —
partnerExtendedData Often appears only when the member’s plan includes this benefit (checkmark row in My account) verified — Premium benefit tied to subscription tier. Your brand must also enable the extended data (partner) app feature before partner-side extended fields can appear in the member app at all. Which bio/preference rows unlock is configured per attribute on your brand (not a single global list). Admin may still see the key on the profile after a plan change. If a member cannot see partner extended fields, check plan tier, app features, and attribute visibility — not only this key.
yourExtendedData Plan benefit indicator (checkmark in My account when the plan qualifies) verified — Same pattern as partner extended data, for your own extended profile fields. Requires the extended data (me) app feature on the brand plus attributes configured for extended visibility. Members do not toggle this key like read receipts — it reflects plan eligibility. Staff rarely edit manually.
Brand-specific keys From the setting attribute group (see Brand setting attributes) May participate in pre-validation when rules reference the key. Attribute name becomes the stored key. Confirm meaning with your brand’s attribute catalog before writing values in Admin.

Brand setting attributes

How custom keys appear on profiles beyond the common premium keys above.

verified — Each brand defines extra profile keys as attributes in the setting group (same family as questionnaire attributes, but grouped for settings). Staff add them on View end user → Profile settings with Add/Update Setting.

Add user setting dialog

FieldWhat to enterEffect on save
Setting (required) Pick one row from your brand’s setting attribute list (labels come from the attribute’s Admin display name). Chooses which Key will be written. The stored key is the attribute’s internal name (camelCase), not the label you picked.
Response Shown when the attribute has two or more predefined answers. Saves the selected answer’s stored id (txtId) as the value — same as questionnaire choice ids.
Value / custom text Shown when the attribute has zero or one predefined answer. Saves the text you type as the value (numbers, language codes, true/false, etc.).
Add/Update Confirm when Setting is chosen and either a response or a non-empty value is present. Merges into the profile’s settings map immediately (overwrites an existing key with the same name).

Cancel closes the dialog without saving. There is no separate Edit row action — add the same setting again to overwrite the value, or delete the row to remove the key.

Pre-validation rules that reference setting keys evaluate the stored value at runtime (alongside questionnaire answers). See Pre-validation and rules.

Premium plan vs stored value

Why a key can be true in party settings but the member still cannot use the feature.

Key familyWhat Admin showsWhat still gates the member app
readReceipts, sendMedia, deleteMessages Boolean stored on the profile when the member toggles premium account options. verified — Matched chat also checks whether the subscription plan includes read receipts, send media, or delete messages. Plan missing → feature off even if the key is true.
partnerExtendedData, yourExtendedData Checkmark rows in My account when the plan tier qualifies. verified — Brand App Features must enable extended data (me/partner). Individual attributes still control which fields appear.
numberOfMatches, whosFirst Interactive controls when the plan includes the benefit. Plan tier sets the max introductions picker ceiling; saving still writes the chosen value to party settings.

Support playbooks: Partner photo hidden (separate key hidePartnerImage) · Swap direction vs whosFirst.

Whos First

Most common support question on party settings — ties to swap direction on pending introductions.

Value in AdminPlain meaningStaff swap on PENDING APPROVAL
first on current initiator Member asked to stay proposer / go first. Extra confirmation dialog before Swap Direction.
second on current responder Member asked to stay responder. Same confirmation dialog.
me / other verified — Premium chips in My account save these spellings (not first / second). No Admin warning today — read the exact Value column before assuming a conflict.
random or empty Default premium preference — no fixed proposer. Swap runs immediately (no who-goes-first warning).

Playbooks: view introduction → Swap direction · swap direction on pending approval.

Pre-validation and rules

verified — When a questionnaire, group, comm, or attribute rule references a setting key, the engine evaluates the current value on the profile’s settings map (alongside questionnaire answers). A failed rule can hide Lora steps, block automated group attach, or skip a comm send — same family of behavior as pre-validation.

Party settings on introduction detail are a diagnostic snapshot during a ticket; changing rules happens on the attribute, group, or content editor — not on this table.