Nimble AMS Event Colleague Registration Scope Explained

Do not index

Learnings

A tricky request we see from associations running Nimble AMS goes something like this:

"Our members are saying they can't register their coworkers for our annual conference. But they're logged in and everything looks fine. What's going on?"

The answer lies in one of those areas where Nimble AMS's default behavior is technically correct but practically surprising. The "Register a Colleague" feature in Community Hub doesn't mean what most people think it means.

What "Colleague" Actually Means Out of the Box

When a logged-in member clicks Register a Colleague on the Manage Registrations page, Nimble AMS doesn't show every active child affiliation for the parent organization; it only shows people who consider that organization to be their PRIMARY affiliation.

For a small association where most members have a single parent affiliation, this works fine. But for associations with complex affiliation structures, your registrants may not find who they expect.

Tricky Documentation

On top of that, Nimble's help documentation, at least as of Spring ‘26, states that "a user without a primary affiliation can also register a colleague." Sounds great, right? Except out of the box, that's not actually true.

This description on Nimble’s help site about colleague registration isn’t accurate.

Per the “Register a Colleague” logic, if an individual has no primary affiliation, they have no colleagues, full stop. The colleague list comes back empty. The button might as well not be there.

This is the kind of disconnect that burns hours if you don't know to look for it. Staff sees the feature in the UI, assumes it works broadly, and then gets hit with confused member emails when registration opens.

Common Scenarios Where This Breaks Down

We've seen this cause issues across a range of use cases:

Associations where the definition of "colleague" should include all child affiliations for the parent organization, not just those marked as Primary Affiliation = TRUE.

Multi-chapter organizations where a member belongs to a national entity and a regional entity, with their primary affiliation set to the latter. They can't register national-level colleagues.

Organizations that want open registration where any logged-in member should be able to register anyone in the system. The default scope is far too narrow for this.

The Fix Exists — But It's Not a Setting

Nimble AMS does provide a mechanism to redefine what "colleague" means: the Custom Colleague Locator. It's not a point-and-click configuration, however; it requires Apex development.

The idea is straightforward: you write a custom class that returns whatever list of person accounts you want the member to see. The scope is entirely up to you.

What makes this tricky isn't the concept — it's getting the query right. You need to understand how Nimble AMS structures affiliations, which junction objects are in play, and how to handle edge cases like inactive affiliations or unaffiliated folks. Get the SOQL wrong and you'll either show too many people (privacy concern) or too few (back to square one).

Why This Matters More Than It Seems

Event registration is often one of the highest-traffic areas for an association's Community Hub, especially around big events. It's when lapsed members log in for the first time in months, when executive assistants are trying to get their teams signed up, and when your staff is already stretched thin handling logistics.

A broken colleague registration flow at this moment doesn't just create support tickets — it undermines trust in the platform. Members start emailing registration links to colleagues manually. Staff may begin questioning whether the AMS migration was worth it.

The good news: once the colleague scope is properly configured, it's a set-it-and-forget-it fix. We've implemented this for multiple associations and it's one of those changes where the ROI is immediately obvious — support tickets drop, self-service adoption goes up, and staff can focus on the event itself rather than manual registration workarounds.

What to Do About It

If your members are running into this issue, here's the short version: it's not a bug, it's a default that doesn't match your business rules. The platform supports a broader definition of "colleague" — it just needs to be told what yours is.

We help associations diagnose and fix this exact issue regularly. If you're gearing up for a conference and want to make sure your registration flow actually works the way your members expect, reach out to us. We can pinpoint the right scope and get it implemented before your next event opens.

What "Colleague" Actually Means in Nimble AMS Event Registration