Row/Column Permission Effects - DingTalk Help Center

Row / Column Permissions in Advanced Permissions

Permission	What you can configure
Edit: records related to me	- Record-level operations: whether the user can add and delete records. - Editable / deletable record scope: whether the user can edit records they created, or records where a person field includes them. - Other record permissions: whether records unrelated to the user are visible. - Field permissions: whether the user can view, edit, or add specified field content. - View permissions: whether the user can add, modify, or delete views.
Edit: specific field content	- Record-level operations: whether the user can add and delete records. - Field permissions: whether the user can view, edit, or add specified field content. - View permissions: whether the user can add, modify, or delete views.
Edit: custom scope	- Record-level operations: whether the user can add and delete records. - Editable / deletable record scope: whether the user can edit or delete records that match a filter. - Other record permissions: whether records unrelated to the user are visible. - Field permissions: whether the user can view, edit, or add specified field content. - View permissions: whether the user can add, modify, or delete views.
View only	- Readable record scope: whether records that match a filter are readable. - Field permissions: whether the user can read specified field content.

How Advanced Permissions Affect Forms

Form field	Behavior	Use case
One-way / two-way link field	Form view: when the user fills out the form inside AI Table, only linked records they have permission to see are shown.	Sales reps logging an order link to a customer, and only see the customers assigned to them.
	Form shared via link: linked records the viewer doesn’t have permission for are hidden — only the index column is shown (e.g. product name, but not stock count).	An office-supplies request form: stock counts are kept internal — the public form only shows item names.
Formula field	Form view: when the user fills out the form inside AI Table, the formula only computes over data the user has permission to see.	An expense form where employees only see the total of their own line items.
	Form shared via link: the formula result shows in full — the viewer doesn’t need permission to the source data.	An order form where the formula field shows the total quote — even if the viewer has no permission on the products table.
Single / multi-select with options sourced from another table	Form view: when the user fills out the form inside AI Table, only options they have permission to see are shown / selectable.	An internal survey shows only options for the user’s region. A new-hire form’s department dropdown shows only departments the user has permission to.
	Form shared via link: when the viewer fills out a shared form, all options are visible and selectable.	A customer-facing intake form lets respondents pick freely from all product categories.