Adding to the Teams of Dynamics CRM
Customer relationship management (CRM) is important for any business, and provides numerous benefits to a business. CRM software is often implemented by many companies to improve marketing and customer service as well as customer data organization. One such software package is Microsoft’s Dynamics CRM. The 2013 incarnation of this software package has a huge difference included in it, changing something that has been a constant since CRM 4.
The thing that is changing slightly are the teams. Thus far, there has been only one team in Dynamics CRM, which is called an Owner Team. However, Microsoft decided to add another team in the 2013 version of Dynamics CRM called an Access Team. There is a reason behind this, and it hopes to resolve some issues that were present in previous versions.
Users of Dynamics CRM were able to create and manage Owner Teams. There were members as well as an admin at the top of the team. There is little change to the number of members as they are static. The only exceptions really to the number of members are expansion or turnover. Otherwise, the members and number thereof remained static.
Each member has their own access and permissions, and this varies among members unless the entire group is assigned a specific permission. The team can own records, which gives them sharing abilities. However, this static nature provided a block as far as flexibility.
These flexibility issues ended up putting extra strain on the system. The reason for this is sometimes additional teams were needed or desired, and it was these additions for special assignments that put the extra stress on the system since access verification based on security permissions has to be checked for each and every person on the main or supplemental teams.
Dynamics CRM 2013 took care of this issue with the introduction of Access Teams. These teams do not have security roles nor are they able to own records. They get their access via sharing from Owner Teams. The permissions in the sharing cannot be adjusted by the Access Teams. Not only that, but the Access Team is created when the first member is added, rather than having to do all of that in advance.
This allows the Owner Teams to get additional teams on certain records when needed. When all member of the Access Team have been removed after doing what they needed to do, the Access Team is removed. This can take some of the stress off the system, which is the entire purpose behind it.
One drawback is a possible drain on system performance. This is because of the record sets being created piecemeal and as the number of record sets that were created continues to grow, the more likely it is that there will be negative implications as far as performance of the system.
Given this last fact, using Access Teams is something that should be considered carefully before going ahead with it and risking bad performance.