Field-Level Security

Administrators and managers can secure fields through the Define Fields functionality, allowing access to or denying access from specific users or teams of users. Users can be given “full access,” “read only access,” or “no access” to fields on a user-by-user basis. A field has a Default Permission that applies to all users until modified by the administrator. Field-Level Security (FLS) can be set on an inclusive (“allow only these users to have full access”) or exclusive basis (“allow full access to everyone except these users”). Users cannot limit access to some core fields or system fields because they are required for basic ACT! functionality

FLS uses three levels of access:
Full Access• – User can view and modify data in the field.
Read Only Access•  – User can view data in the field, but not modify it.
No Access•  – User can neither view nor modify data in the field.

All users who can access a record can access read-only fields in that record in searches, reporting, mail merge, and views. Many system fields in ACT!, such as Edit Date and Create Date, are permanently designated as read-only.If a user has “no access” to a particular field, it’s as if the field does not exist for that user. When that user accesses the database, the no-access field will not appear in any view, and the user cannot access the contents of a “no access” field in any way.

Field access can be controlled using one or more types of permissions:

Default permission• – The base access level to a field which, in the absence of any team or user permissions, applies to all users of the database. The default permission applies to all users not affected by any team or user permissions.

Team permission• – Access granted to user members of a specific team. Team permission takes precedence over the default permission.

User permission• – Explicit access granted to a specific user. User permission takes precedence over both team permission and the default permission.