> For the complete documentation index, see [llms.txt](https://knowledge-base.letsgetdigital.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge-base.letsgetdigital.com/the-admin-panel/content/application-1/personal-programme-app.md).

# Personal programme (App)

<figure><img src="https://772941315-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M5LNCGpK5lyymcFZU4V%2Fuploads%2FCeCHgBl0PNtpunfC0qAm%2FUntitled%20design%20(25).png?alt=media&amp;token=5e027a3c-2008-4ac0-82ed-8e220262dea9" alt=""><figcaption></figcaption></figure>

## How the personal programme works in the App

If implemented users will be able to view a personal programme of sessions that they are registered for at the event. The personal programme can include plenary sessions that may be implemented by default by the event organiser, sessions they registered for when registering for the event or by registering for a session within the app.&#x20;

### How to set up the personal programme in the App

You can simply add the personal programme to the app navigation to allow users to see their personal programme. Read the following article on [how to create a navigation item](/the-admin-panel/navigation/application/the-navigation-menu.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledge-base.letsgetdigital.com/the-admin-panel/content/application-1/personal-programme-app.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.