What can the Doc type be used for?
Influencer management
If you run operations at a livestream commerce company and use AI Table to manage influencers, the table used to hold only structured info — handle, follower count, niche. Now, open the row and create a full illustrated profile for each influencer right in the same record.Project management
Click any task to view / edit the full details — write the spec right inside your project tracking table.Product management
Click any product record to view / edit the full description.Knowledge base
Every AI Table is now a knowledge base out of the box.Basics
Upgrade an existing table to “table as doc”
Double-click the first field name to open the editor — pick Doc as the type to enable table as doc. New tables ship with this turned on by default. A doc icon appears next to the text in the first column. The icon distinguishes “no doc yet” from “doc created”.Edit a doc
Click the View button on the first field of any row to expand the record. Click the blank area below in the right detail pane to start writing — once you type, the record’s doc is created. Type ”/” to summon doc tools; the doc toolbar also appears at the top — the editing experience matches DingTalk Docs.Edit in doc mode
Click the icon in the upper-right and pick Open as doc — switch to full doc editing mode. Doc mode unlocks all DingTalk Docs features. Edits and comments sync between the two views.Change how records expand
Click the icon to the right of the view name to open view settings — switch the record-view style. AI Table supports three ways to expand a record:- View in right side panel
- View in modal
- View as full page
Share
Click Share in the upper-right — pick Send to chat or Copy record link.Permissions
Advanced permissions for “table as doc” split into three parts:- Title — default view permission; you can also enable add and edit.
- Fields — display follows field permissions; only manage permission can add fields.
View Add Edit Behavior ❌ ❌ ❌ Field hidden ✅ ✅ ❌ Field shown; clicking shows “can’t edit” ✅ ✅ ✅ Field shown; double-click to edit normally - Doc — body inherits the title’s permissions by default. Role-group member info syncs to doc permissions; doc permissions can be edited inside the doc. The effective permission is the higher of advanced and doc permissions.
| Advanced permission | Doc body permission | Behavior |
|---|---|---|
| None | Can’t view | Can’t open doc — prompted to request access |
| Can view | Can view doc body | |
| Can edit | Can edit doc body | |
| View / Edit | Can’t view | Title and accessible fields shown, no body |
| Can view | Title, accessible fields, body shown | |
| Can edit | Title, accessible fields, body shown (editable) |
Doc view
| Title perm | Field-content perm | Body perm | Behavior |
|---|---|---|---|
| ❌ | ❌ | ❌ | Can’t open doc — prompted to request access |
| ❌ | ❌ | ✅ | Body shown (title viewable, not editable) |
| ❌ | ✅ | ❌ | Doesn’t exist |
| ✅ | ❌ | ❌ | Title shown; rest shows “advanced permissions enabled” |
| ❌ | ✅ | ✅ | Doesn’t exist |
| ✅ | ❌ | ✅ | Title and body shown; rest shows “advanced permissions enabled” |
| ✅ | ✅ | ❌ | Title and field content shown; rest shows “advanced permissions enabled” |
| ✅ | ✅ | ✅ | Title, field content, and body shown |
Share-card view
| Title perm | Field-content perm | Body perm | Behavior |
|---|---|---|---|
| ❌ | ❌ | ❌ | Hidden — prompted that advanced permissions are on |
| ❌ | ❌ | ✅ | Title and body shown |
| ❌ | ✅ | ❌ | — |
| ✅ | ❌ | ❌ | Title and body shown |
| ❌ | ✅ | ✅ | — |
| ✅ | ❌ | ✅ | Title and body shown |
| ✅ | ✅ | ❌ | Title and field content shown (only when advanced permissions are off; with them on and using the union-take-higher rule, this case doesn’t exist) |
| ✅ | ✅ | ✅ | Title, field content, and body shown |