Published at: 2026-09-17

Configure tasks

Configure the fields, layout, record type, permissions, processes and statistical capabilities of the task in the preset object management.

Before you begin

  • The organization has applied for and activated the phased-release feature of object-based Tasks.
  • You have default object management and related configuration permissions.
  • The roles and business scenarios that require the use of object-based task forms have been confirmed.

Enter the task object

  1. Enter CRM Platform Management > Object Management > Default Object Management.
  2. Find the Task object.
  3. Open the task object configuration page.
  4. Check the task object information and default icon in Basic Information.

Configure fields

  1. Enter Field List.
  2. Check the default fields of the task object.
  3. Add or import custom fields according to business needs.
  4. Maintain field display names and other page-allowed field properties.
  5. Save the configuration.
Commonly used preset fields for task objects are as follows:
Field Type or Purpose Configuration Considerations
Title Single line of text Display can be controlled according to layout
Content Task Content Currently using Collaborative Rich Text 1.0
Executor Multi-select user field Group selection is not supported
Deadline Date/time Used for task deadlines
Reminder Task reminder Whether to display depends on the layout
Associated business data Associated customer, Opportunity and other data The specific object scope is subject to the actual configuration

Configure role permissions

  1. Enter Role Permission Settings.
  2. Select the target role.
  3. Configure permissions such as view list, view details, create, edit, void and delete.
  4. Save the configuration.
The scope of permissions is as follows:
Permissions or roles Scope
View, Create, and Edit Control business users’ viewing and maintenance of task data
Void Control whether the user can terminate the task and its subsequent to-dos
Delete Controls whether administrators can delete data in the Recycle Bin
CRM administrator Has corresponding management rights according to preset object management rules
Other roles Configure corresponding permissions according to actual business needs
[!IMPORTANT] Whether to display new, edit or invalidate operations in the user-facing interface not only depends on the layout, but also is affected by role function permissions, current user identity and existing rules of the task. Deletion is the administrator’s permission in the recycle bin and is not equivalent to invalidation at the user-facing interface.

Configure layout

Task objects support three types of layouts:
Layout Common default content Scope of influence
Details page layout Title, content, executor, deadline, reminder, related business data Task details display
Create/edit page layout New and edit fields for object-based tasks Task forms at the top of Feeds and in new updates
Mobile summary layout Title, content, executor, due date To-do tiles, Feeds feed summary and mobile list cards
Configuration steps:
  1. Enter the layout management of the task object.
  2. Configure the details page layout.
  3. Configure the layout of the create/edit page.
  4. Configure the mobile summary layout.
  5. Assign layouts to target roles and record types by page capabilities.
  6. Save the configuration.

Configure record type

Task object initialization provides default record type. Administrators can maintain task record types based on the organization’s current version capabilities, and control the task forms seen by different people by combining roles and layout assignments.

Configure processes

Task objects support access to business flows and workflows. Administrators can configure process rules based on task objects to include task creation, completion, and cancellation actions into automated processing.
After the process configuration is completed, test tasks should be used to verify whether the trigger conditions, execution actions, and target data are as expected.

Configure data permissions

Task object supports:
  • Basic data permissions.
  • Data permissions within departments.
  • Data sharing.
Administrators should control who can view and process task data based on organization management scope, and verify lists, details, and action buttons in conjunction with role function permissions.

Configure multiple languages

Task objects support access to the translation workbench. The following content can be maintained as a multilingual specification:
  • Customize fields, field names, and field display names.
  • Help information and field null value prompts.
  • Option value and record type.
  • Basic object information and tenant-level scenarios.
  • Details page layout and create/edit page layout.
  • Validation rules.

Configure BI statistics

After an organization enables the corresponding phased-release feature, task objects can be selected for BI reports. Administrators or report configurers can design reporting definitions based on the task fields available in the current version. The specific fields available for analysis are subject to the fields supported by the BI report designer.

Verify before going online

  1. Create a test task from the top of Feeds using the target role.
  2. Create a test task from the new-post entry point using the target role.
  3. Check whether the record type, fields and layout are correct.
  4. Check “Tasks I performed” and “Tasks I initiated” in Workbench > Tasks.
  5. Processing actions such as verification completion, rejection, redo, comment or rating.
  6. Verify View, Create, Edit, and Invalid permissions.
  7. Check the mobile summary, to-do, and feeds feed displays.
  8. Verify that processes, data permissions, and BI statistics match organization configurations.

Impact of phased-release rollout

Before official use, users should be explained:
  • The top of Feeds and new updates use the current object-based task form, and other entries may still use the original task form.
  • The object list page currently does not support configuring task objects.
  • The executor does not support selecting groups.
  • The deletion operation is adjusted to invalid. After invalidation, the data will not be entered into the recycle bin.
  • Foreground invalidation and administrator recycle bin deletion are different permissions.
  • The task content still uses collaborative rich text 1.0, and topics are not supported yet.
  • Web and App support current capabilities, H5 does not currently support publishing tasks.
  • Both new and old organizations need to apply for phased release, which will not be enabled by default.

Related topics

Submit Feedback