> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/ai/searching-across-all-project-data.md).

# Searching Across All Project Data

### Overview

Cross-Project search supports discovery and governance reviews.

Console can surface related items when the location is unknown.

### Key Concepts

* **Cross-Project query**: query that spans more than one Project
* **Result scope**: Organization and Project boundaries applied to results
* **Source links**: traceable links to the underlying items

### How It’s Used

Use cross-Project search for portfolio-style questions.

Use it to find repeated decisions and common blockers across delivery work.

### Benefits

* Faster discovery across Projects
* Better reuse of prior decisions and patterns
* Earlier visibility into cross-team delivery risk

### Setup Steps

{% stepper %}
{% step %}

### Confirm Organization access

Confirm access exists for the intended Organization and Projects.
{% endstep %}

{% step %}

### Run a cross-Project query

Use a query such as:

* `blocked tasks across all projects`
* `requirements approved this month`
* `tests failing in acceptance testing`
  {% endstep %}

{% step %}

### Validate sources and capture follow-ups

Open source links and capture follow-up tasks in the correct Project.
{% endstep %}
{% endstepper %}

### Best Practices

* Keep Process and System naming consistent across Projects.
* Use Segment Types for consistent reporting dimensions.
* Convert high-signal findings into tasks and Save Views.

### Summary

Cross-Project search is strongest when scope is consistent and sources are verified.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.transform.ai/ai/searching-across-all-project-data.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.