How to see who created or edited a person
In my account, I have no problem seeing the username of the person who "Last Changed" something. However, my friend cannot see any names of who changed an event or fact. We are both viewing someone who is marked as deceased.
Is there a setting my friend needs to change in order to see who "Last Changed"?
Respuestas
-
@Blau Debra
.
Debra
.
Short Answer: 'Yes', we can ALL see that for "Deceased" individuals/persons.
.
"Family Tree" of 'FamilySearch' is built on a "Open Edit" Platform - hence, why ANY "Registered" User/Patron can, (1) "Edit" (ie. Add, Delete; and/or, Change); and, ALSO, (2) "See" the "Contact Name" of the User/Patron who/that "Changed" any "Details" of ANY "Deceased" individual/person in "Family Tree" of 'FamilySearch'.
.
Now ...
That said ...
.
Is your Friend is using the "Web" version of "Family Tree" of 'FamilySearch'?
.
Or, is your Friend is using the "Mobile" Application version, of "Family Tree" of 'FamilySearch'?
.
Or, is your Friend, using the "Lite" version of "Family Tree" of 'FamilySearch'?
.
Now ...
Depending ...
.
IF, using the "Web" version of "Family Tree" of 'FamilySearch'; provided, that on the "Person/Details" page/screen in the, "Vitals" Section; and, "Other Information" Section, you have the "Detail View" SWITCH set to 'Green' (ie. On/See/View); THEN, you should easily be able to see the "Contact Name" of the User/Patron who/that "Changed" any "Details" of ANY "Deceased" individual/person in "Family Tree" of 'FamilySearch'.
.
.
Whereas; IF, the aforementioned SWITCH is NOT set to 'Green' (ie. On/See/View); THEN, you will NOT.
.
.
IF, using, either, the "Mobile" Application version; or, the "Lite" version of "Family Tree" of 'FamilySearch', it IS possible, to see the "Contact Name" of the User/Patron who/that "Changed" any "Details" of ANY "Deceased" individual/person in "Family Tree" of 'FamilySearch'; but, more "Selections" are needed/required.
.
I hope this helps.
.
Brett
.
0 -
Thanks much Brett. They were using web version and the settings were not set to green. Changing to green fixed it.
0