> For the complete documentation index, see [llms.txt](https://docs.violetlabs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.violetlabs.com/apps/j/jama.md). # Jama Jama is a solution for managing product requirements from idea through development, launch, and iteration. Learn more at www\.jamasoftware.com. ### Connect Jama in Violet {% hint style="info" %} The below instructions are for connecting cloud-based Jama. If your instance is self-hosted, skip this section and head [here](/apps/j/jama/connect-self-hosted-jama.md). {% endhint %} 1. In [Violet](https://app.violetlabs.com/) (or [VioletGov](https://app.violetgov.com/)), navigate to **Integrations** and click . 2. Select **Jama** \[Optional] Assign permissions to which users or user groups can view the data or edit the credentials:
3. Provide the URL for your Jama instance: 4. For Basic Authentication, enter your Jama Username and Password and click **Connect.** \ (Or head [here](/apps/j/jama/optional-connect-with-jama-client-id-and-secret.md) if you prefer to to connect with a Jama Client ID & Secret). 5. Once connected, configure your integration (optional), then click **Create.** You're done! 1. Select one or more Jama Projects to include in the integration scope. We recommend limiting one Jama Project to one Integration, so that imported projects will be rendered as Violet Programs, and contained requirements can be viewed in Violet Requirements Module (enabling commenting, peer reviews, shared program access, etc.) --- # 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.violetlabs.com/apps/j/jama.md?ask=&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.