Visibility policies below are verified against Admin and member-app code. Member-facing wording may vary by brand translation files.
Attribute visibility and groups
Visibility policy and “editable on screen” group options
Reference status
Visibility options
The Visibility dropdown on display settings sets the default policy for who sees stored values.
| Option in Admin | Plain meaning | Typical use |
|---|---|---|
| Public | Visible to the member, matchmakers, and the other person in an active introduction (when the app shows profile attributes). | Standard bio fields shown on profiles and in shidduch sheets. |
| Private | Visible to the member and admins; hidden from partners and default matchmaker attribute tables. | Personal notes the member sees but does not share on introductions. |
| Hidden | Technical or internal field—not shown in normal profile UI. May still drive matching or automation. | System flags, imported metadata, or attributes only used in Admin reports. |
| SMEAndMe | Visible to the member and matchmakers (SME role); not shown to the introduction partner by default. | Matchmaker-only context on a profile the member can still edit. |
| AutoFilled | Values are written by the system or questionnaires; members do not edit directly in the app flow. | Computed or back-office-filled fields. |
| AdminVisible | Only admins see the stored value in Admin tools; hidden from member and matchmaker apps. | Operational metadata attached to profiles. |
| SMEOnly | Only matchmakers and admins see the value; hidden from the member’s own profile UI. | Internal matchmaker notes mapped as attributes. |
| S-Manager visible | Only visible in Admin, and only to staff with the S-Manager permission on the attribute screen; hidden from regular admins, matchmakers, members, and partners. | Sensitive fields that only senior/super managers should see or set. |
| Hidden from SME | Visible to the member, admins, and their introduction partner—same as Public, except matchmaker (SME) apps never see it. | Member-facing fields that matchmakers don’t need in their own tools. |
The attribute editor’s Visibility field has an info icon that opens the same breakdown as the audience matrix below.
Who can edit visibility: Only staff with S-Manager permission on the attribute screen may set or change S-Manager visible. Other admins see that option disabled when the attribute is already S-Manager-only.
Attributes list filter: The attributes list includes a Visibility column and dropdown filter so you can audit policies in bulk. Hidden attributes are excluded from the reorder list.
Who sees each level
Checkmarks match the info popup on the attribute editor Visibility field.
| Visibility level | Admin | Matchmaker | Member (self) | Introduction partner | Notes |
|---|---|---|---|---|---|
| Public | Yes | Yes | Yes | Yes | Standard profile fields shown in apps and shidduch views when visibility rules pass. |
| Private | Yes | No | Yes | No | Member sees their own value; partners and default matchmaker tables do not. |
| Hidden | No | No | No | No | Not shown in normal profile UI; may still drive matching or automation. |
| SMEAndMe | Yes | Yes | Yes | No | Matchmaker context the member can still edit; hidden from introduction partner. |
| AutoFilled | Yes | Yes | No | No | System or questionnaire writes the value; member does not edit directly. |
| AdminVisible | Yes | No | No | No | Admin tools only — not in member or matchmaker apps. |
| SMEOnly | Yes | Yes | No | No | Matchmaker and admin only; hidden from member’s own profile UI. |
| S-Manager visible | S-Manager only | No | No | No | Senior managers with attribute-screen S-Manager permission only. |
| Hidden from SME | Yes | No | Yes | Yes | Like Public for member and partner, but matchmaker apps never show it. |
Privacy editable (separate toggle on the attribute): when enabled and your brand supports member privacy controls, members who can see the field may change who else sees it in the app. Tag rules can listen for attribute visibility changed events when members adjust privacy.
Attribute groups
Editable on screen assigns which profile bucket owns the field.
| Group | Plain meaning | When to choose |
|---|---|---|
| bio | Facts about the member (who they are). | Answers that describe the member and pair with preference fields in matching. |
| pref | What the member wants in a partner. | Preference questions; often linked to a bio attribute via bio–pref relations. |
| setting | App or account settings stored as attributes. | Notification toggles, feature flags, or non-matching configuration. |
| external | Values filled from outside questionnaires (imports, tag rules, integrations). | Tag-rule keys, external lookups, or API-fed fields. |
| aiAnalysis | AI-generated or AI-scored profile data. | Fields populated by AI pipelines rather than direct member input. |
| none | No group—shown in generic attribute lists. | Legacy or auxiliary fields that do not fit other buckets. |
| other | Miscellaneous profile data outside bio/pref split. | When the value is member-visible but not part of standard bio/pref matching tables. |