Enterprise Archive creates an entry in the Participant page whenever the participant details are imported or ingested. Clicking the listed participant in the Participant page displays these details.

The history of a user or a participant is tracked in the following cases:

• When a Enterprise Archive User becomes a participant—This happens when details of an existing user are ingested or imported on the same identity ID. In this case, history indicates all changes from USER to SYSTEM.

• When a participant becomes a Enterprise Archive user—This happens when an ingested or imported participant information already exists, and a user with the same identity ID is created. In this case, history indicates all changes from SYSTEM to USER.

• When a Enterprise Archive user's attributes are updated using the Enterprise Archive UI, the Source field in the History tab displays the following updates:

  • SYSTEM to USER, if the user was previously an ingested or an imported participant and later converted to a Enterprise Archive User.

  • Source value will remain as “USER”, if the user was previously a Enterprise Archive user and then the attributes (such as First Name, Last Name and so on) have been edited.

    Note

    In this case, only the latest values of the user object are displayed.

• When a Enterprise Archive user's attributes are updated by the import or ingestion process, the Source field in the History tab displays the following updates:
  

  • SYSTEM to SYSTEM, if the user was previously an ingested or imported participant and now the participant information has been updated.

  • USER to SYSTEM, if the user was created through the Enterprise Archive UI and then converted as Participant through ingestion or import.

    Note

    User attributes can be edited or updated several times with different values by either ingesting or importing user attributes with same identity ID as key.

Participant/Participant Group behavior on Distribution Lists

When messages come in that have a Distribution List (DL) included in the To or Cc fields, the DL name gets created in Enterprise Archive as a Participant. However, if the DL name is only on the Bcc field the Participant does not get created.

• DLs coming in from Exchange get expanded and each member written in Enterprise Archive as a participant, as well as the DL itself gets written as a participant AND participant group. However, the DL as a participant and the DL as a Participant Group do not contain any members. The DL will just be an empty participant and participant group.

• DLs coming in from migrations or third-party are handled separately and depends on the nature of the XML coming from the third-party app on how things are handled. Typically, DLs are created as Participants and Participant Groups with no members. This can also be shut off.