Skip to content
Personalising · 5 min read

Personalising LumaVista

Pick a persona and get a working setup in one step — skills, defaults and navigation arranged for how you actually work.

A capable tool with everything switched on is not a gift. It is a configuration exercise handed to someone who wanted to get something done.

Personas are the shortcut: pick how you intend to work, and LumaVista arranges itself accordingly — the relevant skills installed, sensible defaults set, the navigation ordered so what you use is at the top.

What a persona sets

Applying one is a single action that touches four things:

  • A skill pack — the skills that fit this way of working, installed together rather than found one at a time.
  • A research default — how thorough new projects are unless you say otherwise.
  • Menu order — which surfaces sit at the top of your sidebar.
  • Settings — the preferences that go with the shape.

None of it is locked. A persona is a starting position, not a mode; every piece it sets can be changed afterwards, and your own choices win.

The personas

General

The balanced default. No extra skills, standard research defaults, standard navigation. Start here if you are not sure — nothing about it forecloses anything, and switching later costs you nothing you have not explicitly changed.

Note Taker

For working out loud. Capture by voice, act automatically.

It installs the action-item extraction pack, front-loads recordings and notes in the navigation so capture is one click rather than three, and raises the research default. It pairs with the Voice Note → Action Items workflow template: instantiate that, opt the workflow in, opt your recordings in, and spoken commitments file themselves. See Voice to Action.

Note that the persona sets up the machinery but does not consent on your behalf. The two opt-ins that let a recording drive a workflow remain yours to give, per workflow and per recording. A persona arranges the tools; it does not switch on automation you did not ask for.

More over time

The list is short deliberately. A persona is a file — adding one is config, not code, so the catalog grows as real working patterns show up rather than as speculative ones get invented.

Rearranging the navigation

Independently of personas, your primary navigation is yours to order. Put what you use daily at the top and let the rest sit below.

This is per-user, and it survives a persona change: if you have arranged your own menu, applying a persona will not silently undo it.

Changing your mind

Switch personas whenever. Applying a new one sets its defaults; anything you have explicitly customised stays customised. There is no “reset to factory” cliff, because a persona was never a mode you were in — just a set of sensible values applied at a moment you chose.

Availability. Personas are in beta and off by default. If you do not see persona selection or a reorderable menu, it is not enabled for your account — ask and we will turn it on.

Choosing your language

Language is two settings, not one, and they are deliberately independent. Both live in Settings → Personalization, next to the region and number-format controls.

  • Interface language is the chrome: menus, buttons, labels, settings pages. English, Français, Deutsch and Español are available, plus Automatic, which follows the region you have selected.
  • Report language is the default output language for generated research and reports — what the writing itself comes out in. Same choices, same Automatic behaviour.

Splitting them is the point. A German speaker researching an English-language market can run the interface in Deutsch and still get reports in English; someone working for an international team can do the exact opposite. Neither choice pulls the other along.

Two consequences worth knowing:

Report language is a default, not a lock. The generate-report dialog pre-selects it and you can change it for that one report, so a single piece of work in another language does not mean changing a setting and remembering to change it back.

Conversations are not steered by it. Report language governs generated research and reports. Chat and voice answer in the language you are writing or speaking in, so setting reports to German does not start answering your English questions in German.

These help pages are English only

The interface is translated. This documentation is not — every page here is written in English, whatever your interface language is set to. That is a real limitation rather than an oversight, and it is worth knowing before you go looking for a language switch on this page.