Getting Started

Publish the first church form with Amen Identity, Core and Forms.

Getting Started

Amen Forms is the first church SaaS built as a strict specialization of the Amen B2B boilerplate. Identity owns sessions, Core owns churches, members and billing, and Forms owns its product data.

Service topology

Service	Responsibility
Identity	credentials, OTP, OIDC authorization and account security
Core	users, churches, memberships, invitations, billing, API keys and product-session minting
Forms API	drafts, immutable published versions, submissions, notification rules and exports
Forms web	TanStack Start public site, church sidebar, builder and response workflows

Tokens stay in memory. Identity and Core credentials are never persisted by Forms, and every tenant query derives its workspace from a short-lived Core-signed product token.

First activation journey

Sign in through Amen Identity.
Create or select a church. Core owns the workspace and installs Forms.
Open Forms in the organization sidebar.
Start from New visitor, Event registration, Prayer request or Volunteer.
Adapt the questions and consent copy, then publish an immutable version.
Copy the public link or download its QR code.
Submit one response without an account and open it in the Responses screen.

The activation target from the Forms roadmap is a published form in under five minutes and a first response on the same day.

Build a guided form

Use Add to form or the + between questions to open the insertion menu. The inline button inserts the new field at that exact position and stays visible on touch screens. Each question type comes with a suggested label and example answer. In a choice list, add or remove answers and drag the handle to change their order. The handle also supports Alt + Up/Down for keyboard reordering.

To create different paths, add at least two steps after a choice list. For each answer, choose a later step in If selected, go to. Answers left on Next step continue in order. Preview both paths before publishing. Questions on skipped steps are neither required nor saved for that response.

Local services

VITE_IDENTITY_ISSUER=http://localhost:3456/api/auth
VITE_CORE_BASE_URL=http://localhost:3200
VITE_FORMS_API_URL=http://127.0.0.1:3092
VITE_OIDC_CLIENT_ID=amen-console
VITE_CONSOLE_ORIGIN=http://localhost:3091

The browser sends Identity tokens only to Identity, Core tokens only to Core, and Forms product sessions only to the Forms API.

What already works

draft creation and editing;
immutable versions at publication;
public schema resolution and idempotent submissions;
honeypot and timing signals with a generic public response;
response list/detail/summary;
audited CSV export and QR PNG/SVG;
notification-rule configuration without falsely claiming delivery.

External mail delivery, People/Connect actions, adaptive abuse protection, file quarantine, retention jobs and the API-key/MCP gateway remain explicit missing Amen capabilities.