> For the complete documentation index, see [llms.txt](https://alludium.gitbook.io/alludium-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://alludium.gitbook.io/alludium-docs/11.-projects/11.3-managing-projects.md).

# Managing Projects

After a project exists, use the project detail view to coordinate work, maintain context, and keep tasks moving.

## Viewing Projects

The Projects page shows projects available to you. A project card usually includes the project name, description, type or setup, and progress indicators where available.

Use search and filters to narrow the list when your workspace has many projects.

## Working In A Project

Open a project to work with its detail tabs.

| Tab              | Use It For                                                            |
| ---------------- | --------------------------------------------------------------------- |
| **Command**      | Orient around the current project state, stage, and manager guidance. |
| **Tasks**        | View or create project tasks.                                         |
| **Activity**     | Review project events and recent changes.                             |
| **Files**        | Upload, select, and preview project-specific files.                   |
| **Data**         | Review or update structured project fields.                           |
| **Operations**   | Use configured workflow controls.                                     |
| **Integrations** | Check project integration readiness.                                  |
| **Team**         | Review project membership and collaboration context.                  |

The tabs available for a project depend on its setup and workspace configuration.

## Project Tasks

Project tasks keep work tied to the project. Use them when a task depends on project state, project files, or project-specific data.

Tasks may be created manually, from a project setup, by an agent or manager, or through an automation. A task can also require structured output before completion.

## Project Data

Project data stores structured fields for the initiative. For a deal room, this might include company, stage, sector, geography, check size, thesis, risks, or decision state. Other project setups define different fields.

Keep project data current when agents, tasks, or teammates rely on it.

## Project Files

Use the Files tab for documents that belong to the project. These files can support tasks, project manager conversations, and review workflows.

When uploading files:

* Use clear names.
* Prefer source documents over summaries when evidence matters.
* Keep sensitive documents in the correct project.
* Confirm preview and readability where supported.

## Team And Access

Use the Team tab to review who has access to the project. Project access is separate from general workspace membership. A workspace member may need to be added to a project before they can use that project's context.

## Keeping Projects Healthy

Good projects have:

* A clear name and outcome
* Current project data
* Relevant files
* Tasks with owners or next steps
* Clean stage/progress state
* Only the integrations they actually need

Review stale projects periodically so task queues and automation do not drift.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://alludium.gitbook.io/alludium-docs/11.-projects/11.3-managing-projects.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.