> ## 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.

# People & Organization

> The workforce records every other resource points at — people, the attributes that describe them, and the org dimensions they sit in

<Info>
  **Quick Summary:** People are the anchor of the whole API — every record in [Team Data](/api-docs/concepts/team-data) names a person. This group covers the person record itself, the company-defined attributes a person references (job titles, people types, access levels, countries), and the eleven org dimensions plus the manager hierarchy.
</Info>

## The resources

| Resource                                           | What it is                                                                                                |
| -------------------------------------------------- | --------------------------------------------------------------------------------------------------------- |
| [Person](/api-docs/resources/person)               | The workforce record: identity, contact details, access level, manager, org placement and lifecycle       |
| [Org structure](/api-docs/resources/org-structure) | Eleven flat dimensions saying *where someone sits*, and the manager hierarchy saying *who they report to* |

## Addressing a person

Every person-shaped path slot on this API takes the person's **email address** — the primary, documented form — or the opaque `id` from any response. Request fields that reference a person are email fields (`managerEmail`, `delegatedApproverEmail`, `{ "email": ... }`). Email is unique across all of SkillsDB, not just your company.

The field an integration should key on is `externalId` — your own identifier, carried on the person record for exactly this purpose.

## Attributes are their own library

Job titles, people types, access levels and countries are company-configured lists, not free text on the person. A person references them; you manage the lists themselves through their own endpoints. Access levels are the one list you cannot extend — four are assignable (`basic`, `manager`, `admin`, `fullaccess`) and three are legacy and read-only.

## Syncing a workforce

`POST /api/v1/bulk/people` takes a batch of people in one call — the shape an HRIS sync needs. For a single dimension, `PUT /people/{id}/org-schema/{dimension}` replaces that dimension with exactly the supplied list, which is what makes a repeatable sync idempotent.

<Note>
  **SCIM and this API are alternatives, not layers.** If your identity provider provisions people through SkillsDB's SCIM integration, do not also sync people through this API against the same tenant.
</Note>

## What is not here

What a person *knows, holds or has done* is [Team Data](/api-docs/concepts/team-data) — person skills, assessments, certifications, training and career assignments all live there. This group is only the person and where they sit.