CHD-385 already handled the address book groups problem via custom fields. However the initial request was also looking for the option to make some of these groups private by blocking read access.
(quote)
Yupp that would work as long as folks in one group dont ever see address / org entries that belong to someone else. Do not forget to include this tagging in export / import or it could get messy quickly
(end quote)
Here's the rest of the conversation, the request makes a lot more sense in context.
(quote)
dfroberg:
Would segmenting the access to address book entries by Group(s) be something useful for anyone else but me?
It makes sense that people allowed to view only a subset of tickets related to their specific group memberships should only be able to see the same subset of entries in the address book.
jeff@wgm:
We've thought about allowing some kind of grouping/tagging to go on in the Address Book. It wouldn't need to mirror the Worker Groups, because that would be a nightmare at much too fine of a level of detail.
But if you could tag or group addresses/orgs as 'Product X User' and 'Product Y User', you could then make those tags available to only specific groups.
That kind of virtual grouping in the address book would also help with other functionality, like custom fields, mailing lists and SLAs.
dfroberg:
Yupp that would work as long as folks in one group dont ever see address / org entries that belong to someone else. Do not forget to include this tagging in export / import or it could get messy quickly
In my case it would read "Company X Customer" etc etc...
(end quote)
The filtering in the previous issue was a nice addition, but I still require it to be hard locked, as we supply both production services as well as helpdesk services to competing companies, lets just say that the first thing these guys would do is to disable the filter and try to steal eachothers customers :)
New Feature
Open
[Permissions] Ability to make groups of the address books private by blocking read access to workers