...
History records are created at logical points during Registry operations, such as inviting a new person to the platform, or adding a person to a group. These records are stored in the table cm_history_records, and can be linked to a CO Person, a CO Person Role, an Organizational Identity, a CO Group, and/or an Organizational IdentityEmail List. For example, changing an Organizational Identity name will have a history record linked to that Organizational Identity only, whereas adding a CO Person to a CO will have a history record linked to both the Organizational Identity and the CO Person.
...
Administrators can view History Records through the Registry web interface, however records are viewable according to certain rules:
History Record Applies To | Authorized Viewers |
|---|---|
Organizational Identity | If Organizational Identities are pooled, any Administrator. |
CO Person | CO and COU Administrators within the CO. |
CO Person | CO Administrators within the CO, and COU Administrators for the COU of the CO Person Role. |
CO Person | CO Administrators within the CO, and COU Administrators for the COU of the CO Person Role. |
| CO Group | CO Administrators within the CO, and Owners of the CO Group. |
| CO Email List | CO Administrators within the CO. |
Changelogs
Database level transactions logs ("Changelogs") are available for select attributes as of v0.9.4, and for most attributes as of v1.0.0.
...