> For the complete documentation index, see [llms.txt](https://support.vlex.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.vlex.com/vincent-by-vlex/vincent/skills/setting-organization-wide-instructions.md).

# Setting Organization-Wide Instructions

#### Summary

Organization Instructions are always-on context that Vincent follows in every conversation across your firm. Publishers use this field to set house style, jurisdiction defaults, and any standing brief that should apply to every user, every time.

#### Why This is Important

Consistency is one of the hardest things to enforce across a legal team. Everyone has their own way of citing authorities, structuring memos, or referring to the firm's clients, and without a shared baseline, Vincent's output will vary from lawyer to lawyer in ways that make the firm's work look uneven.

Organization Instructions solve this by giving Vincent a single, authoritative brief that applies before any Skill is triggered and before any individual user's preferences kick in. When you set them well, every associate, paralegal, and partner starts from the same baseline, the firm's citation style, jurisdiction defaults, tone, and any non-negotiable guardrails.

#### Who Can Edit Organization Instructions

Only **Publishers** can view or edit the Organization Instructions field. Builders and Users will see the field labeled **Admins only** and cannot modify it. If you need to update firm-wide context but don't have Publisher access, contact your firm's Publisher or see Skills Roles and Permissions.

<figure><img src="/files/QbZMvXPVhRV7ZnuwW1Xc" alt=""><figcaption><p>Access restricted: Only Publishers can modify firm-wide Organization Instructions.</p></figcaption></figure>

#### Step-by-Step Guide

**Step 1: Open the General Tab**

1. On the Vincent home page, click **Customize** in the top right.
2. Make sure you are on the **General** tab (this is the default view).

You'll see two instruction fields: **Vincent Instructions** (your personal instructions, editable by anyone) and **Organization Instructions** (Publisher-only).

**Step 2: Write Your Organization Instructions**

Click into the **Organization Instructions** field and type the guidance you want Vincent to follow across every conversation firm-wide. Write in plain language, you don't need any special syntax.

Below the field, you'll see the confirmation **Applied to all users in this organization**, which tells you the instructions are live once saved.

**Step 3: Save**

Save your changes. The instructions take effect immediately for every user in your organization on their next conversation.

<figure><img src="/files/eTY2fQwYROUpBP2zXygz" alt=""><figcaption><p>Set your firm's rules once. Vincent follows them in every conversation.</p></figcaption></figure>

#### What to Put in Organization Instructions

Organization Instructions work best when they capture things that should apply **universally,** not task-specific guidance (that belongs in a Skill) and not individual preferences (that belongs in Personal Instructions).

Good candidates include:

* **Firm identity and tone:** "We are a mid-sized commercial litigation firm based in New York. Write in a professional, direct tone without hedging language."
* **Default jurisdiction and choice-of-law rules:** "Unless a specific jurisdiction is stated, assume New York state law. For federal questions, default to the Second Circuit."
* **Citation style**: "Use Bluebook citation format for all authorities. When citing a case for the first time, include the full citation and pinpoint page."
* **House style and formatting:** "Use serial commas. Spell out numbers under 10. Do not use contractions in formal documents."
* **Client-handling guardrails:** "Do not reference client names in general research responses. Always include a confidentiality reminder in email drafts."
* **Language and terminology:** "Refer to our firm as 'the Firm.' Refer to opposing counsel as 'Opposing Counsel,' never by name in draft documents."

{% hint style="info" %}
**Start narrow and expand over time.** A short, precise Organization Instructions field is more effective than a long one. Vincent gives more weight to concise, clear directives. Begin with three or four rules that matter most (jurisdiction, tone, citation style) and add more only when you see specific patterns in your firm's output that need correction.
{% endhint %}

#### What Not to Put in Organization Instructions

Some things look like they belong here but actually don't:

* **Task-specific instructions:** how to structure a demand letter, what to check in a contract review. These belong in a **Skill** so they only activate when relevant.
* **One person's preferences:** a partner's preferred email signature, an associate's chosen legal pad style. These belong in **Personal Instructions** for that user.
* **Long reference material:** full playbooks, complete style guides, or lengthy templates. Keep Organization Instructions focused. Attach detailed material as an asset inside a Skill instead.

#### How Organization Instructions Interact with Other Layers

Vincent reads three layers of context in every conversation, in this order:

1. **Organization Instructions** (Publisher-set, applies to everyone)
2. **Personal Instructions** (each user's own standing brief)
3. **Skills** (task-specific instructions that activate on relevant prompts)

{% hint style="warning" %}
**Personal Instructions take precedence over Organization Instructions when they conflict.** If a Publisher writes "Use Bluebook citations" but an individual user writes "Use OSCOLA citations" in their Personal Instructions, that user's conversations will follow OSCOLA. Design Organization Instructions to be the default, not a mandate.
{% endhint %}

#### Best Practices & Pro Tips

* **Review Organization Instructions quarterly.** Firm priorities change — a new practice area opens, a jurisdiction expands, a house style guide is revised. Put a recurring reminder in the Publisher's calendar to audit these instructions so they reflect the firm as it is today, not as it was a year ago.

#### Related Articles

* [Skills Roles and Permissions](/vincent-by-vlex/vincent/skills/skills-roles-and-permissions.md)
* [Setting Up Your Personal Vincent Preferences](/vincent-by-vlex/vincent/skills/setting-up-your-personal-vincent-preferences.md)
* [Reviewing and Publishing Skills for Your Organization](/vincent-by-vlex/vincent/skills/reviewing-and-publishing-skills-for-your-organization.md)
* [What are Skills in Vincent?](/vincent-by-vlex/vincent/skills/what-are-skills-in-vincent.md)

**What's Your Next Step?**

| **New to Vincent?**                                                                                                                                                                                        | **Already a Vincent 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) |