scripts/products/accounts.sh (backup with pg_dump, build with the shared packages, PM2, export, keep, failed-migration recovery); accounts in SUPPORTED_PRODUCTS so deploy updates it where a church has it. Env template in both places, PM2 example, export script, /api/health version from package.json. README, CHANGELOG, WHATS-NEW; the plan's changes while building and what's still to do. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
703 B
703 B
What's new in Accounts
What each version changes for the church, in plain language (read by the Hub like Cross Events' WHATS-NEW.md; a section shows once its version is tagged).
1.0.0
- One sign-in for all your church's sites and apps. People sign in once with their own account and are signed in to the church website, the app and Cross Events, and come back to the page they were on.
- Secure by default: two-step sign-in with an authenticator app, email or WhatsApp, recovery codes, and required for admins.
- People control their own information: they change their details, choose their news, download their data or ask for their account to be deleted, all in one place.