Closes the bulk of audit-pass-#1 admin gaps in one batch. New admin pages: - /admin/inquiries reads website_submissions with filter chips for berth/residence/contact + payload viewer per row. - /admin/sends reads document_sends with sent/failed filter chips and expandable body markdown; failures surface errorReason and any fallback-to-link reason from the SMTP retry. - /admin/email-templates lets per-port admins override the subject of each transactional template (8 templates catalogued in template-catalog.ts). Body editing is a follow-on; portal_activation + portal_reset are wired to honor the override via loadSubjectOverride. - /admin/reports replaces the "Coming in Layer 3" placeholder with a KPI dashboard: 4 KPI tiles, pipeline funnel bars, berth occupancy donut-bars, conversion %, refresh every 60s. - backup/import/onboarding admin pages replace placeholders with actionable guidance: backup posture + planned features, available CLI imports + planned UI, ordered onboarding checklist linking to admin pages. Existing pages widened: - settings-manager exposes the 9 berth-recommender tunables that were previously code-only (recommender_*, heat_weight_*, fallthrough_*, tier_ladder_hide_late_stage). - role-form covers all 19 RolePermissions schema groups; previously missing yachts/companies/memberships/reservations + missing documents.edit + files.edit checkboxes. snake_case residential labels replaced with friendly text. portal-auth.service.ts now also writes audit_log rows for portal invite, resend, activate, password-reset request, and reset (closes one more audit-pass-#2 gap while we were touching the file). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
104 lines
4.2 KiB
TypeScript
104 lines
4.2 KiB
TypeScript
/**
|
|
* Catalog of transactional email templates that admins can customize from
|
|
* /admin/email-templates. v1 supports subject-line overrides only; body
|
|
* overrides (HTML / merge-token authoring) are a follow-on iteration.
|
|
*
|
|
* To add a template here:
|
|
* 1. Pick a stable `key` and add it to TEMPLATE_KEYS (used for the
|
|
* `system_settings` row name).
|
|
* 2. List the merge tokens that the template renders so the admin
|
|
* knows what placeholders are valid in any future override.
|
|
* 3. Provide a `defaultSubject` string identical to what the code
|
|
* template emits when no override is set. Subject comparisons in
|
|
* the admin UI rely on this.
|
|
*/
|
|
|
|
export const TEMPLATE_KEYS = [
|
|
'portal_activation',
|
|
'portal_reset',
|
|
'portal_invite_resend',
|
|
'crm_invite',
|
|
'inquiry_client_confirmation',
|
|
'inquiry_sales_notification',
|
|
'residential_inquiry_client_confirmation',
|
|
'residential_inquiry_sales_alert',
|
|
] as const;
|
|
|
|
export type TemplateKey = (typeof TEMPLATE_KEYS)[number];
|
|
|
|
export interface TemplateMetadata {
|
|
key: TemplateKey;
|
|
label: string;
|
|
description: string;
|
|
/** Token names available inside the subject (and future body) overrides. */
|
|
mergeTokens: string[];
|
|
/** The literal subject the code template uses when no override is set. */
|
|
defaultSubject: string;
|
|
}
|
|
|
|
export const TEMPLATE_CATALOG: Record<TemplateKey, TemplateMetadata> = {
|
|
portal_activation: {
|
|
key: 'portal_activation',
|
|
label: 'Portal — activation invite',
|
|
description:
|
|
'Sent to a client when an admin invites them to activate their portal account. Contains the activation link.',
|
|
mergeTokens: ['portName', 'recipientName', 'ttlHours'],
|
|
defaultSubject: 'Activate your {{portName}} client portal account',
|
|
},
|
|
portal_reset: {
|
|
key: 'portal_reset',
|
|
label: 'Portal — password reset',
|
|
description:
|
|
'Sent when a portal user requests a password reset. Contains the reset link with a short TTL.',
|
|
mergeTokens: ['portName', 'recipientName', 'ttlMinutes'],
|
|
defaultSubject: 'Reset your {{portName}} client portal password',
|
|
},
|
|
portal_invite_resend: {
|
|
key: 'portal_invite_resend',
|
|
label: 'Portal — invite resend',
|
|
description: 'Re-sent activation email when an admin resends a pending portal invite.',
|
|
mergeTokens: ['portName', 'recipientName', 'ttlHours'],
|
|
defaultSubject: 'Activate your {{portName}} client portal account',
|
|
},
|
|
crm_invite: {
|
|
key: 'crm_invite',
|
|
label: 'CRM — staff invite',
|
|
description: 'Sent to a new staff user when an admin invites them to the CRM.',
|
|
mergeTokens: ['portName', 'recipientName', 'ttlHours'],
|
|
defaultSubject: 'You have been invited to {{portName}} CRM',
|
|
},
|
|
inquiry_client_confirmation: {
|
|
key: 'inquiry_client_confirmation',
|
|
label: 'Inquiry — client confirmation',
|
|
description: 'Auto-reply confirmation sent to the client after a website berth inquiry.',
|
|
mergeTokens: ['portName', 'recipientName', 'mooringNumber'],
|
|
defaultSubject: 'We received your inquiry — {{portName}}',
|
|
},
|
|
inquiry_sales_notification: {
|
|
key: 'inquiry_sales_notification',
|
|
label: 'Inquiry — sales notification',
|
|
description: 'Internal alert sent to the sales team when a new website inquiry arrives.',
|
|
mergeTokens: ['portName', 'clientName', 'mooringNumber', 'email'],
|
|
defaultSubject: 'New berth inquiry — {{clientName}}',
|
|
},
|
|
residential_inquiry_client_confirmation: {
|
|
key: 'residential_inquiry_client_confirmation',
|
|
label: 'Residential inquiry — client confirmation',
|
|
description: 'Auto-reply sent to the client after a residential property inquiry.',
|
|
mergeTokens: ['portName', 'recipientName'],
|
|
defaultSubject: 'We received your residential inquiry — {{portName}}',
|
|
},
|
|
residential_inquiry_sales_alert: {
|
|
key: 'residential_inquiry_sales_alert',
|
|
label: 'Residential inquiry — sales alert',
|
|
description: 'Internal alert sent to residential sales recipients when an inquiry arrives.',
|
|
mergeTokens: ['portName', 'clientName', 'email', 'phone'],
|
|
defaultSubject: 'New residential inquiry — {{clientName}}',
|
|
},
|
|
};
|
|
|
|
/** system_settings key for a template's subject override. */
|
|
export function settingKeyForSubject(key: TemplateKey): string {
|
|
return `email_template_${key}_subject`;
|
|
}
|