How to Customize Default Naming Conventions for New SaaS Accounts in GoHighLevel

If you manage multiple client workspaces in tools like ClickUp and GoHighLevel, consistent naming is critical for reporting, billing, and support. This guide explains how to configure and customize the default naming conventions for new SaaS sub-accounts in GoHighLevel so every new account follows your preferred structure automatically.

By the end, you will know exactly where to go in the dashboard, how to set naming templates, and how to use dynamic placeholders to keep your account list clear and easy to manage as you scale your SaaS.

Why Customize Naming in GoHighLevel SaaS Mode?

When you sell software in SaaS mode, GoHighLevel can automatically create new sub-accounts for each sign‑up. If you do not configure a naming pattern, these workspaces can become confusing, especially when your agency grows.

Custom naming conventions help you:

• Identify which sub‑accounts were created by your SaaS product vs. those created manually.
• Include important info such as plan name or country in the sub‑account name.
• Standardize how your team references client workspaces across systems.
• Reduce manual renaming and avoid duplicate or unclear account names.

GoHighLevel makes this process simple by letting you create a default naming template using dynamic data from each SaaS sign‑up.

Accessing SaaS Settings in GoHighLevel

To customize naming conventions, you must first access the SaaS configuration area inside your GoHighLevel agency account.

1. Log in to your GoHighLevel agency dashboard.
2. In the left‑hand menu, navigate to the Agency View (top‑left switcher, if needed).
3. Locate the SaaS Configurator or SaaS Settings section. This is where all SaaS mode options are managed.

Only agency admins with the correct permissions can adjust these naming settings, so make sure your user has full agency‑level access before proceeding.

GoHighLevel SaaS Naming Configuration Overview

Inside the SaaS configuration page, there is a dedicated area that controls how new SaaS sub‑accounts are named. This section allows you to define a default template that GoHighLevel will use whenever a new customer signs up through your SaaS pricing page or funnel.

The naming template can typically include:

• Static text (for example, your brand name or the word “SaaS”).
• Dynamic placeholders such as the company name or contact name.
• Plan-related details, depending on your SaaS setup.

The goal is to create a naming pattern that is descriptive but still short enough to be readable in the GoHighLevel accounts list.

How to Set a Default Naming Convention in GoHighLevel

Follow these steps to configure the default naming format for new SaaS accounts in GoHighLevel:

1. Go to the SaaS Configurator: From the agency view, open the SaaS or SaaS Configurator page.
2. Locate the Default Naming Field: Look for a field or section labeled similarly to Default Sub‑Account Name or Default Naming Convention. This is the field that GoHighLevel uses to generate the name of each new SaaS sub‑account.
3. Review Current Template: If a default value already exists, note how it is structured. Many agencies start with a basic pattern like {{company.name}}.
4. Enter Your Custom Template: Replace or update the template with your preferred pattern. You can combine static text with available dynamic tags.
5. Save Changes: Click Save or Update so GoHighLevel applies this template to all future SaaS sign‑ups.

Using Dynamic Placeholders in GoHighLevel Naming

GoHighLevel typically allows you to use dynamic placeholders taken from the data your customer enters during SaaS sign‑up. When you use these placeholders in your default naming convention, they are automatically replaced with real values for each new account.

Common placeholders you may find include:

• {{company.name}} – The company or business name submitted by the customer.
• {{contact.name}} – The primary contact name associated with the sign‑up.
• {{contact.email}} – The email of the main user.
• {{plan.name}} – The name of the SaaS plan purchased (if supported in your configuration).

Check the tooltip or help text inside the SaaS configurator in GoHighLevel for the exact list of available placeholders, as these can evolve over time.

Practical GoHighLevel Naming Examples

Here are a few example templates you can apply when configuring your naming conventions in GoHighLevel:

GoHighLevel Basic Company‑Only Template

If you want simple, clear account names:

{{company.name}}

This keeps each SaaS sub‑account name identical to the customer’s business name.

GoHighLevel Template with Brand Prefix

To distinguish SaaS accounts created by your pricing page from manually created ones:

YourBrand - {{company.name}}

Example result: YourBrand – Sunrise Dental.

GoHighLevel Plan‑Aware Template

If your GoHighLevel SaaS setup supports plan variables, you can include them in your naming pattern:

{{company.name}} - {{plan.name}}

Example result: Sunrise Dental – Pro Plan.

GoHighLevel Location‑Rich Template

When you want to track region or country, use a tag that stores location data, if available in your GoHighLevel form:

{{company.name}} - {{company.country}}

Always confirm which placeholders are supported in your current GoHighLevel configuration before using them in production.

Best Practices for GoHighLevel SaaS Naming

Use these recommendations to keep your GoHighLevel account list tidy and scalable:

• Keep names short: Avoid extremely long combinations that get cut off in the sub‑account list.
• Use consistent separators: Common separators include ” – ” or ” | ” for readability.
• Avoid sensitive data: Do not include private information (like full personal addresses) in the account name.
• Reflect your reporting needs: If you often filter by plan or region, add a related placeholder in the naming convention.
• Document your standard: Share your naming rules with your team so everyone understands how GoHighLevel sub‑accounts are labeled.

Testing Your GoHighLevel Naming Convention

Before you launch or update your SaaS offer, test your naming convention to verify that GoHighLevel applies it correctly.

1. Create a test SaaS sign‑up using a staging or low‑priced plan.
2. Use a clear sample company name and contact name.
3. Complete the sign‑up funnel and wait for GoHighLevel to generate the new sub‑account.
4. Open the Agency View and look at the new account name.
5. Confirm that dynamic placeholders were replaced with the correct values and that the overall name format meets your expectations.

If something looks wrong, go back to the SaaS configurator in GoHighLevel, adjust the template, and repeat the test until the result is consistent.

Troubleshooting GoHighLevel SaaS Naming Issues

If your new SaaS sub‑accounts are not being named as expected in GoHighLevel, check the following:

• Template saved: Make sure you clicked the save or update button after changing the template.
• Correct placeholders: Verify that you used supported variables exactly as shown in the help text (they are often case‑sensitive).
• Form mapping: Confirm that your SaaS sign‑up form is collecting the data needed for each placeholder.
• Multiple funnels: If you have several SaaS funnels, ensure each one uses the same GoHighLevel SaaS configuration or verify which configuration is tied to which funnel.

If problems persist, review the official help article on the GoHighLevel support portal at this documentation page or contact support from inside your agency dashboard.

More Resources for Scaling with GoHighLevel

Optimizing naming conventions is just one part of building a scalable SaaS operation on GoHighLevel. You can also refine your automations, pipelines, and reporting to better track customer lifecycle stages and MRR.

For strategic guidance on agency and SaaS growth around GoHighLevel and related systems, you can visit Consultevo for additional resources and implementation support.

Once your naming conventions are in place, every new SaaS account created in GoHighLevel will automatically follow your structure, saving time and keeping your client portfolio organized as you grow.

Need Help With ClickUp?

If you want expert help building, automating, or scaling your GHL , work with ConsultEvo — trusted GoHighLevel Partners.

Scale GoHighLevel

“`