Difference between revisions of "About Roles and Data Visibility"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric |
||
| Line 7: | Line 7: | ||
:*[[Visibility Controls]] determine whether records in objects are visible to other users and optionally, whether those users can modify the data | :*[[Visibility Controls]] determine whether records in objects are visible to other users and optionally, whether those users can modify the data | ||
:* [[Team Data Sharing Policies]] enable users to share data across [[Teams]]. These settings override the record-level access permissions specified in the individual's Visibility Controls. | :* [[Team Data Sharing Policies]] enable users to share data across [[Teams]]. These settings override the record-level access permissions specified in the individual's Visibility Controls. | ||
:*[[Role-Based Field Visibility | :*[[Role-Based Field Visibility]] can also be used to specify data visibility at the [[Fields|Field]] level | ||
Revision as of 01:11, 17 October 2012
- Application Access determines who can use an application
- Access Profiles specify administrative and global-access permissions
- Roles specify high-level access rights to individual application objects
- The privileges granted in Access Profiles and Roles are additive. If either the Access Profile or the Role grants permission to perform some operation on an object, then the user has that permission.
- Data Access Permissions determine the data a user can normally access, absent additional Visibility Controls.
- Visibility Controls determine whether records in objects are visible to other users and optionally, whether those users can modify the data
- Team Data Sharing Policies enable users to share data across Teams. These settings override the record-level access permissions specified in the individual's Visibility Controls.
- Role-Based Field Visibility can also be used to specify data visibility at the Field level