​

Client onboarding

TheFaithApp uses a reviewed, invitation-only onboarding process for new church accounts. Public visitors can review product screenshots and setup guidance, or request access without immediately creating an account.

​

Explore before requesting access

Open a product page to review screen examples and setup guidance without an account. Choose Enlarge screenshot beside an image to inspect it in a larger view. Choose View original size to inspect details and scroll around the image. Use Fit to screen to see the whole screenshot again. Open full image opens the image directly. Choose Close or press Escape to return to the product page. Keyboard focus returns to the link you opened. If the viewer is unavailable, the link opens the original image. Screenshots are examples, not an interactive dashboard. The demo dashboard requires sign-in. Review the product guidance and plans before requesting access. For a visual overview, watch the 88-second account-setup walkthrough. It uses fictional details and AI narration to show the access request, private invitation, registration and dashboard setup guide. Requests are reviewed; submitting one does not create an account or guarantee approval.

​

Request access

A church begins from the Request access page on the TheFaithApp website. The form asks for enough context to understand the church, its goals, approximate size, current tools, and desired start date. If the form shows a Security check, complete it before sending the request. An expired check can refresh automatically. Use Retry security check if it cannot finish; your entered details stay on the page. If the check remains unavailable, you can still explore the public product details and return to the request later. Submitting the form does not create an account. The page confirms receipt while the request enters the Super Admin review queue and the platform review inbox receives an alert. The applicant receives a receipt email explaining that review is pending. This is not approval and does not promise a response time. Repeating the same recent request does not send another receipt. Approved applicants later receive a separate private invitation.

​

Review a request

Super Admins can open Client Onboarding to see new requests and invitations already in progress.

1. Select Review beside a church.
2. Confirm the church and contact details.
3. Record internal discovery notes.
4. Move the request through New, Contacted, or Qualified.
5. Send an invitation when the church is ready to proceed, or decline the request when it is not a fit.

Internal notes are visible only to Super Admins. The review panel also records when an invitation was last sent, when it was first opened, when it expires, and how many times it has been sent. Once an account is created, review actions cannot decline the request, revoke its invitation, or send another account setup invitation. Refresh an older review panel to see the current status. Optional attribution can still be removed when consent is withdrawn.

​

Send a private invitation

Selecting Send invitation emails a private account setup link to the approved contact. A Super Admin can also use Invite a client to invite a church directly after an offline conversation. Each invitation:

• is tied to the approved email address;
• can be used only once;
• expires after seven days;
• can be resent with a fresh link; and
• can be revoked before account creation.

The recipient confirms their details, chooses a password, reviews the church information, and optionally uploads the church logo. Churches without a logo use the default TheFaithApp mark until they upload their own in Settings → Church Profile. Opening the email-bound invitation also verifies the approved address, so completing setup does not send another verification, welcome, or new-registration email. The account becomes active only after setup is completed successfully. During invited account setup, Next Step moves to the next section and Previous returns to the earlier section without clearing its values. For keyboard users, focus moves to the new step. If a section needs a correction, focus moves to its first invalid field before you can continue. After account creation, the app starts sign-in so you can continue to the dashboard. If sign-in cannot finish, the sign-in page confirms that your account is ready. Enter your invited email if it is not already filled in and use the password you just chose; you do not need another invitation. While Complete Registration is processing, wait for the result before trying again. If setup fails, your entered details stay available for a retry.

​

Your first steps after signing in

The main church administrator sees Put your first church workflow to work on the dashboard. The five steps continue beyond account setup:

1. Use Members → Add New Member for one person, or Import Members for a CSV. Save a record first, or choose Send a welcome invitation now when the person is ready to receive sign-in details.
2. Publish your first form with public access. A connection-card template is a useful starting point. Test the public link before sharing it.
3. Check your church name, email and location in Settings → Church Profile. Details supplied during signup already count toward this step.
4. Share the published form with someone who wants to connect. A completed public response counts toward progress; unfinished or spam responses do not.
5. Open Forms → Responses, choose a response, assign a staff member and set a due date, then select Save follow-up. If the follow-up is already done, save its status as Completed instead.

A logo is optional and never holds back essential setup progress. You can add or change it later. Publishing a form alone does not finish the guide. Once a public response arrives, the reminder prioritizes its next step in Forms → Responses, then returns to any unfinished setup work. You can work on these steps in any order. Progress reflects saved church data when you return to the dashboard; opening a page does not complete a step. Draft, closed, archived and member-only forms do not complete the public-form step. The compact reminder links to your next unfinished task; expand Setup steps to review the full checklist at any time, including after completion. This guide is for the main administrator, not restricted staff accounts. When all five steps are complete, Your first church workflow is in place keeps response review within reach. Recording a next step does not send a message or complete the actual follow-up for you. Continue checking your response inbox and the work your team has agreed to do. An Active onboarding request means the account was created. It does not mean that every setup step is finished or that the church is actively using the product.

​

Account creation and activation

The onboarding workspace labels completed registrations Account created. In the review drawer, Church activation separately shows whether the church has a member, a published public form, and a completed non-spam public response. All three are required for Activated. These are current-state indicators, not permanent historical events: removing records or closing a form can change the result. No member details or response answers appear in this summary.

​

Compare acquisition activity

Use Acquisition activity to choose a start date, end date and reporting time zone, then select Apply dates. The default is the last 28 complete days in East Africa time. Choose the same dates and time zone as the analytics report you are comparing. Pacific time is available for comparisons with Google Search Console. The report is independent of the request-list search and status filters. The report covers public access requests. It excludes manual invitations and records marked as QA/test. Each saved enquiry counts once; repeating an accepted submission does not create another enquiry. Separate enquiries saved later are separate records, rather than a count of unique churches.

• Unique enquiries uses the date the enquiry was received.
• Accounts created uses the date the private invitation was accepted and the account was created. Each church account counts once.
• Activations recorded uses the first recorded completion of all three activation milestones. Each church account counts once.

Accounts and activations can come from enquiries received before the selected dates. These are activity counts, not a cohort conversion rate. A first recorded activation date is retained even if a form is later closed or a record removed. Recording starts with this reporting feature; earlier activation dates remain unknown. Some bulk updates are observed on the next five-minute check. Source and medium are shown separately, so google / organic and google / cpc remain distinct. Recognized search referrals can supply a source and medium only after analytics-cookie acceptance. Linking those labels to a request also requires the applicant’s separate opt-in on the access form. Search terms and full referring addresses are not stored for this attribution. Unattributed / unknown includes enquiries without both consent choices or available source information. It does not mean direct traffic. Earlier requests are not filled in retrospectively, and these labels do not prove that a channel caused a signup. Browser analytics may omit unconsented or blocked events; its accepted-submission count can also include retries that did not create a new saved enquiry. Open a request to review its optional campaign source, campaign and content label. A content label can distinguish a tracked post or link when the applicant has opted in. Earlier requests are not filled in retrospectively, and a saved campaign label does not establish an organic-search session. Optional measurement does not affect whether an access request succeeds. If your browser cannot keep optional storage, labels on the current tagged link can still be attached after both choices are accepted; earlier visits may be unavailable. Use the confirmation on the request page to know that it was received. An access request is still subject to review and is not a created church account. Open Free tool activity to see the same dated activity for Church SMS templates and the Visitor follow-up planner. It uses the last free tool visited in the previous 90 days with analytics consent, and attaches it only when the applicant separately opts in on the access form. A request can be linked without copying a message, downloading a plan, or using the tool’s Request access button. Other or unattributed includes requests without a consented tool visit. Earlier requests are not filled in retrospectively.

​

Keep QA separate

Use Mark as QA/test in the review drawer to exclude a synthetic record from acquisition reporting, including after its account has been created. This does not revoke access or change the church’s onboarding stage. Remove QA exclusion reverses the classification. Use Show QA records in the request list to find excluded records; this does not include them in acquisition reports. When preparing a test invitation, select This is a QA/test invitation. The current pipeline cards also exclude QA but cover all dates and include ordinary manual invitations. Review suspected spam separately; a random-looking name does not automatically classify a request as QA or decline it. Optional source, medium, campaign, content, and free-tool labels are removed after 90 days. Do not put names, email addresses, or other personal information in campaign labels. If an applicant withdraws consent, find their request and use Remove attribution on consent withdrawal. Their application and church account are preserved.

​

Public exploration and demo access

The public request page keeps two exploration options beside the form:

• Explore product details opens public screenshots, setup guidance, and plan details.
• Demo dashboard sign-in opens the dedicated demo sign-in page. You need demo access to use the dashboard.

Begin with the public product details to understand the platform without an account. Use the access request to share your team’s rollout, migration, or fit questions for review.

​

Invitation problems

If the page says its secure link session is unavailable, reopen the original invitation from your email. This starts a fresh setup session while the original invitation is still valid; you do not need to submit another access request. The temporary page address is not a replacement for the email invitation. If an invitation has expired, was revoked, or was already used, the setup page does not expose the church details. If you already completed setup, sign in with the password you chose. Use Forgot password on the sign-in page if you need to reset it. For an unused invitation that has expired or been revoked, contact TheFaithApp so a Super Admin can review the request and send a fresh invitation when appropriate. If you are unsure whether setup was completed, contact TheFaithApp for help. Connection failures show Try again instead of incorrectly treating an invitation as expired. Failed signup submissions retain entered details while the page stays open. Passwords are not saved as a browser draft. The dashboard also offers Try again if its data cannot be loaded.