 Compartmentalized groups or locations sharing a domain
We are a franchise organization and all of our locations, including the corporate office, share a domain for email. We've implemented Zimbra for the corporate office and are now looking to offer Zimbra to our franchisees. The problem, however, is how to keep everything compartmentalized - resources in particular.
For example, an employee at a franchise location shouldn't be able to schedule a meeting in a conference room at the corporate headquarters. I thought Class of Service would be the answer to this one, but if I have a user in one COS, and a resource in another COS, the user can still see free/busy info on the resource and schedule its use. This brings up another question: What does COS on a resource actually do?
How have other administrators solved this issue? |