Customizing the Student Portal

The student portal is where your buyers spend their time after purchase. A polished, branded portal reinforces that they made a smart decision. A generic one erodes trust.

Accessing Portal Settings

Navigate to Memberships > Settings. This controls everything students see: the login page, course dashboard, lesson layouts, and profile options.

Branding Basics

Logo: Upload your brand logo. It appears in the top-left corner of the dashboard and on the login page. Use a horizontal version — it fits the navigation bar better than a square icon.

Colors: Set your primary brand color (hex code). This controls buttons, links, progress bars, and accent elements. Consistency matters — use the same color from your sales page and website.

Favicon: Upload a 32x32 or 64x64 PNG. The small icon in browser tabs. This detail makes the portal feel professional.

Cover image: A banner at the top of the dashboard. Recommended dimensions: 1920x400 pixels. Keep text minimal — it crops on mobile.

Custom Login Page

By default, students log in at a GHL subdomain. Change this to your own domain. Find the “Portal Domain” field and enter something like “courses.yourdomain.com” or “learn.yourdomain.com.” Add a CNAME record in your DNS settings pointing to GHL.

Customize the login page with your logo, a background image, and friendly copy. Replace “Member Login” with “Welcome back to [Course Name]” or “Your learning dashboard.”

Orientation Content

Create a “Start Here” lesson as the first module. Walk students through:

• Where to find course content
• How to mark lessons complete
• How to download resources
• Where to ask questions

This eliminates dozens of support tickets and helps students start engaging with content faster.

Mobile Testing

Open your phone’s browser. Log in with a test student account. Check:

• Does the logo display correctly?
• Can you navigate between modules?
• Do videos play?
• Can you download PDFs?
• Does the progress bar update?

Most students access courses from mobile at least part of the time. Test on both iOS Safari and Android Chrome — they handle some elements differently. Fix any issues before launch.