Teams & Due Diligence

Two data-room companions: Teams restrict a link (or future surface) to a named cohort of emails, and Due Diligence turns a space into a tracked checklist of requests.

Teams#

A team is a named list of member emails owned by a user. Its only job today is to back the team link visibility gate.

Data model — teams#

Indexed on owner_id.

The team gate#

links gained two columns in Phase 1:

• visibility text default "public" — "public" or "team".
• team_id uuid? → teams.id ON DELETE SET NULL.

checkTeamAccess(link, email) in lib/visitor/gate.ts runs inside the email gate step (createEmailHandler's checkTeamAccess hook):

if (link.visibility !== "team" || !link.teamId) return true;   // not gated by team
const team = await db().select({ memberEmails }).from(teams).where(eq(teams.id, link.teamId));
if (!team) return false;                                        // fail closed
return team.memberEmails?.includes(email.toLowerCase()) ?? false;

It fails closed: a team-visibility link whose team row is missing denies everyone. A visitor whose email isn't in the team gets email_not_in_team. Because it's enforced at the email step (the first gate), an unlisted email never advances.

API#

Behind withOwner, validated by teamCreateSchema / teamUpdateSchema (lib/validation/team.ts):

emailLower (z.string().trim().toLowerCase().email()) normalizes every member email so the includes(email.toLowerCase()) check in the gate is exact.

Due Diligence#

A per-space checklist — the requests an investor/acquirer wants satisfied before they're done. Each item lives under a space and carries a status, optional assignee, due date, priority, and a comment thread.

Data model#

diligence_items

Indexed on space_id and status.

diligence_comments — id, item_id → diligence_items.id CASCADE, author_email, body, created_at. Indexed on item_id.

Status workflow#

open → in_review → satisfied
                 → waived
                 → blocked

status is a free-text column defaulting to open; the API/UI drive it through the workflow above. New statuses are additive (readers default to a neutral state).

API#

Behind withOwner; every item/comment is reached through its space → space.owner_id = caller so cross-tenant access is impossible:

Diligence items are surfaced inside the Spaces owner area. NDA/agreement gating for the room itself is configured on the space, not per diligence item.