#Application in UI

#Data Block Permissions

Visibility of data blocks in a collection is controlled by view action permissions, with individual configurations taking precedence over global settings.

For example, under global permissions, the "admin" role has full access, but the Orders collection may have individual permissions configured, making it invisible.

Global permission configuration:

Orders collection individual permission configuration:

In the UI, all blocks in the Orders collection are not displayed.

Complete configuration process:

#Field Permissions

View: Determines whether specific fields are visible at the field level, allowing control over which fields are visible to certain roles within the Orders collection.

In the UI, only fields with configured permissions are visible within the Orders collection block. System fields (Id, CreatedAt, LastUpdatedAt) retain view permissions even without specific configuration.

• Edit: Controls whether fields can be edited and saved (updated).

  Configure edit permissions for Orders collection fields (quantity and associated items have edit permissions):

In the UI, only fields with edit permissions are shown in the edit action form block within the Orders collection.

Complete configuration process:

• Add: Determines whether fields can be added (created).

  Configure add permissions for Orders collection fields (order number, quantity, items, and shipment have add permissions):

In the UI, only fields with add permissions are displayed within the add action form block of the Orders collection.

• Export: Controls whether fields can be exported.
• Import: Controls whether fields support import.

#Action Permissions

Individually configured permissions take the highest priority. If specific permissions are configured, they override global settings; otherwise, the global settings are applied.

• Add: Controls whether the add action button is visible within a block.

  Configure individual action permissions for the Orders collection to allow adding:

When the add action is permitted, the add button appears within the action area of the Orders collection block in the UI.

• View: Determines whether the data block is visible.

  Global permission configuration (no view permission):

Orders collection individual permission configuration:

In the UI, data blocks for all other collections remain hidden, but the Orders collection block is shown.

Complete example configuration process:

• Edit: Controls whether the edit action button is displayed within a block.

Action permissions can be further refined by setting the data scope.

For example, setting the Orders collection so users can only edit their own data:

• Delete: Controls whether the delete action button is visible within a block.

• Export: Controls whether the export action button is visible within a block.

• Import: Controls whether the import action button is visible within a block.

#Association Permissions

#As a Field

• The permissions of an association field are controlled by the field permissions of the source collection. This controls whether the entire association field component is displayed.

For example, in the Orders collection, the association field "Customer" only has view, import, and export permissions.

In the UI, this means the "Customer" association field will not be displayed in the add and edit action blocks of the Orders collection.

Complete example configuration process:

• The permissions for fields within the association field component (such as a sub-table or sub-form) are determined by the permissions of the target collection.

When the association field component is a sub-form:

As shown below, the "Customer" association field in the Orders collection has all permissions, while the Customers collection itself is set to read-only.

Individual permission configuration for the Orders collection, where the "Customer" association field has all field permissions:

Individual permission configuration for the Customers collection, where fields have view-only permissions:

In the UI, the "Customer" association field is visible in the Orders collection block. However, when switched to a sub-form, the fields within the sub-form are visible in the details view but are not displayed in the add and edit actions.

Complete example configuration process:

To further control permissions for fields within the sub-form, you can grant permissions to individual fields.

As shown, the Customers collection is configured with individual field permissions (Customer Name is not visible and not editable).

Complete example configuration process:

When the association field component is a sub-table, the situation is consistent with that of a sub-form:

As shown, the "Shipment" association field in the Orders collection has all permissions, while the Shipments collection is set to read-only.

In the UI, this association field is visible. However, when switched to a sub-table, the fields within the sub-table are visible in the view action but not in the add and edit actions.

To further control permissions for fields within the sub-table, you can grant permissions to individual fields:

#As a Block

• The visibility of an association block is controlled by the permissions of the target collection of the corresponding association field, and is independent of the association field's permissions.

For example, whether the "Customer" association block is displayed is controlled by the permissions of the Customers collection.

• The fields within an association block are controlled by the field permissions in the target collection.

As shown, you can set view permissions for individual fields in the Customers collection.