Difference between revisions of "About Roles and Data Visibility"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric m (Text replace - '__NOINDEX__' to '<noinclude>__NOINDEX__</noinclude>') |
||
Line 1: | Line 1: | ||
__NOINDEX__ | <noinclude>__NOINDEX__</noinclude> | ||
A user's access to data is determined by a number of factors: | A user's access to data is determined by a number of factors: | ||
Revision as of 00:11, 12 December 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 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.)
- Visibility Controls determine whether records owned by others are visible and optionally, whether they can be modified.
- Team Data Sharing Policies, which allow 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 Field level.