Three steps and about ten minutes: add the module to your Odoo, install it, and connect it to your Pantalytics account.
Someone else manages your Odoo, such as an Odoo partner? Send them this page. They do steps 1 and 2. Step 3 is yours, because it signs in with your Pantalytics account.
Step 1: Add the module from GitHub
The code is on
GitHub,
the branch of your Odoo series: 18.0, 19.0 or 20.0 (the examples
below say 19.0; use yours). How you add it depends on where your Odoo runs: Odoo.sh,
Cloudpepper or your own server.
Odoo.sh
Start on a staging branch, not on production.
-
Open the branch, click Submodule at the top right, then Run on Odoo.sh
-
Repository URL:
git@github.com:pantalytics/pan_mail_pro.git(Odoo.sh only takes this form, nothttps://) -
Branch: pick your series (
19.0for Odoo 19) from the list. Path: leave what Odoo.sh fills in - Click Add a submodule. Odoo.sh commits it and builds the branch
Rather use the command line:
git submodule add -b 19.0 https://github.com/pantalytics/pan_mail_pro pantalytics/pan_mail_pro
git commit -m "Add Mail Pro" && git push
Cloudpepper
- Open your instance and go to the Addons tab
-
Click Add Git repository, not Add from GitHub or Upload to GitHub right beside it
-
In the Add module dialog: Git repository
https://github.com/pantalytics/pan_mail_pro, Branch: your series (18.0,19.0or20.0, the same as your Odoo version), copy method All addons (recommended). Click Add module -
The repository is now a row on the Addons tab, with Upload, Settings, Update and Delete. Click Settings on the
pan_mail_prorow, switch on Install Python requirements on update and Auto upgrade module(s) on update, then click Close
Your own server or Docker
cd /opt/odoo
git clone -b 19.0 https://github.com/pantalytics/pan_mail_pro
# odoo.conf: addons_path = ...,/opt/odoo/pan_mail_pro
Restart Odoo. Odoo's Python needs cryptography; the official odoo:19.0
image has it.
Step 2: Install it in Odoo
Apps → Update Apps List → search "Mail Pro" → Install. Installing takes a few minutes.
On a staging copy
A staging branch, or any restored copy of your database, is a copy as far as Mail Pro is concerned. Settings and the Inbox say so in one line: "This is a copy. Mail is shown, not sent."
-
Outgoing mail leaves through your copy's own mail server, never through Microsoft 365, Gmail or your mail host. On Odoo.sh it lands on the branch's Mails tab; elsewhere it lands in whatever catches the copy's mail, such as Mailpit or MailHog. Each mail shows the address it would have been sent from, and replies keep their thread.
-
Incoming mail is not read. A copy never marks mail as read or moves it in a real mailbox.
-
Connecting to Pantalytics does not work on a copy yet, so step 3 happens on production.
Step 3: Connect to Pantalytics
Settings → Mail Pro → Connect to Pantalytics. Pantalytics opens in the same tab with a code filled in: sign in, check it names this Odoo, approve. You land back in Odoo, connected. No account yet? Create one first at mcp.pantalytics.com/admin/mail-pro. Stuck? See Connect to Pantalytics.
Updating to a new release
-
Odoo.sh or git:
git submodule update --remote pantalytics/pan_mail_pro, commit, push. A submodule never moves on its own, so you decide when. -
Cloudpepper: with the two switches from step 1 on, it pulls the release and restarts by itself. If Apps → Mail Pro still shows the old version afterwards, click Upgrade there.
A release that adds fields or screens also needs Apps → Mail Pro → Upgrade. The release notes say when.