Home/HighLevel/Features/CRM/Configuring association limits in HighLevel custom objects

CRM and Pipelines

Configuring association limits in HighLevel custom objects

In short

Association limits let you specify the maximum number of records that can be linked between two objects in HighLevel. By setting limits per association label, you prevent excessive linking, keep the data model tidy, and give users immediate UI alerts when they try to exceed the defined thresholds.

AreaCRM · Associations
Used forReal estate agency, Marketing firm, Consulting practice
Setup steps9 steps in 1 task
Last updatedNovember 17, 2026

01Who this is for

  • Founders of SaaS startups, need clean relationship data to avoid confusing client connections.
  • Real estate agency owners, want to cap the number of properties any agent can manage.

02Association limits, explained

Association limits are rules that define how many records may be connected between two objects. They are set per association label and are enforced directly in the HighLevel user interface. When the defined maximum is reached, the platform right away shows an error message, preventing further linking.

The limits apply to several relationship types. For multi label associations you can choose one to one, one to N (where N is up to 1000), one to many, N to M (N up to 1000) or many to many. For single label contact to contact links you can use one to one, many to many or a custom N to N.

All configuration options are located in the Settings area under Objects. Within a custom object or Contacts record you access the Associations tab to create or edit an association, select its type, and define any applicable limits.

03How businesses use association limits

  • Real estate agency. Create a one to N association from Agent to Property, set the limit to 50, and let agents assign properties until the UI warning stops further additions.
  • Marketing firm. Define a many to many relationship between Campaign and Lead, set a limit of 1,000 connections per label, and rely on the instant error message when a campaign exceeds the cap.
  • Consulting practice. Establish a one to one link between Consultant and Client record, enforce the rule so each client can only be paired with a single consultant, and see the UI prevent duplicate assignments.

04The numbers and rules that matter

  • One to N (where N ≤ 1000).
  • N to Many (where N ≤ 1000).
  • Limit example: N = 50 for agents to properties.
  • Limits are enforced per label and reflected in the user interface.

05How to set up and use association limits in HighLevel

Set up association limits for a custom object or contacts

  1. Open the desired subaccount and go to Settings > Objects.
  2. Select the target Custom Object or Contacts and click the three dot menu, then choose Edit.
  3. Navigate to the Associations tab within the edit screen.
  4. Press Create Association or select an existing association to modify.
  5. Pick either a single label or a pair of labels for the association.
  6. In the Configure Relationship section, choose the relationship type and enter a limit value when the type supports it.
  7. Review the settings in the Preview area to ensure constraints are correct.
  8. Save the changes; the new association limits appear in the Associations tab.
  9. When a limit is exceeded, the UI shows an instant error message and prevents further linking.

06What it looks like in HighLevel

07Settings that matter

  • Configure Relationship. Determines the type of link (e.g., 1:1, 1:N) and lets you specify a maximum count when the selected type allows a limit.
  • Limits. Sets the numeric ceiling for how many records can be associated under the chosen relationship type.

08Things to know before you rely on it

  • Multi label one to N and N to M relationships can have a maximum of 1,000 linked records.
  • Limits are enforced for each label separately and appear as UI warnings when exceeded.
  • Single label contact to contact associations support one to one, many to many, and custom N to N types.

09How it connects to the rest of HighLevel

Michael's take

Michael Reimer
Michael ReimerFounder of CRM Pros, HighLevel Commander and Certified Admin

Association limits feel like a modest convenience that can turn messy data into tidy, reliable relationships. For a business that depends on consistent linking. Like a real estate office tracking which agents handle which properties. This feature removes the guesswork and keeps everyone on the same page.

If I were setting it up, I’d start with the agent to property limit so no one gets overloaded. I’d preview the constraint first, then roll it out and watch the UI warning keep the assignments honest.

Get More InformationOpens on HighLevelPublished November 2, 2026 · Updated November 17, 2026

Common questions

Common questions about association limits.

What relationship types can have association limits?

Multi label links support one to one, one to N (N up to 1,000), one to many, N to M (N up to 1,000) and many to many. Single label contact to contact links allow one to one, many to many and custom N to N.

How does HighLevel inform users when an association limit is reached?

The platform shows an instant error message in the user interface, preventing any further linking for that association.

Can I set a limit higher than 1,000 records?

Limits above 1,000 are not supported for the one to N and N to M relationship types; the maximum allowed is 1,000.

Do association limits apply to single label contact to contact relationships?

Yes. For single label contact to contact links you can enforce one to one, many to many, or a custom N to N limit.

Next step

Pick the features that matter. Then get the plan that unlocks them.

Explore the features you want, start with the five at the top, and upgrade through my link when you are ready. The bonuses and the team come with it.

The features directory explains every HighLevel feature in plain English. Browse it to see what the platform can do.

Back to the FeaturesSee the full details
⌃

Site preview

Explore the next page

This destination is reserved in the page inventory and is not built yet.