Introduction
The Odoo Multi Company Access Error appears when a user attempts to access a record that belongs to a different company within a multi-company environment.
This issue is common in organizations running multiple legal entities inside a single Odoo database. Even when users have the correct functional permissions, Odoo may block access if company rules restrict visibility.
This guide explains why multi-company access errors occur and how to resolve them safely.
What Is a Multi-Company Access Error in Odoo?
Odoo supports multiple companies within the same database. Each record can be linked to a specific company via the company_id field.
When multi-company mode is enabled:
- Users can only access records belonging to their active company
- Record rules automatically filter records by company
- Certain models enforce strict company separation
If a user attempts to open or modify a record outside their active company context, Odoo blocks the action.
The error usually appears in the UI layer and may resemble:
You are not allowed to access this document.
Common Causes of Odoo Multi Company Access Error
1. Wrong Active Company Selected
Users can switch companies from the top-right company selector.
If the wrong company is active, related records become inaccessible.
2. Record Belongs to Another Company
A record may have:
company_id = Company B
While the user is operating under Company A.
Odoo prevents cross-company access by default.
3. User Not Assigned to All Required Companies
Users must be explicitly assigned to each company they are allowed to access.
If not assigned, access is denied even if the company selector is available.
4. Record Rules Enforcing Company Isolation
Many models include automatic record rules such as:
[('company_id', 'in', user.company_ids.ids)]
If the record’s company is not included in the user’s allowed companies, access is blocked.
5. Shared Records with Company-Specific Fields
Some records may appear shared but contain company-dependent fields that trigger restrictions.
This is common in accounting modules.
How to Fix Odoo Multi Company Access Error
Step 1 – Check Active Company
Switch the active company from the top-right menu and try accessing the record again.
Step 2 – Verify Record’s Company
Enable developer mode and inspect the record’s company_id.
Confirm it matches the user’s active company.
Step 3 – Assign User to the Correct Companies
Go to:
Settings → Users & Companies → Users
Ensure the user is assigned to all necessary companies.
Step 4 – Review Record Rules
Navigate to:
Settings → Technical → Security → Record Rules
Check rules that filter by company_id.
Be cautious when modifying company-related record rules.
Step 5 – Review Multi-Company Configuration in Modules
Some modules enforce strict company segregation.
Ensure module settings align with your operational model.
How to Prevent Multi-Company Access Issues
- Clearly define company structure before deployment
- Assign users carefully to relevant companies
- Avoid manual changes to company_id in production
- Test workflows under each company context
- Document cross-company business processes
Multi-company setups require disciplined configuration. Poorly structured company assignments are one of the most frequent sources of permission-related errors.
How Dasolo Structures Multi-Company Environments
Multi-company access errors usually arise when record rules, company-dependent fields, and user company assignments are not fully aligned. While Odoo supports complex multi-entity setups, small configuration gaps can quickly block legitimate operations.
At Dasolo, we review multi-company environments by focusing on:
- Company visibility settings
- Record rule domain filters
- Shared vs. company-specific records
- Integration users operating across entities
Designing clear company boundaries and consistent access logic helps prevent recurring cross-company conflicts.
Conclusion
The Odoo “Multi Company Access Error” occurs when a user attempts to access data outside their allowed company scope. Although the restriction is intentional, misaligned configuration often causes unnecessary disruptions.
By carefully reviewing company assignments, record rules, and shared resource settings, developers can eliminate recurring access conflicts. A well-structured multi-company architecture ensures secure data separation while maintaining operational flexibility across entities.