Confluence Reviews

Our organization utilizes Confluence along with Jira for additional project documentation and collaboration. Details on every part of our projects are captured, stored, and shared using confluence. This includes meeting notes, shared worksheets, requirements documents, system architecture as well as some process and procedures/outcomes of the projects. IT utilizes this system as a required way to store change information for updates and enhancements.

We are currently using Confluence as a knowledge base for a worldwide project. Our usage of Confluence at the moment consists of creating knowledge articles about certain procedures, contact information (about the customer and about our own team), general information such as the SLA and to generate documentation for the customer, as he likes to know what we did to resolve a problem in his environment. Giving access to our customer to see what we have already created on Confluence gave him a lot of confidence in our work as he can see with his own eyes what are the solution and technologies we are using to sustain his working process.

We use Confluence as a place to document all our I & O help articles and processes. We also build web pages for developers to use a quick reference point to look at test data and test environments. Also starting to build project requirements into these sites for IT and business teams to view and use.

We use Confluence across our organization, but only for those collaborating on projects. In our case, we are designing a new business platform that requires extensive information gathering, sharing, and planning. We use Confluence to organize that project into teams, track to do items, share information, record meeting minutes, etc.

For me, Atlassian Confluence is a one stop solution for all kinds of documentation. I use it whenever I need to write or document about my project. which includes flow diagram as well. This tool has been used by lots of us here and most of us use this for documentation and writing some other design as well.

We use Confluence across our entire organization. We purchased Confluence with JIRA as a file management and communication tool. We still rely heavily on Google Enterprise applications (GDocs/GDrive) but we needed something which could be closely connected to our JIRA project and development pipeline management use case. Confluence allows us to create different content, like cover pages, and long-text details which are linked to JIRA Issues, but aren't necessarily appropriate for custom fields in that JIRA Issue.

We use Confluence to document our engineering practices. From documenting releases and server updates to storing coding guidelines for developers. We've basically replaced MS Office documents and Sharepoint with Confluence. Confluences make for a more user-friendly way to store documentation that is searchable, flexible and far easier to maintain.

Confluence is used to hold documents that are important to various software programs. These include install documents, patch notes, and update information. We use it company-wide and it ensures all information for software is held centrally.

We are mostly using it to document best practices, create software documentations, and store training materials and team calibrations. It is being used across the whole company but mostly by developers and trainers to provide documentation for agents. It is helping us to make the process of documenting and sharing knowledge as easy as possible while maintaining up-to-date information at all times.

My organization uses Atlassian Confluence company-wide as our internal wiki platform. Confluence has moved a formerly silo'd company culture into a more collaborative and visible one. We use the platform to share knowledge, create new content, and manage projects and activities

We used Atlassian Confluence as our internal intranet company-wide. It addressed the need to have a shared repository of information where people could go to access information. There are very specific permission sets that can be applied so that each department can have control over editing their own pages, decentralizing management of the intranet.

We use Confluence to share documents, procedures, and other essential files for more efficient collaboration between departments within the business and also between the business and its service suppliers. The features I like most are creating live tables and simultaneous editing of their information along with file attachment capability.

The entire organization uses it for storing internal information (almost like an encyclopedia of the company). Each department handles their own space within Confluence.

We use Confluence across our organization. We all work remotely so it is a place where we can collaborate on projects, we post our meeting agendas, we post tutorials, training, etc. Any content that employees need to access to do their jobs we put on Confluence. For example, we can put processes on how to complete certain tasks on confluence and we also task each other to complete certain items.

Confluence is being used at my organization to track action items, high level requirements, and decisions that are made in meetings.

Atlassian Confluence is being used as a knowledge base for our entire organization. The software enables our staff to share knowledge easily, across our different offices around the world. We have created different sections of the knowledge base, so each department has their own "area" if you will on the platform, where staff from each department can post relevant information company-wide. This avoids the redundancy of emails and creates a database of company information, as well as shared knowledge.

Confluence is used by the whole company as a repository for managing and storing business information. It is a central repository for information that we all use on a daily basis to record ideas, communicate and coordinate product releases and manage business requirements for our development process. We also use Confluence as a way for the tech team to communicate with the business and marketing departments in the company.

Up until recently, my only interaction with Confluence was through clients that used it. I would typically access designs or mock ups within Confluence. Internally, we have used Jira for a long time, but always used other tools for project asset organization/reference. We made the move to Confluence within the last couple of months in order to make things easier to between project management and asset organization as Confluence and Jira work directly with one another.

We use Confluence to support internal documentation needs. It provides a version controlled, access manageable, configurable repository of knowledge and documentation for the company. It facilitates indexing and search of the document database for quick access to information. We use it globally in the organization as a clearinghouse of information on everything from technical procedures to organization charting.

For years, our organization was using a mix of Word documents on a file server and files in SharePoint, none of which were synchronized, most were out of date and nobody knew where to look for any one document. Enter Confluence. We were able to migrate all of our old documentation to Confluence where it's easily managed, searched, and updated. The live-edit feature is especially great as we're building system documentation or pulling together meeting minutes. We started with a pilot program of one department to see how efficiently it works but have since rolled it out the enterprise as our standardized documentation tool. Every department and project can now easily update, review, and publish documentation in a securely, and centrally accessible tool. It's the perfect combination of a document repository and wiki site.

At my current company different teams have some freedom to choose organizational tools as they see fit. I have used Confluence for the most part of the year, as part of a new product development engagement in the software engineering department of one of our consumer brands. In this particular project it is used as an agile communication and collaborative documentation tool.

Atlassian Confluence has been instrumental in documenting the evolution in our business practice in a wide variety of topics. We use it to disseminate information ranging from HR, to technical knowledge sharing, to procedural administration. Associates of all levels use it to share, learn, publish and research as well. The front end is easy to use and the customization abilities allow for a professional look that is appealing to readers and contributes to a positive user experience (UX).

Our company was always ok at documenting, but not consistent and we did not have a place to collaborate and share. This meant that documents were being created multiple times and in silos. With Confluence we have become better at documentation and sharing information. We also took time to plan out how we wanted our spaces to flow and what information belong where. For example, instead of every department having their own set of documents we found that having a client space and a landing page per client gave us a streamlined approach to organize.

We (stake managers who write stories for the development team) use it for creating the backlog for the development team and the development team uses it for managing sprints. The interface is very intuitive, so even users with no experience or knowledge of the process can easily understand it. Confluence helps us prioritize different development tasks from the business and revenue standpoint and we can also track how successful our dev team was in each sprint, which makes estimation of the following sprits easier.