Skip to lesson
Lesson 10 / 2018 min readUp to date as of 19 October 2026

Artifacts and live sites

A downloadable file or a site to share?

Choose whether you need a document, spreadsheet, presentation or site. Check its content, behaviour and audience before sharing.

Reading time is approximate. Allow extra time for the exercises; practice estimates are shown with the workshops.

After this lesson
  • Request the right output format
  • Prepare a site or interactive block and test it
  • Review publication, access and secret configuration
Section being translated

The chrome and course program are available in English. Deep training modules (prompt library, AI glossary, playbooks) are being translated - some content below is still in Polish.

Edition date and feature availability

Material revised: 19 October 2026; The interface and folder guide was revised on 19 October using supplied screenshots and OpenAI’s public plugin repositories; this does not reverify product access. The models in Chat, Work and Codex were checked on 16 October 2026, and the GPT-5.5 retirement date and Word access rules on 14 October 2026; other prices and availability were not fully reverified. Check the documentation and your account before using a feature: access depends on plan, region and administrator settings. Use the examples for practice and review the results yourself.

See how it works

From file to a result for the recipient

  1. Data

    Check source, period and completeness.

  2. Artifact

    Build a report, presentation or page.

  3. Test

    Open the result and check numbers and interactions.

  4. Sharing

    Check recipient access, then publish.

A concrete example

A dashboard may look correct while counting a row twice. Compare at least one total with the source data.

What does a working link prove?

Only availability at that address. It does not prove data accuracy or every recipient’s permissions.

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

  1. READthe agent reads
  2. DRAFTprepares a draft
  3. REVIEWyou review it
  4. APPROVEyou approve
  5. WRITE / SENDonly now it writes or sends
My progress

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.

Map of the Sites controls
  1. 1. Find or create a site
  2. 2. Review preview and access
  3. 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.

Check your understanding

A dashboard looks correct in your account. What else do you check before sharing?

This is a self-assessment. Mark the lesson complete after doing the exercise and reviewing the result.

Do this now

Build a dashboard with sample data. Check three calculations, filters and mobile layout. Before sharing, define the audience and access permissions.

How to know you can do it

Keep as evidence: A file or site suited to the task.

  • You explain the format choice.
  • You check content, calculations and behaviour.
  • You define recipients before sharing.

Mark the lesson complete after the exercise and review. Reading progress and quiz answers alone do not confirm practical skill.

Lesson status
In progress — 0% of the page scrolled
Next