Hello,
My organization is setting up domain separation. We are using the department field as the basis for the domain separation, which is pretty straight forward. Even if our use of departments is not so clean. We use departments as way of separating out project groups, and their resources. My problem comes in that I'm not sure I'm building out the basic structure correctly, and I want to get some feedback.
In our environment we have a variety of internal clients that we support. Most of their data doesn't have high level constraints and all the members of our support teams can see it. However, we have three clients that have tighter restrictions and need to have their data domain separated.
We need most of our people to be able to see all the data minus the data from these three client domains unless they are a member of the domain. Our support teams are sprinkled throughout all four possibilities in that some members can see one (or more) secure domains but not others. All our support team members need to be able to see any information that is not separated out.
I'm wondering if I go with Top -> default -> which splits to Secure and Standard. Then have three client domains under Secure. Then the four support teams and the larger members domain (everyone not in a secure domain) under Standard.
Then if I'm understanding things I would give the secure support teams visibility into their respective clients.
Something like this:
What I am drawing a blank on is that for the secured clients I'll assign domains that have a department. For the normal clients and our support team that are outside the three secure environments they don't necessarily have a department to assign.
For the support teams would it be better to create a support team domain, and then assign additional visibility on a member by member basis?
Does any of this make sense? Am I on the right track?
Thanks.
