What is Primary Properties?
Primary properties let you separate property access from property operations. A user can still be assigned to a property, but only users marked as part of that property's team — called primary — receive routine operational notifications and appear first in assignment lists. This reduces notification noise and makes it easier to assign work to the right people.
How it works
Enable Primary Properties
Global Admins only.
Go to Settings > Preferences.
Under Primary Properties, toggle on Enable Primary Properties.
Set primary properties for a single user
Admins and above.
Go to Settings > Account > Users.
Click a user to open their profile.
Click Update access.
Click Update primary properties.
Use the dropdown to add or remove primary properties for that user.
Click Save.
Bulk-assign primary properties
Admins and above.
Go to Settings > Account > Users.
Select multiple users.
Click Update Primary Properties at the bottom of the screen.
💡 Tip: To select a range of users quickly, click the first user, then hold Shift and click another user further down the list — every user in between will be checked too.
How primary and non-primary properties are shown
Primary properties are marked with a green badge and a flag icon.
Non-primary (regular) properties show a white badge.
How this affects work order assignment
When you assign a work order, users who have that property marked as primary appear first, grouped under the property's team header. Non-primary users can still be assigned — they just don't appear at the top by default.
Open Work Orders.
Click into a specific work order.
Click Assign to user.
Users with the property marked as primary appear under the property team header.
Notifications for non-primary users
Being non-primary doesn't cut a user off from a property — it only changes default notification routing. A non-primary user still gets notified when they're directly involved, such as when they're:
Assigned to a work order
Mentioned in a comment
Subscribed to a work order
Delegated a task
Explicitly configured to receive a specific notification
Common scenarios
An admin wants an engineer to have access to a building without including them in every routine notification for that property.
A manager wants their core on-site team to appear first when assigning new work orders, without hiding other qualified users.
A user's role shifts from full-time on a property to occasional backup access.
An admin needs to set primary properties for a large group of users at once, such as after onboarding a new team.
FAQ
Does removing primary status remove a user's access to the property?
No. Removing primary status only changes notification and assignment behavior — the user keeps their existing access to the property.
Will a non-primary user still get notified if they're assigned a work order directly?
Yes — direct involvement (assignment, mention, subscription, delegation, or explicit configuration) still triggers notifications regardless of primary status.
Can a user be primary on some properties and non-primary on others?
Yes. Primary status is set per property, so you can toggle it independently for each property a user is assigned to.
Who can turn on Primary Properties, and who can update it for users?
Global Admins can turn the feature on for the account. Admins and above can update primary properties for other users.
Can an Admin update their own primary properties?
No. Admins and above can update primary properties for other users, but not their own. Another Admin or a Global Admin needs to make that change.
Related Articles