Corvus VetSuite: getting started

Corvus VetSuite connects client contacts, animal patients, appointments, and clinical visit records. This starter set explains how to prepare staff access and use the supplied administrative controls. Clinical decisions remain the responsibility of qualified professionals.

These guides review the Odoo 20 source and supplied forms. They do not establish a completed installation, a tested browser journey, or Community or Enterprise runtime acceptance. Confirm the supported edition, included modules, and rollout scope for your deployment before use.

Choose the modules for the work

The reviewed source contains 26 addon manifests. Corvus VetSuite — Core provides the application menu, roles, practice sites, and configuration; installing Core alone does not install the whole suite.

Work	Relevant addons and dependencies
Practice access and configuration	Core depends on Odoo Mail, Employees, and Units of Measure.
Client and patient registration	Clients depends on Taxonomy and Portal; Taxonomy depends on Core.
Visits	Encounters depends on Housing, Inventory, Product Expiry, and SMS; Housing depends on Clients.
Staff appointments	Agenda depends on Encounters, Calendar, Website, and Portal.
Veterinary sales records	Billing depends on Encounters, Sales, Inventory, and Accounting.

Ask your implementation administrator to install the required modules and dependencies. A declared Portal or SMS dependency does not mean that customer access or a messaging provider is ready. This guide does not configure those services.

Assign the right responsibilities

The native Corvus Access choices are cumulative: Front Desk includes Support, Clinician (DVM) includes Front Desk, and Practice Manager includes Clinician (DVM).

Role	Intended starter responsibility
Support	Read accessible patient and reference records.
Front Desk	Register patients and maintain reception records, subject to contact, company, and site permissions.
Clinician (DVM)	Use clinical documentation controls; visit actions can additionally require the assigned veterinary employee.
Practice Manager	Configure practice sites and catalogs. This role also inherits the clinical and reception roles.

An employee's Practice Roles tags and Veterinary Physician flag are separate from the user's Corvus Access permissions. A tag does not grant application access. The flag identifies employees offered in veterinary staff selections; it does not establish professional credentials.

Prepare one practice site

Use a Practice Manager for site configuration. User administration, company settings, and employee maintenance also require the corresponding ordinary Odoo permissions; Practice Manager alone is not a promise of those permissions.

1. Open Corvus VetSuite → Configuration → Practice Setup → Practice Sites. Review the supplied Main Practice record before creating another site. Its supplied code is MAIN and its timezone is UTC; check these against the actual organization.
2. Set the site's Name, Code, Company, and Timezone. A code must be unique within its company. Keep the site Active when it should be selectable for new work.
3. Review Site Address and Operating Calendar, where used. Each must belong to the same company or be shared. The timezone describes the site's operating schedule; also verify staff timezone settings before using appointments.
4. On Access, review Allowed Users. An empty list allows Corvus users in that company; a populated list restricts the site to its listed users. Assign the intended staff before relying on that restriction. Company access still applies.
5. Have an authorized user administrator who also has Practice Manager access review each user's Corvus Practice Sites section on Access Rights. Set Allowed Practice Sites and Default Practice Site consistently with the user's companies. If the allowed-site list is populated, the default must be in that list.
6. With the intended company selected, an authorized settings administrator can open Corvus VetSuite → Configuration → Settings and review Default Practice Site and Default Weight Unit. New site-scoped records use the user's default site when it belongs to the current company, otherwise the company default. Check the actual value on each record.
7. Before creating real records, have the reception user open Corvus VetSuite → Clients → Clients and Patients. Check that intended records are visible and that access does not expose another restricted site. Have the clinical team separately confirm employee/user linkage and the Veterinary Physician flag for its assigned veterinarians.

Expected result: a known company and practice site, a deliberate access list, and staff accounts with the roles needed for their work. This is a setup checklist to carry out and verify in your deployment, not a claim that the checks have already passed.

Try a fictional setup

In an authorized training environment, prepare Training Clinic, code TRAIN, with the organization's training company and intended timezone. Assign a fictional reception account to that site and give it Front Desk access. Confirm the account can open the client and patient menus, then continue with client and patient registration. This guide creates no accounts or records for you.

Troubleshooting and limits

Problem	What to check
Corvus VetSuite menu is absent	Confirm the relevant modules are installed and the user has a Corvus Access role.
Configuration or Practice Sites is absent	Check Practice Manager access and the ordinary permissions required for the operation.
A site or patient is missing	Check enabled companies, the site's Allowed Users, and any Archived filter.
Default site is rejected	Check its company and, when populated, the user's allowed-site list.
A veterinarian is unavailable for selection	Have the responsible administrator check the employee record and Veterinary Physician flag. Do not solve this by granting unrelated roles.

The starter guides cover software records. They do not qualify medical protocols, provider delivery, customer portal access, payment processing, report printing, data migration, or a complete production rollout.

Choose your next task

1. Register a client and patient and verify the patient reference, company, site, and initial authority.
2. For that existing patient, book an appointment and prepare a consultation visit. This path ends at administrative handoff to the clinical team; it does not complete treatment or create a confirmed prescription.

If the authorized clinical workflow has already supplied a Confirmed prescription, an operator with the required clinical and Sales permissions can separately prepare a draft quotation from that existing prescription. Check the guide's Sales permissions, matching payer context, and all three saved billing opt-outs first. The procedure stops at quotation review, before confirmation, delivery, invoicing, or payment.

If the troubleshooting checks do not resolve the blocker, prepare a support handoff with the version, installed addon, staff role, screen, record state, and exact redacted message. Do not include client details, patient records, or clinical notes.