Work & Settings
Work & Settings keeps conversation, assigned work, history, and day-to-day choices together. Choose the service that owns the change or evidence you need.
Boundary
Work & Settings gives each service its own role. Agents & Workflows owns the Runs that Tasks may point to. Governance & Administration owns the Workspace, access, policy, and Governance Audit Log. Reading a notice does not change those owners' state. Open the object named by the notice when that work needs repair.
Services
Work & Settings gives each part of daily work a home. A Chat can lead to a Task. The Task can point to a Run's evidence. Notices tell people when that work needs them.
| Service | Reader decision |
|---|---|
| Chat | Keep a discussion and control who can read it. |
| Tasks | Assign a result and track its state and local history. |
| Activity | Follow execution history across kinds. |
| Notifications | Read a notice and check its delivery path. |
| Settings | Change member preferences and delivery choices. |
Start here
Follow Coordinate and recover work to assign work or recover a missed Task. The Console opens Work & Settings through each service. Start Chat at /c/new, open Tasks at /tasks, or read Activity at /activity. Member choices live at /settings/general. Notice choices live at /settings/notifications.
Use the thread list contract to read saved threads. Read API reference for exact HTTP calls, permissions, and responses. The Console guide explains access and how to find daily work.
Next steps
- Read Tasks when Work & Settings needs a durable owner and result.
- Read Activity when evidence spans several execution kinds.
- Read Notifications and settings when notice delivery needs a separate repair from the work itself.