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

# Process Index: a deeper dive

> Build and manage a multi-level process library, from value streams down to individual activities.

export const NeedHelp = () => <Note>
    <strong>Need help?</strong> Use the in-app chat — click the chat bubble in the bottom-right corner of Klarity Architect (staffed 24×5) — or email <a href="mailto:support@klarity.ai">support@klarity.ai</a>.
  </Note>;

## Overview

The Process Index is the central repository for all captured processes in Klarity. This guide covers advanced features for building and managing a comprehensive, multi-level process library.

## Building a multi-level Process Index

Klarity supports hierarchical process organization, blending 15+ years of company blueprinting experience with industry-standard levels (such as APQC and Business Capability Models):

### Level 1 (L1 / parent nodes): value streams

Broad cross-functional categories like *Order to Cash*, *Procure to Pay*, or *Record to Report*. These are the top-level groupings. We recommend breaking out by:

1. **Customer-impacting value streams** — directly face the customer and correlate to revenue generation and retention.
2. **Employee value streams** — enable your company to find, retain, and develop employees.
3. **Enterprise value streams** — shared services that keep the engine of your company running.

### Level 2 (L2): stages and business capabilities

Major process groups within each area. For example, under Order to Cash: *Order Management*, *Billing*, *Collections*. Think of these as stages that advance the value stream, or as business capabilities.

### Level 3 (L3): processes

Individual processes — for example, *Create Sales Order*, *Generate Invoice*, *Process Payment*. Think of these as Lego blocks that advance a value stream stage or capability.

### Level 4 (L4): sub-processes

Sub-groupings or variations within a process. Optional, depending on the complexity of your organization.

### Level 5+ (L5 / leaf nodes): process activities

Granular processes an individual executes from start to finish. This is where the discovery agent focuses — interviews, Companion sessions, or ingesting documentation.

## Organizing your index

### Creating the index

* Start with L1 categories that align with the value streams crossing functions in your organization.
* Build L2–L3 levels based on actual process groupings.
* Let Discovery agents populate the lower-level (L4–L5) detail. They do this in two different ways:
  * **Companion** runs continuously in the background as people work and automatically builds out the index — creating and updating process nodes as it observes new activity. This is what grows and maintains the Process Index over time.
  * **AI Interviewer & File Uploads** are targeted capture: you point them at a specific process (a guided interview, or an uploaded recording or document) and they populate that node's detail. They fill in the process you're capturing rather than building out the index structure on their own.

<Frame>
  <video autoPlay loop muted playsInline src="https://mintcdn.com/klaritydocs/236MVH64i-O8oUtZ/images/process-index-build.mp4?fit=max&auto=format&n=236MVH64i-O8oUtZ&q=85&s=7dd3b7dd2c6f770c128609e5915d3be8" aria-label="Building the Process Index by creating L1 value stream categories and L2 process group nodes, then adding new nodes to the hierarchy." data-path="images/process-index-build.mp4" />
</Frame>

### Navigating the index

* Use the tree view to browse the index.
* Use search to find specific processes by name, system, or keyword.
* Use filters to narrow by department, region, or process owner.

### Moving processes

Reorganize the hierarchy as your understanding of the business evolves. There are two ways to move a process node:

* **Drag and drop** — grab a node and drop it onto a new parent, or onto the **Drop here to move to root level** zone at the top to promote it to a top-level value stream.
* **Row menu** — open the node's **⋯** menu and choose **Move**, then pick its new location.

<Frame>
  <video autoPlay loop muted playsInline src="https://mintcdn.com/klaritydocs/236MVH64i-O8oUtZ/images/process-index-move-drag.mp4?fit=max&auto=format&n=236MVH64i-O8oUtZ&q=85&s=d9617c942533aeb22563ce0f4c8d829d" aria-label="Dragging and dropping a process node to reposition it within the Process Index hierarchy, including selecting and moving nodes." data-path="images/process-index-move-drag.mp4" />
</Frame>

### Deleting processes

To remove a process node, open its **⋯** menu and choose **Delete**.

<Warning>
  Deleting removes the process node from your index. If you only want to reorganize, use **Move** or **Rename** instead.
</Warning>

<Frame>
  <video autoPlay loop muted playsInline src="https://mintcdn.com/klaritydocs/236MVH64i-O8oUtZ/images/process-index-delete.mp4?fit=max&auto=format&n=236MVH64i-O8oUtZ&q=85&s=cfd897b8ef8a05d398600b6a225d07c7" aria-label="Deleting a process node from the Process Index using the delete option in the context menu." data-path="images/process-index-delete.mp4" />
</Frame>

## Exception handling

Processes often have exception paths — scenarios that deviate from the happy path. Klarity captures these as variant flows within the process, allowing you to:

* Capture multiple paths through a single process.
* Identify the most common exceptions.
* Quantify the effort spent on exception handling vs. the standard flow.

## Advanced features

### Bulk operations

Perform actions across multiple processes at once — useful for large-scale reorganization or metadata updates. Many of these changes can be made conversationally with AI Chat: describe what you want (for example, splitting, merging, or re-tagging a set of processes) and Klarity proposes a plan you can review before it runs. See [Using AI Chat](/docs/user-docs/improve/using-ai-chat).

### Export

Export individual processes or entire sections of the index for reporting, presentations, or external sharing.

<NeedHelp />
