Hello there,

Thanks for the feedback.

The link Ray provided above should now work on all Gmail accounts as long as they are linked to a database that looks like *.odoo.com.
If not, please let us know by creating a support ticket and we'll have a look.

That is indeed very unfortunate for on premise databases but is due to a limitation imposed by Google for valid security reasons (avoid malicious redirections).
See: https://developers.google.com/apps-script/manifest/allowlist-url
Basically we need to give a list of allowed URLs and prove that we own those before we can use them inside actions, meaning it is not possible for us to handle www.mycompany.com

Which is why in this case, we advise creating a copy of the script and deploying it internally from the manifest. From there, you would be able to easily modify this constraint and to get it running smoothly (Google is far less restrictive if you run an addin inside your own organization as it is if you want to publish it on the store).

Hope it helps.

@Luc

Thanks for your feedback.
I can totally understand from that point. from *.odoo.com it's easy for you to control the "source" to allow the addon to validate.

But it would be better if your documentation clearly mention this because:
A. Nowhere in the docs in any place it says the addon "out of the box" is compatible only with *.odoo.com databases (odoo.sh / odoo online)

B. the current script for self-installing does no longer work. The publish features are gone as Google is deprecating the current editor and changing to the new editor has no publishing options at all.

C. there is no simple way for us to clone/duplicate this script from that link.
If would be better if this addon was also published in perhaps a github repo and update the documentation clearly that self-hosted/on-premise setups require creating a standalone version from the script and referring to the github repo where we can clone the script.

Thanks for your understanding.

I can totally understand from that point. from *.odoo.com it's easy for you to control the "source" to allow the addon to validate.
=> Actually it's worst than that, we *have to* provide an allowlist and we *have to* own the domain of those URLs or Google would just refuse our addin as this is part of their security guidelines. So we really had no choice and there was no other way if we wanted to provide an easy install to at least some of our users.

But you are right, we're working on a doc update to explain all that because it cannot be guessed.

As for the repo that is indeed the plan, we already have one and will provide a link there so that one can easily clone it, remove the constraints and deploy it internally.

In the meantime, I'll check what I can do on the script side to at least unblock that.

I'll keep you updated :)

Luc & Ray - It seems like the issue here is the entire email architecture. It takes 5 minutes to set up email with hubstpot, vtiger, copper, ERPNext, etc. because emails are sent from the email provder itself. Y'all can't do this because you want to send out emails with those special headers so you can link it back to a specific business object. The email service providers like this, and many have trouble differentiating between that and spam. However, those headers aren't necessary if you sync everything based on what's open. So if you get an email from a customer who has an open opportunity, it'll automatically sync to the opportunity. With the very nice systems (hubspot, copper) you can optionally remove the email from the business object if you don't want it to sync.

If y'all set up your email architecture like your competitors, you can use email like a normal email. There are multiple businesses who I've recommended odoo to that decided against it specifically because of your email architecture and the limits it imposes. Odoo shouldn't be sending emails, your email service provider is should.

I know "rewrite your email architecture" is a rather large request...but is this something that's on your timeline for the future? I love Odoo and it's helped our business tremendously but the decision to link everything based on headers from the business object introduces massive limitations that makes your email system work much worse than other players in the market. Y'all are doing a ton of innovative things, but in this situation, just copying your competitor's setup would dramatically improve your product.

@robbie

Hi there,
Thanks for the feedback, that is indeed some valuable insights.

These are multiple different "dimensions" so I can't really give a definitive answer but let me try to comment that a bit based on our roadmap & intentions.

- Setting up email in Odoo is tricky
=> Indeed, we do have room for improvements there and we'd like to make it more "plug&play". However, both Outlook & Gmail changed their OAuth processes so our recent priority was to make sure it would keep working on all versions. As a side note, this means that now sending an email using an address they provide is not easy as it used to considering they do multiple extra checks to ensure the content is legit (you can't just use username/pw anymore).

- Thread structure
=> I believe this is a strong added-value so I doubt it would change "per se". That being said, that is what most competitors do too. On top of that (and we do not do that for now), they usually generate unique aliases (lead123456@mycompany.com) and put it in cc, which is why the crm record ends up being sync'd. Not really sure how we could handle it differently and not convinced by a "magical" sync considering you could have multiple different ongoing conversations with the same customer, for example.

-Anything planned regarding the mail framework
=> Yes indeed, we've been working on multiple improvements, some of which will already be available from v16, others a little later. I'll be happy to discuss that further during the Odoo Experience if you are there online or remotely :)

Hope it helps you see a bit more clearly into our plans.

The workaround is to copy the script so you become owner and than to run it at least once...Than you can install it into your Google Workspace...very user friendly and professional from Odoo...

@Pavel Sodomka, Where can we able to find script? to duplicate?