---
title: "Teams > Membership > Creates"
method: POST
path: "Webhooks > Teams > Membership > Creates"
tags: ["Webhooks"]
---

# Teams > Membership > Creates

`POST Webhooks > Teams > Membership > Creates` (webhook)

Subscription_type: `teams/membership/create`. Triggered when a direct membership is created — one placing the employee on that team itself, as opposed to a row they get through a sub-team. Fires whether the membership is created through the API or from Factorial. Inherited rows created afterwards in ancestor teams (nested teams) do not trigger this event; read the memberships endpoint if you need to track them. Nor is this a complete feed of additions, and which event an addition produces depends on the side it is made from. Adding people to a team emits `teams/membership/bulk_upsert` and not this event; adding a team to a person emits both, so `bulk_upsert` is the wider of the two feeds. For companies with nested teams there is a third shape: the employee profile and imports set the complete set of teams the employee belongs to, which emits nothing at all, so those rows are only observable by reading the memberships endpoint.

## Payload

- TeamsMembership
  - `id` string, required: Membership ID
  - `company_id` string: Company ID of the membership
  - `employee_id` string, required: Employee ID of the membership
  - `team_id` string, required: Team ID of the membership
  - `lead` boolean, required: Whether the employee is a lead of the team or not
  - `source_team_ids` string[], required: IDs of the teams this membership originates from (nested teams). In a company with nested teams, a direct membership includes the team itself; an inherited one, the sub-team(s) where the employee is a direct member. Only populated on reads that compute source attribution — reads filtered by a single team, or by a single employee with `with_source_attribution` enabled. Empty otherwise, including create, update and delete responses, and always empty for companies without nested teams. An empty array does not distinguish "computed and genuinely empty" from "not computed for this read" or "could not be computed", so only apply attribution-dependent logic to a read you explicitly shaped for it. A team-anchored read stops attributing above roughly a thousand members of the filtered team: past that the attribution is not computed at all and every row comes back empty, behind a normal `200`.
  - `parent_team_ids` string[], required: IDs of the ancestor teams that receive an inherited membership through this row (nested teams) — the teams this membership rolls up into. Populated under the same conditions as `source_team_ids`; empty otherwise.
  - `direct` boolean: Whether the employee is a direct member of the team (nested teams). Always present. `true` means direct member; `false` means the row exists only through inheritance from a sub-team; `null` means not computed for this read. Only computed on reads filtered by a single employee with `with_source_attribution` enabled — always `null` otherwise, including create, update and delete responses and companies without nested teams. `null` is also returned when directness could not be resolved for a transient reason, even with `with_source_attribution` enabled, so never treat `null` as `false` — retry the read instead.

## Acknowledgement `200`

Return a 200 status to indicate that the data was received successfully

---

[API](https://skmtc.dev/factorialhr/apis/factorial-api.md) - [All operations](https://skmtc.dev/factorialhr/apis/factorial-api/llms.txt) - [OpenAPI document](https://skmtc.dev/factorialhr/apis/factorial-api/revisions/83ac9aa1de50?raw)