# Epic AA-230 - User-defined text assistant actions

Project: Stream Agents & Assistants
Status: new
URL: https://community.openproject.org/work_packages/AA-230

## Detailed specification

### Motivation and background information

### Acceptance criteria

### Out of scope

| Attribute | Value |
| --- | --- |
| Mockups |  |

## Planning

| Attribute | Value |
| --- | --- |
| Roadmap | 2027 Q1 |
| Date |  |
| List |  |
| Target versions | 18.2.0 |
| Relevance |  |

## Subitems

_No work packages_

## Bugs and other work packages

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Module | Artificial Intelligence / AI text helper (AITH) |
| Enterprise plan | Enterprise / Professional (PRO) |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager | Dominic Bräunlein |
| Feature Lead |  |
| Designer |  |
| Developers | OP Dev AI team |
| Interest by |  |

## Estimates and progress

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

## Description

# User Problem

## Problem

Text assistant actions are defined by admins for the whole instance. Users also have writing needs that are personal or one-off, which an instance-wide action does not cover.&nbsp;

**Examples:** 

*   A person doing triage jots down what is missing from an incoming BUG report and turns it into a friendly comment to the reporter.
    
*   A specific tone for a customer when writing comments.
    
*   A report format only one person uses.
    
*   A single instruction like &quot;shorten this to three sentences&quot;
    
*   A non-native speaker writes the comment in German and translates it to English, keeping glossary terms fixed and product names untranslated.
    

## Pain

*   Users ask an admin to add an action for their own use. The admin either declines or the shared list fills up with actions most people never use.
    
*   For one-off instructions, users go back to copying text into external AI tools, with the same break in flow and the same data privacy concerns the text assistant was meant to remove.
    
*   Users who need the same instruction repeatedly have to type it again every time.
    

# Business Case

## Solution

*   Ad-hoc action: users type their own instruction in the text assistant and run it on the current text without saving it.
    
*   Save as personal action: an ad-hoc instruction can be saved with a name. It is stored right away and appears in the user&#x27;s action list.
    
*   Personal actions are visible only to the user who created them. Users can edit and delete them.
    
*   The action list shows admin-defined and personal actions as separate groups.
    
*   Admins get an instance-wide setting in the text assistant administration to allow or disallow user-defined actions.
    

## Out of Scope for the MVC

*   Sharing personal actions with other users or with a project
    
*   Promoting a personal action to an instance-wide action
    
*   Project-level actions
    
*   Allowing the feature per role or group instead of instance-wide
