How to use ChatGPT Work: Scheduled Tasks, plug-in directory and long task approval guide

ChatGPT Work is geared toward research, documents, spreadsheets, and long-term tasks. This article explains how to get started with Work, set up Scheduled Tasks, understand plugin directory permissions, and when you should require manual approval.

ChatGPT Work is a working mode in ChatGPT for longer tasks. It is suitable for researching information, organizing multiple sources, generating documents, tables, presentations, reports or Sites; the difference from ordinary chat is not that the answers are longer, but that the task can go through planning, execution, supplementary information, manual confirmation and subsequent modification.

If you just ask a question or polish a piece of text, it is faster to use Chat directly; if you are writing code, running tests, or processing warehouses, use Codex first. Work is better suited for transactional work that is somewhere in between: there are clear deliverables, but automation should not be allowed to cross permissions or business boundaries without confirmation.

First confirm whether ChatGPT Work is available

Work is gradually opening up to eligible accounts. At the beginning of the release, the web and mobile terminals are open to paid plans, but Free and Go are not included in the first batch; Pro, Pro Lite, Enterprise and Edu will receive priority access, and Plus and Business will be added in batches later. Actual availability is also affected by region, workspace, and administrator settings.

Once you see the entrance, you can start as follows:

  1. Select Work in the ChatGPT web, mobile or desktop app.
  2. Create a new conversation or start one in an existing Project to keep related conversations, files, and instructions together.
  3. Add the files, links, background information, delivery format, and acceptance criteria required for the task.
  4. State goals and boundaries first, then let Work come up with a plan or start execution.
  5. Check progress at key nodes, add constraints, change direction, and finally review the results.

If there is no Work entrance, do not guess the setting path based on screenshots or other people’s accounts. First confirm the package, client version and workspace policy before waiting for batch opening; this is not a problem that can be solved by logging in again or switching models.

How to divide work, chat and codex

model Better suited to the task Scenarios that should not be replaced
Chat Q&A, search, brainstorming, short text processing Tasks that are long-term or require complete deliverables
Work Research, analysis, documents, spreadsheets, reports, presentations and cross-tool workflows Directly manipulate unfamiliar local code bases or run development commands
Codex Coding, debugging, testing, repository modifications and code reviews General administrative organization or content delivery

Work on the desktop can use local files and desktop applications after obtaining permission; Work on the web and mobile cannot directly access files on the computer. At the beginning of the release, cloud Work conversations will not automatically appear in desktop Work, and local files and threads on the desktop will still remain on that computer. Before collaborating across devices, confirm which surface the task is actually running on to avoid mistakenly thinking that files have been automatically synchronized.

Scheduled Tasks are suitable for scheduling tasks

Scheduled Tasks allow Work to execute once, repeat on a schedule, run when an event occurs, or monitor changes continuously. It is suitable to leave repetitive information sorting to the system, and leave judgment and release to humans.

Relatively safe examples include:

  • Check new news from authorized channels every week and update the draft meeting agenda;
  • Check a designated web page or dashboard every day and only send a summary when changes occur;
  • Summarize customer feedback every week and form a list of product issues to be reviewed by topic;
  • Refresh the project tracking sheet every Friday and mark overdue items for confirmation by the person in charge.

When creating a task, the prompt word should clearly state the data range, running frequency, output position and stop condition. For example:

Check the connected project channel every Monday morning, summarize the unclosed items from the previous week, and generate a Markdown draft by responsible person and deadline. Don’t send the message, don’t modify the original task; if the owner or date is missing, just mark the item for confirmation in the report.

This is more controllable than “help me follow up on the project every week” and also provides a clear basis for subsequent reviews.

How to manage Scheduled Tasks

The Scheduled page of ChatGPT will focus on displaying enabled tasks, next run time and running status. Here you can pause, resume, edit or delete tasks. There are also several restrictions that should be noted when setting up:

  • The upper limit of active tasks varies by package; first look at the actual limit in the current account interface.
  • The task running frequency cannot be higher than every hour, so it is not suitable for second-level monitoring.
  • Tasks that have been left uninteractive for a long period of time may be automatically suspended. You should check regularly to see if the task still needs to be continued.
  • Monitoring tasks can search the web or view changes in connected applications, but should only notify when there are changes worth reporting to avoid creating meaningless noise.

If you are using Pulse to receive proactive updates, you should check whether you need to migrate to Scheduled Tasks. The working methods and entrances of the two may be different, do not assume that old updates will automatically be converted to new tasks.

The plugin directory is not an automatic authorization list

ChatGPT is replacing the original App Directory with Plugin Directory. Plug-ins can package skills, apps, and workflow-specific templates; but being able to see a plug-in does not mean that every member can install or use it.

For personal accounts, first check which accounts or application connections are required by the plug-in itself. For Business, Enterprise, and Edu workspaces, also confirm:

  1. Whether the administrator allows the plugin in Workspace settings > Plugins.
  2. Whether the app the plug-in depends on has been opened to your role in Workspace settings > Apps.
  3. Whether existing application permissions, operation approvals, synchronization policies, domain name restrictions, and third-party certifications still meet the requirements.
  4. Whether the workspace is set to Available or Installed for this role, and whether additional authorization is required.

This check sequence can avoid the common misjudgment that “the plug-in is displayed in the directory, but the Work cannot read the data or perform the action”.

Where should long task approval be placed?

Work can show progress during execution, ask questions, and request approval before important actions. Don’t think of approval as the last look at the results, but before the risk occurs.

Recommended actions that require manual approval include:

  • Send outgoing emails, messages, invitations or public web pages;
  • Modify shared documents, project status, schedules, financial tables, or customer data;
  • Use sensitive content in connected applications;
  • Change permissions, install plug-ins or connect new third-party services;
  • Making irreversible business decisions based on incomplete information.

Approval rules can be written directly at the beginning of the task, for example: “Can retrieve, summarize and generate drafts; when it involves sending, publishing, deleting, modifying shared data or calling paid services, first list the intended actions and scope of impact and wait for my confirmation.” This is more reliable than undoing it afterwards.

Two reusable Work prompt words

Weekly project report draft

Based on the files in this Project and connected project tools, summarize this week’s completed items, risks, blocking items, and next week’s plan. Give the source list and missing information first, do not modify the project system, and do not send the content to anyone. Upon completion, a draft of the weekly report is generated that is ready for review.

Competitive Information Monitoring

Check my three designated official websites and authorized sources of information every Wednesday. Generate summaries only when product, price, API, or availability changes, including original link, date of change, and likely impact; do not supplement facts based on media speculation. Any action to send or create a task requires approval first.

Both types of prompt words clearly state the “input range, allowed actions, output format, and approval boundaries”, which is suitable for small-scale testing first, and then gradually increasing the connection application and automation level.

FAQ

Work Why can’t I see the files on my computer?

Web and mobile Work cannot directly read local files. When local files are needed, use the desktop app and grant access only to the files or folders required for the task; alternatively, upload only the necessary files manually instead of providing your entire disk as context.

Why are Scheduled Tasks not executing as expected?

First go to the Scheduled page to confirm whether the task is enabled, whether the next run time is correct, and whether it has reached the package limit or been automatically suspended. Then check whether the task description clarifies the data source and trigger conditions. For monitoring tasks, you should also confirm that “no notification when there are no changes” is not misinterpreted as “not running”.

Why can’t I use the plug-in even after it’s installed?

Typically one of the layers of workspace roles, associated apps, administrator permissions, third-party authentication, or approval policies has not been met. Checking in the order of “Directory Visible → Plug-in Allowed → App Authorization → Account Authentication → Action Approval” is more effective than repeated reinstallation.

Summarize

The value of ChatGPT Work lies in putting longer research and delivery tasks into reviewable processes, rather than handing everything over to automation. First, clearly divide Work, Chat and Codex; Scheduled Tasks start with low-risk, repeatable, and verifiable work; plug-ins are checked according to workspace permission links; manual approval is reserved for sending, publishing, modifying shared data, and payment actions. In this way, automation can reduce duplication of work instead of expanding uncontrollable impacts.

Official information:

记录并分享
Built with Hugo
Theme Stack designed by Jimmy