Confluence logo

    Confluence

    Sold by
    Create, organize, and share work to connect scattered information into a single source of truth.

    Ratings and reviews

    4.2
    4320 ratings
    1 AWS reviews
    |
    4319 external reviews
    External reviews are from G2  and PeerSpot .

    Filters

    Review type

    AWS Marketplace reviews
    External reviews
    Reviews (4320)
    Pranav S.

    Solid knowledge base, search and clutter still get in the way

    Reviewed on Nov 13, 2026
    Review provided by G2
    What do you like best about the product?
    What I like most about Confluence is how it turns tribal knowledge into something the whole team can actually find and use. I treat it as a home base for playbooks, meeting notes, and the “why we decided this” context behind decisions, so when someone is new or I’m switching contexts, I’m not starting from zero. It’s not perfect, but when people keep pages up to date, it cuts down on a ton of back-and-forth and makes it much easier to stay aligned.
    What do you dislike about the product?
    I’d flag a few practical gaps. First, search relevance: even with exact titles, it still surfaces archived or unrelated pages, so people stop trusting the search results. Second, content hygiene: there’s no strong built-in “this is stale” signal, so documentation just piles up over time and navigation gets messy. Third, the editing experience. Especially with tables and large pages. It can feel clunky compared to spreadsheets or newer wiki tools. Exports for client-ready PDFs or Word docs are also hit-or-miss. None of this makes Confluence unusable, but these are the friction points that keep showing up again and again in how teams actually use it.
    What problems is the product solving and how is that benefiting you?
    Confluence solves the problem of knowledge living in too many places. Before it, answers were scattered across Slack threads, email chains, and people's heads. That meant repeated questions, inconsistent processes, and a lot of time spent hunting for the latest version of something.

    It also gives teams a shared place for decisions, playbooks, and meeting notes, so context does not disappear when someone leaves a project or a chat scrolls away.

    For me, the benefit is speed and less rework. I can link one page instead of rewriting the same explanation, onboard or hand off work with less back and forth, and trust that people are looking at the same source. When pages stay current, I spend more time doing the work and less time chasing down who said what.
    Jerin L.

    Rovo AI Summaries Make Corporate Documentation Effortless

    Reviewed on Nov 11, 2026
    Review provided by G2
    What do you like best about the product?
    It has Rovo AI to summarize any page, and it’s also used effectively for corporate documentation.
    What do you dislike about the product?
    Maybe in the future we’ll need more improvements to keep up with the market.
    What problems is the product solving and how is that benefiting you?
    It solves the documentation issue, allowing us to refer to any type of corporate material.
    Anonymous

    Flexible, Easy-to-Use Documentation That Connects Teams

    Reviewed on Nov 05, 2026
    Review provided by G2
    What do you like best about the product?
    I like Confluence’s flexible UI and how easy it is to use. I can create boards and tables easily, and the AI tool helps me write documentation, get suggestions, check grammar, and make content easier for everyone to read. I also value how we can share documentation across business units and collaborate on reviews and feedback. Its collaboration with Google Drive and Google Docs works well for us. Setting it up was pretty easy, with help from the license support team and Confluence documentation.
    What do you dislike about the product?
    nothing much that i dislike
    What problems is the product solving and how is that benefiting you?
    I use Confluence for documentation across our organization and to collaborate across business units. We create projects and spaces, share them based on license access, and teams can access documentation and share reviews and feedback with each other.
    Benjawan Y.

    Confluence Keeps Our Technical Documentation Centralized and Easy to Navigate

    Reviewed on Nov 02, 2026
    Review provided by G2
    What do you like best about the product?
    What I like best about Confluence is its ability to centralize documentation and make information easy to organize, maintain, and share across teams. I use it mainly for technical documentation, solution architecture, system design, API specifications, and project-related information.

    I particularly like the hierarchical page structure, which makes it easy to organize complex information and navigate between related documents. It also supports team collaboration, allowing multiple people to contribute, review, and keep documentation up to date in one central place.

    Overall, Confluence is a valuable tool for knowledge management and maintaining consistent documentation across projects.
    What do you dislike about the product?
    One of the things I dislike about Confluence is that managing large amounts of documentation can become challenging over time. As projects grow, pages can become difficult to navigate, and finding the latest or most relevant information is not always straightforward.

    The page formatting and editing experience can also be somewhat limiting, especially when working with complex technical documentation, tables, and architecture diagrams. Additionally, maintaining consistency across multiple pages sometimes requires extra manual effort.

    Overall, Confluence is a useful documentation tool, but I think its content organization, editing experience, and document management capabilities could be improved.
    What problems is the product solving and how is that benefiting you?
    Confluence helps solve the problem of scattered and inconsistent documentation across projects and teams. Instead of storing information in multiple files, emails, or separate locations, I can centralize technical documentation, solution architecture, system designs, API specifications, and project information in one shared workspace.

    This makes it easier for team members to access the latest information, collaborate, share knowledge, and refer back to important technical decisions. It also reduces duplicated work, minimizes communication gaps, and helps ensure that everyone has a shared understanding of the project.

    For me, the biggest benefit is improved knowledge sharing, better documentation management, and more efficient collaboration across different teams.
    Ash H.

    All Documents in One Place with Seamless Jira and Bitbucket Integration

    Reviewed on Oct 28, 2026
    Review provided by G2
    What do you like best about the product?
    It keeps all of our documents in one place. Everything is easy to trace and search, and it integrates smoothly with Jira and Bitbucket. The UI is also great and makes it simple to navigate.
    What do you dislike about the product?
    The “Publish” and “Close” buttons are confusing for document owners. This really needs to be simpler and clearer.
    What problems is the product solving and how is that benefiting you?
    Solves our document management processes
    Shubham S.

    Page Formatting Can Be Time-Consuming

    Reviewed on Oct 16, 2026
    Review provided by G2
    What do you like best about the product?
    I like Confluence because it’s easy to maintain documentation. Whenever I face an issue or make a mistake, I first check my previous documentation to find a solution and avoid repeating the same mistakes.
    What do you dislike about the product?
    Sometimes formatting pages takes extra time, especially when I want to keep the documentation clean and well organized.
    What problems is the product solving and how is that benefiting you?
    Confluence helps me keep all documentation in one place. When I face an issue, I can check previous solutions, save time troubleshooting, and avoid repeating past mistakes.
    Bernardo R.

    An Awesome Collaborative Internal Wiki for Centralizing Company Knowledge

    Reviewed on Sep 30, 2026
    Review provided by G2
    What do you like best about the product?
    It is like a collaborative internal Wiki on our company so that it helps us to concentrate all information in one place, to check, to edit, etc
    What do you dislike about the product?
    Could be more colorful in all documents, i mean, in the way information is displayed
    What problems is the product solving and how is that benefiting you?
    Before we had no place just some words in the cloud, now all concentrated in one place
    Colleen K.

    A Single Source of Truth for Documentation—Easy Setup and Jira Automation

    Reviewed on Sep 09, 2026
    Review provided by G2
    What do you like best about the product?
    It helps us have one north star, a single repository where we can keep all our documentation, results, and other materials in one place. It ensures we’re all working from the same source, and it’s very easy to set up. You can also tie it in to automate work in Jira. Overall, it’s easy to use, and even if there’s churn, we still have the documentation.
    What do you dislike about the product?
    I have to say there’s a learning curve when you’re first figuring out how to use it. At times the UX feels too reactive: trying to move a paragraph can create multiple rows, and other times you try to move something and it gets wiped off the page. I also didn’t even know how to edit at first, so for new users the learning curve is definitely there.
    What problems is the product solving and how is that benefiting you?
    It gives us a single place to store all our technical documentation, creative documentation, and key learnings from projects and campaigns.
    sreenivasan p.

    Turned scattered test docs into a single source of truth

    Reviewed on Sep 07, 2026
    Review provided by G2
    What do you like best about the product?
    As a QA engineer, Confluence is where my entire testing workflow lives. What I like best is the Jira integration — my test case documents, bug analysis reports, and requirement gap analyses all link directly to the tickets they relate to, and I can embed live Jira issue tables in a page so a feature's test coverage status is always current without manual updates. Page templates are the other big win: I've standardized formats for test plans and PRD review docs, so every feature gets documented the same way and stakeholders know exactly where to find what they need. It also made my own onboarding faster when I joined — the existing QA space gave me feature context in days that would otherwise have taken weeks of asking around. Inline comments have quietly become essential too: when I document a requirement gap or an edge case question, product managers respond right on that line, and the decision stays attached to the doc for future reference. Version history has saved me more than once when tracing when and why a requirement changed between releases. And on the rare occasions I've been stuck, Atlassian's documentation and community forums have had an answer every time — I've never needed to raise a support ticket for day-to-day usage.
    What do you dislike about the product?
    Search is my daily frustration. When I need to find a specific test plan or an older bug analysis doc, Confluence search often surfaces outdated drafts or duplicate pages first, so I've resorted to bookmarking key pages instead of trusting search — which defeats the purpose of a knowledge base. The editor's table handling is my second complaint: my test case documents are table-heavy, and restructuring columns, copy-pasting rows from spreadsheets, or working with large tables is slow and error-prone compared to Excel or Sheets. Long documentation pages also become sluggish to edit, which I hit regularly with detailed test coverage docs. Finally, useful capabilities like AI-powered search and content summaries sit behind the Premium tier, so teams on Standard don't get help with exactly the problem (findability) the product most needs to solve. Better search relevance and native stale-page detection would fix most of this.
    What problems is the product solving and how is that benefiting you?
    The core problem Confluence solves for me is scattered QA knowledge. Before, test plans, requirement analyses, and bug investigation notes lived across spreadsheets, chat messages, and local files — when a dev asked 'was this edge case covered?' or a PM asked 'why did we deprioritize that bug?', answering meant digging through history or relying on memory. Now every feature has a documented trail in one place: the PRD analysis, the test coverage doc, the gap analysis, and links to the related Jira tickets. The benefit shows up in three ways. First, repeat questions get a link instead of a re-explanation, which saves real time every sprint. Second, release retrospectives are faster because the reasoning behind test decisions is already written down next to the tickets. Third, when regression issues surface months later, I can trace exactly what was tested and what was flagged at the time — version history makes that audit trail trustworthy. It's turned QA documentation from something we did for compliance into something the whole team actually uses to make decisions.
    Gagandeep c.

    Confluence Makes a Powerful Central Knowledge Hub for Collaboration

    Reviewed on Sep 01, 2026
    Review provided by G2
    What do you like best about the product?
    Confluence is really helpful for creating a central knowledge portal and community, where it acts as a central repository that allows all stakeholders to collaborate.
    What do you dislike about the product?
    While it’s very useful as a central repository, there are a few small areas that could be improved—mainly the cost. On top of that, there’s a steep learning curve, and the editor feels a bit clunky to use.
    What problems is the product solving and how is that benefiting you?
    I think Confluence helps solve issues that come up when teams work in silos by providing a central repository for documentation, project details, and queries/issues along with their resolutions—all on a single platform.