原文核对：2026-10-13 · 中文正文 · 英文提示词与演示
场景定位
在 ChatGPT Work 中使用 Sites 构建并测试聚焦具体工作流的内部应用，按需添加存储，再将审阅后的版本分享给合适的受众。
- 难度
- 中级
- 时间跨度
- 30 分钟
适合用于
- 希望把重复工作流转成专用内部工具的团队。
- 需要轻量存储、文件上传或工作区共享的应用。
起步提示词
英文原文 · 可复制后按实际材料修改
Use @Sites to build a private internal app for [describe the workflow or tool you need]. Use any attached files or linked documents to understand who it's for, what information it should show, and what people need to do.
Build a focused first version and check that it works on mobile and desktop. Show me a private preview, explain anything that needs my review, and make it easy to iterate.
Do not publish or share the app, change its access, or contact anyone without asking me first.在同一任务中构建和部署
Sites 是 ChatGPT 中的托管服务。你可以让 ChatGPT 创建应用，它能构建项目、启动测试、部署，并返回可分享的 URL。
根据本次核对的原文，Sites 面向符合条件的付费套餐公开测试，推出时不支持 Free、Go，以及欧洲经济区、瑞士和英国。分批开放进度和工作区设置也会影响可用性。
Sites 支持从静态网站到全栈 JavaScript、TypeScript Web 应用，适合目标明确的内部工具，例如入职仪表盘、培训中心、可搜索的资源库、轻量工作流应用和报告页面。
设置、存储、部署和访问权限指南请参阅 Sites 文档。
从一个有用的工作流开始。清晰的首个版本更容易审阅、部署和改进，不必一开始就重建整套内部系统。
你会得到什么
下面是使用已上传发布说明和五条示例请求的虚构案例。首次构建并检查一个聚焦需求的请求跟踪器，后续增加负责人筛选器，并让逾期请求更醒目。
查看官方对话演示（英文）
ChatGPT Work conversation showing an internal launch-request tracker being built, checked, and refined before sharing.
用户
Use @Sites to build a private internal app for [describe the workflow or tool you need]. Use any attached files or linked documents to understand who it's for, what information it should show, and what people need to do. Build a focused first version and check that it works on mobile and desktop. Show me a private preview, explain anything that needs my review, and make it easy to iterate. Do not publish or share the app, change its access, or contact anyone without asking me first.
ChatGPT
Sites · Reviewed the launch brief and five sample requests
Sites · Built a private launch-request tracker preview
Sites · Checked filters, adding a request, saved state, and responsive layout
The launch-request tracker is ready to review: • Five clearly labeled sample requests, including blocked, in-review, and overdue work. • Each request shows its launch, owner, status, and due date. • Blocked requests appear first, and ready requests require an owner. • Adding requests, filtering, saved state, and mobile and desktop layouts were checked. The preview is private. Nothing was published or shared.
用户
Add an owner filter and make overdue requests easier to spot. Keep blocked requests at the top.
ChatGPT
Sites · Added an owner filter and highlighted overdue requests
Done. You can now filter requests by owner, overdue work has a clear visual indicator, and blocked requests stay at the top. Requests still cannot be marked ready without an owner. The preview remains private.
提供工作流背景
说明应用面向谁、用户要做什么、应检查哪些源材料，以及哪些内容需要跨会话保留。明确预期共享范围，并要求 ChatGPT 在部署前测试主要流程。
使用插件获取或更新已连接内部来源的数据。需要使用连接应用或云文件的 Sites 任务，可在网页端 Work，或桌面端 Work、Codex 中启动。本地文件使用桌面应用；需要登录的网站使用内置浏览器；已有 Chrome 会话使用 Codex Chrome 扩展。
需要实时取数时，可以在 Site 设置中配置第三方工具的 API key。不要把秘密值写进提示词或文件。如果希望通过插件连接取数，可以在当前任务中设置定时工作：用插件获取数据、更新应用，并保存一个供审阅的版本。审阅后获批才部署。
选择应用存储
许多内部应用需要持久化。Sites 支持两种存储：
- D1：兼容 SQLite 的数据库，用于清单状态、书签、筛选条件、注释、配置和文件元数据等结构化数据。
- R2 对象存储：用于上传文档、图片和其他需持久保存资源的文件内容。
结构化元数据放在 D1，较大的文件对象放在 R2。只读资源页或小型静态站点可能两者都不需要。
Sites 不支持数据或推理驻留。不要使用它处理受保护的健康信息、支付卡数据或开展金融交易。存储敏感信息前，请查阅 Sites 的数据和使用限制。
管理和分享项目
你可以管理谁能访问已部署的项目。
新项目在审阅内容、数据处理方式和目标受众期间，应保持私有。
根据账号和工作区设置，可以分享给：
- 受邀人员。
- 工作区内所有人。
- 互联网上的任何人。
共享仅允许访问项目，不赋予编辑权限。要变更访问范围，可以打开 ChatGPT 中的 Sites，或直接提出要求：
官方提示词
英文原文 · 可复制后按实际材料修改
Change this site's access to everyone in my workspace.面向工作区之外人群的轻量活动指南、社团资源页等，也可以公开分享。Enterprise 工作区默认关闭公开发布，需管理员启用。即使可以生成公开链接，也应保持内部数据私有。
示例
Sites showcase 提供了包含完整提示词的示例：
- Onboarding Hub：结合首周清单、资源、笔记和上传文档；D1 保存用户状态与文件元数据，R2 保存上传文件内容。
- Enablement Hub：提供可搜索的培训资料库，使用 D1 保存筛选条件和书签。
- Pulse Dashboard：展示指标、趋势和数据来源链，使用 D1 保存配置与缓存快照。
- Sparkboard：将员工创意征集转成工作流，包含认证提交、投票、评论、状态看板和贡献者排名。
- Launch Cal：按月历组织即将发布的产品，结合筛选、风险信号、清单和已连接来源引用。
- Event Planning Hub：结合活动申请、审批、模板、里程碑、政策准备检查和已连接的规划资源。
可以从这些示例开始，再围绕团队工作流和源材料缩小提示词范围。
展开英文原文对照
Use Sites in ChatGPT Work to build and test a focused internal app, add storage when the workflow needs it, and share the reviewed version with the right audience.
Build and deploy from one task
Sites is a managed hosting service in ChatGPT. Ask ChatGPT to create an app, and it can build the project, run it for testing, deploy it, and return a URL you can share.
Sites is in public beta for eligible paid plans. It isn’t available on Free or Go, or in the EEA, Switzerland, or the United Kingdom at launch, and rollout or workspace settings can affect access.
The scope ranges from static sites to full-stack JavaScript or TypeScript web apps. That makes Sites a good fit for focused internal tools: onboarding dashboards, training hubs, searchable resource libraries, lightweight workflow apps, and reporting views.
See the Sites documentation for setup, storage, deployment, and access guidance.
Start with one useful workflow. A clear first version is easier to review, deploy, and improve than a broad request to recreate an entire internal system.
What to expect
Here is a fictional example using an attached launch brief and five sample requests. The first pass creates and checks a focused request tracker; the follow-up adds an owner filter and makes overdue requests easier to see.
查看官方对话演示（英文）
ChatGPT Work conversation showing an internal launch-request tracker being built, checked, and refined before sharing.
用户
Use @Sites to build a private internal app for [describe the workflow or tool you need]. Use any attached files or linked documents to understand who it's for, what information it should show, and what people need to do. Build a focused first version and check that it works on mobile and desktop. Show me a private preview, explain anything that needs my review, and make it easy to iterate. Do not publish or share the app, change its access, or contact anyone without asking me first.
ChatGPT
Sites · Reviewed the launch brief and five sample requests
Sites · Built a private launch-request tracker preview
Sites · Checked filters, adding a request, saved state, and responsive layout
The launch-request tracker is ready to review: • Five clearly labeled sample requests, including blocked, in-review, and overdue work. • Each request shows its launch, owner, status, and due date. • Blocked requests appear first, and ready requests require an owner. • Adding requests, filtering, saved state, and mobile and desktop layouts were checked. The preview is private. Nothing was published or shared.
用户
Add an owner filter and make overdue requests easier to spot. Keep blocked requests at the top.
ChatGPT
Sites · Added an owner filter and highlighted overdue requests
Done. You can now filter requests by owner, overdue work has a clear visual indicator, and blocked requests stay at the top. Requests still cannot be marked ready without an owner. The preview remains private.
Give ChatGPT the workflow context
Tell ChatGPT who the app is for, what people should do, which source material it should inspect, and what should persist between sessions. Be explicit about the intended sharing scope and ask ChatGPT to test the main flow before it deploys.
Use plugins to fetch or refresh data from connected internal sources. Start a Sites task that uses connected apps or cloud files in Work on the web, or in Work or Codex on desktop. Use the desktop app for a local file, the built-in browser for a signed-in site, or the Codex Chrome extension for an existing Chrome session.
If you need live data fetching, you can connect to a third-party tool using an API key configured in the Site’s settings. Keep secret values out of prompts and files. If you want to use plugin connections, you can schedule work from the current task to fetch data with plugins on a set schedule, update the app, and save a version for review. Deploy the reviewed version only after approval.
Choose storage for the app
Many internal apps need persistence. Sites supports two storage primitives:
- Use D1, a SQLite-compatible database, for structured data such as checklist state, bookmarks, filters, annotations, configuration, and file metadata.
- Use R2 object storage for file bytes such as uploaded documents, images, or other assets that should persist.
Keep structured metadata in D1 and larger file objects in R2. A read-only resource page or small static site may not need either one.
Sites doesn’t support data or inference residency. Don’t use it to process protected health information or payment-card data, or to enable financial transactions. Review the Sites data and usage restrictions before storing sensitive information.
Manage and share your projects
You can manage who can visit your deployed projects.
Keep a new project private while you review its content, data handling, and intended audience.
Depending on your account and workspace settings, you can share it with:
- People you invite.
- Everyone in your workspace.
- Anyone on the Internet.
Sharing lets people visit the project; it doesn’t let them edit it. To change access, open Sites in ChatGPT or ask ChatGPT directly:
官方提示词
英文原文 · 可复制后按实际材料修改
Change this site's access to everyone in my workspace.Public sharing also works for a lightweight event guide, club resource page, or other site meant for people outside a workspace. In Enterprise workspaces, public publishing is off by default and an admin must enable it. Keep internal data private even when a public link is available.
Examples
The Sites showcase includes Site examples with full prompts.
- Onboarding Hub combines a first-week checklist, resources, notes, and uploaded documents. It uses D1 for user state and file metadata, and R2 for uploaded file bytes.
- Enablement Hub provides a searchable training library with filters and saved bookmarks backed by D1.
- Pulse Dashboard presents metrics, trends, and lineage details while using D1 for configuration and cached snapshots.
- Sparkboard turns employee idea intake into a workflow with authenticated submissions, voting, comments, status boards, and contributor rankings.
- Launch Cal organizes upcoming product launches into a monthly calendar with filters, risk signals, checklists, and connected-source references.
- Event Planning Hub combines event requests, approvals, templates, milestones, policy readiness, and connected planning resources.
Use those examples as starting points, then narrow the prompt around your team’s workflow and source material.