Goal

Instead of creating every account by hand, let new users sign themselves up — with an email and password, their Apple ID, or their Google account. Offer just one method or all three at once. By the end, your login screen will show exactly the signup buttons you want, Google login will be wired up, and email validation will be on if you want it.

All of these options live together on the Login button’s settings, in the Login Settings group — they’re all describing the same screen. A common setup: allow email signup and Apple/Google together, then require email validation just for the email path.

Before you begin

• You are signed in to WordPress as an administrator.
• Your app has a Login button placed in its navigation. These settings live on that button, so they won’t appear until you’ve added one — check your app’s navigation for a Login item in the main tab bar or the left menu if you’re not sure.
• For Google signup only: a Google Cloud project with OAuth credentials, so you can copy a client ID. You can turn on the other methods first and come back to this.

These settings are global — they apply to every user role, not per role.

Steps

1. Open the Login button’s settings

In the MAM dashboard, open your app’s settings and select the Login button (or the Login Settings group). All of the options below appear there together.

If there is no Login button to configure, add one to your app’s navigation first, then return here.

2. Allow email signup

Find Allow user to sign up with Email and turn it on.

This adds a Sign up with Email option to the login screen, so new users can create an account with just an address and password. Leave it off only if you want everyone coming in through Apple/Google (or pre-issued codes) instead.

3. Allow Apple and Google signup

Find Allow user to sign up with Apple and Google and turn it on.

One toggle, two buttons: turning this on puts both Sign in with Apple and Sign in with Google on the login screen, so users can sign in with an identity they already have instead of a new email and password. Apple and Google are a package deal here — there’s no way to show just one of the two from this setting.

Leave a way in. If you turn email signup off in Step 2, make sure this option (or another sign-in method) is on, or new users will have no way to create an account.

4. Wire up the Google Login API client ID

Apple signup works as soon as the toggle in Step 3 is on. Google needs one more value — without it, the Google button appears on the screen but the sign-in won’t complete.

1. In the Google Cloud Console, open your project’s OAuth credentials and copy the client ID.
2. Back in the Login settings, paste it into the Google Login API field.

Apple does not require a value in this field.

5. Require email validation (optional)

If you turned on email signup, you can require new users to confirm their email address before the account becomes active.

Find Require email validation during account setup and turn it on.

Turning this on catches fake or mistyped email addresses before they can create an account — it costs one extra step, but it’s worth it. Here’s how it works: anyone who signs up with email is sent a validation code and must confirm it before continuing, and their account stays marked unverified until they do. Apple and Google identities are already verified by their provider, so those users skip this step entirely.

6. Save and test on a device

Save your settings, then open the app in the previewer or on a test device and confirm the login screen shows the right buttons:

• Each method you enabled has its own button (Sign up with Email, Sign in with Apple, Sign in with Google).
• The Google button completes a real sign-in, not just appears — this is the fastest way to confirm your client ID is correct.
• If you required email validation, a fresh email signup prompts for the emailed code before logging you in.

Always test Google by actually signing in. A missing or wrong client ID shows up only when the button is tapped, not when the screen loads.

Notes and gotchas

• All global. Every option here applies to all user roles. There is no per-role signup configuration on this screen.
• One toggle for two providers. Apple and Google are enabled together. There is no separate switch to show Google without Apple, or vice versa.
• The Google button can appear without working. Enabling Apple/Google shows the Google button, but it needs the Google Login API client ID to authenticate. Test it, don’t just look at it.
• Email validation only covers email signups. Apple and Google users are verified by their provider and won’t see the code step.

Related

• Choose how users sign in: email validation, Google, or sign-up codes — the broader version of this task, including pre-issued enrollment/sign-up codes.
• Brand your login screen: logo, colors, background — style the same screen once signup is configured.
• App Setting Reference: sign_up_with_email, sign_up_with_google, sign_up_with_email_validation, login_google_client_id, require_login.

What’s next

With signup sorted, it’s time to make that screen look like yours — background color or image, a logo up top, button colors, and your Terms and Conditions message and link, all in the same Login Settings group. Handing out membership or enrollment codes too? Choose how users sign in covers the code-gated signup field.