> For the complete documentation index, see [llms.txt](https://docs.unifize.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.unifize.com/user-guide/definitions/process.md).

# Process

### Definition

A **Process** in Unifize represents a structured workflow designed to achieve a specific outcome. It defines the sequence of activities, stakeholders involved, and the data required for execution.

{% hint style="info" %}
Check out [Developer Documentation for Processes](broken://spaces/cZhAoxKwpBioghRXCQLi/pages/sN2F42QIxZWI5vdiT24e)
{% endhint %}

### Key Features

* Standardizes operations for consistency.
* Tracks progress and automates workflows.
* Ensures visibility and compliance.

### What constitutes a Process?

You can access the settings of an individual process through the Process Builder.

Every process on Unifize contains the following key elements:

* **Team:** The description of the process, owner, default participants and process owner(s).
* **Status:** Various stages in the process lifecycle across two states: Pending vs Completed.
* **Checklist:** Structured way of capturing contextual information for a process record.
* **Deleted Fields:** Fields that are deleted in history.
* **Privacy Settings:** Ability to make certain processes private, editable only by the Process Owner.
* **Advanced Process Settings:** Various configuration options to control the records of a process.
* **Reminders:** Ability to automatically notify participants based on preset parameters.
* **Layout:** Option to choose checklist visibility across different devices.

<figure><img src="/files/jhA98qPnpwhU5YWr3EgN" alt=""><figcaption><p>Checklist configuration of a 'Change Control' process</p></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.unifize.com/user-guide/definitions/process.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.