add Church Flow, Church Flow Portal

[Ivydevdre]

Description

New template for Church Flow (https://church-flow.com), a multi-tenant church management SaaS. The portal service connects a customer-owned domain to their Church Flow portal via a single CNAME to %target%.church-flow.com (the tenant's identifier). The template uses the synchronous flow with redirect_uri and signed apply URLs (syncPubKeyDomain: dc.church-flow.com).

Type of change

Please mark options that are relevant.

• New template
• Bug fix (non-breaking change which fixes an issue in the template)
• New feature (non-breaking change which adds functionality to the template)
• Breaking change (fix or feature that would cause existing template behavior to be not backward compatible)

How Has This Been Tested?

Please mark the following checks done

• Template functionality checked using Online Editor
• Template file name follows the pattern <providerId>.<serviceId>.json
• resource URL provided with logoUrl is actually served by a webserver

Also linted with dc-template-linter -loglevel error -tolerate info -logos church-flow.com.portal.json — exit 0, no findings.

Checklist of common problems

Mark all the checkboxes after conducting the check. Comment on any point which is not fulfilled.
See Template Quality Guidelines for details and rationale on each rule.

• syncPubKeyDomain is set — this is mandatory; omitting it requires explicit justification in the PR description or the PR will be rejected
• warnPhishing is not set alongside syncPubKeyDomain — the two must not appear together
• syncRedirectDomain is set whenever the template uses redirect_uri in the synchronous flow
• no TXT record contains SPF content ("v=spf1 ...") — use the SPFM record type instead (n/a — the template contains no TXT records)
• txtConflictMatchingMode is set on every TXT record that must be unique per label or content prefix (e.g. DMARC) (n/a — no TXT records)
• no variable is used as a bare full record value (e.g. @ TXT "%foo%") unless necessary — prefer @ TXT "service-foo=%foo%"; if bare, justify in the PR description (pointsTo is %target%.church-flow.com — variable is anchored to a fixed provider-owned suffix)
• no bare variable is used as the full host label — the non-variable parts are fixed to limit misuse (e.g. %dkimkey%._domainkey, not %dkimhost%); if bare, justify in the PR description (host is @)
• no variable is used in the host field to create a subdomain — use the host parameter or multiInstance instead (the host parameter is used; hostRequired: true)
• %host% does not appear explicitly in any host attribute
• essential is set to OnApply on records the end user may need to modify or remove without breaking the template (e.g. DMARC) (n/a — the single CNAME is the entire service; removing it disconnects the domain by design)

Online Editor test results

Editor test link(s):

Test church-flow.com/portal example.org/members

Result: members.example.org. CNAME 3600 demo.church-flow.com — as intended.

Apex test (domain only, no host): correctly rejected with "Template requires a host name" — expected, since the template declares hostRequired: true (per the exception noted in this PR template, an apex test link is not required for hostRequired: true templates).

🤖 Generated with Claude Code

[github-actions]

✅ JSON Filename Check Passed

[github-actions]

✅ JSON Schema Validation Passed

[github-actions]

PR Description Check Passed

All required sections are filled in correctly.

Details

  OK  Type of change: 1/4 checkboxes ticked
  OK  How Has This Been Tested?: all 3 checkboxes ticked
  OK  Checklist of common problems: 10/10 checkboxes ticked
  OK  Online Editor test results: 1 link(s) found
  OK  Template coverage: all 1 template(s) covered
Labels to remove: Checklist of common problems not complete, Forged editor links, PR description incomplete, Test links missing

PR description check PASSED

[github-actions]

Linter OK

church-flow.com.portal.json

Level	Code	Note

[github-actions]

Linter passed all checks — approving for auto-merge.

[github-actions]

Thanks @Ivydevdre for contributing to the template. 🎉

This template has been reviewed and merged by @pawel-kow. 🙌

This template repository and its review process are maintained by independent individuals in their spare time, not as part of a paid role. If you or your company benefit from this protocol and its tools, please show your appreciation by buying a beer for @pawel-kow: https://github.com/sponsors/pawel-kow