> ## Documentation Index > Fetch the complete documentation index at: https://docs.faithloft.org/llms.txt > Use this file to discover all available pages before exploring further. # Manage prayer requests > Submit a prayer request, choose who can see it, follow it through the prayer team board, and handle consent carefully. Use **Prayer requests** to share a request with the right audience, see who is praying, and coordinate follow-up. Your role and the request's visibility determine what you can see and change. Keep the request and any comments appropriate for the audience selected. ## Before you begin * You can choose from departments you belong to where **Prayer requests** is enabled. If a department is missing, ask your church administrator to check your department membership and module access. * The **Board** is available to prayer team members. Full management actions such as changing visibility, assigning a request, setting its status, and closing it require prayer management access. Requesters and assigned team members also have limited controls on requests they can access, as described below. Ask your church administrator if an action is missing. * The request form records the signed-in account as the requester and has no separate requester field. If you are entering a request received from someone else, follow your church's process for doing that. ## Submit a request 1. Open **Prayer requests**, choose the department from **Department**, and select **New request**. 2. Add an optional **Title (optional)** and enter the request in **Prayer request**. 3. Choose **Visibility**: * **Private**: visible to the requester and department prayer managers. * **Prayer team**: visible to the requester, prayer managers, and members of the department prayer team. * **Church wall**: visible to other church users who can access the prayer feed. 4. Choose whether to turn on **Post anonymously**. Other viewers will see the requester as anonymous. A prayer manager can see the requester's name only when the requester has also allowed contact about the request. 5. Turn on **Allow contact about this request** only if a permitted prayer leader may contact the requester about it. 6. Turn on **Allow a testimony to be shared** only if the requester agrees that an answered testimony may be used to draft a public Share Kit. A draft still needs approval before it is published. 7. Select **Submit request**. The request opens so you can review its status, visibility, comments, and follow-up details. The form defaults to **Private**. The request text can be up to 5,000 characters. Only include details that are suitable for the visibility you selected. ## Find a request in the list Use **List** to review requests in a table. Select a row to open the request. Select **Refresh** to reload the list. Use the filters together: * **Status**: **Open & answered** hides archived requests; choose **Open**, **Answered**, or **Archived** to narrow the list. * **Visibility**: choose **All**, **Private**, **Team**, or **Public**. * **Scope**: **Default** uses your normal access; **Mine** shows your own requests; **Wall** shows public requests; **Team** shows prayer-team requests; **Assigned to me** shows requests assigned to you. Prayer managers also have **Unassigned** and **All**. Archived requests are limited to your own requests unless you have prayer management access. Use the page controls below the table to move through longer lists. ## Respond to a request Open a request from the list to see its full text, status, visibility, requester, prayer count, comments, and history. * Select **Pray for this** to record that you are praying for the request. Select **Prayed** to remove your response. The total appears on the request. * Add a note in the **Comments** box and select **Post comment**. People who can view the request can also read its comments. You can delete your own comment; a prayer manager can delete any comment. * If the request is unassigned and available to you, select **Take follow-up**. After taking it, select **Release follow-up** if the team should take it back. * The requester can select **Edit request** while the request is open. They can update its status between **Open** and **Answered**; an answered request can be reopened if prayer is still needed. ## Coordinate the prayer team on the board Select **Board** to see the prayer pipeline. It is available to department prayer team members; if you are not on the team, ask a department leader to add you. On a computer, the stages appear as columns. On a phone, choose a stage from the stage selector. The stages are **New**, **Triage**, **Assigned**, **Praying**, **Awaiting update**, **Answered**, and **Closed**. Open a card's actions menu and choose **Triage…** or **Move…**; the available actions depend on the stage and your access. 1. In **New**, choose **Triage…** to set **Priority** to **Normal**, **Urgent**, or **Critical**, and optionally add a **Category**. Save to move the request into **Triage**. Keep the category general: it can appear to anyone with workflow access, so do not put a name or request details there. 2. In **Triage**, a prayer manager can assign the request to a department prayer team member from the detail page's **Manage** panel. The request then appears in **Assigned**. 3. In **Assigned**, the assigned person or a prayer manager can choose **Move…** and select **Start praying**. 4. In **Praying**, choose **Request follow-up** when you need an update, or **Mark answered** when the request has been answered. You can add an optional **Testimony** when marking it answered. 5. In **Awaiting update**, choose **Resume praying** when follow-up is complete, or **Mark answered** if the request has been answered. 6. In **Answered**, choose **Reopen** if more prayer is needed. The request returns to **Praying** when it still has an assignee; otherwise, it returns to **Triage**. 7. A prayer manager can choose **Close** when follow-up should end, then select a closure reason: **Withdrawn**, **Duplicate**, **Invalid**, **No longer needed**, or **Other**. A closed request is archived and appears under **Archived** in the list. Closing also archives unpublished Share Kits derived from the request; review published kits separately. When the standard prayer workflow is active, it reminds leaders after a request has waited 24 hours in **New** or **Triage**, and reminds the assignee and a leader after 24 hours in **Assigned**. After seven days in **Praying**, it moves the request to **Awaiting update**. If contact consent is enabled, the requester also receives a follow-up request. If the request remains in **Awaiting update** for 14 days, the workflow reminds the assignee and a leader; it does not automatically close the request. The department's workflow setup may change these rules. See [Set up and use Workflows](/portal/workflows). ## Manage a request Prayer managers can use the request's **Manage** panel to: * Assign a department prayer team member or select **Unassign**. * Change **Visibility**. * Select **Change status** to set **Open**, **Answered**, or **Archived**. Add an optional **Testimony** when marking it answered. Setting it to **Archived** also archives unpublished Share Kits derived from it. * Select **Delete request** to permanently remove the request and its comments. This cannot be undone. Share Kits derived from the request are retained as archived audit records with their title, caption, and link redacted. The requester can also delete their own request. Before deleting, confirm that the request should be removed rather than kept in **Archived**. ## Protect privacy and consent * Treat **Private**, **Prayer team**, and **Church wall** as different audiences. Do not change a request to a wider audience unless the requester has agreed. * An anonymous request hides the requester's name from other viewers. A prayer manager can see the name only if the requester also allowed contact. The requester's comments inherit the same anonymity. * Contact consent allows an authorized prayer leader to contact the requester. It does not make the request public. * Testimony consent allows the system to draft a Share Kit from an answered testimony. It does not publish the kit automatically. Review it through the [Share Kit approval process](/portal/share-kit). * Changing visibility to **Private** does not retract content that has already been published or made public. Review related Share Kits and archive them if they should no longer be shared. If testimony consent has been withdrawn, check existing kits as well; they are not automatically withdrawn. If you cannot see a request or an action you need, contact your church administrator. Request visibility and department permissions are enforced when the request is loaded and when you try to change it. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.