# Pool / Lane

**Pools and Lanes** are used to **organize and structure activities** within a Process Template Diagram.\
They represent **process participants, roles, or responsibilities**, helping to clearly define **who performs which tasks** in a process.

In ONEWEB **Process Designer**, Pools and Lanes follow **BPMN standards** and improve the readability and maintainability of process models.

***

### Purpose of Pool / Lane

Pools and Lanes are used to:

* Visually organize activities by responsibility
* Represent different roles, departments, or work parties
* Clarify ownership of tasks within a process
* Improve understanding for both business and technical users

Using Pools and Lanes makes complex processes easier to interpret and manage.

***

### First Step in Process Design

The **first step** in designing any process within the **Process Template Diagram** is to **add a Lane**.

In the **Node / Component Panel**, the **Lane section** provides a **Horizontal Lane** component that can be dragged and dropped into the Diagram Panel.

Once added, all activities, events, and gateways are placed **inside a Lane**.

***

### Lane Types in Process Designer

#### Horizontal Lane

* The **Horizontal Lane** is the primary lane type available for process design
* It spans horizontally across the diagram
* Multiple lanes can be stacked vertically
* Each lane typically represents:
  * A role
  * A work party
  * A functional responsibility

Horizontal Lanes help segment the process flow visually while maintaining a single process context.

***

### Working with Lanes

After adding a Lane, users can:

* Rename the lane to represent a role or responsibility
* Drag and drop:
  * Activity Nodes
  * Events
  * Gateways\
    inside the lane
* Add additional lanes to separate responsibilities
* Reorganize lane layout to improve clarity

Activities should always be placed within an appropriate Lane to indicate **ownership and execution context**.

***

### Usage Guidelines

* Always start a process by adding at least one **Lane**
* Use clear and meaningful names for lanes (e.g. *Requester*, *Approver*, *System*)
* Keep the number of lanes manageable to avoid clutter
* Align lanes with **Work Parties or Roles** defined in the process
* Use lanes consistently across related processes for standardization

***

### Summary

The **Pool / Lane** component provides essential **structural organization** for process diagrams.

Key points:

* Lanes define responsibility and execution context
* Horizontal Lanes are used in Process Designer
* Processes should always begin with a Lane
* Improves clarity, readability, and collaboration
* Supports BPMN‑compliant process modeling

Proper use of Pools and Lanes ensures that processes in **ONEWEB Process Designer** are **well‑structured, understandable, and aligned with real‑world responsibilities**.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.onewebstack.com/oneweb-platform-th/designer-reference/process-designer/process-designer-component/pool-lane.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.