Integrations
Integrations
Section titled “Integrations”Prefer external systems for content and church operations that Garrison Bible Study should not rebuild. v1 is mostly deferred except Logos deep linking — see Product Scope.
| Integration | v1 behavior |
|---|---|
| Logos | Deep link to passage in Logos app/web |
| OneNote | None — journaling stays in Garrison Bible Study |
| MinistryImprint | Manual personality fields in onboarding (no API) |
| Planning Center / Breeze | None (design for later OAuth + membership) |
| Canvas / Proclaim / PowerPoint | None |
People management (later)
Section titled “People management (later)”Sync policy: ChMS authoritative only for membership and SSO at link time; Garrison Bible Study authoritative for profile after account exists. Login works if ChMS is down.
ChMS-verified membership at link time satisfies the church-trust path for Identity verification exemption (users skip platform ID checks when linked via this path).
Content
Section titled “Content”- Logos — deep links v1; API if ever available.
- In-app scripture: self-hosted Open Bible–style or Logos per Bible and Scripture.
LMS (later)
Section titled “LMS (later)”- Canvas — LTI and grade passback (not v1).
Presentation (later)
Section titled “Presentation (later)”- Export study outlines to PowerPoint and Proclaim (not in-app presentation mode in current plan).
- MinistryImprint — manual onboarding fields now; import/sync later if valuable.
Technical pattern
Section titled “Technical pattern”- Abstract PeopleProvider (or equivalent) before first ChMS implementation.
- Webhooks and REST endpoints live outside GraphQL where appropriate (Architecture).