Architecture Levels

Architecture Levels

Architecture levels let you define the semantic levels of your process architecture per environment. Instead of a flat list of processes and folders, you can model a real hierarchy (for example, Enterprise Value Stream → Process → Subprocess). Every level has its own name, icon, documentation fields, and rules.

What Are Architecture Levels?

Each level is a configurable process “type” in your hierarchy. A level defines:

• Display name and icon: how processes of this level appear in the catalog
• Documentation fields: which documentation sections are shown for processes of this level
• Model availability: whether processes of this level can have a BPMN model
• Allowed child levels: which levels a process of this level may contain

Exactly one level is the default level of the hierarchy: the level new items are assigned to in the catalog. Folders remain pure organizational containers: they carry no documentation sections and no model.

Default Levels

When an environment is created, ProcessMind seeds it with a starter set of levels:

Level	Description
Enterprise Value Stream	The top level, representing an end-to-end value stream
Process	Standard processes that make up a value stream
Subprocess	Detailed subprocesses nested within a process
Value Stream	Value streams modeled with a Value Stream Mapping (VSM) model
VSM Element Level	The elements inside a VSM model
Folder	An organizational container: no documentation sections, no model
Activity	Individual activities inside a process, documented on the BPMN model

Process is the default level of a new environment, so processes that have no level of their own are assigned to it. You can rename, add, and remove levels at any time, and you decide which level is the default.

Configuring Levels

To define your own architecture:

1. Sign in as an environment admin or organization admin
2. Open Settings and navigate to Process Architecture
3. Edit an existing level or create a new one
4. Set the display name and choose an icon
5. Enable the documentation sections that should appear for this level
6. Decide whether processes of this level can have a model
7. Select the allowed child levels to control what can be nested below
8. Mark exactly one level as the default level

Changes apply to new and existing processes of that level, so the catalog, process settings, and documentation adapt to the level automatically.

How Levels Affect Your Process Catalog

Once configured, levels drive the entire process experience:

• Processes are labeled with their level’s name and icon in the Process Catalog
• The documentation view only shows the fields enabled for the level
• A model editor is only available when the level allows it
• The hierarchy is defined by allowed child levels, not by folder nesting

This makes your Process Catalog reflect your actual process architecture. For the broader picture of environments and hierarchy, see Environments (Tenants) and Organization Settings.

Related topics

• Organization Settings
• Environments (Tenants)
• Audit Log
• Enterprise Process Architecture