Use case or problem
Many of our employees love Obsidian and would like to be able to use it for work but IT/Security has concerns approving it because of the inability to manage it in any capacity on endpoints. We’d like to be able to either block cloud sync entirely (not just Obsidian Sync) or manage which sync services can be used (we’re a Google org so would ideally do local-only with GDrive for backup).
Proposed solution
Introduce the ability to lock/restrict certain settings via a configuration profile deployed via MDM (Jamf, Kandji, Mosyle, etc for Mac users).
Certain things come to mind:
- disable community plugins (or, bonus points for whitelisting plugins on a case-by-case basis)
- disable cloud sync or restrict to a single provider
- restrict ability to log in / sign up
- pre-configure file recovery / snapshot behaviour
Current workaround (optional)
Documentation and forum posts mention blocking requests via sync-xx.obsidian.md, which is great to block Obsidian Sync, but is incomplete since it doesn’t prevent enabling iCloud Sync, etc.
At this time, use of Obsidian is still prohibited for our org but folks are very keen to allow it.
Related feature requests (optional)
Can’t include links but another forum post titled “How to block sync?” is relevant.