3 ms·

One thing that's sort of wonky (and possibly it's something that just got set up in a weird way by an admin here at some point, I'm not remotely a G Suite exper

One thing that's sort of wonky (and possibly it's something that just got set up in a weird way by an admin here at some point, I'm not remotely a G Suite expert or admin) is connecting Groups and service accounts, or having a service account for a group. For example having support@example.com be a group, but also having a support@example.com service account. (Currently we have a support@ service account that sometimes sends automated emails and which forwards incoming things to a group where everyone in the group has been granted "send as support@," since the group side is basically acting as a collab support inbox. I think the whole thing could possibly be a "shared inbox" type group were there just a way to have a service account matching the group email. And of course there may some benefit to it being set up how it is that I'm missing, or a way to do so currently that got overlooked somehow.)

jmathai 8y ago
When you say service account are you talking about one of these? https://cloud.google.com/iam/docs/understanding-service-accounts https://cloud.google.com/iam/docs/understanding-service-acco...
- Glyptodon 8y ago
  I think so? I'll see if I can double check. (My understanding is that it's a kind of psuedo-user account, and that it's being used because there's no "virtual user" to "act as the group" when it comes to automated emails and tasks or something along those lines. I wouldn't be surprised if it's more complicated and they created an actual domain user that belongs to no-one and then give the service account permission to act as it or something along those lines.) Whatever is actually happening isn't supper important though - I think somebody over here just did whatever they thought the minimum effort thing to do was without thinking or looking into it much. I'm fairly certain each group having an admin panel having a page that allows "app passwords" or Oauth2-integrations to be set up for its address/account by the group owner/admins would cover at least 90% whatever we've got going. (And once again, it is completely possible that something like that can already happen and just isn't obvious to anybody over here.)

jmathai 8y ago

When you say service account are you talking about one of these? https://cloud.google.com/iam/docs/understanding-service-accounts https://cloud.google.com/iam/docs/understanding-service-acco...

Glyptodon 8y ago
I think so? I'll see if I can double check. (My understanding is that it's a kind of psuedo-user account, and that it's being used because there's no "virtual user" to "act as the group" when it comes to automated emails and tasks or something along those lines. I wouldn't be surprised if it's more complicated and they created an actual domain user that belongs to no-one and then give the service account permission to act as it or something along those lines.) Whatever is actually happening isn't supper important though - I think somebody over here just did whatever they thought the minimum effort thing to do was without thinking or looking into it much. I'm fairly certain each group having an admin panel having a page that allows "app passwords" or Oauth2-integrations to be set up for its address/account by the group owner/admins would cover at least 90% whatever we've got going. (And once again, it is completely possible that something like that can already happen and just isn't obvious to anybody over here.)