@User that's not possible at the moment. We are working on that though. For now, you have the following options: - Save that field in your own db against the userId returned by supertokens; and / or - Save that info in the session for the user