If the field is disabled in the web, do the accesses work?
No. The field must be included in WEB — then the user will see it in the web interface, or in API, then the API user will be able to retrieve data from this field.
What is the difference between the two types of editing?
Entered during addition in WEB — access to modify the field during the addition of a row. Not applicable in header/footer/prefilter.
Editable in WEB — access to modify the field after the addition of a row to the table or in the header/footer.
How can I use the separation of access to add and change a field?
For example, in a table where Payments are added, it makes sense to have the ability to change the amount when adding a payment, but then restrict the ability to change it for already added rows.
If a user has a field visibility restriction, will he be able to access the data in it?
There is a setting that restricts field visibility by roles — if roles are specified, only they can see the field.
If a role does not see the field, then the role settings for editing and adding are irrelevant for it.
If you make the field visible only to the Creator — it will be highlighted in red. Such fields can be quickly hidden by double-clicking the right mouse button on the eye. This setting is often used for technical fields — it is more convenient than completely hiding the field from the web.
Visibility in the web is disabled only when the field is obsolete and will not be used, but contains archival data.
But there are no strict restrictions, it's just more convenient.
If " Hidden by default " is enabled, will the user be able to display this field?
Yes. This setting hides the field when the page loads in eye.
How do I set up field visibility to quickly hide the creator interface?
Set visibility to Creator only.