Let anyone try your Odoo application safely — without sharing passwords or creating users manually.
Visitors get a temporary, restricted demo account of their own, limited to the apps you choose and the time you allow — then it cleans itself up. Google Sign-In is simply the authentication mechanism: no signup form, no password to leak.
| One-click access with Google sign-in | Demo users provisioned automatically | Sessions expire on a timer | Accounts cleaned up by themselves |
Sharing demo access is broken
Automatically create restricted demo users, enforce time limits, and clean up accounts after each session.
|
Shared credentials
One demo password on a slide, forwarded forever, changed never.
|
Manual invitations
Creating a user for every prospect doesn't scale past the first webinar.
|
Stale accounts
Demo databases full of forgotten logins nobody dares to delete.
|
|
Wide-open demos
Public signup gives strangers whatever the portal template allows.
|
No seat control
Twenty visitors at once and the demo server melts mid-presentation.
|
Sessions that never end
A prospect's tab from last Tuesday still logged in to your database.
|
One visitor, one clean loop — from click to cleanup
Every demo visit runs the same protected cycle. You configure it once.
| Visitor arrives at your demo |
| ↓ |
| Signs in with Google |
| ↓ |
| Restricted demo account created automatically |
| ↓ |
| 15-minute demo session |
| ↓ |
| Account archived automatically |
Come back later? The same Google account is recognised and reactivated instantly.
“Can't I just enable Google OAuth?”
You can — and it will sign in the users you already created. It won't run a public demo. That is the whole difference.
| Capability | Odoo Google OAuth | Public Demo Login |
| Existing users sign in with Google | ✓ | ✓ |
| Auto-create demo users for strangers | ✗ | ✓ |
| Time-limited sessions | ✗ | ✓ |
| Automatic cleanup of demo accounts | ✗ | ✓ |
| Concurrent demo limits | ✗ | ✓ |
| Restrict visible apps | ✗ | ✓ |
| Demo session monitoring | ✗ | ✓ |
Google Sign-In for Odoo
Built on Odoo's standard OAuth2 authentication (auth_oauth),
the same social-login flow visitors already know from every modern app. One familiar button, zero passwords stored,
identity handled by Google.
| No passwords to store, share or reset — Google holds the identity | Standard OAuth2 token flow — no custom auth code paths | Returning visitors are recognised instantly by their Google account |
Secure by default, generous by choice
A new demo user receives nothing until you say otherwise. You choose the security groups they get and the apps they see — everything else stays invisible.
|
Settings · Public Demo Login
Everything an admin controls, on one screen
| |
| Granted security groups | your choice |
| Visible applications | your choice |
| Concurrent demo users | 10 (configurable) |
| Session duration | 15 min (configurable) |
| Cleanup of stale accounts | automatic |
At capacity, visitors see a friendly “demo is currently full” message — not an error page.
Features
| ✓ One-click demo access — no invitations or signup forms | ✓ Automatic provisioning on first login, reuse on return visits |
| ✓ Zero permissions until explicitly granted | ✓ Configurable groups and visible apps |
| ✓ Concurrent user cap with a friendly full-house message | ✓ Hard session expiry (15 minutes by default) |
| ✓ Automatic archiving and seamless reactivation | ✓ Base URL mode for Cloudflare Tunnel & TLS proxies |
| ✓ Demo Sessions monitor for administrators | ✓ Free — LGPL-3 licensed |
Who it's for
Anyone who has ever emailed a demo password to a stranger.
| App developers public demos for Apps Store modules |
Odoo Partners solution demonstrations without babysitting |
Sales teams send a link, not a password |
Consultants customer proof-of-concepts |
| Trainers training databases, one account per learner |
Conference booths let visitors drive it themselves |
Webinars hands-on for everyone watching |
Public sandboxes open environments that stay clean |
Create your Google OAuth client
You need one free Google Cloud project and one OAuth client. Takes about five minutes, done once.
1. Go to console.cloud.google.com and create a project (or select an existing one).
2. Open Google Auth Platform → Branding. Enter your app name, user-support email and developer contact email, then save.
3. Open Google Auth Platform → Audience. Choose External. While the app is in Testing only listed test users can sign in — click Publish app so any Google account can reach your demo.
4. Open Google Auth Platform → Clients and click Create client. Application type: Web application. Give it a name.
5. Under Authorized JavaScript origins add your Odoo URL:
https://yourdomain
6. Under Authorized redirect URIs add — exactly, including the path:
https://yourdomain/auth_oauth/signin
7. Click Create and copy the Client ID. That is the only value Odoo needs — no client secret required for this flow.
redirect_uri_mismatch? The URI in Google must match what Odoo sends, character for character — scheme, domain and the /auth_oauth/signin path.
|
Testing locally? Google accepts http://localhost:8069/auth_oauth/signin; public domains must use HTTPS. You can register both URIs on one client.
|
Configuration
1. Install Public Demo Login (pulls in Odoo's OAuth modules automatically).
2. Settings → Integrations: tick OAuth Authentication and save.
3. Same page: tick Google Authentication, paste the Client ID from step 1, and save.
4. Enable Demo Auto-Provisioning on the Google provider: activate developer mode, then go to Settings → Users & Companies → OAuth Providers → Google OAuth2 and tick the checkbox.
5. Settings → General Settings → Public Demo Login: choose granted groups, visible apps, concurrent users and session timeout.
6. Log out. The login page now shows Sign in with Google.
Your public demo is ready — visitors simply click Sign in with Google and receive a temporary demo account automatically.
Questions, answered
Can demo users see my data?
Only what their granted groups allow. By default they receive no permissions and see no apps — you decide exactly what a demo shows.
What happens when the demo is full?
New visitors see a friendly, configurable “running at full capacity” message on the login page. Seats free automatically as sessions expire.
Does it work behind Cloudflare Tunnel or a reverse proxy?
Yes. If your proxy hides HTTPS from Odoo, enable the optional Base URL mode and OAuth redirect links are built from your public URL.
What does it cost?
Nothing. It is free, licensed under LGPL-3.
Your demo, one Google click away.
Odoo 19 · Community & Enterprise · free · LGPL-3
Need another provider, database reset, per-user data isolation or a feature not listed here?
Write to support@daorys.xyz — we build custom integrations.
Daorys — focused, vertical Odoo apps for real businesses · apps.daorys.xyz
Google Sign-In · Google Login · OAuth2 · social login · public demo access · demo users · trial accounts · Odoo 19
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 584 |
| Technical Name |
public_demo_login |
| License | LGPL-3 |
| Website | https://apps.daorys.xyz |
Please log in to comment on this module