Microsoft's SharePoint is an Intranet solution that enables users to share and manage content, knowledge, and applications to empower teamwork, quickly find information, and collaborate across the organization.
$5
Per User Per Month
Paligo
Score 9.9 out of 10
N/A
Paligo, headquartered in Stockholm, offers their component content management system (CCMS), supporting the creation and publishing of technical documentation and help systems.
We were using our own, custom management scheme - relying on tools like SharePoint to store and collaboratively edit. But we were lacking the reusability feature and content control features that Paligo provides.
Very user friendly. If you're already using M365 products it offers great integration! If you're using Azure AD it offers SSO for IAM and integrates nicely with Azure AD Groups which can then be used for Access management. As our IT / Azure Administrator, I particularly like the "sharing link" options where you can send a link with an expiration date and not have to remember to remove the link / access after a project / business case scenario is over.
Paligo is particularly well suited for developing similar document sets for multiple products or product lines. It is not a page layout application, so don't expect the same capabilities as popular applications for graphics-heavy documentation. With some up-front time developing good layouts, however, Paligo does manage to create very usable PDF output for customer-facing documents.
The review mode is super convenient. Comparing a snapshot of the previous versions with the current one clearly outlines the respective changes and reduces the necessary content to review tremendously.
The option to reuse text fragments is another handy feature. Text fragments will be updated whenever the original text fragment is altered is also extremely helpful.
Managing a content's structure was never easier. An intuitive drag & drop functionality allows you to design your document's structure however you like.
You can also fork content, in addition to reuse text fragments. This is another helpful option that no longer requires you to create repetetive chapters over and over.
The amount of CSS/JS required to customize a site's appearance can be cumbersome
Product documentation can be lacking, specifically with integrations; in some cases, support offered no real help when trying to solve a problem with an integrated service
Some features require extensive development experience to use, which can sometimes be an obstacle to less-experienced team members
It's integral to our business. It's already included with most of the Office 365 licensing we buy, so the cost is effectively zero. It stores our files, it is the foundation for custom applications, and Microsoft only continues to enhance its functionality and its connections to other Microsoft tools. SharePoint just keeps getting better and better.
No usability issues reported. Individual teams also have allocated areas which replace legacy shared drives on local LANs. Access to Sharepoint resources is fully integrated with corporate Active Directory with additional two-factor authentication required for administrative users. Users have access to Microsoft Services Hub which allows you to create, manage, and track support requests while staying current on Microsoft technologies with access to select self-paced learning paths
Generally, I'm very happy with Paligo and the productivity gains that I get from using it. There are a few arbitrary limitations on structure, and when applying conditional formatting, that I don't really understand. Unlinking / editing reused text uses this broadly inscrutible colour-coding that I just hate. It would be nice to double-click a component, make edits, then respond to a popup asking if I want to confirm the edit for all linked content, or unlink this instance. Likewise converting from an informal topic insertion to duplicates of its raw contents.
All the support requests I've submitted have been resolved in one way or another. Sometimes it takes some back and forth, which is to be expected. This is where being on a different continent becomes a drawback. Since we became Enterprise users, we've also had an additional level of help and support from a dedicated account manager in the US, and the resolutions seem to come more quickly
The face to face training I received was on SharePoint Administration. It was rushed as there was a lot of information to cover and the application of the labs weren't that great either. I like to be able to relate what I am learning to what I am currently doing.
I like to learn at my own pace and online training allows for that. Additionally, you can skip through pieces of content that you already know or are already comfortable with. Microsoft actually offers great videos on their website for basic fundamental SharePoint Training. I have used these training videos in some of my own training sessions with end users.
The reasons for selecting MS SharePoint are: SharePoint provides ease of use and web design assistance and support SharePoint helps you schedule your content for publishing. enables users to share documents with external parties and offers a better internal structure of the content and better indexing and searching capabilities.
We moved from Flare to Paligo. One of the main reasons was the fact that Paligo is a cloud product. Collaboration with anyone outside of our team was more difficult with Flare. Also, maintaining a server for Flare content was going to become an issue, and overall I felt the Flare desktop product was prone to errors and issues. The flexibility of assigning Paligo licenses was a huge factor, as was the stability of the cloud platform.
Increased collaboration - MS Sharepoint has increased knowledge share and collaboration between departments. This saves time and energy because of its efficient and effective communication
Increased document security - MS Sharepoint has increased our document security so we're safer knowing that our documents are security and access controlled appropriately. We are less prone to get in trouble by our customers due to the security provided by MS Sharepoint
Negative Impact Compared to other software - Not sure if the MS Sharepoint's main functionalities could've been met with other tools we currently have
I am not involved in the financial decisions for my company regarding Paligo; the decision to migrate our content to this environment predates my hiring. However, I know that the migration effort from WordPress to Paligo was an initially heavy lift, but any content migration effort would be. I believe that ultimately, getting our content out of WordPress was a positive move, and I look forward to seeing what Paligo will help us accomplish in the future. Sorry, no hard numbers from me. :)
