Configuration reference
Every church on Apollos has a set of configuration values that control how features behave — which ChMS you connect to, which optional features are on, and church-specific details like how new members are recorded in your ChMS.
How it works
When a church uses its own API.Bible key, the configured translation remains fixed to the translation supported by that key.
Configuration values are set per church. Most are configured for you during onboarding, and many are managed together with Apollos support — if you're unsure whether a setting applies to you, just ask your Apollos contact.
Sync-related settings (sync status and sync cadence) have their own page: see How data sync works.
A note on timing: configuration changes can take up to 5 minutes to take effect in the app while caches refresh.
Rock RMS settings
These settings apply to churches connected to Rock RMS. See Rock RMS for the full integration guide.
Rock connection settings
| Setting | What it does |
|---|---|
ROCK.API | The address of your Rock instance's API. This is your Rock URL with api added to the end — the api suffix is required. |
ROCK.EVENT_REGISTRATION_URL | The address used for event registration links. Also your Rock URL with api on the end. |
Both values use your church's Rock instance URL. If your Rock URL changes (for example, after a server migration), both settings need updating.
Custom connection status for new members
When someone creates an account in your app, Apollos records them in Rock with a connection status. By default this uses a standard status, but you can choose which Rock connection status new app members receive:
| Setting | What it does |
|---|---|
ROCK.CONNECTION_STATUS_VALUE_ID | The ID of the Rock connection status to assign to people created from the app. |
To set it up:
- Find the ID of the connection status you want in Rock. This short video shows where to look: Guide to retrieving connection status ID values in Rock.
- Ask your Apollos contact to set
ROCK.CONNECTION_STATUS_VALUE_IDto that ID.
Studio C settings
Churches using Studio C can sync Studio C's custom polls into their app, alongside native Apollos polls:
| Setting | What it does |
|---|---|
STUDIOC.ENABLE_POLLS | Set to True to sync polls from Studio C into your app. |
Troubleshooting
How often does WordPress content sync?
Apollos checks your WordPress site for new and changed posts on a regular schedule. That schedule can be adjusted for your church if you publish much more or much less often than usual — ask your Apollos contact. See How data sync works.
Why didn't my configuration change take effect?
Configuration changes can take up to 5 minutes to appear in the app. Wait a few minutes and check again. If a change still isn't taking effect after that, contact Apollos support.
Why are Rock event registrations failing?
Check that ROCK.EVENT_REGISTRATION_URL ends with api — a missing api suffix is the most common cause. The same applies to ROCK.API.