You’re offline. This is a read only version of the page.
305
Hi all
Is there any formal reason why you should use a Role to determine the account manager function, rather than use the Owner property?
I'd prefer to use a Role, as we'll use other Roles for various reasons (Technical Lead, etc) so it makes sense for them all to be there. We also *may* foresee having two account managers for larger clients.
However the Owner field is so easy to use and access, and can be seen on page one of each account, and is always available views. It seems much easier to use the Owner field. However it does prevent us from having multiple account managers.
Thoughts? What are you all doing?
Olly
Hi partner,
A security role defines how different users, such as salespeople, access different types of records. It's a list of users with the same permissions follow your business requirement.
An owner is only a field which on behalf of the user who created (or be assigned) the record. The owner may be salesperson who has many accounts, so it's not a good way to use owner field to be salesmanager.
If you use roles to determine the account manager, you could have multiple account mangaers (a role contains many users), and you could configer the permissions of the role, like "read, edit, delete, create" of an entity.
Here is the DOC about security role for your reference.
https://docs.microsoft.com/en-us/dynamics365/customer-engagement/admin/security-roles-privileges
Hope it helps.
Best Regards,
Leo
Share
Report
All responses (
Answers (
