Contract Preferences are a collection of questions and terms that prefill fields when documents are drafted on a deal. Every agent has their own set under Manage Profile; on a Jointly Business account, an administrator can also set Contract Preferences at team level, so the whole team drafts from standard, compliant values.
Who can set team Contract Preferences?
Jointly Business account administrators. Individual agents set their own preferences under Manage Profile instead — see Contract Preferences.
How do I set team Contract Preferences?
Go to the Team icon in the left bar.
Select Contract Preferences.
Pick a Contract Preference category from the left panel.
Each category shows a list of questions or fields. Select a field and enter your value.
Save each category before moving to the next one.
If your organization has more than one team in Jointly, select the correct team from the team drop-down before you start configuring.
Which preferences win, the team's or the agent's?
For most preferences, the agent's own Contract Preferences are what pull into a deal. So if you change a setting at team level and your agents do not see the change, their individual preferences still need updating too.
There is one important exception. On the four documents below, the team's preference now takes priority for brokerage, broker and supervisor details. The agent's own value is used only as a fallback — when the team's field is blank, or when the agent is not part of a partnership:
Document | Details taken from the team's Contract Preferences |
IABS | Brokerage name, license number, email and phone; broker name, license number, email and phone; supervisor name, license number, email and phone |
Commission Request, CDA and Invoice | Brokerage name, brokerage address and brokerage phone |
Wire Fraud Warning | Brokerage name |
General Information and Notice to Consumers | Brokerage name |
This does not change where the agent's own details come from: an agent's name, license number, email and phone always come from their own account, never from the team.
Can I stop agents from changing a preference?
For the application (screening) fee, yes — team preferences include an option that prevents agents from updating it. Without that option switched on, an amount an agent has set in their own Contract Preferences is what pulls into the deal, not the team's.
Can I update an agent's preferences for them?
Yes. In the Team section, click the agent's icon and choose Manage Preferences.
When do preference changes reach existing deals?
A Contract Preference change is only picked up where the deal has not already saved that value:
If the agent already saved the step that stores the value on the deal — a brokerage address, for example — deleting and re-adding the task brings back the value stored on the deal, not your new preference.
If the task was added but never filled in and saved, deleting and re-adding it pulls in the latest Contract Preferences.
Documents already signed with the old information have to be re-signed once the information is corrected.
The same applies when an agent moves brokerages. Removing an agent from the old brokerage or team only affects deals created afterwards — existing deals stay attached to the brokerage they were created under, so the new brokerage information appears only on newer deals.
Which settings can only be changed at team level?
Some things an agent cannot change on their own profile are controlled in the team's Contract Preferences:
The Prepare for Your Move task — switch it off here, not on the agent's profile.
The emails clients receive from the third-party vendors Jointly works with for moving services.
Compliance and CDA preferences.
Concierge and vendor referrals are also configured here. Where a brokerage has them set to go out automatically, clients are contacted first, and whether a per-client consent task is presented depends on how it is set up in the team settings; any referral email the agent receives is informational. Opting out of automatic referrals altogether is a brokerage-level decision rather than a Jointly setting, so an agent who wants that has to raise it with their brokerage.
Why should an agent only be on one team?
An agent who sits on two teams pulls from two different sets of preferences, which causes problems with templates, default documents and contract preferences. Adding an agent who still belongs to another team should return an error. If an agent has ended up on a second team, that team's admin should remove them.
If a preference is not pulling into your deals the way you expect after checking the above, reply in the chat with the deal and the field and we will take a look.