Sensitive attribute

Toggle on the Display card — not on the settings card.

Mark an attribute Sensitive when its values must be stored separately from normal profile attributes (for example government id numbers or highly restricted fields).

  • Sensitive attributes cannot be used in group attached attribute rules.
  • The first time you enable sensitivity on save, Admin may shorten the attribute’s internal name and register a dedicated identity-provider field — confirm with engineering before toggling on production attributes that already have data.
  • Visibility and matching still respect the attribute’s policy; sensitivity is an extra storage partition, not a substitute for Hidden or S-Manager visible.

Text and pickers

FieldWhat to enterEffect
Admin name Short label for Admin lists and headers. Overrides display name in backoffice tables (including the attributes list Name column) without changing member-facing translation text.
Related batch A questionnaire from the brand. Links the attribute to a questionnaire context (for example jump-to-questionnaire actions in matchmaker views). Does not auto-run the questionnaire.
Search also One or more other attributes. When searching profiles by this field, also match values stored under the selected attributes (combined lookup).
Admin attribute paired Another attribute. Admin treats the pair as one logical field (for example bio + duplicate pref column). Used when resolving preference/bio columns in introduction attribute tables.
Override attribute Another attribute. When this attribute is answered “rather not say”, matching uses the selected attribute’s stored value instead.
Profile search rank None, A, B, C, or D (A = highest weight). Controls how strongly this attribute contributes to free-text profile search in Admin. After bulk rank changes, click Rebuild profile search index on the same settings card (rebuilds the brand-wide search index — may take a moment on large brands).
MM filter category Section title text. Optional heading for this attribute on the matchmaker singles filter screen when MM filterable is on.
MM filter ordinal Integer; lower numbers appear higher. Sort order among optional filters on the matchmaker singles filter.

Toggles

ToggleWhen onMember / matching effect
Important deal breaker Attribute participates in deal-breaker filtering. Potential-matches list can hide rows with many deal-breaker mismatches when showDealBreakers filter is on. “Brave” member settings may bypass some deal breakers when the brand enables that feature. See potential match scores → deal breakers and introduction soft deal breakers for near-miss tolerance.
Soft deal breaker Narrow miss tolerance on this attribute. Instead of removing the pair outright, the matcher may surface a close but blocked suggestion. Requires margin — see Soft deal breaker.
Pending on tolerance Partial tolerance match may send intro to pending. Applies when brand introduction mode is “no tolerance” and scoring relied on tolerance for this attribute.
Compatibility (singles app) Bio attribute may show as a chip on suggestion public profiles. Requires brand feature for compatibility section. Enables optional Pre-Validation rules for when the chip appears (evaluated on the viewing member).
Clearable Member can remove the value in the app. Empty state allowed where the question supports clearing answers.
MM filterable Matchmakers can filter singles by this attribute. Exposes the field on the matchmaker mobile/web singles filter UI.
Resume include Field included in exported / printable resume views. Member resume PDF or share sheet includes this attribute when the brand supports resumes.
Revert to pending Changing the value can move related workflow to pending. Used for attributes that should trigger re-review when updated (brand/workflow dependent).
Admin highlight Show in end-user profile header in Admin. Ops see the value at the top of the member detail page without scrolling.
Append to existing New answers add to the array instead of replacing. Multi-value attributes (for example tags) grow rather than overwrite on each save.
Notify on new response Admins receive notification when value changes. Alert path for sensitive or compliance fields—confirm notification channel with your brand admin.
Decline reason Preference values appear in decline-reason text for the paired bio attribute. Introduction decline copy can cite this pref when explaining why a match was declined.

Soft deal breaker

Turn on Soft deal breaker when a preference mismatch that is only slightly outside range should still be visible to ops as a near-miss, rather than disappearing from suggestion flows entirely.

FieldWhat to enter
Soft deal breakerToggle on the attribute settings card.
Soft deal breaker marginNumeric tolerance — for age/height-style attributes, typically 1 (one year or one inch). Appears only when soft deal breaker is on.

Hard deal-breaker lists on potential match scores still apply for full misses. Soft deal breakers affect how narrowly-missed pairs are classified in the matcher and which attribute names appear on view introduction → Soft deal breakers after the responder answers the check-in.

Compatibility pre-validation

When Compatibility (singles app) is on for a bio attribute, an extra Pre-Validation editor appears below the toggles. Rules control whether the compatibility chip shows on a suggestion profile for the viewing member.

Requires the brand compatibility section app feature. Same AND/OR group semantics as questionnaire pre-validation — see pre-validation guide. Turning compatibility off clears these rules.

Pair with bio–pref relations so the chip compares the member’s answer to the partner’s preference column in the member app.