What is the purpose of the Root Business Unit?

(0) Share

Report

Posted on by Polestar

100

I understand that the Root Business Unit gets created on setup and is usually the organisation's name. However it is not a parent or child business unit and exists all on its own. So why does it exist at all and what is it used for? I'm assuming its used to hold users that are not in any other BU but have special rights such as System Admins... is this correct?

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (2)

Verified answer

Karth on at

Like (0)

Report

The Business Unit is the primary component of the security structure in CRM and is closely associated with the Security Roles and Users. When you install CRM, you need to have a user (Administrator) to perform administrative tasks. Because the business units drive the security in CRM, the internal records, forms and metadata have to be associated with to be associated with a parent or a primary business unit.

It’s like a start-up organization and the administrator is like a founder of the org. You first name an organization, identify the structure of the org, add mass to the org. Once you have done your prelims, you will add additional business units to the org, and at some stage, if you are bored you would even restructure it :-)

Was this reply helpful? Yes No
Polestar 100 on at

Like (0)

Report

Hi karth

Thank you for the reply. I now understood it perfectly. I also want to ask if the names of Security Roles have to be unique in the application. For example, can I two roles both named "Customer Service Rep" but with totally different permissions and assigned to different BUs?

Was this reply helpful? Yes No
Verified answer

Nuno Costa 1,300 on at

Like (0)

Report

Hi Polestar,

Yes you can have same name on different BU with different permissions.

Was this reply helpful? Yes No
Suggested answer

Eber 165 on at

Like (0)

Report

Hi Polestar,

Did you create others BU and worked with right access? Root Business Unit ensure all users will be part of a Business Unit and you can be able to define your desired organization structure. And, if the system administrator is not add on the root of the business unit, it won't be able to assign a security role for users on business units.

When you work with others BUs and with various security roles then that makes sense.

Best regards,

Éber Gustavo

Was this reply helpful? Yes No
Suggested answer

Karth on at

Like (0)

Report

You can have the same name for the Security Role with totally different permissions and assigned to different BU's. But to avoid confusion, it is recommended that you have a identifier for the name of the security role in each BU.

The principal is when you create a security role in the root BU or the parent BU, the security role propagates to all the child BU's. If you have a security role that is very specific to a BU, the you create it at that BU level instead of creating it at the parent BU level.

So, say you have created a security role called "CSR" at the root BU level, the system allows you to create a "CSR" role at a child BU level. Just that you will see two roles with the same name in the child BU. This could lead to a lot of confusion while assigning roles to the user.

Was this reply helpful? Yes No