📊 Lesson 5.3: Audience Q&A, Auto-Advance & Publishing to the Web

The Audience Q&A Tool

Live questions are where a talk comes alive — but in a big room, only the loudest voices ever get heard, and you can't see the questions until someone shouts one. Slides has a lovely fix: a built-in audience Q&A tool. When you start a presentation with Q&A on, Slides shows a short question link at the top of the audience's screen. Anyone in the room types that link into their phone, submits a question, and — crucially — votes on other people's questions. The most-wanted questions float to the top.

From Presenter View, you control the whole thing: you see the incoming questions, and you can present a question on screen (blown up big) when you're ready to answer it, then dismiss it. This solves several problems at once — quiet people get a voice, the room decides what matters most by voting, and you're never ambushed because you see questions before you address them.

You start it from the Slideshow dropdown (look for an "Audience tools" or "Q&A" option) or from within Presenter View. It shines for lectures, conference talks, town halls, and any session big enough that a show of hands gets unwieldy. For a five-person meeting, just ask out loud — the tool earns its keep when the room is large. Two practical catches (at the time of writing): audience members generally need to be signed in to a Google account to submit or vote, and on school or work accounts an admin may limit who can ask, or the option may not appear at all — so test it before a big session.

Auto-Advance & Loop for Kiosks

Sometimes there's no presenter at all. A deck plays on a screen in a lobby, at a trade-show booth, in a museum, or on a monitor in the break room — advancing on its own, looping forever. Slides supports this with auto-advance (each slide displays for a set number of seconds, then moves on by itself) and loop (when it reaches the end, it starts over from the top). Together they make a deck a self-running kiosk.

You'll find these timing options in two places, depending on how you're running it:

• In Present mode: the faint bottom toolbar (or its settings menu) usually has an "auto-play" choice where you pick a per-slide interval and toggle looping. Good for a screen you set up and walk away from.
• In Publish to the web: when you publish (next section), you can set an auto-advance interval and choose to loop — baking the timing into a link or embed that plays itself anywhere.

Design changes for an unattended deck. There's no speaker to explain anything, so the slides must carry the whole message themselves — this is the one time "put the words on the slide" is right, because the slide is the presenter. Keep each slide readable at the interval you chose (a passer-by needs to catch it in a glance), and make the loop feel intentional rather than abruptly restarting mid-thought.

Publish to the Web

Publish to the web takes a snapshot of your deck and turns it into a plain web page anyone can view — no Google account, no sign-in, no permission request. You get two flavors:

• A link — a public URL that opens your deck as a self-contained presentation in any browser.
• An embed — a snippet of code you paste into a website or blog so the deck plays inline on that page.

When you publish, you can set auto-advance timing and loop, which is exactly how you create a self-running deck that lives on a web page or a kiosk browser. You'll find it on the File menu, under "Publish to the web" (or similar — menu names drift). The dialog gives you the link and the embed code, the timing options, and — important — a way to stop publishing later.

Because a published deck needs no account, it's the easiest possible way to put a presentation in front of the world — a portfolio on your personal site, an announcement embedded in a blog post, a looping display for an event. That same easiness is exactly why the next two sections matter so much: public is a strong word.

Share the File vs Publish to the Web

These two are easy to confuse, and the confusion is where privacy accidents happen. They answer different questions. Sharing (the Share button, covered fully in Module 6) grants specific people access to your real, live, editable deck — as viewers, commenters, or editors — and you can revoke it. Publishing broadcasts a read-only public snapshot to the open web, for anyone at all, no account needed.

Read the two branches carefully, because they behave very differently:

The short version: share to collaborate; publish to broadcast. If you only want a few named people to see something, share it — don't publish. Publishing is the right tool only when you truly want it out in the open.

The Privacy Line: Published Means Public

This deserves its own section because it's the one thing people most often get wrong. When you publish to the web, your deck is public. Not "public if someone finds the link" in a wink-wink way — genuinely accessible to anyone who has the URL, with no sign-in wall, and potentially discoverable by search engines or shareable onward by anyone who opens it. There is no "just the people I meant" — publishing is a broadcast.

A few honest, hedged cautions worth internalizing:

• Public can be found. A public URL may be indexed by search engines or forwarded by anyone who sees it. Treat "unlisted" as "not truly secret."
• Unpublishing isn't instant erasure. "Stop publishing" removes the live page, but cached or downloaded copies can persist elsewhere. Prevention beats cleanup.
• Embeds carry the same exposure. An embedded deck is just as public as a published link — anyone who views the host page can view the deck.
• Work/school accounts may differ. If you use Slides through a Google Workspace organization, an admin may restrict or disable publishing entirely — check your organization's rules.

None of this should scare you off a genuinely public deck — a portfolio, a public announcement, a conference resource are all perfect uses. The point is simply to choose publishing on purpose, knowing exactly what it does, rather than reaching for it when you actually just wanted to share with a few people. We go deep on sharing, link access, and privacy in Module 6 and Lesson 8.2.

Building a Self-Running Deck

Let's put the pieces together into a self-running deck — the kind that plays unattended on a screen. The recipe:

1. Design for no presenter. Since the slides do the talking, put the essential words on them, keep each readable at a glance, and make the sequence tell a complete little story on its own.
2. Choose your playback route. For a physical screen you'll set up and leave, use Present mode's auto-play with an interval and loop. For a web page or a remote display, use Publish to the web with auto-advance timing and loop turned on.
3. Pick a comfortable interval. Long enough to read the busiest slide without rushing, short enough that a passer-by doesn't get bored. Test it by standing back and reading as a stranger would.
4. Confirm the loop feels intentional. Make sure the last slide leads gracefully back to the first, so the restart reads as "the loop came around" rather than "it crashed."
5. Mind the privacy line. A kiosk in your own lobby on Present mode isn't public; a published web link is. If your self-running deck lives on a public URL, only put public-safe content in it.

⚠️ Important Note: The exact spots for Q&A, auto-play timing, and "Publish to the web" move as Google updates Slides, and organizations can disable publishing. Don't memorize positions — remember the three concepts: an audience Q&A link during a show, auto-advance + loop for unattended playback, and publish = public as distinct from private sharing. Those ideas survive every redesign.

🎯 Project: Q&A or a Self-Running Deck

Pick the path that fits your running deck and your curiosity. Either try the audience Q&A tool, or build an auto-advancing published version of your deck — and if that published version is private, practice unpublishing it, so the privacy line becomes muscle memory, not just a warning.

Before I click "Publish":
- Is EVERY slide safe to be seen by anyone on the internet?
  (no client names, internal numbers, personal data, unreleased plans)
- Do I actually want the WORLD to see this, or just a few people?
    -> world  = Publish to the web
    -> a few  = Share the file instead (Module 6)
- If private and I published anyway to test: STOP PUBLISHING when done.

Best Practices for Reach & Privacy

✅ Do's

• Invite Q&A early so people submit and vote throughout, giving you a ranked list.
• Design self-running decks for no presenter — the slides must carry the words.
• Run the privacy self-check before publishing. Would you put every slide on a billboard?
• Share to collaborate; publish to broadcast. Pick the tool that matches your intent.

❌ Don'ts

• Don't publish anything sensitive. Published means public, and unpublishing isn't instant erasure.
• Don't confuse publishing with sharing. One broadcasts to the world; the other invites specific people.
• Don't set a kiosk interval so short that a passer-by can't read the busiest slide.
• Don't assume an "unlisted" public link is secret — it can be found and forwarded.

📓 Learning Journal

📝 Lesson Summary

🎉 What You've Accomplished

Your deck now reaches past the moment you stop talking: it can gather the room's best questions, run itself on a screen, and — when you choose it deliberately — live on the open web. Just as importantly, you understand the privacy line that so many people cross by accident. You've finished the whole delivery module: organize a talk, write notes, present with confidence, and extend the deck's reach responsibly.

❓ Common Questions at This Stage

🔭 Looking Ahead

In the next lesson — Lesson 6.1: Sharing & Permissions — we open up the other side of that fork in this lesson's diagram. You'll learn to share the real, editable deck with the right people at the right access level (viewer, commenter, editor), manage link access safely, and hand off collaboration without accidentally over-sharing. It's the natural companion to everything you just learned about publishing.

✅ Before the Next Lesson

• Finish your chosen project path (Q&A or a self-running published deck)
• If you published a private deck to test, confirm you stopped publishing
• Be able to state, in one sentence, how sharing differs from publishing
• Write your Learning Journal entry for this lesson

📚 Additional Resources

• slides.google.com — open the app
• Google Slides Help Center (Google Support)
• Google Docs Editors Help Community