Understanding Email and Your Google Account

Learn how email addresses, accounts and Google apps fit together, then prepare a safe practice workspace.

Part 1 of 10 | Email and Google Workspace for Beginners

Learning goals

Explain what an email address identifies, distinguish an account from an app and choose the correct account before working. Locate the main Google tools used in this course and make a practical account-safety checklist. You will build a fictional training-session project across the ten lessons.

Before you begin

Use a computer browser and an account you are authorised to use. A phone can support many tasks, but button locations and available controls differ. If you cannot access a practice account, complete the planning tasks on paper and record which practical steps remain untested. Do not purchase a subscription or create an account on someone else's behalf for this course.

Understand an email address

An address such as learner@example.com has a local part before the at sign and a domain after it. The domain helps identify the service or organisation handling the address. The example.com address in this course is a placeholder, not a recipient to contact. A small spelling error can send a real message to the wrong person or cause it to fail.

A display name is the friendly name shown beside an address. It is not reliable proof of identity: someone can use a familiar-looking name while sending from a different address. Before sending sensitive information, inspect the complete recipient address and verify the intended person independently. Autocomplete suggestions are convenient but can select an old or similarly named contact.

Separate account service and browser

Your Google Account is the identity used to access services. Gmail handles email; Drive stores and organises files; Docs, Sheets and Slides help create different kinds of content. Calendar handles events, Meet supports meetings and Forms collects structured responses. A browser is the program used to open their websites, not the account itself.

Some people use personal Google accounts and others use accounts managed by a workplace or school. Managed accounts can have restrictions and an administrator who controls services. This course does not promise every feature for every account or require a paid Workspace edition. Follow the rules for your organisation's account and do not move its information into a personal account simply to avoid a restriction.

Open the right service deliberately

Google's official app directory lists addresses including mail.google.com, drive.google.com and docs.google.com. Type an address you have verified into the browser's address bar rather than opening a sign-in link from an unexpected message. After signing in, inspect the account indicator before creating or sharing work. With several accounts open, it is easy to save a file under the wrong identity.

Write a simple app map for the practice project: Gmail for a draft invitation, Drive for the project folder, Docs for the agenda, Sheets for an attendance example and Slides for a short welcome presentation. Later lessons add a private calendar event and an unpublished feedback form. This map helps you choose the tool according to the task instead of searching every app for the same function.

Protect access and plan recovery

Use a unique password and review the additional sign-in methods available under the account's security settings. Google provides two-step verification guidance; the exact setup depends on the account. Keep recovery contact information current and under your control. Do not write passwords, backup codes or verification codes into your course workbook or send them to a helper.

Account recovery must use Google's official process, or the appropriate administrator for a managed account. A stranger claiming that payment guarantees recovery is not a trustworthy alternative. Do not deliberately lock yourself out to test recovery. Instead, review whether the listed recovery methods are still accessible and note any issue to resolve through the official route.

Work safely on shared devices

On a shared computer, avoid saving credentials, check downloaded files and sign out when finished. Closing a browser tab is not necessarily signing out. Private browsing also does not make a shared or untrusted device safe for every purpose. Use a device you trust for account security changes and follow local workplace rules.

Keep the practice project free of real customer, pupil or employee information. Use invented names and descriptions. The purpose is to learn a repeatable workflow without exposing other people's records. If an exercise mentions sending, inviting or publishing, prepare a draft unless you separately choose a controlled practice action with an account you own.

Guided exercise

1. Label the local part and domain in learner@example.com. Explain why a display name alone cannot verify identity.

2. Write a seven-app map showing the task each Google tool will perform in your fictional training-session project.

3. Open an authorised service and identify the active account. Record only whether it is the intended account, without copying private security details.

4. Prepare a security checklist covering unique credentials, additional verification, recovery access and shared-device sign-out. Mark unresolved items honestly.

5. Write a short practice plan naming your device, account type and any features you cannot yet test. Keep every example fictional.

Knowledge check

1. Is a browser the same thing as a Google Account?

2. Does a familiar display name establish who sent a message?

3. Should recovery codes be included in a learning portfolio?

Answer guide

1. No. The browser opens services; the account identifies the user.

2. No. Inspect and independently verify the actual address when necessary.

3. No. Keep them secure and private, outside the learning materials.

Completion standard

Submit an accurate address explanation, app map, non-sensitive account check and security checklist. Identify any untested step. Your project must use fictional information and must not contain passwords, recovery codes or another person's private records.

Sources and verification notes

Open Google Workspace apps. Checked 15 September 2026. Official browser addresses and app access. Available services and controls depend on account, device and administrator settings.

Turn on Google two step verification. Checked 15 September 2026. Official account protection guidance. Check the methods available to your account and keep recovery options under your control.

Recover a Google Account. Checked 15 September 2026. Use the official recovery process. Recovery is not guaranteed and third-party account-recovery promises are not endorsed.