- The article discusses the need for a read-only system admin role for specific internal purposes or audit requirements in Microsoft business applications like Dynamics 365.
- It suggests testing the read-only requirement with existing Auditor roles before creating a new security role.
- If the out-of-the-box roles cannot fulfill the requirement, the article recommends creating a new read-only role using two approaches.
- The first approach is to create a new role and add all view privileges to the role, and then test it.
- The second approach is to add all display and output menu items using a "begin with" filter and giving read, create, and update permissions.
- It is important to remove all display menu items related to security configuration once all display and output menu items are added.
- The article also mentions that any ISV and custom objects can be controlled and tested to create a read-only role.
- Overall, the article provides guidance on how to create a read-only system admin role for specific purposes or audit requirements in Microsoft business applications like Dynamics 365.
Registered users can view the full text for FREE!
Sign In Now!
