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

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

Microsoft Dynamics 2013 structuring assistance

(0) ShareShare
ReportReport
Posted on by

I have ran into some heavy limitations as the previous CRM Admin has structured our organization in a way to where each Location is a business unit which limits salespersons visibility if they do not belong to that specific business unit (Location)..


My question is for some assistance in mocking up some kind of CRM organization.


Here is the structure I have -

Company  (marketing, admin, VPs)
Districts (Northern, Eastern, Western, Southern)
Locations (multiple locations make up a district, and contains users, and service specific territories)

In 'Locations' there are three major positions --

Sales Managers - (needs to have visibility over multiple salespersons in multiple Locations)
Salespersons - (needs to be able to manipulate records in multiple Locations, however also needs to have the ability to limit visibility for specific salespersons to specific Locations only)


I'm thinking of something like this -

                  Company - business unit
                  Districts - business units
                  Location - teams
                  Sales Managers - users (sales manager of multiple teams or specific team)
                  Salespersons - users (salespersons of multiple teams or specific team)

My is to have better control over user permissions and or team permissions within specific Locations, if I choose to limit their permissions.

I'm just not sure what to use where, is teams best or should I create business units or is there a better way to structure?  

currently we have company, and locations as business units and the problem is that I have roaming salespersons that span over multiple locations but I am unable to do this because they have to belong to one specific business unit.

Also, I'm having permissions issues of user owned records, for example if user A from location 1 owns an opportunity, user b from Location 2 cannot manipulate the record and since they are equal in the structure (under the same parent business unit), I have to give full org permissions in order for the user to be able to manipulate the opportunity.

this is confusing please assist :)
                                 

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Community Member Profile Picture
    on at

    Hi Adam,

    Thanks for using the forums.

    The structure that you have suggested is good.

    By making the locations into Teams, you can individually add users to the teams as they move from location A to location B.

    However, a better way to manage these would be through Access team. This would give you more control over the records that the users would have access to. This should solve multiple of your issues with access.

    Please have a look at the following link blogs.msdn.com/.../collaborate-with-new-access-teams.aspx.

    To know more about access team, please have a look at the following document.

    www.microsoft.com/.../details.aspx

  • Verified answer
    Waqar Sohail Profile Picture
    on at

    Hi Adam, Have you go through the sharing record thing? I am pasting below text from the CRM book about sharing. I think it will be helpful to you.

    "Sharing gives another User or Team specified access to a single record. This feature is useful when you want selected Users from other Business Units to work on records that they do not have access to. Sharing applies to individual records instead of all records of a specific entity, and sharing is granted by any User who already has access to the record, instead of by a System Administrator assigning Security Roles to Teams or Users. When you share a record, access is configured for the same privileges that are defined in Security Roles, except that the depth of the access (such as User, Business Unit, or Organization) is not relevant because the share applies to individual records."

    Here is very good Blog which seems to related with your requirement.

    blogs.msdn.com/.../using-teams-to-solve-complex-record-sharing-scenarios.aspx

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans