Talk:Local Unit Messaging

Email addresses

  • The email addresses for ward leadership groups are pretty long? I wonder if we can shorten them (e.g. for the elders quorum). --Kimsiever 15:36, 21 May 2009 (UTC)
  • Could addresses for youth groups be considered as well? priests(1,2...), teachers(1,2...), deacons(1,2...), laurels@, miamaids@, beehives@. Maybe another phase could allow Church-based Scouting units. troop@, scoutmaster@, scoutingcommittee@ --Greenwoodkl 00:01, 29 Jun 2009 (MDT) (GMT -06:00)
  • Just a suggestion, in some colleges Wards (ie BYU) there are several Elder Quorums and Relief Societies. I am not sure if this is being addressed elsewhere but there should be a way to separate the two quorums when sending messages. Chaseneb 22:54, 11 October 2010 (UTC)

Access Table for Messaging?

Who has access to the "Send a Message" tool on the Leader Resources website? Is it possible to grant access to certain people (or callings)? In our ward, we assumed it would be all Ward Council members, but it appears that this is not the default. Currently, our ward executive secretary is asked to send out emails on behalf of other ward leaders, and he'd like to delegate this to members of the Ward Council. We're mindful of spam, but we're trying to figure out who is capable of doing what under the current system.

Today I noticed that the Access Table has been updated; I'm glad to see improvements in this feature. Will you please add an entry for who has access to send email from the "Messaging" tool, along with all the roles that have access to this tool?

A more general question: Where can I subscribe to receive updates on Messaging development? Obviously, I can subscribe to this Page in the wiki; but is there an "announce-only" email list to which I could subscribe? Could I get read-only access to the JIRA account for this project? Thank you. --Jcarroll 01:58, 16 June 2011 (UTC)

This page was last modified on 15 June 2011, at 19:58.

Note: Content found in this wiki may not always reflect official Church information. See Terms of Use.