Association Limits in Sparkforge CRM

By Sparkforge Support Team ·Last reviewed May 3, 2026

Association limits cap how many records can be linked between objects in Sparkforge CRM. The UI enforces limits in real time so users can't over-link contacts, custom objects, or labels.

Association limits control how many records can be linked between objects in Sparkforge CRM. They keep your data structure clean, prevent over-linking, and surface clear UI feedback when a cap is reached.

Supported Relationship Types

Multi-Label Associations

  • One-to-One (1:1)
  • One-to-N (where N is up to 1000)
  • One-to-Many
  • Many-to-Many

Single-Label Contact-to-Contact

  • One-to-One (1:1)
  • Many-to-Many
  • Custom N-to-N

Limits are enforced per label and reflected directly in the UI.

How to Set Up Association Limits

  1. Open your sub-account and go to Settings > Objects.
  2. Select a custom object or Contacts.
  3. Open the Associations tab and click Create Association (or edit an existing one).
  4. Choose a single label or a label pair.
  5. Under Configure Relationship, pick the type (1:1, 1:N, etc.) and set the limit.
  6. Use the Preview section to confirm the constraints, then save.

Example: Real Estate Agency

An agency wants each Agent to manage no more than 50 Properties:

  • Create a one-to-N association from Agent to Property
  • Set N = 50

When an agent hits 50 linked properties, the UI blocks additional assignments and shows a warning.

What Users See

If a user attempts to associate beyond the configured count, an inline error message appears immediately. This keeps data structures predictable without requiring admins to police usage manually.

Frequently Asked Questions

What's the maximum value for N in a one-to-N association?
Up to 1,000 records per parent record.
Are limits enforced retroactively?
No. Existing associations above the new limit remain in place. The cap applies to new association attempts going forward.
Can I set different limits per label?
Yes. Limits are configured and enforced per label, so the same object pair can have different rules for different relationship labels.
Where do users see the error?
An inline UI message appears when an association attempt exceeds the configured limit.
Do association limits apply to imports?
Yes. Bulk imports respect the configured limits and report rejected rows.

Was this article helpful?