1. Sign in to the Admin console with group-management permission and open Directory > Groups.
2. Choose Create group, then enter the name, group address, description and an appropriate owner.
3. Review access settings carefully. A customer-facing enquiry address may need external posting, while an internal finance group should normally restrict it.
4. Create the group and add the intended members with suitable roles. Keep ownership limited to the people responsible for membership and settings.
5. Review each member's delivery preference where relevant. Membership does not always mean the person receives every message individually.
6. Send an internal and an authorised external test message to confirm the chosen behaviour.

Check whether replies go to the sender, the group or another configured destination. Confirm what From address recipients see. A team that assumes everyone is replying privately can accidentally send customer information to a larger audience.

Two colleagues need copies of messages sent to [email protected]. In the Admin console, open Directory > Groups > Create group and create a group named Sales enquiries.

1. Set the group address to [email protected] and appoint the responsible business owner.
2. Add [email protected] and [email protected] with the intended member roles.
3. Permit the external posting needed for customer enquiries and review the other access settings.
4. Send one internal test and one authorised external test.
5. Have both members confirm delivery, then test where their replies go.

Expected result: both members receive the intended enquiries and understand the reply behaviour. If the team needs one shared set of folders and sent messages, assess mailbox delegation separately.

A group is managed through membership and permissions. It is not a reason to share a user's password. If the team needs one mailbox's folders and sent-message history, compare Gmail delegation with the group's collaborative options.

Check the exact group address, member status, subscription preference and moderation queue. Review the sender's rejection and spam handling. Do not broadly open posting permissions to solve a problem caused by one member choosing no email.

Record the group purpose, owners and external-access decision. Review them when staff change, and test delivery after changing any posting policy so important customer mail is not left waiting for an unmonitored moderator.

• Controlling who can send to a Google Group
• Delegating Gmail access without sharing a password
• Adding a Google Workspace email alias and testing replies
• Choosing an alias, group or shared mailbox for a department

• Google Workspace group creation
• Google Groups membership and delivery

• Creating a Google Group for a team email address