Keeping your Primary Contact role up-to-date is an important part of being a Bluetooth SIG member, as there are many tasks and responsibilities related to your membership that only a Primary Contact can do.

Who can be a Primary Contact?

Anyone in your company who has an active user account on Bluetooth.com can be the Primary Contact. Your Primary Contact should be someone who is able to manage your company’s Bluetooth membership and keep your account information up-to-date.

If the person you want to be assigned the role of Primary Contact does not have a Bluetooth.com user account, have them set up a new user account before re-assigning the role. To set up a new user account, go to the User Account Application.

How to re-assign the Primary Contact role if my current Primary Contact is still with my company

To re-assign the role you will need to submit a Support Request. Before you do this, make sure that the person you are re-assigning the role to already has a Bluetooth.com user account.

If your current Primary Contact has an active user account, we will require their confirmation to re-assign the role before this update can be made. 

If you are re-assigning the role to someone other than you, we may ask the other person to consent to the role before finalizing the re-assignment.

How to re-assign the Primary Contact role if my current Primary Contact has left my company

If your current Primary Contact is no longer with your company, and if their Bluetooth.com user account has been deactivated, you may be able to re-assign the role on your own by following these steps:

1. Go to welcome.bluetooth.com and navigate to the “My Membership” page.
2. You should see an alert with instructions on how to re-assign the Primary Contact role to yourself. If you don’t see an alert, this means that your current Primary Contact’s user account is still active in our system and you will need to submit a support request to re-assign the role. We may reach out to other users on the account or require documentation to validate the change request.

KB0010262