Community Meetings — User & Administrator Guide
Welcome to the Community Meetings suite for Odoo 18. This guide teaches you how to use and administer the modules — it does not cover installation.
On this page
What you get
| Module | What it does | For whom |
|---|---|---|
Community Meetings (community_meetings) |
Operational meetings with structured agendas, reusable points, resolutions, follow-ups, dissent, minutes and immutable approved revisions. | Everyone |
Community Meetings – Project Tasks (community_meetings_project) |
Links follow-ups to Odoo Project tasks and adds task policies. | Teams using Project |
Community Meetings – Calendar (community_meetings_calendar) |
Publishes each scheduled meeting as a read-only Odoo Calendar event. | Everyone with Calendar |
Extension Contract Demo (community_meetings_extension_demo) |
Synthetic example showing how developers extend meeting kinds. Developers only — ignore it in day-to-day use. | Developers |
Who is who
The suite is role-based. Find your role, then follow its track:
| Role | Typical person | Start here |
|---|---|---|
| Reader | Any attendee who consults meetings and minutes | Reading meetings |
| Proposer | Any internal user suggesting agenda points | Propose a point |
| Editor | The person preparing and running meetings | Prepare a meeting |
| Approver | Whoever signs off the minutes | Minutes and approval |
| Manager | The module administrator | Administration |
Roles are cumulative: an Editor is also a Reader; a Manager is Editor + Approver. See Roles and permissions.
The 5-minute mental model
- A series describes a recurring meeting (kind, people, schedule, policies).
- Each concrete meeting is prepared from the series or standalone, with an agenda of points.
- A point is a subject with its own identity: it can appear in several meetings, keeping a separate discussion and outcome in each one.
- The meeting is run live from a dedicated screen: discussion notes, agreements, dissents, follow-ups and postponements are recorded in the moment.
- When it finishes, the minutes are prepared and approved. Approval freezes an immutable revision with its PDF.
flowchart LR
S["Series<br/>recurring template & policies"] --> M["Meeting<br/>prepare agenda (wizard)"]
M --> L["Live meeting<br/>notes · agreements · follow-ups"]
L --> A["Minutes<br/>prepare & approve"]
A --> F["Follow-ups<br/>activities · To-dos · tasks"]
L -. "carryovers" .-> M
Document map
| I want to… | Read |
|---|---|
| Understand the vocabulary | Concepts |
| Know who can do what | Roles and permissions |
| Configure the modules | General configuration · Series · Catalogs |
| Prepare a meeting | Prepare a meeting |
| Suggest a point for a future meeting | Propose a point |
| Run a meeting live | Live meeting |
| Write, approve or amend minutes | Minutes and approval |
| Track who does what after the meeting | Follow-ups |
| Move points to another meeting | Carryovers |
| Use Calendar / Project | Calendar · Project |
| See what changed between releases | Release notes |
| Solve a problem | FAQ |