There was a video posted recently about Vault Office, so I thought I would have an article about API licensing for Vault Office. And while I’m at it, I may as well go over all the licensing rules for Vault 2015. It’s not my favorite topic either, but it has to be done. I’ll try to go quickly.
In case you are not aware, Vault Office is a separate license type designed for non-CAD users. The idea is simple: The Office license is cheaper than a standard Vault license, but the functionality is limited. There are specialized clients which consume Vault Office licenses instead of regular Vault Workgroup or Professional licenses.
Don’t confuse Vault Office with the Vault plug-in for Microsoft Office. They are different things. Actually, there is an MS Office plug-in which consumes a normal Vault license and an MS Office plug-in which consumes a Vault Office license. So I guess it is kind of confusing.
Regarding API development, you cannot develop your own apps against a Vault Office license. Currently, none of the Vault Office clients support plug-ins. If you write your own standalone client, it will log in using a standard Vault license.
Here is a run down of the different licensing rules by product:
| Regular license | Read only login | Vault Office license | |
| Vault Basic | Development allowed. End user must have a qualifying CAD license. | Development allowed. End user must have a qualifying CAD license. | N/A |
| Vault Workgroup and Professional | Development allowed. Vault Server manages the license. | Development allowed. No license is consumed. | Development not allowed. |
Leave a Reply to Doug RedmondCancel reply