So I don't even need that much (although I do use nesting groups for other things). The problem is that while Gmail is hipaa-compliant, groups is not. HIPAA c

So I don't even need that much (although I do use nesting groups for other things). The problem is that while Gmail is hipaa-compliant, groups is not. HIPAA considers any personal health information INCLUDING account ids, names, etc to be PHI. Since it's quite easy to accidentally include any of this information, we can't give operations or eng-support a group (or even customer service. To workaround this we have individual email accounts for customer service with shared credentials, with personnel taking turns to log in and triage. Super-ugly) So right now what we have looks like ``` customerservice_for_client1@ (user account with shared credentials) -> user1@ -> user2@ -> user3@ -> user4@ ``` That groups isn't hipaa compliant, feels inane, especially since email is hipaa-compliant. There's obviously something that prevents it (probably the ease of making records public). If you'd prefer to get on a call or meet in NYC let me know.