By default tab and column permissions are applied on the server side. Once the form is loaded the permissions are not evaluated again. Column will remain in Write, Read or Hidden mode until the form is submitted and re-opened.

Using Apply permissions dynamically option (found at the bottom of the permissions interface), you can apply permissions in real time. As soon as you make a change to one of the column used in conditions for tab/column permissions, this permission rule is re-evaluated and applied. You can set columns to be read-only, writable or hidden instantly by changing values of other columns.

There are several limitations to the dynamic permissions feature (these limitations do not apply to the Office 365 app version):

• Only certain column types are supported for dynamic conditions:
  • Single line of text
  • Choice
  • Number
  • Currency
  • Yes/No
  • Lookup
  • Infowise Connected Field
  • URL or Picture
  • Infowise Color Choice Field
  • Infowise URL Plus Field
  • Conditions values cannot include functions, arithmetic operations or reference to unsupported columns. You can use scalar values (such as Marketing or 1000) or single column references (such as [Option]).
  • Validation rules, such as Required field validation, are always applied, even if the column is set to read-only or hidden. You should not make a column required if you plan to allow users to set it to hidden, as they will not be able to submit the form.

Unsupported conditions are evaluated on the server side before the form loads and are not re-evaluated dynamically.

For example, suppose you have a column using Person or Group column type. Even when the user value is changed on the form, the condition is not re-evaluated.