Email - Well Starter Kit

The Email entity represents email addresses in the Well system. It can be associated with people or companies and includes verification status, primary designation, and contextual labels.

Table structure

Table name: emails

Main fields

Name	Type	Required	Constraints	Allowed Values	Description	Example
`id`	string, UUID, 🔒 system	—	Unique identifier (read-only)	—	Unique ID	`”email-uuid-123”`
`email`	string	✅ Yes	Valid email format	Valid email format = local part + ”@” + domain + ”.” + TLD	Email address	`”john.doe@company.com”`
`is_primary`	boolean	⚪ No	default: true, only valid when in relationship with a Person or Company	`true`, `false`	Marks preferred address	`true`
`is_verified`	boolean, 🔒 system	—	Verification flag. Only systems or whitelisted workspaces can modify	`true`, `false`	Verification flag	`true`
`label`	string (50 char)	⚪ No	max 50 chars, only valid when in relationship with a Person or Company	`work`, `perso`, `other`	Tag for extra context when having multiple emails	`”work”`
`created_at`	string (ISO 8601) 🔒 system	—	auto timestamp	—	Creation timestamp	`”2023-01-01T12:00:00Z”`
`updated_at`	string (ISO 8601) 🔒 system	—	auto timestamp	—	Last update timestamp	`”2023-01-01T12:00:00Z”`
`deleted_at`	string \| null 🔒 system	—	nullable ISO 8601	—	Deletion timestamp (soft delete)	`“2024-01-01T12:00:00Z”`

Relations

Many-to-Many relations

People: Can be associated with multiple people
Companies: Can be associated with multiple companies

Relationship schema

Email (N) ←→ (N) People
Email (N) ←→ (N) Companies

# Direct relationship without intermediate tables
# Each email can belong to multiple people/companies
# Each person/company can have multiple emails

Data Model

​Table structure

​Main fields

​Relations

​Many-to-Many relations

​Relationship schema

Table structure

Main fields

Relations

Many-to-Many relations

Relationship schema