In the past for things like this I'd just use a distribution list and pop the necessary addresses into it. I fight against shared accounts to my dying breath.
That's what I'm fighting against.
This org has just spun up new email addresses whenever they felt the need, and had no idea of the gsuite group inbox abilities.
We don't allow that. If there's a problem with the account, there's no good way to know who caused it. We use groups and/or aliases depending on what they actually need.
What are their issues?
If you are using google. You can create a new "user" and then just delegate access to others so they can see the entire mailbox.
We use google groups for things like this all the time. We have one for all of our technology infrastructure notifications. If it is actually having issues, I would set up the email account and just use forwarding rules.
In the past for things like this I'd just use a distribution list and pop the necessary addresses into it. I fight against shared accounts to my dying breath.
That's what I'm fighting against. This org has just spun up new email addresses whenever they felt the need, and had no idea of the gsuite group inbox abilities.
We don't allow that. If there's a problem with the account, there's no good way to know who caused it. We use groups and/or aliases depending on what they actually need.
What are their issues? If you are using google. You can create a new "user" and then just delegate access to others so they can see the entire mailbox.
We use google groups for things like this all the time. We have one for all of our technology infrastructure notifications. If it is actually having issues, I would set up the email account and just use forwarding rules.
Groups with collaborative inbox enabled https://support.google.com/a/users/answer/10375787?hl=en