Odoo knowledge management for a wiki and a Help Center
As of October 2026, Odoo Knowledge on a free plan is US$0 for one app. Adding Helpdesk for a Help Center starts a 15-day trial. Articles, rights, and prices.
Key takeaways
- Articles are the unit: a title and an HTML body, including records from other apps
- Browse Templates and Add to Templates for SOPs you want every team to copy
- A search for odoo help usually lands on Odoo's own site, download page, forum login, or source repository.
- Owners usually want both an internal wiki and a customer Help Center.
What odoo help and odoo knowledge management refer to
A search for odoo help usually lands on Odoo's own site, download page, forum login, or source repository. Those pages do not explain how a company stores procedures or publishes a customer Help Center. Odoo knowledge management is the product job: the Knowledge app, whose pages are called articles.
An article is a title plus an HTML body. The body can hold text, images, links, records from other Odoo models, and templates. Child articles created under a parent are nested articles. They inherit the parent's access rights, and properties apply to the group of nested articles under that same parent.
The product page links Knowledge with Project, CRM, Sales, and Helpdesk, and it describes live collaboration, access rights, public sharing, PDF export, and revision history. The operating split is simpler than the feature list. Keep working documents in the internal categories, and publish a separate set of articles when customers should read them.
From-scratch creation offers five starts: Load a Template, Build an Item Kanban, Build an Item List, Build an Item Calendar, and Generate an Article with AI from a prompt. Generate an Article with AI starts from a prompt, and an editor should review the draft before anyone relies on it or publishes it.
- Articles are the unit: a title and an HTML body, including records from other apps
- Nested articles inherit the parent access rights
- Sidebar categories are Favorites, Workspace, Shared, and Private
- The same library feeds an internal wiki and, article by article, a public Help Center
- Knowledge is included with Standard and Custom; it is not a separate per-app price
Internal wiki vs customer Help Center
Owners usually want both an internal wiki and a customer Help Center. Knowledge can do both, and the gates are different. Workspace articles with Can Edit or Can Read are the company wiki. Private articles are personal. Shared covers articles shared with specific users. Favorites only pins a page for the person who starred it.
The Help Center is Helpdesk integrated with Forums, eLearning, and Knowledge. Three gates have to be true before customers see answers. The Helpdesk team's visibility must be Invited portal users and all internal users (public). Enabling a Help Center feature turns on the Website Form. Each customer-facing article, including every nested article, needs Share to web set to Article Published.
Checking Knowledge on a Helpdesk team adds an Article field. Odoo supplies a default article named Help. Publishing that parent does not publish nested articles. A returns policy written under Help stays internal until that child article is published on its own.
People who only have the public URL see inserted views when they can access the inserted content. A sales pipeline embedded in an internal SOP stays hidden from a website visitor who cannot open that view. That is the practical boundary between a runbook and a public FAQ.
| Dimension | Internal wiki | Customer Help Center |
|---|---|---|
| Who it is for | Employees, plus portal users you invite | Customers and website visitors |
| Where it lives | Workspace, Shared, or Private | A Helpdesk team article, often the default Help article |
| How access is set | Can Edit, Can Read, Members only, invite | Share to web set to Article Published on each article |
| Apps required | Knowledge | Helpdesk, Website, and Knowledge; Forums and eLearning are part of the Help Center |
| Plan effect as of October 2026 | Knowledge can be the single free app | Installing Helpdesk or Website on One App Free starts a 15-day trial |
Articles, templates, and powerbox blocks
Templates are loaded from Browse Templates at the bottom of the sidebar. Load a Template is also one of the from-scratch options. An existing article can be added to that list with Add to Templates, which is how a finance lead standardizes a month-end checklist or a support lead standardizes a refund answer.
Inside an article, Knowledge powerbox commands are Index, Item Kanban, Item Cards, Item List, Item Calendar, Clipboard, Foldable Section, and Article. Index lists nested articles. The item commands build boards, cards, lists, and calendars. Article inserts a shortcut to another article. Foldable Section collapses a long procedure so the reader opens the step they need.
A clipboard block stores content you reuse in other apps. On a Helpdesk ticket, clipboard boxes show Send as message and Use as description. Use as description appends text to the ticket description. Write the repeatable answer, such as a reset sequence or a shipping update, in the clipboard, and let agents send that wording from the ticket.
Views from other apps are inserted from the source view's cog menu: Knowledge, then Insert view in article or Insert link in article. The form view of other apps also has a Knowledge bookmark icon. Search for an article runs a semantic search. Advanced Search is a parametric search. Ctrl+K, then ?, searches visible articles.
Covers and emoji are part of the article model in the Odoo 19.0 documentation, and the features list includes Unsplash images. None of that changes access. A user who cannot open the underlying view cannot see that view inside the article.
- Browse Templates and Add to Templates for SOPs you want every team to copy
- Item Kanban, Item Cards, Item List, and Item Calendar for structured article items
- Clipboard, then Send as message or Use as description, for repeat ticket answers
- Insert view or Insert link from the source app's cog menu
- Properties apply to the nested articles under the same parent, so owner and review fields can sit on the parent
Sidebar categories, access rights, and Share to web
The sidebar categories are Favorites, Workspace, Shared, and Private. Workspace holds articles accessible to all internal users. Shared holds articles shared with specific users. Private holds personal articles. An article you favorite stays in Favorites for you.
Default access rights are Can Edit, Can Read, and Members only. Can Edit means all internal users can edit. Can Read means internal users have read only. Choosing Can Edit or Can Read moves the article to Workspace. No access moves it to Private if it is not shared with an invited user.
Workspace visibility is a second switch: Everyone or Members only. Members-only articles stay out of the sidebar for other users. Those users can still find hidden articles with Ctrl/Cmd+K and $.
Internal or portal users can be invited with a chosen permission. Portal sharing is how a private nested article, or a Workspace article, is opened to a portal user. Customers on the portal are not paying users. A paying user is someone with backend access to create, view, or edit documents, or an HR employee record with no linked user.
Share to web generates a public URL. The Website app must be installed to share that URL. That requirement is why a pure internal wiki can stay on Knowledge alone, and a public page cannot. More actions on an article include Move To, Lock Content, Create a Copy (the copy lands under Private), Open Version History, Download PDF (the browser print dialog), Add to Templates, and Send to Trash.
| Setting | What it does | Where you use it |
|---|---|---|
| Can Edit | All internal users can edit | Company wiki in Workspace |
| Can Read | Internal users read only | Published-to-staff policies you do not want everyone rewriting |
| Members only (default access) | One of the three default access rights | A page limited to invited members |
| No access | Moves the article to Private if it is not shared with an invited user | Drafts and personal notes |
| Visibility: Everyone | Workspace article appears for internal users | SOPs the whole company should see in the sidebar |
| Visibility: Members only | Stays out of the sidebar; findable with Ctrl/Cmd+K and $ | A Workspace article you do not want browsed casually |
| Portal invite | Opens a private nested article or a Workspace article to a portal user | A customer or contractor who should read one tree |
| Share to web | Public URL; Website must be installed; set Article Published per article | Help Center pages |
How to publish a Help Center without exposing the wiki
Start from the audience, then the team, then each article. Internal SOPs stay on Workspace or Private with no public URL. Customer answers get their own nested articles under the Helpdesk article, and each of those articles is published on its own. Enabling the parent Help article does not publish the children.
On the Helpdesk team, set visibility to Invited portal users and all internal users (public). Turn on Knowledge under Help Center and choose the article. The default name is Help. Enabling any Help Center feature can install extra apps, and it turns on the Website Form. If the database is still One App Free, that install starts the 15-day trial described in the pricing section.
For each customer page, open Share, then Share to web, and leave it on Article Published. Confirm the Website app is installed, or the public URL is not available. Read the page as a visitor would: inserted views appear for someone who only has the URL when that person can access the inserted content. Keep order lists and project boards on internal articles.
Agents already in a ticket use the Knowledge bookmark to search. On the article, a clipboard can be sent with Send as message, or appended with Use as description. Design the public article for the customer and put the agent wording in a clipboard so the two texts stay aligned.
Version history has a Content tab and a Comparison tab, so a reviewer can see what changed before a public page is updated. Lock Content is available from the same actions menu once the wording is approved. Trash, covered below, is the retirement path.
Separate internal and customer trees
Put SOPs in Workspace or Private. Create the customer articles under the Helpdesk Help article. Do not treat a nested child as public because the parent is public.
Set the Helpdesk team gates
Visibility must be Invited portal users and all internal users (public). Enable Knowledge and select the article. Expect the Website Form to turn on, and expect extra apps when you enable Help Center features.
Publish every customer article
Set Share to web to Article Published on each article the customer should open. Install Website first, because Share to web needs it.
Add clipboards for agents
Store the repeatable reply in a clipboard. From the ticket, Send as message composes with that body. Use as description appends it to the ticket description.
Check the public URL
Open the URL without an employee login. Confirm the article text is visible and that embedded views stay limited to people who can access the source content.
Owners, lock, version history, and the 30-day trash
Knowledge does not assign a reviewer for you. The controls that exist are access rights, properties on a parent, Lock Content, version history, and trash. Put an owner property on the parent article so the nested articles under that parent share it. Finance owns the close checklist. Support owns the Help tree. Operations owns shipping and receiving.
Use version history before a large rewrite. The Content tab and the Comparison tab show the earlier version and the difference. Lock Content after a customer-facing article is approved so a casual edit does not go live on the public URL. When a product or policy changes, the owner updates the article, compares the version, and locks it again.
Send to Trash keeps an article for 30 days before permanent deletion. Restore is available from Open the Trash or the Trashed filter. Thirty days is the retention figure in the Odoo 19.0 documentation. Article count, storage, and version-history retention are unpublished, so plan cleanup around that 30-day trash window.
A first usable phase for a company of 20 to 100 people is a named owner per tree, a Workspace for internal SOPs, and a short Help Center built from the questions agents already answer. Flectic sets the timeline for that first phase in the written scope, with a fixed price. The phase includes the publish check on every nested customer article, not a pile of unpublished children under Help.
| Control | Where it is | Use it when |
|---|---|---|
| Properties on the parent | Inherited by nested articles under that parent | You want one owner across a topic tree |
| Lock Content | Article actions | A public answer is approved and should stay stable |
| Version history | Content tab and Comparison tab | You need to see what changed before you publish again |
| Create a Copy | Article actions; copy is placed under Private | You want a draft that does not overwrite the live page |
| Send to Trash | Restorable for 30 days from Open the Trash or the Trashed filter | A page is retired and you still want a month to undo that |
| Download PDF | Opens the browser print dialog | Someone needs a file copy of an approved article |
Odoo Knowledge pricing as of October 2026
Standard and Custom include all apps for one fee. Knowledge is not a separate per-app price. The Knowledge product page says the first app is free forever, including hosting and support, with unlimited users, until more applications are installed. That is One App Free: US$0 for one app on Odoo Online. Knowledge can be that single app.
A real Help Center installs more than Knowledge. Installing a new application on a One App Free database starts a 15-day trial. If no paid subscription is added, the database is no longer active or accessible when the trial ends. Choose Standard or Custom before you install Helpdesk and Website, because the trial is only 15 days.
As of October 2026, the US pricing card shows two figure pairs for Standard, per user per month, next to a Yearly control and a Monthly control: US$24.90 and US$31.10, and beside them US$31.10 and US$38.90. A footnote says the discount is valid 12 months for the initial users ordered. The card does not label which pair is the price after that discount. Custom shows US$49.00 and US$61.00, and beside them US$61.00 and US$76.20, on the same yearly and monthly controls. Custom includes all apps, Odoo Online or Odoo.sh or on-premise, Studio, multi-company, and the external API. Odoo.sh hosting is extra.
A Light User at US$8.90 includes read-only access to Knowledge, among other limited capabilities. Light User licenses are quoted by an Odoo advisor, not listed as a self-serve toggle on the pricing card. Editors still need a full user. Portal users such as customers are not paying users.
The Canada English pricing URL (odoo.com/en_CA/pricing) showed the same US dollar card on 5 October 2026. Use the USD amounts above for a Canadian company; Odoo did not print a Canadian dollar list on that page. Odoo's pricing page positions Knowledge against Notion and Helpdesk against Zendesk, and it does not publish Notion or Zendesk prices there.
Worked cost, assumptions stated. A 40-person company has 12 people who create and edit articles, 15 people who only read the wiki, and customers who use the portal. Portal customers add US$0. The 12 editors on Standard, using the pairs as printed, come to US$298.80 per month at US$24.90, US$373.20 at US$31.10, and US$466.80 at US$38.90. The same 12 editors on Custom come to US$588.00 at US$49.00, US$732.00 at US$61.00, and US$914.40 at US$76.20, before any Odoo.sh hosting. Fifteen Light Users at US$8.90 are US$133.50 per month, and that figure is an advisor quote, not a checkout button. If this company starts on One App Free and then installs Helpdesk, the 15-day trial starts.
Community 19.0, Success Packs, and who implements
The public Odoo 19.0 Community repository does not contain addons/knowledge. That GitHub path returns 404. The editions comparison lists a Knowledge row. Plan a Knowledge project on a licensed database that already shows the app, and do not schedule an install from the public Community 19.0 addons tree.
Odoo publishes Success Packs as hour bundles with a dedicated consultant. They are not a Knowledge-only package. As of October 2026, returning customers pay US$580 for Starter (4 hours), US$3,600 for Basic (25), US$7,000 for Standard (50), US$12,500 for Custom (100), and US$25,000 for Pro (200). New customers get 15% off the first pack only: US$493, US$3,060, US$5,950, US$10,625, and US$21,250 for the same hour buckets. Travel and custom-module maintenance are billed on top of the pack price.
A wiki or Help Center setup is usually a slice of those hours, not its own SKU. Odoo directs companies under 50 employees to Success Packs, companies over 50 employees to a local partner, and companies over 250 employees to contact Odoo.
Flectic implements Odoo and Microsoft Dynamics 365 for companies of 20 to 100 people in the US and Canada. The next step is a scoping call with Flectic, where we price the first phase against your article trees and your plan, using the Success Pack hours only as Odoo's published services menu. Our delivery is designed to deliver up to 3x faster, and Flectic stays after go-live.
Odoo Knowledge vs Dynamics 365 knowledge articles
Companies already buying Odoo can keep the wiki and the Help Center in Knowledge, next to CRM, sales, projects, and tickets. Insert view and Insert link pull a live Odoo view into an article, and the view still obeys the reader's access. Clipboard replies stay on the Helpdesk ticket. That is the reason to adopt Knowledge when the rest of the company works in Odoo.
The closest Dynamics 365 equivalent is Knowledge Management in Dynamics 365 Customer Service, also available in Dynamics 365 Contact Center standalone, on the KnowledgeArticle entity. Representatives create articles, mark them for review, and a reviewer approves or rejects. Approved articles can publish to the portal, show up in search, and be translated. Related approved translations can publish with the parent. Publishing can be immediate or scheduled, with optional expiration dates that remove the article from search when it expires. Authoring is in Customer Service Hub or Copilot Service workspace under Service, Knowledge Articles. Search uses the knowledge search pane or smart assist, with optional federated external providers.
Odoo's pricing page names Notion beside Knowledge and Zendesk beside Helpdesk, and it leaves their prices off that page. Use those names as the products Odoo expects you to compare, then judge the operational fit: live Odoo records and a Helpdesk clipboard, or a Microsoft case lifecycle with approval, translation, schedule, and expiration. Flectic scopes either path. Book a free discovery call if the choice is still open.
| Question | Odoo Knowledge | Dynamics 365 Customer Service |
|---|---|---|
| What you store | HTML articles in a sidebar tree | Knowledge articles on the KnowledgeArticle entity |
| Customer publishing | Share to web, Article Published, on each article | Approve, then publish to the portal, immediately or on a schedule |
| Review trail | Version history with Content and Comparison tabs; Lock Content | Mark for review, approve or reject, major and minor versions |
| Language and expiry | Publish each article you want customers to see | Translations can publish with the parent; optional expiration leaves search |
| Live operating data | Insert view or Insert link from another Odoo app | Search in the case workspace, including optional federated providers |
| Who it fits | A 20 to 100 person company running Odoo | A support team already working in Dynamics 365 Customer Service |
When Knowledge fits a 20 to 100 person company
Choose Knowledge when the company will run Odoo and the pain is repeated answers: month-end steps, onboarding, shipping exceptions, and the questions that already become tickets. The internal wiki can be the free app only while Knowledge stays the sole application. The moment you add Helpdesk or Website, budget Standard or Custom and treat the 15-day trial as a deadline, not a test environment you can ignore.
Choose Dynamics 365 knowledge articles when case handling already lives in Customer Service and you need the approval, translation, scheduled publish, and expiration lifecycle Microsoft documents. Choose a separate file tool when the problem is controlled files rather than HTML articles. Odoo Documents is the related app for that file problem; Knowledge remains the article library.
Read-only staff are the Light User conversation at US$8.90, sold through an advisor quote. People who write articles need a full user at the Standard or Custom pairs above. Portal customers who only read a published Help Center are not paying users. Confirm the database is not the public Community 19.0 tree, which does not ship addons/knowledge.
For a company of 20 to 100 people, a sensible first phase is one Workspace tree, one Help article with every customer child published on its own, clipboard text for the top ticket replies, and a named owner on each parent. Success Pack hours are Odoo's menu if you buy services from Odoo. Flectic will scope the same work on a call and stay after go-live.
List the pages staff already need
Write down the SOPs staff ask for every week and the customer questions that already become tickets. Those titles become the first articles and the first templates.
Pick the plan before you install Helpdesk
Knowledge alone can stay on One App Free at US$0. Installing Helpdesk or Website starts a 15-day trial. Put the 12-editor math, or your own headcount, next to Standard or Custom before that install.
Set rights, then publish article by article
Can Edit or Can Read for the wiki. Share to web, Article Published, for each customer page. Invite portal users only to the trees they should see.
Hand agents a clipboard
Put the approved reply in a clipboard. Train the team on Send as message and Use as description from the ticket, and on the Knowledge bookmark search.
Name an owner and a restore path
Properties on the parent carry the owner to nested articles. Lock Content after approval. Trash keeps a removed article for 30 days.
How Flectic can help
Flectic implements Odoo one app at a time on a single database, starting with the apps that remove the most manual work. Core operations (four to six apps, a basic data import, up to 25 users) has a planning range of $6,000 to $30,000, not a quote. Our Odoo implementation fits companies of 20 to 100 people in the US and Canada that want sales, stock and finance in one Odoo database. To start, book a free discovery call with Flectic.
Sources
Odoo Knowledge articles are a title plus an HTML body that can hold text, images, links, records from other models, and templates. Nested articles inherit the parent's access rights, and properties apply to the group of nested articles under the same parent.
odoo.comChecked 2026-10From-scratch creation offers Load a Template, Build an Item Kanban, Build an Item List, Build an Item Calendar, and Generate an Article with AI. Templates load from Browse Templates. Add to Templates promotes an existing article. Share to web needs the Website app. Portal users can be invited. Version history has Content and Comparison tabs. Trash lasts 30 days. Views insert from the cog menu. Search includes semantic search, Advanced Search, and Ctrl+K then ?.
odoo.comChecked 2026-10Sidebar categories are Favorites, Workspace, Shared, and Private. Knowledge powerbox commands are Index, Item Kanban, Item Cards, Item List, Item Calendar, Clipboard, Foldable Section, and Article. Default access rights are Can Edit, Can Read, and Members only. Can Edit or Can Read moves an article to Workspace. No access moves it to Private if it is not shared with an invited user. Workspace visibility is Everyone or Members only. Hidden articles can be found with Ctrl/Cmd+K and $.
github.comChecked 2026-10The Help Center is Helpdesk integrated with Forums, eLearning, and Knowledge. Team visibility must be Invited portal users and all internal users (public). Enabling a Help Center feature turns on the Website Form and can install extra apps. Knowledge on a team adds an Article field and a default article named Help. Publishing the parent does not publish nested articles. Clipboard on a ticket offers Send as message and Use as description, which appends. A new app on One App Free starts a 15-day trial, after which the database is no longer active or accessible if unpaid.
odoo.comChecked 2026-10Helpdesk team visibility options are part of the Help Center setup documented for Odoo 19.0.
odoo.comChecked 2026-10The Knowledge product page describes collaborative articles, public sharing, and links to Project, CRM, Sales, and Helpdesk, and states that the first app is free, including hosting and support, until more applications are installed.
odoo.comChecked 2026-10Knowledge features include internal and external sharing, a public URL, item views, clipboards, revision history, PDF export, and Unsplash images.
odoo.comChecked 2026-10As of October 2026, Standard shows US$24.90 and US$31.10 and also US$31.10 and US$38.90 per user per month beside Yearly and Monthly controls. Custom shows US$49.00 and US$61.00 and also US$61.00 and US$76.20. A footnote says the discount is valid 12 months for initial users ordered. The card does not label which pair is the post-discount price. Light User is US$8.90 and includes read-only Knowledge, sold via an advisor quote. Standard and Custom include all apps. Portal users are not paying users. Odoo.sh hosting is extra on Custom. Companies under 50 employees are directed to Success Packs, over 50 to a local partner, and over 250 to contact Odoo. The page positions Knowledge against Notion and Helpdesk against Zendesk without listing those vendors' prices.
odoo.comChecked 2026-10The Canada English pricing URL showed the same US dollar amounts as the US pricing card on 2026-10-05.
odoo.comChecked 2026-10-05Success Packs for returning customers are US$580, US$3,600, US$7,000, US$12,500, and US$25,000 for 4, 25, 50, 100, and 200 hours. New customers receive 15% off the first pack only: US$493, US$3,060, US$5,950, US$10,625, and US$21,250. Travel and custom-module maintenance are billed on top of the pack price.
odoo.comChecked 2026-10The editions comparison lists a Knowledge row. The fetched page did not expose Community versus Enterprise checkmarks.
odoo.comChecked 2026-10The public Odoo 19.0 Community tree does not contain addons/knowledge. That GitHub path returns 404.
github.comChecked 2026-10Dynamics 365 Customer Service includes Knowledge Management on the KnowledgeArticle entity, with a review and approve lifecycle, major and minor versions, translation, scheduled publishing, expiration, and search in the service workspace.
learn.microsoft.comChecked Existing guide source, retained for the Dynamics 365 comparison.Dynamics 365 knowledge articles can be published immediately or on a schedule, with optional expiration, and the knowledge workspace includes search and related article process steps.
learn.microsoft.comChecked Existing guide source, retained for the Dynamics 365 comparison.
Frequently asked questions
How do I use the same Odoo Knowledge library as an internal wiki and a public Help Center?
Keep employee procedures in Workspace, Shared, or Private, with Can Edit, Can Read, or Members only. Build the customer pages under the Helpdesk article, set the team visibility to Invited portal users and all internal users (public), and set Share to web to Article Published on every page a customer should open. The Website app has to be installed for the public URL. Nested articles keep their own publish setting, so employee pages and customer pages can both live in Knowledge.
Does enabling the Help article publish every nested article?
No. Checking Knowledge on a Helpdesk team adds an Article field, and Odoo supplies a default article named Help. Publishing that parent does not publish nested articles. Each customer-facing article needs Share to web set to Article Published. Enabling a Help Center feature also turns on the Website Form and can install extra apps.
Why does Share to web ask for the Website app?
Share to web generates a public URL, and the Website app must be installed to share that URL. An internal wiki can run on Knowledge alone. A public Help Center cannot, because the URL depends on Website. People who only hold that URL see inserted views when they can access the inserted content.
What happens to a One App Free database if I install Helpdesk or Website for the Help Center?
Knowledge can be the one free app, with hosting, support, and unlimited users, until you install more applications. Installing a new application on a One App Free database starts a 15-day trial. If you do not add a paid subscription, the database is no longer active or accessible when the trial ends. Standard and Custom then include Knowledge with the rest of the apps for one per-user fee.
Can portal customers read Knowledge articles without a paid user seat?
Portal users such as customers are not paying users. A paying user is someone with backend access to create, view, or edit documents, or an HR employee record with no linked user. You still choose what the portal user can open: invite them with a permission, or publish the article with Share to web. A public URL is not the same thing as an invite to the internal Workspace.
What can a Light User do in Knowledge?
As of October 2026, a Light User at US$8.90 includes read-only access to Knowledge, among other limited capabilities. Odoo sells that license through an advisor quote, not as a self-serve control on the pricing card. People who create or edit articles need a full Standard or Custom user. Light User is the seat to quote for staff who only consult the wiki.
Is Knowledge in Odoo Community 19 or only on a licensed database?
The public Odoo 19.0 Community repository does not contain addons/knowledge. The GitHub path returns 404, so you should not plan to install Knowledge from that tree. The editions comparison lists a Knowledge row. Confirm the app is available on the database you will subscribe, then use Standard, Custom, or One App Free while Knowledge remains the only app.
How do I insert a sales or project view into an article without showing it to people who lack access?
On the source view, use the cog menu and choose Knowledge, then Insert view in article or Insert link in article. Users who cannot access the view cannot see it inside the article. The same rule applies to a public URL: someone with only the link sees inserted views when they can access that content. Keep pipeline and project boards on internal articles, and keep customer pages as written answers plus clipboards.
How long does a trashed article stay recoverable, and how do I restore a version?
Trash keeps an article for 30 days before permanent deletion. Restore it from Open the Trash or the Trashed filter. Version history is separate: Open Version History shows a Content tab and a Comparison tab so you can review an earlier edit. Create a Copy places a duplicate under Private if you want a draft beside the live article.
Where can I get implementation services, and how much does it cost?
Odoo Success Packs, as of October 2026, are US$580 to US$25,000 for returning customers (4, 25, 50, 100, or 200 hours) and US$493 to US$21,250 for a new customer's first pack after 15% off. Travel and custom-module maintenance are extra, and the pack is not a Knowledge-only product. Odoo points companies under 50 employees to those packs, companies over 50 to a local partner, and companies over 250 to contact Odoo. Flectic scopes the wiki and Help Center for companies of 20 to 100 people in the US and Canada, with a fixed price for each phase in a written proposal.