feat: selectable different 'personas' via system prompt #4621

Closed
opened 2025-11-11 15:58:53 -06:00 by GiteaMirror · 5 comments
Owner

Originally created by @aleixdorca on GitHub (Mar 31, 2025).

Check Existing Issues

  • I have searched the existing issues and discussions.

Problem Description

I am constantly changing the System prompt to force a language change, behaviour, or expected outputs. To do so I have to open the Preferences for the user and set the System prompt every time, using an external Notepad to keep different prompts available.

Desired Solution you'd like

Add different selectable System prompts per user, easily selectable, for quicker 'persona' change.

Alternatives Considered

No response

Additional Context

No response

Originally created by @aleixdorca on GitHub (Mar 31, 2025). ### Check Existing Issues - [x] I have searched the existing issues and discussions. ### Problem Description I am constantly changing the System prompt to force a language change, behaviour, or expected outputs. To do so I have to open the Preferences for the user and set the System prompt every time, using an external Notepad to keep different prompts available. ### Desired Solution you'd like Add different selectable System prompts per user, easily selectable, for quicker 'persona' change. ### Alternatives Considered _No response_ ### Additional Context _No response_
Author
Owner

@Classic298 commented on GitHub (Mar 31, 2025):

use stored prompts in the workspace for this, easily accessible with the / command

@Classic298 commented on GitHub (Mar 31, 2025): use stored prompts in the workspace for this, easily accessible with the / command
Author
Owner

@aleixdorca commented on GitHub (Mar 31, 2025):

This is fine, @Classic298 , I do use them, but can only be configured if you are an Admin user, and are only limited application-wide.

My proposal allows for each user to define its own 'personas', not quite 'prompt templates'.

Thanks!

@aleixdorca commented on GitHub (Mar 31, 2025): This is fine, @Classic298 , I do use them, but can only be configured if you are an Admin user, and are only limited application-wide. My proposal allows for each user to define its own 'personas', not quite 'prompt templates'. Thanks!
Author
Owner

@ProjectMoon commented on GitHub (Apr 1, 2025):

Wouldn't this be covered with making custom models? Which regular users can do if given permission.

@ProjectMoon commented on GitHub (Apr 1, 2025): Wouldn't this be covered with making custom models? Which regular users can do if given permission.
Author
Owner

@aleixdorca commented on GitHub (Apr 1, 2025):

I guess custom model could do it, yes, and be given access by group or user. Isn't it a overkill, though, having the admins create custom models when it could be solved by the user (bear in mind some environments can have many users) by simply creating this 'personas'?

Not trying to be picky... I just think it would be a 'nice to have' feature.

@aleixdorca commented on GitHub (Apr 1, 2025): I guess custom model could do it, yes, and be given access by group or user. Isn't it a overkill, though, having the admins create custom models when it could be solved by the user (bear in mind some environments can have many users) by simply creating this 'personas'? Not trying to be picky... I just think it would be a 'nice to have' feature.
Author
Owner

@ProjectMoon commented on GitHub (Apr 1, 2025):

I think custom models are exactly what you're asking for. Regular users can be given access to the Workspace in the permissions settings somewhere. That will allow them to create models from the base models they can see. The only thing, maybe, is that I am not sure if access to things like Tools can be limited. No reason to have users be able to upload arbitrary code execution. I think 0.6 also further advances permissions, so maybe there is something in that too that can be helpful.

@ProjectMoon commented on GitHub (Apr 1, 2025): I think custom models are exactly what you're asking for. Regular users can be given access to the Workspace in the permissions settings somewhere. That will allow them to create models from the base models they can see. The only thing, maybe, is that I am not sure if access to things like Tools can be limited. No reason to have users be able to upload arbitrary code execution. I think 0.6 also further advances permissions, so maybe there is something in that too that can be helpful.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#4621