Module B
Artifacts and live sites - a result you can click
A Work task does not end with text in a chat window. It hands you a file - and if you ask, a working site on its own address. This lesson covers what to order, how to manage it and where the risk starts.
Slide deck (.pptx)
A complete file with slide layout, tables and charts - opens in PowerPoint, not a screenshot.
What to ask for: State the slide count, one slide = one idea, plus who reads it and in how many minutes.
Rich document with tables and checklists
A longer piece with structure: headings, comparison tables, checklists you can tick off.
What to ask for: List the sections you expect and a maximum length - otherwise you get an essay.
Spreadsheet
Data across tabs, formulas, assumptions separated from calculations.
What to ask for: Ask for a separate "assumptions" tab - without it you cannot audit where a number came from.
Interactive web app
A working interface: filters, charts, forms. You can keep it in the chat or publish it as a site.
What to ask for: Describe what the user should be able to click - that defines the app better than looks.
@sites - a site instead of a file
Command center, client portal, team dashboard
The @sites command in a prompt tells the task that the deliverable is a hosted app, not a downloadable file. The rest of the prompt looks like any task description: goal, sections, data, access.
@sites GOAL: a command center for the sales team - one page I open every morning. DELIVERABLE: a page with four sections: 1) pipeline: deal count and value per stage, bar chart, 2) a top-10 deals table with last-contact date and an alert colour after 14 days of silence, 3) today's task list with checkboxes persisted in the browser, 4) a note-of-the-day field. DATA: the uploaded crm-export.csv. Do not invent records that are not in it. ACCESS: private page, me only, until I say otherwise. LOOKS: readable on a phone, light and dark background, no animations.
Publishing
Instead of a file, the Work task hands you a working page on a chatgpt.site address. No server to set up, no hosting to configure.
Before you send the link to anyone, open it in a private window and see what a stranger sees.
Access and address
You decide whether the page is private, limited to named people, or public. The address can be customized and, for serious use, pointed at a company domain.
"Public" means: anyone with the link. If the page carries client names, that is a disclosure of personal data.
Environment variables
Keep API keys and tokens only in a server-side secret store. Configuration exposed to the browser is not safe - anything that reaches the browser is visible to the user.
A key in a secret store is still a key someone can burn through. Give it a quota and its own narrow scoped permissions.
Lifecycle
The page lives on even after you forget the conversation. Put a review in your calendar: once a month check which pages are still needed.
The most common incident is not a breach - it is a forgotten page with last year's data.
Availability depends on your plan, region, workspace and administrator configuration.
Interactive blocks - when the answer should be an interface
Not everything needs its own site. Some things are best delivered as a block inside the conversation that you can click and edit. The rule is simple: if after reading the answer you would start recalculating, reordering or rewriting something - ask for a block instead.
Kanban board
Laying out a rollout or a sprint when a bullet list stops being enough.
Instead of a task list, give me an interactive kanban board with To do / In progress / Done columns. Cards carry an owner and a due date, and dragging should persist the state.
Calculator
Pricing, discount or ROI conversations where "what if" is the whole point.
Build an interactive margin calculator: sliders for price, cost and volume, a live result, and a three-scenario table beside it. Show the formulas you used.
Flowchart
A process with conditions and branches - prose loses the exceptions.
Draw this process as a flowchart with decision points and the places where a human approval is required. Below the diagram, list the exceptions you could not draw.
Editable email block
Replies you would edit anyway - edit them in place instead of copying back and forth.
Draft the reply as an editable email block: subject, body, recipients. I want to edit the text in the block. Do not send - I will trigger the send myself after reading it.
An email block can send the message with one click through your connected mailbox. That is convenient and therefore dangerous: sending cannot be undone. Stick to the same ladder as for every action outside the chat.
Every action outside the chat
- READthe agent reads
- DRAFTprepares a draft
- REVIEWyou review it
- APPROVEyou approve
- WRITE / SENDonly now it writes or sends
Codex → Sites
Sites: from draft to sharing
The supplied screen lists sites alongside their publication and access status. Publishing and choosing the audience are separate decisions.
- 1. Find or create a site
- 2. Review preview and access
- 3. Publish and verify the link
- Create / Search sites
- Create starts a new site; search finds an existing one.
- Owned by you / Shared with you
- Filters distinguish your sites from ones shared with you.
- Not published / Publish
- An unpublished entry offers Publish. Review the preview and access settings before publishing.
- Only you / Everyone
- The Shared with column shows the audience. In the supplied screenshot these labels distinguish private and broadly shared items; inspect your site's actual access settings.
- Share / …
- Share opens sharing controls. The ellipsis opens further actions; inspect labels and confirmation dialogs.
Try it without publishing
Open Sites, locate one entry and identify its publication and access status. Before sharing a real site, inspect its content and verify the link using an account with the intended access.