Best Practice for including Security Roles in a Solution?

(0) Share

Report

Posted on by ghdunn

235

We currently include all elements of our Dynamics 365 App in a packaged solution, including custom Security Roles. Whenever we have to make a change to those roles we do so first in the solution in the Development environment and then release into Production environment.

We are just discussing the option of configuring those security roles separately, only in the Production environment, so we can hand over configuration to users rather than make it a dev task. This might increase flexibility and reduce dependence on dev resources and a release process.

Does anyone have any thoughts on the pros and cons of doing this? Or could anyone point me at any references or resources for this kind of environment/solution trade off?

Thanks

Ged

All responses (2)

Nya 29,060 on at

Like (0)

Report
Copy link

Link copied!

Hi Ged,

In fact, the pros and cons are obvious in your description of the problem, the original solution is safer and easier to manage but more cumbersome, while the new solution is more flexible.

Ultimately, it depends on what you value more in terms of safety and convenience.
ghdunn 235 on at

Like (0)

Report
Copy link

Link copied!

Hi Nya...many thanks. I suppose I was looking for more than the one or two thoughts that I had, based upon the experience of the forum. I have been searching for a dedicated admin blogger or community of practice. Even this forum relies on simply an admin tag. I was just trying to use this specific question as a way of hooking into a broader and more expert source of best practice.

Any further help or thoughts would be appreciated.