Your login screen ships with sensible default wording, but off-the-shelf labels rarely
sound like your brand — and if your app collects accounts, you’ll likely need a Terms and
Conditions line at sign-up too. A small group of text settings covers all of it: the login
and sign-up buttons, the code-entry field, and a Terms and Conditions message that links to
your own terms page. Here’s where each one lives and what it does.

This article covers the text on the login screen. To change the colors, logo, and
background, see Brand your login screen: logo, colors, and background.

Goal

By the end, your login screen’s Login, Sign Up, and Send Code buttons will read
the way you want. The sign-up code field will show helpful placeholder and reminder text,
and a Terms and Conditions line will display your wording and open your hosted terms page
when tapped.

Prerequisites

• An admin account on the WordPress site that powers your app.
• A Login Button already added to your app (in the tab bar or the left menu). If you
  have not added one yet, see Add a login button and turn on in-app accounts.
• For the Terms and Conditions step: a public URL for your hosted terms page.

Keep in mind: all of the settings below are global — they apply to every user role,
with no per-role variation of this wording.

Where these settings live

You’ll find every control below in one place: the Login Settings group on the
Login Button content type. In the Mobile App Manager, open App Setup, edit your
Login Button, and open Login Settings — that’s where each field named in this article
lives.

Leave a field blank and the app falls back to its built-in default wording for that
element — you only need to fill in the ones you actually want to change.

Steps

1. Rename the action buttons

Three text fields control what your login screen’s buttons say:

• Login Button Title — the primary sign-in button (e.g. “Sign In”, “Log In”, or
  “Member Login”).
• Signup Button Title — the create-account button (e.g. “Create Account”, “Join”, or
  “Register”).
• Send Code Button Title — the button that emails the sign-up / verification code to
  the user, used in code-based or passwordless sign-up (e.g. “Send Code” or
  “Email My Code”). This button only matters if your app uses email-code sign-up or
  verification.

Keep the wording short — long titles are the first thing to get clipped on smaller phones.

2. Guide the sign-up code field

If your app sends a verification code at sign-up (see Let users sign up with email,
Apple, and Google), two text fields help make that step clearer for users:

• Sign Up Code Placeholder — the faint placeholder text shown inside the code field
  before the user types (e.g. “Enter your 6-digit code”). It disappears once they start
  typing.
• Sign Up Code Reminder — short helper text shown near the code field (e.g.
  “Check your email for the code we just sent”). It helps users who don’t immediately spot
  the code they were sent.

If your app doesn’t use email-code sign-up or verification, leave both blank and move on.

3. Set the Terms and Conditions message

Two fields work together here to add a Terms and Conditions acceptance line to your
sign-up screen:

• Terms and Conditions Message — the visible wording of the acceptance line (e.g.
  “By signing up you agree to our Terms & Conditions”). Leave it blank and no Terms line is
  shown.
• Terms and Conditions URL — the page that opens when a user taps the Terms link.
  Point this at your hosted terms page.

Fill in both together — the Message is the wording your users see, and the URL is
where that wording links to. Set the message alone and there’s nothing to link to; set the
URL alone and there’s no visible line for anyone to tap.

Compliance note: Apple and Google both expect apps that collect accounts to surface
terms / privacy information at sign-up, and filling in these two fields is a quick way to
meet that expectation. Confirm the exact wording and the linked page with whoever owns
your legal copy.

4. Save and preview

Save your settings, then open the app (or your preview build) and head to the login and
sign-up screens to check that:

• The Login, Sign Up, and (if used) Send Code buttons show your wording and
  the text isn’t clipped on a small phone.
• The sign-up code field shows your placeholder, and the reminder text reads clearly.
• The Terms and Conditions line appears at sign-up, and tapping it opens the correct page.

If anything’s off, adjust the wording and save again.

Tips

• Blank means default. Leave a field empty and it falls back to the app’s built-in
  wording — you never have to touch a field you’re happy leaving alone.
• Keep button labels short. Long titles wrap or get clipped on smaller devices, so
  preview on a real phone rather than trusting the desktop manager alone.
• Test the Terms link on a device. A typo in the URL is easy to miss in the manager but
  obvious the moment a user taps the link and lands on the wrong page.
• Wording and color are separate. If your renamed buttons or Terms link are hard to
  read, that’s a color problem — adjust Button Text Color and Links text color in
  Brand your login screen: logo, colors, and background.

Related

• Brand your login screen: logo, colors, and background — colors, logo, and background.
• Add a login button and turn on in-app accounts — adds the Login Button these settings
  live on.
• Let users sign up with email, Apple, and Google — sets up the code-based sign-up the
  code field text supports.
• App setting: Login Button Title (login_login_button_title)
• App setting: Signup Button Title (login_signup_button_title)
• App setting: Send Code Button Title (login_send_code_button_title)
• App setting: Sign Up Code Placeholder (login_sign_up_code_placeholder)
• App setting: Sign Up Code Reminder (login_sign_up_code_reminder)
• App setting: Terms and Conditions Message (login_terms_and_conditions_text)
• App setting: Terms and Conditions URL (login_terms_and_conditions_url)

What’s next

With the login screen’s wording and terms in place, finish the first-run experience by
shaping what new users see right after they sign in — see
Customize the onboarding flow new users see.