> 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/stop-workflow-for-entity.md).

# How to stop a workflow for a given entity?

When you have a workflow with enrolments in progress, you can decide to stop the workflow to not execute the next steps. We will show you to do that.

## Stopping a workflow for an enrolled entity

If you want to stop the workflow from executing for an enrolled entity, you can do so by following these steps:

* Go to **Workflows**, open the **Workflow**, and click **Enrollments**
* Select the entity, such as a partner, team member, or payout
* Click **Unenroll** and the **Yes, I’m sure option**

Once you do this, it will mean the workflow has been stopped manually.

The next time the same entity matches the criteria to enter the workflow, the entity won’t be enrolled a new time because the entity was manually removed.

## Common use cases

### Partner follow-ups

For example, if you have a *Partner invitation status changed* trigger, you send reminder emails to partners when the Partner invitation status is Pending. Still, the partner decides that they do not want to join. You can stop the workflow by unenrolling the partner team member, so they stop receiving emails.


---

# 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/stop-workflow-for-entity.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.