> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dekasign.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Categories and Request Forms

> Categories, form versions, workflow releases, and requester cards.

## Create a category

An Owner/Admin opens **Request Forms** and selects **Add category**. Enter a clear name and description. A new category does not automatically create a form, workflow, or approval permission for every member.

Set who can submit, use templates, and approve the category. Approver candidates must be active and authorized for the category; appearing in the member list does not necessarily make someone eligible.

## Connect the designs

Create/save a Form Builder template, then select that category and template in the workflow canvas. Configure, Validate, test in Sandbox, and Publish. A Request Form card comes from a published workflow, not an empty category alone.

## Versions

The same category/form-template combination uses the new published release for new submissions. Different category/template combinations can produce separate cards/forms. Cards show the active form and workflow versions.

Running requests retain their accepted release snapshot. Do not use label changes to reinterpret historical data; field keys and versions are part of the submission contract.

## Archive

Do not archive workflows/categories still used by active requests. Relevant API and UI controls reject these conflicts. Archiving does not delete decisions or document evidence.

## Missing a card?

Check published status, the active category, form scope, and Request Create permissions. Requester role alone does not make every category visible. Ask a manager to correct configuration; do not submit through another tenant.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.