Customize SaaS Sub-Account Naming in GoHighLevel — Save Time

Managing dozens—or even hundreds—of client accounts in GoHighLevel can quickly become chaotic if you don't have a naming system in place. Every new sub-account that gets created with a generic or inconsistent name makes it harder to find clients, organize your workspace, and onboard new team members. That's where the SaaS Configurator naming feature comes in. By customizing how sub-accounts are named from day one, you can eliminate post-onboarding edits, maintain clarity across your entire platform, and save your team countless hours of administrative work.

In this guide, I'll walk you through exactly how to set up and leverage default sub-account naming conventions in GoHighLevel—so your agency runs like a machine, not a filing cabinet. And if you haven't tried GoHighLevel yet, start your FREE 30-day trial here (that's double the standard trial) to see how this feature works in your own account.

What Is SaaS Sub-Account Naming & Why It Matters

Before GoHighLevel introduced customizable naming conventions, every new SaaS sub-account defaulted to a generic format: "Customer Name's Account." While functional, this approach lacked flexibility. If you manage 50 clients, searching through dozens of identically-formatted accounts becomes tedious. Teams waste time manually renaming accounts after creation, inconsistencies creep in, and onboarding new staff becomes confusing.

The SaaS Configurator's naming feature solves this by letting you define how accounts are labeled at the moment of creation. Instead of a reactive, manual process, naming becomes proactive and standardized. You choose whether accounts are labeled by customer name, company business name, or a combination—and every new sub-account respects that standard automatically.

This small change has massive ripple effects: faster account discovery, cleaner dashboards, fewer naming conflicts, and a more professional workspace that scales with your agency growth.

How to Access the SaaS Configurator

The SaaS Configurator lives in your main GoHighLevel agency account (not in a sub-account). Here's how to find it:

1. Log into your GoHighLevel account — make sure you're in your primary agency account, not a sub-account.
2. Navigate to Settings — look for the settings gear icon in your left sidebar.
3. Find "SaaS Configurator" — scroll through settings until you locate the SaaS Configurator section. It's typically grouped with other account setup options.
4. Look for "Default Sub-Account Names" — this is the specific setting that controls how new sub-accounts are named.

Once you're in the SaaS Configurator, you'll see the naming configuration options. This is where the magic happens.

Choosing Between Customer Name vs. Company Name

The SaaS Configurator gives you two primary naming options—and the choice depends on your agency's structure and how you manage client relationships.

Option 1: Customer Name

Naming by customer name works best if you work directly with individual decision-makers or if one person owns the relationship with your agency. The account displays as "[Customer First & Last Name]'s Account." This approach is personal and great for agencies focused on individual consultants, freelancers, or solopreneurs. It makes it immediately clear who the contact is when you glance at your account list.

Option 2: Company Name

Naming by company business name is ideal for agencies managing corporate clients, local businesses, or enterprises. The account displays as "[Company Business Name]." This approach keeps your workspace more professional and formal, making it easier to organize accounts by business entity rather than by contact person. If a client changes points of contact, the account name stays consistent.

Which Should You Choose?

If you work with a mix of both individual and company clients, consider your dominant client type. Most agencies find that company name works better at scale—it's easier to reference in meetings ("Let's review the XYZ Corp account") and creates a clearer paper trail for billing and contracts. However, if relationship management is your core business, customer name might feel more natural.

This is built into GoHighLevel. Try it free for 30 days →

Step-by-Step Setup Instructions

Now let's configure your naming convention. Follow these steps:

1. Open SaaS Configurator Settings — Navigate to Settings > SaaS Configurator > Default Sub-Account Names as outlined earlier.
2. Select Your Naming Format — You'll see radio buttons or a dropdown menu. Choose either "Customer Name" or "Company Name" (or whatever exact labels GoHighLevel displays in your version).
3. Review the Preview — GoHighLevel typically shows you a preview of how new accounts will be labeled. Read this carefully to make sure the format matches your expectations.
4. Save Your Changes — Click the save button. This setting applies to all new sub-accounts created going forward—it does not rename existing accounts retroactively.
5. Test with a New Sub-Account — Create a test sub-account to verify the naming convention is working as expected. This confirms your settings took effect before you onboard real clients.

The entire setup takes about 2 minutes. The real time savings emerge once you've created 10, 20, or 50 accounts—you'll never again manually rename sub-accounts to keep them organized.

External Checkout Requirements & Best Practices

If you're using GoHighLevel's external checkout feature to let clients sign up directly for your services, there's an important consideration: the naming convention also applies when clients self-onboard.

When a client creates an account through an external checkout link, GoHighLevel automatically creates a sub-account and names it according to your configured default. Make sure your naming choice makes sense from a client onboarding perspective too. For example, if a client doesn't provide their business name during signup, the system needs something to work with.

Best Practice Recommendations:

• If using external checkout, ensure your signup form captures the information you need for your chosen naming format (customer name or company name).
• Make the relevant field required—don't let clients skip it—so naming happens automatically without errors.
• Test your external checkout flow with the naming convention enabled to catch any issues before client signups begin.
• Document your naming standard in internal team docs so everyone understands the system.

Real-World Benefits & Time Savings

Let's quantify the impact. Imagine you manage 100 client accounts. Without a naming standard, here's what happens:

• New accounts come in with inconsistent names (some say "John Smith's Account," others say "Smith, John," others say "JS Company").
• A team member spends 2-3 minutes per account manually renaming for consistency. That's 200–300 minutes (5+ hours) of wasted labor.
• Searching for client accounts becomes slow and error-prone. A new team member takes days to learn the naming system.
• Billing and reporting become harder when account names don't match client names in your contracts or invoices.

With configured naming conventions, every account is named correctly from day one. Teams spend less time on administrative busywork and more time serving clients. And scaling to 200 or 500 accounts doesn't add chaos—the system keeps everything tidy automatically.

Beyond time savings, there's a professional impact: clients see an organized agency that runs like a machine. Internal team morale improves when systems actually work as designed. And onboarding new staff becomes faster because naming logic is clear and enforced by the platform itself.