> For the complete documentation index, see [llms.txt](https://flapjax.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://flapjax.gitbook.io/docs/your-data/people/understanding-the-person-profile-page.md).

# Understanding the person profile page

*Article · Collection: People*

The person profile, also called the person detail page, is your single view of one contact. Who they are, what they have done, which labels and records attach to them, and the notes your team has left. This article explains each part and where its information comes from.

> Gaming setups sometimes call this the "player profile". It is the same person detail page for every use case.

## Opening a profile

Click any person in the People list. You can also open one from a report, a label or a search.

Move to the next or previous person in your current list without going back. That helps when you work through a filtered set.

## The header

The top of the page carries the person's name and the quick actions your permissions allow:

* **Enrol in sequence** starts a sequence for this person.
* **Add label** attaches a label.
* **Send email / SMS** sends a one-off message.
* The overflow menu copies the person's external ID or page link, or deletes them.

## The properties panel

The side panel holds the editable properties. Standard fields sit there: name, email, mobile, date of birth, language. So do the person's **consents** for email, SMS and push, plus your custom attributes.

Edit inline. Flapjax tracks your changes, shows an unsaved indicator, and saves on Cmd/Ctrl-S. Relationship attributes link to related records, and you can click straight through.

## The tabs

**Overview** gives you the summary at a glance: key IDs and dates, a preview of recent activity, the person's labels, recent notes and associated records. The recent-activity list comes from the person's logged history.

**Activity** holds the full timeline of what has happened to and for this person. Automation runs, messages, changes. This tab is your audit trail.

**Labels** lists the labels on this person and when each one arrived. Add and remove labels here. Smart labels come and go on their own as data changes. See [How labels are applied in real time](/docs/your-data/labels/how-labels-are-applied-in-real-time.md).

**Records** collects the records across your stacks that reference this person, grouped by stack. One view of everything connected to them.

**Notes** keeps your team's free-text notes. Notes auto-save as you type.

## Where the numbers come from

Most of the page is the person's stored data and their logged activity. Three points are worth knowing:

* **Labels** show the live state, smart labels included. A person whose data just changed already has the right labels.
* **Activity** is the running log of events and automation actions for this person, written as they happen.
* **Associated records** are the records that reference this person right now.

Your own setup may compute per-person summaries such as totals, tiers or scores. Those live as attributes or referenced records that your automations maintain, and they appear in the properties panel or the Records tab like any other data. Flapjax stores and displays them. Your automation configuration produces them.

## Sending from the profile

The send actions in the header go through your connected providers. They respect the person's consent settings and any campaign tagging you use.

A message you send here goes out asynchronously. It appears in your Communications log with its delivery status as that status progresses: sent, delivered, opened and so on.

## Permissions

Your role decides what you can do here. Viewing needs *people: view*. Editing, sending, enrolling, labelling and deleting all need *people: manage*. Flapjax hides any action you lack the permission for.

## Quick recap

The profile is the whole picture of one person. Editable properties and consents, a full activity timeline, live labels, connected records, team notes, and quick actions to message, enrol and label. Everything on it is the person's current stored state and logged history, kept up to date as your data changes.