Atlassian Confluence Reviews

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!

We use Atlassian Confluence for project documentation. It works as a repository of documents. We can write documents, including tutorial information, technical manuals, and other company procedures.

The product has a valuable feature for quick verification of documents.

There could be an option to collaborate with other users while editing the documents. We have to wait for other users to edit and release the document to make further changes or updates.

We have been using Atlassian Confluence for one and a half years.

The product is very stable. I rate its stability a ten out of ten.

We have 125 Atlassian Confluence users in our organization. We use the tool every day. I rate its scalability a seven out of ten. The lack of a collaboration feature affects the scalability level.

I have used SharePoint before.

I rate Atlassian Confluence a six out of ten. I advise others to look for other tools if they want a feature for collaboration.

I use Confluence to organize my data. In the case of Confluence, I use it to handle various transactions in the bank. We have multiple channels in the bank. The bank I work for is one of the largest in Brazil.

I manage five different channels in the bank. I receive messages, put them in a pipeline, and then process the data in various ways. After that, I distribute the processed data through different channels. I also have other tasks related to client management.

For example, I have to connect my legacy systems with new solutions, and Confluence helps me with that. I use different connectors to transfer data from legacy systems to new core solutions.

For me, the most valuable feature is its high performance. It's crucial for us in the bank, as we handle a massive number of transactions every day. It's very efficient and saves a lot of time.

Additionally, the ease of use and the availability of different connectors are important. They help me connect with various databases and facilitate integrations with different solutions.

I have a couple of different pipelines that I work with. However, I'd like to see them displayed differently on the same dashboard. So, I would like to have a unified dashboard to view the different pipelines.

In my case, the governance aspect is the most important. It doesn't work well with a huge company, and it's not as effective as it could be for software developers.

Moreover, there is an area of improvement in the governance functionality within Confluence, especially for large companies like ours, to have a more sophisticated governance solution associated with Confluence.

I have been using it for six months. I am using both Confluence SaaS solutions. I have access to various versions of the software.

It is very stable solution. 

I would rate the scalability high. 

The customer service and support team was not so good. In Brazil, the technical support for Confluence is not very good because the team is small. We are still trying to improve, but there are a lot of open permissions on the internet. However, Confluence is a very important tool and has good features. So, it's important to have better support because it can make it easier for users to work with Confluence. Currently, it's not as close as other brands, which makes it hard to propose new ideas or get prompt assistance. There are a lot of opportunities to make it more user-friendly.

The initial setup was complex.

In my opinion, it's worth the investment. I saw an ROI in a short time.

The pricing is good. In my opinion, there are no better alternatives.

I would definitely recommend using this solution. Overall, I would rate the solution a ten out of ten.

We provide this solution to customers and also use it in our company. It's often used as an intranet and then for collaboration or communication. It enables you to have project spaces or team internal spaces and different types of documentation. We are platinum partners with Atlassian and I'm a principal consultant. 

I think the structuring of information into spaces and the search functionality are really powerful features. The solution is user-friendly and anyone can comment or write documentation related to a customer's project. The main value is that Confluence makes communication easier. It has a very unique feature in that it has a marketplace of apps which means you can extend Confluence by installing apps into it and make it work differently.

I'd like to see easier integration.

I've been using this solution for 10 years. 

The stability is very good. 

The solution is scalable, we have around 600 users. We'll probably expand usage to new areas. 

Customer support has deteriorated because the company has grown so much. They can't provide the same level of service. We provide consultancy services so it works to our benefit.

Positive

I've also used Sharepoint and in comparing the two, Confluence makes communication much easier. SharePoint is more difficult to use and a complex solution.

The initial setup requires some planning. To get Confluence up and running took a day but it took close to a year before everyone felt comfortable with the solution. Following the initial setup, it required user management and security settings. And then build the data structure or space structure and install plugins. Following that there is a training process for users. We deployed internally because we have experience providing that type of consultancy to other companies. Half of the companies we deploy to use some external help and half do it by themselves. It takes longer if you do it without assistance.

Maintenance requires less than one man month per year because you don't have to install updates. But still there's some maintenance, cleaning up data and fixing the permits and things like that.

The ROI is both in terms of time as well as financial. 

Confluence used to be really affordable but they've been increasing their prices. It's not super expensive but more expensive than it used to be. We pay an annual licensing fee which includes some essential plugins. 

Spend some time planning the structure and how you're going to use Confluence and provide some initial training. It makes the deployment easier.

I rate this solution nine out of 10.

My primary use case is for documentation.

The most valuable feature is the accessibility from different sites for different colleagues and the search option. 

I would like to see the text editor upgraded from its current limited abilities.

I have been using Atlassian Confluence for the past ten years.

When it comes to stability I have not seen the solution go down in the past couple of years so it is good.

When it comes to scalability you can add as many documents and sites as you like. We currently have around two thousand users 

I can recommend Atlassian Confluence for any company that requires document management and documenting ongoing processes, Of course, it is not a very intuitive or very comprehensive management tool because you cannot track the requirement object changes with it, but you can use it for general documentation purposes. I would rate Atlassian Confluence an eight out of ten.

Our company is using Atlassian Confluence for all work related to documentation, calendars, notes, organization of processes, and workflows.

For example, if we have a new process, or we are updating a current process, we use Confluence Project and share it across the entire team. If we need to calendar a vacation, or an event, we use Confluence. The solution is also used to share best practices and release notes relating to the product.

The solution is valuable based on our company policy. It is easy to use. The interface is basic, with everything linkable. We also use JIRA, so Confluence can link any ticket or task from JIRA to be included on the Confluence page.

The way Atlassian Confluence handles tickets could be improved. This process should be easier, more flexible and more useable, such as the ease of creating a table. 

I have been working with Atlassian Confluence for two years.

The product is stable. 

Atlassian Confluence is a scalable tool. We use the solution across lots of teams, not only on-premise but through remote access. We currently have approximately 100 users in the organization. 

Anytime we need to update or add something, we reach out to our administration team. That team can contact the maintenance team for any attention required to fix and close the ticket in a short period of time.

The initial setup of Atlassian Confluence is straightforward. 

I would recommend Atlassian Confluence to anyone considering the implementation of the solution into their organization.

Overall, I would rate Confluence a seven out of 10.

Our different business units use it for different purposes. We have analysts, developers, DevOps team members, project managers and product managers using it. All these roles use it for artifacts for the jobs they need to do. 

The best feature is the automatic tagging of information in documents. The automatic algorithm highlights irrelevant information that conflict with the actual documents.

You can add different tables and text and format it for different purposes. The integration with JIRA and other tools is quite useful. The different plugins for different purposes are also great. 

The flexibility and simplicity of this solution could be improved. We would also like the ability to add plugins. 

I have used this solution for eight years.

This is a stable solution. We have not experienced any cases of instability.

You need extra time and money to make it useful for a large number of people.

The initial setup is rather straightforward. 

If you are looking for a simple solution to generate documents and artifacts in one place and a simple tool for rules of privacy of this information, I would recommend Confluence. 

If you have a large number of employees or complex processes, you need to have extra time and money to develop tools for Confluence. It doesn't have a pre-built solution for difficult cases for cross functional teams and connections of subjects.

I would rate this solution a seven out of ten. Confluence is a good collaborative tool for work with artifacts of documents, but it has room for improvement. That's why I would rate it a seven and not eight or nine.