[IMP] General: Multi-Company Limitations
closes odoo/documentation#10418
X-original-commit: bed068f95a
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
Signed-off-by: Jessica Rogers (jero) <jero@odoo.com>
Co-authored-by: ksc-odoo <73958186+ksc-odoo@users.noreply.github.com>
This commit is contained in:
parent
6cc002d59c
commit
b76bb3b610
@ -51,11 +51,13 @@ except under the following circumstances:
|
|||||||
Mitchell Admin has multiple companies enabled, but the current company is `My Company (Chicago)`.
|
Mitchell Admin has multiple companies enabled, but the current company is `My Company (Chicago)`.
|
||||||
When he creates a new product record, the :guilabel:`Company` field is left blank by default.
|
When he creates a new product record, the :guilabel:`Company` field is left blank by default.
|
||||||
|
|
||||||
When he creates a new sales team, the :guilabel:`Company` field automatically defaults to `My
|
When a new sales team is created, the :guilabel:`Company` field automatically defaults to `My
|
||||||
Company (Chicago)`.
|
Company (Chicago)`.
|
||||||
|
|
||||||
Sharing data
|
.. _general/sharing-data:
|
||||||
============
|
|
||||||
|
Share data
|
||||||
|
==========
|
||||||
|
|
||||||
In a |mcd|, certain records are able to be utilized by all of the companies (or several, based on
|
In a |mcd|, certain records are able to be utilized by all of the companies (or several, based on
|
||||||
permissions).
|
permissions).
|
||||||
@ -113,3 +115,26 @@ To keep their database from becoming overly complex, the furniture company does
|
|||||||
entirely new company. Instead, they can take advantage of existing features, such as :doc:`analytic
|
entirely new company. Instead, they can take advantage of existing features, such as :doc:`analytic
|
||||||
accounting <../finance/accounting/reporting/analytic_accounting>`, and multiple warehouses, to
|
accounting <../finance/accounting/reporting/analytic_accounting>`, and multiple warehouses, to
|
||||||
manage the new product line, without having to overly complicate transactions.
|
manage the new product line, without having to overly complicate transactions.
|
||||||
|
|
||||||
|
Limitations
|
||||||
|
===========
|
||||||
|
|
||||||
|
In some instances, a |mcd| may *not* be the best option, due to potential limitations.
|
||||||
|
|
||||||
|
Access rights
|
||||||
|
-------------
|
||||||
|
|
||||||
|
A user's access rights are configured on a database level. If a user has access to more than one
|
||||||
|
company in a |mcd|, their access rights are the same across every company.
|
||||||
|
|
||||||
|
Shared records
|
||||||
|
--------------
|
||||||
|
|
||||||
|
Individual records are either :ref:`shared <general/sharing-data>` between all companies, or belong
|
||||||
|
to a single company.
|
||||||
|
|
||||||
|
PDF Reports
|
||||||
|
-----------
|
||||||
|
|
||||||
|
Some customizations, specifically for PDF reports, apply to all companies. It is not always possible
|
||||||
|
to separate reports for individual companies.
|
||||||
|
Loading…
Reference in New Issue
Block a user