# Feature OP-10049 - Configurable landing page for project

Project: OpenProject
Status: new
URL: https://community.openproject.org/work_packages/OP-10049

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| Sprint |  |
| Backlog bucket |  |
| Votes | 1 |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Feature Lead |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

**As** a project admin  
**I want to** be able to configure the landing page of a project not to be the work packages  
**so that** other modules get more tightly integrated and accessible.

For instance: the top level project might benefit from landing on the Overview page. If would also make the Boards module more useful. The current behaviour of OpenProject kind of degrades that this functionality as its implemented to be a direct competitor for the work package table. But OpenProject kind of forces the table views into place.

**Acceptance criteria**

  - Having a setting in the project settings to set a specific module(?) as landing.
  - The module itself should be responsible on figuring out the more specific landing (e.g. as proposed in <mention class="mention" data-id="31423" data-type="work_package" data-text="##31423">##31423</mention>), not inside the project settings.
