This module assigns company to the user and its partner newly created through portal signup.
Odoo's standard behavior when a new portal user signs up:
- User's company is taken from the template user.
- Partner which links to the new user does not have a company assigned.
This behavior is problematic under multi-company, multi-website settings where partners should be seggregated between the companies, and this module intends to fix this issue.
auto_awesome What this module does
AI-generated from the code · Odoo 15.0When a new portal user signs up, this module assigns the current company to both the new user and their linked contact, instead of leaving the contact without a company.
In standard Odoo, a portal signup creates a user whose company comes from the template user, and the contact linked to that user has no company at all. In a multi-company or multi-website setup this mixes contacts between companies.
This module changes that behaviour on the res.users model:
- During signup, the new user is created with the company of the current website/company as both their main company and their allowed company.
- After the user is created, the contact linked to that user is also given the current company.
There are no new menus, screens, buttons or reports. The change happens automatically in the background when someone registers through the portal signup form. It only affects the signup flow and the res.users model, and it requires the standard signup module (auth_signup) to be installed.
Depends on
Models and fields (1)
- res.users · extends an existing model
Text generated by AI (DeepSeek) from reading the Odoo 15.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: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 15.0
Confirmed on 2026-11-03 in branch 15.0 of OCA/server-auth.
terminal Installation and usage
No verified informationInstallation 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.