Skip to main content

​
Overview

Projects are organizational groups for work that belongs together. Use a Project to bring related Apps, Flows, Missions, and chat threads into one shared context without changing their existing tags, categories, or execution state. Projects are separate from the internal execution project used by a Mission. A Mission can therefore keep its execution history while also being assigned to an organizational Project for discovery and coordination.

​
Create and manage Projects

Create a Project with a name and optional description. Project names can contain up to 255 characters, and descriptions can contain up to 5,000 characters. Projects can be renamed, edited, archived, and restored. Archiving does not remove existing assignments; archived Projects are omitted from the default Project list but can still be retrieved.

​
Assign work

Assign or clear a Project from the owning feature:
  • Apps — use the Edit Metadata modal when you can manage the App.
  • Flows — use the Project control in the flow detail view when you can edit the Flow.
  • Missions — use the Project control in mission details when you have Mission edit permission. For the Mission Center’s Today and History views, see Missions and Tasks.
  • Chats — start a chat from a Project context or change the assignment from the thread controls.
An item can belong to at most one organizational Project. Select No Project to clear an assignment. The Project label appears with the item wherever the feature displays Project metadata. The Apps Library and Flows workspace provide Project filtering, sorting, and grouping. The Apps Library also keeps legacy dashboards in the grouped view without assigning them to an organizational Project. Project choices include all Projects, No Project, and a named Project. When an app has a non-empty last error and its recorded stop_reason is dataset_preflight_failed, its library card and row explain that the underlying dataset is missing or unavailable and advise discussing repair or recreation with your agent.

​
API access

For automation, use the organizational Project routes documented in the API Reference.