Creating a role, System Administration Light

(0) Share

Report

Posted on by Lasse Jamt

Hi guys,

Sorry for the bad title but I will try and explain it better here.

I have a customer that want 20 Enterprise licenses. However they do not want 20 workers having full access with setup, parameters and so on.

So what they want me to do is as follows:

- Create 1 role with full access but without any setup for all of the modules. Are there any easy way for me to give full access but without setup? Or an easy way of removing all of the menu items in setup if they come up.

Thanks.

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (2)

Verified answer

Vilmos Kintera 46,149 on at

Like (1)

Report

There is no easy way, you have to create a custom role with all Privileges included, and you have to investigate which one might provide create/update/delete access to tables that you consider as setup and those should be excluded.

Some privileges obviously will need access to parameter tables in order for the system to function.

Was this reply helpful? Yes No
Verified answer

André Arnaud de Cal... 300,911 Super User 2025 Season 2 on at

Like (0)

Report

Hi Lasse,

Vilmos is correct about creating a new role. The system administrator role is a special one and does not have duties/privileges linked, but ignores all security.

So have to create the role from scratch. Note that usually it would be recommended to include Duties instead of Privileges. In this case the privilege option might prevent the Segregation of Duties alerting on this role (if you are planning to use this feature).

Have also a look at the next thread with a statement related to contents of standard privileges: community.dynamics.com/.../583881

So you might need new privileges to fully support your requirement.

Was this reply helpful? Yes No
Lasse Jamt 45 on at

Like (0)

Report

Okey thank you for your answer.

Too bad there's no Security Development Tool in Dynamics 365 Operations.

Was this reply helpful? Yes No
Lasse Jamt 45 on at

Like (0)

Report

I've never understood why you should recommend Duties. Never had any problems using privileges for the most part. And the customers don't need any Logic With the content of roles ( since they always want me to do it for them ).

Thank you for your answer.

Was this reply helpful? Yes No
André Arnaud de Cal... 300,911 Super User 2025 Season 2 on at

Like (0)

Report

Hi Lasse,

Duties are grouping multiple related privileges to perform a certain task. If you want to be able to have an overview on what access is granted, the duties provides better overview. One duty in stead of sometimes 20 privileges. That makes a difference in overview when a role would need lets say 30 duties. Imagine how many privileges are then used on the role.... Reviewing the role might become unwieldy. Also the duties can be used for the Segregation of Duties like mentioned above. It is not checking on conflicting privileges.

For the role you are creating now, I would probably also add the privileges in detail; just to prevent SoD conflicts.

Was this reply helpful? Yes No

Community site session details

Creating a role, System Administration Light

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

Featured topics

Product updates

Community site session details

Creating a role, System Administration Light

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

Featured topics

Product updates