Email basics: recipients, attachments and links
Decide who receives the message and what they can see
An email has a sender, recipients, a subject and a message body. To, Cc and Bcc are recipient fields. In the ordinary Gmail example below, all three receive the message; the difference is their role and address visibility.
| Field | Role in this example | Visibility in the original Gmail message |
|---|---|---|
| To | Teacher: the main addressee | Visible to recipients |
| Cc | Coordinator: receives a visible copy | Visible to recipients |
| Bcc | Observer: receives a hidden copy | This Bcc address is not shown to the To/Cc recipients |
The role names are hypothetical, not real email addresses. Cc means carbon copy; Bcc means blind carbon copy. Bcc does not remove the sender: the person who added a Bcc recipient knows that address. Gmail also hides other Bcc recipients' addresses from a Bcc recipient; other mail systems can handle delivered headers differently.
Hidden in the original message is not anonymous forever. If a Bcc recipient replies to visible recipients or forwards/discloses the message, their participation can be revealed. Inspect the actual recipient list before sending a reply, especially Reply All.
A file copy and a cloud link are different
| What you send | What the recipient gets | What to check |
|---|---|---|
| An ordinary file-copy attachment | A copy of the file with the message | Correct file/version and completed attachment upload |
| A cloud-file link | A way to open the cloud file, subject to its access rules | Intended recipient access and suitable view/edit permission |
Pasting a restricted cloud link into an email does not, by itself, give the recipient permission to open the file. Check access for the intended people; do not automatically make the file public. Attaching a file copy and inserting a cloud link can be different choices even when they start from the same file.
Walk through a pre-send check
Suppose you are preparing a practice email to the teacher, with the coordinator in Cc and the observer in Bcc. No email is sent in this exercise.
- Check the intended recipient addresses and their To/Cc/Bcc fields. Decide whether their visibility is appropriate.
- Read the subject and message body. Make the purpose and requested action clear.
- Check the right file and version. For an attachment, confirm upload completion; for a cloud link, check the intended recipients' access.
- Review recipients and file/link once more before Send. A hidden Bcc address or a pasted link does not replace these checks.
These checks are a practical workflow, not a promise that a service will catch every mistake. Attachment limits and controls vary by service/account; check the current limit when needed.
Five practice checks
- In the ordinary Gmail example, the observer should receive the email without their address appearing to the To/Cc recipients in the original message. Which field fits?
Show answer
Correct answer: C
Bcc sends the observer a copy without showing that Bcc address to the To/Cc recipients in the original Gmail message. The sender still knows whom they added.
Option A: A To address is visible to recipients in this example.
Option B: Cc is a visible copy-recipient field, so it does not meet this requirement.
Option D: Subject names the message topic; it is not a recipient field.
Hint: Choose the recipient field for a hidden copy, not a visible copy.
- A Bcc recipient replies to the visible recipients. Which statement is correct?
Show answer
Correct answer: A
Bcc hides an address in the original message as described; it does not guarantee anonymity in later actions. A reply to visible recipients can disclose the Bcc recipient's participation.
Option B: Bcc is an address-visibility feature, not a guarantee of anonymous replies.
Option C: A sender who adds a Bcc recipient knows that address; hiding it from other recipients does not erase that knowledge.
Option D: A Bcc recipient receives the message in this example; hidden-copy status does not mean no delivery.
Hint: Separate visibility in the original email from what a later reply reveals.
- You paste a restricted cloud-file link into an email. What should you do before sending?
Show answer
Correct answer: D
A cloud link points to a file governed by access rules. Check the intended recipients' permission separately; the presence of a link in an email is not proof that they can open it.
Option A: Renaming an email subject does not set the linked file's permissions.
Option B: Writing the word "link" says nothing about whether the intended people can open the file.
Option C: Pasting a restricted link does not itself guarantee access; verify the actual permission instead of assuming it.
Hint: A route to a file and permission to open it are separate things.
- You selected a file, but the attachment upload is still in progress. What is the appropriate next check?
Show answer
Correct answer: B
Selection can happen before the attachment finishes uploading. Confirm completion and the correct file/version before sending the intended attachment.
Option A: A selected filename is not proof of a completed attachment upload.
Option C: Cc/Bcc changes recipient visibility, not the state of the file upload.
Option D: The subject and attachment serve different purposes; removing the subject does not complete an upload.
Hint: Check both the transfer state and the identity of the file.
- Which comparison is correct?
Show answer
Correct answer: C
An ordinary file-copy attachment carries a copy with the message. A cloud link points to the cloud file, so intended-recipient access must be checked separately. Both also need the correct recipient list.
Option A: A restricted cloud link does not automatically make the file public, and a file-copy attachment does contain a copy.
Option B: A copied file and permission-controlled access to a cloud file are different delivery models.
Option D: In either model, a wrong recipient can still be a mistake; file choice does not replace the recipient check.
Hint: Ask whether the message carries a file copy or points to a cloud file.
Keep the checks separate
Who receives it? Who can see the addresses? Is the right file ready? Can the intended people open the link? One field or button cannot answer all four.
Source notes: Gmail recipient fields, Gmail attachments, Drive files in Gmail and Outlook file copies and cloud links. Scenarios and practice questions are original.
Sign in to keep your progress. Sign in