> ## Documentation Index
> Fetch the complete documentation index at: https://help.skillsdb.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Team Data

> The records about people — one shared shape: a person, a definition they point at, and the evidence attached

<Info>
  **Quick Summary:** Team Data is everything the API records *about a person*, as opposed to what the company configures. Every resource here has the same three-part shape — **person + definition + evidence** — and these are the records an integration syncs daily.
</Info>

## The shared shape

Every Team Data record joins a person to a [System Object](/api-docs/concepts/people-and-organization) and attaches what was observed:

| Part           | What it is                                                                                    |
| -------------- | --------------------------------------------------------------------------------------------- |
| **Person**     | Who the record is about — addressed by email address, or the opaque id                        |
| **Definition** | The system object it points at: a skill, a certification, a career, a learning item, a survey |
| **Evidence**   | What was observed: grades, dates, status, files, notes, approval decisions and history        |

Once you know a resource's definition side, you already know most of its read shape. The differences are in the evidence.

## The resources

| Group              | Resource                                                                                     | The definition it points at                        |
| ------------------ | -------------------------------------------------------------------------------------------- | -------------------------------------------------- |
| Proficiency Data   | [Person skill](/api-docs/resources/person-skill)                                             | [Skill](/api-docs/resources/skill)                 |
| Assessment Results | [Assessment](/api-docs/resources/assessment)                                                 | Skills, within a cycle                             |
| Certification Data | [Person certification](/api-docs/resources/person-certification)                             | [Certification](/api-docs/resources/certification) |
| Training Data      | [Learning plan](/api-docs/resources/learning-plan)                                           | [Learning item](/api-docs/resources/learning-item) |
| Training Data      | [Training record](/api-docs/resources/training)                                              | A [person skill](/api-docs/resources/person-skill) |
| Survey Results     | [Survey](/api-docs/resources/survey), [Survey response](/api-docs/resources/survey-response) | A survey template version                          |
| Career Assignments | [Career assignment](/api-docs/resources/career-assignment)                                   | [Career](/api-docs/resources/career)               |

## Three rules that hold across the group

**Grades are resolved rungs, never integers.** Every grade and benchmark is returned as `{ id, grade, label }` against the company [grading scale](/api-docs/resources/grading-scale). A bare integer does not rank.

**Expiry is derived from a date, never from a status.** An approved certification or training stays `approved` in storage after its date passes. Reads carry a separate expiry signal — use it, rather than inferring currency from the status.

**History is written, not overwritten.** Unassigning a career records career history first. Renewing a training supersedes the old record rather than deleting it. Removing a person skill writes history before it goes. Past state stays readable.

## The definition must exist first

Team Data records cannot invent their definition side. A training record requires the skill to already be on the person's profile. A learning plan requires the catalogue item. A person certification requires the library certification. Sync the [System Objects](/api-docs/concepts/skills) first, then the records about people.

## Detecting change

There are no webhooks. Poll the activity feeds — see [Polling for Changes](/api-docs/rest/polling) for the pattern, and the [activity event](/api-docs/resources/activity-event) envelope for the shape.