
One of the biggest reasons we chose Document360 was for its ability to make your knowledge base private. Because of the type of technical content we were curating in the knowledge base, we needed to be sure that it stayed internal. Once you make your Document360 knowledge base private, users must log in with an account in order to access any of the articles. For most of the solutions, we looked at while vetting, this just wasn't an option, but Document360 made it as easy as flipping a switch in settings and then adding readers.
Another reason we chose Document360 was because of how flexible the permission sets were. We could configure a custom role for readers that gave them access to a pre-defined set of categories. This was helpful for teams using the knowledge base see only what they needed to see instead of having to wade through everything that wasn't relevant to them.
We also really wanted something with a solid analytics suite to help our content curation funnel. We thought that the internal knowledge base data could help us see what our internal solutions engineers were searching for and engaging with the most that we could and Document360 let us do exactly that. Review collected by and hosted on G2.com.
As someone who works mainly on Google docs, Github, and Figma, I was disappointed with the lack of collaboration tools. Though there are a few nods in the direction of team tools, the processes felt lacking and forced us to lean on a lot of external comms, which sometimes disrupted workflows.
There were also smaller UX/UI details in the product that felt awkward to use. However, the product and customer support teams at Document360 were always incredibly quick to respond to questions, and bug and issue tickets. Plus they were always pushing improvements into the product and keeping my team up-to-date about what those were.
And finally. there were multiple smaller features missing that, when combined, disappointed the team. For example, the article tagging functionality wasn't very powerful, though the search capability more often than not made up for it, there were multiple cases where my team needed a more powerful tagging function.
Overall, we were really happy with Document360, and I think a big part of that was because we made a list of what we needed before we started evaluating platforms. I always recommend doing this to make sure the platform you end up with is one that'll truly solve your biggest pain points as a company or team. Review collected by and hosted on G2.com.

At G2, we prefer fresh reviews and we like to follow up with reviewers. They may not have updated their review text, but have updated their review.
Validated through LinkedIn
Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.





