Assigning mass security roles to users in D365 CE

When faced with the configuration of a D365 CE implementation with a large number of users, we may think that we are going to spend a lot of hours doing repetitive work when we register the users and configure their security roles, thinking that there is no obvious option to select them in bulk by filtering, making the case worse if they depend on a varied selection of roles among them.

There are two main configuration scenarios: one in which the security roles of these users are also highly dependent on the business unit they are associated with, or another scenario in which they are grouped by different characteristics that are different from their business units.
In either of these two scenarios, we would act in the same way: working with the team table.

Within the teams, if we pay attention to the advanced configuration screen, if we are still working with the classic configuration, we will see how we can find the assignment of security roles to the teams:

If we configure the teams from the Power Platform administration, we will see that when we create a team, it will ask us to apply a security role to the team that we create:

And if we want to assign roles to a team, it is also possible to do so from the top menu, just like in the classic configuration:

But what is the purpose of assigning a security role to teams? As you may have guessed (or read in the title), what will happen when adding users to these teams is that they will inherit the security roles of the teams they are part of, so it will only be necessary to add these users to the groups and it will no longer be necessary to assign them a security role individually, which would solve the second scenario we mentioned at the beginning of the article.

In addition to what has already been explained, there is a standard behaviour that affects teams within the CRM. The system, when you generate a new business unit, automatically creates a team associated to that business unit, to which it adds by default all the users belonging to that business unit, so we would solve the first scenario in this way, thus managing to assign all the users in an agile and error-free way as opposed to assigning them individually.

See you next time!