Confluence
AtlassianReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
4,258 reviews
from
External reviews are not included in the AWS star rating for the product.
Solid Tool, But Naming Limitations
What do you like best about the product?
I like the integration with Jira because it allows me to automate the monthly report directly to Confluence based on Jira tickets. The analytics for pages are helpful as I can see if the page is popular or not. Confluence is also much more solid and user-friendly compared to Mediawiki, which we used before.
What do you dislike about the product?
I can't reuse the name for the page. For example, when I have Service 1 and Service 2 pages and try to create the page 'Intro' in the second nested page (Service 2 -> Intro) I got an error that 'Page already exists', so it requires a more complicated naming for pages.
What problems is the product solving and how is that benefiting you?
I use Confluence to keep internal documentation and provide IT support articles. It helps me organize documentation and manage the knowledge base.
Confluence: The Single Source of Truth with Room for Improved Connectivity
What do you like best about the product?
I like that Confluence is considered our company's single source of truth. It holds all of our company's data history, and the more we use it, the more valuable it becomes for decisions, processes, and knowledge. As a Product Manager, I find Confluence most valuable because it's where decisions, PRDs, and OKRs live permanently next to our work, which helps ensure there is always an answer to 'why we build this?'
What do you dislike about the product?
It lacks a true knowledge graph. Pages are in isolation instead of connecting into a living compounding web of linked knowledge.
What problems is the product solving and how is that benefiting you?
Confluence serves as our company's wiki, providing a single source of truth for decisions, processes, and knowledge, making it invaluable for project management.
Easy File Creation and Cataloging Across Systems - Customers and Company Benefit
What do you like best about the product?
I like the ability to create a file and then catalogue it with other systems, like Zendesk, or our knowledge base website.
What do you dislike about the product?
The design features lack and it is not intuitive to make an article with many options.
What problems is the product solving and how is that benefiting you?
It is providing a central online database for internal needs with the company.
One-Stop Team Documentation Hub
What do you like best about the product?
It supports writing by multiple team members and serves as a one-stop place for documentation.
What do you dislike about the product?
Attaching files or screenshots to the page isn’t well organized, and it could be structured more clearly.
What problems is the product solving and how is that benefiting you?
Documenting is easy, and it’s an everyday go-to place for me.
The Most Robust Documentation Index
What do you like best about the product?
All the features that allow you to build a segmented view and proper documentation index.
What do you dislike about the product?
Lacks some integrations with third parties, but I appreciate this might be very niche and specific for my use cases.
What problems is the product solving and how is that benefiting you?
Confluence is our go-to for process documentation and we rely on it to capture all our processes. What it does best for my team is its connections to Trello and Jira and how easy it is to set-up automations across all those platforms.
"Great for team collaboration"
What do you like best about the product?
Confluence makes it easy to create and share documentations within the team. I use it every day for writing minutes of meetings, maintaining proper documentations. The interface is simple, and editing them is really helpful.
What do you dislike about the product?
Sometimes formatting is little tricky, especially while working with large pages. And the other thing is searching results are inconsistent if the content is not well structured.
What problems is the product solving and how is that benefiting you?
It helps all the team knowledge put in one place, so it is really easier to access information and collaborate. It reduces dependency on scattered documents and improves to keep everything organized.
Structured, Searchable Wiki with Powerful Real-Time Collaboration and Jira Integration
What do you like best about the product?
It helps move teams away from scattered documents and into a structured, searchable wiki. The real-time co-editing is powerful, and the deep integration with Jira makes it indispensable for technical teams by keeping requirements and project updates automatically in sync.
What do you dislike about the product?
My main frustration with Confluence is its clunky search and navigation; as workspaces grow, finding specific pages can be difficult and time-consuming. The editor’s formatting quirks also persist—tables and layouts can break unexpectedly, especially when moving content between apps.
What problems is the product solving and how is that benefiting you?
Confluence helps solve the problem of “knowledge silos” by offering a transparent, shared space where documentation is accessible to everyone, rather than being trapped in private folders or buried in email threads.
A reliable knowledge backbone for engineering teams
What do you like best about the product?
As a Technical Lead, what I like most about Confluence is how naturally it fits into our day-to-day engineering workflow. It has become the single source of truth for my team - architecture decisions, sprint retros, onboarding guides, deployment runbooks, API contracts - everything lives in one searchable place.
The Jira integration is a huge win. Linking a Jira ticket to a Confluence page (and vice versa) keeps requirements, tech specs, and tickets tied together so nothing slips through the cracks. The new editor is smooth, the page templates save real time, and the macros (Table of Contents, Code Block, Info panels, Page Tree, Excerpt) are exactly what an engineering team needs without going overboard. Real-time co-editing has cut down a lot of the back-and-forth that used to happen over email and Slack.
Space and page-level permissions are flexible enough to share docs with external stakeholders without exposing internal-only content, and the Marketplace adds genuine power when you need it (Draw.io, Scroll Viewport, Comala, etc.).
The Jira integration is a huge win. Linking a Jira ticket to a Confluence page (and vice versa) keeps requirements, tech specs, and tickets tied together so nothing slips through the cracks. The new editor is smooth, the page templates save real time, and the macros (Table of Contents, Code Block, Info panels, Page Tree, Excerpt) are exactly what an engineering team needs without going overboard. Real-time co-editing has cut down a lot of the back-and-forth that used to happen over email and Slack.
Space and page-level permissions are flexible enough to share docs with external stakeholders without exposing internal-only content, and the Marketplace adds genuine power when you need it (Draw.io, Scroll Viewport, Comala, etc.).
What do you dislike about the product?
Performance can dip when a space gets really large or pages have heavy attachments — loading older pages with lots of embedded content is sometimes slow. Search has improved a lot, but it still surfaces outdated or duplicate pages too easily, so the team has to stay disciplined with page naming and labels to keep things clean.
The migration from Server/Data Center to Cloud was not the smoothest journey for us — some macros and Marketplace add-ons behaved differently after the move, which forced a few rounds of cleanup. Pricing also scales quickly once you start adding Premium features and third-party apps from the Marketplace.
Lastly, the analytics around page usage are okay but not great — it would be nice to have richer insights out of the box on which pages are stale or unused so we can prune them more confidently.
The migration from Server/Data Center to Cloud was not the smoothest journey for us — some macros and Marketplace add-ons behaved differently after the move, which forced a few rounds of cleanup. Pricing also scales quickly once you start adding Premium features and third-party apps from the Marketplace.
Lastly, the analytics around page usage are okay but not great — it would be nice to have richer insights out of the box on which pages are stale or unused so we can prune them more confidently.
What problems is the product solving and how is that benefiting you?
Confluence solves the classic problem of scattered knowledge across an engineering org. Before standardising on it, our specs lived in Word docs, decisions were buried in email threads, and onboarding relied heavily on tribal knowledge. Now everything — coding standards, environment setup, architecture diagrams, release notes, runbooks — sits in one searchable place.
The biggest measurable benefits for us:
- New developer onboarding has dropped from roughly 3-4 weeks of hand-holding to about a week, because devs can self-serve through our 'Engineering Onboarding' space.
- Sprint planning and retros are faster because we link Jira tickets straight into the meeting page.
- Audit and compliance reviews are much smoother since we can point to a documented trail of architectural decisions, change logs, and approvals.
- Cross-team handoffs (dev to QA, QA to release) have far fewer gaps because the spec, test plan, and release notes all sit on one parent page.
For me as a Technical Lead, the real benefit is that I can delegate confidently. If a process is well-documented in Confluence, I'm no longer the bottleneck — the team can unblock themselves.
The biggest measurable benefits for us:
- New developer onboarding has dropped from roughly 3-4 weeks of hand-holding to about a week, because devs can self-serve through our 'Engineering Onboarding' space.
- Sprint planning and retros are faster because we link Jira tickets straight into the meeting page.
- Audit and compliance reviews are much smoother since we can point to a documented trail of architectural decisions, change logs, and approvals.
- Cross-team handoffs (dev to QA, QA to release) have far fewer gaps because the spec, test plan, and release notes all sit on one parent page.
For me as a Technical Lead, the real benefit is that I can delegate confidently. If a process is well-documented in Confluence, I'm no longer the bottleneck — the team can unblock themselves.
Effortless Document Management with Confluence
What do you like best about the product?
I like that Confluence is very practical and easy to use. It's very clear and organized, offering folders and subfolders, which helps in keeping everything organized. I appreciate the variety it provides with different types of text, organization styles, titles, and typographies. The addition of emojis makes the information dynamic and engaging. I find it straightforward as every button is direct and intuitive, making finding information easy. Additionally, Confluence provides videos online, which aids in understanding and using it easily.
What do you dislike about the product?
I think that maybe sometimes articles get too old. And information might not be very accurate to what is going on in any company or any situation right now. So it would be very good to have maybe a new notification or be informed constantly of how long articles have been there. Like, 'this article has been here for two years. Do you want to update it? Do you wanna check it?' Because that's the main failure that I think can happen. We can forget about articles that are too old, and they start becoming trash because they are not useful anymore.
What problems is the product solving and how is that benefiting you?
I am able to find information about work or issues and track articles on new projects with Confluence.
Centralized Knowledge Sharing with Confluence
What do you like best about the product?
I really like Confluence's ability to create, organize, and share documents in a structured and collaborative way. It's awesome how it acts as a single source of truth for all teams in our organization. This really solves the problem of scattered documentation and knowledge silos, ultimately benefiting us by improving centralized knowledge sharing, enhancing collaboration, helping with onboarding, and reducing dependency on individuals. Since all our documentation is hosted on Confluence, it serves as a really good data source for training our LLMs.
What do you dislike about the product?
Search can sometimes be inconsistent in managing large spaces, and pages can become cluttered. Formatting can also feel restrictive compared to more modern editors. Integrating Confluence with documentation as code is more of a hassle due to its changing APIs.
What problems is the product solving and how is that benefiting you?
I use Confluence to streamline documentation as a single source of truth, solving scattered knowledge and silos. It enhances centralized sharing, collaboration, onboarding, and reduces dependency on individuals, also serving as a data source for training LLMs.
showing 1 - 10