> 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-settings/profile-assignments.md).

# Profile assignments

**Profile assignments** control who is allowed to enter a journey. Set them on the journey's **Settings** tab.

## Assign access

Under **Profile assignments → Add assignment**:

1. Choose a **Role**.
2. *(Optional)* Choose a **Profile** to narrow the assignment — leave it as **All profiles** to apply to the whole role.
3. Click **Assign**.

Add as many assignments as you need. A customer or CSR can open the journey only if their role (and profile, when one is specified) matches an assignment.

This replaces the profile assignment that lived in the legacy journey "General" configuration.


---

# 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-settings/profile-assignments.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.