Note: This is mock/placeholder content for demonstration purposes.
The database schema is designed with a multi-tenant architecture that supports both personal and team accounts.
The users table stores user authentication data and is managed by Supabase Auth:
id - Unique user identifieremail - User's email addresscreated_at - Account creation timestampThe accounts table represents both personal and team accounts:
id - Unique account identifiername - Account display nameslug - URL-friendly identifieris_personal_account - Boolean flag for personal vs team accountsStore your application's project data:
id - Unique project identifieraccount_id - Foreign key to accounts tablename - Project namedescription - Project descriptioncreated_at - Creation timestampAll data in the application is tied to accounts through foreign key relationships. This ensures proper data isolation and access control through Row Level Security (RLS).