Odoo Calendar & Contacts: A Practical Guide to Scheduling and the Address Book

What Odoo Calendar and Contacts actually do

Odoo Calendar is the core scheduling app in Odoo 19, grouped under Productivity alongside Documents, Discuss, and the separate Appointments app. It opens to a calendar overview with Day, Week, Month, or Year views and a Show weekends toggle. Clicking any date opens the New Event popup with the signed-in user auto-added as the first attendee, so an event is never orphaned.

Odoo Contacts is the central repository for every business relationship in the system: customers, suppliers, partners, and individual employees. It is accessible as a standalone app and is the single source of truth that Calendar, CRM, Sales, Purchase, and Accounting all read from. The two apps are designed to interlock. A meeting scheduled from a contact, an opportunity, or a project task links back to that record through the Chatter, so context travels with the event rather than being copied into a separate system.

This tight coupling is the practical reason SMEs consolidate scheduling and contacts on Odoo instead of stitching together a calendar tool, a contact manager, and a CRM. There is one partner list, one attendee model, and one activity history per record.

Inside the Odoo Calendar event model

Every Odoo Calendar event supports All Day or specific start and end times, multi-day spans, manually added or auto-generated videocall URLs, and a full form with Duration, Organizer, Tags, description, Reminders, and Recurrent options. Recurrence is granular: you pick a repeat period, configure recurrence rules, and choose an end condition (a fixed count, an end date, or Forever), with explicit timezone selection so distributed teams do not lose an hour on daylight saving.

Attendees are partner records referenced through a many-to-many field, which means internal users and external contacts share one attendee model. Adding a guest is the same action whether the guest is a colleague or an outside customer, and removing them sends the right cancellation depending on the active sync provider.

Share Availabilities, also called Specific Slots, lets a user drag to select available time ranges, copy a shareable link, and configure the Appointment Title, Users, Location, and Video Link type. The configuration screen adds tabs for Availabilities, Questions, Communication (templates and reminders), and Options including auto-confirm, automatic CRM opportunity creation, and scheduling or cancellation windows. For more advanced self-service flows, the separate Odoo Appointments app adds user- and resource-based booking, published booking pages, capacity management, pre-booking windows, manual or auto confirmation, guest invites, and CRM opportunity creation.

Reminders, attendees, and event privacy

Every Odoo Calendar event carries a Reminders field where you stack one or more alarms, each of which fires independently. Two reminder types ship out of the box: a Notification, which surfaces as an in-app popup in Odoo Discuss at the configured offset, and an Email, which drops into the mail queue and is sent to attendees. A typical external-meeting setup pairs them: a Notification 10 minutes before the start so the organizer gets a popup, plus an Email 1 day before so outside guests receive a written reminder in their inbox. You can add as many reminders as a meeting warrants, and each can use a different type and offset.

To avoid re-entering the same offsets on every event, Calendar, Configuration, Alarms is where you define reusable reminder presets. Create named presets such as '15 min popup' or '1 day email', and teams inherit a consistent reminder policy instead of each organizer guessing. Customer-facing event types (demos, interviews, support calls) are good candidates for a default alarm preset so no-shows drop without anyone manually chasing.

Two behavioural edges are worth knowing before you rely on reminders. First, Odoo's forums document a long-standing expectation gap: the event creator does not always receive the reminder email that attendees get, because the organizer is treated as the sender rather than a recipient on some reminder paths. If the organizer needs the nudge too, add the organizer explicitly as an attendee, or pair an in-app Notification (which the creator does see) with the attendee Email. Second, reminders depend on the mail queue and the scheduled cron that processes it; if outbound email is misconfigured or the cron is stalled, an Email reminder will sit in the queue and never send, so verifying outbound mail in a test event before go-live prevents a silent failure.

Attendees are full partner records, so adding an external guest is identical to adding a colleague, and each attendee's accept, decline, or tentative status is tracked on the event's Chatter. Privacy is set per event with three options: Public, which lets colleagues see the event in shared availability; Private, which hides the title and details and shows only that the user is busy; and Only Attendees, which limits visibility to the people on the event. Setting sensitive items (1:1s, reviews, confidential meetings) to Private keeps them out of overlaid team views while still blocking the slot, so colleagues respect the busy time without seeing the subject.

Shared and team calendars in Odoo

Odoo does not ship a standalone team-calendar collection. Instead, the Calendar dashboard exposes an Attendees box that lists colleagues, and toggling individual users on and off shows or hides their availability when you are scheduling an event that involves multiple people. Sharing is therefore a function of attendee visibility and the Share Availabilities feature, rather than a separate object you have to create and maintain.

For SMEs this is usually sufficient. You see your colleagues free or busy inline, you add the relevant ones as attendees, and the event appears on each of their calendars through the same partner_ids link. Where a published booking page is needed (for example, for external prospects to self-book a discovery call), the Appointments app extends Calendar with a public-facing flow that still writes back into the same Calendar data.

The practical workflow for booking a multi-person slot is to open the Calendar, toggle each colleague in the Attendees box to overlay their events on the same grid, find a gap where everyone is free, and click the empty cell to create the meeting in place. You can save a given set of overlaid users as a Favorite (for example, 'Sales Team' or 'Project Squad') so the same group is one click away next time, and color-code events by user or by tag to spot conflicts at a glance. Because Private events only show the user as busy, overlaying calendars still protects confidential items: you see that someone is unavailable without seeing what the meeting is about.

Google and Outlook two-way sync

Odoo Calendar supports bidirectional, two-way synchronization with both Google Calendar and Microsoft Outlook. The Odoo documentation states the Google integration lets you see and manage meetings from both platforms with updates going in both directions, and the Outlook integration is described as a two-way process in which events are reconciled in both accounts.

Setup for Google requires a Google API Console project with the Google Calendar API enabled, an OAuth consent screen, Web application credentials, and the redirect URI set to your Odoo URL plus /google_account/authentication. The Client ID and Secret go in Odoo under Settings, Calendar, Google Calendar. Outlook setup requires an Azure (Entra ID) app registration configured as multitenant with personal accounts, a redirect URI of your Odoo URL plus /microsoft_account/authentication, and a client secret (Odoo recommends a maximum 24-month expiry). Those credentials go in Odoo Calendar under Configuration, Settings, Outlook Calendar.

One behavioural difference is worth flagging during implementation. When Odoo is synced with Google, creating an event or adding a contact triggers Google to send an invitation, and deleting or removing a contact sends a cancellation. With Outlook, the behaviour is more aggressive: creating an event, deleting an event, unarchiving an event, archiving an event, adding a contact to an event, removing a contact from an event, or editing the date or time of an event in Odoo each cause Outlook to send a notification to all participants, with no exceptions. Odoo's documentation explicitly describes this as a Microsoft-side limitation that Odoo cannot fix, so it should be set as an expectation with users before go-live.

Sync is reset per user. From Settings, Manage Users, select the user, open the Calendar tab, and choose Reset Account, with options for the user's existing events (leave them, delete from external, delete from Odoo, or delete from both) and the next synchronization (new events only versus all existing events). A Pause Synchronization checkbox for Google temporarily disables sync without removing credentials.

Setting up Google or Outlook sync, step by step

Calendar sync is configured once at the database level by an administrator, then authorized by each user. The two providers follow the same OAuth pattern but live in different consoles: Google uses a Google Cloud project with the Google Calendar API, and Outlook uses a Microsoft Azure (Entra ID) app registration. In both cases an administrator registers an external application, copies the Client ID and Client Secret it produces, pastes them into Odoo under Calendar, Configuration, Settings (Google Calendar or Outlook Calendar), and each end user then connects their own account.

The setup that most independent guides document, and that the official Odoo documentation specifies for version 19, follows four stages: create the external application and enable the calendar API, configure the OAuth consent or API permissions, add a Web credential with the correct redirect URI pointing back at your Odoo database, then paste the resulting Client ID and Secret into Odoo and have each user authorize. The redirect URI is the single most common point of failure: it must exactly match your Odoo URL plus the provider callback path, or the token exchange throws an invalid authorization code error.

Two failure modes recur in the Odoo forums and are worth pre-empting. The first is an invalid or expired secret: an Azure client secret has a maximum lifetime, and Odoo recommends a 24-month expiry, so calendar sync silently breaks the day a forgotten secret lapses. The second is Outlook sync failing on events whose attendees carry no valid email address; the forum documents the symptom as Outlook rejecting the sync when a participant cannot be emailed, so cleaning attendee records (or removing invalid participants) resolves the error rather than reissuing credentials.

Contacts, tags, companies, and deduplication

Odoo contacts come in two types: Person, for individuals (with a Job Position field and a parent Company field), and Company, for organizations that can have multiple associated contact persons and typed addresses. A contact form surfaces contextual tabs for Contacts (associated people and addresses typed as Contact, Invoice, Delivery, or Other), Sales and Purchases, Accounting, Internal Notes, and conditionally Partner Assignment and UBO (Ultimate Beneficial Owner, which requires the Equity app). Smart buttons at the top surface related Opportunities, Sales, Meetings, Invoices, and more.

Tags are the primary way to segment that partner list without resorting to custom fields. A Tags field on the contact form accepts preconfigured tags you type in, and the same tags can be applied in bulk by switching to list view, selecting records, and adding the tag from the action menu. One structural caveat that catches teams out: tags applied to a parent company do not automatically cascade to its child contact persons and addresses, so filtering individuals by a tag that only sits on their company requires either a saved filter that traverses the parent or a deliberate tagging pass over both levels. Used deliberately, tags let you drive marketing segments, sales assignments, and reporting without duplicating the underlying partner records.

The link between Contacts and Calendar is what makes the address book worth maintaining. When you sync a calendar, every attendee on an imported event is resolved into a contact record, and a meeting scheduled from a contact, opportunity, or helpdesk ticket carries that record's context into the event's Chatter. The practical upside is one shared attendee model; the practical risk is contact bloat, which is why deduplication and hygiene belong in the same conversation as sync.

Because Calendar, CRM, and Sales all write back to the same partner list, duplicates accumulate quickly. Odoo provides two layers of cleanup. The built-in Merge action lets you select two or more contacts, choose Action, then Merge, pick the Destination Contact (which defaults to the oldest record, i.e. the one created first in the system), and confirm. The Deduplicate the other Contacts tool searches by Email, Name, Is Company, VAT, or Parent Company, and records must match all selected fields to be suggested. The tool excludes contacts that have an associated user or journal items to avoid merging accounting-affecting records.

For higher-volume hygiene, the optional Data Cleaning app (Enterprise only) adds a dashboard with rules per model (including Contacts), similarity scoring, manual or automatic merge modes, scheduled daily cron actions, domain filtering, field cleaning (Formats rules for find-and-replace standardization), a Recycle feature that identifies outdated records to archive or delete, cross-company matching, and configurable similarity thresholds. Pair this with Partner Autocomplete, an Odoo in-app-purchase service that auto-fills company data (name, logo, phone, email, tax ID, address, UNSPSC tags) when creating a new company contact, reducing manual entry and duplicates at the source.

One sync-driven mess is common enough to plan for before you enable Google Calendar synchronization: the first sync imports every past event on the connected calendar, and Odoo creates a contact record for each attendee on those historical events. Users on the Odoo forum report waking up to hundreds of auto-generated contacts cluttering the address book with no native setting to limit the import by date or to block attendee-to-contact creation. Because there is no built-in toggle, the realistic mitigations are operational rather than configurational: connect each user against a clean or secondary calendar that holds only current and future events, run a deduplication pass immediately after the initial sync using the built-in Merge tool, and if you operate Enterprise, schedule the Data Cleaning app's daily cron so the imported attendee contacts are scored and merged automatically rather than accumulating. Treating the first sync as a one-time data event, rather than a set-and-forget connection, is what separates a clean address book from a noisy one.

The Dynamics 365 equivalent: Activities, Account, Contact, and Bookings

Dynamics 365 does not ship a single Calendar plus Contacts app the way Odoo does. The closest equivalent combines three pieces: the normalized Account and Contact entities, the Activity-based scheduling model on Dataverse, and optional Microsoft 365 Bookings for external self-service booking.

On the contact side, Dynamics 365 separates Account (companies or organizations) from Contact (individual people). A contact is linked to one account at a time through a Company (parentcustomerid) lookup, giving a one-to-many relationship between account and contacts. This is more normalized than Odoo's unified res.partner model, where companies and individuals share one table and are differentiated by an is_company flag and parent-child links. The D365 split is cleaner for complex B2B hierarchies but means managing two record types per relationship.

On the scheduling side, Dynamics 365 models appointments, emails, tasks, and phone calls as Activity entities that all inherit from ActivityPointer, which Microsoft defines as any action which can be entered on a calendar and has time dimensions such as start time, stop time, due date, and duration. The Appointment table is defined as a commitment representing a time interval with start and end times and duration, with required and optional attendees, an organizer, a Regarding lookup (polymorphic to account, contact, opportunity, or case), recurrence through RecurringAppointmentMaster (pattern, interval, occurrences, with Master, Instance, and Exception handling), and Teams online-meeting fields. Participants are modeled through the ActivityParty table with roles such as Required attendee, Optional attendee, Organizer, Regarding, and Owner.

Dataverse also has a separate calendar table used by the scheduling engine to define when an appointment or activity is to occur, with types including Default, Customer Service (for SLA KPIs), Holiday Schedule, and Inner. This table is primarily used by Customer Service service activities and Field Service work orders and bookings, not day-to-day meeting coordination. For external self-service booking, Microsoft Bookings is a separate Microsoft 365 app, not a Dynamics 365 module, with booking pages, services (duration and pricing), staff availability, email and SMS confirmations, scheduling policies, and Teams meetings. Its data lives in Exchange Online shared mailboxes rather than Dataverse.

For SMEs that want contacts and scheduling in one place with minimal setup, the Odoo model is lighter and faster to stand up. For organizations already standardized on Microsoft 365, the D365 activity timeline plus native Exchange server-side sync and Teams integration is the differentiator.

Implementation considerations for SMEs

Three decisions drive most of the value from an Odoo Calendar and Contacts rollout. First, decide early whether you will sync with Google, Outlook, or both, because user training and the Outlook all-participants notification behaviour should be set as expectations before go-live. Second, plan a one-time deduplication pass using the built-in Merge tool plus Partner Autocomplete before turning on any CRM or email-marketing workflow that creates contacts automatically; cleaner seed data prevents the duplicate snowball. Third, decide where the line is between Calendar's Share Availabilities (good for internal and simple external scheduling) and the Appointments app (better for published booking pages with questions, capacity, and auto-confirm), so users are not improvising both.

Because Contacts is foundational to every other Odoo app, getting the company-versus-person structure right at import time pays compound interest across CRM, Sales, Purchase, and Accounting later.

Frequently asked questions