Hello SJ, thanks for your speedy follow-up. If your advice here summarizes the current policy-driven workflow for how project Leaders need to personally execute merges like this, then might I suggest whoever wrote (or now owns) the boilerplate instructions provided by the website to post here to G2G update the blurb to include that detail?
Broadly speaking, I am just trying to do what the website tells me to do in this case. (Approving a merge I lack the authority to approve, for a profile I "manage" but am prevented by policy from editing or administering.) If the instructions I am following are currently inadequate, we can avoid future G2G posts going to the wrong ppl if we update the instructions / post template.
By extension, we could also avoid this entire class of technical gremlins if somebody with access to the database dumps a report listing all the Pre 1500 profiles currently managed by non-Pre 1500 WikiTree members (and perhaps the orphans which create the backdoor to this situation, as anyone can adopt an oprhan even if they can't edit it or approve merges). It is presumably a large but finite list, and might be helpful to queue into medieval project todo lists.
Thoughts?
