Projects
How Projects organize intelligence and control access to shared research.
A Project groups work around one intelligence objective. It connects chats, reports, profiles, graphs, images, evidence, and private documents. Projects require Lite, Pro, or Elite.
The Project boundary
Each Project belongs to a workspace and has an owner. It starts private. Its owner can grant selected workspace members access as readers or editors. Workspace membership alone does not grant Project access.
Private conversations and linked resources retain their own permissions. A Project grant does not expose every resource its owner can read. Y2 checks access again when background work runs.
Project knowledge remains separate from Global Knowledge. Archiving a knowledge binding does not publish it elsewhere.
Project views
| View | Purpose |
|---|---|
| Graph | Maintain the investigation graph |
| Timeline | Review intelligence and activity in time order |
| Situation | Explore linked geographic signals |
| Evidence | Preserve sources, notes, tags, and lineage |
| Knowledge | Add documents for Project chat |
| Overview | Review resources, recent chats, and eligible Automations |
Projects and Automations
Automations require Pro or Elite. They can use an active Project when their owner has write access. Their output stays associated with that Project.
Elite governance
Audit records identify the user and workspace for significant Project changes. Governance access does not grant access to private Project content.