Preferences
Preferences controls how the platform speaks to you, how Narrova defaults behave, and how your account handles training-related consent. This is where you tune the platform to your workflow instead of forcing your workflow to match someone else's.
If you are new to Dramatica terms, Preferences is one of the fastest ways to make the platform feel more usable immediately. If you already know Dramatica well, you can keep things mostly untouched and work with the default language directly.
Personalize Your Experience
The Narrova Personas library saves named instructions for the voice and assumptions Narrova uses when it responds to you. In plain language, this tells the platform what kind of storyteller or professional you are so it can explain structure in the way that is most useful to you.
This matters because Dramatica can be extremely precise. Precision is useful, but not every writer wants every answer delivered in dense theory language. A Persona lets you keep the structural rigor while changing the explanatory surface.
To find Persona presets on the web, open Account → Preferences → Narrova Personas and choose New Persona. Enter a Persona name, write your instructions or choose Preset Personas as a starting point, and review the text. Choose Create Persona to save it. Selecting a preset fills the editor; it does not save the new Persona until you create it.
Confirm that the named Persona appears under Your Personas. Active identifies the account default; choose Activate for another saved Persona or Use no persona to deactivate that default. Edit → Save Persona saves revisions. A Story or conversation override can still take precedence over the active account default.
Persona Examples
Some Personas are intentionally broad. Others are designed to translate Dramatica for a very specific way of thinking.
Structure-Focused Writer
Use Structure-Focused Writer if you want the full structural benefit of Dramatica without wading through theory vocabulary in every answer. This Persona asks Narrova to connect Dramatica directly to character development, plot structure, thematic meaning, and conflict management while translating specialized terms into everyday writing language.
This is the best choice for many experienced writers who care deeply about structure but do not want to think in formal Dramatica terminology all day. It keeps the architecture while reducing the jargon barrier.
Writing use: Choose this Persona if you want answers like "this Throughline is the story's external conflict arena" instead of answers that assume you already speak fluent Dramatica.
Experienced Dramatica User
Use Experienced Dramatica User if you want the platform to speak with minimal translation. This is the most direct mode for writers, analysts, and teachers who already know the model and want speed over interpretation.
If you are comfortable with terms like Throughline, Signpost, Concern, and Problem without explanation, you may not need a Persona at all. Choose Use no persona and check for Story or conversation overrides when you want to use Narrova without a custom Persona.
New to Dramatica
Use New to Dramatica if you want the platform to teach the theory as it helps you write. This Persona keeps the canonical term, then bridges it into familiar story language so you can gradually build fluency.
This is useful when you want to learn the model rather than just use the output. It slows the conversation down in a good way.
Experienced Writer
Use Experienced Writer if you already understand craft and want Narrova to engage you at a higher level. This Persona assumes you can work with nuance, but still benefits from theory being connected directly to narrative construction instead of being left abstract.
This is a good fit if you want deeper structural commentary but still want the platform to remain practical.
Story Analyst
Use Story Analyst if you are examining scripts, films, novels, or drafts and want Dramatica translated into evaluative language. This Persona is useful when your goal is diagnosis: what is missing, what is misaligned, and what argument the story is currently making.
Creative Executive
Use Creative Executive if you are making development decisions rather than writing line by line. This Persona pushes Narrova toward practical answers about what is not landing in the story and what needs to change.
Common Mistakes
The most common mistake is choosing a Persona once and forgetting you can change it. If Narrova starts sounding too basic, too abstract, or too theory-heavy, return to Account → Preferences and switch Personas.
Another common mistake is stacking a Persona with highly conflicting custom instructions. If the results feel inconsistent, simplify your custom instructions so the Persona has a clear job to do.
Writing use: Match the Persona to the kind of work you are doing right now. Use Structure-Focused Writer while drafting, then switch to Story Analyst when diagnosing a revision problem.
Custom Personas and Persona Context
Custom Personas let you save your own instructions for Narrova's voice, priorities, and way of working. The Dramatica plan supports one custom Persona; Plus and Pro support multiple Personas.
Create and edit Personas in the Persona library, then decide which layer should supply the active instructions:
- Account default applies when no narrower choice exists.
- Story default applies to new inherited conversations inside that Story.
- Working Context Persona saves assistance guidance with that Working Context, which can optionally be related to a Project, without changing the account default.
- Conversation override chooses one Persona for the current thread.
- No persona deliberately ignores both Story and account defaults for that conversation.
In a web Narrova conversation, open Context → Persona, then choose Use defaults, a named Persona, or No persona. If you have permission, Story default also lets you choose the Story’s default or Use account default. Changes affect the next message and keep the existing conversation intact.
Reopen Persona to confirm the conversation's selected mode and name. If a Persona was edited after the conversation began, choose Apply updated [Persona name] when offered. Conversation Persona changes save separately from staged Story and Storyform choices, so cancelling that conversation dialog does not undo a Persona update already applied.
Open Project button → Working Context → Persona to inspect the approach used by that Context. The panel identifies Working Context Persona; a named selection or No persona is saved with that Working Context rather than activating an account default. An inherited selection can use the Story or account default. Complete the Working Context save flow and verify the selected sources. Use the Persona library when you intend to change the account default.
A Persona contributes to how you approach the work. It does not choose what Story or Storyform should receive accepted development, grant another writer access, or move a conversation. Two collaborators can approach the same work differently; an agent’s instructions should still name its task and permitted destination. See Working on and Working Context.
Native app arrangements and save controls can vary. Check which scope the app identifies before applying a Persona. See Context: Personas and What You Work On for the distinctions between a saved working selection, a conversation override, and account preferences.
Writing use: Give a Story its own Persona when tone and working method should remain consistent across several conversations, then use a conversation override for a temporary editorial or analytical pass.
AI Drafting
Open Preferences → AI Drafting to choose whether Narrova may write scenes, dialogue, and narrative prose when you ask, including in Story Guide and Voice. With it off, use assistance to develop ideas, outlines, objectives, and treatment blueprints, or to analyze writing you supply. With it on, ask for the prose you want and specify the form, length, point of view, and voice.
Wait for AI Drafting preference updated after changing the switch. If the preference could not be saved, retry before relying on it. Start a new Voice session after changing it. This preference is separate from AI access and enabling AI features; it does not generate writing or save suggestions automatically. Read Story Guide assistance for the relationship between conversation and manual workbook work.
Narrative Agent Preferences
Narrova Intelligence offers Efficient / Deep. Efficient uses a smaller model with careful reasoning for focused work and makes your allowance go further. Deep uses a larger model with careful reasoning for demanding story development and uses your allowance much faster. Both use the same Dramatica foundations and available Story Context.
Basic defaults to Efficient and can choose Deep. Plus and Pro default to Deep and can choose Efficient for lighter tasks. In One Narrova, choose the mode directly in Narrova → composer → Narrova Settings; confirm that the desired button is selected before sending the next request. The conversation keeps your choice, and an active turn keeps the mode it started with.
Individual Narrative Agent preferences remain available under Account → Preferences → Narrative Agent Preferences for workflows that use separate agents. Choose Efficient or Deep and a Response Length, then click Save Agent Preferences. When One Narrova is active, these individual preferences are preserved but do not control One Narrova's Intelligence mode.
Common Mistakes
If One Narrova does not pick up an individual agent preference, use its composer toggle. If a separate agent does not pick up a preference, confirm you clicked Save Agent Preferences. An explicit choice in an existing conversation can also differ from the default.
Writing use: Choose Efficient to clarify one Storypoint and Deep to examine how a revision affects several Throughlines. Confirm the selected mode in the composer before starting that work.
Narrova Experimental Features
The Narrova Experimental Features section controls early workflow systems that can appear in commands, composer controls, and Narrova orchestration.
In the platform, go to Account → Preferences → Narrova Experimental Features, then turn on the features you want to test.
| Feature | What becomes available |
|---|---|
| Narrova Goals | /goal, the Goal pill, and managed Goal Manager Steps |
| Narrova Advisors | Named independent perspectives and the Advisors panel |
| Side Chats | /side, Ask in side chat, active Side Chat controls, and /return |
| Story Development Ledger | The Develop button and Story Development's durable story-state surface |
- Location:
Account → Preferences → Narrova Experimental Features. - Action: Turn a feature on or off.
- Outcome: Its eligible controls and orchestration become available or hidden.
- Validation: Return to Narrova and confirm the corresponding command or control appears.
For full workflows, see Narrova Goals, Narrova Advisors, Side Chats, and Story Development.
Writing use: Enable only the workflows you intend to use, then keep accepted creative decisions in the durable Story or Storyform surface that owns them.
Training and Data Controls
The Training and Data Controls setting lets you decide whether new interactions may be used to improve system performance and response quality. In plain language, this is your consent setting for product improvement, not a transfer of story ownership.
This matters because the platform does not need training access to help you build or analyze stories. Dramatica works without it. Training is optional and off by default.
In the platform, go to Account → Preferences → Training and Data Controls. Turn the training switch on or off based on your comfort level.
- Location:
Account → Preferences → Training and Data Controls. - Action: Toggle the training setting.
- Outcome: Your choice applies to new interactions going forward.
- Validation: The toggle remains in the selected state after the preference updates.
Your Storytelling content, including the Storytelling field and submitted Illustrations, is not used to train or improve our systems unless you explicitly enable this setting.
Support and Reliability Access
Operational access is separate from training. Authorized staff may access limited portions of logs, traces, or content when needed for support, debugging, abuse prevention, security, or legal compliance.
This does not mean your content is being used for model training. It means the platform can still be operated and supported responsibly.
Common Mistakes
The most common mistake is assuming "not used for training" means "never accessible under any circumstances." That is not what this setting does. Support and reliability access may still occur when necessary to operate the service.
Another mistake is assuming training consent changes how Narrova reasons about your current story. It does not. The feature controls future improvement use, not whether Narrova can help you right now.
Writing use: If you are working on confidential client or studio material, review this setting before you begin serious drafting or analysis sessions.
Narrative Framing Lens
The Narrative Framing Lens controls how Storyform language appears across cards, prompts, and guidance. In plain language, it changes how the platform names things, not what the Storyform actually is.
This matters because the same structural relationship can be described in more than one useful way. Some writers think more clearly in classic Dramatica terms. Others think more clearly in character-oriented or plot-oriented language. The Framing Lens helps the interface meet you where you think.
In the platform, go to Account → Preferences → Narrative Framing Lens and choose the framing mode you want to use by default.
- Location:
Account → Preferences → Narrative Framing Lens. - Action: Select
Auto,Plot-focused / Linear, orHolistic / Character-focused. - Outcome: Labels and guidance across the platform adopt that framing.
- Validation: Storyform cards and prompts show the updated wording while your underlying Storyform data remains unchanged.
Current Options
| Setting | What it does |
|---|---|
Auto |
Uses the story's Main Character Problem-solving Style to choose the most fitting default language. Linear stories lean Plot-focused. Holistic stories lean Character-focused. |
Plot-focused / Linear |
Forces Plot-focused terminology regardless of story style. Useful when you want traditional Dramatica-flavored phrasing or a single shared vocabulary across a team. |
Holistic / Character-focused |
Forces Character-focused terminology regardless of story style. Useful when relational and experiential wording helps you think more clearly about conflict. |
What Changes On Screen
You will see labels update in cards, prompts, and other guidance surfaces. For example, Throughline Problem/Solution/Symptom/Response labels can be shown with more character-oriented translations such as:
DissonanceReliefFrictionAccommodation
You will also see more explicit label prefixes in places where clarity matters, such as MC Resolve, MC Growth, Story Driver, and Story Outcome.
Common Mistakes
Do not use the Framing Lens as a substitute for changing the Storyform itself. If the story's structure is wrong, a different label set will not fix it.
Do not assume one framing is objectively better. The best setting is the one that helps you see the story's conflict clearly enough to make stronger writing decisions.
Writing use: If Dramatica terms feel dense, pair Structure-Focused Writer with Holistic / Character-focused or Auto framing to keep the structural power while reducing terminology friction.
For the full terminology mapping and rationale, see Framing Terminology: Plot-focused and Character-focused.
Show context usage
In Preferences → Narrova Context, turn on Show context usage to display the context meter in the composer and at the top of Narrova Settings. It is off by default for everyone. When off, the composer shows the Narrova settings icon for Intelligence and response length. Narrova continues managing conversation context automatically.