Partner Contacts

Contacts are the people at your partner's company — the individuals you invite to sign in to the partner portal. This article covers the full contact lifecycle: adding contacts, sending and resending portal invitations, setting a primary contact, and enabling or disabling access.

Where to find it: Go to Partners, open a partner, then open the Contacts tab.

Who can use this: Team members with the Admin or Partnerships role can add, edit and invite contacts. Only Admins can enable or disable a contact.

Contacts vs assigned users

These two tabs sit next to each other on the partner page and are often confused. They describe two completely different groups of people.

Contacts are people at the partner's company. They are the ones who receive portal invitations and sign in to your partner portal. When you invite a partner, you are inviting a contact.
Assigned users are members of your own team. Assigning them to a partner links internal owners to that relationship — it never grants portal access and never sends an invitation.

In short: add a contact when you want a person at the partner to log in to the portal. Add an assigned user when you want one of your colleagues to own or follow the partner internally.

Invite a contact

Adding a contact from the Contacts tab also sends them a portal invitation by email.

Open the partner and go to the Contacts tab.
Select Invite contact.
Fill in the contact's details. Email is always required — it is the address the person will use to sign in. Depending on your field settings, First name, Last name, Phone, and Position may also appear and may be marked required.
Optionally add contact Tags.
Select Send invite. The contact is created and an invitation email is sent immediately.

You can also add contacts while creating a partner, and you can choose to save the partner without sending invitations yet — see Creating a Partner. Contacts added without an invitation (including those brought in through CSV import) can be invited later from the Contacts tab. For the wider partner setup journey, see Partner Onboarding.

Set a primary contact

The primary contact is the partnership's main point of contact. Marking a contact as primary highlights them with a star and sorts them to the top of contact lists and pickers throughout Journeybee.

On the Contacts tab, find the contact you want to make primary.
Select the star icon next to their name.

Each partnership can have only one primary contact. Marking a new contact as primary automatically removes the primary flag from the previous one. Select the star again to unset it.

Edit a contact

You can update a contact's details at any time.

Open the Contacts tab and locate the contact.
Edit any field — name, phone, position, or tags — directly in place. Changes save automatically.

One field behaves differently: once a contact has signed in to the portal, their email becomes read-only. Their email is the identity they log in with, so it can no longer be changed here. Their phone number and other details stay editable.

Disable or remove a contact

To stop a contact from signing in, you disable them. Journeybee has no separate "delete contact" action — disabling is how you remove someone's access, and it is reversible.

Open the Contacts tab and find the contact.
Change their Status from Enabled to Disabled.

A disabled contact is moved to a separate section at the bottom of the list and can no longer sign in to the portal — the change takes effect immediately. To restore access, set their status back to Enabled. Only admins can enable or disable a contact.

Portal invitations

A contact needs an invitation before they can sign in for the first time.

When invitations are sent

When you add a contact from the Contacts tab using Send invite.
When you create a partner and choose to send invitations (see Creating a Partner).

Contacts added without an invitation show an envelope icon labelled Invite Contact. Select it to send their first invitation.

Resend an invitation

On the Contacts tab, find a contact who has already been invited but has not yet signed in.
Select the envelope icon to resend their invitation.

You can resend an invitation once per day per contact. If you have already sent one today, the button is disabled until the next day. Once a contact has signed in and linked their account, the resend option no longer appears — they can sign in directly instead.

A contact must sign in using the same email address that is on their contact record. If they use a different address, Journeybee will not recognise them as a partner.

The partner portal login offers these methods:

Continue with Google
Continue with Microsoft
Email magic link — the portal emails a one-time sign-in link.
Phone verification code — the portal texts a one-time code to the contact's phone number.

For Google, Microsoft, and magic link, the contact's email must match their contact record. For phone sign-in, their phone number must match.

You can let people from a partner company sign in without an individual invitation, as long as their email domain matches the partner's company domain. This is useful for partners with many staff, where inviting each person by hand is impractical.

There are two settings:

Per partner: open the partner and go to the Settings tab, then turn on Auto-create users on login.
Company default: go to Settings → Partner Portal Access and turn on Automatic partner user creation. This sets the default applied to new partners.

Important conditions:

It works only when partners sign in through your custom domain.
It works only for company-specific email domains. Public providers such as Gmail, Yahoo, and Outlook.com are never auto-registered.
The person's email domain must match the domain registered on the partner.

When these conditions are met, a matching person who signs in is automatically given portal access and added as a contact — no invitation needed.

Contact custom fields and tags

Custom fields

You can capture extra information on contacts using custom fields in the Contact category — for example a LinkedIn URL or a preferred language. Contact custom fields appear on each contact and can be marked required, so the field must be filled in. Set them up in Custom Fields.

Your admin can also control the standard contact fields: First name, Last name, Phone, and Position can each be hidden or marked required. Email is always shown and always required.

Where else contacts appear

Email recipients: when you email a partner, you pick recipients from that partnership's contacts. See Emailing Partners.
CSV import: you can bring contacts in when importing partners — the import supports contact email, first and last name, phone, and tags. See Importing Partners from a CSV.
Spiffs: when you set up an individual payment incentive, you can direct it to a specific contact as the recipient. See Spiffs.

Troubleshooting

A contact did not receive the invitation

Check the contact's email address on the Contacts tab for typos and confirm it is the address they expect to use.
Ask them to check their spam or junk folder.
Resend the invitation using the envelope icon. Note you can only resend once per day per contact — if you have already resent today, wait until the next day.

They must sign in with the exact email address on their contact record. Signing in with a different address, or a personal address instead of their work one, will not be recognised.
Confirm their status is Enabled — a disabled contact cannot sign in.
For phone sign-in, the number they enter must match the phone number on their contact record.

A contact should lose access

Set the contact's Status to Disabled. This blocks portal sign-in immediately. Only admins can do this.
Disabling is reversible — set the status back to Enabled to restore access. To remove the whole partner instead, see Deleting a Partner.

Good to know

Adding a contact from the Contacts tab always sends an invitation. To add someone without emailing them yet, add them during partner creation and save without inviting, then invite them later.
Each partnership can have only one primary contact.
A contact's email becomes read-only once they have signed in, because it is the identity they log in with.
Contacts are the portal identity: a person signs in as a contact, not as an assigned user. Assigned users are your internal team and never receive portal access.
There is no separate delete action for contacts — disabling a contact is how you remove their access, and it can be reversed.