The catalog

Every module a platform can be granted, in one table.

Updated July 26, 2026

The modules

Key	What it does
`records`	The custom-data engine — declare record types, get a generic filtered/sorted/paginated surface. Most other modules ride it.
`customers`	The people the platform serves, and portal auth: customer CRUD, JWT portal login scoped to one platform, session revocation.
`projects`	The unit of work, per customer — the spine the rest hangs off: a customer has projects; a project has a website, a board, to-dos, tickets, expenses and files.
`websites`	The sites the platform builds and keeps alive: domain, environment, stack, status, uptime, last deploy — and per-site API keys (`dfd-site-*`) for the site surface.
`forms`	Dashboard-built forms — intake, signatures, file uploads, payment details — with a public submit path (honeypot + rate limiting) and submissions that can materialize into records.
`contacts`	Public-form leads worked as an inbox (`new → contacted → closed`), stored as `contact` records, with owner/admin email alerts.
`media`	The files library: uploads with WebP variants + LQIP placeholders, CDN delivery, folders/tags/labels, taggable to a customer or site.
`inventory`	A display-only product catalog (`product` records, draft/active, variations, gallery) served read-only to client sites. Deliberately not commerce: no cart, checkout or stock.
`pages`	CMS content for public surfaces — content types and items, SEO metadata, legal documents. Blog posts on client sites are content rows in a `blog` section.
`insights`	First-party analytics: pageviews, visitors, sessions, attribution — collected into the platform's own tables rather than GA4.
`invoices`	The platform invoicing its own customers — one-off invoices and retainers, pay links, status.
`expenses`	Costs incurred on a customer's behalf (hosting, backlinks, ad spend), one-off or monthly, visible to the client.
`tickets`	Support threads between a customer and staff, with priority and workflow status; both sides write.
`planner`	The team's global task board — Planned / Doing / Done / Discarded, assignees, checklists, optional project link. Staff-only.
`calendar`	Bookable time: guests request calls, clients schedule from the portal, staff confirm and block out windows; reminder emails per platform.
`team`	The platform's own operators: invite with a role (owner / admin / member), deactivate without deleting history; feeds assignee pickers.
`email`	Transactional email from the platform's own domain via its own Resend account — mail goes out as the brand, never as Dash4Devs. Key server-side only, redacted from whoami.
`logs`	The platform's own request trail: every authenticated platform + site API call, filterable by method, module and status class.
`reports`	Report templates run on demand — PDF builder + email delivery.
`integrations`	Third-party providers with per-platform status, credential tests and scheduled syncs.

Grants are per platform: an agency might take nearly everything; a fleet of catalog sites might take records, customers, websites, inventory, media, pages and insights and nothing else.

The modules

Key	What it does
`records`	The custom-data engine — declare record types, get a generic filtered/sorted/paginated surface. Most other modules ride it.
`customers`	The people the platform serves, and portal auth: customer CRUD, JWT portal login scoped to one platform, session revocation.
`projects`	The unit of work, per customer — the spine the rest hangs off: a customer has projects; a project has a website, a board, to-dos, tickets, expenses and files.
`websites`	The sites the platform builds and keeps alive: domain, environment, stack, status, uptime, last deploy — and per-site API keys (`dfd-site-*`) for the site surface.
`forms`	Dashboard-built forms — intake, signatures, file uploads, payment details — with a public submit path (honeypot + rate limiting) and submissions that can materialize into records.
`contacts`	Public-form leads worked as an inbox (`new → contacted → closed`), stored as `contact` records, with owner/admin email alerts.
`media`	The files library: uploads with WebP variants + LQIP placeholders, CDN delivery, folders/tags/labels, taggable to a customer or site.
`inventory`	A display-only product catalog (`product` records, draft/active, variations, gallery) served read-only to client sites. Deliberately not commerce: no cart, checkout or stock.
`pages`	CMS content for public surfaces — content types and items, SEO metadata, legal documents. Blog posts on client sites are content rows in a `blog` section.
`insights`	First-party analytics: pageviews, visitors, sessions, attribution — collected into the platform's own tables rather than GA4.
`invoices`	The platform invoicing its own customers — one-off invoices and retainers, pay links, status.
`expenses`	Costs incurred on a customer's behalf (hosting, backlinks, ad spend), one-off or monthly, visible to the client.
`tickets`	Support threads between a customer and staff, with priority and workflow status; both sides write.
`planner`	The team's global task board — Planned / Doing / Done / Discarded, assignees, checklists, optional project link. Staff-only.
`calendar`	Bookable time: guests request calls, clients schedule from the portal, staff confirm and block out windows; reminder emails per platform.
`team`	The platform's own operators: invite with a role (owner / admin / member), deactivate without deleting history; feeds assignee pickers.
`email`	Transactional email from the platform's own domain via its own Resend account — mail goes out as the brand, never as Dash4Devs. Key server-side only, redacted from whoami.
`logs`	The platform's own request trail: every authenticated platform + site API call, filterable by method, module and status class.
`reports`	Report templates run on demand — PDF builder + email delivery.
`integrations`	Third-party providers with per-platform status, credential tests and scheduled syncs.

Grants are per platform: an agency might take nearly everything; a fleet of catalog sites might take records, customers, websites, inventory, media, pages and insights and nothing else.