kepano @stephango.com · Aug 19 We're considering ways that IT departments can more confidently deploy Obsidian to employees and students. What do you think about this approach?
37 likes 4 replies
Replies
Not sure I have a use-case for this in my deployment, but if I could upload policy.json to something on your side that would correlate it with my license key and it would be downloaded and applied automatically that would be much nicer. Doesn't need to be a fancy interface, just upload (&validate).
Here’s a framing that may help you with this. Imagine I’m an employee and want to use obsidian in a way that doesn’t comply with the company policy. Can IT prevent me from doing that using this system?
The difficulty with policies like this is that they have to be deployable in a way that the user of the machine can’t just launch obsidian without it or can’t easily modify it. This unfortunately means things like GPO on windows or system profiles in MacOS.
I understand the IT perspective here, but disabling community plugins really nerfs the product. What kind of sandboxing might be possible instead?