Member
Edited 1 time, last by chriswoodut on
There seems to be changes on who can grant someone a calling. I swear two weeks ago I had the ability to give someone the calling of 'clerk'. I needed to change the brother's calling from finance clerk to ward assistant clerk to get the right LCR rights for his calling. (Actually, I need him to have access to both.) The system would not let me assign him the calling. I'm a ward clerk. I then released him as a finance clerk hoping it would then allow me to assign it. Nope, now he has no clerk calling.
I asked the stake clerk to fix it. He says he can't assign the calling because the system is prompting for 2 logins to assign an assistant ward clerk a calling! This latest push to make everything double logins to change anything is making things really hard and I'm not sure that it is really making things more secure.
I'm seeing these things now require 2 person authentications to get done:
1. Finance approvals (batch, checks). This makes sense to me.
2. Granting someone a clerk calling. This seems new. Not even a stake clerk can do it. What's hard is that it requires two people to be in the same place/same computer at the same time to do it. We can't both be remote from each other. The real kicker is forcing the two to be in the same room. If people are traveling, it is hard. We now allow financial reimbursements to be done remotely and separately, it would be nice if this was as well.
3. If someone wants to change their password on MLS, two logins are required. Plus, they have added password expiration. We got in a jam where a password expired and it was discovered in the middle of a tithing batch and couldn't complete the batch without another person driving to the church to authenticate the batch. (Note that recent studies have proven password expiration does not increase security. The church is really late to implementing it and now companies such as Microsoft have declared the theory dead.) On the other hand, the church has made two factor authentication available on LCR which is cool.
4. Have you guys seen other changes?
(Usually when I see people post here there are two unhelpful responses, so don't bother with those. The two are; you should trust the church is doing the right thing and don't ask questions, and the second is that nobody from the church IT departments read these forums so don't post here because it's not helpful.)
I asked the stake clerk to fix it. He says he can't assign the calling because the system is prompting for 2 logins to assign an assistant ward clerk a calling! This latest push to make everything double logins to change anything is making things really hard and I'm not sure that it is really making things more secure.
I'm seeing these things now require 2 person authentications to get done:
1. Finance approvals (batch, checks). This makes sense to me.
2. Granting someone a clerk calling. This seems new. Not even a stake clerk can do it. What's hard is that it requires two people to be in the same place/same computer at the same time to do it. We can't both be remote from each other. The real kicker is forcing the two to be in the same room. If people are traveling, it is hard. We now allow financial reimbursements to be done remotely and separately, it would be nice if this was as well.
3. If someone wants to change their password on MLS, two logins are required. Plus, they have added password expiration. We got in a jam where a password expired and it was discovered in the middle of a tithing batch and couldn't complete the batch without another person driving to the church to authenticate the batch. (Note that recent studies have proven password expiration does not increase security. The church is really late to implementing it and now companies such as Microsoft have declared the theory dead.) On the other hand, the church has made two factor authentication available on LCR which is cool.
4. Have you guys seen other changes?
(Usually when I see people post here there are two unhelpful responses, so don't bother with those. The two are; you should trust the church is doing the right thing and don't ask questions, and the second is that nobody from the church IT departments read these forums so don't post here because it's not helpful.)