help! Added contacts to companies not working... subdomain issues

New hubtstotter here…

We have a bunch of companies added to our account.

Trying to add contacts to them. however its giving me a error msg every time.

I figured out why, its because the email domain doesn’t match the company url.

This is a big issue, as almost all our clients have a main domain, with many subdomains depending on their division/location/etc…

How do I disable this feature, so we can add whatever email we want under the company? I tried unchecking the “Create and associate Companies with contacts”, but it didn’t do anything.

For example:

Company ABC COMPANY

Domain abc-company.com

Contact email is JOHNDOE@EAST.ABC-COMPANY.COM

Is this a bug, or ???

thanks!

Hi @VT75,

Can you please share a screenshot of the error you’re seeing?

Are you a super admin or were you invited by an admin to your portal? There is a dedicated permission for associating records - you might be missing that.

Best regards

sure thing, yes im super admin.

I have this unchecked, so it should let me put whateveer email domain I want for contacts under a company…

@VT75 thank you - what exactly did you click before the red error appeared?

Sure, simply fill in the box, and when I click “CREATE” button it gives the msg. doesnt’ save.

it only works if the email domain matches the company domain. (which is rare)

@VT75 I’d be very surprised if there was an actual connection to the company name - as you’re not entering that at the same time.

Can you confirm you’re using a supported browser? Browsers supported by HubSpot

Habe you tried after clearing cache/cookies and disabling all browser extensions?

Do you have permissions to view all contacts in the CRM?

Are you entering data in correct case, e.g. lower case email address?

Thanks for reply, yes i checked browser support, tried in booth chrome and MS.

OMG. You are genius. I have email set to UPPER CASE only as a rule. When I removed that, it works fine. (even though email was upper case?!) so I assume this is a bug of sort.

Anyways, works now. Thank you so much!