> For the complete documentation index, see [llms.txt](https://everyday-digital.gitbook.io/pathways-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://everyday-digital.gitbook.io/pathways-docs/pathway-editor/create-a-pathway.md).

# Create a Pathway

## **What is a Pathway?**

**Pathways are interactive journeys composed of a sequence of digital and real-life activities.** You can create multiple levels, each containing steps, activities or tasks to be fulfilled. 

## Quick Steps: Pathway Setup

1. **Open Pathways.** Select the + icon to create a new Pathway.
2. **Name your Pathway.** Choose the app it will be published to, and select Create.
3. **The Pathway Editor will be opened under Listing.** Go to Pathway to start creating.
4. [**Add Activities**](/pathways-docs/pathway-editor/pathway-activities.md)**.** By default, you can have up to four (4) Pathway levels. Add activities to a level of your choosing by selecting the + icon on the page. 
5. **Setup nudge notifications (optional).** 
6. **Complete and** [**Publish**](https://everyday-digital.gitbook.io/publishing-docs/guides/publish-from-pathways)**.** When your Pathway is ready, check the preferred Settings, Listing and Theme & Assets. Go to [Targeting](https://everyday-digital.gitbook.io/publishing-docs/publishing-options/targeting) to publish the Pathway to your app.

{% hint style="info" %}
**The** **Publish pathway to...** option will only be available for accounts with **multiple apps**.
{% endhint %}

## **What are Pathway Levels?** 

**A Pathway can contain up to 4 levels**. Each level contains a series of rows with up to three (3) activities per row. 

**Only levels to which activities are added will become part of your Pathway.** This means you can choose to use 1-4 levels.

{% hint style="info" %}
All required (non-optional) activities must be completed in a level for the user to reach the **next level** in a path. 
{% endhint %}

## What are Pathway Level Milestones?

**By default, each level starts with a single** [**Milestone**](/pathways-docs/pathway-editor/pathway-activities/milestone.md) **activity in the** **first row**. No other activities can be placed alongside or in place of the Milestone activity. 

## **Pathway Rows**

**Each row can have** **up to three (3) activities**. This can be a combination of optional and required activities A user must complete all required activities in a row (1-3 activities) before they can move down to the next row in a level.

## **Required vs Optional Activities**

**Activity Settings.** When editing a [Pathway activity](/pathways-docs/pathway-editor/pathway-activities.md), choose whether it is required or optional. Required activities must be completed before proceeding. 

**Colour** **activities represent a required activity**. This means the user must complete the activity in order to proceed. 

**Grey** **cards are optional activities**. The user is not required to complete them.

## **Rewards**

**Rewards are automatically awarded to a user when they reach the row that the reward is on.** Ideally, a reward should sit as a single activity in a row. [Go here to learn more.](/pathways-docs/pathway-editor/pathway-activities/reward-activity.md)

## **Certificates**

**Certificates are automatically awarded to a user when they reach the row that the certificate is on.** Ideally, a certificate should sit as a single activity in a row. [Go here to learn more.](/pathways-docs/pathway-editor/pathway-activities/certificate-activity.md)

## **Connect Pathway**

**Connect Pathway allows you to connect multiple Pathways.** When a user interacts with connected Pathway activity, it enrols them on the Pathway and allows them to switch to the connected Pathway or remain on the current Pathway.<br>


---

# 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://everyday-digital.gitbook.io/pathways-docs/pathway-editor/create-a-pathway.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.