WWJD Works · Famplified LLC

Your privacy choices

This release uses essential browser storage and an essential sign-in cookie for secure sign-in, invitations, and your session. Our public website pages also use Google Analytics cookies to count page views. Church workspaces, account pages, and prayer, connect, and unsubscribe pages are not measured. We do not load advertising 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.

Campaign labels

If you arrive through a link that carries campaign labels, such as one of our ads, those labels are kept for this visit and saved with a church workspace you create, so we can tell which campaigns help churches find us. They do not identify you and are not shared with advertisers.

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.

You can block or delete cookies, including the page-view cookies, in your browser settings.

Privacy notice · Data policy

WWJD Operations · STEP-BY-STEP GUIDE

Route reviews and recover interrupted changes

Decide on the submitted details, preserve history and check saved state before trying again.

By the WWJD Works team · Updated October 5, 2026

Before you begin

Sign in to the correct organization and make sure this product is enabled. Creation and administration require the appropriate team role. Screens may differ with your language and permissions.

Choose one campus with current Operations staff access. Records stay at that campus. All permitted campuses does not combine records. Archived campuses are read-only; requests have narrower visibility than team tasks.

Church owners and administrators add physical, online, or temporary campuses in Settings → Campuses. In Team & permissions, open Campus & product permissions to set each person’s campus, role, and products. A campus administrator manages records; church settings remain with church administrators and owners.

1

Route without changing the request

A current campus Operations administrator or owner can change the reviewer of a draft, returned or submitted request. Choose a different eligible non-requester account and add a reason. Review and confirm. Routing does not edit content or erase the submission. The previous reviewer loses decision access; separate viewing permissions may remain. Refresh after reassignment. Assignment does not grant membership or authorize contact. Use Next even on an empty selector page when more pages exist; First page restarts expired pages.

2

Decide on the saved submission

Only the currently assigned eligible reviewer can return, approve or reject a submitted request, and never their own. Read the submitted copy, currency, amount and revision. Add a decision note, review and confirm the selected action. Return allows the requester to edit and submit a new snapshot; old evidence stays in history. Approval records a decision only: it does not reserve money, place orders, reimburse anyone or establish a budget balance. There is no payment processing, bookkeeping or financial compliance certification.

Operations — Review a record
Review a record · English interface shown with fictional training data. Select the image to enlarge.
3

Withdraw or revoke with evidence

The requester or an authorized campus administrator can withdraw a draft, returned or submitted request with a reason. An authorized administrator other than the requester can revoke an approval with a reason. Revocation preserves the original approval and does not reverse purchases or other actions outside the app. Rejected, withdrawn and revoked requests are terminal; corrections require a new request and fresh review. History shows oldest changes first and retains reasons, decision notes and visible actors. Review all relevant pages; a partial list cannot prove a record is absent.

4

Recover without repeating uncertain saves

Copy unsaved text before leaving or changing campus; drafts are not stored in your browser. Validation keeps editable input. If the record changed, reload its saved state and review again. If creation could not be confirmed, inspect saved tasks or requests and their pages before creating another. If a decision response is lost, refresh to see whether it saved; do not repeat automatically. Access loss clears private details. Sign in or ask your administrator when necessary; never use another campus or account to bypass a denial. Keep sensitive pastoral narratives and bank details out of tasks and requests.

Watch the getting-started video

If something looks different

Missing actions usually depend on your role, the record’s visibility or status, or whether the product is enabled. Ask your organization administrator before creating duplicate records or changing access.

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.