> For the complete documentation index, see [llms.txt](https://docs.sumble.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sumble.com/our-data/people.md).

# People

What Sumble knows about people: profiles, job functions and levels, where they work, and the scores that rank them.

Sumble keeps professional profiles for people at the organizations it tracks. Profiles are one of Sumble's two primary sources, with job posts. See [Our data](https://docs.sumble.com/our-data/our-data.md#primary-sources).

To find people in the web app, see [People search](https://docs.sumble.com/web-app/people-contacts/people-search.md). To get them through the API, see [People API](https://docs.sumble.com/api/core-data/people.md).

## Profiles

A profile holds a person's name, current title and employer, location, LinkedIn URL, past roles with dates, the "About" summary they wrote, and the skills and technologies they list. Sumble refreshes profiles daily and links each person to the organization they work for.

The number of people linked to an organization is its **People** count. It differs from the **Employees** count the organization reports. See [Employees and people](https://docs.sumble.com/our-data/organizations.md#employees-and-people).

## Job function and level

Sumble classifies each person's role into a job function, such as Data Engineer or Account Executive, and a job level, such as Manager or VP. The full lists are in the [filter reference](https://docs.sumble.com/our-data/filter-reference.md#job-functions).

Job functions form a tree. When a title is too general to place in a specific function, Sumble assigns the broader parent instead. So the people counts of a function's children don't add up to the count for the function itself.

## Technologies

A person's technologies are the skills and tools on their profile. An organization can match a technology filter through its job posts or through its people's profiles. See [Technologies & projects](https://docs.sumble.com/our-data/technologies-and-projects.md#where-technology-evidence-comes-from).

## Managers and direct reports

Sumble infers each person's likely managers and direct reports. The [People API](https://docs.sumble.com/api/core-data/people.md#composable-response) returns these as `related_people`.

## Contact details

Email addresses and phone numbers aren't part of a profile. Sumble looks them up when you reveal them, which costs credits. See [Credits](https://docs.sumble.com/get-started/credits.md).

## Scores

Sumble ranks people and teams against your ICP, the profile of the buyers you sell to. Your company sets it up under [ICP & sales context](https://docs.sumble.com/system-setup-and-configuration/admin-portal/icp-and-sales-context.md). Four scores use it:

* **Person score** (0 to 100) measures how well a person at an organization matches your ICP, with a breakdown of what contributed. The API returns it as `person_score`.
* **Contact score** (beta) ranks people on the People tab, the People page and in exports. Admins tune it under [Contact scoring](https://docs.sumble.com/system-setup-and-configuration/admin-portal/contact-scoring.md). Where it's turned on, it can differ from the API's `person_score`.
* **Team score** (0 to 100) measures the same for a team, with a Great, Good or Possible label. See [Teams](https://docs.sumble.com/our-data/teams.md).
* **Suggested contact relevance** (1 to 10) ranks the people Sumble suggests contacting for a single signal. It scores fit for that signal, not for your ICP overall, so it's on a different scale. See [Signals API](https://docs.sumble.com/api/intelligence/signals.md).

Person and team scores need one organization in scope at a time, because they compare people within that organization.

For ranking whole accounts, see [Sumble score](https://docs.sumble.com/our-data/sumble-score.md).
