Public product notes for the hosted Odoo MCP gateway: governance, connectors, and console updates.
Changelog — ERPipe hosted beta
Product updates
— Approve Odoo buttons from your AI, a second check on automatic actions, and clearer setup
Your AI can now ask to run Odoo buttons such as confirming an order, posting an invoice or validating a transfer. A person approves each one first, and it runs only if the records have not changed since. Only connections you granted write access can run them.
Actions you allow to run automatically now get a second check from JEV. For the first weeks it only records whether a call looked unusual; later, unusual calls will wait for your approval. If the check is unavailable, your actions keep running as before.
Approvers get one reminder when half the approval time has passed, with the same change details as the first email. Requests that touch accounting or stock now stay open for an hour.
Connection setup now tells you when the database name is wrong, when the address is not an Odoo server, or when ERPipe could not reach your Odoo at all, and only accepts language codes that Odoo understands.
When Odoo answers an action with a confirmation dialog, for example cancelling an order on Odoo 16 to 18, your AI is now told the step still needs finishing in Odoo instead of reporting it done.
Deleting a connection or replacing its Odoo or Cloudflare Access credentials no longer shows a "connection changed" error after the change was already saved.
Approval and reminder emails name the Odoo button, for example "Confirm sales order".
New guide: which Odoo editions and plans can connect AI through MCP. Our privacy notice and subprocessor list describe the new check.
— Stronger field privacy, approval isolation, and sign-in protection
Field restrictions now apply consistently across record searches, totals, and sorting so hidden fields stay private.
Telegram approval bots stay isolated to their own workspace, and you can link the same Telegram account across multiple workspaces.
Connection consent screens clearly show the requesting app and redirect address before you approve access.
Incorrect sign-in code attempts no longer cancel active sign-in links in your email, and workspace deletion removes all linked sign-in and notification records.
— Fewer repeated connection alert emails
When an Odoo server keeps going offline and coming back, you now get at most one outage email and one recovery email per connection each day, instead of an email every time it changes.
If a connection goes offline soon after an earlier alert and stays offline, you are emailed once a day has passed since that alert.
— Safer sign-in and client connections
Sign-in and approval pages have stronger protection against being embedded by other sites.
Repeated client connection attempts are limited to protect service availability. If you reach the limit, wait before trying again.
Invalid sign-in details now return a clear error instead of an unexpected failure.
— Choose exactly which Odoo instances each client can access
Choose the Odoo instances an AI client may use when connecting. Other instances, including ones added later, stay outside that connection.
Only workspace owners can manage Odoo connections, and approved changes must be validated again after connection credentials or the database change.
Reconnect existing AI clients to select their permitted instances and start a new session.
— Fresh approval checks before changes run
Changes run only while the saved approval remains valid for the person requesting the change.
When an older approval can no longer be used, you can validate the change again and request a new owner review.
— Stronger protections for sign-in and connection secrets
Connection signing secrets are visible only to workspace owners, and social sign-in finishes in the browser where it started.
Sign-in code attempts stay limited even when requests arrive at the same time. Sign-in pauses safely if the limit cannot be checked.
Approved changes re-check field restrictions and current Odoo fields before running. Restricted fields stay hidden when reading a single record.
After signing in, redirects stay within ERPipe. Dashboard requests are limited to approved sites.
— Clearer help correcting search filters
Invalid search filters now explain how to correct the input before trying again.
Filter descriptions include a ready-to-use example, while existing valid filters continue to work.
— Practical Odoo 20 integration guides
Follow a read-first ChatGPT or Claude setup, plan the main integration migration decisions, and qualify company access, approved changes and PDFs.
The Odoo 20 Community gateway is deployed and passed an authenticated production read and document smoke against the pinned test installation. Customer deployments and other editions still need separate checks.
— Odoo 20 Community connections
Connect Odoo 20 Community for record reads, leave dates, files and approved changes. Compatibility is verified with a pinned Community test installation; other editions and custom modules need separate checks.
The optional Odoo 20 Bridge supports approved Sales confirmation and quotation PDF downloads with document and company permissions. Downloads that would change data are refused.
Older Odoo connections preserve numeric-looking text and XML characters, and record downloads avoid fetching inaccessible extra fields. Other editions and custom modules need separate checks.
File download restrictions cover both older and newer Odoo file formats. Self-hosted PDF downloads respect those restrictions too.
— New guides to Odoo 20 AI and native connections
Explore what changed in Odoo 20 AI, how its native connection works, and when an external gateway may fit your workflow.
The guides include setup examples, practical comparisons and clear version limits, with links to Odoo's official documentation.
— A practical guide to Jev and Odoo MCP
Read how Jev helps ERPipe find Odoo models and prioritize saved troubleshooting notes, while existing permissions continue to apply.
The guide explains the integration, failure handling, dated pilot results and limits, with Odoo 20 context and links to provider documentation.
— Discovery and saved-note ranking across hosted workspaces
All hosted workspaces can now use the pilot to find relevant Odoo information and prioritize relevant saved troubleshooting notes.
When the optional service is unavailable, requests use ordinary results. Repeated interruptions temporarily pause the service and notify operators by email.
The privacy notice and provider list explain the query, model labels and saved-note excerpts processed by TypeSafe AI.
— Optional discovery and saved-note ranking are now active
Participating workspaces can now use the pilot to find relevant Odoo information when ordinary discovery finds no match, and to prioritize relevant saved troubleshooting notes.
The pilot continues to respect workspace permissions and falls back to ordinary results when it cannot make a reliable decision.
— Clearer setup guides and analytics choices
Public pages agree on available tools and explain when owner approval applies to a change.
Japanese visitors can choose analytics in Japanese, with shorter notices that leave more room on small screens.
Opening a dialog no longer interrupts typing when you have already selected a field.
Workspace sign-in records available source labels and respects your analytics choice when using saved attribution. With analytics allowed, public visits can be measured separately from workspace activity.
— Optional help finding Odoo information and past fixes
An optional pilot is being prepared to recognize common Vietnamese requests and help find relevant Odoo information when ordinary discovery finds no match.
Once activated for participating workspaces, the pilot can also prioritize relevant saved troubleshooting notes. Existing permissions and approval steps continue to apply.
Saved troubleshooting notes from paused or removed connections no longer appear in recall.
— More reliable activity history
Activity history keeps recording when an approval is handled across different agent sessions.
Delayed activity no longer makes a completed or declined approval appear to be waiting again.
Activity history stays responsive as your workspace grows.
— Connect and recover Odoo behind Cloudflare Access
Connect protected Odoo instances with a Cloudflare Access service token, directly from connection settings.
If both your Odoo login and Access token change, replace them together. A failed check keeps your previous settings intact.
Follow the new setup and troubleshooting guide, with clearer connection settings on small screens.
— Recover protected Odoo connections when credentials change
When your Odoo login and Cloudflare Access token both change, you can replace them together from the existing connection's Configure page. Both are checked before anything is saved.
A failed check keeps the previous settings intact. Paused connections stay paused and Odoo write permissions remain unchanged.
Connection troubleshooting keeps saved credentials hidden, and replacing an Odoo credential can recover an unreadable previous value.
— Cloudflare Access setup help and clearer mobile connections
A new setup guide explains how to connect protected Odoo with a service token, verify a read and troubleshoot login redirects or denied requests.
Connection settings link directly to the guide and reference documentation in a new tab, keeping the form you are working on open.
The mobile Connections table keeps its accessibility labels inside the scrollable table. The workspace URL card also fits small phone screens without expanding the page sideways.
— Connect Odoo protected by Cloudflare Access
You can add a Cloudflare Access service token while connecting Odoo or from an existing connection's Configure page. Your Odoo login stays separate.
Workspace owners can replace the token without re-entering the Odoo password. ERPipe checks the new token before saving it.
Removing a token checks that Odoo can still be reached first. If that check fails, the saved token stays in place and the page explains what to check.
Saved Access credentials are hidden. Pausing tools or changing Odoo write permissions continues to work independently of the service token.
— Clearer Odoo connection choices and more reliable public pages
Japanese page titles, descriptions and reading links now stay consistent when you open a page or move around the site.
Guides stay readable while the interactive page loads. A failed page download offers a reload option instead of hiding the available content.
The updated comparison distinguishes hosted Odoo services, native Odoo connections and self-hosted options, including the differences between a free beta and a free trial.
Japanese explanations clarify when human approval is required and which controls depend on your workspace settings.
Optional analytics now distinguishes visits from AI assistants and preserves filtered campaign labels without sending private link queries. Your analytics choice still controls whether Google Analytics loads.
— Public pages now share one content width
The homepage, guides, integration docs, and legal pages now line up on the same outer column as the header, so the layout no longer jumps when you move between them.
— Japanese site end to end, audit and dialog polish
The Japanese guides, tool catalog, pricing, and about pages now have Japanese bodies — not just Japanese menus around English text.
Each Japanese page also exposes a Markdown mirror for AI agents, and search engines get Japanese titles and descriptions for every /ja page.
The feedback form no longer clips the title or hides the message under the close button.
The Japanese site uses the language code ja (not jp) and the same translation library as English, so menus and the homepage stay in one language.
Menus, footer, approval demo, and theme toggle on /ja now use Japanese labels — not a mix of English chrome and Japanese headlines.
The Japanese landing page no longer lets the headline run over the approval card, and the demo buttons on that card are in Japanese.
Each write now shows one final result instead of a leftover “waiting” row after it already ran.
While an assistant checks whether you have approved, those check-ins no longer clutter the audit list.
If you reject or a request expires, the audit line updates to match — you will not see a waiting badge with an empty Approvals inbox.
Visitors can now explore ERPipe in Japanese at /ja with tailored explanations of human approval write gates and enterprise AI safety.
A quick language toggle is now available in the navigation bar to easily switch between English and Japanese.
— AI assistants now see your latest guides
The machine-readable content map that AI assistants (ChatGPT, Claude, Gemini) read to discover our documentation now reflects the current guide library and comparison pages, with a fresh as-of date.
— Totals no longer trip up your AI
When your AI asks for a grand total (sum, count, average) it now gets one clean number back instead of an error telling it to group first.
Grouped breakdowns work exactly as before — and if the AI forgets to say how to group, the error now shows it the right way to ask.
Asking for a record count now works on every Odoo version we support — older servers no longer reject the request.
— Odoo webhooks are now actually easy to turn on
Each connection now shows a 5-minute, click-by-click recipe for creating the Odoo automation that feeds events to your AI — including the exact field to add, since Odoo cannot send custom headers.
A new Test webhook button queues a sample event so you can confirm end-to-end in seconds: press it, ask your agent to run list_odoo_events, and see it.
The connection page now shows webhook status at a glance — waiting for the first event vs working, with the time of the last event.
Behind the scenes, events can now authenticate the way Odoo actually allows (secret in the payload or URL), and the secret is never stored in the event log.
— A clearer first run, and a safer default for your Odoo login
The connections page now opens with the three setup steps in order, so the workspace address for AI clients appears once you actually have an instance to use it with
The Odoo user field no longer suggests your administrator account, and the setup step explains what happens to the credential before you type it
The setup guide now says which client plans can run MCP tools, so you can check that before blaming the connection
Setup progress is now recorded per workspace, so we can see where people get stuck and fix the real step
— Guides, tools, pricing, and about now follow the homepage story
Each page now opens with a clear claim and supporting proof, followed by the same measured runway used on the homepage
The complete guide library, hosted tool catalog, beta pricing details, and company background remain available in their new layouts
— Every public page now has dark mode and a working mobile menu
Guides, pricing, legal, comparison and connector pages share the same header and footer as the homepage — including the theme toggle, which these pages did not have before
On phones there is now a real slide-out menu with every site link instead of a cramped row of links that did not fit on small screens
Public pages download much less code on a first visit, so guides and articles open noticeably faster
Buttons, form fields, badges, switches, menus and confirmation dialogs across the workspace and marketing desk now use the same component system as the homepage, with consistent keyboard navigation and focus handling
— The ERPipe logo is back in the homepage header
The homepage header shows the full ERPipe logo again — it had been replaced by a small square during the landing page rebuild
The logo switches to its light version automatically in dark mode, like the rest of the page
— The landing page is rebuilt, faster to read, and now supports dark mode
The homepage is rebuilt around the approval gate, so you can see exactly how an AI write to Odoo is paused for your decision before you ever connect
The page now offers a dark and light theme, remembers your choice, and follows your system preference on a first visit
It is faster to load and easier to read on phones, with larger text, clearer contrast, and real product controls instead of diagrams
— Link previews now show how agents connect to live Odoo
When you share most ERPipe pages in chat or social apps, the preview image now shows AI agents connecting through the hosted gateway to live Odoo, with human approval and an audit trail
Each guide still uses its own article preview image
— Telegram approval messages now show which Odoo instance
Write-approval messages in Telegram now name the Odoo instance, so you can tell a test database from production before you approve
Production-like instance names are marked clearly, matching the existing approval email
After you approve or reject, the short status line also includes the instance
— Your analytics choice is back, and comparison pages now open complete
The analytics choice is offered again. It had stopped appearing, which also stopped ERPipe recording where a new workspace first came from — so recent signups have no source recorded and that gap cannot be recovered
You can now allow or decline analytics independently of whether Google Analytics is switched on, and declining still stores nothing
The connector setup page and the comparison, alternatives, and compatibility pages now include their full text in the first page response, so search engines, AI readers, and text-only browsers no longer see a short summary
Every public page now links onward to related pages, and the Odoo compatibility table is read from one shared source so the page and the machine-readable version cannot disagree
Each guide now publishes its questions and answers in a form search engines and AI assistants can quote, and the two setup guides publish their steps the same way
— Guides now arrive complete and share with their own image
Every Odoo × AI guide now includes the complete article in the first page response, so search, AI readers, and text-only browsers do not need JavaScript to reach the body
Each guide now has its own share image, while the Guides page describes the complete seven-article collection consistently
— Guides now separate setup, field notes, and Odoo AI changes
The Guides page is now an Odoo × AI field manual, so you can tell repeatable setup from implementation experience and official-source analysis before opening an article
New notes compare native Odoo AI agents with an external MCP gateway and explain when a local process, Odoo addon, or remote gateway fits
The human-approval guide now explains why Odoo permissions remain essential and why AI writes still need a narrower decision path
Claude Code now has a focused setup guide for browser sign-in, shared or personal configuration, and a safe first Odoo check
A new guide explains how agents can reuse a short lesson from a verified fix while still checking live Odoo every time
— Approved Odoo writes can finish safely even after a lost response
For supported Odoo actions, your agent can show a preview, wait while an owner approves in the dashboard, then continue the same request
If the first response is lost, retrying the approved request returns the completed result without applying the Odoo action twice
Changed or expired approval details are rejected before they reach Odoo
— Campaign visits can now be followed through a working Odoo connection
If you allow analytics, ERPipe keeps one bounded campaign source and referring hostname, then measures aggregate progress from signup to first Odoo connection and first successful tool
Campaign labels reject email-like values and never include full referring URLs, Odoo data, credentials, or record details; choosing Continue without analytics before starting sign-in creates no attribution row
The homepage, About page, guides, pricing, changelog, and open-source lineage are now easier to find and use one clear product description
— Analytics now waits for your choice
ERPipe does not load Google Analytics until you choose Allow analytics
You can continue without analytics or change the choice later; signups are now counted separately from returning sign-ins
— The tools page now starts with the read-only checks most people need
After you connect an agent, the tools page and ChatGPT setup guide now start with a live receivables-style check, then drill into one company
The full list of tools is still there. Writes still stay off until you turn them on, and they still wait for your approval
— ChatGPT setup is easier to find from the connector guide
The connector setup page now shows the five ChatGPT steps up front and links to the full how-to
The steps work over a hosted connection, so you do not run a local MCP process on your laptop
— Agents can read larger Odoo files
Your agent can now pull Odoo files up to about 10 MB instead of 2 MB
Files bigger than about 15 MB still need to be opened in Odoo
— Approval previews follow the language you are using with the agent
The approval card, email, and Telegram note for each request follow the language you are using with the agent, including the why text and the actions on that request
Existing requests keep the language they were created with. The rest of the dashboard does not switch
— The guides index is readable without JavaScript
The Guides page now lists every guide and comparison even if JavaScript is turned off
Search engines and text-only browsers can read the same titles and short descriptions as the interactive page
— Privacy, terms, and security pages are readable without JavaScript
Privacy, Terms, Security, DPA, and Subprocessors now show their full notices even if JavaScript is turned off
Search engines and text-only browsers can read the same trust-center text as the interactive pages
— Connection health emails open the right settings page
The Open connection settings button in up/down emails now opens that Odoo connection instead of a missing page
Older emails that used the instance name in the link still work after you sign in
— About and pricing pages are readable without JavaScript
The About and Pricing pages now show their full notes even if JavaScript is turned off
Search engines and text-only browsers can read the same founder and beta-price details as the interactive pages
— Public changelog notes are readable without JavaScript
The public changelog page now shows recent product notes even if JavaScript is turned off
Search engines and text-only browsers can read the same notes as the interactive page
— Send feedback sits quietly at the bottom of the workspace menu
The signed-in menu is English-only. Send feedback is a small action under the page list, not another Admin item
It still opens a short note about ERPipe Cloud. It is not an Odoo support ticket
— Send product feedback from the signed-in workspace
There is a Send feedback control in the signed-in workspace so you can report a bug or idea about ERPipe Cloud
Your note goes to the ERPipe team with the page you were on. It is not an Odoo support ticket and there is no in-app reply thread
Do not include passwords, keys, or personal records. The privacy notice now explains how this feedback is stored
— Sign-in page is no longer treated as the homepage
The sign-in page now tells search engines not to index it
It no longer points search engines at the public homepage by mistake
— Public pages keep their layout on refresh
The marketing site no longer drops to plain unstyled text after you reload
If a tab still looks broken, refresh once so it picks up the restored styles
— Public list of every hosted Odoo MCP tool
There is now a public catalog of the 43 tools your AI client can call on the hosted connector, including which ones exist only on hosted ERPipe
Guides that explain what an Odoo MCP server is, how to connect ChatGPT, and how write approval works now lead with dated facts and comparison tables
Search engines and assistants that do not run JavaScript can read the catalog and those guides from the first HTML response
— Public pages now readable without running the app
Search engines and AI assistants that do not run JavaScript can now read the product definition, FAQs, and guide text on the public site
Missing pictures and leftover files no longer pretend to be the homepage
The hosted tool count on the site matches the live connector (43 tools)
New comparison page: ERPipe versus Pantalytics, with unknowns marked and no invented scores
— Record totals are no longer a short search page
When an agent asks how many records you can see, it now uses the full access count instead of a search page that stops at 50
Reconnect your AI client so it picks up the corrected lookup path
— Stale write approvals time out on their own
A write request that sits unapproved, or approved but never finished, now expires after a short wait instead of hanging in Approvals
If a write was already running and got stuck, it is marked unclear rather than left in progress — check Odoo if you are not sure it applied
Reconnect your AI client so it looks up records the supported way, which avoids a common class of failed searches
— Approve or reject a write from the email
Approval emails now have Approve and Reject, like Telegram
Tapping a button opens a short confirm page that applies the decision. You do not need to sign in or open the dashboard first
Review details is still there if you want the full inbox. Do not forward the email — those buttons decide the write
— Limit which Odoo models an agent may use
On each connection you can now list the models and operations an agent is allowed to read or change. Leave the list empty to keep the current open behavior
You can save short named actions for allowed Odoo methods so agents call those instead of inventing their own server scripts
Writes still start off and still need your approval when you have turned that on
— Clearer answers for connecting AI agents to Odoo
A new About page explains who built ERPipe and why a hosted, approval-first path exists
The ChatGPT setup, build-versus-buy, and alternatives pages now lead with a direct answer and common questions
New pages cover what an Odoo MCP server is, how write approval works, and when a custom server still makes sense
— GitHub sign-in is paused for now
Continue with GitHub is temporarily unavailable on the sign-in page
Use Google or an email sign-in link to get back into your workspace
— Agents can reuse verified past fixes without being asked
ERPipe now guides connected agents to look up similar past cases when a problem looks familiar — you do not have to ask them first
After a verified reusable fix, they can save a short lesson for next time, not passwords, secrets, or one-off lookups
Ask them to forget a saved case if it is wrong. Reconnect the agent if it still ignores past cases
— Telegram approval cards update when you decide in the dashboard
Approving or rejecting a write in the dashboard also clears the Telegram approval buttons
You get the same short confirmation in Telegram, including on other linked owner chats
Tapping Approve or Reject in Telegram still updates every card for that request
— Workspace owners control connection settings
Only the workspace owner can create, edit, pause, or delete Odoo connections, change write settings or field rules, and rotate webhook secrets
Teammates still see connections and can review and approve write requests
— Sign-in codes are protected from guessing attacks
Too many wrong code entries blocks that email for a short time and cancels its outstanding sign-in codes
Each email address gets a limited number of sign-in messages per window to stop automated abuse
— Saved agent memories stay private to you
Each person's saved cases stay in their own workspace account — teammates do not see them
Agents only bring back closer matches, so unrelated past work is less likely to appear
— Agents load less of your Odoo data by default
Agent lookups now need a search filter instead of dumping an entire table
Each lookup returns a smaller page of rows so chats stay faster
If an agent asks for too many rows at once, we trim the request automatically
— Choose how you get write-approval alerts
In Settings → Notifications you can turn email, Telegram, and browser push on or off independently
Everything stays on by default. Turning a channel off pauses alerts without unlinking Telegram or this browser
Enable this browser from the Approvals inbox; manage all channels from Settings
— Approve in Telegram with one tap
Tapping Approve on a Telegram approval card now approves immediately — no second confirmation tap
Reject is still one tap. Dashboard Approvals still asks you to confirm before deciding
— Telegram approvals leave a short confirmation
After you approve or reject a write in Telegram, the long approval card is removed from the chat
You get one short confirmation instead of a second long message
Approval alerts no longer expand with a large website preview
— Telegram approval buttons now reliably appear
Fixed an issue where Approve and Reject buttons were silently dropped by Telegram, causing approval notifications to never arrive
Buttons are now compact and stay within Telegram's size limits — no changes needed on your end
— Telegram bot linking now works reliably
Fixed a silent failure that prevented Telegram from pairing after you sent /start — bot tokens are now stored correctly
The Settings page now warns if your bot is shared with another webhook so you know to create a dedicated bot in @BotFather
A live webhook check runs at connect time; if your bot is already claimed by another service you'll see an 'overridden' badge instead of a silent failure
Pairing status updates automatically after you open the connect link — no need to refresh the page
If you set up Telegram before this update, go to Settings → Notifications → Disconnect, re-paste your bot token, save, then click Connect Telegram and open the link (do not type /start manually)
— Clearer Odoo errors and connection health tracking
Agents now get a short hint when a lookup or write is blocked — including which methods are allowed, how to fix a missing group-by, and how to check field names for this Odoo version
Count and group lookups on newer Odoo versions no longer fail on a bad count formula
We now record why an Odoo connection is unhealthy (login versus host down) so we can later pause broken logins automatically — nothing is auto-paused yet
— Connect your own Telegram bot for approval alerts
Each workspace now uses its own Telegram bot — create one in @BotFather, paste the token in Settings → Notifications, and ERPipe sets everything up automatically
No shared bot or manual configuration required: webhook registration, encryption, and deep-link pairing all happen in the dashboard
Approve or reject writes directly in your bot's chat with the same one-tap buttons as before
— Approve or reject writes directly from Telegram
Connect your Telegram account from Settings → Notifications to receive write approval alerts in Telegram
Each notification shows the operation, model, summary, rationale, risk level, and time remaining
Tap Approve or Reject in the Telegram message — same authority as the approval inbox in the dashboard
Approve requires a confirmation tap before executing, matching the dashboard confirm dialog
Use /status in the bot to list pending approvals, /unlink to disconnect
— Agents wait briefly after you approve a write
After you approve a write, connected agents now wait a few seconds for the result instead of stopping the chat
If you need more time, the request stays in Approvals and the agent can continue later
— Approval cards show names on vendor pricelist lines
Write approvals now show the Odoo record name instead of Unresolved name, including vendor pricelist lines that do not have a Name field
The current value of each changed field is shown when Odoo can read the record
— Agents can remember solved Odoo work
Connected agents can save a short summary of a solved problem and recall similar past cases later
Saving a remembered case works after a normal Odoo lookup — the agent can cite the step it just ran
Looking up a similar past case now works in live workspaces after a case is saved
Recalled memories are labeled as untrusted history — agents still re-check live Odoo data before acting
You or the agent can forget a saved memory when it is wrong or outdated
Signing in and reconnecting an agent stays on the fast path; remembering happens only when the agent saves or looks up a case
Platform admins can review and forget agent memories across workspaces from the admin console
— Optional browser alerts for write approvals
Workspace owners can opt in to browser alerts when a write is waiting for approval
Each alert opens the pending request for review in the secure dashboard
Alerts never approve a write automatically and can be disabled from the Approvals page
— Beta interest confirmation email
Joining the priority beta list now emails a confirmation with a free Connect Odoo link
Platform admins get an alert when someone joins from the landing page
Landing form success copy points people to their inbox