📝 Lesson 6.2: Smart Chips, the @ Menu & Smart Canvas

The @ Menu — One Key to Insert Anything

If you learn only one thing from this module, make it this: type @ and a menu appears. Anywhere in a document, the moment you type the @ symbol, Docs pops up a universal insert menu. Start typing and it filters instantly. It's the fastest, most direct way to add structured content — no hunting through menus, no clicking across the toolbar. One key, and the whole toolbox opens under your cursor.

Think of @ as a command palette for your document — like asking "what would you like to insert?" and getting an instant, searchable answer. From the @ menu you can drop in:

• Smart chips — people, files, dates, places, calendar events, and more
• Building blocks — the meeting notes, email drafts, and trackers from Lesson 6.1
• Document structure — headings, bulleted and numbered lists, checklists
• Interactive elements — dropdowns and table templates

Why does one keystroke matter so much? Because friction decides habits. When inserting a linked file means opening a menu, finding the right submenu, browsing, and pasting, most people just type the filename as plain text and move on. When it's type @, type a few letters, press Enter, they actually do it — and the document gets richer as a result. The @ menu removes the friction, so the good habit becomes the easy one.

Smart Chips — Living Bits of Information

Smart chips are the stars of the @ menu. Each one replaces a dead piece of text with something that knows things and shows them on demand. Here are the ones you'll use most:

A people chip turns "email John about this" from a note-to-self into a live reference: hover it and John's details appear right there. A file chip is quietly transformative — instead of a bare "see the budget doc," you get a chip you can hover to preview the actual budget without opening a new tab and losing your place. A date chip looks nicer than typed text and stays interactive. On some accounts you'll also see calendar event chips (linking a doc to a meeting) and even finance chips for stock tickers — availability varies, which we'll be honest about shortly.

⚠️ Important Note: A file chip only links to a file — it doesn't change who can open it. If you share your document with someone who doesn't have access to the linked file, they'll see the chip but can't preview or open the file. This connects straight to the sharing and permissions ideas from Module 5: the chip is a pointer, and the pointer only works for people the target file is shared with.

Interactive Elements — Dropdowns, Checkboxes, Tables

Chips represent information. The next tier of @-menu items lets readers do things — and this is where a document starts to feel less like paper and more like a small, shared app.

Dropdown chips

A dropdown is a chip that holds a set of options; click it and a menu lets you choose one. Insert one via the @ menu (type @dropdown) and you get either a ready-made set — a project status like Not started / In progress / Done — or a blank one you fill with your own options and colors. It's perfect anywhere a value should be picked from a fixed list rather than typed freely: statuses, priorities, stages, yes/no. Because everyone picks from the same list, the document stays consistent — no more "Done" versus "done" versus "complete" scattered through a table.

Checkboxes

A checklist (a checkbox list) is a list you can actually tick off. Insert it from the @ menu or the toolbar's list button. Unlike a bullet, a checkbox is clickable — check it and the item gets a line through it. For to-do lists, action items after a meeting, packing lists, or any "did we do this yet?" content, checkboxes turn a static list into a working tracker.

Table templates

The @ menu also offers table templates — pre-built tables wired up with chips already inside. Two you'll meet often:

• Product roadmap — rows for features or milestones, with status dropdowns and date chips ready to go
• Review tracker — rows for items moving through a review, with reviewer people-chips and status dropdowns

These are the "furniture" version of interactivity: instead of building a table and adding chips cell by cell, you drop in a whole structured, interactive table at once and just fill it in. (They overlap with the building blocks from Lesson 6.1 — same idea, reachable from both the Insert menu and the @ menu.)

The picture in one line: one keystroke opens the menu, the menu inserts chips of every kind, and the chips together turn a plain page into an interactive, connected document.

The Smart Canvas Idea

Google's name for all of this — chips, building blocks, interactive elements working together — is smart canvas. The idea is bigger than any single feature: instead of a document being an island of text, it becomes a canvas connected to everything else in Google Workspace. The people in your organization, the files in your Drive, the events on your calendar, the places on the map — a document can reach out and reference any of them, live.

The shift is worth pausing on. Traditionally a document is a snapshot: you type what you know at the moment, and it goes stale. A smart-canvas document is more like a dashboard. The people chips stay linked to real people; the file chips preview the current version of those files; the calendar chips point at real meetings. The document becomes a hub — a place where information, people, and tasks meet — rather than a dead-end where you retype things that live elsewhere.

You don't need every chip in every document — a personal letter needs none. But knowing the canvas is there changes what you reach for. A project plan, meeting notes, a team status doc, a research page full of references — these come alive when the people, files, and dates in them are real and interactive rather than typed and dead.

Honest Availability — What Needs Workspace

Now the honest part, because it matters and tutorials often skip it. Smart chips are not all equal across account types, and the difference usually comes down to context rather than a paywall on the feature itself.

The pattern: the core, self-contained chips — dates, dropdowns, checkboxes, table templates, links to your own files — work on a free personal account. The chips that lean on an organizational directory or calendar — rich people actions, calendar events — are naturally fuller on a Google Workspace account, because that's where a directory of coworkers and a shared calendar exist to connect to. It's less "pay to unlock" and more "these chips connect to things a personal account may not have."

⚠️ Important Note: Everything in this lesson's project uses core chips that work on a free personal account — a person from your contacts, a date, one of your own Drive files, a dropdown, and a table template. You will not need a paid account to complete it.

🎯 Project: Make a Plain Doc Interactive

You'll take a plain document and, using only the @ menu, add five kinds of interactivity: a person, a date, a linked Drive file, a dropdown, and a table template. By the end it should feel less like a page and more like a little app.

Project Hub — [your project]

Heading 2: Owner and dates
Owner: @[person chip]
Kickoff: @[date chip]
Reference: @[file chip to a Drive file]

Heading 2: Status
@[dropdown: Not started / In progress / Done]

Heading 2: Roadmap
@[table template: product roadmap]
  | Feature      | Status (dropdown) | Owner (person) | Due (date) |
  | First build  | In progress       | @you           | @date      |

Heading 2: To do
[ ] Draft the plan       (checklist item — click to tick)
[ ] Share with the team

Best Practices for Chips & Interactive Docs

✅ Do's

• Reach for @ first. Make typing @ your reflex for inserting anything structured — it's faster and reminds you what's possible.
• Use file chips instead of pasted links for Drive references, so readers preview in place instead of tab-hopping.
• Use dropdowns for fixed choices. Statuses and priorities picked from a list stay consistent across the whole document.
• Check sharing when using file chips. Make sure the linked file is shared with everyone who needs to open it.

❌ Don'ts

• Don't over-chip. A letter or an essay needs none — chips shine in plans, notes, and trackers, not in every paragraph.
• Don't assume every chip is available. Some depend on a Workspace account, an admin setting, or a gradual rollout.
• Don't rely on a chip for access. A file chip links, it doesn't grant permission — share the file itself.

📓 Learning Journal

📝 Lesson Summary

🎉 What You've Accomplished

You've turned a plain document into an interactive, connected one — inserting people, dates, files, dropdowns, and a table template, all from a single keystroke. You also understand the smart-canvas idea behind it, and you can tell honestly which pieces need a Workspace context and which work free.

❓ Common Questions at This Stage

🔭 Looking Ahead

In the next lesson — Lesson 6.3: Voice Typing, Translate, Dictionary & Add-ons — we turn to a different kind of power-up: tools that help you get words in and out of a document. You'll dictate a paragraph by voice, translate a copy, use the dictionary and word count, and browse an add-on — with an honest caution about the permissions add-ons ask for.

✅ Before the Next Lesson

• Keep your Project Hub doc — it's a great sandbox for experimenting with more chips
• Notice one real document this week that would benefit from a status dropdown or a file chip
• Write your Learning Journal entry for this lesson

📚 Additional Resources

• docs.google.com — try the @ menu in a new document
• Google Docs Help Center (Google Support)
• Google Docs on Google Workspace — smart canvas overview