Membership - Well Starter Kit

The Membership entity represents a person’s membership in a workspace within the Well system. It serves as the central linking table for the multi-tenancy system, allowing a user to belong to multiple workspaces with different roles.

Table structure

Table name: memberships

Main fields

Name	Type	Required	Constraints	Allowed Values	Description	Example
`id`	string, UUID, 🔒 system	✅ Yes	Unique identifier (read-only)	–	Unique identifier of the membership previously created	`”membership-uuid-123”`
`person`	People (UUID)	✅ Yes	Foreign key reference	–	Reference to the person	`”person-uuid-456”`
`workspace`	Workspace (UUID)	✅ Yes	Foreign key reference	–	Reference to the workspace	`”workspace-uuid-789”`
`firebase_id`	string	⚪ No	nullable	–	Firebase user ID for authentication	`”firebase-user-id-123”`
`membership_role`	string	⚪ No	nullable	`admin`, `member`, `viewer`, `owner`	User role in the workspace	`”admin”`
`created_at`	string (ISO 8601) 🔒 system	–	auto timestamp	–	Creation timestamp	`”2023-01-01T12:00:00Z”`
`updated_at`	string (ISO 8601) 🔒 system	–	auto timestamp	–	Last updated timestamp	`”2024-01-01T12:00:00Z”`
`deleted_at`	string \| null 🔒 system	⚪ No	nullable ISO 8601	–	Deletion timestamp (soft delete)	`“2024-01-01T12:00:00Z”`

Relations

The Membership entity is a Many-to-Many linking table between People and Workspace:

Many-to-One relations

People: The member person (one membership → one person)
Workspace: The workspace (one membership → one workspace)

Relationship schema

People (1) ←→ (N) Membership (N) ←→ (1) Workspace

# Enables Many-to-Many relationship:
People (N) ←→ (N) Workspace via Membership

Data Model

​Table structure

​Main fields

​Relations

​Many-to-One relations

​Relationship schema

Table structure

Main fields

Relations

Many-to-One relations

Relationship schema