The error message "Requested identity schema 'preset://email' is not enabled for self-service flows" means that the identity schema you are trying to use (in this case, the email preset schema) is not currently active or available for self-service operations like registration or social sign-in in your Ory project. What does this mean? - Ory requires that an identity schema be enabled and set as the default (or at least available) for self-service flows such as registration and login, including social sign-in. - If you try to register or sign in with a schema that is not enabled, you will get this error. What should you do? 1. Check your active identity schema: Go to the Ory Console under User management → Identity schema and verify which schema is set as the active schema. If

<preset://email>

is not listed or not active, you need to enable it. 2. Enable or switch to the correct schema: - If you want to use the email preset, select it from the Active schema dropdown and click Change active schema. - If you need a custom schema, ensure it is created and set as active. You can create a custom schema by duplicating an existing one, making your changes, and then activating it. [Manage identity schemas](https://www.ory.sh/docs/identities/model/manage-identity-schema) 3. Update your configuration if using CLI or GitOps: If you manage your configuration via CLI or GitOps, make sure your

identity-config

sets the correct

default_schema_id

and includes the schema in the

schemas

array. For example:

json    {      "default_schema_id": "<preset://email>",      "schemas": [        {          "id": "<preset://email>",          "url": "<https://schemas.ory.sh/presets/kratos/quickstart/email-password/identity.schema.json>"        }      ]    }

[GitOps: Identity Schema](https://www.ory.sh/docs/guides/gitops#identity-schema) Do you need a different schema? - Not necessarily. You just need to ensure that the schema you want to use (e.g.,

<preset://email>

) is enabled and set as the default or is available for self-service flows. - If your use case requires a different schema (e.g., username-based or a custom schema), create and activate that schema instead. Summary: You do not need to use a different schema unless your requirements have changed. You just need to make sure the schema you want to use is enabled and set as the active schema for self-service flows in your Ory project. Once this is done, social sign-in and other self-service operations should work as expected. If you continue to see issues after enabling the schema, double-check that your configuration changes have been applied and that your project is using the correct schema for new identities and self-service flows. [Manage identity schemas](https://www.ory.sh/docs/identities/model/manage-identity-schema) [GitOps: Identity Schema](https://www.ory.sh/docs/guides/gitops#identity-schema)