Use Groups.
The best way I've found to handle this is to create Groups. These can be set up in the Admin Console alongside Users, and have an input email address, as well as fine grained control over access restrictions.
For groups that will receive from public emails, you'll want to make sure the "Publish Posts" setting is set to "External", otherwise email addresses outside your organization will not be able to send messages to the group address. See image below for access settings recommendations for these types of public-facing groups.
After setting this up, you'll be able to add group members. Each of these people will then be essentially 'subscribed' to all messages sent to the group.
I find this to be much less hacky than the Gmail default routing settings, although still use them for catchalls etc.
Another quick note is that you can use groups as a forwarder to another system, e.g. a ticketing or helpdesk system. For example, [email protected] can be the Support Group, which has one member that is the ticketing system's input address. To do this, you will need to enable the setting "Allow members outside your organisation". With this said, using groups can rewrite the sender's name and email so ensure your system is able to decode the email headers correctly to find the original sender.
In this situation (creating orders@)
- In Admin Console, Access Directory > Groups
- Click Create Group.
- Group Name: Required, Will be seen frequently, so maybe [Business] Orders would do.
- Description: Optional, describe what purpose of group is.
- Group Email: Required, [email protected]
- Group Owners: Optional, If you want to receive emails, enter your own account in this field. Otherwise, it is okay to leave it blank and manage the group from Admin Console.
- Click Next
- Access Settings: Required, Set as shown in image below.
- Click Create Group
- Click Add members
- Add members as required. You can also change role to Manager if you want them to be able to add and remove other members.
Group access settings recommendations for public-facing inboxes
