Use case or problem
The inability to be able to completely or granularly restrict community plugins is the reason that Obsidian is being blocked at my work, which is a real shame because in really enjoying using it.
Proposed solution
The means for which, via our managed Self Service, to allow for all (or some) of the community plugins to be restricted. Perhaps some kind of SSO sign on integrated with our current SSO, and for those accounts to be managed so that community plugins are disabled.
I wish I had a better solution, this is more of post to raise this issue and to see if there are any thoughts from the community?
Current workaround (optional)
Use another app