From 778f032e8519b38e773783f4b8aaba4c6ac5025d Mon Sep 17 00:00:00 2001 From: KT-Doan Date: Mon, 4 May 2026 14:39:49 +0900 Subject: [PATCH 1/3] docs: document deleting custom identity schemas --- .../model/manage-identity-schema.mdx | 34 +++++++++++++++++++ 1 file changed, 34 insertions(+) diff --git a/docs/identities/model/manage-identity-schema.mdx b/docs/identities/model/manage-identity-schema.mdx index 2034b782a..7202faea6 100644 --- a/docs/identities/model/manage-identity-schema.mdx +++ b/docs/identities/model/manage-identity-schema.mdx @@ -98,6 +98,40 @@ However, you can use the existing schema as a template to create a new schema. S It's recommended to manage identity schemas in version control. Learn more about [managing Ory Network configuration in git](../../guides/gitops). +## Delete a custom schema + +Custom schemas you no longer need can be deleted. The deletion is rejected if the schema is still attached to a project or is +referenced by an identity. Once a schema is attached to a project, that attachment cannot be removed, so the schema cannot be +deleted as long as it remains in use. + +Presets cannot be deleted. + + + + +1. Go to . +2. Find the schema you want to delete in the **Custom schemas** section. +3. Open the row menu (three dots) and select **Delete schema**. +4. Confirm the deletion in the dialog. + +If **Delete schema** is disabled, the schema is currently attached to a project and cannot be deleted. + + + + +Delete a schema through the Ory Network Console API using a +[workspace API key](../../concepts/personal-access-token.mdx#authorizing-ory-network-workspace-admin-apis): + +```shell +curl -X DELETE "https://api.console.ory.sh/identity-schemas/$SCHEMA_ID" \ + -H "Authorization: Bearer $ORY_WORKSPACE_API_KEY" +``` + +If the schema is still in use, the API returns `409 Conflict` with the number of projects that reference it. + + + + ## Update identities to use a new schema Updating the identity schema of a project can result in inconsistencies between the new schema and the identities created with the From d0a2f64146a4537665ddadaa87bd283af6cc6e30 Mon Sep 17 00:00:00 2001 From: unatasha8 Date: Wed, 6 May 2026 01:27:16 -0700 Subject: [PATCH 2/3] Apply suggestions from code review Co-authored-by: unatasha8 --- docs/identities/model/manage-identity-schema.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/identities/model/manage-identity-schema.mdx b/docs/identities/model/manage-identity-schema.mdx index 7202faea6..d0929380c 100644 --- a/docs/identities/model/manage-identity-schema.mdx +++ b/docs/identities/model/manage-identity-schema.mdx @@ -100,7 +100,7 @@ It's recommended to manage identity schemas in version control. Learn more about ## Delete a custom schema -Custom schemas you no longer need can be deleted. The deletion is rejected if the schema is still attached to a project or is +You can delete a custom schema that you no longer need if the schema is not being used by a project or referenced by an identity. referenced by an identity. Once a schema is attached to a project, that attachment cannot be removed, so the schema cannot be deleted as long as it remains in use. From 2c2adc114d3811ce3ee143c3fdf01deb40afe141 Mon Sep 17 00:00:00 2001 From: KT-Doan Date: Wed, 6 May 2026 17:41:33 +0900 Subject: [PATCH 3/3] docs: clarify project-attachment constraint --- docs/identities/model/manage-identity-schema.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/identities/model/manage-identity-schema.mdx b/docs/identities/model/manage-identity-schema.mdx index d0929380c..5a4b1db58 100644 --- a/docs/identities/model/manage-identity-schema.mdx +++ b/docs/identities/model/manage-identity-schema.mdx @@ -101,8 +101,8 @@ It's recommended to manage identity schemas in version control. Learn more about ## Delete a custom schema You can delete a custom schema that you no longer need if the schema is not being used by a project or referenced by an identity. -referenced by an identity. Once a schema is attached to a project, that attachment cannot be removed, so the schema cannot be -deleted as long as it remains in use. +You can switch which schema your project uses, but a schema that has already been added to a project remains referenced by it. +That reference is what blocks deletion. Presets cannot be deleted.