Member Web is where members read the current bulletin and church information, contribute approved photos and videos, and—when authorized—update app announcements and event pages. This guide covers browser-based Member Web and WordPress operations only.
Start here: Open the Member Web Home. Obtain access details and administrator credentials privately from the Church; never add them to this public guide.
Separate app procedures: Sending from iPhone, creating an order setup, and managing media in the app are in the App Administrator Guide. This page is only for Member Web and its WordPress administration screens.
1. Entry points and roles
Goal
Entry point
Required access
Read the bulletin, announcements, and church updates
Member Web access, the media-contribution session, and Davar App User/Operator/Administrator accounts are separate systems. Unlocking one does not automatically grant another.
2. Use Member Home
Open Member Home and use the access method provided by the Church.
Use View Bulletin near the top for the current weekly bulletin. You can view it on the page, choose Read as Text, or open the PDF.
Scroll through the entire page to review Announcements, scenes from Los Angeles headquarters, Faith Life, social/video channels, branch and worship-location updates, and Website Updates.
Tap an article, photo, or video card to open its source. If it opens another site, use the browser Back control to return.
If content appears old, reload the page. If it still does not update, report the bulletin date and exact section name to an administrator.
Weekly updates: Normal bulletin, summary, and video updates arrive through the approved weekly workflow. Do not edit Member Home merely to make a date look current. If part of a week is missing, report the week and section instead of publishing duplicates.
Two kinds of announcements: Announcements shown on Member Home are member-page content selected from sources such as the bulletin. They are separate from App Announcements published to the Davar App Inbox.
3. Contribute photos and videos
Choose Upload Photos & Videos on Member Home or open the contribution page.
Enter the separate contribution password and choose Authenticate. Confirm that you have permission to share every selected item and consent to immediate Church publication and use.
Under Choose from Device, select multiple JPEG, PNG, WebP, HEIC, HEIF, MP4, or MOV files. The limit is 10 GiB per file. Keep the page open until processing completes.
Under Import from Cloud Share URL, paste one public iCloud Photos, iCloud Shared Album, Amazon Photos, OneDrive, or Dropbox share URL and choose Review Contents.
Review the discovered items, select only what is needed, then choose Import Selected Files and Publish. A link that requires sign-in or a password cannot be used.
Review Uploads in This Session. Use Refresh when needed and verify that each intended item is Public.
When iPhone keeps only a smaller copy
After storage optimization, device selection may provide a reduced copy. If the original remains in cloud storage, use a public share URL that allows the original to be downloaded.
When part of a job fails
Check the connection and link expiration, then retry only failed items. Do not start another URL over an active cloud job; finish or cancel the current job first.
Publication
The current web contribution flow publishes completed items immediately. Before selecting media, confirm rights and consent, especially for children, name badges, addresses, documents, prayer, or private conversations.
Notification timing
Items publish as they complete. One summary notification is sent 30 minutes after the last new contribution. Do not submit the same item repeatedly.
4. Create an app announcement
This WordPress operation is Administrator-only. Publishing the Inbox item and sending a push are two separate actions.
In WordPress administration, open App Announcements → Add App Announcement.
Enter the Japanese title in the standard title field and the English title in English title.
Enter short, push-safe text in Japanese summary and English summary. Never include names, counseling, prayer requests, order details, passwords, or other private information.
Only when needed, enter Japanese HTTPS URL and English HTTPS URL. Only approved HTTPS hosts are accepted.
For a time-limited item, enter Expires at as UTC ISO-8601, for example 2026-12-31T23:59:59Z. Expired items stop being delivered to the Inbox.
Only when a device alert is appropriate, enable Eligible for a separately confirmed APNs send. Then choose Publish first.
In Davar App, open Announcements → Church Announcements and verify both languages, the expiration, and links. Publishing alone does not send a push.
After verification, return to the App Announcements list and choose Send app notification once for that row. Read the sent/failed result and do not casually resend the same alert.
A push cannot be recalled. Verify the complete Inbox item first, then use the separate send action only when an alert is necessary. Apple TV reads the Inbox but does not register for phone-style push notifications.
5. Create an event page with App Pages
App Pages is an Administrator-only, non-public editor for adding timely event information without waiting for an app release. The app renders the published page from a constrained data format.
In WordPress administration, open App Pages → Add App Page.
Enter Japanese in the standard title and content fields. Line-based authoring supports # heading, > callout, - list, ---, and [label](https://…). Other markup becomes plain text.
Enter English title and English content. Japanese and English must use the same block types and order: headings, paragraphs, lists, dividers, and links.
Enter Menu group (Japanese / English). Every page in one event must use exactly the same Japanese and English group names.
Choose an Icon and enter Menu order. Smaller numbers appear first.
Enable Show in app menu. Save as a draft, recheck both languages, and then choose Publish.
Current app versions treat Member Web App Pages as timely event content and group them under Events. Do not use App Pages as a replacement for stable core features or permanent navigation.
Link and capability limits: Links must use HTTPS on port 443 and an approved Davar-related host. Arbitrary JavaScript, HTML, PHP, embeds, and remote code are not delivered. A new interface, permission, or capability still requires an app update.
6. App Navigation and Events
Settings → App Navigation is an advanced editor for the complete menu shown below Settings. A mistake can affect many menu items, so adding an App Page normally does not require changing this JSON.
Field
Meaning
presentation
group creates an expandable group; leaf opens one destination directly.
destination.type
builtin opens a shipped app screen, page opens a published App Page, and web opens an approved HTTPS page.
id
Use a unique ASCII identifier for every group and item. Do not casually change a published ID.
title.ja / title.en
The Japanese and English labels. Supply both.
placement
event places a timely event group in the Events area before permanent menus.
order
Smaller numbers appear first. Preserve the policy of Events first and permanent information below.
Before editing, copy the entire JSON textarea into a safe working note so it can be restored. Do not include passwords or secrets.
Preserve existing IDs, bilingual labels, item counts, and destinations. Change only the smallest necessary section.
Set "placement": "event" on event groups. This applies to 2026JBS, 2026SBS, and App Pages added through Member Web.
For a page destination, publish the App Page first and use its actual delivered page ID. A missing or draft page is rejected.
A builtin destination must already exist in the app allow-list. Do not guess a new name.
Choose Save App Navigation and read any error. Malformed JSON, duplicate IDs, missing pages, unapproved URLs, or unknown built-ins reject the complete replacement and preserve the last known-good menu.
Content policy: Only stable, low-change core features are hard-coded in the app. Member Web App Pages are timely event menus and belong under Events. 2026JBS and 2026SBS follow the same event placement.
7. Verify after publishing
Japanese and English titles, body, links, ordering, and expiration carry the same meaning.
Pull down to refresh Davar App Home, close the menu, and reopen it.
The App Page appears in the intended Events group and order, without duplication in permanent navigation.
The App Announcement was checked in the Inbox before push, and the sent/failed result was reviewed.
Refresh Uploads in This Session and verify that only intended media became Public.
Verify the result as a normal member and normal app user, not only from the administrator screen.
8. Troubleshooting
An App Page does not appear
Confirm it is Published, Show in app menu is enabled, and both languages use the same block types in the same order. Refresh Home and reopen the app menu.
Navigation is not adopted
Read the App Navigation save error. Check JSON syntax, duplicate IDs, page IDs, HTTPS URLs, and built-in names against the previous copy.
A push did not arrive
Confirm that Publish and push send were both completed, the push-eligible checkbox was enabled, sent/failed counts were read, and the device enabled Administrator Announcements and iOS notifications.
A cloud import does not progress
Confirm the URL is public, unexpired, requires no sign-in, and permits original downloads. Refresh the current job or cancel it before retrying with a new link.