Minimum rights to use Set Regarding
Tuesday, April 29th, 2008When it comes to the security roles I like to use roles based on a functionality instead of based on business roles.
In most companies employees with a similar business roles are allowed to do different things in the MS CRM system. Making exceptions is hard when you use role based security roles. Functionality roles on the other hand can be easily combined to create the right level of authorization.
A functionality based role can be, ‘Maintain Accounts’. A user with this role is allowed to read, write, append, append to, share and assign accounts on Business Unit level. Combined with ‘Maintain Contacts’ or ‘Create and Delete Account’, etc, gives a complete set of functionality.
Next to these clear functionality roles a user needs in general a basic role to be able to use the MS CRM basic functionality. For example the ‘Set Regarding’ functionality to link a email to a record in MS CRM.
When designing the basic use role I came across some oddities I couldn’t directly explain. Users with the basic role should be allowed to use the ‘Set Regarding’ functionality, but for some reason I couldn’t get it to work. So I created a new organization with 1 custom entity and puzzled until I found the minimum rights to use the ‘Set Regarding’ functionality.
That’s when I came to the conclusion you must have read rights on Account, Contacts, Leads and Opportunities, to regard an email to a custom entity.
I put the complete set of rights in the pictures below (click the pictures to see an enlargement):
