Difference between revisions of "About Roles and Data Visibility"

From AgileApps Support Wiki
imported>Aeric
imported>Aeric
Line 2: Line 2:
:*[[Custom Access Criteria]] are a set of rules which define the [[Users]] who can perform various Actions (add, view, update, delete) on [[Record]]s in application [[Objects]]
:*[[Custom Access Criteria]] are a set of rules which define the [[Users]] who can perform various Actions (add, view, update, delete) on [[Record]]s in application [[Objects]]
:*[[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]] in a primary [[Team]]
:*[[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 22:33, 20 June 2012

Note that Team Data Sharing Policies override record-level access specified by individual Visibility Controls.