Hey guys, thank you for SuperTokens! I'm trying to evaluate if SuperTokens could be a good fit to migrate from Auth0. We want to migrate mainly because the local development experience of Auth0 is awful, you just can't run it locally. (+ their lack of discord or slack community is very frustrating) So my main requirements are to be able to : - 1 / run the authentication service locally for dev and self-hosted for staging - 2 / update the JWT with the user's roles, both at the token creation time and later (eg. when we let the user chose the identity he wants for its current session, when a user has many identities linked to its account (eg. 1 user account -> 3 identities in 3 companies as employee, and 1 identity as manager)) - 3 / synchronize users that have been created upfront by the backend (eg. when inviting a team member, or user) with the user created when he signs up 1 / this seems OK 2 / I read the doc and found a way to do both 3 / It's not clear if the SuperTokens (when self-hosted) DB/schema is separate from my main DB where I store my users and main data model? Can they be the same DB? Or do SuperTokens needs an isolated DB/schema? If this is the case how can I synchronize new supertokens users (signup) with the users I provisioned upfront in my own main DB? If SuperTokens can run on my own main DB/schema (ie. I only have one user table then) how can it work when I use the hosted version of SuperTokens? Thank you so much!