Projects
Understand how Projects keep chats, evidence, documents, graphs, and intelligence outputs inside one workspace-bound objective.
Projects are private working contexts for a single intelligence objective. A Project connects related chats, reports, profiles, graph boards, generated images, evidence, and private documents without mixing them into another workspace or the global knowledge corpus.
Available on Lite, Pro, and Elite
Projects use the active workspace's plan. Free workspaces can see the upgrade path but cannot read or change Project data.
The Project boundary
Every Project has both a workspaceId and an ownerId. In this release, that means:
- The Project can use only resources owned by the same user in the same active workspace.
- Project chats and private knowledge stay attached to that Project.
- Switching workspaces removes access until the Project's workspace is active again.
- Other Elite workspace members do not automatically receive access. Project sharing is not yet supported.
Y2 checks the boundary again for background indexing, graph projection, chat writes, and Automation runs. A saved identifier alone does not grant access after membership or plan access changes.
Project views
| View | Purpose |
|---|---|
| Graph | Maintain a persistent graph for the objective. |
| Timeline | Review attached intelligence and Project activity in time order. |
| Situation | Explore geolocated signals attached to the Project. |
| Evidence | Preserve citations, captures, notes, tags, and lineage. |
| Knowledge | Add private source documents for Project-scoped retrieval. |
| Overview | Review attached resources, recent chats, and eligible Automations. |
Project knowledge is separate from Global Knowledge. Removing a Project binding archives that binding; it does not publish the content globally.
Projects and Automations
Projects are available starting with Lite. Automations require Pro or Elite. A Lite user can still use every Project view, but the Automation card presents the Pro upgrade path instead of querying protected Automation data.
On Pro or Elite, an Automation can be bound to a Project. Its output thread and run context remain inside the same owner and workspace boundary.
Elite governance
Elite workspaces add user-bound audit records for material Project changes, including Project creation and settings changes, resource and evidence lifecycle actions, graph changes, chat moves, and tracking-rule changes. Audit records identify the acting user and workspace; they do not make private Projects visible to other members.