Access Controls

The platform supports several kinds of access controls:

• Data Access Permissions define the data (Objects, Records, and Fields) that Users in Teams are privileged to view or modify, by virtue of their Role assignments and other factors.

• The Access Control permission is an Administrative Permission that lets a user Roles and Password Policies.

• The User Management permission is an Administrative Permission lets a user manage Users and Teams.

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]].

• 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 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 Field level.