Loading Depth Study
Preparing your workspace
Supabase Auth stores authentication identity while application tables can store additional profile and business information.
A common application pattern is to keep authentication information in Supabase Auth and create a public profiles table for application-specific data such as name, role, status, avatar, department, or preferences. The profile ID can match the authenticated user's ID. This separation keeps authentication concerns distinct from application data. Server-side or database-level logic can create or maintain profile records after account creation.
A learning platform can keep the user's authentication identity in Auth and store name, platform role, organization status, and preferences in profiles.
create table profiles ( id uuid primary key references auth.users(id) on delete cascade, name text, role text not null default 'user', status text not null default 'active', created_at timestamptz not null default now() );
The profiles table uses the authenticated user's ID as its primary key and links it to auth.users.