Alan_Brown wrote:I certainly agree that it is not a good implementation to send such emails to all the default approvers, and it should be fixed.
However, I wonder how big a deal this really is. You mentioned admin emails, like "Calendar Waiting for Approval." Are there other such messages?
Apparently it was a big enough deal for him to seek me out and discuss it.
A notice goes out each time we add or delete a calendar, and once we get settled, the notices probably will calm down. A notice also goes out when you add or delete an individual as an editor, but that one may just go to that person, and it may have gone to him. During set-up we've approved nine calendars and deleted two, so over the last two weeks a flurry of "admin messages" would have gone to all these individuals, with only one person actually needing them.
Additionally, he may have his calendar notifications (from within the calendar itself) set to notify him by email of new calendars, which may have given him an additional nine emails of new calendars. This he can uncheck, of course, as this is a calendar subscriber preference and not an admin one
Originally Posted by Alan_Brown
Personally, I find it hard to understand why this functionality was added --
Trying to remember...
I think as the directory and the first tools came online, they were tied to just a single calling. I, as ward clerk, was the admin in charge of photo approval for the directory, but only myself. The questions were immediatly raised: Does that mean all ward clerks now must have a computer to be called as a ward clerk, or your ward will not be able to have photos in your directory? What if the bishop wanted the exec secretary to perform those duties? Why tie it to a priesthood calling (Clerk or assistant clerk) when a sister could function as a
website admin equally as well or better and perform as the administrator? What if a bishopric member needed oversight or more administrative control?
As updates and revisions continued, the rights were expanded and the
Website administrator calling was also added as one that had administrative abilities in
tools on lds.org, (and not just over LUWS) but this came after the original implementation of these tools, if I remember.
Once the
website admin was granted this ability, the default approvers no longer needed to recieve admin emails, as
jdlessley correctly states:
An implementation similar to classic calendar which has a designated web administrator the one to receive the e-mail messages would solve this (maybe they are working on it). But instead of only one approver, or default approver, receiving the messages all could have that option to be either active or inactive. Of course there would always have to be at least one active to receive the messages.
I've sent this in as feedback.
