> For the complete documentation index, see [llms.txt](https://docs.veedna.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.veedna.com/xbom/sbom360-hub/my-products.md).

# My Products

### What is the SBOMs Tab?

Your SBOM360 Hub account will open to the homepage, titled SBOMs. This is an organization wide SBOM database. Whenever SBOMs are published by your company, they will appear here upon approval.

### SBOMs Tab Features

This page has the features:

* Add to My SBOMs
  * Select the box to the left of your desired SBOM in the SBOMs tab
  * Go to the right of the screen and click Add to My SBOMs
  * Confirm that the SBOM has been added
* Upload
  * Jump to the guide on uploading SBOMs to SBOM360 Hub
* Share
  * Jump to the guide on sharing SBOMs with other users
* Request
  * Jump to the guide on requesting full access to SBOM data
* Download and Delete
  * Jump to the guides on downloading SBOMs to your computer and deleting SBOMs from SBOM360 Hub
* Details and View Details
  * Jump to the guides on reviewing the basic and elaborate SBOM details
* Assess & Export
  * Jump to the guide on creating an SBOM assessment report and exporting it to a PDF

<br>

<br>


---

# 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.veedna.com/xbom/sbom360-hub/my-products.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.
