Difference between revisions of "Role-Based Field Visibility"
From LongJump Support Wiki
imported>Evelyn m |
imported>Aeric m (Text replace - 'Form Layout' to 'Form') |
||
| Line 11: | Line 11: | ||
;Considerations: | ;Considerations: | ||
*When a field is added to a [[Form | *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 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 Logs|Audit Log]] | *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 Logs|Audit Log]] | ||
Revision as of 00:33, 13 July 2011
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