You can deactivate the plugins button in the editor’s initialization config in the “customization” section, here is the link from the Onlyoffice API Website ONLYOFFICE Api Documentation - Config
NB! This solution is available for server-based Document Server. It is not available for cloud solutions.
I don’t understand how the above solution disables plugin manager for all users? Could please share an example on how we can disable plugin manager for all users?
Hello @nivesh
If you don’t mind, I will join this thread.
The mentioned link is useful in case of your own integration (you have your own storage and you integrated Document server (DS) with it). In case of using ready-to-go connector apps (https://www.onlyoffice.com/all-connectors.aspx) you can’t perform such actions, because you don’t have direct access to customization section. The connector apps are provided ‘as is’.
Nevertheless, probably there’s a workaround solution. The plugin manager is a plugin too. You can perform the same actions for it as for other plugins. Please check out this title: Adding new plugins to server editors - ONLYOFFICE
It describes manual plugin installation on the server.
the point is that you can remove the plugin manager folder and restart all services to disable this feature for all users.
Here’s my test where I removed this folder (and Macro folder too):
First I removed marketplace and then I did not restart service, and was seeing broken functionality. I thought there was some other way to do it, but in the end I forgot to restart. Silly me.
After reading your comment it struck me. Thanks for assisting!
Sorry ! I need a clarification by setting the “plugins” parameter to false, I only hide\disable the “plugins manager” button and I leave the ability to the users to use the already installed plugins ?
Hello @4535992
If the plugin tab is hidden: Customization, a user won’t be able to start the plugin from the editor interface. However, if your plugin has been added to autostart it should work anyway.
If I misunderstood your question, please clarify it.
Yes thank you ! I’ll try this solution. I would have preferred to be able to set it via the rest api, to have more control for each individual plugin, but your solution is acceptable for my use case, since I have control over the Document Server I can act accordingly.