If two PM wish to merge a profile is it necessary for then to ask to go on the trusted list first?

+7 votes
I am currently involved in a discussion concerning a merge of a long standing profile and a guest profile. After discussion with the originating PM

I initiate a merge. Another member suggested the guest  PM had to request to go on the trusted list of the original profile first before they could be merged.

I queried this as I can find no reference to PM's in agreement needing to request trusted list status before merging the profiles. This issue has never cropped up before, when I have been merging profiles

My understanding is if I wished to complete the merge I had to request to go on the trusted list first.  But this does not apply to the two PM - who are cousin's working in collaboration. In the end the merge was complete by someone else who is on the trusted having had worked in collaboration with the originating PM before.

Appreciate it if it could be clarified

Thank you for your advise Janet

Always happy to learn
WikiTree profile: Brett Mouton
asked Mar 8 in WikiTree Help by Janet Wild G2G6 Mach 1 (14,950 points)
edited Mar 8 by Janet Wild

If both profiles have a locked privacy level, the person completing the merge needs to be on both trusted lists to complete the actual merge.

That is my experience, Janet.

Great answer Lindy. Also if one of the profiles is privacy locked, a default merge cannot take place even if the permission came from the privacy locked profile.
Thank you Lindy

I just cannot see any reference to this in the help pages and had never come across it before.

Do you have a link for me to review, if you do I would appreciate it Thanks

3 Answers

+8 votes
Best answer

Hello Janet.

It all depends on the privacy level of the profiles to be merged.

Merging a profile is like editing or changing the information of the profile.

If both of the profiles to be merged are "Open" any Wiki Genealogist can complete the merge after the approvals for merging the profiles are recorded. (Privacy "Open" - any WikiTree member in good standing with a confirmed e-mail address who has signed the Wiki Genealogist Honor Code can edit it).

Please see:


Merges of profiles with privacy level other than "Open" need to be completed by someone on their Trusted List. If none of both profiles are "Open", only someone on the Trusted List of both profiles is able to complete such merge.

answered Mar 8 by Rubén Hernández G2G6 Pilot (273,850 points)
selected Mar 9 by Louis Heyman
+5 votes
Nope - you don't have to be on the trusted list or PM of both profiles, but it does make the merge go more quickly if you are. In essence, the PM of the 1st profile (either can be 1st, so don't get caught up in order) provides approval - the PM of the 2nd profile provides approval and the PM who provides the 2nd approval then completes the merge now that there are 2 approvals on the merge. If you happen to be on both, you can approve #1, approve #2 and then merge pretty much all at once. But either way it gets done once 2 approvals are registered.
answered Mar 8 by Scott Fulkerson G2G6 Pilot (308,890 points)
Hi Scott, the normal merge process does not apply where privacy locked profiles are involved.
Thanks perhaps Louis you can explain and provide a link to show what should happen.   As I have yet to find the evidence to support the suggestion of a PM having to go on the trusted list first before approving the merge.

Yes both PM need to approve but if they both approve does the merge still not go ahead?
I first read about it on G2G. Problem is I have been looking for that conversation which was a very short one and probably marked completed. I have merges outstanding for several months now because one/both of the profiles is/are privacy locked.

The fastest and only solution is to get on the trusted list of both profiles..

Example https://www.wikitree.com/wiki/Hyman-324
Thanks for looking

Have you thought of going down the Unresponsive manager route to get profiles opened?
I would prefer not to discuss that in open forum.
+1 vote

I found a note I made about the new merge system

Due to privacy, we cannot open up editing on these merges, so they can no longer be default completed


answered Mar 9 by Louis Heyman G2G6 Mach 2 (27,600 points)
edited Mar 9 by Louis Heyman

According to the changes log of Hyman-98 you proposed the merge of Hyman-328 and Heyman-98 on 13 Aug 2017. Heyman-98 was merged into Hyman-324 on 18 Dec 2017. That is why the pending merge of Hyman-328 and Hyman-324 shows a "Last updated" date of 2017-12-18.

The reason you are not having the default approval for that merge is not the privacy level, the reason is that the merge originally proposed was to a merged-away ID. You need to re-propose the merge (Hyman-328 into Hyman-324) and wait for the default approval.

Thamks Ruben

I did not propose a string merge, but I'll cancel and do the merge again

The profile LNAB is supposed to be Heyman, The other manager must have swapped the proposed merge around. Great stuff

I even wrote a message so that it would be done right. 

On 15 Dec 2017 at 06:36 GMT Louis Heyman wrote:

Hyman-324 and Heyman-98 appear to represent the same person because: Obvious duplicate Heyman-98 has the correct LNAB according to the baptism which is currently on Hyman-328 also to be merged


Louis, there is a way you can shorten the waiting period. Please see the answer by Robin Lee to this post:


Related questions

+9 votes
2 answers
117 views asked Nov 10, 2015 in WikiTree Tech by Julie Ricketts G2G6 Pilot (232,210 points)
+12 votes
1 answer
+5 votes
1 answer
121 views asked Jun 14, 2015 in Policy and Style by Peter Roberts G2G6 Pilot (369,680 points)
+21 votes
1 answer
139 views asked Jun 4, 2015 in WikiTree Tech by S Willson G2G6 Mach 8 (83,250 points)
+6 votes
2 answers
+7 votes
1 answer
263 views asked Feb 16, 2014 in WikiTree Tech by anonymous G2G6 Mach 2 (20,000 points)
+4 votes
2 answers
97 views asked Oct 3, 2015 in Policy and Style by S Willson G2G6 Mach 8 (83,250 points)

WikiTree  ~  About  ~  Help Help  ~  Search Person Search  ~  Surname:

disclaimer - terms - copyright