The selected file /tmp/fileKOOKo8 could not be uploaded, because the destination sites/default/files/css/css_a91cd284035e73ba34d112bfed2f5a16.css is not properly configured.
  The selected file /tmp/fileqr6LUg could not be uploaded, because the destination sites/default/files/css/css_de1aa27776f1462d2b0d83a80ce4b92d.css is not properly configured.

Security and Modes refer generally to the ability for a particular user to access or change a particular set of data. The concepts are closely interrelated.

A Layout may operate in one or more of three possible modes;

• View - Fields within the Layout are not editable.
• Edit - Fields within the Layout are about an existing Item, may contain data, and the values in the Field are exposed to be changed by the user. Upon saving, any values changed by the user will be permanently stored on the Item, whereas the old values will be permanently deleted. (note: the builder can use a variety of tools make a copy of that value)
• Add - Fields within the Layout are not about an existing item, may contain data, and the values will be stored on a new Item created at the point the Layout is saved.

A Field's modes can be either dependent upon, or independent of, their parent Layout's mode.

Layout modes are determined by Security Settings, however in the absence of specific settings, the modes are inherited from any parent.

Field modes are inherited from the parent layout, but may be overridden by specific settings.

Layouts without any specific security settings are managed by their parents “behavior” (aka view, edit, add, save) controls. Fields without any specific security settings are also managed by the parents behavior controls. Checking for a parents behavior controls chains all the way up to the first parent that actually has its own behavior controls, and those control then control the behavior all children or chidren's children etc. who do not have their own behavior controls.

See also:

LDAP Connector