0đź‘Ť
Technically NO!!!!
Well as you’ve mentioned that you’ve already made your first CEP panel and it’s also working fine, I can assume you’ve gone through the method of loading test panels via PlayerDebugMode 1.
So here is the catch. Photoshop only recognises 2 type of extensions called Signed and Unsigned. So when you create a new panel in your local appdata/library – CEP – extensions folder, You creates a unsigned panel and photoshop considers that as test/development panel. When you finish your panel and then make it distributable by either making installable package like .exe or .dmg or .zxp, It gets signed and photoshop considers them as signed plugins and will install it automatically on their legit path.
if I were able to host it on one of the company’s webservers then anyone in the company could access it.
The only way I could manage was sharing latest .zxp to my work server where my other designer mates copied and installed them into their system. That’s what you can do if you really want to share but you can’t assign some global path to extensions because photoshop won’t allow you to do it. Regards!