Skip to main content
The Super Admin Dashboard is for authorized TheFaithApp platform operators. It is separate from a church administrator’s dashboard and permissions.

Sign In and Choose a Workspace

  1. Open the platform operator sign-in page.
  2. Enter the email registered for your operator account.
  3. Open the private sign-in link sent to that address before it expires.
  4. Choose Client Onboarding, Users, Bible Packs, Admins, App Users, Feedback, or Listmonk from the dashboard menu.
A church administrator account alone does not grant platform access. Do not forward a sign-in link or use someone else’s operator identity. If the verification page asks you to reopen your original email, open the link from that email. To request a fresh link, select Back to administrator sign-in and enter your operator email again.

Review Church Onboarding

Open Client Onboarding to qualify requests, record internal notes, prepare an invitation, or review activation progress. An invitation is an explicit message to the approved contact, not an automatic result of reviewing a request. Follow Client onboarding for the request, invitation, revocation, and activation workflow.

Find and Support a Staff User

  1. Open Users and search by name, email, or church.
  2. Use All Churches to choose a church. You can also filter administrator status and email verification. If church choices fail to load, use Try again beside that filter.
  3. Select Church Summary on a user with a church to review its Overview, Content, People, Marketing, Engagement, and Analytics summaries.
  4. Use Export CSV only for the records needed for the support task. The export follows the current search and filters.
AI Email prepares a draft for the selected church. Review the generated subject and body before copying them. Generating or copying a draft does not send an email.

Impersonation

Use Impersonate only for an authorized support task. The church workspace opens with the selected staff user’s permissions. Any action you take there can change that church’s real records. Use the impersonation banner’s return control to leave the staff session and return to your operator identity. Do not leave an impersonated session open when your support work is finished.

Manage Platform Operator Access

The Admins workspace controls who may use platform operator sign-in. It is not the church’s staff-and-roles screen.
  1. Open Admins and search for the person before adding another entry.
  2. Add their name and correct email, or edit an existing entry.
  3. Remove access when it is no longer authorized.
Saving an entry does not send a sign-in link automatically. At least one operator must remain. Church staff access is managed separately under Church Management → Admins.

Review App Users and Feedback

App Users is a searchable list of member accounts, their church, login type, and available login dates. Export CSV follows its current search. This is an operator support view, separate from a church’s member directory. In Feedback:
  1. Search by message, member, or church.
  2. Open a feedback row by pointer or keyboard.
  3. Review the message, rating, submission time, member snapshot, and available app/device context in the detail drawer.
  4. Close the drawer to return to the results.
The current Feedback screen is for reading submissions. It does not offer a reply, status-edit, or message-send action. Feedback can contain private support context; keep it within the people handling that case.

Build a Bible Pack

Use Bible Packs to turn a licensed source into a downloadable reading pack. Raw JSON is an import source; members download the built pack.
  1. Choose a .json or .txt source containing a JSON array of verse rows. Each row needs a supported book name, chapter, verse, and content. Empty sources cannot produce a pack.
  2. Review the inferred metadata after choosing the file. Enter Version ID, Language code, Display name, Abbreviation, and Content revision. Choosing another file updates untouched suggestions and keeps fields you have edited. Use Reset Form to clear the source and start with fresh metadata.
  3. Enter the license details and minimum supported app version when needed. Choose Text direction. Publish only content you have permission to distribute.
  4. Usually leave Optional pack ID override empty. Version ID, language code, content revision, and an override must start with a letter or number and contain only letters, numbers, dots, hyphens, or underscores. Use a distinct pack ID for each revision you want to retain for rollback.
  5. Select Upload And Start Build. Wait for the background build to finish; uploading the file alone does not make it available to members.
  6. Review the build status, verse count, and preview sample. If the build fails, correct the source or metadata before starting another build. A failed build is not a published revision.
  7. Use Refresh Packs when you need the latest library state.

Publish and Manage Revisions

  • Publish makes a built pack available for app download. Publishing another pack for the same version and language deactivates the previous published pack.
  • Unpublish returns a published pack to Draft.
  • Download opens a short-lived download link for the built pack. A link that has expired needs to be generated again.
  • Rollback lets you select another retained pack from the same version and language. Review the target, then choose Confirm Rollback.
  • Deactivate removes a pack from the public catalog while keeping its history. Confirm the intended pack before proceeding.
  • Delete is available only for a deactivated pack and permanently removes that pack and its downloadable artifact. Keep any revision needed for rollback.
These are platform-wide reading resources, rather than one church’s content library. Review metadata, rights, and the preview before publishing.

Configure the Platform Mailing Connection

Listmonk is a platform mailing integration. It is separate from a church’s Marketing provider settings.
  1. Enter the Server URL, API Username, and API Token for the approved server, then select Save Connection.
  2. Select Test Connection. If it fails, correct the connection and test it again before syncing.
  3. Under Users or App Users, enter a list name and select Create & Map, or enter an existing list ID and select Map ID.
  4. Confirm the intended audience and list before selecting that audience’s Sync. Sync All includes both audiences.
  5. Review the sync state and processed, synced, skipped, failed, and pending counts. A queued sync is still waiting for background processing; it is not confirmation that every record reached the mailing server.
The token is masked after saving. Leaving the saved mask in place preserves it; enter a new token only when intentionally replacing the connection. Sync preserves an existing subscriber’s disabled or blocklisted status and existing list subscription choices. It does not reactivate a person who opted out. If the mailing server cannot confirm whether the subscriber exists, that record fails safely rather than being treated as a new subscriber. Users sync includes verified staff email accounts. App Users sync includes member records with usable email addresses. Syncing creates or updates mailing list records; it does not send a campaign or establish a person’s marketing consent. Review the audience and the platform’s communication policy before using these lists for messages.

Review Jobs and Operate the Service

Choose Review Jobs employers, vacancies and reports from the dashboard.
  • In Employers, review the organization and posting authority, select a decision, and record a meaningful reason.
  • In Vacancies, compare the submitted revision with any published revision. Approval does not publish a role automatically. Suspension removes a role from public availability; reinstatement leaves it closed until the employer confirms and renews it.
  • In Reports, review the concern and record the resolution reason. Reload after a conflict so a decision uses the current record.
  • Open Jobs operations and privacy support for service health, targeted recovery requests, and documented retention holds. A recovery queued for a background service is not proof that the external action completed.
  • Jobs merchant support and Sensitive hiring support require their separate named authorization. General platform access does not grant them.
  • Social roundups prepares reviewed role summaries and downloadable share material. Downloading or recording a publication URL does not publish to a social network for you.
Follow Church and ministry jobs for the complete moderation, support, rollout, and publication boundaries. Candidate and employer marketplace workspaces are separate from the church dashboard.