Separately, I've also noticed that I have the same custom schema listed multiple times (Project ID 2a8944ff-4286-4120-8325-218fefc81a52 for reference)
Any idea why this would be?
I'm managing the Ory Network config in git and applying the config via the API on merge - a simple infrastructure as code implementation in the absence of an offical provider.
c
creamy-art-71586
11/19/2025, 8:49 PM
For historical reasons the identity schema belongs to a workspace and hence why you see it repeated in every project in your workspace
b
bulky-keyboard-95137
11/20/2025, 1:39 AM
Ah right, but it's configured at a project level? Is the default identity schema also applied at a workspace level?
I have created multiple projects to represent our different environments. Should I instead be creating multiple workspaces?
I suppose we can make do if there is some confusing duplicated config but we need the default identity schema to be stable and deterministic as we update the different environments.
c
creamy-art-71586
11/20/2025, 7:13 AM
The id is a hash of the schema definition content so it is stable and deterministic. Please do not use separate workspaces for this
👍 1
b
bulky-keyboard-95137
11/20/2025, 7:15 AM
Okay thanks for clarifying.
bulky-keyboard-95137
11/20/2025, 7:17 AM
It seems like the API keys needed to apply config changes to projects are also at a workspace level.
Because of that, I decided to put our dev project in a different workspace - since engineers will have access to the dev API key.
Any concerns with that approach?