I use the solution in my company for documentation purposes. Most of our company's release notes are present on Atlassian Confluence for client review and for the processes we use in our organization. All the details about the new features of the upcoming releases and all the stuff related to the company policies, like employee engagement and everything else that should be documented, are present in Atlassian Confluence. I use Atlassian Confluence for document-controlling purposes.
The most valuable feature of the solution stems from its document-controlling feature. In Atlassian Confluence, controlled documents cannot be edited by anyone else.
I would say that Atlassian Confluence's old versions consume too much memory, making it an area where optimization is required from an improvement perspective.
There are some issues with the templates in Atlassian Confluence. In our company, when some team members try to edit the templates in the product, they get stuck. There were complaints about the templates being less refined. When the components increase in the template, the product's users in our company get stuck, making it in an area where improvements are required.
It would be great if Atlassian Confluence could integrate with Microsoft Teams since it would allow our company to use just one tool instead of two.
The quality of the technical support needs improvement.
I have been using Atlassian Confluence since 2020. I am a user of the tool.
Stability-wise, I rate the solution as eight out of ten due to the high memory consumption of the product, specifically its IaaS and not the SaaS version.
Scalability-wise, I rate the solution a seven out of ten.
The tool is suitable for all types of companies. Many enterprise-level companies use Atlassian Confluence because they have lengthy processes that run for years. The aforementioned area prompts enterprises to choose Atlassian Confluence for their documentation.
Even though my company is able to open tickets with the tool's support team, we haven't gotten all of our issues resolved. I rate the technical support a six out of ten.
With Atlassian Confluence, there are two types of setup processes available. My company uses the on-premises version of the product. My company also uses its own infrastructure to host Atlassian Confluence. Our company also uses the SaaS version of the product. In general, both versions of the product are being used for different projects. I think the SaaS version of the product does great in terms of memory and everything. The on-premises version of the product is a bit old but is more secure and preferred by our clients since they feel that their documents are safe in an on-premises setup.
In terms of the tool's ability to ensure better productivity of the team in our company, I would say that the old versions of Atlassian Confluence consume too much memory while also using Java libraries.
I don't think that the product ensures better communication between my team members.
It is secure to share documents through Atlassian Confluence. Documents shared via Atlassian Confluence cannot be edited or modified until and unless they are reviewed by the specific person for whom they are meant.
Though not to a large extent, my company has used Atlassian Confluence's integration capabilities. In our company, there were a few products for which we had to review the links with the clients and review the documentation, which was not much. I think Atlassian Confluence has much more to offer, but my company hasn't explored it that much.
If I consider large volumes of pages and space, I would say that the tool works fine with large virtual volumes of pages and spaces, but not all the time.
I recommend the product to those who plan to use it.
I rate the tool an eight out of ten.