> For the complete documentation index, see [llms.txt](https://docs.devally.com/EfyQpV4281edZ3h0g8tY/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devally.com/EfyQpV4281edZ3h0g8tY/core-concepts/markdown.md).
# Products
A product is one site or app you audit in DevAlly. Each product lives inside one workspace and owns its own audits, issues, workflows, and variables.
There are two types: **Website** and **Web app**. You pick the type when you create the product, and the choice is permanent. DevAlly tailors the rest of the product around it.
***
#### Choosing a product type
| | **Website** | **Web app** |
| -------------------------------- | -------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------- |
| Best for | Public sites you can crawl, such as marketing sites, blogs, docs, and e-commerce | Apps behind a sign-in or single-page apps where audits need to follow user journeys |
| Site audits (multi-URL crawl) | ✓ | |
| Auto-scan to discover URLs | ✓ | |
| Manage a list of additional URLs | ✓ | |
| Workflows (Wendy or builder) | ✓ | ✓ |
| Workflow audits | ✓ | ✓ |
| Issues, ACRs, variables | ✓ | ✓ |
Choose **Website** if you want to scan many URLs across a public site. Choose **Web app** if your audits need to sign in, navigate through screens, or follow specific journeys. Record those flows with [Wendy](/EfyQpV4281edZ3h0g8tY/core-concepts/workflows-and-automations/recording-with-wendy.md).
{% hint style="warning" %}
**Product type is permanent.** To switch types, create a new product and re-create its workflows.
{% endhint %}
***
#### Creating a product
{% stepper %}
{% step %}
Open **Products** in the sidebar of the workspace you want to add to, then select **Create product**.
{% endstep %}
{% step %}
Pick a type:
* **Audit your website**: find accessibility issues across your whole site.
* **Audit your web app**: record flows to test specific journeys in your product.
DevAlly tailors the next form to your choice.
{% endstep %}
{% step %}
Fill in the form:
* **Product Name**: a unique name for this product, e.g. `Marketing Website` or `Admin Dashboard`.
* **Product URL**: the URL of your product.
* **Website**: must be a root URL with no path segments, e.g. `https://example.com`.
* **Web app**: can be a root URL or include path segments, e.g. `https://app.example.com/login`.
For a website only:
* **Add Additional URLs** (optional): add more URLs manually, or use **Auto Scan (Beta)** to discover them automatically. Auto Scan can take up to 3 minutes. You can add or modify URLs later in product settings.
{% hint style="info" %}
**Auto Scan is in Beta.** It tries to find your other URLs automatically by crawling your site. It may not catch every page. You can always add or remove URLs later.
{% endhint %}
{% endstep %}
{% step %}
Select **Create Product**. DevAlly takes you back to the products list.
{% endstep %}
{% endstepper %}
***
#### What you can do with a product
For each product, you can:
* Run audits: [site audits](/EfyQpV4281edZ3h0g8tY/core-concepts/images-and-media/site-audits.md) (Website products) and [workflow audits](/EfyQpV4281edZ3h0g8tY/core-concepts/images-and-media/workflow-audits.md) (both types).
* Track and remediate [issues](/EfyQpV4281edZ3h0g8tY/core-concepts/interactive-blocks.md).
* Generate an [Accessibility Conformance Report (ACR)](/EfyQpV4281edZ3h0g8tY/core-concepts/accessibility-conformance-reports.md).
* Create and manage [workflows and automations](/EfyQpV4281edZ3h0g8tY/core-concepts/workflows-and-automations.md).
* Store product-specific variables (like sign-in credentials) for use in workflows.
---
# 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.devally.com/EfyQpV4281edZ3h0g8tY/core-concepts/markdown.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.
