ClientManagerBlazor · extracted from source, not guessed

Communication Entity Field Reference

The unified Email/SMS record — appears standalone at /communications and as a sub-tab on Project, Company, Person, and Lead. Documented once here; the other entities' guides link back to this page rather than repeating it. Pulled directly from the real .razor components.

3 tabs
7 panels/sub-grids
20+ fields

Click a tab below (or the arrow) to expand it and see its fields.

Communication

One compose form handles both Email and SMS — the selected Type determines which channel it actually sends through. Recipients-first: To/Cc/Bcc drive automatic Client/Vendor visibility, and mixing a client with a vendor on one message is blocked.

Reachable four ways: standalone at /communications, as a sub-tab on Project/Company/Person/Lead, from the banner bar's Email quick-compose button, or via each entity's Notes-style panel.

01CommunicationThe message itself — channel, recipients, subject, and body.

Type, Sender, Date
Communication Type*The channel — email vs. SMS is decided by whether the selected type's name contains "SMS."Required
From UserWho's sending it — reloads that user's signature when changed.Editable
Communication DateDefaults to today.Editable
Include SignatureOnly shown if the From User has a saved signature; toggling it inserts/removes the signature block from Message Body.Editable

Relates To
Relates ToOptionally links the message to a Project, Company, Person, or Lead in addition to whoever it's sent to.Editable
Project / Company / Person / LeadWhichever one is picked above — mutually exclusive, only one is kept.Editable

Recipients
To*At least one recipient is required. A "+ New Contact" shortcut adds someone on the fly without leaving the form.Required
Cc / BccAdditional recipients.Editable

Client/Vendor Visible are never manually checked here — they're computed from the actual recipient mix, and the save is blocked outright if it would mix a client and a vendor on the same message ("split it into separate communications instead").

Subject, Body & Attachments
Message Subject* / Description*The subject line and a short internal label.Required
Message Body*The message content, rich text.Required
AttachmentsFiles sent along with the message — genuinely delivered as email attachments, not just stored.Editable

02RepliesThe reply thread — requires saving the communication first.
Reply threadEvery reply so far, with sender/date and an "Internal only" badge on anything not client-visible.Read-only
ReplyYour reply text.Required
Visible to clientWhether the client sees this reply — checked by default.Editable
Send SMSAlso sends the reply as a text.Editable
03AttachmentsFiles attached to this communication, separate from any attached at compose time.
Type / Description / Notes / FilesUpload one or more files with shared metadata.Editable
UploadedWhen the file was added.Read-only