---
title: "Set up roadmap work with Kai Copilot"
description: "Choose who decides on requests, who hears about shipped features, and how release notes and newsletters go out."
url: https://help.gleap.ai/de/articles/385-set-up-roadmap-work-with-kai-copilot
collection: "Roadmap and changelog"
updated: 2026-11-01
language: de
alternates: [en]
---

# Set up roadmap work with Kai Copilot

Choose who decides on requests, who hears about shipped features, and how release notes and newsletters go out.

Open **Kai Copilot → Settings → Roadmap & changelog**. This is the current setup for the work previously called Kai PM. You need the plan and permissions shown by the page; the request board can still be worked manually.

### Review the setup card

![First-run roadmap setup and the proposed automation choices in the Pied Piper demo project.](https://staticfiles.gleap.io/p613b5dd730aed737108f87ab/HYTDDpK7kxLYA9AY8OdxDGQgWMlJ4N1YpqxpN09612KW7uu7OeDUFengoKl0ypXkCpXFglNU0uV.png)

![Roadmap settings screen in the Pied Piper demo project.](https://staticfiles.gleap.io/p613b5dd730aed737108f87ab/Ct0puxb1VQMvQCI1MyavMu4aDUnSvbbY9H7wRKI2OfYL4YzXbHCyIJM8zXTR5zaeF6HDAwS9dHM.png)

If roadmap work has not been set up, **Set up your roadmap** shows the initial choices. Review each one before choosing **Use these**:

-   **New requests** starts on **Asks first**.
    
-   **Tell requesters it shipped** starts on **Does it**.
    
-   **Release notes** starts on **Asks first**.
    
-   **Newsletter** starts on **Never**.
    
-   **Weekly brief** is offered on.
    

The text beside each choice says what it will do. You can change the choices before applying them and afterwards on the settings page.

### Choose the roadmap team

Add the people who should receive heads-ups, review work and receive the brief under **Roadmap team**. Make sure someone owns approval work before enabling a schedule.

### Give Kai your priorities

Under **What comes first**, add **Your goals**, check the **Company profile** and decide whether **Revenue at stake** should count.

Use goals that help compare actual requests, such as improving onboarding for a particular customer group. Keep the company profile current when your product or audience changes.

### Set feature-request handling

Choose a mode for **New requests**. Use **Asks first** if your team should review decisions in Needs you, **Does it** for automatic decisions within the configured rules or **Never** for manual handling.

Review **Ask for details** and **Spot what already exists** separately.

### Set publishing and follow-up

Configure **Tell requesters it shipped**, **Release notes** and **Newsletter** individually. Review schedules, sources, writing style, newsletter recipients and sender before turning automatic sending on.

Open **Inbox → Roadmap** to check the first requests and **Needs you** to review proposals. Check the first routine run before relying on recurring work.

### Related

-   [Let Kai Copilot help run your roadmap](https://help.gleap.ai/en/articles/384-let-kai-copilot-help-run-your-roadmap.md)
    
-   [How Kai ranks feature requests](https://help.gleap.ai/en/articles/386-how-kai-ranks-feature-requests.md)
    
-   [Follow Kai’s roadmap work](https://help.gleap.ai/en/articles/391-follow-kais-roadmap-work.md)