Skip to content
Ömer Tiryaki (Home)
← All notes

Guidechecked

Google Workspace admin

Set up and run Google Workspace for a small company: domain and email, users, groups, shared drives, sharing, security, onboarding and offboarding. With DNS examples and a checklist.

The Admin console

Everything runs through the Admin console at admin.google.com. There you manage users, groups, apps, security and billing. Menu names are given as they appear in the English interface. Admin roles under Account, Admin roles control who can do what. Besides super admin there are prebuilt roles such as User Management Admin, Groups Admin and Help Desk Admin. For daily work these are almost always enough.

Caution:Hand out super admin sparingly. Google recommends more than one super admin, each for a different person, and a dedicated admin account separate from the everyday account. Security keys are the best choice for admins, including a spare key and backup codes stored safely.

Verifying the domain and setting up email

A TXT record proves that you own the domain. The MX record routes mail to Gmail, and SPF allows Google to send for the domain. firma.example is a placeholder.

  1. Add the verification TXT record on host @. The value starts with google-site-verification= and is 68 characters long in total.
  2. Add an MX record with priority 1 pointing to smtp.google.com. Remove all other MX records. Older accounts with records starting with aspmx keep working and need no change.
  3. Add SPF as a TXT record on @. Each domain has exactly one SPF record. Other senders such as a newsletter service go into the same record with include:.
firma.example.  3600  IN  TXT  "google-site-verification=<TOKEN>"
firma.example.  3600  IN  MX   1 smtp.google.com.
firma.example.  3600  IN  TXT  "v=spf1 include:_spf.google.com ~all"

DKIM and DMARC

DKIM signs every outgoing message, DMARC tells the recipient what to do with mail that fails SPF and DKIM. Without both, your mail quickly lands in spam at large providers. You generate the DKIM key under Apps, Google Workspace, Gmail, Authenticate email.

  1. Pick the domain, select Generate new record, 2048 bits and prefix google. Use 1024 only if your DNS provider cannot handle 2048 bits. After Gmail is turned on the key can take 24 to 72 hours to become available.
  2. Add the TXT record under google._domainkey at your DNS provider, and only then click Start authentication. It can take up to 48 hours before DKIM works.
  3. Add DMARC no earlier than 48 hours after SPF and DKIM. Start with p=none and read the reports sent to the rua address for about a week.
  4. Once all genuine senders pass cleanly, move to p=quarantine with a small pct value, raise it step by step and finally set p=reject if needed.
google._domainkey.firma.example.  3600  IN  TXT  "v=DKIM1; k=rsa; p=<KEY FROM THE ADMIN CONSOLE>"
_dmarc.firma.example.             3600  IN  TXT  "v=DMARC1; p=none; rua=mailto:dmarc@firma.example"

Planning organizational units

You find organizational units (OUs) under Directory, Organizational units. They are not an org chart but containers for settings. Every account sits in exactly one OU, and child OUs inherit the settings of their parent. This lets you enforce 2-Step Verification for a test OU first and then for everyone. Only create as many OUs as there are different settings.

/                     baseline settings for everyone
/Staff                regular accounts
/Staff/Test           try new policies here first
/Admins               separate admin accounts, stricter policies
/Leavers              suspended accounts until deletion

Creating users

You create single accounts under Directory, Users with Add new user. Fix the naming scheme first, for example firstname.lastname@firma.example, with umlauts transliterated (ü becomes ue). Check that a free license is available.

  1. Enter first name, last name, address and the right OU.
  2. Let the password be generated and require a change at first sign-in.
  3. For many accounts use Bulk update users, download the blank CSV template and fill it in. Required are First Name, Last Name, Email Address and a Password of at least 8 characters. For non-ASCII names save it as UTF-8 with BOM.

Caution:Password length and strength rules do not apply to passwords you set by hand or upload via CSV. So always require a change at first sign-in and hand over the initial password separately from the username.

Groups

Groups under Directory, Groups serve as distribution lists such as info@firma.example, as permission holders for shared drives and calendars, and as a collaborative inbox. Ideally, grant access only through groups. When someone leaves, removing them from their groups is then enough.

  1. For lists such as info@ allow external senders to post, otherwise customer mail does not arrive.
  2. For a collaborative inbox, first turn on Groups for Business under Apps, Google Workspace. The group owner then enables the feature in Google Groups, including conversation history.
  3. Every group needs at least two owners.

Shared drives instead of My Drive

In My Drive every file belongs to one person and hangs on their account. In shared drives the files belong to the team and stay when someone leaves. Company data therefore belongs there. Since 2024 they are also available in Business Starter, with fewer admin settings there.

  1. Roles: managers handle members and settings, content managers can also move and delete files, contributors can add and edit files, commenters comment, viewers only read.
  2. Add groups as members, not individual people.
  3. Under Apps, Google Workspace, Drive and Docs, Sharing settings, Shared drive creation decide who may create shared drives and what managers may change. Under Manage shared drives you see all shared drives, even without being a member.

Controlling external sharing

Under Apps, Google Workspace, Drive and Docs, Sharing settings, Sharing options you decide whether files may leave the company. The setting applies per OU, and changes can take up to 24 hours.

  1. On allows external sharing, Off blocks it, Allowlisted domains allows only trusted domains.
  2. Keep the warning for sharing outside the organization turned on.
  3. Allow sharing with people without a Google account (visitor sharing) only if you really need it.

Tip:A good middle ground: external sharing and warning on, client projects in their own shared drives.

Security

You find 2-Step Verification (2SV) under Security, Authentication, 2-step verification. Google now enforces it for admin accounts itself. For everyone else you turn it on in two stages.

  1. Turn on Allow users to turn on 2-Step Verification, with enforcement off. Everyone sets up a second method.
  2. Then turn on enforcement from a date and set a new user enrollment period (1 day to 6 months).
  3. Methods: at least Any except verification codes via text, phone call. Only security key is the most secure and requires a grace period during which admins hand out backup codes.
  4. Password rules under Authentication, Password management: minimum length between 8 and 100 characters. Expiry is off by default and I keep it that way.
  5. Check the alert center under Security regularly, it is included in all Business editions. The security dashboard and security health page exist only in Enterprise and Education.

Caution:Anyone without a second method by the deadline is locked out. Check the report beforehand to see who is still missing, and start with the admins.

Devices

Under Devices, Mobile & endpoints you control phones and laptops with a company account. Basic management is on by default and needs no app: require a screen lock, see devices and remove the company account from a lost device. Advanced management with work profiles, approval of new devices and full device wipe is available from Business Plus. Users then need a management app on the device.

Offboarding

When someone leaves, order matters: close access first, then secure the data, and free the license last. Important: a suspended account still costs as much as an active one.

  1. Reset the password, reset the sign-in cookies under the account’s security settings, suspend the account and move it to the leavers OU.
  2. Remove the company account from the phone and take the person out of all groups.
  3. Secure email: Gmail cannot be transferred during deletion. Move it into another mailbox with data migration beforehand, or archive the account.
  4. Delete the account under Directory, Users, Delete user. Super admins transfer Drive files, the primary calendar and Looker Studio assets to the successor in the process.
  5. Within the 20 days the address can be reassigned to another account so customer mail keeps arriving.

Tip:Delete or archive? Deleted accounts can only be restored for 20 days. For longer retention there is the paid Archived User license: the data stays, and sign-in is no longer possible. On the Flexible plan the bill drops pro rata after deletion, on the Annual plan the license becomes free for the next person.

Retention with Vault

Google Vault retains email, chats and files, places holds for legal purposes and exports data. It is included in Business Plus and the Enterprise editions, not in Business Starter and Standard. Without a retention rule Vault keeps nothing, and after an account is deleted the data can be gone for Vault too. So set up rules before the first person leaves.

Common mistakes and fixes

These cases come up again and again.

  1. DMARC too strict: with p=reject on day one, mail from the newsletter service, for example, gets rejected. Start with p=none, read the reports, add missing senders.
  2. Broken SPF: two SPF records, or more than 10 DNS lookups from too many include: entries, make SPF invalid. Put everything into one record and remove unused services.
  3. Data not transferred before deletion: after 20 days email and files are gone. Migrate Gmail beforehand and transfer Drive during deletion.
  4. Super admin for everything: if that account is taken over, the whole company is open. Do daily work with limited roles.

Short checklist

The short version to tick off.

  1. Domain verified, MX, SPF, DKIM and DMARC set and tested.
  2. At least two super admins with security keys, daily work with limited roles.
  3. OUs created, 2SV enforced, password rules set.
  4. Groups with two owners, company data in shared drives, external sharing set deliberately.
  5. On leaving: access closed, email and files transferred, groups removed, account deleted or archived, license checked.

More notes

Privacy

No tracking cookies

Nothing about you is collected here.

What your browser remembers

None of it is used for analytics.

Read the privacy policy