The customer problem
Keep the workflow where your team already works.
A volunteer can be added to a group, complete a form, or receive a connection in One Church, then someone still has to remember to start screening and chase its status in a second system. That handoff is easy to miss when the ministry is busy.
What shipped
Clearer work, fewer handoffs.
P51 now receives configured One Church events, routes the person to the checklist your church selected, and returns a Background Check safeguard to the One Church record. The safeguard shows the current state and includes a PreSearch link for staff who need the detail behind it.
- Configured group, form, or connection events can begin the workflow.
- Checklist routing keeps the screening requirements tied to the church workflow.
- The person receives a secure onboarding link to complete the intake.
- One Church receives lifecycle status updates and a link back to PreSearch.
Written walkthrough
What the video shows, in plain language.
The walkthrough starts with a fictional church team adding a Background Check connection to a volunteer profile. P51 receives the configured event, creates the right screening path, and emails the volunteer a secure link. Once the volunteer completes the forms, the church reviews and submits the order in PreSearch. One Church then reflects the status as the screening progresses, including a clear result or a result that needs the church's review.
- 1Start from the church workflow
A configured One Church connection, group membership, or form event can begin the screening path.
- 2Complete the secure intake
The person receives a secure onboarding link to complete the screening steps.
- 3Review and submit
The church reviews the order in PreSearch, or uses a configured automatic-submit rule.
- 4See the status return
The One Church safeguard follows the screening lifecycle and links back to PreSearch.
Who this is for
This is for churches and ministries that use One Church and want a screening handoff that matches how they already add volunteers and staff.
Related services
What you'll need to get started
Your church needs its own One Church API key, the trigger you want to use, a Background Check safeguard field, and the checklist that should apply. PSBI helps map and test that setup with your team.
Questions teams ask
Release FAQ
What can start a screening in One Church?
A configured connection, group-membership event, or form event can start the screening path. Your church decides which workflow should act as the trigger.
Does every One Church change start a background check?
No. P51 only acts on the event and configuration your church selects. Other profile edits do not start a screening.
Where does the church make a decision when results need review?
The church reviews the screening in PreSearch. A result that needs review stays visible as such in the One Church safeguard until the church makes its decision.
What do we need before launch?
A One Church API key, the configured trigger and safeguard field, and a mapped P51 checklist are needed before the connection is ready.