> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/scan-fix-and-prevent/scan-with-snyk/snyk-projects/project-information.md).

# Project information

The **Projects** page lists imported Projects and information about the Projects, such as vulnerabilities and license issues. On this page, you can group, filter, and sort your Projects and activate, deactivate, change test frequency, or delete them.

## Filter existing Projects

On the **Projects** page, you can filter your Projects by whether or not they contain issues and by the type of Git integration. The following filters are available:

* **Show**:
  * **With issues** - displays only Projects with issues.
  * **Without issues** - displays only Projects without issues.
* **Integrations** - displays the integrated Git repositories imported to Snyk.

To reset all filter criteria, click **Reset**.

{% hint style="info" %}
Only active Projects with discovered issues are displayed on the Projects page by default.
{% endhint %}

## View Project details

To view detailed information for a Project, click a Project entry. The page that opens displays the detailed Project information.

The following information is available:

* **Header**: displays a summary of the Project. See [Project summary](#view-project-summary).
* **Issue cards**: display summaries of issues found. See [Issue card information](/scan-fix-and-prevent/scan-with-snyk/snyk-projects/issue-card-information.md).
* **Views** (links at top right):
  * **Overview**: displays [Project issues, fixes, and dependencies](/scan-fix-and-prevent/scan-with-snyk/snyk-projects/view-project-issues-fixes-and-dependencies.md).
  * **History**: displays historical snapshots of recent tests. See [View Project history](/scan-fix-and-prevent/scan-with-snyk/snyk-projects/view-project-history.md).
  * **Settings**: displays [Project settings](/scan-fix-and-prevent/scan-with-snyk/snyk-projects/view-and-edit-project-settings.md).

## View Project summary

In the header of each Project overview, you can view information about:

* File and history details
  * Name and external link of the monitored repository
  * Name of the monitored branch
  * Direct link to the Project file in the SCM
  * The time when the Project was first imported to Snyk
  * The last time Snyk took a snapshot of the file that was fetched from the SCM and tested it
* Project import
  * **IMPORTED BY**: The user who imported the Project.
  * **PROJECT OWNER.** You can add an owner for this Project from a list of users who have access to the Project by clicking **Add a project owner**. You can also view this information through the endpoint [List all Projects for an Org with the given Org ID](/developer-tools/snyk-api/reference/projects.md#orgs-org_id-projects).
* Predefined [Project attributes](/scan-fix-and-prevent/scan-with-snyk/snyk-projects/project-attributes.md) and any additional [Project tag](/scan-fix-and-prevent/scan-with-snyk/snyk-projects/project-tags.md) metadata.


---

# 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://docs.snyk.io/scan-fix-and-prevent/scan-with-snyk/snyk-projects/project-information.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.