What is your primary use case for Atlassian Confluence?

I use Atlassian Confluence for documentation purposes. It is utilized for storing project data, sharing tickets through Jira to Confluence, and measuring documentation for every step of a project, much like a Wikipedia-style tag. Everything is noted in a step-by-step process on the Confluence pages.

I'm using it to handle the projects, the Jira project, and the joint projects, track all reported user stories, tasks, and bugs, and create reports and dashboards.

We mainly use Confluence for our internal documentation work and to plan new features, design documents, and knowledge transfer documents. Most of the documentation work is done using Confluence. We have a separate Confluence space for our team, with public articles about our projects and how to set up our repositories, available for anyone to access. Additionally, we maintain private content within the team's Confluence space.

Confluence is an important tool for collaboration.

I use the solution in my company for documentation purposes. Most of our company's release notes are present on Atlassian Confluence for client review and for the processes we use in our organization. All the details about the new features of the upcoming releases and all the stuff related to the company policies, like employee engagement and everything else that should be documented, are present in Atlassian Confluence. I use Atlassian Confluence for document-controlling purposes.

We use Atlassian Confluence for internal communication and documentation for protocols. You can also use the solution for knowledge management and document management because it allows attachments and some descriptions.

I use it as a knowledge base system for sharing knowledge and creating Kanban boards.

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.

We use the database for documentation and requirement gathering. So, we document those and create plans or backlogs.

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.

My primary use case is for documentation.

We mostly use Atlassian Confluence to store information and share knowledge with a colleague.

We use Confluence for project documentation alongside Jira which we use for all our task assignments. We have been using Jira for six months and have not yet used it to its full potential as we do not have qualified scrum masters in our team. We are able to assign tickets, make a scrum board and a sprint system. We have thousands of users who work with this solution.

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 use Confluence for project documentation and team collaboration.

It is a collaboration tool. All of our company documentation is on Confluence. I am using its latest version. It is a cloud solution. Atlassian is the cloud provider.

We used this solution to create and manage shared documentation, as well as managing the team details and giving visibility of attendance and absence to all team members.

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 use the solution for all kinds of documentation that are part of the testing, product, and development phases and for taking meeting notes.

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.

We were developing an eCommerce platform and wanted to capture all of the metrics that were coming across. We chose Confluent, which is a ready-to-use solution. The use case was to track all of the traffic that was coming from across the globe, and create metrics out of it.

The company needed a tool that project managers put their plans, documentation, and everything related to project management into, including milestones that are not available on Jira. They have to use both this and Jira in order to give a full report to management.

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.

We use this solution to manage the knowledge base within our organization. We're looking to use Confluence for collaboration and data, sharing information internally and externally. Confluence is connected to our JIRA, so we also use it for task management. And vice versa, JIRA can link to the Confluence page. We are customers of Confluence and I'm a data manager.

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.

We use it for our knowledge base and also for internal blogging.

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

We are using Atlassian Confluence as a repository for files.

We document all the processes and flows we are planning to implement on projects. We capture all kinds of documentation.

We have a standalone, server-based version. Confluence is installed onsite. Nowadays, they don't provide any standalone versions anymore. They just provide the cloud versions for subscription.

We are a banking institution and use this solution to provide the key technical and functional documentation of the project that we share with our users. I'm the managing partner and we are customers of Atlassian.

We use Confluence to share weekly project information. Everyone in the company uses it daily from project managers down.

I use Atlassian Confluence for all kinds of documentation purposes, such as sharing information about specifications among the group and distributing those documents for review remarks from others. It's a nice way of distributing information between different teams.

It's the knowledge base for our company. We have project spaces for our customer projects, and the project teams share information about the projects. We also use it as a wiki for our company.

We are using a lot of Confluence. While we are gathering the requirements from the business for the development, Confluence is used. We are creating project charters there. It covers all the functional requirements including knowledge sharing sessions. Basically, when somebody's leaving or somebody is being hired, everything related to that goes on Confluence. This also includes information, for example, about annual leave information, et cetera. If a person is hired and we need to prepare a KT plan for that. So we prepare a page in Confluence.

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.

My team uses this solution for documentation and collaboration.

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.

My primary use case is for processes in project documentation.

Our primary use case is for documentation. We used to maintain other documents in another location, but we moved to Confluence. We use it for the design documentation perspective, not for the analytics perspective.

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).

I used Confluence mostly for the wiki and documentation.

We mainly used Jira for backlog management within IT development landscapes. We used Confluence for early-stage documentation and communication within and across teams. Since we worked mostly with large enterprises, they typically install and host any server-based solutions on their own.

In multiple organizations, we have been using Atlassian Confluence as a knowledge base, and for development. Our developers use it alongside Jira.

Every project and every initiative we start gets a Confluence site to track artifacts that are created related to that initiative. For example, we will use it for a knowledge base and for general documentation. We collect all of our meeting minutes, action lists, and so on. It is grouped in scenarios for reference, et cetera.

We primarily use it as a knowledge management tool for all of our consultants, which are architects.

We have got our own private Confluence set up. In our department, we use Jira and Confluence a lot. These are our in-house go-to tools for managing the agile ways of working. We sort of follow a bit of both models: traditional and agile. We follow the traditional waterfall model outside of Confluence and Jira, so that's more like requirements, specifications, and documents. There's another team, with which I haven't been that involved, that writes user stories and allocates tasks in Jira. They use it quite heavily. We use Jira more for agile type processing, like for Kanban boards and all that sort of stuff and allocating work tasks and two-week sprints. It supports the actual agile process. Jira is much more focused on the process of delivery.

We are a remote company at this point. We use it to collaborate on different initiatives within our interior and marketing teams. It's kind of our one-stop-shop to house our collateral and sales information. It covers pretty much anything and everything we need and everything our marketing teams would need as well.

Our primary use for this solution is EA documentation.

Implementing Confluence in documenting functional specifical documents and preparing RTMs, product requirements.

We used Confluence to coordinate products with our engineering and marketing teams. This allowed us to easily convey project details across our worldwide development and marketing teams.