> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/getting-started/the-logicnets-designer/designer-project-report.md).

# Designer Project Report

## Description

This feature is useful in documenting and preserving a record of your projects. For any project, you can generate and download an HTML-based report that outlines the logicnets, nodes, parts and content resources used in a project.

## Generate and Save Report

In the bottom panel of the Designer screen, select the *Review* tab. Note, based on your subscription/license, not all tabs in the image below may be visible in your account.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-3acc5f486c7396508857ec9b49255306e22c3856%2Fe53aabde-6754-44cc-b44c-71bc4dedcadf.png?alt=media)

Select the following:

1. ***Generate report*** - When you click this the system creates a report and allows you to review the report.
2. ***Download report*** - Once you have created a report, click this to download an HTML file of the report for printing and other use.

Notes:

* If you are using version control, the system prints the project revision number in the header.
* You can hardcode the project version in the project settings.

### Tips and Tricks

When using version control, we recommend that you generate/save copies once you check in the project so the report is tied to the designs you included in the revision. Once the project is checked out and edited, the report will correspond to the designer project as it is in the revision PLUS any new changes made since the checkout date/time.

### Using Profiles

The default Designer Project Report uses the "All Access" Designer Profile that prints all the active parameters for a node.

If you are using Designer Profiles you have access to a custom profile that only displays your relevant configuration items in the part editors (see the [Designer Profiles](/release-9/platform-documentation/system-administration/system-settings/designer-profiles.md) article for more information).

Running the Designer Project Report after selecting that profile will generate the report only displaying the configuration items from the profile, and hiding unused and irrelevant fields.


---

# 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://community-test.logicnets.com/release-9/getting-started/the-logicnets-designer/designer-project-report.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.