> For the complete documentation index, see [llms.txt](https://docs-vnext.kiflo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-vnext.kiflo.com/automation/workflow-enrollments.md).

# What are workflow enrollments?

When a workflow is executed, an entity will be enrolled and can have different statuses during the workflow execution.

## Workflow enrollments meaning

Enrollments are an entity that has entered the workflow. Enrollments have different types, which are based on the trigger. At this time, the existing enrollment types are:

* Payout
* Partner
* Partner team member
* Partner Program

## Viewing enrollments

* Go to **Manage**, open **Workflows**, choose an existing Workflow, and then click the **Enrollments** tab

## The 5 enrollment statuses

### Success

The status refers to when an entity has reached the end of a workflow and all the steps have been executed without any issues.

### In progress

Under this status, the entity is still in the workflow, they have yet to reach the end, and there are no errors.

### Stopped

The status means a user has manually stopped the workflow. In that case, the workflow is not completed.

### Cancelled

The status means the system has automatically stopped the workflow because we are not able to continue the execution of the workflow. The workflow could have been disabled or the associated entity deleted. In that case, the workflow is not completed.

### Error

The status means the system has automatically stopped the workflow due to technical errors. In that case, the workflow is not completed.

## Filter Enrollments

* To filter Enrollments, click **Show filters**
* Select whether you want to filter Enrollments based on the **Enrollment date**, **Name,** or **Status**


---

# 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-vnext.kiflo.com/automation/workflow-enrollments.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.
