Overview

Open this page by clicking any row in the End Users list. It shows everything about one member: their profile, questionnaire answers, status history, introductions, and more.

What you can see and do depends on your role. Some sections are visible only to managers; others require specific feature flags to be enabled for your brand.

Page sections

Navigate using the left sidebar. Not all sections are visible for every role or brand configuration.

SectionWhat it containsVisibility
Profile and StatusPhoto, name, and status control.Always visible
Personal DetailsContact information and core profile fields.Always visible
Free Text BioThe member's free-text about-me and looking-for text, plus optional staff review flags. See Free text review flags.Admin-only
AI Analysis AttributesAI-scored bio and preference traits with optional reasoning text. See AI Analysis Attributes.Admin-only; when AI analysis attributes exist on your brand
Bio and PreferencesQuestionnaire-derived bio and preference attributes.Always visible
SettingsProfile-level settings (for example, notification preferences, matching behaviour flags).Admin-only
Package DetailsPremium subscription information.When the premium feature is enabled
Questionnaire DetailsPredictor and scoring data from completed questionnaires.Admin-only; requires Customer Support or Brand Manager access
Personal ImagesPhotos the member has uploaded.Always visible
Profile CommentsInternal staff notes embedded at the bottom of the Free Text Bio card (not a separate sidebar item).When the profile comments feature is enabled; admin-only
External InfoTag-rule tags and other externally computed attributes attached to this profile.Admin-only
Intro StatisticsHorizontal status chips (S-Manager can click to open filtered introduction history) plus read-only Member app snapshot rows that mirror the member app. See Introduction statistics and Member app snapshot.Admin-only
Decline ReasonsList of reasons given when this member's introductions were declined.Admin-only
Usage StatisticsApp usage data for this member.Admin-only
CS TicketsOpen ticket count plus one chip per ticket topic. See CS Tickets.Requires Customer Support page access
NotificationsEditable per-category notification channel toggles (not a send log). See Notifications.Requires Customer Support page access
DeviceLast known app session device metadata. See Device.Requires Customer Support page access
Predictor AI admin summaryAI-generated English predictor summary for admins with Regenerate. See Predictor AI admin summary.System admin; when predictors feature is on
ReferralsThis member’s referral code and referee list; mark confirmed referrals as drawn. See Referrals.Requires Referrals page access
GroupsGroups this member belongs to; option to add or remove them from groups.Admin-only; when the groups feature is enabled
Related SMEsMatchmakers linked to this member.Admin-only; when the related SMEs feature is enabled
Profile Status LogsFull history of every status change, with timestamp, reason, and who made the change.Always visible
Profile Notifications DocumentationDelivery audit for comms sent to this member (channel, event, errors). See Profile comm logs.Requires Communications page access

The Activity Information card (within the page) also shows: Created, Last Login, Last Suggestion, Active Since, Approved Since, and Available Introductions. If tag-rule tags are attached to the profile they appear here as clickable chips.

See Available Introductions below when support asks why a member is not receiving new suggestions.

Personal details

The Personal Details card — contact fields you can edit when you have permission.

Click Save at the top of the page after changing any field here. Saving also refreshes the member in the matching engine (same path as a normal profile update).

FieldWhat to enterEdit rules
First name / Last nameMember’s legal or display name shown across Admin and (when published) the member app.Requires Edit on End Users. Required before save when empty.
Email addressLogin email. Must look like a valid address (name@domain).Editable when you have Edit permission and either external-auth is off for your brand or this profile is marked Internal. Child accounts linked to a parent cannot change email here. Non-admins may see a masked value (first characters + domain).
Phone numberFull international number; Admin normalizes US numbers when you omit the country code.Same edit gate as email. Verification icon beside the field (see below).
Email / phone verification iconGreen check = staff marked verified; red outline = not verified. Click toggles verification without changing the address.Only when the field is editable. Does not send OTP to the member — ops use this after manual identity checks.
BirthdateDate picker for date of birth (drives age in the header).Same Edit + external-auth / internal rules as other personal fields.
LanguageRead-only English on this screen today.—
View ParentOpens the parent profile in a new tab when this row is a child account.Shown only when a parent id is linked.

Who can edit: Brand managers and above with Edit permission see full contact values. Other roles may see truncated email/phone. When external auth is enabled for your brand, live member accounts keep identity fields read-only in Admin unless you mark the profile Internal first (then personal details unlock for test/support edits).

AI Analysis Attributes

Read-only AI pipeline output — not questionnaire answers typed by the member.

This section lists attributes in the aiAnalysis group (and paired preference traits resolved through bio–pref relations). Columns:

ColumnWhat it shows
Add AttributeTrait name (human label from attribute configuration).
M ProfileAI-derived value about the member, with reported date when available.
Looking ForLinked preference-side value when a bio–pref relation exists.

When reasoning is stored for a row, hover or expand the cell to read the AI explanation text (stored separately from the displayed value).

A last calculated caption appears when the pipeline has run — shows when scores were last refreshed for this profile.

If no AI analysis attributes are configured, the section shows a short empty-state message instead of the table.

Configure which fields feed this section on Attributes (group aiAnalysis). See attribute groups reference.

Free text review flags

Quick staff checkboxes on the Free Text Bio card.

When your brand enables the matching app features, toggle buttons appear above the about-me and looking-for text:

Button (when enabled)What it records
Build reviewedStaff confirmed the member’s build / photo set meets brand guidelines.
Photo reviewedStaff reviewed profile photos (also reflected in the header badge when enabled).
About me reviewed / Looking for reviewedStaff reviewed the corresponding free-text fields.
ContactedStaff reached out to the member outside the app (ops tracking — does not send a comm by itself).

Each click toggles a stored flag on the profile and shows a success toast. Flags are visible to admins on the profile; they do not change matching scores directly unless a tag rule or communication references the underlying attribute keys.

Admins with edit access can also inline-edit about-me, looking-for, and admin insights text from the same card.

Profile comments (same card)

When the profile comments feature is on, a Profile Comments thread appears below the bio fields. Staff can add a note, edit or delete their own comments; admins can edit any comment. Entries show author and timestamp. This is internal only — members never see these notes.

My Profile & What I'm looking for

Tree table of questionnaire-derived bio and preference values — the main ops view of what the member answered.

Rows group under the questionnaire name (or attribute category when bio/pref grouped by category is enabled). Imported attributes appear under a dedicated Imported group. Predictor factor rows may append at the bottom when predictor external info exists.

Column / controlWhat it showsHow to use it
Group rowsQuestionnaire or category name (expand/collapse).Use Open All / Close All to expand every group at once.
M ProfileMember’s bio-side value with reported date when available. Red dot = admin external-info override on this attribute.Double-click to edit (opens attribute dialog). Hidden rows respect attribute visibility and pre-validation unless your role bypasses MM gates.
Looking ForLinked preference value for the same bio row.Double-click opens the populated preference attribute (or the first linked pref if several exist).
Declines (optional column)Info icon when the member declined introductions citing this attribute, or when deal-breaker importance is set.Hover for decline text or importance label. Only when show declines column feature is on.
Add / modifyToolbar button.Add a new bio/pref value or change an existing one via the same attribute picker used on external info.

Edit / add dialog fields: pick Attribute (bio-only filter when editing bio cells), then Response multi-select or free-text / height field depending on attribute type. Delete in the dialog clears the value. Saving calls the profile attribute API and refreshes questionnaire responses.

For read-only history of every answer row (including skip flags), use View Profile Responses at the bottom of the profile.

Activity Information

Quick dates and matching eligibility at the top of the profile — below the header photo and status.

FieldWhat it showsSupport notes
Created When this profile was first registered on your brand. —
Last Login Most recent app sign-in. —
Last Suggestion When this member last had an open suggestion where they were initiator (RAW / AVAILABILITY CHECK) or responder (INITIATOR APPROVED). Compare with potential matches Last Search: when diagnosing stale scores.
Active Since When the profile last entered active status. —
Approved Since When staff or automation last approved the member for matching. —
Available Introductions verified — How many new introduction slots the matcher considers open for this member right now (whole number, often 0 or 1). When the count is 0, hover the field — Admin shows a short reason (profile not active, open introduction blocking, inspection backlog, monthly cap, etc.). Full reason table: Support troubleshooting → No new suggestions.

When tag rules have written tags for this member, tag-rule chips appear at the end of this row — each chip links to the matching tag rule in Admin.

When status is DNF questionnaire (incomplete onboarding), an extra Onboarding stuck question indicator may appear with the question id and text; click it to open that questionnaire step in Admin.

Changing profile status, closing introductions, or clearing inspection backlog updates Available Introductions on the next matcher availability run — refresh the profile after you fix the underlying issue.

External Info

Tag-rule output, AI pipeline values, and manual admin tags — not questionnaire answers.

Open the collapsible External Info card (admin-only). Use the Source dropdown to filter which pipeline wrote each row:

Source (Admin label)What it meansTypical ops use
AdminManually added or approved by staff.Override a tag, seed a test value, approve a pending AI suggestion.
Tag rulesWritten by an executed tag rule.Segmentation counts from analytics — also shown as chips on Activity information.
AI agent / predictors / AI attributesAutomated inference or predictor jobs.Read-only diagnostics; re-run pipelines from their source screens when available.
Waiting for adminAI-mapped value pending staff approval before matching uses it.Review queue — approve flips source to Admin.

Table columns: Attribute name (human label + group), value (choice label when the attribute has responses), source, and Delete (removes that external-info row for this profile).

Add external info (card header): opens a dialog — pick any attribute, then either choose response(s) from the list or type a custom value (height fields use the feet/inches editor). File-upload attributes accept a URL string only. Confirm writes an Admin row.

Tag-rule tags on this table are the same keys referenced on Tag rules and in Singles Advanced Search external-info filters.

Settings

Key–value flags stored on the member profile — used by matching, comms, and pre-validation.

The Settings card lists every setting key currently on the profile. Values appear as plain text; keys are shown in friendly Title Case.

ActionWhat it does
Add/Update Setting (card header)Opens Add user setting (see field table below). Writes or overwrites one key on the profile’s settings map.
Delete (row action)Removes that setting key from the profile immediately.

Add user setting dialog

FieldWhat to enterAfter you confirm
Setting Required. Choose one attribute from your brand’s setting group (dropdown labels match attribute Admin names). The attribute’s internal name becomes the Key column on the card.
Response When the attribute has multiple predefined answers, pick one. Stores the answer id the app expects (same idea as a questionnaire choice id).
Value When the attribute has no multi-choice list (or only one answer), type the value. Stores your text as-is (for example a language code or true).

Confirm is enabled only when Setting is selected and either a response or a non-empty value is filled in. To change a value later, run Add/Update Setting again with the same setting — there is no inline edit on the grid row.

Settings here can gate pre-validation rules (merged at evaluation time). They do not replace questionnaire answers in Bio and Preferences.

On view introduction, the same keys appear per party as First Asked Settings / Responder's Settings (delete only on that page). Catalog of common keys and support notes: Profile party settings (reference).

Groups

Membership for this member — manual attach/detach from the profile (see Groups for group definition).

Visible when the groups app feature is enabled. The card shows every group this profile belongs to and lets you add or remove membership without opening the group detail page.

ControlWhat it doesSide effects
Add to GroupAttaches the profile to the chosen group.Writes attached attribute rules from the group onto the profile. Does not change profile status or run group pre-validation (manual Admin attach bypasses automated gates). See Groups → attach and detach.
Remove (row)Detaches from that group.Removes the join row only — attached attribute values are not automatically reverted.
Row clickOpens the group detail page in Admin.—

Columns: Name, description, type (Inclusive vs Exclusive), status chip, created date, actions.

Intro Statistics

Admin status chips at the top of the card — one count per introduction bucket.

The Intro Statistics card has two stacked areas: status chips (this section) and Member app snapshot (see below). They answer different questions — do not expect the numbers to match row-for-row.

AreaWhat it countsTypical use
Status chips (horizontal strip) Every introduction row for this member, grouped into Admin buckets (open suggestions, matched, approved, declined, ignored, terminated). “How many introduction records are in each workflow stage?” — same buckets as profile introductions filters.
Member app snapshot Unique partners — at most one outcome per other member, using the same rules as the singles app My introductions summary. “What does the member see on their phone?” — reconcile support tickets that quote app copy.

Chip labels abbreviate the first word and replace Me with the member’s first name — for example App. By Sarah for Approved by [name].

S-Manager users can click a chip to open Introductions History with ?filter=… pre-selected (for example ?filter=matched). Other roles see counts only — chips are not clickable.

Full chip meanings, URL filter values, and table behavior: Profile introductions → Intro statistics chips.

For one introduction’s full timeline (logs, chat stats, party settings), open view introduction — this card is a summary only.

Member app snapshot

Same unique-partner introduction counts the member sees in the singles app (My intros).

Below the status chips, Admin loads the same introduction-stat rules the member app uses on My introductions (singles app). Admin shows six rows (including Total); the member app shows five — it does not display the total line. Rows are read-only — there is no click-through and no edit action.

Refresh: Both sides query live data when the screen loads — reload this profile page after you change an introduction; ask the member to leave and reopen My introductions before comparing to an old app screenshot. Details: Member app snapshot → When numbers refresh.

Why totals can differ from the chips above: Chips count introduction records (two suggestions with the same partner = two toward a chip). The snapshot counts distinct partners and keeps only the best outcome per partner (for example a later match replaces an earlier ignore for that person). Suggestions the member was never shown in Lora chat generally do not count against either side in the snapshot.

Row labelPlain meaningWhen support quotes this
Total Partners with any counted outcome — excludes staff-rejected suggestions and system-only closures with no member attributed. “How many people have I interacted with on introductions?” in the app.
You declined This member said no — whether they were initiator or responder on that suggestion. Member insists they declined someone but Admin shows an open row — check the specific introduction status on profile introductions.
You didn't pick up This member did not follow through — missed deadline, marked busy, ended the suggestion, or froze it — only when the suggestion card was delivered to their Lora feed. “You didn’t pick up” in the app; auto-expired suggestions they never saw usually do not increment this row.
They didn't pick up The other person was shown the suggestion but did not move it forward (for example ignored or closed on their side) while this member’s outcome for that partner is weaker. Member waiting on a response — partner may still be in RAW on Admin while this row increments.
Matched Partners where both sides reached a match or post-match stage (including dating and engagement), or the couple later unmatch after having matched. Aligns with “we matched” in the app more than a raw open suggestion count.
Dated Partners where at least one in-person date was recorded on the introduction (date counter on the couple). Shidduch or dating brands — distinct from “matched” when no date number is stored yet.

Deep dive (priority rules, visibility in Lora chat, exclusions): Member app introduction snapshot (reference). When support tickets disagree with chips: Introduction support troubleshooting → Reconcile snapshot vs chips.

Personal Images

Profile photos — review, crop, approve, or remove.

Photos display in a horizontal scroll row. Counters at the top track deleted by user, replaced, and deleted by admin over the profile lifetime.

ControlWho can use itWhat it does
Status dropdown (per photo)Edit permission on End UsersSets moderation state — typically Pending, Approved, Not approved, or Approved as secondary. Saves immediately per image.
Edit (crop icon)Edit permissionOpens crop dialog; saving uploads new crop coordinates for that asset.
DeleteEdit permissionConfirmation dialog; marks image deleted-by-user and increments the deleted counter.
Upload An ImageEdit permissionUpload a new image file from your computer.
Photo Reviewed (page header)Edit permission; when photo review feature enabledSame as the review flag documented under Free text review flags — also available on the Personal Images card header in the live UI.

S-Manager users see every asset status in the dropdown. Other editors only see the four simplified moderation states; hidden internal statuses are filtered out of the row list.

Questionnaire Details

Per-questionnaire completion progress (admin + customer support access).

Requires Customer Support page access and Brand Manager on End Users. The table lists each questionnaire assigned to your brand:

ColumnMeaning
QuestionnaireQuestionnaire display name.
ProgressPercent of steps completed, or 100% when marked complete.
CompletedCheckmark when the member finished the batch.
Last AnsweredDate of the most recent answer in that questionnaire.

Use with Bio and preferences when a member is stuck mid-onboarding — progress here shows which batch is incomplete; the bio tree shows current attribute values.

Questionnaire DetailsPredictor AI admin summary
Who sees itCustomer Support access + Brand Manager on End UsersSystem admin; predictors feature
What it showsPer-questionnaire completion %, completed flag, last answered dateOne English AI narrative paragraph for staff
Data sourceQuestionnaire stats API (getQuestionnaireStats)External info predictorDescriptionsAi / attribute predictorDescriptionsAdminEn
ActionsRead-only tableRegenerate (AI) rebuilds AI copy
Typical use“Which batch is incomplete?” / onboarding stuck“Summarize this member’s predictor traits for a human reviewer”

See also Predictor AI admin summary — not a substitute for Profile responses (raw answer rows).

Predictor AI admin summary

System-admin card — English AI narrative stored on external info.

Shown when your brand enables the predictors app feature. Requires system admin on End Users (stricter than Questionnaire details).

On load, Admin reads external info source predictorDescriptionsAi and displays the predictorDescriptionsAdminEn attribute when present. Text preserves line breaks.

Regenerate (AI) calls the backend to rebuild predictor descriptions for this profile, shows a success or failure toast, then reloads the card silently.

When no text is stored yet, the card shows the empty-state message instead of body copy.

Predictor AI admin summaryQuestionnaire Details
OutputProse summary (traits, themes)Structured progress per questionnaire
Updates whenAfter Regenerate or pipeline runAfter each member answer save
PermissionSystem adminCS access + Brand Manager

For completion percentages and last-answered dates, use Questionnaire details. For individual answers, open Profile responses.

Referrals

Referral program activity for this member as referrer.

Requires Referrals page access. Loads referrals/stats?profileId=… for this profile.

When there is no referral code and no referee rows, the card shows No referral activity for this member.

Otherwise:

  • Referral code — this member’s share code when they are a referrer.
  • Referees table — one row per invited person who used the code.
ColumnMeaning
RefereeLink to the referee’s End User profile (name resolved asynchronously).
StatusReferee lifecycle label from the referrals service.
CreditCredit amount tied to this referral row.
Invited / Confirmed / DrawnTimestamps for invite, confirmation, and prize draw (dash when not yet reached).

Mark selected as drawn — enabled only when you tick rows that are confirmed and not yet drawn. Sends the selected referral ids to referrals/mark-drawn and refreshes the table.

Checkbox selection is disabled for rows already drawn or not yet confirmed.

Package details

Premium plan and token balance.

Shown when the premium app feature is enabled. Read-only summary:

  • Plan name and purchased date (from the member’s subscription record).
  • Tokens left — remaining M-tokens for in-app purchases (for example extending introduction deadlines).

Token purchases and plan changes happen in the member app or billing flows — this card does not edit balances.

Decline Reasons

Why this member declined introductions — from configured decline-reason questions.

Admin-only. Answers come from questionnaire steps listed in your brand’s decline reason questions app setting — not from free-text bio.

My declines — chips group identical short answers; the number is how many introductions used that reason. Click a chip to open the linked introduction(s) in a new tab.

Other reasons — free-text decline answers with a link per introduction.

On matchmaker brands, an Ended shidduchim table lists closed introductions with unmatch reason codes, optional other-reason text, and per-party reason columns. Row click opens the introduction.

Overlap with introduction detail decline history — use this card for a member-centric rollup; use the introduction page for one match at a time.

Usage Statistics

In-app engagement counters for this member.

Visible when the chat feature is enabled. Shows counts per event type:

MetricWhat is counted
Pic sentPhotos sent in introduction chats.
Video sentVideos sent in chats.
Audio call / Video callVoice or video calls placed.
BTIBreak-the-ice prompts started or answered (brand configuration).
Daily moodDaily mood check-ins submitted.

Read-only diagnostics — useful when validating chat activity alongside CS Tickets or introduction chat stats on the introduction detail page.

Customer support tickets

Support ticket counts for this member — summary chips, not the full ticket list.

Requires Customer Support page access (view permission). Collapsed by default.

Chips load from the profile tickets API:

  • Open — tickets in status 1 or 2 (open / in progress).
  • One chip per topic — count grouped by ticket topic name from your brand’s Ticket topic general codes.

Topics with zero tickets for this member still appear with value 0 once topic codes have loaded.

Open counts only New (status 1) and Open (status 2) — not Solved, Closed, or On Hold. See ticket statuses.

Workflow — from profile chips to the ticket queue

  1. Note which topic chip is elevated (or that Open is above zero) on this profile.
  2. Open Support → Customer Support (member-app queue).
  3. In Search, paste the member’s Profile ID (UUID from the profile header) — search matches tickets by profileId. You can also search by name, email, ticket number, or keywords in title/content.
  4. Optional: narrow with the Category or Status filters to match the chip you saw.
  5. Click a row to open ticket detail — use Single's Conversation to reply to the member. The Reporter column on the list links back to this profile for member-app tickets.

Reverse path: from ticket detail, open the reporter’s End User profile and scroll to Customer support tickets for the same rollup without re-counting manually.

Ticket assignment and guest replies may also appear in Profile comm logs (param customerSupportTicketAssigned / customerSupportGuestAdminReply).

Notifications

Member notification preferences — edit channel toggles per category.

Requires Customer Support page access. This is not Profile Comm Logs (delivery history lives in the comm logs card when you have Communications access).

Rows are notification categories; columns are channels enabled for your brand:

Category (when feature on)Channels shown
IntroductionsPush; plus Email / SMS / WhatsApp when each channel feature is enabled.
Chat messagesSame channel set when chat notifications feature is on.
SystemSame channel set when system notifications feature is on.

Push is always listed as a column. Email, SMS, and WhatsApp columns appear only when the matching app feature is enabled for your brand.

Click a boolean cell to toggle. Each change saves immediately via the notification-settings API (no page Save button). Cells without a stored setting render blank instead of a switch.

Use this when a member reports missing emails or pushes — confirm the relevant category/channel is still enabled before checking Profile Comm Logs for delivery errors.

Device

Last session platform metadata from the member’s profile session.

Requires Customer Support page access. Read-only chips from profileData.session.platform:

ChipSource field
SystemOS family (for example iOS, Android).
OS versionOperating system version string from the app.
App versionMember-facing app version.
BuildNative build number.
ModelDevice manufacturer and model concatenated.

Values reflect the last reported session, not a live device ping. Empty fields show blank chips when the member has not opened the app recently or the client did not send platform metadata.

View Questionnaire Answers

Separate read-only page — every stored questionnaire answer row.

From the profile bottom bar, click View Questionnaire Answers (all roles). Opens a dedicated table with:

ColumnMeaning
BIDBatch content id (step id in the questionnaire).
reportedWhen the answer was saved.
QQuestion text.
ResponseHuman-readable answer (choice labels when available).
Skip ReasonSingle-letter skip code when the member skipped the step.
BAIDBatch assignment id tying the answer to a questionnaire run.
SettingsTrue when the value was seeded from profile settings rather than a member tap.

Below the table, Attribute change log lists staff and system edits to profile attributes over time (separate from questionnaire response rows).

Jump to question

Support unblock for members stuck in DNF questionnaire status.

Bottom-bar action when the member’s status is DNF questionnaire and you have both S-Manager and Brand Manager on End Users.

Dialog fields:

  1. Questionnaire — pick any questionnaire on your brand.
  2. Question — active question-type steps only (draft or non-question rows are omitted to avoid backend errors).

Confirm moves the member’s Lora/onboarding pointer to that step. The server may reject the jump (already answered, non-chat questionnaire, wrong brand admin, etc.) — the dialog shows the error message returned.

Pair with the Onboarding stuck question chip on Activity information when you need to know which step blocked progress.

Changing status

The status control is in the Profile and Status section. To change a member's status:

  1. Select the new status from the dropdown.
  2. If the new status is Active, the change applies immediately — no reason is needed.
  3. For any other status (Suspended, etc.), a dialog opens asking for a reason. Enter a short explanation and confirm.
  4. The change is saved, and the new status appears in the header. The reason and timestamp are recorded in Profile Status Logs.

Changing status requires an Edit permission on the End Users page.

What gets recorded: Whenever the member’s profile status actually changes, a new row appears in Profile Status Changes (see below). Staff changes from this page always stamp who made the change. Automated changes from the member app or matching flows may show a Reason without a staff name when the system did not record an Admin user.

Profile Status Changes

Audit trail of every profile status transition for this member.

Open the collapsible Profile Status Changes card near the bottom of the profile (admin-only section). It loads automatically when you expand it.

ColumnWhat it shows
Date When the status change was recorded (local date and time).
Previous Status Status label before this change (from your brand’s profile status list).
New Status Status label after this change.
Reason Short explanation stored with the change. For staff updates this is what you typed in the status dialog (or empty when you set Active without a prompt). For some automated flows this may be a system reason code or snooze reason id translated to text.
Changed By Full name of the Admin user who changed status from this screen. Blank when the change came from an automated server path that did not attach a staff id (for example member self-service snooze or introduction side effects).

When rows appear:

  • Staff status change — You pick a new status on this profile and confirm (reason required except when moving to Active). The row includes your name in Changed By.
  • Bulk or import — Profile import templates that map status history columns can insert historical rows with optional legacy staff ids. Those appear here alongside live changes.
  • Automated status updates — Introduction engagement broken, group attach rules, member snooze/delete, and similar flows that change profile status write a row when the underlying status value changes. Reason may be filled from the system; Changed By is often empty.

Rows are ordered newest first. If the table is empty, this profile has no recorded status transitions yet (common for members who have never left their initial status).

Common automated reasons

The Reason column may show a short system phrase (translated for your brand) instead of text someone typed. Use this table when you are reconciling profile status with an introduction or group change:

SituationWhat you typically seeChanged By
Staff changed status on this profile The reason you entered in the status dialog (or blank when you set Active without a prompt). Your name.
Introduction marked ENGAGED or EXTERNALLY ENGAGED A phrase meaning the member became engaged through this introduction. Usually blank — automated when introduction status advances.
Introduction marked ENGAGEMENT BROKEN A phrase meaning engagement ended and the profile returned to active. Ops playbook: Engagement broken. Staff name when you changed introduction status manually; otherwise blank.
Introduction left ENGAGED or MARRIED for another closed status A phrase meaning the couple is no longer engaged/married in the system; profile returns to active. Usually blank unless staff drove the introduction status change.
Member attached to a group with a profile-status rule May reference the group or rule that set the new status (automated attach path only — manual Admin attach does not change status). Blank.
Member snoozed, deleted account, or returned from incomplete signup Snooze reason text, delete flow label, or “returned to draft” style wording depending on the path. Blank.
New profile created at signup Profile-created style wording on the first row. Blank.

This log is separate from Introduction status history on the introductions screens — use those logs when you need to audit a specific match row, and this section when you need the member’s overall profile status timeline.

Profile Notifications Documentation

Delivery audit — what the platform attempted to send to this member.

Requires Communications page access (view permission). Collapsed by default. Not the same as Notifications (preference toggles) or CS Tickets (support queue counts).

Loads the latest 100 rows from comm-logs?profileId=…&brandId=… for the current brand. Read-only table — no inline edit.

ColumnWhat it showsHow to use it
DateWhen the send was logged.Sort mentally newest-first (table order matches API).
ChannelPush, Email, SMS, WhatsApp, etc. (channel enum name).Match against the member’s notification toggles for that category.
EventTrigger family — for example Introduction update, Chat, Lora message, System, BO admin update, MM emails.Cross-check the communication template on Communications or trigger events reference.
ParamSub-type within the event — for example verify email, verify phone, ticket assigned, delayed execution.Narrows which template variant fired.
Communication IDNumeric comm template id when present.Open that comm in Admin → Communications → History for channel-level send history on the template.
Introduction uuid when the send was introduction-scoped.Jump to the introduction detail page for chat stats or status history.
ErrorProvider or pipeline error text/json when delivery failed.Non-empty = attempted but failed (bounced email, push token invalid, etc.).

Common support patterns

  • “Member says they never got the email” — Confirm Notifications still has Email on for that category; then look here for a row with channel Email. Empty table + toggles on → likely no trigger fired (check introduction status or comm pre-validation).
  • “Push works but email doesn’t” — Filter visually by channel column; errors on Email rows point to provider issues; missing Email rows mean the template skipped email or never ran.
  • CS ticket updates — Rows with param customerSupportTicketAssigned or customerSupportGuestAdminReply tie back to Customer Support workflows.

States: loading spinner; No communication logs found for this profile. when the query returns zero rows; red error text when the API fails.

Marking as internal

Internal profiles are test or staff accounts. They are hidden from the default member list and excluded from matching and statistics.

To toggle internal status, click Mark as Internal or Unmark as Internal at the bottom of the page. This button is visible to Brand Manager level and above. The change takes effect immediately.

When a profile is marked internal:

  • An Internal badge appears in red in the profile header.
  • The profile is hidden from the default end users list unless Show Internal is toggled on.
  • On brands that use external authentication, marking a profile internal also allows its personal details to be edited directly in Admin.

All actions

Top of page (requires Edit permission):

ActionWhat it does
SaveSaves changes made to the personal details and other editable fields on the page.
View Potential MatchesOpens the potential matches page for this member. Requires the Potential Matches page permission.
Introductions HistoryOpens all introductions for this member with bio/pref context and status filters. Requires View User Interactions Statistics page permission.
Calculate AI attributesOn the AI Analysis Attributes card header — re-runs the AI attribute pipeline for this profile and refreshes the table.
Build ReviewedMarks the profile's full build as reviewed. When the feature is enabled for your brand.
Photo ReviewedMarks photos as reviewed. Appears in the Personal Images card header. When the feature is enabled.

Bottom of page:

ActionWho can use itWhat it does
View Profile ResponsesAll rolesOpens a read-only view of all questionnaire answers for this member.
Make PrimaryBrand Manager; only for child accountsPromotes a child account to be the primary account for the parent.
Mark as Internal / Unmark as InternalBrand Manager and aboveToggles the internal flag. See Marking as internal above.
Link Child AccountAdmin; parent-type profilesOpens a dialog to link a child account to this parent profile.
Link Parent AccountAdmin; non-parent profilesOpens a dialog to link this profile to a parent account.
Unlink child account / Unlink from parentAdmin; parent or child accountsBreaks the parent–child link without deleting either profile.
Jump to questionS-Manager + Brand Manager; status DNF questionnaireOpens a dialog to move the member to a specific onboarding question (support unblock).
Delete End UserRequires Delete permissionPermanently deletes this profile. This cannot be undone.