Some must know about CRM 2013/2015

Hi folks.

Today I want to share you some ‘must knows’ about Microsoft Dynamics CRM 2013 and 2015

Feel free to comment this article and share your ‘must knows’.

  • About security roles
    • Are a collection of privilege
      • Which describe data access or action
      • Are cumulative
    • Can be assigned to users or owner teams
    • Can be applied to a group of records by ownership, business unit or organization
    • Will be cached from the application server

       

  • About field level security
    • Field level security profiles can only be assigned to custom fields (Version 2013)
    • Field level security profiles can be assigned to custom and system fields (Version 2015)
    • Filed level security profiles can be assigned to users or teams
    • Is the third way to obtain security and it’s consumes performance

       

  • About users
    • Only users has access to the application
    • A User is a member of a business unit
    • Has one or more security roles
    • The Security Roles and Business Units of a user will be cached from the application server

       

  • About teams
    • A team is a member of a business unit
    • Has one or more security roles
    • The Security Roles and Business Units of a team will be cached from the application server
      • Has none or many user (out of different business units) as members

         

  • About team types
    • Owner Teams
      • Can own records
      • Can be scheduled as a resource
      • User membership will be cached from the application server
      • Can only be created, deleted or updated manually or programmatically
    • Access Teams
      • Cannot own records
      • Has no security roles
      • Cannot be scheduled as a resource
      • Access teams are not cached
      • Are not shown in the most team views
      • Can be created, deleted or updated from the system, manually or programmatically
      • More than one team is required if different access right is desired for the team’s members (read team // read write team)

         

  • About data ownership
    • Record ownership can granted to
      • Users or Teams
      • The ownership model is independent from the amount of records in the database
      • The number of teams have no significant performance impact

         

  • About sharing
    • Is a direct assignment of privileges to a record
    • Can be given to users
    • Can be given to teams
      • Use a team of users how has the same access to the records. This will decrease the performance impact.
    • The use of explicit sharing has a significant performance impact
      • For each data access a complex database query will run and determinate the individual sharing rules.
      • Shares can be given to child records, this increases the performance impact
      • The privilege for each record that is shared will be checked by access.

     

 

No comments yet.

Leave a Reply