Skip to main content

Admin: Authentication

Use Admin > Authentication when your app needs visitor accounts, sign in, signup, protected pages, or Google login.

Authentication is useful for apps such as:

  • member portals
  • customer dashboards
  • course websites
  • booking systems
  • internal tools
  • private apps
  • apps with saved user information

If your app is only a public brochure website, you may not need authentication.

What Authentication Controls​

The Authentication section can control:

  • whether login is enabled
  • whether email and password login is enabled
  • whether Google login is enabled
  • whether Google uses CloudMySite managed OAuth or your own Google credentials
  • which domains are allowed
  • preview and published redirect settings

Step 1: Open Authentication​

  1. Open your Genie app.
  2. Select Admin.
  3. Open Authentication.

You will see switches and settings for login methods.

Step 2: Choose Login Methods​

Email + Password​

Turn on Email + Password if visitors should create an account with an email address and password.

This is a good option for most apps because it is familiar to users.

Google Login​

Turn on Enable Google login if visitors should be able to sign in with their Google account.

Google login can make signup faster because visitors do not need to create a separate password.

Google Login Options​

If Google login is enabled, you may see two setup choices.

Use CloudMySite Managed OAuth​

This option uses CloudMySite's managed Google login service.

It is usually the easiest option for nontechnical users because the published app does not need to store your Google Client ID or Client Secret.

Use this when you want the simplest Google login setup.

Use My Own Google OAuth Credentials​

This option uses your own Google Cloud OAuth app.

Use this if:

  • your organization requires its own Google OAuth app
  • you need full control over Google branding and verification
  • you already have a Google Cloud project for the app
  • you are testing Google login in preview with your own credentials

This setup requires values from Google Cloud:

  • Google Client ID
  • Google Client Secret

Keep the Client Secret private.

Preview Callback URI​

The Preview Callback URI is used for testing Google login before publishing.

If you use your own Google OAuth credentials, copy the preview callback URI and add it to your Google Cloud OAuth app as an authorized redirect URI.

Use this only for preview testing. The published app uses its own production redirect URI.

Allowed Domains​

Allowed domains control which domains are approved for authentication.

Use this when your app should only accept login from specific domains.

Examples:

  • yourdomain.com
  • app.yourdomain.com
  • members.yourdomain.com

If you are unsure, keep this simple and add only the domain where the app will be published.

Step 3: Save Authentication Settings​

After choosing your settings:

  1. Review the enabled login methods.
  2. Check Google settings if Google login is enabled.
  3. Select Save Authentication Settings.
  4. Wait for the success message.

Saving may update files in your app so the login screens and routes work correctly.

Step 4: Test Login​

Test the login flow before launch.

For email and password:

  1. Open preview.
  2. Go to the login or signup page.
  3. Create a test account.
  4. Sign out.
  5. Sign in again.

For Google login:

  1. Save Authentication settings.
  2. Select Test Google Login.
  3. Complete the Google login flow.
  4. Confirm the app returns to the correct page.

If Google rejects the redirect URI during preview testing, copy the Preview Callback URI and add it in Google Cloud.

Step 5: Publish and Test Again​

After preview testing works:

  1. Publish the app.
  2. Open the live published URL.
  3. Test signup.
  4. Test login.
  5. Test logout.
  6. Test Google login if enabled.

Production login is best tested on the published domain.

When to Ask Genie to Add Login Pages​

If your app does not have login or account pages, ask Genie to add them.

Prompt examples:

Add login, signup, and account pages to this app.
Add member-only dashboard pages and require login before visitors can view them.
Add a sign in button to the header and an account page after login.

After Genie adds the pages, return to Admin > Authentication and save the settings.

Best Practices​

  • Turn on only the login methods you need.
  • Test every login method before launch.
  • Use Google managed OAuth unless you specifically need your own Google Cloud setup.
  • Keep Google Client Secrets private.
  • Add login links where visitors can find them.
  • Add logout and account links for signed-in users.
  • Test on the live domain after publishing.

Troubleshooting​

Google Login Says Redirect URI Is Invalid​

If using your own Google OAuth credentials, add the preview or production redirect URI to your Google Cloud OAuth app.

For preview testing, use the Preview Callback URI shown in Admin.

For published testing, use the published app redirect URI.

Google Login Works in Preview but Not Live​

Check that the production redirect URI is added in Google Cloud if you use custom credentials. Also confirm the app has been published after saving Authentication settings.

I Do Not See a Login Page​

Ask Genie to add login and signup pages, then save Authentication settings again.

Email Login Does Not Work​

Confirm Email + Password is turned on and the app was published after saving settings.

I Accidentally Turned On Login​

Return to Admin > Authentication, turn off the login methods you do not want, save settings, and publish again.