# How to Configure Workflow Details: Naming, Descriptions, and Tags

### Summary

Properly configuring your workflow's details, its name, description, and tags, is the first and most crucial step in Studio. This metadata ensures your team can easily find, understand, and trust the **custom legal workflows** you create.

### Why This is Important

The "Workflow Details" screen is the first impression your automation will make on your colleagues. While the underlying logic is powerful, a clear name and a compelling description are what drive adoption. Taking the time to get these details right turns a great tool into a *usable* tool and is a critical part of effective **legal process automation**.

{% hint style="info" %}
**The 'New Colleague' Search Test:** Before you save, ask yourself: "If a new associate who knows nothing about this project needed to find this tool, what words would they type into a search bar?" Make sure those exact words appear in your workflow's **Name**, its **Description**, and its **Tags** to ensure it is easily discoverable.
{% endhint %}

### Configuring Each Field for Maximum Clarity

After clicking **+ New Workflow**, you will land on the **Workflow Details** page. Here is how to approach each field.

#### 1. Name

This is the official title of your workflow that will appear in your firm's library.

* **Best Practice:** Use a clear, action-oriented name that describes the outcome. Start with a verb.
* **Example:** Instead of "NDA Tool," use a name like `Analyze Incoming NDA for Red Flags`.

#### 2. Icon

This provides a quick visual reference for your workflow in the list.

* **Best Practice:** Choose an icon that visually represents the primary action of the workflow.
* **Example:** For a workflow that analyzes documents, a **magnifying glass** icon is a perfect choice. For one that checks compliance, a **shield** icon works well.

<figure><img src="https://1556743161-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MS8Dq_iqEIflAmbaOkI-887967055%2Fuploads%2FTqmErXYtndqUuzBHnjQV%2Fimage%20(2).png?alt=media&#x26;token=277160e2-d15f-497b-a383-d26b0cb491d5" alt=""><figcaption><p>Choose an icon that makes your workflow instantly recognizable</p></figcaption></figure>

#### 3. Description

This is the most important field for your end-users. It is the short summary that appears under the name and tells them exactly what problem your workflow solves.

* **Best Practice:** Write a single, concise sentence from the user's perspective. Clearly state the purpose and benefit.
* **Example:** `Use this workflow to perform a rapid 'red flag' analysis of Non-Disclosure Agreements based on our firm's official standards.`

{% tabs %}
{% tab title=" English Interface " %}

<figure><img src="https://1556743161-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MS8Dq_iqEIflAmbaOkI-887967055%2Fuploads%2FwWGjkyIq2zPH8tj666gf%2Fimage%20(3).png?alt=media&#x26;token=979a7a1f-c69c-4377-8a9b-6568725b9372" alt=""><figcaption><p>Add a concise description that tells users exactly what the workflow does and the problem it solves.</p></figcaption></figure>
{% endtab %}

{% tab title="Interfaz en Español" %}

<figure><img src="https://1556743161-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MS8Dq_iqEIflAmbaOkI-887967055%2Fuploads%2FMbJBwF9nDOxNZFy63zOS%2FCaptura%20de%20pantalla%202026-01-29%20a%20las%2017.44.54.png?alt=media&#x26;token=d61c8915-1da8-4b8b-bd7f-5e109497483e" alt=""><figcaption><p>Introduce una descripción breve que explique a los usuarios la función del workflow y el problema que soluciona.</p></figcaption></figure>
{% endtab %}
{% endtabs %}

#### 4. Tags

Tags are keywords that make your workflow searchable and allow your team to filter the library to find the right tool for the job.

* **Best Practice:** Use the consistent, pre-defined list of tags established by your organization. This ensures proper categorization.

Below are the definitions for your firm's official tags. Choose the one(s) that best describe your workflow's purpose.

* **Document Analysis**
  * Select this tag for any workflow whose primary function is to **review, summarize, extract information from, or compare** existing documents. This is for workflows that *process* information you already have.
  * *Examples: Contract review, deposition summary, fact extraction from a complaint.*
* **Drafting**
  * Choose this tag when the workflow's main purpose is to **generate new written content**. This could be a complete document, a specific clause, or even a formatted email.
  * *Examples: Drafting a motion, generating standard contract clauses, creating a client update email.*
* **Litigation**
  * Apply this tag to workflows designed for tasks related to **disputes and court proceedings**. This includes all phases, from pre-trial discovery to motion practice and trial preparation.
  * *Examples: Analyzing a complaint, summarizing a deposition, drafting a request for production.*
* **Research**
  * Select this tag for workflows that **find, analyze, or synthesize legal authorities** like case law, statutes, or regulations. This is distinct from document analysis, which focuses on documents you upload.
  * *Examples: Building a legal argument, finding supporting case law, comparing statutes across jurisdictions.*
* **Transactional**

  * Use this tag for workflows related to **agreements, deals, and corporate matters**. This covers the non-contentious side of legal practice.
  * *Examples: Reviewing an NDA, drafting a purchase agreement, performing due diligence analysis.*

{% tabs %}
{% tab title=" English Interface " %}

<figure><img src="https://1556743161-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MS8Dq_iqEIflAmbaOkI-887967055%2Fuploads%2FElD39bZ68gWgfYHJBcPK%2FAdd%20tags%20to%20make%20your%20workflow%20easy%20to%20find.%20Use%20your%20firm%E2%80%99s%20official%20tag%20list%20for%20consistency%20and%20proper%20categorization..gif?alt=media&#x26;token=9e478652-5002-4121-a613-2372126c2757" alt=""><figcaption><p>Add tags to make your workflow easy to find. Use your firm’s official tag list for consistency and proper categorization.</p></figcaption></figure>
{% endtab %}

{% tab title="Interfaz en Español" %}

<figure><img src="https://1556743161-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MS8Dq_iqEIflAmbaOkI-887967055%2Fuploads%2FIRba6O0sM7egq1QnvUlp%2FAgrega%20etiquetas%20para%20que%20tu%20flujo%20de%20trabajo%20sea%20fa%CC%81cil%20de%20encontrar.%20Usa%20la%20lista%20oficial%20de%20etiquetas%20de%20tu%20firma%20para%20coherencia%20y%20una%20correcta%20categorizacio%CC%81n..gif?alt=media&#x26;token=655c98f1-01a3-42e2-9110-1fbc9d19851e" alt=""><figcaption><p>Agrega etiquetas para que tu flujo de trabajo sea fácil de encontrar. Usa la lista oficial de etiquetas de tu firma para coherencia y una correcta categorización.</p></figcaption></figure>
{% endtab %}
{% endtabs %}

### Best Practices & Pro Tips

* **Think Like Your User:** Write the name and description for a junior associate who has never seen this workflow before. Is it immediately obvious what it does and when they should use it? If not, simplify it.
* **Establish a Naming Convention:** For firm-wide consistency, agree on a standard naming pattern. For example, always start with a verb and follow with the subject: `Analyze [Document Type]`, `Draft [Agreement Type]`, `Review [Clause Type]`.

### Related Articles

* [Accessing Vincent Studio and Navigating the Main Interface](https://support.vlex.com/vincent-by-vlex-1/vincent-studio/getting-started-with-vincent-studio-workflows/accessing-vincent-studio-and-navigating-the-main-interface)
* [Driving Adoption: How to Get Your Team to Use Vincent Studio Workflows](https://support.vlex.com/vincent-by-vlex-1/vincent-studio/creating-and-managing-ai-workflows-in-vincent-studio/driving-adoption-how-to-get-your-team-to-use-vincent-studio-workflows)

### Unlock the Power of Legal Automation

Ready to see how Vincent Studio can transform your firm's efficiency?

[**Contact our sales team for a personalized demo today.**](https://vlex.com/book-a-demo?utm_source=website\&utm_medium=organic\&utm_campaign=web_trial_homepage\&campaign_id=4270741)

**What's Your Next Step?**

| **New to Vincent Studio?**                                                                                                                                                                                 | **Already a Vincent Studio Customer?**                                                                                                                     |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [See how Vincent can transform your practice. **Request a personalized demo**.](https://vlex.com/book-a-demo?utm_source=website\&utm_medium=organic\&utm_campaign=web_trial_homepage\&campaign_id=4270741) | [If you still have questions or need help with a specific feature, our team is here to assist. **Contact our Support team**.](https://vlex.com/contact-us) |


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://support.vlex.com/vincent-by-vlex-1/vincent-studio/creating-and-managing-ai-workflows-in-vincent-studio/how-to-configure-workflow-details-naming-descriptions-and-tags.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.