---
title: "Organize Intelligence in a Project"
description: "Manage resources, evidence, knowledge, access, and archived work."
canonical: https://y2.dev/docs/projects/organizing-intelligence/
---

Projects

# Organize Intelligence in a Project

Manage resources, evidence, knowledge, access, and archived work.

Start with an existing Project in the active workspace. You need write access to change its content. Only the Project owner manages access.

## Attach reports and profiles

Open **Overview**. Search for a resource you own in the workspace. Choose its role, then attach it.

| Role          | Use                 |
| ------------- | ------------------- |
| Knowledge     | Background material |
| Working       | Active analysis     |
| Output        | Deliverables        |
| Primary graph | Main graph board    |

## Preserve and classify evidence

Open **Evidence**. Capture a web source or preserve citations from attached reports. Add notes and tags. Mark important items for later review. Trackers can classify future evidence by domain or URL prefix.

Before pruning a source, review its downstream lineage. It can support reports, graph objects, incidents, or assertions. Use archive when you need a reversible removal.

## Add private knowledge

Open **Knowledge**. Upload a supported document within the [storage limits](https://y2.dev/docs/projects/reference#view-and-storage-limits). PDFs must contain selectable text. Y2 does not accept scanned PDFs that require OCR.

Uploaded content is available to authorized Project chats. It does not enter Global Knowledge. Archive a binding to stop retrieval. Restore it when needed.

## Maintain the Project graph

Open **Graph** to create a graph, or save an Explorer graph to the Project. Saving again merges nodes and edges by identifier. See [graph limits](https://y2.dev/docs/projects/reference#view-and-storage-limits).

## Move an existing chat

Select a chat you own in the active workspace. Move it to an active Project where you have write access. Future messages and background work must pass that Project's access checks. A chat derived from a shared Project cannot move outside that Project.

## Manage access

As the Project owner, select **Manage access**. Choose a workspace member and a **Reader** or **Editor** role. Select **Grant access**. Use **Revoke** to remove a grant.

Private conversations and linked resources retain their existing permissions. Revocation also blocks retained Project conversations and future Project work.

## Archive completed work

Archive the Project when its objective is complete. Archiving removes it from active lists without deleting history. Restore it from the archived Projects view to resume work.