web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

CRM 2013: Enabling the team members to accesss the records

(0) ShareShare
ReportReport
Posted on by

Hi,

I have a system where there are 2 teams under one Business Unit (say Team A and Team B).

I need to setup a security role so that Team A members cannot access Team B members' Account records but should be able to access same team members' records.

And there are 2 security roles one for Team and other for Users. Both security roles have 'user-level' access to Account records.

QuestionIs there any way to set this security configuration?

My tests:

I have tried the following steps:

1. When an account is created by a member X of Team A, it is not seen by Team B members - which is CORRECT

2. When I login as member Y of Team A, I cannot see the record either - which is WRONG

3. Now if I assign Owner of that record to 'Team A' then Point 2 is working correct.

Many thanks,

Wesley

*This post is locked for comments

I have the same question (0)
  • Royal King Profile Picture
    27,686 on at

    If you want to restrict data access based on user ownership create 2 different BU's one for team1 users and another one for team2 users. once you have this set it up you can add access level at BU for the entity so all users within that BU will have access to record regardless who own's the record.

  • Community Member Profile Picture
    on at

    Hi Chitra,

    Thanks for your response, is this the only way to make this work?

    Regards,

    Arjun

  • Royal King Profile Picture
    27,686 on at

    other option is sharing record with team whenever record is created or assigned. I don't recommend this approach as it will affect the performance of the system if the sharing record grows over the period of time.

  • Suggested answer
    Aileen Gusni Profile Picture
    44,524 on at

    HI Wesley,

    "1. When an account is created by a member X of Team A, it is not seen by Team B members - which is CORRECT"

    --> Yes, it is not because of Team, but it is because you set User-Access level, Member A create an Account, let's say Account 1, then by default, the owner is the creator (unless you change the assignment), that is Member X. And of course member from Team B cannot see the record, because the Account 1 is owned by Member X and other members cannot see records not owned by them or by their team.

    "2. When I login as member Y of Team A, I cannot see the record either - which is WRONG"

    --> It is because previously, you set:

    "And there are 2 security roles one for Team and other for Users. Both security roles have 'user-level' access to Account records."

    So, yes, the highest level is the User Access (because both Team and User are having User-Access level to Account in security role).

    Then the Member Y of Team A, cannot see the record from number 1, because it was still owned by member X. And your user + team are only having access until user level, so it means, correct, record owned by X is not seen-able by Member Y, member Y only can see records from Member Y himself, because the highest privilege you set is User.

    So, for number 3:

    "Now if I assign Owner of that record to 'Team A' then Point 2 is working correct."

    --> Yes, if you set the Access level of A Team until User only, so the user can only see Records owned by himself or Records OWN by his Team.

    And Account 1 (created from step1) as mentioned before is owned by Member X, not Team A, so it means, another member from Team A also cannot see this record, unless this record is belonging to TEAM as THE OWNER, not THE TEAM MEMBER, so to make it works, for this Team scenario, yes, you need to make the Records owned by A TEAM, not AN USER.

    Basically, User and Team access level are similar, the difference is just User is an Individual, Team is a collection of user, if you set as User level, then the records must be owned by Team as well, once the records belong to Team, it means that all members are the 'owner' of this record, so that member can see each other.

    But, you can do sharing between Team and Users as well if you feel not enough for this privilege. This will make complicated design. And also you can try Access Team.

    Another workaround that is crossing my mind now is:

    You split Team A, Team B into 2 different BU, BU A and BU B.

    Then, you give Access to the Users to BU-level.

    So that either the records is owned by Member X, Member Y, or a TEAM A, any member in team A can see the record, and members of Team B cannot see.

    Hope this helps!

    Thanks.

  • Suggested answer
    Kamakshi Parate Profile Picture
    on at

    Hello,

    If you want to restrict data access based on user ownership, you can create 2 different Business Units one for BU1 users and other one for BU2 users. You can add access level permission at BU for the entity so all users within that BU can access the record regardless who owns the record.

    Thanks.

    Kamakshi

    Microsoft Dynamicsâ„¢ CRM Support Engineer

  • Tomar Sourabh Profile Picture
    110 on at

    Thanks Aileen for descriptive answer.

    Suppose if we don't want to create BU then what workaround we have?

    As you said access team can you please elaborate. How?

    Thanks & Regards,

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
ScottDurow Profile Picture

ScottDurow 2

#2
GJones Profile Picture

GJones 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans