TOPIC:

Member in question belongs to two clubs, and uses the same email address login & Password on both club's websites.
After I changed her Name info to include her new TI rank (from ACB to ACS) using Member Management option, she couldn't log into our club's site but could log into her other club's website (whose admin hadn't changed her Profile); after I change it back on our website she could log in (and perform her VPE duties). (She's our only dual member, and officer in both clubs (VPE in our 1645 club, Pres in her "home" 8623 club). Have other club's Administrators run into the same problem and handled if differently?

It had never occurred to me that a Dual Member's FTH Profile could be common over multiple club websites. How should Administrators in multiple clubs change a 'shared' dual member's User Profile? I'll email the 8623 webmaster to see how our two clubs can coordinate changing her Profile.

It should not matter. The code only looks for email duplication within a single club.

I personally know of other Toastmasters who've done exactly the same thing (same email and password on multiple sites) and it's never caused a problem.

Please have the member

1) Click the reload at the bottom of your home page
2) clear their cookies for Toastmastersclubs.org
3) verify their cookie setting to this documentation.
support.toastmastersclubs.org/doc/item/cookie-settings

I had changed her Profile two times, this week the day before she tried to log in today; also last week, when she pointed it out. Starting FTH in a new browser tab does or does not reload FTH or clear cookies?

To be clear, Brian, ...... I can change her Profile (TI award), and before trying to log in she must:
1) Clicks the reload at the bottom of your home page
2) clear their cookies for Toastmastersclubs.org
3) verify their cookie setting to this documentation.
Then she will be able to access our club website with ACS, and maybe the other club's website as ACB?

Do we eventually have to clear up both websites separately?. (Or will my change affect all her Profiles on all websites sharing the same login email and password? Unlikely but I had to clarify)
I'll forward Brian's instructions to her along with all other comments, and we'll try to get together Tuesday to resolve it since I don't want to interfere with her not being able to log in to print agendas Monday. (So far my email to the 8623 webmaster has not been answered.)

Nothing you did caused this issue.

Stale cookies do happen.

Ok, some specifics...

1. As noted, the system only looks for email duplicates within a single club. This actually allows for members to be part of multiple clubs without any issue, since the same email address can be used for each.

2. However, even given #1 above, the profiles for the two clubs are treated independently, as if they are two different people with the same email address. This is sometimes mentioned as a flaw with the FTH db design... there are pros and cons with the single profile for multiple clubs approach also. What I have done to bridge the "gap" is allow members to enter their TI member number in their profile, which should be the same regardless of number of clubs you are a member of. This will allow me to (hopefully) do some cool stuff in the future like produce consolidated role reports that cover all clubs someone is a member of. I could also potentially use the TI # to do a sync of profile information in the future.

3. As long as you do not create a new member record in Membership Management for someone, everything should be fine. So, if you delete an existing member record and recreate it, the system will think it is a different person, because the system does not track people by name... it uses an internal tracking number for everyone. Therefore, you should always strive to avoid creating a new member record for someone (avoid deleting them also... make them former members instead)... if you delete someone, their role history will be lost even if you recreate their Membership Management record.

4. If someone cannot log in, just have them re-authenticate... log in without a password. That is easy and built into the system.