> 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/features/requirements/verifications.md). # Verifications Violet supports use of Verification entities, as well as direct linking of requirements to associated Violet entities (tests, analyses, etc.). ### Using Violet Verifications Violet Verifications are separate entities from requirements, which can be linked to one or many Violet Requirements and have their own attributes and status. Show or hide verifications using the column selector.

#### Custom Violet Verifications Attributes Add custom attributes to Verifications in [Custom fields](/features/requirements/custom-fields.md). By default, each Verification has Name, Assignees, Status, and Evidence attributes. #### Creating Verifications From the requirements table view with Verification columns shown, double click in a requirement's row under the Verification heading to create a new verification against the requirement. Enter data in the side panel and click OK. Use the Requirements drop down to select one or more requirements that will be addressed by this Verification. #### Adding Evidence Each Verification can have an Evidence item added, with its own description, status, URL or link to another Violet entity. Add one or many attachments as necessary to support requirement closure.

### Linking Requirements Directly to Other Verifying Entities If you'd rather directly link a Violet Requirement directly to the test run, ticket, or other entity representing the verification work, follow the approach below. #### Attach a Verification Attach a Verification to a Violet Requirement via the **Verified by** relationship. In the Requirement edit pane, use the keyword search to find and attach the appropriate verification entity (test, analysis, etc.):

#### Verifiers Once linked, users assigned to the Verification will auto-populate the **Verifiers** field. #### Automatic Verification Status Tracking As the verification is updated (eg. from draft, to in progress, to done), the **Verification Status** field will auto-update.

--- # 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/features/requirements/verifications.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.