> For the complete documentation index, see [llms.txt](https://docs.openbrim.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openbrim.org/templates/truss-bridge-workflow/organization-tb/saved-reports-tb.md).

# Saved Reports \[TB]

This section displays the reports created within the project after they have been saved. These saved reports can be accessed and reviewed without repeating the analysis and design processes. Additionally, they can be downloaded, shared, or have their links retrieved.

First, the report to be saved is opened within the model that has already undergone analysis and design.

![image-20250923-124056.png](https://openbrim.atlassian.net/wiki/download/attachments/2804514838/image-20250923-124056.png?api=v2)

Next, click the 'Save' button located at the top right. After this, the saved project will be listed automatically.

![image-20250923-124604.png](https://openbrim.atlassian.net/wiki/download/attachments/2804514838/image-20250923-124604.png?api=v2)

![image-20250923-124742.png](https://openbrim.atlassian.net/wiki/download/attachments/2804514838/image-20250923-124742.png?api=v2)

**Name:** The name of the saved report is displayed in this cell.

**Folder:** The name of the saved report folder is displayed in this cell.

**URL (readonly):** The URL of the saved report is displayed in this cell. By clicking the three-dot icon located next to the cell, the file can be viewed automatically.

![image-20250923-125504.png](https://openbrim.atlassian.net/wiki/download/attachments/2804514838/image-20250923-125504.png?api=v2)

![image-20250923-125711.png](https://openbrim.atlassian.net/wiki/download/attachments/2804514838/image-20250923-125711.png?api=v2)


---

# 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://docs.openbrim.org/templates/truss-bridge-workflow/organization-tb/saved-reports-tb.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.