Built-in Access Levels

The Access Levels associated with built-in fields cannot be modified or deleted but you can, and should, use the built-in levels with fields that you create if your field contains the same type of information as the built-in field. While Access Levels are a valuable tool in securing information, creating too many levels can make your user permission configurations overly complex. The table below explains, in general terms, how the built-in levels are used.

Access Level

Type of Information

User Preference

Associated with the fields in the user type and individual user preferences. This type of information is typically not used in a document.

Personal Information

Information in a user's account that would typically also be displayed in a document such as name and email address. This level can be used for all of the personally identifying information in a document that would normally be concealed from reviewers during a blind review.

Account Information

Associated with most of the fields used to define and track the status of a user account. This type of information is typically not used in a document.

Reserved (3)

Associated with built-in utility selection fields such as state and month lists. These types of fields would typically not be directly used in a document but would act as Master Fields and provide option lists for the fields that are used in a document.

Reserved (4)

Reserved for future use.

Document Information

Associated with the fields that contain information about the document and its components - ID, parent form name, various timestamps, the current and previous states, etc.

Also see:

Using Access Levels

Setting User Permissions