Difference between revisions of "About Roles and Data Visibility"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric |
||
| Line 1: | Line 1: | ||
__NOINDEX__ | __NOINDEX__ | ||
:*[[Roles]] specify high-level access rights to application objects | :*[[Roles]] specify high-level access rights to application objects | ||
:*[[Custom Access Criteria]] can be | :*[[Custom Access Criteria]] can be used to specify access rights for individual [[Record]]s (add, view, update, delete), based on record data, user characteristics, and any other available information. | ||
:*[[Visibility Controls]] define whether User data is available to other users, whether records in objects are visible or hidden and optionally, whether the User has rights to modify data records based on [[Record Owners|Record Ownership]] | :*[[Visibility Controls]] define whether User data is available to other users, whether records in objects are visible or hidden and optionally, whether the User has rights to modify data records based on [[Record Owners|Record Ownership]] | ||
:*[[Data Sharing Policies]] are a set of rules that enable users to share data across [[Teams]], with the level of access based on each User's [[Role]] | :*[[Data Sharing Policies]] are a set of rules that enable users to share data across [[Teams]], with the level of access based on each User's [[Role]] | ||
:: Note that [[Team Data Sharing Policies]] override record-level access specified by individual [[Visibility Controls]]. | :: Note that [[Team Data Sharing Policies]] override record-level access specified by individual [[Visibility Controls]]. | ||
:*[[Role Based Permission Control|Field Visibility (Role Based Permission Control)]], a security control that provides data visibility rights at the [[Fields|Field]] level | :*[[Role Based Permission Control|Field Visibility (Role Based Permission Control)]], a security control that provides data visibility rights at the [[Fields|Field]] level | ||
Revision as of 00:40, 21 June 2012
- Roles specify high-level access rights to application objects
- Custom Access Criteria can be used to specify access rights for individual Records (add, view, update, delete), based on record data, user characteristics, and any other available information.
- Visibility Controls define whether User data is available to other users, whether records in objects are visible or hidden and optionally, whether the User has rights to modify data records based on Record Ownership
- Data Sharing Policies are a set of rules that enable users to share data across Teams, with the level of access based on each User's Role
- Note that Team Data Sharing Policies override record-level access specified by individual Visibility Controls.
- Field Visibility (Role Based Permission Control), a security control that provides data visibility rights at the Field level