Atlassian Confluence Reviews

The business analysts use Atlassian Confluence for project documentation and use case stories. I use it primarily for dashboards and KPIs that are set for programs. Most people are comfortable using Atlassian Confluence.

This solution should have customized dashboards that could be built by the user and connect to the data and filtering mechanisms to create dashboards. It will be great for any C-level executive to monitor their KPIs rather than depend on somebody else to create them. So, the dashboards should be improved.

I have been using this solution for about ten years. It is mainly deployed on cloud.

We don't have any issues with stability. We have about 200 users of Atlassian Confluence.

We don't have any experience with technical support.

We have used Zoho, Salesforce, Bamboo and Trello. They almost all work the same because I've seen things done differently. Whether you do project management or documentation, you can choose a solution that's friendly for developers and easy to understand and pick up quickly. I would not say one is better than the other, and each solution has its abilities. Atlassian Confluence seems stable, and we don't have a problem. When dealing with compliance, some of our projects need people and PCI nest compliance, so we also have to look at tools hosted in the manner in which they comply with these standards. IBM products meet some of those requirements.

All things in Atlassian Confluence are set up on cloud. The clients have their administration teams, and they extend an account for our developers, our PAs, and our managers on these platforms. So we don't set up anything. The administration team sets up the Jira accounts on cloud. GitLab and GitHub are set up on-premises while keeping the code version internally. Setup is not a major issue because most of these things are very simple, and you have instructions.

I rate the price an eight out of ten, with ten being a good price and one being a high price. Pricing is not a problem, and you might have other products with lower rates. For bigger companies, price is not a problem because there is always a budget, and the clients fund it. However, if the price gets cheaper, it will be better for users.

I rate this solution a seven out of ten.

We use Atlassian Confluence for the documentation of the application or applications that we are billing. 

Confluence has other functions. My team uses, Confluence every day, but I am just writing some information there that is used for the entire team and is vital for the entire team. 

We are also writing various kinds of material. It is useful for the team to interact and convey information, as well as to document only the information that we use.

I only use it occasionally to check up on documentation or to compose something. 

That is what I am doing. That is the only thing my team uses, however, we also use Confluence to communicate information to the customer. 

Our Confluence is available to the customer. 

We are working on the release notes, and he can get data or the most recent version via our app.

I work with Confluence, however, I'm not sure what's lacking.

The price could be improved. I have heard that certain adjustments would be made in 2024 and that it will then be more expensive, but I don't know the specifics.

I have been using Atlassian Confluence for one year.

We are using the premium version.

Atlassian Confluence is quite stable. I have not had any problems with the stability.

Atlassian Confluence is scalable, and usable from anywhere, as well as from my phone. There are various Confluence or Jira applications, I can access the data immediately anytime I want.

We have multiple projects and half of my colleagues are using it. We have approximately 25 users in our organization.

We have plans to increase our usage. 

We intend to extend it throughout the entire organization. We want to conduct certain HR initiatives on Jira as well. 

Our HR department may also collaborate with them and Jira. I believe it is a useful tool.

I have not contacted technical support.

I use Jira to manage everything in development, and I also use it because we operate in Scrum.

I also use YouTrack.

We used Word to document everything, but that should be the last THRIVE threaded with SharePoint. But, in my opinion, the ideal way is to use all of Confluence for that.

I was not involved with the initial setup. It was done by my colleague.

We now have two or three persons setting up our administrators, and they are setting up some data and looking after the maintenance.

We have to pay licensing fees.

I would recommend this solution to others who are interested in using it.

I think that it is one of the best products on the market from my experience.

I would rate Atlassian Confluence a nine out of ten.

We use this solution for documentation purposes. It's very tightly integrated with Jira, so we handle project management with Jira and document management with Confluence.

We value the way we can tag documentation to Jira because we can cross-reference a Jira ticket to a Confluence page, and we can also add a Confluence page to a Jira ticket. The way both work together helps us to reduce the duplication of the codes, and if we need to have documentation, we describe it in Confluence and tag the page in the Jira ticket for someone to work on, which reduces the duplication of work.

On each page, we can see the different version updates that have already been done by colleagues. It's auditable, which helps us to figure out what changes have been done at what point. Documentation with an auditing capability helps us to manage the overall documentation effectively.

Nowadays, the standard for documentation for developers is mostly in Markdown, so pretty much everything we can do is in the Markdown language. The support for Confluence to import something that's in Markdown is not that great. Sometimes it's also not that great when it comes to including code snippets or similar things, so I think the couple of improvement areas would be around Markdown support and support for adding code.

As for added features, I would like to see more flexibility in the way we can design a workflow in Confluence, and maybe some templates that we can use based on the purpose of the document. 

I would also like to see more integration with other common application services. Other than draw.io, there is not much integration to other services like Lucidchart or similar services, which are helpful for reporting your documentation with drawings and architecture diagrams. Those improvements would make it a bit more user-friendly.

I have been using this solution for five years now. 

The stability partly depends upon the resources that you allocate for the solution, but it's pretty much been stable for the last couple of years that I've been working with it.

The solution is scalable and it's centrally controlled, and we have a couple of central responsibility roles for adding new users. It's helpful for us on the backend because if we want to provide access to different sets of people, some may need edit access, some may need read-only access, and we utilize those different permissions.

Other than utilizing the public documentation that is available, I haven't reached out to the support team.

I was not very involved in the setup of Confluence, but my understanding is that it was not that difficult.

Confluence might be a burden to small and medium companies, like startups, so I probably would not recommend it to them, but I would definitely recommend it for companies at the enterprise level.

I would rate this solution as an eight out of ten because we found it helpful. It's good if you are in need of long-term documentation of projects, both on the functional side and the technical side, but at the same time, it needs some improvements, like more integration to other solutions. 

We are using it for collaboration, team communication, documentation portal, and sometimes project-related content. We keep the details of the project and related documents.

It is a good collaboration tool. You share the document content and also its history through Atlassian Confluence so that you can trace its development. Also, you can add comments to the project-related items in order to track the history. It has JIRA integration in a way that you can combine the project-related dashboards into one space. This increases the communication between the teams. It is a good way to record know-how basis. You can use it as a know-how base for newcomers to be initiated more easily to the items provided.

It is easy to use and create new page content. It has macros and some stamp dates for your projects. If you would like to make something new that you have not done before, it is usually easy to find out on the internet. There is a lot of information available and the search function is excellent. You can search in different spaces and get answers for items you want to find easily.

I would like to see more macros provided by the company. Currently, those macros require extra cost. Additional free capability for those types of integration or components would be helpful in the existing license.

I have been using Atlassian Confluence for almost four years.

It is very stable. I have not seen any virus interruption or issue related to the stability.

I would say that Atlassian Confluence is scalable we have more than one thousand users.

Currently, I have not contacted technical support.

We implemented it through a third party.

We went with Atlassian Confluence because JIRA had the same type of usage.

If you need to create some teamwork spaces it is very good. I would rate Atlassian Confluence a nine out of ten.

We use Atlassian Confluence for creating different pages, and projects on it.

The most valuable feature of Atlassian Confluence it's very easy to use and there are different options. 

We have to use other applications that make Atlassian Confluence more customized for what you want. They should improve by adding the ability to make more customizations.

In a future release, they could add easy reporting. For example, EZPi can be deployed easily into 

I have used Atlassian Confluence within the last 12 months.

Atlassian Confluence is stable.

We have not had a problem scaling up Atlassian Confluence.

We have approximately 300 people using the solution in my company. We all use it on a daily basis.

I have not used the support from Atlassian Confluence. It is an easy tool to use. You do not need a lot of help, but you do need some training.

The setup of Atlassian Confluence can be difficult and other times easy because if you want to implement something, you need to have your process figured out. You have to understand exactly for what purpose you want to use something. Once you understand that, you have to know how you're going to use it. Not only immediately, but also in the future. Once you have this map, then you will be able to use a tool properly. Otherwise, you will be doing trial and error for a while.

If you want to get Atlassian Confluence up and running, the time is depending on whether you want something simple or customized. However, it can be done within a week and have everything running.

There is a license needed to use Atlassian Confluence.

We are using Atlassian Confluence because we mainly implement Atlassian tools for customers. It is helpful for us to use them to understand our customers' needs if there is a problem.

It is important to know what the client wants to use this solution for. After knowing what they want to use it for I would advise them to use it or not.

I rate Atlassian Confluence a ten out of ten.

We're using Confluence as a document management solution. Confluence includes all our documents internally in the company in regards to policies or how to document or about business requirement documents. Therefore, it's a document management system for us.

Confluence can give you the possibility of installing plugins to meet your different needs and you can cover all your needs. Most of them are free to install.

The initial setup is very easy.

Due to the fact that there are so many diverse plugins available, the solution really isn't missing any features. 

The product is considered expensive. 

In the future, I would like to be able to copy from other documents, local documents on your PC, and paste them into Confluence pages while keeping the formatting. At the moment, you can copy and paste, however, all your formatting disappears. This is one of the features that I would want. 

In terms of the feature for uploading documents, at the moment, when you want to upload documents from your local PC into Confluence, you can do it. However, when you want to make updates on your document, you need to download it from Confluence, make the changes in the document, and then upload it again. Instead of doing this, instead of downloading the document from Confluence, it's better to have the possibility to make your changes in Confluence and open the document in Confluence instead of downloading everything.

I have been using the solution for four years. It's been a while now. 

It's stable. It's a really stable product. There are no bugs or glitches. It doesn't crash or freeze. 

We have 50 people on the solution and we have no plans to increase usage. I can't, therefore, really speak to the scalability potential.

I've never had to reach out to technical support. I can't speak to how helpful or responsive they would be. 

I found the implementation process to be simple and straightforward. It's not complex at all. 

I don't handle the licensing aspects of the product. I'm unsure as to the exact costs. It's my understanding, however, that it is an expensive product. On a scale from one to five, where one is cheap and five is expensive, I'd rate it at a three and a half. 

We're a customer and an end-user.

I'm not sure which version of the solution I am using at this time. 

I'd advise new users to not be scared, to play with anything on it, or create documents and delete documents. It keeps tracking the item version. It keeps a version history so that you can revert all your changes back. Never be scared to play with Confluence.

I'd rate the solution nine out of ten. It's an easy tool to use. It gives you the possibility to integrate it with JIRA. All your documents and business documents can be connected to JIRA. With the versioning available in Confluence, history versioning, if you delete something, you can always find it. If someone changes anything in the document, you can find it from the history. It's a really good product.

It is linked with the documentation tools. SourceSafe is very quick and a more stable tool, especially for online multi-usage. Microsoft Project Service is much worse from when I was using it 10 years ago, but I don't have recent experience with it. With Atlassian Confluence, maybe the user interface is poorer, but the use of it is much more dimensional and stable.

I like the documentation. It's a central platform, and there are many things that I can do with it. I'm very pleased about it.

I can put my workspace and tasks under related documentation. I can put it heuristically on the portal, so I can see everything and the comments, and the document, the outputs, and the coding links. I can put down all the photos and see all of the portfolio in one shot, as a summary.

The user interface could be improved.

I have been using Atlassian Confluence for more than 10 years.

My personal experience is related to the R&D process, R&D funding process issues, and R&D funding projects. I'm responsible for project management, program management, or department-related IT consultancy and also software development project teams. For the last 10 years, I have also been responsible for R&D project management and all of the process management of R&D centers, so government and funding organizations' process.

We are just analyzing many programs to enhance our project management tools, agile management and agile projects.

We have been using the JIRA platform recently, and tools for documentation and some custom internal tools that departments have just developed for us.

The solution is stable.

I don't know how scalable it is, but it's enough for 10 or 20 partners of companies to use it online.

In our company, especially with the development teams, we had more than 100 people using the solution.

I used Microsoft Project Server for almost two or three years. It's very hard to concentrate or consolidate the portfolios of resources in different projects. It's very hard to manage. There was too much administration that we had to do, so we stopped using that tool. 

I think Atlassian is better because it includes all the features that a PM or a project team needs.

I would rate this solution 8 out of 10. 

I would recommend this solution to others.

I primarily used this solution for IT documentation and documenting ISMS based on ISO 27001.

With the Confluence Wiki, I implemented quite a series of successful IT and Security Documentation projects. Confluence was my preferred product when starting any collaboration project that had to produce comprehensive, centrally organized, and highly usable documentation.

I worked on several projects that implemented an ISMS, based on the ISO 27001 standard, which mandates a "documented ISMS". I introduced Confluence as the tool to be used for that documentation.

I used Confluence as the "self-hosted" server in VMs or on MiniPCs running Linux. I always added backup methods, so the HA functionality of the much more expensive "datacenter-edition" was never needed. The largest environment I worked in had 100+ active authors, but typically I would work with the 10- or 25-user license, which are both quite affordable even for small customers and where the server resources are manageable (From two to four virtual cores and 4-16GB RAM will do fine).

This solution worked fine until Atlassian decided to force everybody into the cloud.

The most mentionable improvement is that documentation with Confluence gains a much better structure. Instead of hundreds of .doc and .xls files roaming the network shares and C: drives of team members, once you get Confluence set up, spend a few hours with all designated authors to define a few guidelines on how pages should look, be interlinked, and how to generally use the tool, the productiveness of creating and improving documentation is phenomenal!

The key is to take the mentioned few hours, get everybody together and produce a "style guide", for want of a better word, about how to use Confluence. Then agree on the top-level structure of your documentation and if everybody accepts this and uses it in their work, all is fine.

My recommendation is to meet for an hour every other week with those who work the most with the tool and fine-tune said "style guide" and the structure. This will help everybody to keep being motivated and to produce the best results. Also in such meetings, ideas about add-ons can be discussed and their integration planned.

Atlassian Confluence is a very good and seasoned Wiki Solution.

First and foremost, I want to mention its top-notch usability. It has a very intuitive user interface, which every user able to manage the basic functionality of a PC will be able to work with and produce quite satisfactory results.

There is a big and responsive community to help with questions and so far, Atlassian is still doing a good job to help.

Also, there are add-ons from various sources, which can be integrated with the product quite easily and have good chances to function together as a whole, like intended.

Another thing worth mentioning is the very good import and export functionality. You can just use Copy-Paste on a website or a document and Confluence will in most cases manage to reproduce the content quite recognizably. Export not only as XML, to be able to reimport, but also, PDF and Word DOCX work quite well. They can be further improved, speaking from personal experience with PDF files, by adding a few add-ons for formatting, page heading, and such.

Oh, and last but not least the flexibility should be mentioned. If for any reason there is the need to change the structure of the contents, say to move a branch of pages from one top-level area to another, just copy them or export them and re-import them in their own area. Mostly, that works without a glitch (exceptions prove the rule) and even cross-area-links will continue to work. For more complicated restructuring, one can always use the XML-Export and load it into an XML-Editor. Of course, that´s for people who can read and understand XML structure.

Atlassian should rethink its withdrawal of the self-hosted version of the product. They only offer cloud-based service or the "datacenter-edition", which is quite expensive for small companies and private users.

I have been using and recommending Atlassian Confluence for more than four years now, and never had to regret it until the end of 2020, when they suddenly got this cloud madness.

Not only does the cloud version come nowhere near the responsiveness of the self-hosted version (which is a matter of course, as self-hosted servers are within the LAN with single-digit milliseconds of round trip time, whereas cloud-hosted servers will always have 20+ ms), but also it requires a customer to entrust their data to a third party, which is in many cases a no-go.

The only way out would be to buy the "datacenter edition" and thus spend a whole lot more money on the product. This may be what Atlassian intended in the first place and if so, shame on them.

With that, I will no longer recommend the product, as I am opposed to the cloud-first hype. Our data should be our own and we should be free to decide where we store them.

We have been using Atlassian Confluence for approximately five years.

No complaints that I know of - unless some admin shoots the underlying VM (has been heard to happen), confluence is just rock-solid. To be sure: It needs some resources, and if the VM starves of memory or CPU, performance and stability will suffer.

As I said, the largest environment i was working with at a customer has 100+ authors and I imagine plenty of pages and other content - sadly I do not know the exact figures - but we never had reason to complain in our project which only consisted of 12 people actively using Confluence. So I guess scalability should not be an issue.

Prior to Confluence, I tried working with Microsoft SharePoint. Well, there were those sad tries, and my advice is to forget it.

SharePoint may have advantages when it comes to organize and share files, but the ease and intuitive way to create structured documentation just is not there.

And as a sidenote: When working on projects we would oftentimes edit a page in confluence with three or four of us concurrently updating table entries or text segments. Very seldom have I experienced problems with allowing concurrent edits and in my mind never incorrect merging of inputs. Again, that is true for the on-premises self-hosted version, in the cloud that does not work quite as well.

And why do I point this out: Have any of you tried to edit a word document in MS Teams concurrently? ... it produces quite funny effects but in my opinion cannot be trusted, really.

The cases where I set up the server myself were straightforward and went without any glitch along the documented steps.

Up until now I only had inhouse admins implement the servers, they did it noiselessly and with satisfying results.

Erm. ROI. Hm. Can anybody please call the finance guy? ...

Well, that´s difficult now. Until the end of 2020, using a self-hosted server, have one of your IT-Admins set it up, costs $10 a year for the 10-Author license.

Nowadays? Don´t use it. The price of the on-premises data center version is too expensive.

To be honest, after being introduced to Confluence by a colleague all those years ago, I did not evaluate any other option in earnest.

Recently, I started looking at Tiki Wiki, which is a fully OpenSource alternative, but I haven´t gotten around to installing it or using it in a new project.

I would not consider alternatives but for the policy of Atlassian. Such a good product should run in every datacenter. NOT in the Clouds, though.

My advice for everybody is to flame Atlassian into re-providing the self-hosted server version!