4 ms·

I'd be fine with just an alias to a group of emails. A use case is that a customer service rep finds out that there is an issues with a patient's data. They can

by twunde 8y ago

I'd be fine with just an alias to a group of emails. A use case is that a customer service rep finds out that there is an issues with a patient's data. They can't forward a request to a business operations team to look into the issue or to the engineering support team. Just having an alias for a team that we could email would be a big win

tracker1 8y ago
Agreed... I'd love that as well... to be able to have outside users email dev@mydomain, I had to setup a group, allow posting from the internet, etc... (it took a while for me to figure out, as the permissions are strewn across the gsuite admin, and in a few places in the groups admin, when all I wanted was a distribution list that anyone could send to.
- jmathai 8y ago
  Even Googlers are perplexed when it comes to what certain group settings do and where you go to change them. We're working on improving that. Do you primarily use groups.google.com, admin.google.com or the AdminSDK APIs?
  - twunde 8y ago
    I mainly use the admin console (and that's where I would prefer the controls to be). Right now to update group permissions I use the admin console to go into the google groups console and then update the permissions there (as far as I know, there's no way to update google group permissions from the admin console).
  - tracker1 8y ago
    Personally, I'd prefer it in the admin.google.com area. Having to dig in felt painful... TBH, I'd love it if there were an option in google domains' mail, the mail forward option is great, if I could add multiple people, even better.
jmathai 8y ago
Would nesting groups meet your needs? For example... service_requests@ (group) -> operations@ (group) -> user1@ -> eng-support@ (group) -> user2@ Then sending an email to service_requests@ would send the email to both user1@ and user2@.
- twunde 8y ago
  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.

by twunde 8y ago

tracker1 8y ago

Agreed... I'd love that as well... to be able to have outside users email dev@mydomain, I had to setup a group, allow posting from the internet, etc... (it took a while for me to figure out, as the permissions are strewn across the gsuite admin, and in a few places in the groups admin, when all I wanted was a distribution list that anyone could send to.

jmathai 8y ago
Even Googlers are perplexed when it comes to what certain group settings do and where you go to change them. We're working on improving that. Do you primarily use groups.google.com, admin.google.com or the AdminSDK APIs?
- twunde 8y ago
  I mainly use the admin console (and that's where I would prefer the controls to be). Right now to update group permissions I use the admin console to go into the google groups console and then update the permissions there (as far as I know, there's no way to update google group permissions from the admin console).
- tracker1 8y ago
  Personally, I'd prefer it in the admin.google.com area. Having to dig in felt painful... TBH, I'd love it if there were an option in google domains' mail, the mail forward option is great, if I could add multiple people, even better.

jmathai 8y ago

Would nesting groups meet your needs? For example... service_requests@ (group) -> operations@ (group) -> user1@ -> eng-support@ (group) -> user2@ Then sending an email to service_requests@ would send the email to both user1@ and user2@.

twunde 8y ago
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.