diff --git a/docs/identities/configuration/index.md b/docs/identities/configuration/index.md
new file mode 100644
index 000000000..b5b3a0803
--- /dev/null
+++ b/docs/identities/configuration/index.md
@@ -0,0 +1,22 @@
+---
+title: "Configure Identities"
+date: "2025-02-25"
+sidebar_position: 2
+---
+
+You can configure which identifiers to use. They can be in any part of the event payload, whether the atomic event properties or in entities.
+
+You can also choose to process identities for all events, or a subset of events.
+
+## Default settings
+
+Defaults: user_id, domain_userid, network_userid, client_session.userId
+All events.
+
+## Custom identifiers
+
+## Event filtering
+
+## Testing
+
+Testing, QA, troubleshooting.
diff --git a/docs/identities/data-models/index.md b/docs/identities/data-models/index.md
new file mode 100644
index 000000000..8d26dd9a3
--- /dev/null
+++ b/docs/identities/data-models/index.md
@@ -0,0 +1,11 @@
+---
+title: "In the warehouse"
+date: "2025-02-25"
+sidebar_position: 3
+---
+
+These dbt packages support Identities.
+
+They make tables.
+
+Links to config pages of existing models?
diff --git a/docs/identities/index.md b/docs/identities/index.md
new file mode 100644
index 000000000..00b645477
--- /dev/null
+++ b/docs/identities/index.md
@@ -0,0 +1,42 @@
+---
+title: "Identities"
+date: "2025-02-25"
+sidebar_position: 6
+---
+
+Snowplow Identities provides real-time identity resolution.
+
+As events flow through your pipeline, the Identities graph database checks the identifiers. It uses deterministic profile stitching to link identifiers into a single profile, and adds the persistent `snowplow_id` as an entity to each event. This `snowplow_id` allows you to create one-row-per-user and identifier mapping tables in your warehouse.
+
+Use cases for Identities include:
+* Attribution and analytics: tie together user behavior across sessions, devices, and domains to form a complete picture of the user journey. This improves accuracy in marketing attribution, conversion funnel analysis, and multi-touchpoint reporting.
+* Feature engineering and personalization: aggregate behavior across platforms, enabling feature extraction and personalization in both real-time and batch contexts.
+* Audience targeting and activation: create deduplicated user audiences for targeting in marketing tools, CRMs, adtech channels, or other engagement platforms.
+
+## Using Identities
+
+Contact Support to get started with Snowplow Identities. Check out the Configuration ADD LINK page for more details.
+
+## Architecture
+
+## Identities entity
+
+The added entity uses schema X. The `snowplow_id` has format Y.
+
+Here's an example:
+
+```json
+{ "probably":"json"}
+```
+
+## Merge event
+
+When Identities merges two profiles, it generates a merge event and adds it directly to your enriched event stream.
+
+This event is useful for ??? in modeling.
+
+The merge event uses schema Z.
+
+```json
+{ "probably":"json"}
+```
diff --git a/docs/identities/logic/index.md b/docs/identities/logic/index.md
new file mode 100644
index 000000000..4a0a87cfc
--- /dev/null
+++ b/docs/identities/logic/index.md
@@ -0,0 +1,13 @@
+---
+title: "Stitching logic"
+date: "2025-02-25"
+sidebar_position: 1
+---
+
+The Identities user stitching logic is very clever.
+
+Flow chart etc
+
+### Examples
+
+Here are some examples of how the stitching logic works in practice.