> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/product/journeys-and-pages/journey-steps/journey-step-types.md).

# Step Roles

A step's **Role** declares what the step is for — and, crucially, **which internal commerce actions the step must perform**. When a step has a role, the role brings a mandated set of **required (locked) commerce actions** with it, so PeakCommerce's own writes always run for that kind of step. Some roles also change how the step runs.

| Role        | What it does                                                                                                                                                                                                                                                                                                           |
| ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **(none)**  | Default runner behavior; no mandated actions.                                                                                                                                                                                                                                                                          |
| **Pricing** | Skips the `?p=` prefill requirement, so custom pricing pages don't trip the prefill guardrail.                                                                                                                                                                                                                         |
| **Signup**  | Marks an account-creation / lead-capture step and mandates the internal writes that create the organization and contact. Signup steps also unlock the [signup form field editor](/product/journeys-and-pages/journey-steps/signup-form-fields.md), which controls the fields the form collects and how each validates. |
| **Payment** | Marks a payment / checkout step and mandates the internal writes that record the order and keep the contact and organization current.                                                                                                                                                                                  |
| **Content** | Marks an informational step.                                                                                                                                                                                                                                                                                           |

Set a step's role when editing it on the **Steps** tab. The required actions a role brings appear **locked** (🔒) in the step's **Commerce actions** list — you can reorder them but not remove them. See [Commerce Actions](/product/journeys-and-pages/journey-steps/commerce-actions.md#required-actions).


---

# 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.peakcommerce.com/product/journeys-and-pages/journey-steps/journey-step-types.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.