You’re offline. This is a read only version of the page.
Hello!
I have a question about joining user to an access team.
I create access team which grant read privillege and add an user to it. For example I add user to access team on the Account. Account has parental relationship to Opportunities, Cases etc. Do user have also permission to view the other entities related to account on which he's added to access team?
Thank you in advance.
Regards,
JJ
*This post is locked for comments
Hi Jarjar,
Access Team does have a cascading behaviour that menas if you add access team to an account, opportunities related to this account will also carry the same access team. As far as performance issues are concerned, it should not be a performance issue, to be frank this feature was released to get rid of Sharing feature because sharing does access POA table and leads to performance issues which access teams can take care. since you have less than 10 users both the features are fine to go ahead with. following are few URLs on access teams:
crmbusiness.wordpress.com/.../crm-2015-the-benefits-of-access-teams
blog.crmguru.co.uk/.../why-use-access-teams-in-dynamics-crm-2013
file:///C:/Users/Spartians/Downloads/Access%20Teams%20with%20Microsoft%20Dynamics%20CRM%202013.pdf
Hi,
I don't think there will be performance issue. It's CRM's internal functionality and it will not impact your system's performance.
Also, I checked the parental impact, and if you add user to the access team of parent record, then it also grants access to its related records. Hence you can use Access Teams in your business scenario without any issues.
Thanks & Regards,
Yadnyesh kuvalekar
Tick verify answer if this resolves your query.
In this case I wonder if it is not a multiplication of shares.
Because if I use access team on an account which is parental to the opportunity and there will be another access team on opportunity and both of them gives read access to the user.. and so on.
Multiply it by number of relations x users x records and it may be a little too much considering the performance of server.
Hi JJ,
As you want to restrict access at record level, you will need to go for Access teams only.
So, in your case, you also want to restrict access from its related records?
Business situation looks like this:
There are only few (less than 10) users in the system. All of them should have access to every single record. But there is condition - Manager should take away access for any single record from any user.
We came up with solution like this: we put access teams with read privillege on every entity and the manager can delete members from it when its neccessary.
Maybe someone has better idea?
Regards,
JJ
Hi JJ,
Its new learning to me as well. I was not aware of this and have never tried the same. But as per MSDN link it also provokes access ro related records.
Thanks for the answer Yadnyesh,
in the meantime I found this on the msdn:
"Owner teams and access teams provide access rights to the record and related records, such as to an account and all opportunities related to this account. In case of parental relationship between the records, cascading rules are applied. For the owner teams, you can access entities based on the roles assigned to the user plus the roles assigned to the team that a user is a member of. This allows a user to have privileges outside their business unit"
what do you think ?
Hi JJ,
Access Team works per record and adding user in access team on account entity will not grant/revoke access of related records of the account record.
To grant access to related records, you will either need to add user in opportunity's access team or through security role you can control the access.
If you share your scenario, I can guide you properly.
Thanks & Regards,
Yadnyesh Kuvalekar
Tick verify answer if this solves your query.
#1
Mohamed Amine Mahmoudi
83
Super User 2025 Season 1
#2
Community Member
52
#3
Victor Onyebuchi
6
Share
Report
All responses (
Answers (
