Google Workspace Handbook

Document: OPS-100Type: HandbookStatus: ApprovedOwner: Business OperationsVersion: 4.2.0Updated: 2026-07-17

Current architecture

Primary licensed user: admin@→Aliases→One Gmail inbox→Labels + Filters + Send mail as

Aliases receive mail in the primary inbox but cannot be used as separate Google sign-in accounts.

Approved aliases

Alias	Purpose	Recommended label	Send as
hello@	Primary public and general inquiries	👋 Hello	Yes; default external identity where appropriate
accounts@	Vendor ownership, Cloudflare, subscriptions, invoices	💳 Accounts	Yes
engineering@	Engineering identity and technical correspondence	🛠 Engineering	Yes
support@	Customer and product support	🎧 Support	Yes
security@	Security notices and vulnerability reports	🔐 Security	Yes
privacy@	Privacy requests	🛡 Privacy	Yes
social@	Social platform operations	📣 Social	Yes

Filter standard

Create a Gmail filter using the recipient address, then apply the matching label. Example for engineering:

to:(engineering@cloudberrie.com)

1. Gmail → Settings → See all settings → Filters and Blocked Addresses.
2. Create a new filter with the alias in the To field.
3. Apply the approved label and optionally mark it important.
4. Test from an unrelated external address.

Send mail as standard

1. Gmail → Settings → Accounts and Import.
2. Under Send mail as, add the alias.
3. Complete verification.
4. Select the alias in the From field when composing or replying.
5. Confirm the recipient sees the alias—not admin@.

Long-term model

When employees join: each employee receives an individual account such as firstname@cloudberrie.com. Aliases continue as functional addresses and may later move to Google Groups or delegated mailboxes.