Require WordPress login

The [mga_chat_app] surface can require visitors to be signed in to WordPress before they can interact with the chat. When enabled, logged-out visitors see a polished sign-in card instead of the chat surface. This is independent of the server-side bot password — both can coexist.

Turn it on

1. Open the customizer for the bot you want to protect. (Bot workspace → pick a bot.)

2. Click Chat app sections → Behavior.

3. Scroll to Authentication & gating and flip Require WordPress login on.

4. Customize the sign-in copy (default: “You need to be logged in to be able to interact with this assistant.”) and optionally a Sign-in redirect URL — visitors get a button that takes them there. If empty, WordPress’s default login URL is used.

5. Click Save changes.

What the toggle looks like in the customizer

M

MyGPT Assistantsfor WordPress

Chat app sections

BrandingComposerBehavior

←

Chat App Customizer

Soporte CCreators — Behavior

🔒

Authentication & gating

Require a WordPress login before visitors can interact with this chat.

Require WordPress loginWhen on, logged-out visitors see the sign-in prompt below instead of the chat surface.

🔒

This bot also has a server-side password set on the MGA platform. The WordPress login gate is independent — it controls who reaches the chat surface, but the password is enforced by the API itself. Manage bot password →

Sign-in prompt text

You need to be logged in to be able to interact with this assistant.

Shown to logged-out visitors when WordPress login is required.Sign-in redirect URL

https://example.com/login

If set, a button takes the visitor here. Otherwise WordPress’s default login is used.

Allow guests to view the welcome screenVisitors can see suggested prompts before signing in.

What a logged-out visitor sees

When a visitor without a WordPress session lands on the page, the [mga_chat_app] shortcode renders the sign-in card instead of the chat surface. Once they sign in, the chat loads normally.

🔒

You need to be logged in to be able to interact with this assistant.

Sign in →

Per-embed override

You can flip the gate on/off per embed without touching the customizer by passing require_wp_login="true" (or "false") directly on the shortcode:

[mga_chat_app public_id="a8d3-…-f72c" require_wp_login="true"]

Bot password vs WordPress login

These two are independent gates. Bot password (set on the MGA platform) is enforced by the chat API itself. Require WordPress login is enforced by the WordPress plugin — it never lets the React surface render at all for logged-out visitors. Use the bot password for cross-channel protection (the same bot embedded outside WordPress is also locked), and Require WordPress login when you want to limit a WordPress page to your members area.

Legacy behavior

If a bot was already gated by the server-side password before you upgraded to v1.2.10+, the WP-login gate stays on automatically until you open the customizer once and explicitly toggle Require WordPress login to your preferred value. After your first save, the toggle in the customizer is the canonical source.