WWJD Works · Famplified LLC

Your privacy choices

This release uses essential browser storage for secure sign-in, invitations, and your session. It does not load analytics, advertising, or tracking cookies.

Essential storage — always active

Authentication and security storage are needed to provide the service you request. Signing out clears the app’s sign-in session.

Language preference

Choosing a language saves that preference on this device. You can remove the saved preference below. This does not change your account or ministry records.

Optional tracking is off. If optional tools are introduced, we will ask before activating them and let you change your choice here.

Privacy notice · Data policy

Learning library

Track a discipleship journey

Publish a pathway, enroll an existing person and reopen their saved progress.

Discipleship is available to authorized staff when selected for their church. Participants come from shared People records. Mentor assignments do not grant access; follow-up tasks stay in the staff workspace and send no message or reminder.

  1. 1. Open your campus workspace

    Sign in, choose your church and open Discipleship. Choose a specific campus in Campus view. An administrator selects Discipleship in Explore apps within your plan and provides the necessary Discipleship and People campus access. Check existing pathways and participant journeys before creating another record.

  2. 2. Publish a pathway

    In Pathways, select New pathway. Enter Pathway title and Pathway description, then add the ordered milestones with Add milestone. Select Create draft pathway. Review the saved draft; use Edit draft pathway and Save draft pathway for changes. Select Publish pathway when the titles, descriptions and order are ready. Publishing freezes that pathway content for enrollment.

  3. 3. Enroll an existing person

    Select Enroll participant. Choose the existing person and a published pathway. Choose an eligible mentor or Continue without a mentor, review the choices and select Confirm enrollment. Open the saved journey to check its participant and copied pathway milestones. A person can have only one journey for the same pathway, including stopped journeys.

  4. 4. Save progress and follow-up

    Open the journey and select Record completion beside a milestone, then Confirm completion. Correct completion marks it incomplete again: enter Reason for correction and select Save correction. For the next staff action, select Schedule follow-up, choose an eligible owner, enter Follow-up title and Follow-up due date, then save with Schedule follow-up. Use Resolve follow-up and record the outcome when the work is done. Once every milestone is complete and no follow-up remains open, select Complete journey. Open the saved journey again to confirm its status and progress.

  5. 5. Review saved history and downloads

    Open Discipleship history to review recorded actions. From Participant journeys, choose the campus and status you need. In Discipleship CSV content, choose Journey summary or Milestone progress, then Download CSV batch. Continue with Download next CSV batch until the export is complete, even if a batch has no rows. Exports start from the beginning of the chosen scope, independently of the displayed list page. They omit notes, descriptions and history; share working copies only with authorized staff.

    If another editor changed the record, select Refresh Discipleship and review its current saved state before editing again. If a record becomes unavailable, ask your administrator to check current campus and People access.

Open your church workspace

Earlier development walkthrough

The existing video below is an earlier development demonstration. Follow the written steps above for the currently available staff workflow.

Watch setup tutorial — Discipleship

Report a problem

Tell us what happened and what you expected. Please do not include passwords or private ministry details.

Page:

Your report includes this page, product, language, and your account and church details when signed in. We do not attach page contents or screenshots.