Rich-Text Custom Fields
What is a Rich-Text Field?#
A rich-text field is a custom field type that stores formatted, multi-line content. Unlike a plain text field, it supports bold, italic, links, bulleted and numbered lists, headings, and code blocks. It also supports inline images stored directly in your connected cloud provider (Dropbox or Google Drive).
Common use cases include:
- Meeting notes — capture structured notes directly on the contact or opportunity record
- Project descriptions — link-rich narratives with embedded mockups or screenshots
- Customer profile narratives — long-form background on key accounts, including logos or org charts
- Design briefs — annotated specs attached to an entity without leaving the CRM
Adding a Rich-Text Field#
Rich-text fields are created in Admin Settings the same way as other custom fields. Only users with the Admin role can add or remove custom fields.
- 1Go to Admin Settings → Custom Fields.
- 2Click "Add Field".
- 3Set the field type to "Rich Text".
- 4Enter a label — for example, "Meeting Notes" or "Project Brief".
- 5Choose which entity type this field should appear on (Contacts, Companies, Opportunities, etc.).
- 6Click Save — the field immediately appears on all records of that entity type.
Drag-and-Drop Field Order#
The order of custom fields in the Custom Fields list controls the order they appear on entity records. You can rearrange fields at any time:
- In Admin Settings → Custom Fields, locate the grip handle (
⠿) on the left of any field row. - Click and hold the grip handle, then drag the row to a new position.
- Release to drop — the order saves automatically.
- When you add a new field, the Custom Fields list smooth-scrolls down so the new field is visible at the bottom.
Editor Toolbar#
When a user edits a rich-text field on an entity record, a formatting toolbar appears above the editor canvas. The toolbar provides:
Kick-off call with Acme Corp
Discussed Q3 rollout timeline. Key action items:
- Send updated proposal by Friday
- Schedule follow-up with procurement lead
- Share API docs link
| Button | What it does |
|---|---|
| B (Bold) | Wraps selected text in bold formatting. |
| I (Italic) | Wraps selected text in italic formatting. |
| Link | Converts selected text into a clickable hyperlink. Paste or type the URL in the prompt. |
| • List | Starts or converts a selection to a bulleted list. |
| 1. List | Starts or converts a selection to a numbered list. |
| Code | Wraps selected text in a monospace code block. |
| Insert image | Opens the image picker — choose a file from your computer, paste from clipboard, or drag an image file into the editor. |
Inline Images#
Rich-text fields support embedding images directly in the content. Images are uploaded to your cloud storage provider at the moment of insertion and rendered inline when users view the record.
Inserting an image
- Drag and drop — drag an image file from your desktop directly into the editor. The file uploads automatically and the image appears inline.
- Paste from clipboard — copy an image (e.g. a screenshot) and paste it into the editor. You will be prompted to enter a filename before the upload begins.
- Insert image button — click the
Insert imagebutton in the toolbar to open a file picker.
Resizing an inline image
Click any inline image to select it. Four corner resize handles appear. Drag any corner to resize — the aspect ratio is preserved automatically.
Limits
- Maximum file size: 10 MB per image.
- Supported formats: PNG, JPEG, GIF, WebP, SVG.
Image Storage Configuration#
Before users can insert images, an Admin must choose which cloud provider and folder should receive uploads for each rich-text field.
- 1Go to Admin Settings → Custom Fields.
- 2Click the rich-text field you want to configure.
- 3Open the "Image storage" section in the field settings panel.
- 4Choose Dropbox or Google Drive from the provider picker. (The provider must already be connected in Admin Settings → Integrations.)
- 5Click the folder picker to choose or create a destination folder in that provider.
- 6Click Save.
Each rich-text field can point to a different folder. For example, you might store Meeting Notes images in Dropbox / CRM / meeting-notes and Design Brief images in Google Drive / Design / briefs.
Permissions & Security#
Because images live in your cloud provider, their visibility follows the cloud provider's sharing rules:
- Dropbox— uploaded files are shared as “link with access” by default, meaning anyone with the signed URL can view the image. Signed URLs are short-lived and regenerated on each page load.
- Google Drive— files are added to the configured folder. Access is controlled by the Drive folder's sharing settings. Coeffection requests a signed download URL on each view.
Coeffection stores only the file IDreturned by the cloud provider after upload. The actual image bytes never pass through or are stored on Coeffection servers. When a user views a record containing a rich-text field, the editor fetches a signed URL from the provider API and loads the image directly in the browser from the provider's CDN.
Deleting a cloud file from Dropbox or Google Drive will cause that image to display as broken in the editor. Coeffection has no way to detect this automatically — if an image goes missing, re-insert it from the cloud provider.