I manage a large engineering team and we are considering using Obsidian as a replacement for our current wiki. I firmly believe that reducing the friction involved in updating our wiki will improve both the quality and quantity of our internal documentation, and Obsidian makes the process nearly 100% friction-free. I have something setup that is functional, butit is hacky and imperfect and I’m unlikely to move forward with it. For example, I am using Perlite to provide a web UI for reading the wiki, but it is not aware of plugins and does not render them properly, causing divergence between the desktop application and an online view.
I believe a team-oriented product is a major opportunity for your team and urge you to consider it if you are not doing so already. Getting it into a team environment would result in rapid internal spread and a large number of business user licenses. And if you ARE already considering this, please share some info so I can avoid wasting time looking elsewhere! Conversely, if your position is “we will never do this” that would also be helpful to know.
Some specific elements that are key to my uses (and I am certain are key to those of many other customers based upon searching your forum) are:
- Keep all data on-premises - no cloud component unless we can host it ourselves.
- Sync across multiple users without requiring them to have knowledge of git.
- Maintain a sync’ed, on-premises static version of the website that properly renders plugins in addition to core obsidian/markdown formatting.
- Prevent non-“admins” from making changes to the vault configuration (plugins, etc) while still allowing them to maintain some local preferences, storage of window state, etc. (perhaps allow user prefs to sit above managed vault prefs in a cascading way?)
This is in line with many, many other requests, e.g.:
- Collaborating in Obsidian, multiple users, teamwork - Help - Obsidian Forum
- Team Documentation Sharing in Obsidian - Resolved help - Obsidian Forum
- Permissions for Obsidian Sync with Teams - Feature archive - Obsidian Forum
- Obsidian for Hackish Team KM - Share & showcase - Obsidian Forum
- Obsidian for RnD team - creating a collective brain! - Help - Obsidian Forum
- Enterprisey private publishing - Feature requests - Obsidian Forum
Thanks for considering this.
edit: as further evidence of a desire for this, I was initially prevented from posting this because the title “Obsidian for Teams” had already been used