> ## Documentation Index
> Fetch the complete documentation index at: https://docs.thefaithapp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Steadier dashboard workflows

> Keep drafts safe, manage campaign delivery, protect staff access, and recover interrupted work.

## Keep your work in the right account

Form responses and saved views follow your church and staff account. Switching
accounts or opening another response clears unfinished response notes so
another record does not inherit them.
Event and staff editors ignore older requests when you open a different record.
An in-progress save keeps the editor open, and a failed save preserves your entries.

## Send campaigns with clearer feedback

Email **Send Now** queues the campaign for sending. Audience totals refresh
with your selection, and a failed queue request can be retried using the saved
draft. Retrying checks whether that campaign is already sending or sent before
queueing it again. A queued confirmation describes the sending request; it does
not confirm delivery to every recipient.

Open an email campaign to view its saved content and delivery status, or edit a
draft without choosing a new template. Scheduled emails can be cancelled before
sending begins. Retrying a failed email or SMS campaign refreshes its totals and
skips recipients already marked as sent. Interrupted workers cannot restart a
cancelled campaign or consume work belonging to a newer send attempt.

SMS summaries say **Accepted by provider** and show the **Provider acceptance
rate**, distinguishing sending requests from delivery to a phone.

## Work confidently with people and groups

Members tabs keep their place in the page address, so shared links and browser
history return to the selected workspace. **Edit group** opens the group you
selected, and meeting days and times display clearly. Existing attendance marks
and notes stay in place when you save attendance or publish another group update.

Staff permissions apply consistently to Communications, SMS inboxes and church
campaign management. Text-to-join setup explains when a keyword is already in
use. Volunteer signups accept only time slots belonging to that opportunity.

## See clearer results

Default analytics metrics for members and events save successfully. Failed
Fapshi campaign payments show a clear unsuccessful result and a way to retry.
Event calendars, upcoming lists, and details show the church timezone
consistently, including events at a calendar range boundary. Public church
images can display from church-managed image hosts without interrupting the page.
Finance tables and statement histories show each currency with its correct
decimal places. Cancelling a PayPal recurring gift waits for provider
confirmation, so an interrupted response can be retried safely.
Bulletin actions, fund controls, and named dialogs work with assistive
technology and keyboard navigation.

## Recover interrupted work

Outreach campaign details open their existing editor directly and refresh after
saving. Campaign and donor-field editors keep older requests and unfinished
work with the selected record, offer load retry, and prevent overlapping saves.
Donor Select and Radio fields support one choice per line while attached forms
stay locked. Empty received-cash totals show clear wording instead of a blank
amount, and campaign, item and form actions have keyboard-accessible names.

Operations, Governance, and pastoral care workspaces offer **Try again** when
their initial information cannot load. Governance resource drafts stay in place
after a failed save. Outreach donation lists return to an available page when
the previous last page disappears.

## Continue pathway editing safely

Changes made while a pathway is saving remain visible and marked as unsaved.
Pathway and learner lists recover when actions empty their current page.
New fast dates keep their intended length across time zones.

## Use clearer controls

Password visibility controls have clear names and work with a keyboard.
Sign-in explains how long to wait after too many attempts. Password recovery
explains the reset link, and profile email changes return you to verification.
Saving a profile photo preserves other unfinished profile edits. Public church menus
show a clear menu button on phones, and the form builder keeps its action bar
below the dashboard header while scrolling.
Video dialogs respond to Escape and backdrop dismissal. Livestream previews
accept YouTube URLs, use an HLS player with captions, and explain when an RTMP
stream needs its provider's player. Preview media closes with the dialog.
Manual slide reorder controls have descriptive names.
Product groups and event actions work with a keyboard, and form fields expose
their visible labels and validation messages to assistive technology.

## Read form responses clearly

Choice answers show the label from the version the person submitted, even if
you rename that option later. The response inbox and detail drawer use the same
readable wording on desktop and phone screens. Needs and Offers moderation
labels the decision note and explains which decisions require it. Hiring
reviews show application requirements and screening choices, with clear salary
wording when only a minimum is available.

See the [Marketing guide](https://docs.thefaithapp.com/product/marketing.md),
[Admin, Data and Governance guide](https://docs.thefaithapp.com/product/admin-data-governance.md), and
[Discipleship guide](https://docs.thefaithapp.com/product/discipleship.md) for the current workflows.

## Keep community work consistent

Chat follows current church, role, and channel access. Private invitations do
not expose conversations before acceptance, bans stay in place when someone
tries to leave, and revoked readers lose live updates while retained readers
remain connected.

Visitor contact restrictions stay visible across the record's tabs. Archived
Bible reading plans can be published again without discarding enrollment
progress. Gathering edits reject an end time before the start, and operational
event cards show the church's intended time. Prayer summaries distinguish
withdrawn and answered requests and describe their selected audience clearly.

## Continue everyday work reliably

Formation and care workspaces recover from interrupted loading, resolved care
requests show their saved outcome, and network views keep the selected church's
work together. Export failures explain how to try again. Ministry schedules
reject reversed times, volunteer instructions retain custom serving times, and
family sessions stay open until every child has been checked out.

Uploaded devotional and campaign images display reliably. Rendered clips open
correctly, and common M3U8 stream previews play without activating a broadcast.
Keyboard navigation reaches streaming, settings, profile and conversation
controls, while session forms keep validation messages visible.

Removing a profile photo persists after reloading, upload failures preserve
unfinished edits, and staff role changes take effect. Mailing-list synchronization
preserves existing opt-outs. Platform operators can filter users by church and
follow the [operator tools guide](https://docs.thefaithapp.com/product/platform-operator-tools.md) for Bible
packs, feedback and other internal workspaces.

Bible imports preserve metadata you have already edited when choosing a source
file. Participation rates compare the same connected groups, and empty analytics
views wait for observations before offering retention or upgrade guidance.

Campaign greetings use imported subscribers' saved names when available. Email
totals are labelled **Accepted by provider**, and duplicating an SMS campaign
keeps you on the campaign list. Wide drawers fit within smaller browser windows.

Notification edits offer **Try again** after a loading failure and retain
unfinished messages after a failed save. Care plans keep local scheduling times,
closed cases show read-only plans, and rejected preaching-history imports retain
their rows. Assistant conversation controls have accessible names. Role editors
show all available permissions, and category and role edits stay with the
selected record while loading or saving.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.