5.1. Business Units and User Security

Your implementation of Microsoft Dynamics CRM 4.0 requires you to define an Organization name during the installation, which creates a root Organization Business Unit, and then allows you to create child Business Units through the Business Unit administration screens. If you do not research how this structure will be used, you may be tempted to create a structure that closely resembles your organization hierarchy. In most implementations, this would not be a recommended approach for one or more of the following challenges it may represent:

• Security is tied to the Business Unit structure. If set up incorrectly, it can create usability or access issues.

• Once in place, some elements of the Business Unit structure cannot be changed without a reinstall (detailed next).

• A complex Business Unit structure increases maintenance and administration unnecessarily if based solely on the organization structure and not needed for specific security roles.

• Business Unit structure does not allow for the ability to manage information related to the company structure. Custom entities may be an easier approach to manage this requirement if needed.

• Using only Business Units to define security may lead to developing an overly-complex structure that limits the solution in other areas. There are other options for providing user access in conjunction with Business Unit-based security including Teams and sharing.