Forms gives your church one place to create flexible forms, share them, and
coordinate what happens after someone responds. Use Forms for connection cards,
ministry interest, membership next steps, feedback, pastoral requests, internal
requests, and other church workflows that do not belong to a specialized
product.Each response stays attached to the exact version of the form that the person
completed. Your team can assign an owner, set a due date and priority, add
private notes, and keep an activity history without moving the response into a
separate spreadsheet.
At least one administrator has permission to manage Forms.
Staff who will review responses have response access.
Sensitive or restricted forms have named form managers.
The church’s privacy wording and follow-up owner are agreed before publishing.
Any custom domain you want to use is already connected in TheFaithApp.
Forms may contain pastoral, child, safeguarding, health, or other sensitive
information. Collect only what your church needs, choose the correct
sensitivity, and give response access only to the people responsible for the
follow-up.
From All Forms, select Create form to start with an empty form, or
select Browse templates to start with reviewed questions and settings for a
common church workflow.The template catalog includes starting points for:
General contact and connection cards.
Baptism and membership interest.
Volunteer interest and applications.
Small-group interest.
Child dedication and pastoral appointments.
Prayer requests and praise reports.
Event feedback and facility requests.
Annual member-information review.
Communication preferences and testimony submissions.
Templates are editable starting points. Review every question, privacy notice,
access choice, sensitivity, and manager before publishing.
Start with the shortest form that can support the next action. A clear form
with fewer questions is usually easier to complete and easier for staff to
follow up.
Select a question on the canvas, then review its settings. Depending on the
question type, you can:
Change the label, help text, and placeholder.
Make the question required.
Set minimum or maximum limits.
Add a custom validation message.
Mark the answer as standard, sensitive, or restricted.
Map an eligible answer to a member-profile field for staff review.
Choose whether the answer may appear on the confirmation screen.
Drag blocks to reorder them, or use the up and down controls for keyboard
reordering. Duplicate a block when several questions need similar settings.Profile mapping never silently replaces a member’s saved details. A matching
response can create a proposed change for an authorized staff member to review.
Member aware remains public and can safely prefill verified member details
after sign-in.
Member only requires a verified church member.
Invite only requires a valid invitation.
Restricted is intended for tightly managed or sensitive collection.
You can also decide whether a verified member may respond for themselves, an
authorized adult in their household, or a child in their household. Child
responses require guardian attestation and restricted handling.
The staff members or permission groups responsible for the form.
Restricted forms should always have explicit managers. Managers can be used to
limit response access and receive response notifications without opening the
answers to every administrator.
Select Preview to review the draft without accepting a submission.
Check required questions, choice options, privacy wording, and confirmation
text.
Select Publish or Publish update.
Confirm the version that will become public.
Publishing creates an immutable version. Later edits create a new draft, while
the public form continues using the last published version. Select Versions
to review the version history.This keeps older responses understandable after a question is renamed,
reordered, or removed.
Paste the complete code into a website block that accepts custom HTML or an
iframe.
Publish the website page.
Test the page on a phone and computer.
Submit one test response and confirm that it appears in Responses.
Do not change the address inside the supplied iframe. If the form is long, the
website manager can increase the iframe height while keeping the form address
unchanged.
Open the public link before sending it to anyone.Confirm that:
The church name, form title, description, and color are correct.
Required questions and validation messages are clear.
The privacy notice explains how the answers will be used.
The form works at phone and desktop widths.
The confirmation message gives the respondent a useful next step.
Scheduled opening, closing, and response limits behave as expected.
Public submissions include duplicate and spam protections. If a connection is
interrupted, the respondent can retry safely without creating an extra response
from the same submission attempt.
A published form can be placed in a reviewed area of the member app through App
Customization. Members see the same published questions and validation rules as
the web form.
Invite a member when the form should be delivered directly rather than shared
as a general public link. The delivery record shows whether the invitation was
queued, sent, opened, started, submitted, declined, or expired.Reminders use the original delivery channel and respect the member’s messaging
preferences. Avoid repeatedly reminding someone about a sensitive form.
Open Forms → Responses for the global inbox, or open a form and choose its
responses view.Use the inbox to:
Search respondents and answers.
Filter by form, status, priority, owner, and submission date.
Show current or historical answer columns.
Choose visible columns.
Save a useful filter as a view.
Export the authorized view to CSV.
On phones, each response appears as a readable card with its submitted time,
status, priority, form, respondent, owner, and selected answer columns. Select a
card to open the full follow-up view. On larger screens, the same information is
available in the response table.One row is always one submission. Repeated responses from the same person stay
separate instead of being merged.Sensitive answers are hidden or redacted for staff who do not have permission
to see them. Export uses the same access rules as the inbox.
Forms can start reviewed actions for supported workflows such as visitor
follow-up, member journeys, events, volunteer coordination, Community Groups,
prayer requests, or an Outreach Campaign review reference.Configure actions from Delivery and review the target before activating
them. Each action is recorded against the response so staff can see whether it
completed, failed, or is waiting for review. A failed action does not remove the
original response.Forms does not copy submissions into the legacy Donor Forms tables. A future
fundraising or donor-data transfer must be separately reviewed and explicitly
configured.
Forms separates permission to build forms from permission to review responses.
Sensitive-answer access and form-manager restrictions narrow access further.Recommended practice:
Give form-building access only to staff who design church workflows.
Give response access only to staff who own follow-up.
Name managers for pastoral, child, safeguarding, or other restricted forms.
Avoid collecting financial card data, passwords, government identifiers, or
information that belongs in a specialized product.
Review CSV exports before sharing or storing them outside TheFaithApp.
Confirm consent before sending reminders or starting a connected action.
The current release does not yet include nested conditional logic, multi-page
branching, partial submissions, file uploads, electronic signatures, payments,
calculations, webhooks, or direct spreadsheet integrations.Use the existing specialized Giving, Events, Prayer Requests, Visitor, and
Outreach Campaign workflows when they already match the church’s need.
