Page 1 of 1

Default users home ward

Posted: Thu Oct 03, 2013 4:15 pm
by alz1
In 2.2.1, the default ward seems to be the boundaries in which a user lives, or what is typically their home ward. Although this behavior makes sense for most users, it is preferred that tools opens to our calling specific situation. For example, a stake user would open to the stake. A YSA user would open to their assigned YSA ward. This thought process is based on why a user is accessing tools 80% of the time. It is for their calling.

Secondarily, when a LDS.org users logs in they are presented with their tools based on their calling.

Re: Default users home ward

Posted: Thu Oct 03, 2013 6:30 pm
by russellhltn
I would expect that the default ward is the one in which the member's membership record resides.

The idea of defaulting to an out-of-unit ward isn't a bad one, but how would it determine who is a "stake user"?

Maybe the best idea is to default to what was last used.

Re: Default users home ward

Posted: Mon Jul 11, 2016 8:54 am
by jefferyshoeshine
I agree with the last accessed idea. It would be better if it didn't default to ward for stake calling users.

Re: Default users home ward

Posted: Mon Jul 18, 2016 4:03 pm
by sbradshaw
This is good feedback – I'd suggest sending in-app feedback under settings, to make sure it gets to the developers. Members with stake callings and out-of-unit leaders are good use cases.