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 Policies · STEP-BY-STEP GUIDE

Publish, collect acknowledgments, and revise

Keep acknowledgments tied to the exact version each person read.

By the WWJD Works team · Updated September 30, 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.

For a church with multiple locations, choose a campus in the top bar before creating a record. All permitted campuses combines only records you can access. Check the Campus field before saving; changing it transfers that record and requires access to both campuses. Policies and boards can also be church-wide.

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

Publish the reviewed version

Open the draft and choose Edit policy. When the text, document, and assignments are ready, change Status to published and save. Published wording and its document are fixed; review them before this step.

2

Record individual acknowledgments

Assigned team members sign in, open the policy, read its contents, check the acknowledgment statement, and choose Record my acknowledgment. Administrators can review completion and use Remind pending members. Email delivery requires the configured mail service.

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

Create a new version for changes

Use Create next version when the policy wording changes. The new draft is a separate version with no inherited acknowledgments. Review, assign, and publish it so readers acknowledge the revised text themselves.

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.