Skip to main content

Prayer Community

Prayer Community gives members a shared church prayer feed inside the mobile app. It turns prayer requests into a simple community rhythm: someone submits a need, the church reviews and approves it, members pray, and the requester can later mark the request answered with a testimony. This feature is church-scoped in the current release. Members see approved prayer requests from their own church, not a public global prayer wall.

Where Members Find It

Members open Prayer Community from the Connect page by tapping Prayer community. From there, they can browse approved requests, submit a new request, mark that they prayed, and return to their own requests for follow-up.

What Members Can Do

  • Submit a new prayer request from the mobile app.
  • Choose whether the request should appear anonymously.
  • View approved requests shared by their church.
  • Tap I prayed to show support for a request.
  • See how many members have prayed for a request.
  • Review their own submitted requests.
  • Mark their own request as answered.
  • Add optional testimony text when a prayer has been answered.

Submitting a Prayer Request

Members use the Prayer Community submit flow when they want the church to pray with them. Typical steps:
  1. Open Connect.
  2. Tap Prayer community.
  3. Open the submit request action.
  4. Enter the request title and description.
  5. Choose whether to submit anonymously.
  6. Submit the request.
After submission, the request follows the church approval process before it appears in the community feed.

Approval and Moderation

Prayer Community uses the existing prayer request approval flow as the moderation gate. Approved requests appear in the church feed. Pending, rejected, or unreviewed requests stay out of the feed. This helps churches keep sensitive requests, duplicate submissions, or inappropriate content from becoming visible to the wider community. For admins and prayer teams, the practical workflow is:
  1. Review incoming prayer requests.
  2. Approve requests that are appropriate for the church feed.
  3. Leave sensitive or private requests out of the public church feed when needed.
  4. Keep request status up to date so members see the right requests.

Anonymous Requests

Prayer requests can be anonymous. When a request is anonymous, the feed hides the requester identity. This lets members ask for prayer without exposing personal details publicly. Non-anonymous requests can show the member or display name so the church can recognize who is asking. Use anonymous requests for sensitive needs, family situations, personal struggles, or any request where privacy matters.

Praying for Requests

Members can tap I prayed on a request to show they prayed for it. Each member can mark I prayed once per request. The count helps the requester know that the church is standing with them, without requiring every person to leave a comment or message.

My Requests

The member’s own requests are available for follow-up. This area helps request owners see what they submitted, track whether the request is still active, and mark it answered when the situation changes.

Answered Requests and Testimonies

Request owners can mark their own requests as answered. When they mark a request answered, they can add optional testimony text. This gives the church a simple way to celebrate answered prayer without creating a separate testimony workflow. Good testimony text is usually short, specific, and safe to share. Members should avoid including private details about other people unless they have permission.

Current Scope

Prayer Community currently focuses on the core church prayer loop:
  • Member submission
  • Church approval
  • Approved church feed
  • I prayed support
  • Owner follow-up
  • Answered requests
  • Optional testimony text
  • Anonymous display rules
The following community expansion ideas are intentionally left for later phases:
  • Prayer teams
  • Prayer circles
  • Friend or follow networks
  • Volunteer prayer networks
  • Public or global prayer walls
  • Follow-up notifications