Difference between revisions of "Type Field Permissions"
From SmartWiki
Nancy Sabo (talk | contribs) |
|||
| (10 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
| − | When you use custom fields in conjunction with the [[UTA]], additional permissions are available. The Type Field Permissions control the visibility | + | When you use [[custom fields]], [[standard fields]] or [[submit buttons]] in conjunction with the [[UTA]], additional permissions are available. The Type Field Permissions control the visibility of the field or button for different [[Templates]]/[[Types]]. |
| − | [[Image:TypeFP.png]] | + | <!--[[Image:TypeFP.png]]--> |
| − | * '''Allow View Field''' – Defines on which templates/types the field will be displayed. | + | * '''Allow View Field''' – Defines on which templates/types the field or button will be displayed. |
| − | * '''Deny View Field''' – Defines on which templates/types the field will not be displayed. | + | * '''Deny View Field''' – Defines on which templates/types the field or button will not be displayed. |
* These permissions are used in conjunction with the [[Role Field Permissions]] and the [[Status Field Permissions]]. You must be in a given [[Role|role]] to see a field AND the field needs to be visible at that [[Status]]. | * These permissions are used in conjunction with the [[Role Field Permissions]] and the [[Status Field Permissions]]. You must be in a given [[Role|role]] to see a field AND the field needs to be visible at that [[Status]]. | ||
* In addition to Role, Status and Type field permissions, field visibility may also be controlled by [[Visibility Condition]]s. | * In addition to Role, Status and Type field permissions, field visibility may also be controlled by [[Visibility Condition]]s. | ||
| − | * This feature is available for | + | * This feature is available for [[Custom Field|custom fields]] at {{l1}}, {{l2}} and {{l3}} in a {{UTA}}. |
==See Also== | ==See Also== | ||
| + | * [[Field Permissions]] | ||
| + | * [[Visibility Condition]]s | ||
| + | * [[Batch Update Custom Field Settings]] | ||
{{VisibilityofCustomFields}} | {{VisibilityofCustomFields}} | ||
| − | + | ||
[[Category:Custom Fields]][[Category:Security]][[Category:Roles]] | [[Category:Custom Fields]][[Category:Security]][[Category:Roles]] | ||
Latest revision as of 15:16, 10 September 2018
When you use custom fields, standard fields or submit buttons in conjunction with the UTA, additional permissions are available. The Type Field Permissions control the visibility of the field or button for different Templates/Types.
- Allow View Field – Defines on which templates/types the field or button will be displayed.
- Deny View Field – Defines on which templates/types the field or button will not be displayed.
- These permissions are used in conjunction with the Role Field Permissions and the Status Field Permissions. You must be in a given role to see a field AND the field needs to be visible at that Status.
- In addition to Role, Status and Type field permissions, field visibility may also be controlled by Visibility Conditions.
- This feature is available for custom fields at Level 1, Level 2 and Level 3 in a .
See Also
Visibility of Custom Fields can also be controlled using:
- Role Field Permissions
- Status Field Permissions
- Type Field Permissions
- Field Permission Matrix
- Show/Hide Header
