User Guide — ORMdoo Admin Interface

Open the access URL provided in your welcome email (format: https://admin.SLUG.ordoo.online). Enter your username and password, then click Log in.

1. Open the URL in your browser.

2. Enter your username and password.

3. Click Log in.

After login, you land on the Dashboard. It provides an overview of your Odoo instances: used quota, number of active/stopped/error instances, a compact instance list with their status, and a distribution chart.

Navigation

The left sidebar gives access to 7 sections: Dashboard, Instances, Versions, Users, Settings, Backups and Support. At the bottom, the Light / Dark / Auto buttons switch the interface theme, and the Logout link ends your session.

The Instances page lists all managed Odoo instances. Each instance card shows:

• The instance name and access URL
• The Odoo version and type (Production or Staging)
• The MASTER password (masked — 👁 reveal and 📋 copy buttons)
• The Custom domain block (production only)
• The row of action buttons
• Real-time metrics at the bottom of the card

Available action buttons

• ⏹ Stop / ▶ Start — Stops or starts the Odoo service
• ↺ Restart — Restarts the Odoo service
• ⚙ Configuration — Shows the instance configuration
• 📦 Addons — Installs custom modules
• 💾 Backup — Creates a backup (active instance only)
• 📥 Restore — Restores from a backup
• ⧉ Clone — Clones to a staging instance (production only, if no existing staging)
• 🔄 Rebuild — Rebuilds the staging instance from production (staging only)
• 📬 Mailpit — Opens the staging instance's test mailbox (staging only, if domain active)
• 👤 Connect as — Opens an Odoo session under a user account (active instance)
• ✉ Email — SMTP configuration for the instance (production only)
• ⎇ Git repos — Manages module repositories
• 🗑 Delete — Permanently deletes the instance

At the bottom of each instance card, metrics refresh automatically and show the server state:

• DB Connections — Donut chart: active vs inactive PostgreSQL connections
• Odoo Errors (6h) — Bar chart of errors over the last 6 hours
• Memory used (in MB)
• Workers — Number of active Odoo processes
• Deadlocks — Blocking PostgreSQL locks

Click + Create an instance in the top right of the Instances page to open the creation form.

Infrastructure section

• Odoo version — Only installed versions are available (see Versions chapter)
• Edition — Community (free) or Enterprise (requires SSH key configured on GitHub)

Identity section

• Instance name — Lowercase letters, numbers, hyphens and underscores only (e.g. demo, client-test, prod-v2)
• Odoo admin login — Administrator account login (default: admin)
• Auto-generate password — Checked by default; uncheck to set a custom password

Localisation section

• Company phone — Optional
• Language — Default language of the Odoo company
• Country — Sets the company's country, currency and timezone

After clicking 🚀 Create instance

Provisioning starts. The instance card appears with the In progress status. Progress is displayed in real time. Full provisioning takes about 5 minutes.

The backup generates a ZIP archive in standard Odoo format: SQL dump + filestore/ folder (attached documents). This file is compatible with restoration via this panel or directly via /web/database/manager on any Odoo instance. See also the Backups chapter for nightly automatic backups.

1. Click the 💾 button on the desired instance card.

2. Select the database to back up from the dropdown.

3. Click 💾 Create backup.

4. Wait for the operation to complete. The ZIP file is downloaded automatically.

Restoration completely replaces the database and filestore of the target instance with the content of the uploaded ZIP. The expected format is the standard Odoo ZIP format (dump.sql + filestore/), compatible with an export from /web/database/manager on any Odoo instance.

1. Click the 📥 button on the target instance card.

2. Select the backup ZIP file (standard Odoo format).

3. Click 📥 Restore. The instance is stopped, the database recreated, then the instance restarts.

This function uploads custom Odoo modules to the server. The ZIP is automatically extracted into the instance addons directory, and the instance restarts automatically.

Step 1 — Prepare the ZIP

The ZIP should contain the Odoo module folders directly at the root or in a subdirectory. The interface automatically detects the structure.

Step 2 — Upload via the panel

1. Click the 📦 button on the instance card.

2. Click Choose a file and select your ZIP.

3. Click 📦 Add addons. The instance restarts automatically.

Step 3 — Activate modules in Odoo

Once the instance has restarted, open Odoo and go to Apps. Find your modules and click Install.

Cloning creates a copy of the production instance as a staging instance. Data is automatically sanitised at the end of cloning (emails disabled, passwords reset). A staging instance offers the 🔄 Rebuild button to resync later from production, and 📬 Mailpit access to intercept test emails without ever really sending them.

1. Click the ⧉ button on the production instance card.

2. Enter a name for the staging instance.

3. Click Clone.

This feature opens an Odoo session directly under a user's account, without entering their password. Useful for assisting a user or checking their account status.

1. Click the 👤 button on the instance card.

2. The list of active Odoo users is displayed.

3. Click the desired user. A new window opens directly logged into Odoo under that account.

Link a Git repository containing custom Odoo modules to an instance. The repository is cloned on the server and its path added to the Odoo configuration. A GitHub or GitLab webhook can trigger an automatic pull on each push.

1. Click the ⎇ button on the instance card.

2. Click + Add to expand the add form.

3. Fill in the repository URL, branch and access token (for private repositories).

4. Click Add repository. The repository is cloned and its path added to Odoo.

5. Install the modules from Apps in Odoo.

Every production instance can be exposed on your own domain name (e.g. erp.mycompany.com) in addition to its *.ordoo.online subdomain. The Custom domain block appears on every production instance card.

1. With your domain registrar, create an A record pointing your domain to the ORMdoo server's IP address (shown in the panel).

2. In the Custom domain block on the instance card, enter the domain (e.g. erp.mycompany.com) and click Save.

3. Once the SSL certificate is generated, the domain becomes clickable and redirects to your instance.

The ✉ button on a production instance card configures the SMTP server used by Odoo itself to send its emails (quotes, invoices, application notifications) — not to be confused with the admin console's SMTP (Settings chapter), which is only used for this interface's own emails.

• SMTP server and Port (e.g. 587)
• Encryption — STARTTLS (587), SSL/TLS (465) or None (25)
• SMTP username and Password (leave the password empty to keep the existing one)
• Sender email (From) — Same as SMTP account if empty
• Sender name — Name shown on outgoing emails
• Filter (domain or regex) — Restricts this outgoing server to specific addresses (e.g. @mycompany.com)

1. Click the ✉ button on the production instance card.

2. Fill in the fields above.

3. Click Test connection to verify the credentials before saving.

4. Click Save. The configuration is applied directly inside Odoo.

The Versions page shows the Odoo versions installed on the server, allows installing new versions and upgrading from Community to Enterprise edition.

Installed versions table

For each installed version, the table shows: version number, edition (Community or Enterprise), number of active instances using this version, Python version used and installation path on the server.

Install a new version

The Install a new version section lists all supported versions available (17 to 20 — versions 14, 15 and 16 are blocked, EOL or unsupported). Click a card to start the installation.

1. Click the card for the desired version. A confirmation dialog appears.

2. Optionally check Install Enterprise modules (requires a configured GitHub SSH key — see below).

3. Click 🚀 Start installation. The process runs in the background (~15-30 min for the first version, ~5-10 min for subsequent ones).

4. A real-time log is displayed in the dialog. You can close the page — the installation continues on the server (use 🔄 Refresh to resume tracking).

5. Once done, an Installation completed successfully message appears and the new version shows in the installed versions table.

Upgrade to Enterprise (Community → Enterprise)

If a Community version is already installed, the Upgrade to Enterprise button lets you add Enterprise modules without recreating existing instances.

1. Make sure an SSH key with access to odoo/enterprise is configured (see Enterprise SSH key section below).

2. In the installed versions table, click Upgrade to Enterprise for the desired version.

3. A dialog automatically checks the GitHub SSH connection. If the key is valid, the Launch Enterprise upgrade button appears.

4. Click Launch Enterprise upgrade. The repository cloning starts (~5-10 min). A progress bar is displayed.

5. Once done, a Enterprise modules successfully added message confirms the upgrade. The edition switches to Enterprise in the table.

Enterprise SSH key

Odoo Enterprise is distributed via a private GitHub repository accessible only to customers with an active subscription. You must link an SSH key to your authorised GitHub account.

1. In the Enterprise SSH key section, copy the displayed public key (using the 📋 Copy button).

2. Go to GitHub → Settings → SSH and GPG keys → New SSH key. Paste the key and save.

3. Request access to the odoo/enterprise repository from Odoo S.A. via your contract.

4. Test the connection with the 🔌 Test GitHub connection button. A confirmation message appears if the key is recognised.

The Users page has two tabs: 👥 Users (admin account management) and 📧 Email history (log of all emails sent).

Create an account

1. Enter the Username (email address).

2. Set a Password (minimum 10 characters).

3. Check Allow user management if this admin should be able to create other accounts.

4. Click Create user.

Actions on existing accounts

• 📧 Send email — Sends an email to the user via the configured SMTP
• Reset password — Sets a new password for this account
• 🔒 Enable 2FA — Enables two-factor authentication (TOTP). The user must scan a QR code with Google Authenticator, Aegis or Bitwarden.
• Delete — Permanently deletes the account

This SMTP is used only for this admin console's own emails (login OTP codes, alerts). It is independent from each Odoo instance's SMTP — to configure email sending from an instance (Odoo quotes, invoices), use the ✉ button on its card, Instances page. A badge shows the current state: Configured (green) or Not configured (red).

Fill in the form

• SMTP server (host) — Sending server address (e.g. mail.infomaniak.com, smtp.gmail.com)
• Port — SMTP port (587 for TLS, 465 for SSL)
• User — Sending email address
• Password / App Password — For Gmail, use an App Password generated in Google security settings

Click Save to save. The badge turns green if the configuration is valid.

In addition to manual backups (see Create a backup), the platform runs an automatic backup of all active production instances every night.

Rotation

• 7 daily backups — one per day, kept for 7 days
• 4 weekly backups — kept for 4 weeks
• 3 monthly backups — kept for 3 months

How it works

• Runs every night at 02:00 (server time)
• Only running production instances are backed up (staging and stopped instances are skipped)
• Standard Odoo ZIP format (database + filestore), compatible with restoration via the 📥 Restore button or /web/database/manager

The Support page lets you send a request directly to the ORMdoo team, without leaving the admin console.

1. The From field is pre-filled with your login email address (not editable).

2. Fill in the Subject — briefly describe your issue.

3. Fill in the Message (5000 characters max) with the details of your request.

4. Click ✉ Send. The ticket is forwarded to the support team.