Is the Office plugin aimed mostly at users who lack an integrated CMS?
And relatedly, are most customers authoring complex documents that the Jive Rich Text Editor can't handle in their integrated CMSs rather than the Jive Office plugin?
Here's the background for this question:
at National Instruments, we learned we're something of a corner-case in that we don't integrate with another CMS like SharePoint. We currently use Jive as a defacto CMS.
Our best practice is to use Jive for Office to create documents that are more complex than the Jive rich text editor can handle, but now we're wondering if we're also a corner-case when it comes to that 'best practice.'