This module allows to restrict surveys per company.
auto_awesome What this module does
AI-generated from the code · Odoo 19.0Lets you assign each survey to a specific company and automatically hides surveys that belong to other companies, so each company only sees its own surveys.
This module adds company ownership to surveys. On the survey form, a new Company field appears right after the Responsible field, but only for users who can work with multiple companies.
A security rule is added on surveys: users only see surveys that belong to one of their allowed companies, plus surveys that have no company assigned. Surveys without a company stay visible to everyone, so existing surveys are not hidden after installing the module.
When someone opens a survey through its public link, the module makes sure the survey and the related answer are handled under the survey's own company. This keeps company-specific settings, such as email senders or templates, consistent for respondents even if the visitor is not logged in.
The module touches the survey.survey model and the survey form view. It does not add new menus or reports; the change is visible directly in the existing survey configuration screen and in the list of surveys each user can access.
Depends on
Models and fields (1)
- survey.survey · extends an existing modelcompany_id
Text generated by AI (DeepSeek) from reading the Odoo 19.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 3 confirmed, 6 with no information of 9 versions.
Sources · Odoo 19.0
Confirmed on 2026-11-03 in branch 19.0 of OCA/survey.
terminal Installation and usage
OCA documentation · Odoo 19.0Usage
Source · Odoo 19.0To restrict a survey to a certain company:
- Go to to Surveys and select the survey you want to edit.
- Set the desired company.
Only the users in that company will be able to access the survey.
No verified information in OCA: Installation, Configuration.
Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.