Configuring an identity is optional.
For each application, you can define identity parameters based on an attribute value that will be matched to the OnBase login values. This is how the system will find the currently logged in user's object to identify them.
In some instances a more complex approach must be taken using security attributes to create the desired results. Security attributes can be used to evaluate relationships between one or more Association classes to determine security attribute control. In order to use class association levels to determine security rights using security attributes, three main steps are required. First, you must create security attributes. Second, you must configure user identification for applications. Lastly, you must assign security attribute values to specific user groups.
To define an identity: