Hi! I use Kratos for my Identity management and I would like to have additional fields for my users. I would also like my users to be part of Organisations or UserLists which are other tables. I am wondering if it’s best to: 1) Use the Kratos Identities table and add new custom columns to it 2) Have a new table for users that duplicates the Identities one from Kratos and Use Ory Actions to synchronise the tables on user creation / deletion The solution 2) seems more robust to me but also more issue prone in case of un sync. I wonder what’s the typical way of doing this as it seems like a common use case. What do you think ?

We are doing 2 with webhooks. Best to separate concerns and not access the Kratos database from your application.

Thanks for the feedback!

Does this help with #1? https://www.ory.sh/docs/kratos/manage-identities/identity-schema

Well I thought about addind the values at traits but it seems like it is a very bad practice as stated in their documentation: https://www.ory.sh/docs/kratos/manage-identities/best-practices I think solution 2 might be the most reliable one even though it adds a bit of overhead

@victorious-eye-56567 Kratos also has the limitation that you cannot easily add or pull properties from the traits / metadata objects, typically these objects are being replaced fully. The patch identity admin endpoint does have the ability to mutate accurately based on json paths though.