DOCS UPDATE:Supabase Database Schema Documentation

[Peehu1308]

Is this related to an existing part of the documentation?

• Yes, it is related to an existing section

What needs to be updated?

Current Documentation Issue
The current backend documentation does not clearly define the Supabase database schema used by the application. While SQL migration files exist in the repository, there is no centralized or human-readable documentation describing:
Which tables are used by the app
The purpose of each table
The fields/columns within those tables
Relationships between tables

As a result, contributors attempting to work on features such as profile editing, user preferences, or settings face difficulty understanding which tables to query or update, slowing down development and increasing onboarding time.

Proposed Changes
Add a dedicated Database Schema Documentation section that clearly explains the Supabase tables used in the project.

Suggested additions include:

A table-by-table breakdown listing:
Table name
Column names
Data types
Purpose of each field
High-level explanation of relationships between tables (e.g. users → teams → tasks)
Optional ER diagram or schema overview generated from Supabase
Clear indication of which tables are:
Read-only (e.g. auth.users)
Meant to be accessed/updated by the frontend (e.g. public.users, preferences tables)
This documentation can live in:
The backend setup guide, or
A separate DATABASE_SCHEMA.md file in the repository

Additional Context
Contributors currently need to manually inspect SQL migration files or the Supabase dashboard to understand the schema
This creates friction when implementing common features such as:
Editing user profiles
Managing preferences (e.g. language selection)
Extending existing backend functionality
Clear schema documentation would significantly improve contributor experience and reduce duplicated effort

Impact
Faster onboarding for new contributors
Fewer backend-related blockers
Clearer separation of responsibilities between frontend and backend
Improved maintainability of the project

Relevant Documentation Link (if any)

No response

Record

• I agree to follow this project's Code of Conduct
• I want to work on this update

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Related PRs

#88 - Feat: Add Google OAuth 2.0 Authentication Support [merged]

👤 Suggested Assignees

• may-tas

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[ayush-gupta18-hub]

Hi @Peehu1308 , I’d like to work on this issue.
I will document the Supabase database schema (tables, columns, and relationships) and add it as a new DATABASE_SCHEMA.md / docs section.

Could you please assign this issue to me? Also, please let me know if you have any preferred format or location for the documentation. Thanks!

[ayush-gupta18-hub]

Hi @Peehu1308 ,
PR ready for review — happy to make any revisions based on feedback.

[Peehu1308]

@ayush-gupta18-hub I raised this issue with the intention of working on it. I am currently awaiting approval from the maintainers before proceeding

[SharkyBytes]

As a result, contributors attempting to work on features such as profile editing, user preferences, or settings face difficulty understanding which tables to query or update, slowing down development and increasing onboarding time.

Proposed Changes Add a dedicated Database Schema Documentation section that clearly explains the Supabase tables used in the project.

Please make sure to stick to the issue template while creating issues, and the same applies to PRs as well (it makes reviews much easier for us)

Good Suggestion @Peehu1308 ! since we are actively updating and iterating on Ell-ena’s schema to make it more functional and useful, the schema is still evolving..because of this, I m marking this issue as on hold for now, and we can revisit it once things stabilize.

[SharkyBytes]

i can see 2 PRs open for this now... really appreciate the effort you guys put in!

instead of documenting the schema like a README, it’d be great if we could represent it in some visual format...easier to look up and more contributor-friendly I guess..

i’d suggest collaborating on this together and lhopping over to the discord channel. tag me there once you have the current schema visual ready (feel free to use any platform/tool for the visuals).