Lock down Files/Terminal

[ctg49]

This might already be a thing, but I couldn't find it in documentation/anywhere obvious. I'd like a way to lock down the files/console part of OT when added into open-webui. We're leveraging this for shared user API access and necessarily, the account performing the API lookups has read access to the keys. In a shared environment, that's not ideal. If it were possible to have OT running, but without direct access to read the keys, that'd be a lot better for multi-user usage.

[Classic298]

Access.... To what keys exactly? What? ... I read it again... And ... What?

[Classic298]

if anything about the docs here: https://docs.openwebui.com/features/extensibility/ is ambiguous to you, please let me know, happy to improve it. but personally i think the difference is relatively clear

[Classic298]

@ctg49 the instance wide option should already be here as well (see admin panel > settings > models > settings on the top right: these all apply to ALL Models instance wide. this is also documented)

[ctg49]

I'm seeing those settings in the model settings, (perfect for system-wide prompt!) but unless I'm blind, there's no option to hit system-wide attachments of knowledge bases, custom tools, etc. That in a different spot?

[Classic298]

hmmm yeah that one doesnt exist yet for instance-wide model knowledge

but the rest i hope at least helps

[ctg49]

It does. And honestly, thank you. Somewhere between my misunderstandings/failure to fully understand the documentation, and reliance on the LLM to 'figure it out' resulted in me having a very functional but not-ideal setup, this is far better. You didn't need to be this patient with me but I'm glad you were.

Here's to fully automated sysadmin work!