Published at: 2026-09-17
Collaborative rich text
Overview
The collaborative rich text field extends rich text with collaborative editing capabilities, including cloud drive file insertion, polls, and CRM object references. It is suitable for team collaboration editing, proposal documents, and other scenarios that require multi-user collaboration. If you only need single-user text-and-image editing, use a rich text field.
Basic specifications
| Attribute | Description |
|---|---|
| Applicable scenario | Product design documents, collaborative proposals, team documents, text-and-image content with CRM data references |
| Maximum characters | 131,072 characters |
| Mixed text and image | Supported |
| Platform support | Full support on web and mobile |
When to use collaborative rich text vs. rich text
| Scenario | Recommended field type | Reason |
|---|---|---|
| Team-edited proposal documents | Collaborative rich text | Requires cloud drive files, polls, CRM object references, and other collaboration features |
| Content that references CRM data | Collaborative rich text | Rich text does not support CRM object references |
| Content that embeds cloud drive files or polls | Collaborative rich text | Rich text does not support these two features |
| Image uploads, tables, and links on mobile | Collaborative rich text | Rich text does not support these features on mobile |
| Product descriptions, announcements, and other display-only content | Rich text | Only requires basic formatting, no collaboration needed |
| Contract terms with fine formatting (font color, alignment) | Rich text | Collaborative rich text does not support font color or alignment |
[!TIP] Quick rule: If you need “team collaboration + CRM data references + full mobile editing”, choose collaborative rich text. If you only need “attractive text-and-image formatting + fine format control”, choose rich text. See Rich text.
Collaborative rich text editing capabilities
The following capability matrix is based on the source document and is organized by platform:
| Feature | Web | Mobile (ShareCRM app) | Third-party app |
|---|---|---|---|
| Upload images | Supported | Supported | Supported |
| Tables | Supported | Supported | Supported |
| Links | Supported | Supported | Supported |
| Strikethrough | Supported | Supported | Supported |
| Cloud drive files | Supported | Supported | Not supported |
| Polls | Supported | Supported | Not supported |
| CRM object references | Supported | Supported | Supported |
| Bold | Supported | Supported | Supported |
| Italic | Supported | Supported | Supported |
| Emoji | Supported | Supported | Supported |
| Ordered list | Supported | Supported | Supported |
| Unordered list | Supported | Supported | Supported |
| Left, right, and justify alignment | Not supported | Not supported | Not supported |
| Font color | Not supported | Not supported | Not supported |
| Location | Not supported | Not supported | Not supported |
| Voice | Not supported | Not supported | Not supported |
| Voice to text | Not supported | Not supported | Not supported |
| OCR | Not supported | Not supported | Not supported |
[!NOTE] Collaborative rich text provides full editing capabilities on both web and mobile (including image uploads, tables, links, cloud drive files, polls, and CRM object references), but does not support font color or alignment. Use rich text for fine formatting control.
Feature comparison: collaborative rich text vs. rich text
| Feature | Collaborative rich text | Rich text |
|---|---|---|
| Upload images (web) | Supported | Supported |
| Upload images (mobile) | Supported | Not supported |
| Tables (web) | Supported | Supported |
| Tables (mobile) | Supported | Not supported |
| Links (web) | Supported | Supported |
| Links (mobile) | Supported | Not supported |
| Strikethrough | Supported | Supported |
| Cloud drive files | Supported | Not supported |
| Polls | Supported | Not supported |
| CRM object references | Supported | Not supported |
| Left, right, and justify alignment | Not supported | Supported |
| Font color | Not supported | Supported |
| Bold / Italic / Emoji / Lists | Supported | Supported |
[!TIP] Key differences: Collaborative rich text adds three unique features — cloud drive files, polls, and CRM object references — and has stronger mobile editing capabilities. Rich text adds two fine formatting features — font color and alignment.
Configuration highlights
- Default value: Supports fixed text only. Formulas are not supported.
- Filtering limitation: Collaborative rich text fields cannot be used as filter conditions for roll-up summary fields or lookup relationship fields.
- Field name: Must be unique within the object.
- API name: Auto-generated by the system. Do not modify unless necessary.
Default values and required settings
Default value
The collaborative rich text field default value supports fixed text input only. Formula calculations are not supported.
[!NOTE] The default value is auto-filled when creating a new record in the front end. Users can modify it after pre-filling. After modifying a default value, historical data is not recalculated.
Required configuration
- Field-level required: On the field configuration page, set “Required” to “Yes”. This applies across all scenarios (front-end entry and back-end import). Missing values prevent saving.
- Layout-level required: If the field is required only in specific business scenarios, set it as not required in the field properties. Then, in the specific page layout editor, check “Required”.
- Conditional required: If the required condition depends on the value of another field, configure validation rules.
FAQ
Collaborative rich text content is not fully displayed
Cause: The content may have been copied from other pages and carries incompatible text styles.
Solution: Copy the text content out, clear the formatting, and paste it back into the collaborative rich text field.