Sub-Account Settings in HighLevel

Updated: February 6, 2026  | 
Author: Bill Stilwell

This post covers the key Settings sections in a HighLevel sub-account, what each section configures, and what features each section enables – including the recommended order for completing Settings when setting up a new account.

Reading time: about 6 minutes.

What Is Sub-Account Settings in HighLevel?

Sub-Account Settings is the configuration center for an individual HighLevel sub-account. It contains every setting that determines how the sub-account operates – the business information it carries, the platforms it connects to, the phone numbers it uses, the email infrastructure it sends through, the team members who have access, and the data structures it uses for contacts and tags.

Most HighLevel features depend on Settings being configured correctly before they will work. Reputation management requires Integrations to have a Google Business Profile connected.

Email campaigns require Email Services to have a sending domain set up. SMS automation requires Phone Numbers to have an LC Phone number provisioned.

Settings is the foundation everything else builds on.

Access it via the gear icon in the bottom left navigation of the sub-account.

Business Info

Business Info is the first Settings section to complete. It stores the fundamental details about the business: the business name, phone number, email address, physical address, time zone, and logo.

This information is not just administrative – it is used throughout the platform. The time zone setting affects when scheduled automations fire relative to the contact’s local time.

The business name appears in email footers and platform communications. The logo appears wherever branding is displayed.

Accurate Business Info is the foundation of a correctly operating sub-account.

The address entered in Business Info also serves as the physical address for CAN-SPAM compliance in email footers. If the sub-account sends bulk emails, this address must be accurate and current – it is a legal requirement in commercial email.

Integrations

The Integrations section connects the sub-account to external platforms. The most impactful integrations for most businesses: Google Business Profile (enables reputation management, GBP posts, GBP messaging), Facebook (enables Facebook Messenger, Lead Ads, and social posting), Stripe (enables payment processing), and Gmail or Google Workspace (enables the connected email account for individual Conversations Inbox replies).

Each integration is connected via OAuth or API key. After connecting, verify the integration shows the correct account name – particularly important for client sub-accounts, where the client’s accounts (not the agency’s personal accounts) must be connected.

An agency accidentally connecting their own Facebook Page to a client’s sub-account is a common setup mistake that the connection verification step catches.

Phone Numbers

The Phone Numbers section is where LC Phone numbers are provisioned for the sub-account. Add a phone number, select the number type (local 10-digit, toll-free), choose the area code, and provision.

The number is immediately active for SMS and calls.

For US sub-accounts sending SMS at any volume, A2P 10DLC registration must be completed. The registration process is initiated from within the Phone Numbers section – brand registration first, then campaign registration.

A2P registration takes several business days to approve; initiating it during initial setup ensures it is approved before SMS campaigns go live.

Email Services

The Email Services section configures the email sending infrastructure. Add the sending domain, generate the SPF, DKIM, and DMARC DNS records, add those records to the domain registrar, and verify them in HighLevel.

Once verified, the sub-account can send authenticated bulk emails through the configured domain.

The From name and From address are also configured here – how the business appears in the From field of emails it sends. A recognizable From name (the business name or a specific person’s name) improves email open rates.

The From address should be on the authenticated sending domain for deliverability alignment.

Team Members

The Team Members section (sometimes labeled My Staff) manages user access to the sub-account. Add team members by entering their name and email address and assigning a role.

Available roles typically include admin (full access), user (standard access), and potentially more specific roles depending on the HighLevel configuration.

Each team member added receives an invitation email to set up their account access. Once set up, they appear as available assignees for tasks, calls, conversations, and calendars throughout the sub-account.

Team member configuration is what enables HighLevel’s multi-user features – conversations can be assigned to specific team members, calendars can be assigned to specific staff, and tasks route to the right person.

Custom Values

Custom Values stores the sub-account-level text variables – the business name, phone number, address, booking link, website URL, and any other recurring text that appears across templates. Creating Custom Values during initial setup means all templates and workflows in the sub-account can reference the values by variable rather than hard-coding the text.

For snapshot-based onboarding, Custom Values are especially important – they are what make the snapshot’s generic templates instantly specific to the new client. Import the snapshot, update the Custom Values, and every template in the account reflects the correct client information automatically.

Custom Fields

Custom Fields defines the additional data fields available on contact records beyond the defaults (first name, last name, email, phone, etc.). Create custom fields for any contact-level data the business needs to track – industry, company size, lead source, service interest, preferred contact time, or any other variable that is relevant to the business’s CRM needs.

Custom Fields integrate with forms (form fields map to contact custom fields), workflows (custom field values can be used in conditions and personalizations), and Smart Lists (filter contacts by custom field values). Define the custom fields that the business needs before building forms and workflows – adding a field after a form is already deployed requires updating the form to include the new field mapping.

Tags

The Tags section shows the sub-account’s tag library and allows creating, renaming, and deleting tags. Creating the standard tag set during initial Settings configuration ensures consistent tagging from the first contact that enters the sub-account.

The tag library in Settings is the reference for the entire tag architecture. Tags created here are available for selection in contact records, workflow actions, and Smart List filters.

A well-maintained tag library – with consistent naming and no redundant tags – is the foundation of effective contact segmentation and automation.

Notifications

The Notifications section configures which events trigger alerts for team members – new inbound messages, new contact created, appointment booked, missed call, and other significant events. Notifications can be delivered via email, SMS to the team member’s phone, or push notifications on the HighLevel Mobile App.

Properly configured notifications ensure the team responds quickly to high-priority events. A new lead submitted a form – the assigned team member should know immediately.

A new appointment was booked – the relevant calendar owner should be notified. Configuring notifications during setup rather than after go-live means the team is alerted from day one rather than discovering that notifications were not set up when they miss an important event.

Other Settings Sections

Beyond the core sections, sub-account Settings contains additional configuration areas: Calendars (calendar creation and configuration), Pipeline Stages (sales and service pipeline definitions), Custom Domains (connecting custom domains to funnels and websites), Compliance Settings (consent language and GDPR configurations), Conversation AI (AI agent configuration), and more. Each section configures a specific aspect of the sub-account’s operation.

Not every section is required for every business type – configure the sections relevant to the features being used.

Recommended Setup Order

When configuring a new sub-account, completing Settings sections in a logical order prevents dependencies from causing delays. The recommended order: Business Info first (sets the foundation), then Integrations (connects external platforms), then Phone Numbers (provisions communication infrastructure), then Email Services (sets up email sending), then Team Members (adds the people who use the account), then Custom Values (enters the business-specific text variables), then Custom Fields (defines the contact data structure), then Tags (creates the tagging taxonomy), then Notifications (configures the team alert system), and finally feature-specific settings like Calendars and Pipelines.

This order ensures that each subsequent step has the prerequisite configuration in place. Adding team members before the phone numbers are provisioned means the team cannot use the phone features.

Setting up Custom Values before entering Business Info leaves the values empty. The sequence matters for a smooth setup.

What Can You Do With It?

• Configure every aspect of how a sub-account operates from one central location: Settings is the single configuration hub – business identity, external connections, communication infrastructure, team access, and data structures all defined in one place.
• Enable features that require prerequisite configuration: Reputation management, email campaigns, SMS automation, and many other features only work when the corresponding Settings sections are correctly configured. Getting Settings right unlocks the platform’s full capability.
• Standardize sub-account setup across multiple clients with a configuration checklist: Agencies with a documented Settings setup checklist ensure every client sub-account has consistent configuration – reducing “why isn’t this working” support questions caused by missed setup steps.
• Manage team access and roles across the sub-account: Team Members in Settings controls who can access what within the sub-account – ensuring the right people have the right access level for their responsibilities.

Key Definitions

Who Is This For?

How to Configure a New Sub-Account

Step 1: Business Info

Settings, then Business Info. Enter business name, phone, email, address, time zone.

Upload the logo.

Step 2: Integrations

Settings, then Integrations. Connect Google Business Profile, Facebook Page, Stripe, and Gmail/Google Workspace via OAuth.

Verify each shows the correct account name.

Step 3: Phone Numbers

Settings, then Phone Numbers. Add a local number.

Begin A2P 10DLC brand and campaign registration for US accounts.

Step 4: Email Services

Settings, then Email Services. Add the sending domain.

Add SPF, DKIM, DMARC records to the domain registrar. Verify all records in HighLevel.

Step 5: Team Members

Settings, then Team Members. Add each team member with name, email, and role.

They receive an invitation email.

Step 6: Custom Values

Settings, then Custom Values. Create variables for business name, phone, address, booking link, website URL.

Step 7: Custom Fields

Settings, then Custom Fields. Create any additional contact fields needed for this business type.

Step 8: Tags

Settings, then Tags. Create the standard tag set with the established naming convention.

Step 9: Notifications

Settings, then Notifications. Configure alerts for new lead, new message, appointment booked, and other key events for the team.

How Does It Connect to HighLevel?

• LC Phone: LC Phone is configured in Settings, then Phone Numbers. Every SMS and call feature in HighLevel depends on having a provisioned LC Phone number in Settings.
• LC Email: LC Email is configured in Settings, then Email Services. Every bulk email and automated workflow email depends on the sending domain being correctly set up in Settings.
• Integrations: The Integrations section within Settings is where all external platform connections are managed. Every feature that depends on an external integration – reputation management, payment processing, social publishing – requires the corresponding integration to be connected in Settings.
• Custom Values: Custom Values configured in Settings power the reusable text variable system used across email templates, SMS messages, funnel pages, and workflow content.
• Tags: The Tags library managed in Settings is the source for the tag options available in workflows, Smart Lists, and contact records throughout the sub-account.

Common Questions

What is in the Sub-Account Settings in HighLevel?

Business Info, Integrations, Phone Numbers, Email Services, Team Members, Custom Values, Custom Fields, Tags, Notifications, Calendars, and more. Every configuration that determines how the sub-account operates.

Where do I find Settings in a HighLevel sub-account?

Gear icon in the bottom of the left navigation. Opens the Settings section with a navigation menu for all available configuration categories.

What should I configure in Settings when setting up a new HighLevel sub-account?

In order: Business Info, Integrations, Phone Numbers (with A2P registration), Email Services (with DNS records), Team Members, Custom Values, Custom Fields, Tags, and Notifications. Then feature-specific settings like Calendars and Pipelines.

What is Business Info in HighLevel Settings?

The section storing the business’s name, phone, email, address, time zone, and logo. Used throughout the platform and required for CAN-SPAM email compliance (the physical address field).

How do I add team members to a HighLevel sub-account?

Settings, then Team Members. Add name, email, and role.

The team member receives an invitation email to set up their account access.

To Wrap It Up

Settings is the part of HighLevel that most users spend the least time in after initial setup – and that is exactly right. A well-configured Settings section operates in the background, enabling every other feature without requiring ongoing attention.

The goal of a thorough initial Settings configuration is to not need to think about Settings again except for periodic maintenance (reconnecting expired integrations, adding new team members, updating phone numbers).

The problems that send users back to Settings repeatedly are almost always the result of an incomplete initial setup. The reputation dashboard shows no reviews – the GBP integration was not connected.

Email campaigns land in spam – the sending domain was not authenticated. SMS automations fail – A2P registration was never completed.

Each of these is a Settings problem, and each is preventable with a thorough setup checklist.

For agencies, a Settings configuration checklist is one of the highest-value process documents to create and maintain. A checklist that covers every required Settings section, with verification criteria for each, ensures every client sub-account is fully functional from day one.

The five minutes per sub-account spent working through a checklist prevents the hours of troubleshooting that incomplete setups generate later.

1. Navigate to Settings via the gear icon in the bottom left navigation
2. Complete Business Info – name, address, time zone, logo
3. Connect Integrations – Google GBP, Facebook, Stripe, Gmail
4. Provision a Phone Number and begin A2P registration
5. Configure Email Services with the sending domain and DNS records
6. Add Team Members with appropriate roles
7. Create Custom Values for recurring business information
8. Create Custom Fields for additional contact data points
9. Build the tag library with the designed naming convention
10. Configure Notifications for the team’s key alert events

Build an agency Settings configuration checklist and version-control it. HighLevel adds new Settings sections and options as the platform develops.

A checklist that was accurate six months ago may be missing new required sections today. Reviewing and updating the checklist quarterly ensures the setup process stays current with the platform’s capabilities – and every new client sub-account benefits from the most complete setup the current HighLevel version supports.