CRM with data tables as: Contacts/Users, Accounts,Projects at the core.
We will have multiple levels of hierarchy. Example in the borrowed pic below:
So my questions is this, how do i create this the right way the first time. I know i can assign row owners to column like “REGION” but how do i from there within the region make things not visible from one sales person to another yet the manager of that team in teh region can see all the sales people in, and the main manager of the entire region can see all teh sales managers sales people info. The pic describes what i need greater than my words. I just really want to configure it properly. I need this to work proper in my workflow of converting a contact to an account and a project…all needs to bleed through the progression of the sales cycle in the crm with no filters yet all locked down hierarchy row owners. @ThinhDinh @Robert_Petitto @Darren_Murphy
1 Like
It’s really just a matter of carefully defining your groups, and then applying Roles and Row Owners correctly. Based on your diagram, you’ll need something like the following:
Roles
- CEO Role
- A separate role for each manager (eg. Manager1, Manager2, etc). This is necessary, because your managers have overlapping responsibility.
- Staff: probably no need for a Staff role, as it appears that they do not share clients.
- Clients: if your clients have multiple users, then you should use a ClientID as a role for them. Otherwise just use their email addresses as row owners
Row Owners
- In your Users table, you’ll most likely need the following Row Owner columns:
– Email: every user owns their own row
– Owner/CEO: CEO owns every row
– Owner/Manager: as managers share staff (and clients), you’ll need one of these for every manager
– Owner/Staff: each staff member gets ownership of the clients that they manage. There appears to be no overlap here, so a single column will do, and you can use the staff email addresses
- For other tables, you’ll need something similar. So in effect you’ll need 3 owner columns (CEO, Client, Staff) plus one more for every manager.
6 Likes
Read this over twice. Seems sound! Nice job @Darren_Murphy
I use the setup that Darren describes. When implementing these row owner columns on a client table, I use an additional staff row owner column so that they have access to the client records too.
thanks man…I will apply this as my base as of now when i start to implement this…thanks for your output my friend…it is always appreciated…and if you are ever in new orleans I got your crawfish covered just let me know when you make it! : - )
2 Likes