Google Workspace email
Dots can matter in Google Workspace, school, and organizational accounts.
The familiar rule that Gmail ignores dots applies only to personal @gmail.com addresses. If your email is on a company or school domain managed through Google Workspace, dot behavior depends entirely on how the admin set things up.
The key difference from personal Gmail
On personal @gmail.com accounts, Google automatically strips dots during mail delivery. Every dot permutation of a username resolves to the same inbox and no one else can register a variation.
Google Workspace does not apply this automatic normalization. An organization's admin creates each user account manually (or via provisioning tools), and the exact username string the admin enters is what defines the mailbox. That means j.smith@company.com and jsmith@company.com can be two entirely different people with separate inboxes, calendars, and Drive storage.
How Workspace user provisioning works
When a Google Workspace administrator adds a new user, they type in the primary email address. That exact string, dots included, becomes the canonical address for the account. The admin could then add email aliases to the same account (including dot variations), but those aliases only exist if explicitly configured.
In practice this means:
- No automatic dot equivalence: Unlike personal Gmail, the system does not treat
jane.doeandjanedoeas the same account by default. - Aliases are opt-in: An admin can add
janedoe@company.comas an alias forjane.doe@company.com, but it does not happen automatically. - Catch-all routing changes behavior: If the admin enables a catch-all address, mail sent to any unrecognized username (including unregistered dot variations) goes to a designated mailbox rather than bouncing.
School and university accounts
Educational institutions typically use Google Workspace for Education. The same rules apply: the school's IT department provisions accounts, and their naming conventions determine whether dots matter.
Common patterns seen in educational environments:
- Student accounts with ID numbers: Some schools assign usernames like
s12345@school.eduwhere dots are never part of the format, making the question moot. - Name-based accounts: Schools that use
firstname.lastname@school.eduas the primary format may or may not have configuredfirstnamelastname@school.eduas an alias. - Inconsistent policies: Large universities with thousands of accounts often have legacy configurations. The only reliable way to know is to ask IT support or send yourself a test email.
What happens when you email a dot variation on Workspace
If you send a message to a dot variation that does not exist as a user or alias on a Workspace domain, one of three things happens:
- Bounce: The mail server returns an undeliverable error. This is the default behavior when no catch-all is configured.
- Catch-all delivery: The message goes to whatever address the admin designated as the catch-all recipient.
- Delivery to another user: If the dot variation happens to match a different account that was provisioned with that exact username, the message goes to that other person's inbox.
This is why you should never assume the dot trick works on non-gmail.com addresses. Sending sensitive information to a guessed dot variation on a Workspace domain could result in it reaching the wrong person entirely.
Admin options for controlling dot behavior
Google Workspace administrators have several tools to manage how dots are handled on their domain:
- User aliases: Add alternate addresses (including dot variations) to an existing account through the Admin console under Users > Account > Alternate email addresses.
- Catch-all routing: In the Admin console under Apps > Google Workspace > Gmail > Default routing, admins can route unrecognized addresses to a specific mailbox.
- Group aliases: A Google Group can receive mail at multiple addresses, providing another way to consolidate dot variations.
- Directory sync: Organizations using LDAP or Active Directory sync should ensure that the naming conventions in the source directory align with how Google Workspace handles the imported usernames.
Comparison: personal Gmail vs Google Workspace
| Feature | Personal Gmail | Google Workspace |
|---|---|---|
| Dots ignored automatically | Yes, always | No, admin-dependent |
| Dot variations blocked at registration | Yes, all reserved | No, admin can create both |
| Plus addressing | Always works | Works if not blocked by admin |
| Case sensitivity | Ignored | Ignored |
| Catch-all option | Not available | Available in Admin console |
Testing whether dots matter on your domain
If you are not sure how your organization handles dots, run a quick test:
- Open a second email account (a personal Gmail or any other provider).
- Send an email from that account to a dot variation of your Workspace address that you know you did not configure. For example, if your address is
jane.doe@company.com, try sending tojanedoe@company.com. - Wait a few minutes. If the email arrives in your inbox, the admin has either set up a dot alias or enabled a catch-all. If it bounces, dots are significant on your domain.
For personal @gmail.com accounts where dots are always ignored, you can generate every variation using our Gmail Dot Variations Generator. Read the companion guide on dots in personal Gmail for the full breakdown.