Published at: 2026-09-17
Tasks overview
Tasks are used to release work arrangements, specify executors and deadlines, and continuously track task execution, feedback, and processing results. The current manual only explains the task capabilities after accessing the CRM default object management.
Applicable scenarios
- Organizations want to uniformly maintain task titles, content, executors, deadlines, reminders and associated business data.
- Employees need to centrally view and process the tasks they perform or initiate on the workbench.
- The executor needs to complete or reject the task, and the creator needs to request redoing, comments or ratings.
- Administrators need to control the view, create, edit, void and delete permissions of tasks by role.
- Organizations need to configure task fields, record types and page layouts for different roles.
- Organizations want to handle actions such as task creation, completion and cancellation through business flows or workflows.
- Report configurers need to select task objects in BI and design reporting definitions.
- International organizations need to maintain multilingual texts for task fields, layouts, record types, etc.
Objectability
After the task is connected to CRM default object management, it can be maintained according to the standard object method:
| Configuration scope | Main capabilities |
|---|---|
| Basic information | View and maintain task object information and default icons |
| Fields | Use preset fields, add or import custom fields, and maintain field display names |
| Layout | Configure details page, create/edit page and mobile summary layout |
| Permissions | Configure role function permissions, basic data permissions, intra-department data permissions and data sharing |
| Record type | Use the default record type and maintain related configurations according to version capabilities |
| Process | Integrate tasks into business flows and workflows |
| Analysis | After the organization enables the corresponding phased-release feature, select the task object in the BI report |
Entry point adaptation range
The task forms used by different portals are not exactly the same:
| Entry point | Current adaptation status |
|---|---|
| Task tab at the top of Feeds | Uses the current object-based task form |
| New-post entry point | Uses the current object-based task form |
| Work > Workspace > Task | Displays My Tasks and Tasks initiated by me |
| Object list page | Creating Task objects from the list is not currently supported |
| Set as task on a Feed detail page | Uses the legacy task form |
| Tasks created from Chats | Uses the legacy task form |
| Task components | Use the legacy task form and retain their existing behavior |
This manual focuses on the object-based task form. The table above identifies legacy entry points so users can understand why fields and actions may differ.
Client and content restrictions
- Web and App support current object-based task capabilities.
- Both the web and app support saving task drafts.
- H5 currently does not support publishing object-based tasks.
- The task content field uses collaborative rich text 1.0, which currently does not support topic capabilities.
- The executor is a multi-select field for personnel, but group selection is not supported.
- The front-end user terminates the task through void; after being voided, the related to-dos are cleared and the data does not currently enter the recycle bin.
- Delete is the administrator’s data processing permission in the recycle bin, and is not equivalent to invalidation at the user-facing interface.
Activation scope
The current capabilities are phased-release features, and both new and old organizations need to apply for activation through the organization’s activation process. Whether the portal is displayed is also affected by configurations such as role function permissions, record type, and layout assignment.