Apps Settings
Per-app branding, integrations, canvas controls, and publishable API keys.
Overview
An app is the container for flows, SDK keys, integrations, and canvas editor controls. Settings here affect both what authors can place in the flow builder and what your live app receives at runtime — for example attribution and paywall adapters.

App list and general settings
- Apps — Create or select an app from the workspace app list. Each app has its own flows, channels, analytics, and credentials.
- App information: Set the app name, website, store link, and branding used where Rheo surfaces app identity.
SDK
Open App settings → SDK, directly under API Keys. This screen holds web SDK settings. It does not require a plan toggle.
Web SDK
- Allowed web origins — add each site as scheme, host, and port (
https://app.example.com). Use Add http://localhost:5173 for the Next.js example.httpis allowed only forlocalhostand127.0.0.1. Browsers may call the SDK only from origins you list. Requests with noOriginheader, such as the mobile SDKs, are unchanged.
See Web SDK.
Integrations
Open App settings → Integrations to connect partner services. Integration availability depends on your workspace plan — Grow and above.
Stripe
Toggle Stripe on to allow Integration Nodes that open a Stripe Payment Link in a web funnel. While it is on, the webhook fields stay visible so you can copy the URL into Stripe, save the signing secret, and choose whether Stripe charges count as web revenue.
See Stripe Payment Links.
RevenueCat
Toggle RevenueCat on to allow Integration Nodes with a RevenueCat paywall in the flow builder. While it is on, the webhook fields stay visible so you can paste the URL into RevenueCat, save the Authorization value, and choose which stores count RevenueCat charges. One provider can count charges for each store.
Your host app still initializes the RevenueCat SDK directly; Rheo coordinates paywall presentation through your flow. Your engineering team can follow the RevenueCat integration guide.
Superwall
Toggle Superwall on to allow Integration Nodes that register a Superwall placement mid-flow. While it is on, the webhook fields stay visible so you can paste the URL into Superwall, save the signing secret, and choose which stores count Superwall charges.
Your host app still configures Superwall (API key / provider) directly; Rheo registers the placement when the flow reaches the node and branches on the outcome. See the Superwall integration guide.
External Surface Nodes (host custom UI) do not appear here — they are always available in the flow builder on Grow+ and are wired in the host app via externalSurfaces. See Headless external surfaces.
AppsFlyer
Toggle AppsFlyer on so live resolve can advertise attribution support and your SDK may attach mobile measurement listeners after resolve. Requires a plan that includes attribution.
Your engineering team can follow the AppsFlyer integration guide in the Developer Guide.

Convert settings
Convert settings hold the canvas editor gates for onboarding flows.
Canvas controls
App settings → Convert settings → Canvas controls lets you restrict which layer types appear in the flow builder palette. Disabled types are hidden from authors and block publish if an existing flow still uses them.
Controls cover:
- Lottie animations
- OAuth sign-in (preset and custom providers)
- Email and password auth rows
- OS permission request layers
Your workspace plan may further limit availability. On Indie, animations are not available regardless of the per-app toggle.
Engage settings
Engage settings cover outbound lifecycle messages for Rheo Engage: email, webhook, and push.
- Email Settings — Connect one bring-your-own provider (SES, Resend, Postmark, or SendGrid), set a physical mailing address, paste the bounce/complaint webhook URL, and review deliverability health. That URL is for your email provider, not the Engage webhook channel. For Amazon SES, follow Set up Amazon SES.
- Push settings — Connect APNs, Firebase Cloud Messaging, and Web Push. Generate the Web Push VAPID keypair here. The private key stays encrypted.
- Webhook — No connection on this page. Each broadcast or automation step stores its own endpoint.
- Frequency Cap — Max emails per contact (email only), rolling window, app default timezone, quiet hours (defer email, webhook, and push), and the test destination allowlist (email only).
- Marketing consent — Optional marketing topics mode (off by default), topic labels, and branding/copy for the hosted preference center.
See Set up Engage for the full setup path, including the Amazon SES walkthrough.
API keys
Create or rotate publishable keys for test and live environments under App settings → API keys. Test keys are for development and staging; live keys serve production users.
Share keys only with your engineering team. Rotate immediately if a key is exposed.
These keys authenticate the mobile SDKs and the web SDK. For terminal automation, create a separate CLI API key under Account → Personal and see the CLI guide.
Limits and permissions
- Some settings require admin or owner roles.
- Plan caps — maximum apps, channels per environment, seats, and MAU — are enforced across the workspace. The dashboard shows upgrade prompts when you approach or hit a limit.
See Plans & entitlements for the full tier comparison.