Goal

Make signing in mandatory. Turn Require Login? on, and the login screen becomes the first thing users see — they’ll have to sign in or create an account before they can reach any content. Along the way, you’ll also point the Terms & Conditions link on the signup screen at your hosted legal page.

By default, a MAM app opens straight into its content and signing in is optional — users only log in when they want something account-gated, like favorites, orders, or their profile. This how-to flips that: once you’re done, the app is closed to anonymous users entirely.

Only want some features behind a login — say, open browsing but gated ordering? You don’t need this article. Leave Require Login? off and let users sign in on demand.

Prerequisites

• A MAM app with MAM Main active.
• Admin access to Mobile App Manager in WordPress.
• A Login button already added to your app. The login settings in this article live on the Login button’s settings, so the app needs one. If you don’t have one yet, add a button and choose the Login Button content type first. (See Recipe: Add a button.)
• At least one sign-up method you intend to allow — email, or Apple/Google social login. If users can’t create an account, gating the app behind login locks everyone out.
• A hosted Terms & Conditions web page with a public URL, if you want to link to your legal terms (recommended, and often required by the app stores when you collect accounts).

Steps

1. Open the Login button’s settings

Every setting in this how-to lives on your Login button, so that’s where you’ll start. In WordPress, go to Mobile App Manager and open the screen that contains your Login button, then edit that button to reach its settings — the login options are grouped under the Login Settings tab.

Heads up: everything below is global. These settings apply across your whole app and every user role, not just to this one button or screen.

2. Turn on “Require Login?”

In Login Settings, set Require Login? to Yes — this is the switch that closes the app to anonymous users.

With it on, the login screen becomes the app’s front door: users land there on launch and can’t reach any content until they’ve signed in or created an account. With it off (the default), the app opens straight to its content and login stays optional.

Don’t strand your users. Once Require Login? is on, the login screen is the only way in — so before you publish, make sure at least one sign-up method (Step 3) is enabled and working. Skip that, and anonymous users hit a wall they can’t get past.

3. Enable at least one way to sign up

Decide how new users create an account, and enable the matching option in Login Settings:

• Allow user to sign up with Email — shows the Sign up with Email option so users can register with an email address and password.
• Allow user to sign up with Apple and Google — shows the Sign in with Apple and Sign in with Google buttons. Google sign-in also requires the Google Login API client ID to be filled in on the same tab.

You can turn on both. Keep in mind that if you only offer social login, the app stores generally still expect Sign in with Apple to be available alongside Google.

Optionally, set Require email validation during account setup to Yes so new users have to verify their email address (via a code) before the account activates — it blocks fake or mistyped addresses, at the cost of one extra step for everyone signing up.

4. Wire up the Terms & Conditions link

Still in Login Settings, fill in the two Terms & Conditions fields:

• Terms and Conditions Message — the wording of the acceptance line shown on the signup screen, for example “By signing up you agree to our Terms & Conditions.” This is the visible text.
• Terms and Conditions URL — the web address opened when a user taps that link. Point it at your hosted terms page (for example, a page on your own WordPress site).

Think of the two fields as a pair: Message is what the user reads, URL is where the link takes them. Fill in the message but leave the URL blank, and the link has nowhere to send anyone.

5. Save, rebuild, and test

Save the button settings, then refresh or rebuild the app preview so it picks up the new login configuration. Now test the full path on a device or simulator:

1. Launch the app fresh — you should land on the login screen, with no content reachable behind it.
2. Confirm the sign-up method(s) you enabled in Step 3 appear.
3. On the signup screen, confirm the Terms & Conditions line shows your wording and that tapping it opens your hosted terms page.
4. Create a test account (and complete email validation if you enabled it), then confirm you reach the app’s content.

Verify it worked

• A brand-new user, with the app launched for the first time, cannot see any content until they sign in or register.
• The signup screen offers the account-creation method(s) you turned on.
• The Terms & Conditions line reads the way you wrote it, and its link opens your legal page.

If anonymous users can still reach content, re-check that Require Login? is set to Yes and that the app was rebuilt or refreshed after saving.

Related

• App setting: Require Login?
• App setting: Allow user to sign up with Email
• App setting: Allow user to sign up with Apple and Google
• App setting: Require email validation during account setup
• App setting: Terms and Conditions Message
• App setting: Terms and Conditions URL
• App setting: Google Login API
• Content class: Login button
• Recipe: Add a button

What’s next

• Style the login screen to match your brand — background color and image, top logo, link and button colors, and the login/signup button titles are all in Login Settings. See the login app-setting reference for each option.
• Set up a Logout button so signed-in users can sign out. See Content class: Logout button.