Roles
.gif) |
Microsoft CRM ships with a set of thirteen predefined roles that reflect common user roles with access levels defined to match the security best-practice goal of providing access to the minimum amount of business data required for the job. With these roles you can quickly deploy a Microsoft CRM system without having to define your own roles. However, you can create custom roles using the predefined roles as a template, or you can define an entirely new set of roles. For a list of these predefined roles, see Appendix A: Security Roles and Privileges.
Each of the defined roles is associated with a set of privileges that determines the user's access to information within the company.
You can create roles within Microsoft CRM and modify or remove these custom roles to fit your business needs. The roles you create for your business unit are inherited by all of the business units in the hierarchy.
You can assign a user zero, one, or any number of roles. For example, a user can have the Sales Manager role in addition to being a Customer Service Representative, in which case that user gets all the privileges of both roles.
You cannot modify privileges at the user level, but you can create a new role with the desired privileges. For example, John is given a Salesperson role, which requires him to accept all leads assigned to him. However, the administrator wants John to be able to reassign leads assigned to him. As a result, the administrator either needs to modify the Salesperson role to allow this or create a new role that incorporates this specific privilege and add John to this role. Creating a new role is the recommended option unless you think it essential that all users who are assigned the Salesperson role now have this additional privilege.
Related Topics