Do all team members have access to all the records created by that team's members?

(0) Share

Report

Posted on by cranialsurge

I have a Business Unit team (owner team) that has a custom security role associated to it. I have an account whose owner is this team. Whenever I log in as one of the team users with this security role (that the team is associated with under 'manage roles') and create an opportunity based on the account mentioned above, everyone in the team has full access to it to modify, delete it.

However the security role in question does not permit this. For the opportunity entity, the security profile only allows for 'user' level write, delete, assign access. And 'BU' level for Create, append to and share.

The moment I change the owner on the Account to an individual instead of the team, it works as expected and no one else on the team can modify, delete opportunity records that they did not create.

Is this expected behavior or am I misunderstanding the scope of the team in some way? Ideally I don't want every member of the team to be able to edit all opportunities that were created based on this account by another team member. Reads are fine, but not update/delete operations.

*This post is locked for comments

I have the same question (0)

All responses (7)

Answers (1)

Verified answer

Hosk on at

Like (2)

Report

User level in this case will mean the users of the team because when the account owner is the team the team is the user, which consists of all the users in the team.

I think it's working as it should be

Was this reply helpful? Yes No
Suggested answer

Royal King 27,686 on at

Like (0)

Report

This is the expected behavior. If team role has User level permission to opportunity records that means all the users who are part of team will have access to those records owned by team(Just like owned By user to read/write).

Was this reply helpful? Yes No
cranialsurge on at

Like (0)

Report

What's weird though, is that if I have an account whose owner is an individual instead of a team and then I switch the owner to a team, this behavior is not seen. In such cases no one except the opportunity owner is able to edit his/her opportunity. I wonder if this might be a product related issue of some sort.

Was this reply helpful? Yes No
Suggested answer

Prati 980 on at

Like (0)

Report

Hello Cranialsurge ,

Thank you for the Post . I agree with Ben and Chitrarasan , When the Owner is the team All the Users of team will be able to access / modify each others record , However when you change the Owner to an Individual the restrictions are enforced on other members of team as per the Security role and they no longer have access to each others records .

Its working as it should . For more info please refer the links:

1. www.dummies.com/.../understanding-access-levels-and-roles-in-microsoft.html

2.technet.microsoft.com/.../jj191623(v=crm.6).aspx

Wish you a very happy and prosperous new year .

If my answer assisted you then please mark it as verified .

Thanks and regards

Prashant T

Was this reply helpful? Yes No
Royal King 27,686 on at

Like (1)

Report

Check whether you have share with original Owner when record is resigned set to Yes, if its value is set to yes ?when record is reassigned from team to owner by default record is shared with team. That might be providing access to all team members ater reassigning the record.

Was this reply helpful? Yes No
cranialsurge on at

Like (0)

Report

Hi Chitra, the scenario I am pointing to(in my second post below the original) is the other way around. While everyone on the team has access to opportunities based on newly created accounts owned by a team, if I reassign an existing account from 'individual' to 'team' ownership, in that case all the team members do not have access to opportunities. that are created against such existing accounts that were re-assigned from 'individual' to 'team'.

Was this reply helpful? Yes No
Royal King 27,686 on at

Like (0)

Report

Does Team assigned with role? If so check the role at least as read access to opportunity entity

Was this reply helpful? Yes No