Filtered User Properties
What it is
Admins can now limit which users appear as options in default user properties, like Company Owner, so only users from specific teams show up as choices instead of every user in the portal.
Why it matters
Before this, every property that let you pick a user pulled from the entire portal roster. On a large team, that turns a simple field into a scroll-and-search exercise, and it's easy to pick the wrong person by mistake. Filtering the list to the team that actually owns that property makes the dropdown usable again.
The Take
Any admin who has watched someone pick the wrong Company Owner out of a fifty-person dropdown knows exactly what this fixes.
This is a small update, but it's the kind of small that adds up. Any admin who has watched someone assign the wrong Company Owner because they picked the third name that looked right in a fifty-person dropdown knows exactly what this fixes. It's not exciting, it's just correct — the same way filtering a picklist to your own pipeline stages is correct.
If you're running default user properties like Company Owner and your portal has grown past the size where everyone knows everyone, this is worth setting up this week. It's low-risk, it's reversible, and it removes a genuine source of bad data entry.
FAQ
What properties does this apply to?
Default user properties that let you assign a user, like Company Owner — you can now limit the options to a specific team instead of showing every user in the portal.
Do I need to do anything to get this?
It's live now, on all hubs and tiers. Check your user-property settings to scope the dropdown to the right team.
Is this worth setting up this week?
Yes, if your portal has grown large enough that picking the wrong person from a property dropdown is a real risk. It's a low-effort, low-risk fix.
Produced by Value-First Media