Difference between revisions of "Role-Based Field Visibility"
From LongJump Support Wiki
imported>Aeric m (Text replace - 'Form Layout' to 'Form') |
imported>Aeric |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
Set Field Visibility based on Role. This option defines the [[Roles]] that are permitted to view and use the designated [[Field]]. Available field settings include: | Set Field Visibility based on Role. This option defines the [[Roles]] that are permitted to view and use the designated [[Field]]. Available field settings include: | ||
*Visible | :*Visible | ||
*Read-Only | :*Read-Only | ||
*Hidden | :*Hidden | ||
This control is created when a [[Fields#Add_a_Field|Field is Added]] to an object. | This control is created when a [[Fields#Add_a_Field|Field is Added]] to an object. | ||
:''Learn more: [[Visibility Controls]]'' | :''Learn more: [[Visibility Controls]]'' | ||
;Considerations: | ;Considerations: | ||
Latest revision as of 22:00, 16 October 2012
Set Field Visibility based on Role. This option defines the Roles that are permitted to view and use the designated Field. Available field settings include:
- Visible
- Read-Only
- Hidden
This control is created when a Field is Added to an object.
- Learn more: Visibility Controls
- Considerations
- When a field is added to a Form, the field visibility control is set to Visible by default
- When a new role is added, that role receives Visibility rights to all the fields across all the objects
- When this control is specified for a field, it will be enforced in the Field Audit Log; This means that the user Role determines whether a record is visible in an Audit Log