Connection and API keys

Open Settings in the builder header, then the Connection tab. This is where the app’s link to your site lives, and where you see which optional services are configured.

The WordPress connection

The panel shows which user the app is connected as, and the version of the Memberside plugin answering on your site.

To change the site, rotate the application password, or reconnect after revoking one, connect again from here. See Connect your WordPress site.

If the plugin cannot be found, this panel says so and links to the plugin’s own admin screen, at /wp-admin/admin.php?page=memberside-keys on your site.

Where API keys actually live

Keys are stored on your site, not in Memberside

Push credentials, Turnstile secrets and Maps keys are held by the Memberside plugin on your own WordPress install, under Memberside → API Keys. The builder reads only whether each one is present. The values never reach Memberside’s servers and are never returned by the API.

This is why the Connection tab shows availability rather than fields to paste secrets into. A secret you can read back from a hosted builder is a secret you have to trust the builder with.

Set them in WordPress under Memberside → API Keys. Each can also be defined as a PHP constant in wp-config.php, which takes precedence over the stored value — useful when your keys belong in deployment configuration rather than in a database.

What you can configure

Key	Used for
Turnstile site key and secret key	Cloudflare Turnstile on Default Login and Default Register
Firebase service account	Push notifications
Firebase server key	Push notifications, the legacy method
OneSignal App ID and REST API key	Push notifications through OneSignal
Google Maps API key	Location fields and static maps on profiles

The site key half of a Turnstile pair is public and is compiled into your app. The secret key never leaves your server — it is used by your site to verify a challenge, and it is never included in a build.

Push notifications

Push needs either a Firebase service account or a OneSignal pair, configured on your site. The Connection tab reports which it found.

Push cannot be tested in the preview. It only exists in a compiled app on a real device.

When it does not work

Symptom	Cause	Fix
The connection panel says the plugin was not found	The plugin is inactive, or the site URL is wrong	Install the plugin
A key you set is reported as absent	It was saved empty, or saved on a different site	Re-enter it under Memberside → API Keys
A key set in wp-config.php seems ignored	A constant overrides the stored value, not the reverse	Check the constant’s spelling; it wins when defined
Turnstile passes in preview but fails in the app	The secret key is missing on the site	The site verifies the challenge, so it needs the secret half

Next

The launcher screen.