Originally created by @nonlinear on GitHub (May 19, 2025).
Check Existing Issues
I have searched the existing issues and discussions.
Problem Description
When using Azure TTS, you can set vocie only in system, and sometimes, some voices per user (sometimes not. some voices pass per user, some crash)
Desired Solution you'd like
It would be best if voice settings follow the suggested cascading path:
system
group
user
agent (model)
conversation
with later taking precedence over first.
this way we have enough granularity for different voices and languages (my group is bilingual, my users are not)
Alternatives Considered
No response
Additional Context
No response
Originally created by @nonlinear on GitHub (May 19, 2025).
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
### Problem Description
When using Azure TTS, you can set vocie only in system, and sometimes, some voices per user (sometimes not. some voices pass per user, some crash)
### Desired Solution you'd like
It would be best if voice settings follow the suggested cascading path:
1. system
2. group
3. user
4. agent (model)
5. conversation
with later taking precedence over first.
this way we have enough granularity for different voices and languages (my group is bilingual, my users are not)
### Alternatives Considered
_No response_
### Additional Context
_No response_
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @nonlinear on GitHub (May 19, 2025).
Check Existing Issues
Problem Description
When using Azure TTS, you can set vocie only in system, and sometimes, some voices per user (sometimes not. some voices pass per user, some crash)
Desired Solution you'd like
It would be best if voice settings follow the suggested cascading path:
with later taking precedence over first.
this way we have enough granularity for different voices and languages (my group is bilingual, my users are not)
Alternatives Considered
No response
Additional Context
No response
@silentoplayz commented on GitHub (Nov 6, 2025):
Related - https://github.com/open-webui/open-webui/issues/15143