> For the complete documentation index, see [llms.txt](https://docs.linuxfoundation.org/lfx/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.linuxfoundation.org/lfx/organization-dashboard/organization-dashboard-v1/projects.md).

# Projects (Deprecated)

Projects tab provides you with summary of information related to a specific foundation or project. The project tab provides you various graphs, charts, and widgets related to the project. You can search for an open source project or foundation to view the following details:

* Membership details
* Benefits
* Project contributions
* Project contributors
* Committees
* Meetings
* Resources

## Search a Project

To search a project and to view details related to the project, perform the following:

1.Login to [Organization Dashboard](https://myorg.lfx.dev).

2.On the vertical sidebar navigation menu, click **Projects** and in the **Search** box enter project name. The project name appears below the Project. Click **Project Overview** to see the project details.

![Project Overview](https://files.gitbook.com/v0/b/gitbook-28427.appspot.com/o/assets%2F-MgAESFs0H7zYsmTgcOZ%2F-Mi27xdOeFevUxulrZvP%2F-Mi2AheNqZKqwbUgWqeK%2FProject_Overview.png?alt=media\&token=bef5a69e-ab5b-4f81-93ab-0dccc4579149)


---

# 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.linuxfoundation.org/lfx/organization-dashboard/organization-dashboard-v1/projects.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.