Alan_Brown wrote:Actually, the way I read the quote is the way it actually works -- everyone in the ward should be associated with a record number, but the Stake Administrator is not.
Two notes. We were not sharing a stake login. We were using individual logins, so we would know who was actually doing the work if there was a problem. I guess the new procedure is that there will be a Stake Administrator login and several folks will need to know that password and share it.
The other challenge we will have is with the unit that has NO membership records for those who use MLS. This is a correctional unit. All of the records are for incarcerated members. All of the leaders come from other units in the stake, and their membership records remain in their home wards.
With MLS 2.9, it appears that we will now be in the position of having one login for the leadership of the unit, which will have to also be the Stake Administrator login, since there is not way to associate a leader's login with a membership in MLS.
Is there an alternative that the Urgent Task to link the logins with membership records may just be ignored? I would in principle discourage such an action, but I am not sure the alternative is any better for this particular unit.
I understand the desire and need for security, but the issue does arise (once again) that a new idea was not thoroughly vetted in the real world. I will post separately on the other two issues that have arisen.