> ## Documentation Index
> Fetch the complete documentation index at: https://docs.duvo.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Clarity
> Capture, organize, and improve process documentation with Clarity.
## Introduction
Clarity is Duvo's process documentation and analysis system. It helps you capture how work actually gets done — through video recordings, AI voice interviews, documents, and images — then uses AI to turn those captures into structured documentation with cost-benefit insights.
Whether you're onboarding new team members, evaluating automation opportunities, or standardizing operations, Clarity gives you a clear picture of your processes.
Clarity is built into Duvo — there's no separate setup. Open the Clarity section in the sidebar and create your first process to get started.
## Roles and process ownership
Builders, Managers, Administrators, and Owners can create Clarity processes. Builders can rename and edit the guidance and generated content of any process they can access in their team, including processes created by someone else.
A Builder can delete only a process they created. Managers and above can delete any team process and manage team-wide settings and process structure. Generation, sharing, visibility, and access remain with the process creator or a Manager. Clarity Members contribute browser interviews but cannot edit generated process content.
## Key Capabilities
* **Capture processes** via screen recordings, browser voice Agent interviews, uploaded documents, and process images
* **AI-powered video analysis** that extracts steps, systems used, and decision points
* **Automated documentation generation** with cost-benefit analysis
* **Industry-specific benchmarks** for retail, grocery, and CPG workflows
* **Sharing and collaboration** through public links or shareable invite links for people outside your team
## Quick Start: Map a Process in 7 Steps
Open the **Clarity** section in the sidebar and click **New Process**. Enter your role, department, and company website. Duvo saves public company context in the background, then asks which goal should steer your first map.
Select a catalogue process and click **Continue**, or name a process yourself. Clarity then shows a sample map so you can see what the interview will produce. The sample is not a map of your company.
Start with the voice interview. Describe a recent run, the systems and handoffs involved, and what happens when the process goes off track. The interview workspace shows each process step with the people and tools involved.
When you finish, review the people involved and add email invitations for anyone who should share another perspective. Continue to start the map, then open Process Landscape while Duvo generates it. If you want to enter Clarity without adding a capture, select **Skip mapping for now** on the capture step.
Clarity builds a rough current-state map from the conversation. Longer generations continue in the Process Landscape, and Duvo emails you when the map is ready.
Return to the Process Landscape or follow the email link to open the generated map. Map more yourself, or invite the people who run the process.
## Capture a Process
Clarity supports four capture methods. Pick the one that fits how the knowledge lives today — or combine several on the same process.
A voice interview is a conversation with an AI agent that asks you questions about a process and records your answers automatically. This is the fastest way to capture process knowledge — no typing required.
Open the process you want to document.
Click **Add Content** and select **Interview**.
Your browser will ask for microphone access. Click **Allow**.
Select your preferred interview language — English (United Kingdom), English (United States), Czech, French, German (Germany), German (Switzerland), Hungarian, Polish, Portuguese (Brazil), Portuguese (Portugal), Slovak, Slovenian, Spanish (Mexico), Spanish (Spain), Thai, or Ukrainian. Your team's default Clarity language is preselected; change it here if this interview needs a different one.
Click **Start** to begin the interview. The AI agent will introduce itself and start asking questions about the process.
Answer naturally. Duvo asks follow-up questions to capture details, decision points, and exceptions. It also asks once how often the process happens and its approximate end-to-end duration.
If the agent feels too slow or too fast, click the **Voice speed** button in the interview controls and drag the slider — Slower, Normal, Faster, or Fast. The new pace takes effect as soon as you close the menu, without interrupting the interview. (Shown only when the interview voice supports speed adjustment.)
If you need to pause (e.g., someone walks in), click the **Mute** button. Click **Unmute** when you are ready to continue — the interview picks up where you left off.
When you have covered everything, click **End Interview**. A dialog appears with three options:
* **Continue interview** — return to the interview if you have more to share.
* **End interview** — save the session and complete the interview.
* **Discard** — permanently delete the recording and transcript. This cannot be undone.
Click **End interview** to save. The interview appears as a capture in the process once it is saved.
The AI agent may also end the interview proactively when it has gathered enough information. When this happens, the same dialog appears — choose **Continue interview** if you have more to add, or confirm by clicking **End interview**.
Tips for a good interview:
* Find a quiet space — background noise can affect the AI agent's ability to hear you.
* Describe the process as if you are explaining it to a new colleague.
* Mention specific tools, systems, and people involved at each step.
* If you make a mistake, just correct yourself — the AI will use the most recent version.
Upload a screen recording or video walkthrough of someone performing the process. Clarity uses AI to analyze the video and extract individual steps, tools used, and decision points.
Open the process you want to document.
Click **Add Content** and select **Upload Video**.
Select or drag-and-drop your video file.
Wait for the upload and analysis to complete. Clarity processes the video automatically — this may take a few minutes depending on the video length.
Once analysis is done, the capture appears in the process with a summary of the extracted content.
**Supported formats:** MP4, MOV, WebM, MPEG, AVI, FLV, WMV, 3GP.
**Maximum file size:** 2 GB.
Tips for a good recording:
* Record the entire process from start to finish, including any waiting or decision points.
* Use a screen recorder if the process happens on a computer — this captures the exact screens and clicks.
* Narrate what you are doing as you go ("Now I open the ERP system and navigate to Purchase Orders..."). Narration helps the AI produce a more accurate breakdown.
Attach an existing AOP, process guide, spreadsheet, or reference material. Clarity extracts text documents immediately. The Agent inspects spreadsheets directly when it generates the process.
Open the process you want to document.
Click **Add Content** and select **Upload files**.
Select or drag-and-drop your document file.
The capture appears when the upload is ready. Text documents are extracted immediately; spreadsheets remain unchanged until the Agent inspects them during process generation.
**Supported formats:** PDF, Word (.docx), TXT, Markdown (.md), BPMN, Excel (.xlsx), CSV.
**Maximum file size:** 25 MB.
Duvo keeps the original spreadsheet unchanged. During process generation, the Agent inspects the workbook directly as primary evidence, including all relevant worksheets.
Upload an application screenshot, process diagram, flowchart, whiteboard, form, table, or system diagram. Clarity reads both the visible text and visual relationships such as arrows, branches, handoffs, and swimlanes.
Open the process you want to document.
Click **Add Content**, select **Upload files**, then select or drag-and-drop your image.
The upload completes first, then Duvo reads the image in the background. The capture updates automatically when its analysis is ready.
If processing fails, the capture shows the specific reason when it is safe to share, such as an unsupported animation or unreadable file. Fix the file and upload it again.
Open **View image analysis** to review the process details Duvo found. If the image is blank, illegible, or unrelated to a process, the capture stays in the list with **Needs attention** and explains why. Clarity excludes that capture from generation.
**Supported formats:** PNG, JPEG, WebP, SVG.
Duvo converts SVG files to safe PNG images before reading them.
Animated images aren't supported. Upload a still image instead.
**Limits:** 25 MB, 16,384 pixels per side, and 50 megapixels.
For SVG files, the 50-megapixel limit also applies to all embedded images combined.
Use the highest-resolution original available. Make sure labels and connectors are legible, and avoid screenshots where the process diagram occupies only a small part of the image.
You can rename captures you created. Team Managers, Administrators, and
Owners can also rename team captures. Organization Admins, Owners, and
Executives can rename captures in the organization landscape. Documents
cannot be renamed until processing finishes.
To save a copy of the original source, open the capture's actions menu,
select **Download capture**, then choose the file. If a recording has several
source files, Duvo lists each file separately. You can also download a stored
source file when document processing did not complete.
### Delete a capture
Deleting a capture removes it from the process and from future analysis. Unlike exclusion, a deleted capture no longer appears in the capture list. To delete a capture, open its actions menu, choose **Delete**, and confirm. People without delete permission do not see the option.
Who can delete a capture depends on where it lives:
* **Your own captures** — you can delete a capture you added to a process. A capture that is still being analyzed cannot be deleted yet; wait for analysis to finish, then try again.
* **Team captures** — team Managers, Administrators, and Owners can delete captures created by other people, including completed and excluded captures.
* **Organization landscape captures** — only organization Admins, Owners, and Executives can delete these, including completed and excluded captures and captures other people created.
* **Process Landscape folder captures** — the capture's creator or an organization Admin, Owner, or Executive can choose **Delete capture** on the capture card. Use this to remove a capture that failed or is stuck pending or processing.
If you want the capture out of analysis but still available for review, exclude it instead (see below).
### Exclude an unhelpful capture
Clarity keeps captures available for review even when they should not influence the process. An excluded capture stays visible with an **Excluded** badge, but Duvo leaves it out of future analysis, briefing updates, evidence selection, and Process Landscape generation.
* Before an interview starts or while it is running, choose **Not my process** when you cannot provide useful knowledge about the process. If you confirm before recording, Duvo skips microphone and screen access and creates an excluded capture. If you confirm during an interview, Duvo ends the interview and excludes the saved capture.
* Duvo may exclude an interview automatically only when the interview contains no useful process knowledge and the Agent is highly confident. The standard end-interview dialog still appears, so you can continue, complete, or discard the interview as usual.
* The capture's creator or a team Manager, Administrator, or Owner can choose **Exclude from analysis** from a completed process capture's menu. Organization Admins, Owners, and Executives can do the same for organization landscape captures.
* Hover over the **Excluded** badge to see who excluded the capture and why. If you can manage the capture, the badge also reveals an **X** control. Select it and confirm to include the capture in future analysis again.
This behavior applies to captures attached to a process and to interviews collected for Process Landscape. Exclusion does not delete the recording or transcript.
## How to Invite People
You can invite subject matter experts to add their own captures to a process — even if they do not have a Duvo account yet.
Open the process you want others to contribute to.
Click **People** in the top right of the process to open **Access and interviews**.
Enter one or more email addresses and send the invitation. You can invite multiple people at once.
Each invitee receives an email with a link to the process.
When an invitee opens the link, they see a simplified view where they can start a voice interview or upload a video.
Their captures appear in the process alongside yours, grouped by person.
Invited users who are new to your team are automatically added with the **Clarity Member** role (see below).
### See who has been interviewed
The **People** tab lists everyone on the process: the owner, invited people, pending invitations, and anyone else who has recorded. Each row shows the person's email, access level, and how many interviews are done or still processing. Expand a row to see each interview and follow-up that person has recorded, plus follow-ups assigned to them that they have not recorded yet. Select an interview to open it.
Use the row menu to remove someone's access. For a pending invitation, the menu offers **Resend invitation** to send the invitation email again as a reminder, and **Cancel invitation**.
## How to Create a Client Invite Link
A client invite link lets you share a specific process with an external stakeholder — such as a client or vendor — without sending an individual email invitation or adding them to your team. Anyone with the link can open the process and contribute a voice interview.
Open the process you want to share.
Click **People** in the top right of the process. The interview link is at the bottom of the **People** tab.
Click **Create link**. Duvo generates a unique, process-scoped token. If the process already has a visible link, click **Copy link**. If its URL is hidden, click **Get a new link** and confirm that you want to replace it; the old link stops working.
Copy the link and share it directly with the people you want to contribute — via email, Slack, or any other channel.
To invalidate the existing link and generate a new one, click **Regenerate link**.
People who open the invite link see a focused interview view where they can start a voice interview and contribute to the process. They do not gain access to the rest of your team workspace.
Client invite links are process-scoped — each link is tied to a single process. If you want to invite people to a different process, generate a separate link from that process.
## How to Generate and Review Documentation
Once you have added at least one capture and configured your team settings, you can generate the process documentation.
### Generate
Open the process.
Click **Generate process map**.
Clarity processes all captures and generates a structured document. A progress indicator shows which sections are being built.
Wait for generation to complete.
### Navigate the output
The process view uses an immersive layout: the BPMN process diagram fills the full canvas, with a floating tab switcher overlaid on top. Select a tab to open a side panel alongside the diagram.
The diagram supports interactive navigation: use the controls overlaid on the canvas to zoom in, zoom out, fit the entire diagram to the view, or download the diagram as an SVG file. Pan by clicking and dragging the canvas or scrolling with two fingers on a trackpad. Pinch or hold Command/Control while scrolling to zoom.
To follow one branch, click a path leaving a decision, or its label. The highlight includes nested decisions and stops at the first step also reachable from another path of the same decision. Loop-back connections stay visible without following the loop again. The highlight stays in place while you pan or inspect steps. Click the highlighted path again or click an empty part of the canvas to clear it. Entering Edit mode or changing the map version also clears the highlight.
You can also move around a long process from the keyboard. Select the canvas, then use the arrow keys to pan step by step, hold Shift with an arrow key to move further, Page Up and Page Down to move a screen at a time, Home to jump back to the start of the process, End to jump to the last step, and the plus and minus keys to zoom. The overview map in the bottom-left corner shows where you are in the whole process; click or drag inside it to move the view.
| Tab | Content |
| - | - |
| **Vision** | Where the process could go — what an optimized version looks like |
| **Overview** | Summary of how the process works today |
| **Impact** | Projected financial impact — revenue recovered, cost avoided, and risk reduced — with confidence rating and supporting assumptions |
| **Steps** | Step-by-step breakdown of each stage |
| **Risk & Vulnerabilities** | Identified risks, gaps, and exception points |
| **Automation Guidance** | Editable guidance that shapes the automation strategy |
Each step can show several exceptions separately, so distinct failure modes are not buried in one paragraph. An exception can include how the team handles it and an observed frequency. Clarity leaves handling or frequency unspecified when the captures do not provide that detail.
In edit mode, use **Add exception** to record another exception for a step. Enter its description, add handling if known, and choose a frequency or leave **Not specified**. Remove an exception with its remove button. Each exception needs a description before you can save the process; cancel or undo to discard edits.
### Share
Open the completed process.
Click **People**, select **Sharing settings**, and enable **Public sharing**.
To include the live Automation Proposal, enable **Share automation proposal**. Existing public links continue to show only the Current Process until you enable this option.
Copy the public link and send it to anyone — they do not need a Duvo account to view the documentation.
The shared view uses the same immersive layout as the private view. It always shows the **Current Process**. When you choose to share a live Automation Proposal that matches that version of the Current Process, recipients can switch between both views from the top of the page.
Public links share the proposal's steps and summary only after you enable **Share automation proposal**. Projected Impact, source evidence, and capture details remain private. If the Current Process changes, update the Automation Proposal before sharing it; Clarity hides a proposal that is based on an older version.
***
## How Clarity Handles Conflicting Inputs
When you add several captures to a process, they will not always agree. Two interviewees may describe the same workflow differently, or an uploaded AOP may not match what someone explains in an interview. Clarity does not pick a winner automatically — there is no fixed priority order that ranks one source above another.
Instead, Clarity treats every capture as **evidence**:
* **Inputs are evidence, not authority.** Clarity does not assume an AOP outranks an interview, or that one interviewee is more correct than another. It weighs what each capture describes rather than deferring to a single source.
* **Conflicting versions are surfaced with attribution.** When two captures describe a step differently, Clarity shows both versions and where each one came from, so you can see who said what rather than silently merging them into one account.
* **Conflicts in decision logic are flagged.** Disagreements that affect decision points, branching, or escalation paths are flagged as high-priority, because that is where an unresolved conflict has the largest impact on how the process actually runs.
* **The team is prompted to align.** Rather than auto-resolving a conflict, Clarity prompts your team to agree on a single standard for the process, so the documented version reflects a real decision instead of a guess.
* **Extra capture clarifies missing detail.** When a step lacks enough detail to automate — often because the captures conflict or leave a gap — Clarity asks for an extra capture to clarify it. See [Fill in missing information](#fill-in-missing-information) below and the capture requests in [Organize processes](#organize-processes).
This keeps the generated documentation honest about where the source material disagrees, and puts the decision about the single correct version in your team's hands.
### Choose how interviews use earlier context
Each process has an interview mode that controls what Clarity knows when a new interview starts:
* **Independent interviews** (switch off): each interview starts fresh. Clarity doesn't use earlier interviews or what it has already learned about the process, so every interviewee describes the process from scratch. Your process guidance still applies. Use this when you want each person's own account, so Clarity can record where people disagree instead of steering them toward an earlier answer.
* **Context-aware interviews** (switch on): Clarity uses everything it already has for the process, such as earlier interviews, recordings, files, and the process map. It then asks only about what's missing. Use this to fill gaps quickly after you already have a solid first version.
New processes use independent interviews by default. Processes created before this setting existed keep context-aware interviews. The interviewee's own name still reaches the interview in both modes.
To change the mode:
Open the process and click **Guidance** in the process header. The **Process guidance** dialog opens. Before the process map is generated, you can instead expand the **Process guidance** panel on the process page.
Turn **Interviews build on what Clarity already knows** on for context-aware interviews or off for independent interviews.
Click **Save**. The new mode applies to interviews that start after you save.
Builders and above can change the interview mode. You can also set it from the CLI with `duvo clarity update --interviews independent` or `--interviews context-aware`. See the [Clarity CLI reference](/cli/clarity).
***
## Edit and Ask with Clarity Chat
Clarity Chat lets you ask questions about a process and make changes to it through a simple chat — without editing anything by hand. It works on both the **Current Process** and the **Automation Proposal**.
### What you can do
* **Ask about the process** — for example, "Why is this step a risk?", "Where are we leaking margin?", or "What would change if we automated this?"
* **Edit the process** — add, reword, or remove steps, or refine the Automation Proposal, just by describing what you want.
* **Create an SOP with screenshots** — ask Duvo for a downloadable Markdown and Word procedure based on the Current Process and its screenshare captures.
* **Fill in missing information** — when a step is flagged as needing more detail, Duvo asks you one focused question at a time and updates the process from your answers.
* **Review before you accept** — every change appears as a preview, with added text highlighted and removed text struck through, so you see exactly what will change before applying it.
### How to use it
Open a completed process.
Find the **Ask Duvo** box at the bottom of the diagram. Type what you want, or pick one of the suggestions — **Edit the process**, **Ask about the process**, or **Add missing information**.
Duvo reads the process and replies. For an edit, it shows a preview of the changes on the diagram and in the step details.
Review the proposed changes. Accept them to apply, or keep chatting to adjust.
To stop a response while Duvo is working, click the stop button next to the message box.
### Generate an SOP with screenshots
Open a completed process and ask Duvo to "Write an SOP with screenshots for this process." Duvo creates a Markdown file and a Word document. Each procedure step includes a recorded screen image when one is available, followed by the action, system, inputs, outputs, and exceptions.
Download both files from the chat. Review images marked as automatically selected before you publish the procedure or use it for training. A step without a suitable recorded image includes a **No screenshot captured** note.
### Fill in missing information
When the Automation Proposal has steps that need more detail, those steps are flagged. Where the people who mapped the process give enough signal, Duvo also suggests who is best placed to fill each gap in a follow-up interview, with a short reason. Managers can assign that person to the flagged step in one click.
To provide what's missing:
Open the flagged step and choose **Answer in chat** from its menu, or click **Add missing information** in the chat.
Duvo asks one question at a time about a single step. Answer in your own words — there are no fixed choices, and you can skip a question.
Once you've covered the gaps, Duvo proposes a single update for you to review and accept.
Clarity Chat works on the generated process. Generate the documentation first (see above) before you start chatting.
## Link an Agent to a Step
Each step can name the Agent that runs it, so a process says who does the work and not only what the work is. It works on both views: on the **Current Process** the Agent is the one running that step today, and on the **Automation Proposal** it is the one proposed to run it. One Agent can run several steps; a step names at most one Agent.
Open the process and start editing the view you want — use **Edit mode** on the canvas, or double-click a step in the Steps panel.
On the step you want to hand over, open the **Agent** picker and choose one of your team's Agents. Choose **No Agent** to remove a link. Start and end markers do not support Agent links, so they have no picker.
Save. The linked steps light up on the diagram, and each one shows its Agent in the step details — click through to open that Agent.
Regenerating a view produces new steps, so it does not carry your links over. Clarity Chat edits keep them.
## Organize the Process Library
The team library has three views, switchable from the toolbar:
* **Folders** (default) — collapsible folders your team owns, plus an **Unfiled** section holding every process without a folder.
* **Ungrouped** — one flat grid of all processes.
* **Organization** — a read-only view grouping your team's processes by their Process Landscape areas, with an **Unclassified** section for processes the landscape has not placed yet.
### Key Capabilities
* **Team-owned folders** — create, rename, reorder, and delete folders (team managers and above). Deleting a folder never deletes processes; they return to Unfiled. Any team member can move processes between folders.
* **Set up from landscape** — one click creates a folder for each landscape area that contains your team's processes. These folders follow the area's name until you rename them; renaming makes the name permanently yours. Folder changes never modify the landscape itself.
* **Suggestions** — an unfiled process that the landscape has classified shows a **Suggested** chip on its card. Click the chip to file it, or use **File all suggested** on the Unfiled section header to file every suggested process at once.
* **Focused browsing** — search, status filters, and **My processes** always show flat results across all folders; clear them to return to your folder view.
### How to use it
Open **Clarity** and use the view switcher above the library to choose **Folders**, **Ungrouped**, or **Organization**.
In the Folders view, choose **Set up from landscape** to start from your operating model, or **New folder** for a custom grouping such as "Q3 priorities".
Open a process card's menu and choose **Move to folder**, or click a card's **Suggested** chip to accept the landscape's placement.
Switch to **Organization** to see the same processes grouped by their landscape areas — useful for checking how your team's work maps to the operating model.
A process lives in at most one folder. For cross-cutting groupings, use labels in the Process Landscape instead.
## Organize processes
The Clarity library follows the same hierarchy shown in Process Landscape. Open a folder to review the processes grouped under that part of your operating model.
For organizations where Process Landscape is enabled, access works as follows:
* **Open and understand the landscape** — All organization members can open **Process Landscape**. Organization Admins, Owners, and Executives see the complete folder hierarchy. Other members see the processes they can open and the areas that hold them. Processes you can't open don't appear. Ask an admin when you need access to one.
* **Maintain process nodes** — Managers can maintain process nodes for teams they manage. Organization Executives, Owners, and Admins can maintain the skeleton and all process nodes.
* **Assign process people** — Managers can assign people to processes for teams they manage. Organization Admins, Owners, and Executives can assign people across their organization scope. Access is checked for every selected process and team before any assignments are made.
* **Generate the landscape** — Only organization Executives and Owners can generate **Process Landscape**.
* **Assign ownership** — Process ownership assignment remains limited to organization Admins, Owners, and Executives.
Process Landscape generation organizes your organization’s existing processes into a company landscape. Captures add optional context for grouping and summaries, but existing processes are the source of truth. When your organization has processes but no areas yet, Executives and Owners see **Generate landscape** in the organization Clarity header.
Select **+ Add Captures** in the Clarity header to open the captures panel for the current team or organization. Use it to add interviews and documents that help Duvo understand the wider landscape.
Generation does not add or change handoffs between processes. Handoffs that people added remain unchanged when the landscape is generated again.
### Landscape interviews
Voice interviews started from Process Landscape stay at the organization level. Duvo first asks what work, outcomes, and decisions the participant is responsible for. It then uses one interview approach for the rest of the conversation:
* **Strategic perspective** — connects company goals to measurements and KPIs, value drivers, high-level contributing processes, and the relationships between those processes.
* **Process-owner perspective** — follows a natural walkthrough of the participant's area to discover high-level process purpose, boundaries, ownership, and dependencies.
The participant's description of their responsibilities determines the approach, even when their job title or existing context suggests something else. The interview does not switch approaches partway through. Landscape interviews may ask once for the frequency and approximate end-to-end duration of a high-level process, but they do not collect individual task or step timing. They also do not collect detailed process steps, systems, inputs and outputs, or exceptions; add a capture to the relevant process when that level of detail is needed.
### Key Capabilities
* **Ask Duvo across the organization** — Start a chat from an organization page to compare the accessible Process Landscape across teams, including ownership, coverage, duplication, relationships, and gaps. Duvo reports how many processes and teams it considered and warns when the landscape is too large to read in full. Organization-wide answers use landscape summaries; open a process when you need its captures or interview evidence.
* **See the full hierarchy on the map** — the map view draws each area as an outlined region with its folders nested inside, split into value chain and support rows. Areas at every depth use the same heading height and padding. Organization Admins, Owners, and Executives see every area, including empty ones. Everyone else sees an area once it holds a process they can open.
* **See which processes matter most**: **High** priority is visually emphasized on the map. **High**, **Medium**, and **Low** priorities appear in the tree and process details. Open a process and read the **Priority** section in its details for the reason behind the ranking and when it was assessed. Duvo assesses priorities automatically. Managers can override or clear priorities for processes owned by teams they manage; organization Admins, Owners, and Executives can do this across the organization. Select **Not set** to clear a priority and return the process to the unassessed state.
* **Maintain the organization skeleton** — organization Admins, Owners, and Executives can move areas and folders, change their order, add sub-areas, and delete areas and folders they no longer need — from the tree and from the map alike. Deleting an area never deletes the processes inside it; they move to **Unsorted**.
* **Maintain team processes** — managers can add, edit, move, and remove process nodes for teams they manage. Organization Admins, Owners, and Executives can maintain process nodes across all teams.
* **Review proposed processes on the map** — proposed processes appear as dashed cards. Click one to open its details. Organization Admins, Owners, and Executives can assign its owning team or remove it.
* **Accept or decline proposed areas and folders** — a proposed area or folder shows a **Proposed** badge and, when selected, the reason it was suggested. Organization Admins, Owners, and Executives can accept it into the landscape or decline it — from the hover actions on its row in the tree, from **Accept suggestion** in its details, or from its region menu on the map. A proposed area or folder stays proposed until acceptance succeeds, so moving or renaming it first does not confirm it. Declining an area or folder that already holds content also removes the suggested items inside it; the processes inside are not deleted and move to **Unsorted**. Proposals are for review by organization Admins, Owners, and Executives, so only they see proposed areas, folders, and processes. Everyone else sees the processes inside a proposed area at the top level of the landscape until it is accepted.
* **Review ownership suggestions** — managers can review team assignment suggestions for processes owned by teams they manage. Organization Admins, Owners, and Executives can review suggestions across the organization.
* **Reassign a process to another team** — organization Admins, Owners, and Executives can change the assigned team on a process. The process moves to the new team together with its interviews, captures, and invite links, and open ownership suggestions for it are cleared. Wait for any capture recording or upload in progress to finish before moving the process.
* **Map handoffs between processes** — open a process and use **Handoffs** in its sidebar. **Receives work from** lists the processes that hand work to it, and **Hands work to** lists the processes it hands work to. The other team's name shows when a handoff crosses teams. Select **+** to add a handoff, or remove one from its row.
* **Add processes manually** — managers can add a missing process for a team they manage and describe it. Organization Admins, Owners, and Executives can also assign the team that owns it.
* **Track process people** — add real people by email or placeholders by name, with an optional role tag for each process.
* **Assign people across processes** — select up to 20 accepted processes and choose **Assign people** to review and save the assignments together.
* **Accept or dismiss suggestions** — managers can review capture and team assignment suggestions for teams they manage. Organization Admins, Owners, and Executives can review suggestions across the organization.
* **Assign capture requests** — choose the teammate who should provide the missing interview or capture.
* **Notify the assignee** — accepted capture suggestions become open capture requests, and the assigned teammate receives the same notification used for extra capture.
* **Select multiple processes** — tick the checkbox on each process, or the checkbox in the toolbar to select all, to act on several at once.
* **Assign or remove in bulk** — organization Admins, Owners, and Executives can assign selected processes to one team. Managers can remove selected process nodes for teams they manage.
* **Reorganize together** — drag any selected process, in the tree or on the map, to move the whole selection into another area at once.
### How to use it
Open **Clarity** and go to **Process Landscape**.
Select a process or area with suggestions.
Use **+ Add Process** in the Clarity header to add a process. Enter a name or select a suggestion below the Name field. You can edit a suggested name before adding the process. Team Managers, and organization Admins, Owners, and Executives, can use **Add Area** on the right of the search and filter toolbar to create an area. Each area needs a name that its sibling areas don't already use; capitalization and extra spaces don't count as a difference.
To add a missing process within an area for a team you manage, open the area's action menu, click **Add process**, then enter the process name. Organization Admins, Owners, and Executives can also choose the owner team.
When you open Clarity inside a team where you can create processes, **Owner team** selects that team. If only one team is available, it is assigned automatically and the Team field is hidden. With multiple teams, choose the team that will own the process. Every process added through this dialog has an owner team.
If areas are available, choose an **Area**. Each area appears by name on its own row. Opening **Add process** from an area selects that area. Choose **Unsorted** to leave the process outside the folders. The list shows every area in the organization, because areas are shared across teams.
Open **Filter** and select **My processes** to see processes you created, captured, are listed on, or accepted an invitation to. Remove the filter to see every process you can open again. A team page opens with that team selected in the **Team** filter; remove the filter to see every team. Each view shows the areas that hold its processes.
An area or process you add stays in view even when the current search or filters would hide it. So does a process you move, and the area it leaves if the move empties it. They follow the normal rules again once you change the search or filters, or reload the page. An empty area is always available in the **Area** list, so you can file a process into it later.
To move a process to another area, open it and pick an area in the **Area** row of the **Overview**. The list holds every area in the organization; choose **Unsorted** to take the process out of its area. Anyone with the Builder role or higher on the process's team can do this.
When the current view has no areas, the Area field is hidden and **List** shows processes without an Unsorted heading. On the **Map**, process cards appear directly on the canvas when the landscape has no areas. Once an area exists, unassigned processes appear under **Unsorted**. Filtering an area out of the map keeps the Unsorted group visible.
When there are no areas or processes, Clarity shows an animated example of a process being mapped from interviews. Select **Add process** to add your first process, or **Add area** to start with an area. The introduction and landscape replace each other as content is added or removed; the previous screen disappears before the new screen appears.
Review team assignment suggestions in the sidebar's **Overview** area. Managers can accept or dismiss suggestions for processes owned by teams they manage. Organization Admins, Owners, and Executives can review suggestions across the organization.
Under **People** in that same **Overview** area, add a person by email to invite them to that process, or add a placeholder name such as "John from Finance" when you do not have an email yet.
Add or edit the optional role tag when you want to record how that person relates to the process.
Select up to 20 accepted processes, click **Assign people**, add the people by email, choose the team role each new person is invited with, and review the assignments before saving them.
In **Captures**, review capture suggestions and choose **Request capture** to create an open request.
Use the assignment picker to choose the teammate who should provide the capture.
Clarity opens in **List** by default. The **List / Map** switcher sits in the Clarity header. A view selected through the switcher or supplied in a link takes priority over the default. Sorting is available in **List**.
The Map keeps the minimap and its zoom controls visible at every process count. Use the controls below the minimap to zoom or fit the map to the available space. Turn on **Handoffs** in the toolbar to show connections across the map. With Handoffs off, selecting a process shows its connections.
Switch to the **Map** view to see accessible processes laid out spatially. Areas and folders appear as nested regions. Click a process card — including a dashed proposed card — or an area or folder name to open its details. Organization Admins, Owners, and Executives can hover over an area or folder name and open its menu to move it earlier or later, add a sub-area, delete it, or — for a proposed area or folder — accept or decline the suggestion. Managers can add and maintain process nodes for teams they manage. Drag a process card into another area or folder to move it there, just like in the tree — available when the landscape is grouped by **Structure**, not when it is grouped by **Team**. Anyone with the Builder role or higher on the process's team can drag it.
People added by email show **Pending** until the invitation is accepted. People who are new to a team are invited as **Clarity Members** by default; while reviewing the assignments, you can pick a different team role for each new person in each team, limited to the roles your own role in that team lets you grant. Existing team roles do not change. The optional role tag only describes that person's relationship to the individual process. Placeholder people do not receive an invitation and do not create a Duvo account.
Every process assignment may send its own invitation email. Assigning one person to 20 processes can send 20 separate invitation emails.
If some processes cannot be updated, they remain selected. Click **Retry failed assignments** to retry only those processes. Assignments already saved or already present are not duplicated. An invitation delivery failure does not roll back a saved assignment.
To move a single process to a different team, open it and click the **Assigned team** row in the **Overview** area, then pick the new owner. Reassignment is available to organization Admins, Owners, and Executives.
To act on several processes at once, tick the checkbox on each process you want. Organization Admins, Owners, and Executives can use the toolbar to assign them to one team. Managers can remove selected process nodes for teams they manage. You can also drag selected process nodes for teams you manage to move the whole selection into another area.
### Process tags
Process tags help your organization mark and find related processes in the Landscape. Tags are shared across the whole organization, so the same tags are available to every team.
* Tags appear on process nodes in the Landscape.
* Managers and above (and organization admins) create, edit, and delete tags; everyone in your organization can see them.
* Tags are managed by people: add or remove them directly on a process, or ask Duvo in chat to do it for you. Duvo never adds or removes tags on its own.
### When to use it
Use Process Landscape suggestions after sorting new captures, importing process material, or reviewing an L1-L4 area where ownership or missing context is still unclear.
## Inspect Processes from the CLI
Use the [Duvo CLI](/cli/clarity) when you need terminal access to a Clarity process. The CLI can find processes, compare generated versions, review evidence citations, list gaps and extra capture requests, import Miro exports, create interview invite links, export Markdown briefs, and produce structured JSON for scripts or AI assistants.
The Clarity CLI also exposes public write commands for generating, promoting, reverting, postprocessing, and building automations from Clarity process context.
## How to Regenerate Documentation
If you add new captures, want to incorporate feedback, or need a more thorough analysis, you can regenerate the documentation at any time.
Open the completed process.
Click **Regenerate Documentation**.
Optionally enter **Additional details** — any extra context or instructions that should inform the new documentation. This is useful when the existing captures do not tell the full story or when you want to emphasize specific aspects of the process.
Confirm the regeneration.
Regeneration replaces the existing documentation with a new version based on all captures and any additional details you provide. While documentation is regenerating, all tabs are disabled and the diagram canvas shows a loading state. Wait for generation to complete before switching tabs.
## Duplicating a Process
You can create a copy of any existing process using the duplicate action. This is useful when you want to start a new process based on an existing one, or when you need to make a variant without modifying the original.
To duplicate a process:
From the **Clarity** section, find the process you want to copy.
Open the process card's menu (three-dot icon).
Click **Duplicate**.
Duvo creates a new process named "Copy of \[original name]" with:
* All usable captures from the original process (voice interviews, videos, documents, and images that were fully processed — any captures still recording, processing, or marked **Needs attention** are skipped)
* The full message and generation history
* The same analysis, automation guidance, and process breakdown
The duplicate starts as a **Draft** and its sharing settings are reset — it is private by default and you will need to re-enable sharing if required.
Duplicating a process requires the **Manager** role or above.
## Process Diagram Version History
Open the **Version History** tab on the right of the process diagram to move between previously generated versions and revert to an earlier one if needed.
Team members with access to a process can review its version history. Builders and above can save, promote, revert, and remove editable drafts for any process they can access in their team.
The full history is kept — nothing is dropped as a process accumulates versions. The **Version History** tab lists each saved version by the date and time it was saved, newest first, and pulls in older ones as you scroll (or with **Load older versions**). Each entry also shows the email address of the person who made the change; versions generated by Duvo on that person's behalf show their email too. The version you are looking at is highlighted. Select another entry to show that version. The first version of a process has no **Version History** tab.
## Configure Team Settings
Before generating documentation, set up your team context so Clarity can provide accurate cost-benefit analysis.
Open **Settings** in your team space.
Navigate to the **Clarity** section.
Fill in the following fields:
| Setting | Description |
| - | - |
| Company name | Your organization's name |
| Industry | Sector for relevant benchmarks (e.g., Retail, Grocery, CPG) |
| Team size | Number of people involved in the process |
| Hourly rate | Average labor cost for time calculations |
| Revenue | Annual revenue for ROI context |
| Currency | Your preferred currency for financial figures |
| Language | Default language for interviews and generated processes |
These settings apply to all processes in the team and are used to calculate financial impact in the generated documentation. The Language setting is preselected for every new browser interview and is the language Clarity writes the generated current process, automation proposal, and chat edits in — English (United Kingdom), English (United States), Czech, French, German (Germany), German (Switzerland), Hungarian, Polish, Portuguese (Brazil), Portuguese (Portugal), Slovak, Slovenian, Spanish (Mexico), Spanish (Spain), Thai, or Ukrainian. Thai is available for interviews only: processes from Thai interviews, and chat edits to them, are written in English.
## Process Statuses
Each process moves through the following stages:
```mermaid theme={"dark"}
stateDiagram-v2
[*] --> Draft
Draft --> Collecting
Collecting --> Generating
Generating --> Complete
Complete --> Generating: Regenerate documentation
Complete --> [*]
```
| Status | Meaning |
| - | - |
| **Draft** | Process created, no captures yet |
| **Collecting** | Captures are being added and analyzed |
| **Generating** | Documentation is being generated from captures |
| **Complete** | Documentation is ready to review and share |
## Clarity Member Role
Team members with the **Clarity Member** role have a focused, interview-only experience. When a Clarity Member opens a process:
* Only the browser interview option is shown. It supports voice or screen sharing; file uploads are not available
* They can see and manage captures they have personally added
* Their captures are visible to process owners and admins alongside other contributions
This role is designed for subject matter experts who contribute process knowledge through interviews without needing full Clarity access. Admins can invite Clarity Members from team settings — enter one or more email addresses at once to send bulk invitations in a single step.
## Key Takeaway
Clarity turns informal knowledge — videos, voice interviews, documents, and images — into structured, actionable process documentation. Use it to understand how work gets done today and identify where automation can save time and cost.
## Next steps
Use the Duvo CLI for terminal access to Clarity processes — compare versions, export briefs, and produce structured JSON.
Turn Duvo's sorting pass into clear ownership and follow-up capture work across your operating model.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.