> 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/console.md).

# Console

### Overview

Console is a natural language interface for searching and investigation.

Availability and capabilities vary by plan and permissions.

### Key Concepts

* **Query**: prompt used to retrieve an answer or item set
* **Sources**: links to the underlying items used to support an answer
* **Scope**: Organization and Project boundaries applied to results
* **Permissions**: access rules that constrain visibility

### How It’s Used

Use Console to find decisions, approvals, and blockers quickly.

Use it during troubleshooting to validate what changed and when.

### Benefits

* Faster discovery across Projects
* Better governance through linked sources
* Reduced manual navigation during investigations

### Setup Steps

Start with the Console workflow pages:

* [Console Overview and Access](broken://spaces/bO5MkvlsUXaVsGsjqKWy/pages/IHr5D4941EfyTqBdCYqy)
* [Console Features and Capabilities](broken://spaces/bO5MkvlsUXaVsGsjqKWy/pages/f6mM0HdSZi2Fc8RoDp6F)

### Best Practices

* Start with a focused query and add constraints gradually.
* Validate sources before using outputs for governance decisions.
* Convert follow-up work into tasks and Save Views.

### Summary

Console provides fast retrieval and investigation through natural language queries and source links.

Related:

* [Console Overview and Access](broken://spaces/bO5MkvlsUXaVsGsjqKWy/pages/IHr5D4941EfyTqBdCYqy)
* [Console Features and Capabilities](broken://spaces/bO5MkvlsUXaVsGsjqKWy/pages/f6mM0HdSZi2Fc8RoDp6F)
* [Console AI Search](/ai/console-ai-search.md)

### Overview

Console provides a single place to ask questions across Transform content.

It returns answers with linked sources when available.

### Key Concepts

* **Scope**: Organization and Project boundaries applied to results
* **Result**: item, summary, or linked source
* **Access**: permissions that constrain what can be retrieved

### How It’s Used

Use Console when discovery is slower than direct navigation.

Use it during governance reviews to validate decisions and approvals.

### Benefits

* Faster retrieval of high-signal information
* Better traceability through source links
* Reduced manual searching across Projects

### Setup Steps

{% stepper %}
{% step %}

### Confirm access

Confirm access exists for the Organization and Project scope that should be searchable.
{% endstep %}

{% step %}

### Open Console

Navigate to **Console** from the main navigation.
{% endstep %}

{% step %}

### Run a first query

Use a focused query such as:

* `blocked requirements`
* `decisions about testing scope`
* `overdue tasks this week`
  {% endstep %}

{% step %}

### Validate sources

Open at least one source link to confirm accuracy.
{% endstep %}
{% endstepper %}

### Best Practices

* Keep queries short and specific.
* Add one constraint at a time, such as time window or status.
* Convert follow-up actions into tasks and Save Views.

### Summary

Related:

* [Using Console for Natural Language Search](/ai/using-console-for-natural-language-search.md)
* [Console Features and Capabilities](broken://spaces/bO5MkvlsUXaVsGsjqKWy/pages/f6mM0HdSZi2Fc8RoDp6F)

### Overview

Console works best with focused questions.

Use the patterns below. Then iterate based on results.

### Key Concepts

* **Constraint**: filter term, such as time window or status
* **Object type**: requirements, tasks, tests, meetings
* **Sources**: links used to validate an answer

### How It’s Used

Start with a short query and add constraints gradually.

Validate results using source links.

### Benefits

* Faster retrieval of decisions and blockers
* More repeatable review questions during governance
* Better traceability through explicit sources

### Setup Steps

#### Good query patterns

**Find specific work**

* `show tasks assigned to a Teammate due this week`
* `requirements related to order-to-cash`
* `tests that failed in acceptance testing`

**Find risk and blockers**

* `what is blocked right now`
* `overdue tasks by owner`
* `requirements missing tests`

**Find decisions**

* `decisions from last 30 days`
* `approvals for go-live scope`

**Summarize and recap**

* `summarize project progress`
* `what changed since last week`
* `key open questions`

{% hint style="info" %}
Screenshot placeholder: Console results with a “sources” list linking to items.
{% endhint %}

### Best Practices

* Include time windows: “this week”, “last 30 days”.
* Include object types: “tasks”, “requirements”, “tests”.
* Include owners: for example, “assigned to a Teammate” or “owned by a Line of Business lead”.
* Ask for “sources” when traceability is required.

<details>

<summary>Examples by role</summary>

Project lead:

* `summarize blockers by workstream`
* `overdue items by owner`

Business analyst:

* `requirements awaiting review`
* `open questions tagged integration`

Tester:

* `failed tests needing retest`
* `tests linked to requirement X`

</details>

### Troubleshooting

<details>

<summary>I’m getting generic results</summary>

Tighten the question:

* add a time window
* specify a workstream (process/system)
* specify an object type

</details>

<details>

<summary>I can’t find something I know exists</summary>

Possible causes:

* access does not include the required Organization or Project
* the item title uses different wording
* the item is archived or filtered out

Try searching by a unique keyword from the title or description.

</details>

### Summary

Query quality improves with constraints, object types, and validated sources.

Store follow-up work in tasks and Save Views for repeatable governance.

Related:

* [Using Console for Natural Language Search](/ai/using-console-for-natural-language-search.md)
* [Finding Decisions and Approvals](/ai/finding-decisions-and-approvals.md)

### Overview

Console features improve query precision and answer quality.

They support repeatable governance questions and investigations.

### Key Concepts

* **Query**: natural language text used to retrieve results
* **Filter**: constraint on the result set, such as time window or item type
* **Source**: linked item used to support an answer
* **Scope**: Organization and Project boundaries applied to results

### How It’s Used

Use filters and scope constraints to reduce noise.

Use decision-focused patterns to improve retrieval.

### Benefits

* Faster answers with fewer retries
* Better auditability through linked sources
* More repeatable governance workflows

### Setup Steps

{% stepper %}
{% step %}

### Narrow scope first

Add a scope constraint when results are too broad.
{% endstep %}

{% step %}

### Add filters gradually

Add one filter at a time, such as:

* time window
* status
* item type (requirements, tasks, tests)
  {% endstep %}

{% step %}

### Request sources

Open at least one source link to validate answer quality.
{% endstep %}
{% endstepper %}

### Best Practices

* Use consistent decision patterns, such as `Decision:` and `Approved by:`.
* Prefer stable Process, System, and Segment naming for better retrieval.
* Store repeatable review questions as a small list for governance meetings.

### Summary

Related:

* [Finding Decisions and Approvals](/ai/finding-decisions-and-approvals.md)
* [Console Search Tips and Examples](/ai/console-search-tips-and-examples.md)


---

# 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, and the optional `goal` query parameter:

```
GET https://help.transform.ai/ai/console.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.