ACT! Security Model 3

Rex

Types of Security in ACT!

Database Security• – Controls who can use a database. Individuals access an ACT! database using a unique user name. The ACT! database administrator also can implement a password policy to further restrict database access.

Feature Security• – Controls who can use specific features. Each ACT! database user is assigned a role. Each role dictates which features (permissions) a user can access in the application. ACT also offers custom permissions which can be granted to or withheld from a user.

Record Security• – Controls who can see data and what data they can see. Every record in ACT! has an owner known as a “record manager.” When a record is marked “private,” only the record manager can view it. ACT! users can access all public data, their private data, and any limited access records they have specifically been granted access to. Administrators can access all records except private records owned by other users. A user must have access to a parent record (contact, company, or group) in order to access any extended data (notes, history, activities, opportunities, or secondary contacts) belonging to that parent record.

Field-Level Security • – Controls who can see and modify fields and what fields they can view and modify. Users who are assigned administrator or manager roles in ACT can secure fields, so that the information is available only to specific users and/or teams of users. Administrators or Managers can give “full access,” “read only access,” or “no access” to fields on a user-by-user basis3. A field can be given a Default Permission that applies to all users. Some core fields and system fields cannot be secured because they are required for basic ACT! functionality.