# Epic ITSM-19 - OpenProject service portal

Project: Stream IT service management (ITSM)
Status: in specification
URL: https://community.openproject.org/work_packages/ITSM-19

## Detailed specification

### Motivation and background information

*   Growing OpenProject usage increases operational complexity
    
*   Current admin workflows do not scale
    
*   Customers expect enterprise-grade service experiences
    
*   Portal aligns with long-term positioning as a platform, not just a tool

### Acceptance criteria

##### _\[To be discussed\]_&nbsp;First Version (MVP):

1.  **Authentication &amp; Access**
    
    *   Login via existing OpenProject credentials
        
    *   Role-based visibility
        
2.  **Service Portal Dashboard**
    
    *   Overview metrics (open requests, response time, resolution rate)
        
    *   Quick actions (New Incident, New Bug, Feature Request, Access Request, New Project)
        
    *   Navigation to main service areas
        
3.  **Support &amp; Operations**
    
    *   List of user’s requests with status and priority
        
    *   Request creation flow with structured forms
        
    *   Tracking of existing requests
        
    *   Categories: Incident, Bug, Feature Request, Service Request, Question
        
4.  **Access Management**
    
    *   List of all members and users with access
        
    *   List of access requests pending of action
        
    *   Option to request new accesses
        
    *   Permissions management
        
    *   Group management
        
5.  **Plans and billing**
    
    *   Overview of current plans and billing
        
    *   Option to upgrade or downgrade
        
    *   Redirects to current billing platforms
        
6.  **Portfolios, programs and projects**
    
    *   List of all active projects with status track
        
    *   List of all projects in process of approval
        
    *   Create new project requests (PIR)
        
7.  **Knowledge Base**
    
    *   Quick access to instance wiki pages
        
    *   Quick access to OpenProject documentation
        
8.  **Integrations**
    
    *   Overview of available integrations
        
    *   Connect / disconnect flows (guided modal)
        
    *   Basic configuration inputs
        
9.  **Compliance and security**
    
    *   List of all audits passed for that OpenProject version
        
    *   Quick access to GDPR and ISO guidelines
        
    *   Quick access to terms and conditions of OpenProject
        
    *   Data related request: data deletion, data export...
        
10.  **Feedback and roadmap**
     
     *   Creation of new feedback and ideas requests
         
     *   Most voted community work packages visible
         
     *   Product roadmap visible

### Out of scope

*   Automated workflows and approvals
    
*   Full add-ons planning, billing and payment handling
    
*   Advanced SLA configuration and reporting
    
*   Cross-tenant management and branding
    
*   Custom integration builders
    
*   Full ITSM change and problem management
    
*   ...

| Attribute | Value |
| --- | --- |
| Mockups | https://www.figma.com/design/nEyOtdOvDTflfBBZGSOCic/Service-Portal?node-id=0-1 |

## Planning

| Attribute | Value |
| --- | --- |
| Roadmap | 2027 Q1 |
| Date |  |
| Votes | 1 |
| List | RM ITSM |
| Target versions |  |
| Relevance |  |

## Subitems

| ID | Type | Subject | Status | Assignee | Target versions | Project | Priority | Spent time |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| FND-265 | Epic | Define reporter while creating the work package | new | Alfonso Mancilla |  | Stream workspace foundations | Medium |  |
| ITSM-48 | Feature | Report service request with optional user account registration | in specification |  |  | Stream IT service management (ITSM) | Medium |  |

## Bugs and other work packages

| ID | Type | Subject | Status | Assignee | Target versions | Module |
| --- | --- | --- | --- | --- | --- | --- |
| ITSM-16 | Task | Automated Notifications per Service Level | new |  |  |  |
| ITSM-13 | Task | Technical Support Request Form | new |  |  |  |

## Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Enterprise plan |  |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager | Nova Bonic |
| Feature Lead |  |
| Designer | Marc Alcobé |
| Developers | OP Dev Titan Team |
| Requested by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| Work |  |

## Description

# User Problem

## User

Project Managers and Customers operating OpenProject at scale (multiple projects, users, integrations).

## Problem

Users interacting with OpenProject lack a **centralized, role-based service interface** to:

*   Report incidents and bugs
    
*   Request services (access, projects, licenses)
    
*   Track request status and outcomes
    
*   Manage integrations and configurations
    

As a result, operational and administrative interactions are fragmented, opaque, and inefficient.

## Pain

**Current workarounds**

*   Sending emails or chat messages to admins/support
    
*   Creating ad-hoc work packages in random projects
    
*   Using external ticketing tools disconnected from OpenProject
    
*   Manually configuring integrations without visibility or guidance
    

**Why this is painful**

*   No transparency into request status or ownership
    
*   High manual effort for administrators
    
*   Inconsistent handling of similar requests
    
*   Users do not know where to go or what is possible
    
*   Poor scalability as user base grows
    

# Business Case

## Reach

*   10–20% of active OpenProject users, mainly admin users, regularly interact with support, access, or admin processes
    
*   100% of enterprise or managed-service customers would benefit of this portal
    

## Impact

*   Reduced admin and support workload
    
*   Faster resolution times for incidents and service requests
    
*   Improved user satisfaction and trust
    
*   Increased adoption of advanced features (integrations, automation)
    
*   Stronger positioning of OpenProject as an enterprise-ready platform
    

## Confidence

**Top risks**

1.  **Scope:** turning portal into a full ITSM tool  
    Mitigation: Strict MVC definition aligned with mockups
    
2.  **Integrations:** external systems, auth  
    Mitigation: Start with visibility + request flows, not full automation
    
3.  **Role and permission:** data transmission, logins, permissions management  
    Mitigation: Clear persona-based access rules and centralised login options
    
4.  **Adoption risk:** users keep emailing even if they have a portal for it  
    Mitigation: Make portal the single visible entry point and migrate emails to the portal
    

## Urgency and Priority

*   Very useful for enterprise and managed-service scenarios
    
*   Strong dependency for scaling OpenProject usage
    
*   No hard external deadline
    
*   Tradeoff: Delays other feature work but reduces long-term operational cost
    

## Solution

A **central Service Portal UI** tightly integrated with OpenProject that provides:

*   A single entry point for operational and administrative requests
    
*   Clear request types, forms, and status tracking
    
*   Self-service access to integrations and documentation
    

## Out of Scope for the MVP

## Differentiation

*   Native integration with OpenProject work packages and permissions
    
*   Clear separation between **project work** and **service interactions**
    
*   Role-aware, opinionated UX instead of generic ticketing
    
*   Lightweight alternative to external ITSM tools
    
*   Consistent experience aligned with OpenProject UI patterns
    

<br>

# Launch and Growth

## Measures

**Quantitative**

*   % of support requests created via Service Portal
    
*   Reduction in admin email/chat requests
    
*   Average time to resolution
    
*   Number of self-service integrations connected
    
*   Active monthly portal users
    

**Qualitative**

*   User feedback on clarity and transparency
    
*   Admin satisfaction with reduced manual effort
    

## Messaging

<figure class="table op-uc-figure_align-center op-uc-figure"><table class="op-uc-table"><tbody><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">Headline</p></th><td class="op-uc-table--cell"><p class="op-uc-p">Introducing the OpenProject Service Portal: One Place for Support, Access, and Integrations</p></td></tr><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">First Paragraph</p></th><td class="op-uc-table--cell"><p class="op-uc-p">OpenProject introduces the Service Portal — a centralized, self-service interface that gives users and organizations a clear, structured way to request support, manage access, and configure integrations. The Service Portal reduces friction, improves transparency, and helps teams scale OpenProject with confidence.</p></td></tr><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">Customer Quote</p></th><td class="op-uc-table--cell"><p class="op-uc-p">“Before the Service Portal, every request started with an email. Now our teams know exactly where to go — and we finally have visibility and consistency across all requests.”</p></td></tr></tbody></table></figure>

## Go to market

*   _\[To be discussed\]_
