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

# Editorial Guide: Define Wolfia's Voice for Your Org

> The Editorial Guide controls Wolfia AI's tone, voice, formatting, and terminology across every questionnaire and conversation, brand consistency on autopilot.

## What the Editorial Guide controls

* **Tone and voice**: Professional vs casual, first-person vs third-person
* **Formatting preferences**: Bullet points vs paragraphs, headers, response length
* **Terminology standards**: Company name usage, abbreviation preferences
* **Brand consistency**: Ensuring all AI answers sound like they come from your organization

## What it doesn't control

The Editorial Guide only affects *how* answers are written. It won't change:

* Which facts are included in answers
* The compliance framework focus (use [Questionnaire Instructions](/how-to/questionnaire-instructions) for that)
* The technical depth of responses (use [Questionnaire Instructions](/how-to/questionnaire-instructions) for that)

## Setting up your Editorial Guide

<Steps>
  <Step title="Navigate to settings">
    Go to **Settings → AI customization**
  </Step>

  <Step title="Select the Editorial guide tab">
    Select the **Editorial guide** tab and enter your style preferences
  </Step>

  <Step title="Save your guide">
    Click **Save guide**
  </Step>
</Steps>

Your guide applies to all AI-generated answers across questionnaires and conversations.

## Examples

### Tech startup wanting approachable answers

**Editorial Guide:**

> Be conversational and direct. Use "we" and "you." Avoid jargon. Keep answers under 150 words when possible.

**Before (default AI answer):**

> Access controls are implemented using role-based access control (RBAC) with multi-factor authentication required for all users.

**After (with Editorial Guide):**

> We use role-based access so you only see what you need. Everyone on the team logs in with multi-factor authentication.

***

### Enterprise with strict brand guidelines

**Editorial Guide:**

> Always use "Acme Corporation" instead of "we" or "the company." Use formal, third-person voice. Lead with customer benefits.

**Before (default AI answer):**

> We conduct quarterly security assessments and penetration testing.

**After (with Editorial Guide):**

> To protect customer data, Acme Corporation conducts quarterly security assessments and annual penetration testing.

***

### Fast-growing startup wanting technical credibility

**Editorial Guide:**

> Use precise technical language. Include specific product names and standards. Write for a technical audience.

**Before (default AI answer):**

> Data is encrypted both at rest and in transit using industry-standard encryption.

**After (with Editorial Guide):**

> All data is encrypted at rest using AES-256-GCM via AWS KMS. Data in transit uses TLS 1.3 with ECDHE key exchange.

## Best practices

* **Start simple**: Begin with 2-3 core preferences and refine over time
* **Be specific**: "Use formal tone" is vague; "Use third-person voice and avoid contractions" is actionable
* **Test with examples**: Upload a questionnaire and review how answers change

## Common questions

<AccordionGroup>
  <Accordion title="Does this change what facts are included?">
    No. The Editorial Guide only affects writing style, not content.
  </Accordion>

  <Accordion title="Does this apply to all questionnaires?">
    Yes. The Editorial Guide applies organization-wide.
  </Accordion>

  <Accordion title="Who can edit the Editorial Guide?">
    Only Admins and Experts can edit. Other users can view it.
  </Accordion>
</AccordionGroup>