FieldPermissionsEntities
Breaks field-level permissions into their underlying rules to help you understand exactly how visibility and edit rights differ across users and groups.
Select
The AppId column is required in the WHERE clause. The server will use the Kintone APIs to filter the results by this column. By default, the server will process other filters client-side within the server.
For example, the following queries are processed server side:
SELECT * FROM FieldPermissionsEntities WHERE AppId = 6 SELECT * FROM FieldPermissionsEntities WHERE AppId = 6 AND IsPreview = false
Columns
| Name | Type | References | Description |
| AppId [KEY] | Integer | Identifier of the Kintone app whose field-permission assignments are being examined or updated. | |
| Code [KEY] | String | Field code that identifies the specific app field for which detailed entity-level permissions are defined. | |
| EntityType | String | Type of entity receiving the field permission, such as a user, group, or department, allowing you to understand how access is structured across the organization. | |
| EntityCode | String | Code that uniquely identifies the user, group, or department to which the field permission applies. | |
| Accessibility | String | Permission level granted to the entity, indicating whether the entity can view, edit, or is restricted from interacting with the field.
The allowed values are READ, WRITE, NONE. | |
| IncludeSubs | Boolean | Indicates whether field permissions granted to a department should also apply to its subordinate departments, supporting hierarchical access control. |
Pseudo-Columns
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description | |
| IsPreview | Boolean | Indicates whether to retrieve field-permission details from the preview environment ('true') or from the live environment ('false'). The default value is 'true'. |