Separate login from the parish apps. First sign-in on a fresh install becomes the owner.
management.vianney.church
Parish instances
Subdomain
Parish
Status
Plan
Monthly
Paid until
Last payment
No instances yet — add the first parish below.
Add a parish instance
New instances start as provisioning with the manual render.yaml steps recorded on the row. Plans are sized by souls; once stats can see the parish, the details panel suggests the right tier. Monthly follows the plan tier’s price (see Plans & pricing under Billing).
Clusters & Pastorates — link separate parishes under one pastor. Databases stay separate; this is an overlay only.
Click one to open it.
New cluster or pastorate
A cluster or pastorate links existing parish instances under one pastor (distinct juridic persons, separate registers and books). Each parish keeps its own database; the parish app simply learns it is grouped through the registry and offers the pastor a combined view.
Dioceses — a diocese governs parishes. Create it, add officials (password + Google sign-in), then assign it to a parish under that instance.
The first admin can sign in at diocese.vianney.church by password (shown once) or Google. Manage each diocese’s officials below; assign a diocese to a parish in that parish’s row under Diocese. The assignment is what turns on that diocese’s policy and communications for the parish.
Funeral homes — the shared list parishes pick from when assigning a funeral. One entry per home (parishes no longer free-type). Published to every parish; nothing here touches a parish database.
The city/area helps tell apart homes with the same name. Archive a home to retire it from the pick-list without affecting funerals already assigned to it. The canonical id is what the portal login and each parish assignment key on.
Import from a state directory (CSV)
Pulls the current Mortuary Science list straight from the state — no download needed.
Pulls South Dakota’s licensed establishments from the state roster PDF — shows a preview to verify before importing.
MN Dept. of Health → Healthcare Provider Lookup → Provider Group “Mortuary Science” → Search → Download CSV, then upload it here. Only funeral homes (MSE records) import; only currently-licensed homes appear in the parish pick-list.
Account requests — funeral homes that asked for a login from the portal. Review, then set one up or decline.
No pending requests.
Portal logins — one login can cover several locations of the same funeral home. Tick which locations it sees.
Creating a login (or ticking reset) shows a one-time temporary password to give the funeral home. They sign in at funeralhomes.vianney.church and see funerals from all their ticked locations.
Console administrators — who may sign in to this management console. Google sign-in only; no passwords here.
loading…
The new administrator signs in with Google using this exact address — there is no password to set. owner can manage administrators and everything else; admin is reserved for future scoping (today admins have the same console access as owners). You can never remove the last owner or your own account.
Registry-read credentials — each service's own identity for reading the registry, replacing the one shared token.
loading…
Minting shows the value once — copy it, then set it on that service in Render under the environment variable shown. It can never be redisplayed; if it is lost, Revoke and mint again. Minting is safe at any time: the parish and diocese keep using the shared token until you set the variable, and a re-mint leaves the old credential working through a short overlap window. Rolling a service back: a set-but-rejected credential fails closed rather than silently retrying the shared token — so delete the environment variable first, verify registry reads on the legacy token, and only then Revoke (which kills every credential in the scope, overlap window included).
Automation credentials — each nightly job's own identity, replacing the shared token for automation.
loading…
Billing and Support credentials go live at mint (Management is their receiver) — paste each into its GitHub Actions secret. Usage and Readings install on the parish first as pending (they cannot authenticate yet): paste the value into its GitHub secret / Render cron variable, then press Promote to switch it live. Values are shown once; if one is lost or an install fails, Revoke the scope and mint again. The same fail-closed rollback rule applies: remove the secret first, verify the job on the legacy token, then revoke.
Statistics
Parish
Status
People
Staff
Actions 7d
AI $ (month)
Msgs 30d
Captures 30d
Storage
Est. cost /mo
Margin /mo
Last activity
No live instances to report on yet.
Live Demo
…
Audit trail
Appearance — tune the brand for every Vianney site. Changes preview live in this console; Save publishes to all sites within a minute. Platform owner only.
Loading…
Preview
Active tabTab
ChipBadge
Sample heading
Body text in the brand. The button, tabs, chip, badge and this card update as you drag — and so does this whole console.