This was a question we were recently asked by one of our clients, and the answer is – Yes, role-based forms can be used to determine write access based upon the security role of the user. In Microsoft Dynamics CRM 2011 the read-only property of an attribute can be changed per form. Therefore, a number of forms may be created with similar fields but with different access privileges to those fields based on the user’s security role. Each of these forms can be assigned to a single or multiple security roles, thus restricting the form/field access to only the users with assigned security roles.
This is an alternative to setting up field-level security on a number of fields on the form. In the following example the “Vice President of Sales”
does not have write access to the “Winning Carrier,” “Winning Carrier Rate,” “Estimated Members,” and “Estimated Contracts” fields; while “Vice President of Marketing” does have the write access. To make this happen create two forms, each having the fields mentioned above. In the form for “Vice President of Sales” mark these fields as read-only and assign the security role to the form as “Vice President of Sales.” Whereas in the form for “Vice President of Marketing” leave these fields as writable and assign the security role to the form as “Vice President of Marketing.”
Follow the screenshots for “How to make an attribute read-only on the form?” and “How to assign security roles?”
How to make an attribute read-only on the form?
Repeat this process for all the attributes required to be read-only.
How to assign security roles?
Repeat this process for each form for different security role/roles.
Related PowerObjects blogs:
Microsoft Dynamics CRM 2011 – Role Based Forms
Field-Level Security Out-of-box in Microsoft Dynamics CRM 2011
MSCRM 2011 just keeps getting better – if there is anything the MSCRM Experts and PowerObjects can do please reach out.