A few days ago, someone simply showed up as a member of one of my projects, despite the fact that I require a join authorization. This person clearly should not belong, so I went to his Contact page to get his email address. There was none, so I simply removed him from the project. Today, I got a join request, and despite being told email addresses would now appear in them, there was no email address, and I had to go through the form on my GAP to respond. Oddly, when I got to the table of Join Requests, there was a Kit # for person, namely, "DEMO-2." While doing that, I noticed that there was an unread join request from back on December 29th. I never got an email alerting my to the request, so now it appears on my GAP that I was derelict in responding promptly. I guess, from now on, I'm going to have to check the GAPs for all six of my projects every day or run the risk of overlooking a join request. Is anyone else experiencing problems with join requests? I thought this was resolved when they told us the join request email notification would include the email address of the requestor. Diana

Diana, I have been having the same experience. The Join Requests were going to the Asst-Admin, but not to me. We removed him from the project. He was still getting the messages, I was not. I sent in another feedback a couple of days ago, and today I got a Join Request for a new subscriber. Since you are apparently getting the JRs, you have to scroll down almost to the bottom of the message for the e-mail address of the potential subscriber. It appears on a line by itself, close to the bottom of the message, with no information as to what it is. Marleen Van Horne

Hi Marlene, I guess, in a way, it's comforting to know I'm not the only one having problems... I went back and double-checked. The request email came from FTDNA, and it was addressed to me. Those were the only email addresses anywhere in the message. I had no choice but to respond through my GAP. It just occurred to me there is a better solution if FTDNA wants to be certain they aren't losing sales (i.e., if they don't trust us). Reduce all their prices to Group prices and just let people buy a kit, on their own volition. In the email acknowledging their purchase, give them a link to a page of surname projects, and *then* let them apply to join a project. FTDNA regains total control of the sales process, and the project admin still gets to filter new members. The down side is that the leverage we admins have (i.e., the discounted price) to get them to join a project disappears. On the other hand, I think it's worth it to get rid of the current situation. They could, when the kit is purchased, check the test subject's surname against the surnames listed in the project profile database, and send emails to both the admins and the customer as to what projects it would be appropriate to join, so it wouldn't require any additional staff costs for them. Diana > -----Original Message----- > From: y-dna-projects-bounces@rootsweb.com [mailto:y-dna-projects- > bounces@rootsweb.com] On Behalf Of Marleen Van Horne > Sent: Thursday, January 06, 2011 11:26 PM > To: y-dna-projects@rootsweb.com > Subject: Re: [Y-DNA-projects] flakey join authorizations again > > Diana, > > I have been having the same experience. The Join Requests were going to the Asst- > Admin, but not to me. We removed him from the project. He was still getting the > messages, I was not. > > I sent in another feedback a couple of days ago, and today I got a Join Request for a new > subscriber. Since you are apparently getting the JRs, you have to scroll down almost to > the bottom of the message for the e-mail address of the potential subscriber. It appears > on a line by itself, close to the bottom of the message, with no information as to what it > is. > > Marleen Van Horne