EmirBase LogoEmirBase Logo
  • Home
  • Blog
  • Services
  • Pricing
  • FAQ
  • Contact
Sign InSign Up
EmirBase LogoEmirBase Logo

footerDescription

copyright

about
  • Blog
  • contact
product
  • Documentation
legal
  • Terms of Service
  • Privacy Policy
  • cookiePolicy
  • Introduction
    • Installing Dependencies
    • Quick Start
    • Project Structure
    • Configuration
  • Authentication Overview
    • Configuration
    • Email & Password
    • OAuth
    • Magic Links
  • Database
    • Database Overview
    • Migrations
    • Row Level Security
    • Querying Data
    • Functions & Triggers
  • Features
    • Features Overview
    • Team Collaboration
    • File Uploads
  • Billing & Payments
    • Billing Overview
    • Pricing Plans
    • Webhook Integration

Database Overview

Understanding the database schema and table structure in your application.

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.

Core Tables

Users Table

The users table stores user authentication data and is managed by Supabase Auth:

  • id - Unique user identifier
  • email - User's email address
  • created_at - Account creation timestamp

Accounts Table

The accounts table represents both personal and team accounts:

  • id - Unique account identifier
  • name - Account display name
  • slug - URL-friendly identifier
  • is_personal_account - Boolean flag for personal vs team accounts

Projects Table

Store your application's project data:

  • id - Unique project identifier
  • account_id - Foreign key to accounts table
  • name - Project name
  • description - Project description
  • created_at - Creation timestamp

Relationships

All 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).

Next Steps

  • Learn about migrations
  • Understand RLS policies