Self-Hosted: User Authentication Context and Auditability in Supabase Studio

Hi Supabase team, We are using a self-hosted installation of Supabase and have noticed that while we can enforce authentication (e.g., via SSO or MFA) to access Supabase Studio, the Studio interface itself does not appear to maintain or apply the authenticated user’s identity within the UI. For example, even after logging in, Studio seems to operate as if the user is unauthenticated For compliance and security purposes, we also need to audit actions performed via Studio (e.g., who executed a query, modified a table, or changed a policy). Without the user’s identity being tied to their actions in Studio, it’s challenging to maintain a clear audit trail. Is there a way to configure Studio to fully respect the authenticated user’s context ? Are there existing features, extensions, or configurations for self-hosted Supabase that improve auditability for actions performed in Studio, such as logging which user performed specific operations? Supabase is a powerful tool ! Tha…