Supabase Auth in immutable auth object in JWT

At the moment if I use Supabase Auth and connect it to Discord, the only way I can access the Discord user information in my application is via user_metadata, which is able to be changed via a Supabase API call.

Could you please put auth-related information in a separate immutable object as part of the JWT object (I can't see why we would want it mutable) so that it's easy to access as part of an RLS policy? The idea of using webhooks to populate your own auth table seems excessive and tricky.

I have discussed this topic at length in this thread: