Skip to main content
The Platform, Access & Integrations workspace brings accessibility support, developer tools, data portability, and plan controls together without weakening the privacy rules of the products that own the underlying records.

Help Members Shape Their Experience

Members open Profile > Access & data in the mobile app to choose text size, contrast, reading presentation, reduced motion, audio-first use, language, caption language, Data Saver, and optional image loading. These device choices apply across the app and continue to work when the network is unavailable. Members can also record a large-print bulletin need, interpreter request, mobility help, audio description, sensory information, dietary or allergy information, and other support notes. Those details are private by default. They appear to an authorized church support team only after the member turns on sharing. Requesting help also requires that explicit sharing choice.
Access notes can help a church prepare, but they are not an emergency or medical service. Keep urgent safeguarding, medical, and emergency needs in the workflow responsible for them.

Respond to Access Requests

Staff with Platform access support permission open Platform, Access & Integrations > Member access. The queue contains only profiles members have chosen to share. Staff can acknowledge or resolve a request without adding its private narrative to general member search, analytics, or audit descriptions. The same section holds the church’s default language, access-support email, and low-bandwidth stream fallback. Export retention belongs in Data & plan.

Configure Integrations Where They Are Used

Provider setup stays in the product that uses it, so administrators do not have two competing places to manage the same connection. For example:
  • Giving providers remain in Giving settings.
  • Messaging providers remain in Communications or Marketing.
  • Streaming providers remain in Streaming and media settings.
  • Imports remain in the member-data migration workflow.
The Platform workspace keeps only cross-product developer controls such as the public API and outgoing webhooks.

Send Signed Webhooks

An integration administrator can add an HTTPS endpoint, choose Event, registration, and Giving event types, and send a safe test event. The signing secret is displayed only when the endpoint is created or the secret is rotated. Copy it immediately to the receiving system. Failed deliveries are retried with the same event identifier, and an administrator can retry a delivery manually. Giving payloads contain status and financial identifiers needed for reconciliation, not donor identity. Webhook receivers must use a public HTTPS address; local and private network destinations are refused.

Export Church Data

An administrator with Platform data export permission can request one full church export from Data & plan. The ZIP contains a manifest and machine-readable files for church-owned relational records. It excludes or redacts passwords, API keys, provider credentials, tokens, sessions, queue internals, and webhook secrets. The export is private, tenant-scoped, audited, and available only until the displayed expiry. Download it before that time and keep the copy according to your church’s records and privacy policy.

Change or Cancel a Plan

Base plans are month to month and have no termination fee. A user with Platform billing management permission can cancel the current paid base plan in one action. Cancellation moves the church to Free and stops future base-plan renewal without deleting church records, donation history, or giving provider connections. Existing add-on access remains available through its already-paid period. Create and download a full export before leaving if the church needs an independent copy of its records.

What Remains Gated

Real-time sermon translation is still a separate low-latency streaming and live-caption workflow. The platform’s AI Assistance safeguards are available, but they do not yet provide that live audio pipeline. Published transcript translations, captions, multi-language content, campus workflows, and first-party clearance status continue to work now.