Confluence

We use Confluence as our main source of documentation. We use it from creating documents that contain tables of data. We use it for creating design documentation. We use it for creating operational documentation. It has good search capabilities and it's easy to create simple to use navigation. It also has capabilities that allow you to be notified of changes to the documentation.

We use Atlassian Confluence for knowledge management. If a developer is working on a feature and wants to share the technical details or non-technical details about that feature he can create a confluence page for that so that other stack holders can go there to understand the work. Also, let's say I am another developer who made some changes to the existing feature then I can go and edit the page with the latest information. If I am new and want to understand a particular feature, I can search for it on Atlassian Confluence. So it helps to gain knowledge about the product functionalities and get an idea of the logic when working with the legacy code.

Atlassian Confluence has been a great way for my team and I to organize our ticketing queue, project management, and integration with Salesforce through custom APIs. The problem we were facing was that a lot of work was being done through Slack. We needed a better way to track the work that was being done to ensure SLAs were met and scalability was approachable.

We at our organization use confluence for managing all the research documentation,designs,page updates,development updates,calculations on the topics,developed code histories,quarter plans and multiple time to time handover records.
It addresses the local documentation,access issues.Easy sharing documents with team filters, login safety, data privacy.
Its interface gives the option to Auto select title content,standard headings in the paragraph options. Status highlight options.
Its a part of the documentation life in the organzation.

We are using Confluence increasingly throughout our entire company. I manage our Test Engineering team and I was the first leader to really utilize Confluence to the best of its ability. We had all this knowledge in everyone's heads that needed to be documented. You know, the "bus factor." Utilizing Confluence for this has rapidly increased the knowledge sharing across our team and teams. Also, it's much faster to onboard new employees when you can direct them to your library of documentation and how-tos!

Confluence for the Cloud cannot handle numbered lists well – it resets the sequence to 1 if you have other items such as a table or certain apps (such as /note) or similar included in the list. This is a major drawback if you have complex procedures to create. Don’t be fooled. Confluence is actually very, very expensive to own. The Marketplace apps are seemingly very cheap - even free, however, if you have a large user base, that £5 per app is automatically multiplied by the number of users, in my case the company has some 500 users, which represents some considerable investment, especially if you want the app to do something pretty basic. The included apps look like a good deal, that is until you start using them. These apps have not all been developed with love and care (or decent supporting documentation) and turn out to be inflexible, and format themselves according to how the developer has designed them. Plus, the apps are really not all that proficient. The styles are limited to what THEY consider you will use - which personally, I don't like. Their spell checker is inaccurate for the UK market. If you've been using the old template they now have a new one and upgrading existing documents may not always work. All requests for enhancements are handled by Developers and if your request falls under a certain number of 'likes' then you can forget having the enhancement - as is the case with the numbered lists (2 years and no improvement). The page layouts are restricted to their idea of what columns of information should look like and there is little flexibility. Changing the column widths is poorly implemented to using their presets which do not always suit. You can't include anything other than videos or photos (graphics) unless you purchase an app - useless for say using Excel Tables are 'clunky' to work with. There is none of the functionality you would expect from a more proficient word processor such as Word - forget such items as search and replace Overall, if I were to choose again, I would not use Confluence for anything more than a form of a notebook.

Atlassian Confluence is currently used in the company for documentation. The roadmaps, technology, architecture, etc are documented in confluence. Atlassian Confluence provides nice templates for the creation of various artifacts. It has nice integration with the Jira Stack.

Confluence is a collaboration wiki tool used to help our teams to collaborate and share knowledge efficiently. With confluence, we can capture project requirements, assign tasks to specific users, and manage several calendars at once with the help of [the team] There is a great deal of content in most corporate wikis. Understanding which pages are the ones you need to complete a process or solve a problem is not always apparent. It often takes several searches and parsing through the results to find what you think is the right content. We have always [had] issues for centrally [managing] all wikis and team info along with all required data and collaboration with other automation tools along with we can get the maximum output and confluence having all the required parameters and smooth working while best speed and easy to use approach

We use Atlassian Confluence across [the] whole organization and it's a standard tool for project documentation storing. One of the biggest values of which Atlassian Confluence brings to our company is that you can manage all access and edit rights to your documents from a single console or even grant access for customers if needed. The other big advantage is that Atlassian Confluence [has] deep integration with other tool[s] like Jira and Miro so you can easily share content between them.

It's used as a wiki of shared knowledge amongst team members of the same department. It is used as a handbook for new hires and a refresher for those who need to take over a colleague's task if they're out of the office.

[Atlassian] Confluence helps different divisions to maintain and organize information about Software Products we develop or just to create our own reliable source of [information]. It's the best ally when it comes to developing an onboarding process for new hires, it helps to create a comprehensive page that contains all the basics for the new developers.

We are using [Atlassian] Confluence across several departments within the organization, but not across the entire organization. It allows us to keep our documentation related to Jira issues in one easily accessible place that directly ties into our Jira projects, which keeps us well organized and makes it more convenient to keep documentation up to date.

Confluence has been our standard company tool for years to capture, organize, share, and discover knowledge. Confluence is used by the entire company but enjoys high utilization with the technical software engineering teams. Confluence ensures that product architectures, partner integrations, and customer projects are fully and accurately documented. Confluence is also used externally to share common customer documentation, online help, and integration specifications to our product's platform. Confluence is the ideal tool for sharing structured and connected content both inside and outside of the company.

We currently use Confluence as our primary document collaboration repository - everything from meeting notes, status updates, how-to documentation, business processes, etc are all stored inside Confluence. This allows for anyone in the company to obtain access to meeting information and policies from a central, easy to navigate system. Every team within the company has their own 'space' within Confluence to format and design how their team operates within Confluence. The amount of data we moved from various Word documents and PDFs has been staggering.

Confluence is the perfect collaboration space for company knowledge, from DevOps, to internal meeting notes, to individual process documentation.

[Atlassian] Confluence is used across some departments within the company. Its primary purpose is to be a "knowledge hub" for content, information, training, etc for our teams. It's the go to place for resources about the product, metrics or to link out to various other resources (google docs, applications, etc).

We're using [Atlassian] Confluence as a repository for internal documentation and engineering documentation. It's used across the whole company but mostly our developers and engineers are using it on a regular basis. [Atlassian] Confluence addresses the challenges of keeping an organization's documentation in one neat place that's easily accessible.

Atlassian confluence is used in whole organisation across various departments and at all levels.
It is used in sharing documentation ,sops, dashboards,excel sheet etc with concerned teams or person.
Atlassian confluence solves the main problem of storing and accessing the documents from single source instead of creating copies to store as archives.
If some changes are there in any documents we use to create multiple copies to store everywhere. But after using confluence it is uploaded in single link and everyone can reach out to it. Thus saving time

[Atlassian] Confluence is being used by our organization across all departments and trams. [Atlassian] Confluence is great for helping our company maintain all documentation, standard procedures, etc. We have a lot of different technologies that we use, so it is great to keep everyone on the same page and house all of these standards.

Atlassian Confluence is used across the company, within several locations. Atlassian Confluence is an easy tool to use and connects several teams across the whole organisation. It addressed several communication backlogs and created a more convivial area to share quickly and efficiently updates on projects and steps to follow.

Atlassian Confluence was originally used in conjunction with Atlassian's other primary project -JIRA- as a collaborative workspace which fed into JIRA for project management and oversight. It was originally used by our whole organization from creative to dev to PMS etc but we found that the structure and integrations were too limiting to be used so broadly. Primarily it wasn't conducive to a dev workflow with PM oversight. As such we have branched out to using other products as a more collaborative workspace while using Confluence more as knowledge dump as well as various wikis for different departments.

Atlassian Confluence is used by entire organization across departments and geographies. Atlassian Confluence primarily acts as a central repository for all the knowledge that exists in the organization. The information is well organized in terms of pages and spaces and Atlassian Confluence acts as the first place to search whenever anyone is looking for the information. So it avoids reinventing the wheel by allowing to check if similar work has been done by some other team in some other geography which can be adapted or used as such.

Confluence is being used across all departments of our company: IT, business development, HR. Each of those areas has it's own customised way of dealing with knowledge pages, but at the same time we are able to cross-reference and easily exchange information and details. We are also using a standarised sharing workflow, with the ability to control access on various levels, be it for single staff members, teams, or departments.

[Atlassian] Confluence is used in two primary ways within Cisco AppDynamics. The first use case is for internal documentation, where we use [Atlassian] Confluence across nearly all departments for documentation surrounding internal services, directories, glossary of terms, high level project planning, reporting and dashboarding, and policies/procedures.

The second use case is for our public facing customer documentation of our software. This saves use the time and headache of building our own solution to provide docs, and since our target customers tend to be in the tech field, most have familiarity with navigating Confluence's UI.

We use Atlassian Confluence as documentation/wiki for the entire organization. It addresses our need for a centralized document management system. We call it wiki/intranet.