cant access the lds.org/leader site

[miketorg]

Just wanted to let u know the reasons for my issue was my Stake has not removed me from my previous calling. Come to think of it i wasn't released from the pulpit either.

[aebrown]

Just wanted to let u know the reasons for my issue was my Stake has not removed me from my previous calling. Come to think of it i wasn't released from the pulpit either.

That's interesting. Theoretically, having another calling with lesser permissions shouldn't cause you to lose access for a calling that should have permissions. For example, at one point I was a financial clerk (which has no access to the LDS.org/leader site) and also an Assistant Stake Clerk (which does have access). The fact that I had a calling with no permissions had no negative effect on the permissions I had because of the calling which did have permissions.

How are you able to make that definitive statement? Did the stake remove you from your previous calling and now you have access? Or did someone tell you that if the stake removes you from that calling, your permissions for your branch leadership calling will suddenly start working?

[jonesrk]

Just wanted to let u know the reasons for my issue was my Stake has not removed me from my previous calling. Come to think of it i wasn't released from the pulpit either.

The problem is that your lds.org headers don't show your new calling. You will need to talk to LUS to get that back in sync.

[scottdwoolsey]

I am having the same problem, but I have not had a previous calling in this Stake. Who is LUS?

[jonesrk]

LUS = Local Unit Support

[Mikerowaved]

I am having the same problem, but I have not had a previous calling in this Stake. Who is LUS?

Welcome to the forum, Scott. Yes, we tend to throw around our share of acronyms and abbreviations. If you ever need to figure out any other terms, there is a Glossary created in the Wiki that lists the more common ones.