Business Unit in MS CRM

                 Below are the some of the points about Business unit

1. The organization (also known as the root business unit) is the top level of a Microsoft Dynamics 365 business unit hierarchy. Dynamics 365 automatically creates the organization when you install or provision Dynamics 365. You can’t change or delete the organization name.
2. You can’t change the name of a business unit or delete a business unit after it has been created. You can disable a business unit or change the parent, however. When you disable a business unit, all users and teams associated with the business unit are also disabled.
3. Changing the parent business removes security roles for users and teams associated with the business unit. You must reassign them.
4. You can change the business unit for an individual facility, equipment, or user. By changing the business unit for a user, you remove all security role assignments for the user. At least one security role must be assigned to the user in the new business unit.
5. You can delete a business unit to completely remove it from Microsoft Dynamics 365.

                 Before deleting a business unit, be sure to consider the following:

• Deleting a business unit is irreversible.
• The records owned by the business unit are deleted at the same time you delete the business unit.
• You can’t delete a business unit until you delete any associated users, teams, and child business units.

6. You can assign a different parent business to a business unit to accommodate changes in your business requirements. When you reassign a business unit, any child business units are also reassigned with it.
7. By default, when you create a user the user has read and write access to any data for which they have permission. Also, by default, the user client access license (CAL) is set to Professional.

                 Access mode. This setting determines the level of access for each user.

• Read-Write access. By default, users have Read-Write access that allows them access to data for which they have appropriate permission set by security roles.
• Administrative access. Allows access to areas that the user has appropriate permission set by security roles but doesn’t allow the user to view or access business data typically found in the Sales, Service, and Marketing areas, such as accounts, contacts, leads, opportunities, campaigns, and cases. For example, Administrative access can be used to create Dynamics 365 administrators who can have access to perform a complete variety of administrative tasks, such as create business units, create users, set duplicate detection, but cannot view or access any business data. Notice that users who are assigned this access mode do not consume a CAL.
• Read access. Allows access to areas for which the user has appropriate access set by security role but the user with Read access can only view data and can’t create or change existing data. For example, a user with the system administrator security role who has read access can view business units, users, and teams but can’t create or modify those records.