AgileApps Support Wiki

Difference between revisions of "About Roles and Data Visibility"

From AgileApps Support Wiki
imported>Aeric
imported>Aeric
Line 1: Line 1:
__NOINDEX__
__NOINDEX__
:*[[Application Access]] determines who can use an application
A user's access to data is determined by a number of factors:
:*[[Access Profiles]] specify administrative and global-access permissions
 
:*[[Roles]] specify high-level access rights to individual application objects
:* The user's [[Access Profile]] specifies global access permissions and administrative permissions.
:* 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.
:* The [[Application Access]] settings determine which applications the user can run. The [[Objects]] available to the user are therefore the combination of
:*[[Visibility Controls]] determine whether records in objects are visible to other users and optionally, whether those users can modify the data
:::a. Objects that are part of the running application
:* [[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.
:::b. Objects that or are shared from other applications.
:*[[Role-Based Field Visibility]] can also be used to specify data visibility at the [[Fields|Field]] level
 
:* The user's [[Role]] in the application, as specified by the [[Application Access]] settings), specifies 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.)
 
:* The [[Team]] the user belongs to, and the access to records owned by other team members, as determined by the user's [{Role]].
 
:*[[Visibility Controls]] determine whether records owned by others are visible and optionally, whether they can be modified.
 
:* [[Team Data Sharing Policies]], which allow to data to be shared across Teams. (These settings override the record-level access permissions specified in the individual's Visibility Controls.)
 
:*[[Role-Based Field Visibility]], when used, specifies data visibility at the [[Fields|Field]] level.

Revision as of 01:44, 17 October 2012

A user's access to data is determined by a number of factors:

  • The user's Access Profile specifies global access permissions and administrative permissions.
  • The Application Access settings determine which applications the user can run. The Objects available to the user are therefore the combination of
a. Objects that are part of the running application
b. Objects that or are shared from other applications.
  • The user's Role in the application, as specified by the Application Access settings), specifies 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.)
  • The Team the user belongs to, and the access to records owned by other team members, as determined by the user's [{Role]].
  • Visibility Controls determine whether records owned by others are visible and optionally, whether they can be modified.
  • Team Data Sharing Policies, which allow to data to be shared across Teams. (These settings override the record-level access permissions specified in the individual's Visibility Controls.)
Retrieved from "https://agileappscloud.info/aawiki-src/index.php?title=About_Roles_and_Data_Visibility&oldid=9185"