Skip to main content

Use ModuleCare and qualified support

Use this guide for an eligible project's support scope or an available ModuleCare result. ModuleCare support and change advice are separate from ordering a new module through Module Studio.

Before you start​

Sign in as the registered project owner. Starting a qualified support request requires an active project and an existing support enrollment. Coverage depends on the reviewed Odoo version, edition, hosting arrangement and environment.

Verification scope: the live Qualified support entry was checked, but the account had no owned project or request form. Populated cases and ModuleCare decisions below are source-reviewed instructions for eligible projects. If the corresponding controls are absent, use your agreed support channel.

Request and follow a support review​

  1. Open My account and choose Qualified support, or open Qualified support directly.
  2. If your project shows Request scope review, complete its Customer-safe summary. Include the expected and actual result, affected environment, reproduction steps and time. Choose the relevant category and severity, then use Request staff review when ready to submit. Keep credentials and private customer records out of the summary.
  3. When Corvus has reviewed the request, read the proposed scope, coverage, environment and expiry. If a separate Topology enrollment offer is shown, review its hosting arrangement and scope before deciding whether to approve it.
  4. If the reviewed case offer is correct, use Approve this exact quoted coverage and scope, then Approve support request. Ask for a revised review if anything is wrong or has changed. The initial request does not approve additional work or an operational change.
  5. Follow Decision, Last observed operation and any Published guidance. Use Refresh exact status where offered. A queued action is not a completed outcome. If the console shows Managed Support current state, use Open the Odoo owner Support workflow for its approval steps.
  6. If diagnostic access is requested, review the separate access workflow and its scope, expiry and verification requirements. A support case alone does not grant access. Use the offered revoke or case-close controls when withdrawing an approval, and verify the resulting status.

Review a ModuleCare result, when provided​

  1. Open the result link supplied for your project, or Changes and compatibility in an available project console.
  2. Review the summary, risk, revision and evidence state. Choose Prepare safely, Hold or Request help only when offered and appropriate to that current result.
  3. Read the returned decision and later lifecycle status. Refresh changed or expired evidence before making another decision. Preparation or advice is separate from deployment; it does not directly change live Odoo.

Expected result​

An eligible request is recorded for review. After an exact reviewed scope is approved, you can follow its decision, available guidance and observed outcome. Diagnostic access and technical operations retain separate authorization and status.

Troubleshooting and limitations​

  • No project or form: check the owner account and ask Corvus to confirm enrollment and eligibility.
  • Unavailable scope, receipt or approval: the service, ownership, coverage or offer may have changed. Obtain a current review; do not assume a rejected approval succeeded.
  • No result: use qualified support or the agreed support route. Missing evidence is not a successful compatibility check.
  • Unclear access or operation status: use Support handoff with the reference and redacted message. Do not send credentials to resolve a missing approval.

Support may provide guidance, evidence review, escalation or separately approved diagnostics. This guide does not establish automatic repair, upgrade or deployment, universal version coverage or a response-time commitment.

Guide version 1.0, verified 28 October 2026 (UTC). The Qualified support heading and qualification explanation were checked live. No request, approval, diagnostic session or ModuleCare decision was submitted.