The cases where I set up the server myself were straightforward and went without any glitch along the documented steps.

The initial setup for Atlassian Confluence isn't easy. It would be best if you had some time to understand how to approach the tool entirely, but it doesn't take up so much time. Atlassian Confluence has many features, which is why it's normal if it's a little bit complex, though Jira is even more complex.

Atlassian Confluence is similar to Jira because it takes more than five minutes to create dashboards and tickets, for example. It also takes time to involve the team and understand Atlassian Confluence and its functionalities. Though the tool is flexible enough to start using it without complete knowledge, the more you use it and get more involved with it, the better you can understand Atlassian Confluence and use all features it provides better.

I'm not aware of how long it took for the tool to be implemented because it was handled by a different team, though I believe the team in charge customized Atlassian Confluence with the help of some experts or third parties.

The product is easy to set up. It's not a complex process. 

Overall, the product requires zero maintenance. 

Setup is pretty simple. We did the basic setup. When we created a project, we could give access to people and start creating a trial page, parent page, etc.

The implementation process is easy for me. People sometimes find it easy and yet there is room for improvement in the process. 

We advised a third party on how our workflows needed to be implemented and they implemented them on the cloud. Then they moved the project to our cloud and set it as a base for everything there. It was actually really smooth. It didn't take too much time.

The full implementation strategy took two months. 

There was a little bit of complication from the bank side. We have a lot of security, unblocked IPS, et cetera. The two months weren't the full implementation time. We had areas that were blocked due to our security control. A couple of times we remained blocked for one week. I want to say the ideal time for the implementation was one month and a week. For us, of course, it took longer. 

We had five people in total ding the deployment. There were three from our side and two from the third party. 

I'd rate the entire process a three out of five in terms of the ease of implementation. 

We have a contract for handling maintenance. The vendor partners are handling it. 

The initial setup is straightforward, and takes less than five minutes to register and create your first site.

I rate the setup phase a ten on a scale of one to ten, where ten means that it was a very easy setup process.

The solution is deployed using the cloud services offered by Atlassian. The tool cannot be deployed on an on-premises model.

The solution can be deployed in a matter of minutes. The moment you are okay with the domain and other stuff, it will just take two to three minutes for you to initiate or spin an instance for you.

Depending on the system, the solution's initial setup could be easy or complicated. I rate Atlassian Confluence around eight to ten out of ten for the ease of its initial setup.

The initial setup of Atlassian Confluence is straightforward. It's set up within the company and we ask to create workspaces for ourselves.

I was not involved with the initial setup. It was done by my colleague.

We now have two or three persons setting up our administrators, and they are setting up some data and looking after the maintenance.

The initial setup is straightforward. 

I was not very involved in the setup of Confluence, but my understanding is that it was not that difficult.

The installation is easy, and there's nothing more to do after the installation. It can be ready to use very quickly.

Deployment would probably take a day or two at the most. However, if the client needs advice regarding the structure of the company and how to do the knowledge base, then it can take several days. Usually, this is up to the organization, but as it's really quick to use, you can create whatever you want the day after the installation.

The initial setup was straightforward and quick. 

The setup of Atlassian Confluence can be difficult and other times easy because if you want to implement something, you need to have your process figured out. You have to understand exactly for what purpose you want to use something. Once you understand that, you have to know how you're going to use it. Not only immediately, but also in the future. Once you have this map, then you will be able to use a tool properly. Otherwise, you will be doing trial and error for a while.

If you want to get Atlassian Confluence up and running, the time is depending on whether you want something simple or customized. However, it can be done within a week and have everything running.

The initial setup was complex.

I'm not an administrator but I believe the initial setup is relatively simple. From a user perspective, you can very easily create a dashboard, quick links, and things like that.

There was no problem with the setup process. 

The initial setup was straightforward and not too complex. I rate the setup a seven out of ten. I think the solution was previously deployed on-prem, but now, I think it is on the cloud. I also do not have an idea of how long it took to deploy Atlassian Confluence, as it was done by the backend team and not us.

The initial setup is simple although it was not done by our team. We had a separate team do it for us.

I found the implementation process to be simple and straightforward. It's not complex at all. 

All things in Atlassian Confluence are set up on cloud. The clients have their administration teams, and they extend an account for our developers, our PAs, and our managers on these platforms. So we don't set up anything. The administration team sets up the Jira accounts on cloud. GitLab and GitHub are set up on-premises while keeping the code version internally. Setup is not a major issue because most of these things are very simple, and you have instructions.

The initial setup is rather straightforward. 

The initial setup was easy and happened in the background.

The initial setup is straightforward.

Less than one full-time employee is needed for the maintenance of this solution.

With Atlassian Confluence, there are two types of setup processes available. My company uses the on-premises version of the product. My company also uses its own infrastructure to host Atlassian Confluence. Our company also uses the SaaS version of the product. In general, both versions of the product are being used for different projects. I think the SaaS version of the product does great in terms of memory and everything. The on-premises version of the product is a bit old but is more secure and preferred by our clients since they feel that their documents are safe in an on-premises setup.

I installed version 4 from scratch. That was very straightforward. I connected it to Postgres (PostgreSQL), and that was trouble free and straightforward.

I haven't had the need to install more recent versions or manage installations that service a large number of concurrent users.

The initial setup requires some planning. To get Confluence up and running took a day but it took close to a year before everyone felt comfortable with the solution. Following the initial setup, it required user management and security settings. And then build the data structure or space structure and install plugins. Following that there is a training process for users. We deployed internally because we have experience providing that type of consultancy to other companies. Half of the companies we deploy to use some external help and half do it by themselves. It takes longer if you do it without assistance.

Maintenance requires less than one man month per year because you don't have to install updates. But still there's some maintenance, cleaning up data and fixing the permits and things like that.

The initial setup, the installation, was managed by someone else. 

It is just for document collaboration. There is no deployment period. You are just creating your documents on Confluence.

The initial setup was easy. We used SaaS.

The initial setup is very simple.

I didn't do the initial setup, but I think it's pretty easy. When I had to configure a new site, it was very easy.

The initial setup of Atlassian Confluence is straightforward. 

We deployed in-house. 

The initial setup was straightforward.

The setup was straightforward and perfectly documented. Atlassian gives you a step-by-step guide. You would expect nothing less from a documentation platform.

The initial setup is very simple.

In terms of the initial setup, we were not able to do it right. Separately, we needed to build our own add-on.

The initial setup is pretty straightforward, I have never had any issues.

I was not here for the initial setup, but the upgrades setup is complex for us mainly because cloning the environment for testing is complex.

The setup is fairly simple, it's just a website that you login to use. There's nothing to install. Just register an account and use it. 

The initial setup is very straightforward. 

Having a cloud solution, setup is easy. Being somewhat of an expert from using Atlassian products for years, I know where to look. For novice users, I’ve been told that not everything is easy to find.

Atlassian Confluence was relatively simple to set up. The time it took was only a few minutes.

The installation was straightforward. It was easy to start, easy to setup with low administration involvement, as long as you have an "open by default" policy around content.

Complexity comes into play to drive evolution, content curation, usage, and adoption analytics. When you don’t have enough information on usage easily available, setting up some guidelines can help drive consistent patterns of usage. You need people to help guide that process and keep the organization of the content coherent.

Confluence setup is very straightforward, but an absence of formal training availability caused it to take longer than it should have to become productive.

We had help from hired services help such as K16T and others. I also think our installation was much more complex than most from what I am told.

Deploying Confluence is complex. It requires deploying many other libraries. We don't pay for maintenance anymore. We just maintain the solution ourselves. 

• Setup was fairly straightforward
• Some configuration is required to integrate with LDAP for authentication, if that is your chosen route
• Some configuration is required if you integrate with other Atlassian products
• The installation guide covers everything

The installation and setup for Confluence itself is relatively straightforward. There is good online documentation for it as well. The templates help make easy work of the design and site creation.  

The setup is more complex and the developers helped to set up the environment.

Initial setup with the cloud version is super easy but the server is only slightly more complex depending on your firewall, SSO, etc.

The initial setup is very, very good. It's not complex it all. It's very straightforward and they make it very easy.

The entire setup isn't an intricate process. We didn't have to pour over documentation to try and figure things out. We just followed our instincts and it worked out quite well.

Initial setup is easy‎. The Atlassian documentation is good. Just make sure to read the requirements description.

It was straight forward.

Deployment and setup was handled by the client's infrastructure team. I'm unable to comment on this

The initial setup was easy, and not complex at all.

Initial setup was straightforward.

Straightforward

Straightforward.

The setup was straightforward.

The installation can be quite complex. You need to know what you are doing in order to install it on your own. The cloud version is very easy to install.

Straightforward install and setup.

I was not involved with technical administration or the implementation procedure from an IT infrastructure team perspective. For this reason, I can't speak for individual customers.

The initial setup was fine. More memory may be required, depending upon the size of the attachments.

Setup was very easy once the we established our goals in using the system.

The initial setup is straightforward, though the time it takes depends on the size of the project.

You should initially use consulting to make good decisions about architecting this product. Also, designating at least two SMEs to be dedicated to the setup and enhancements is key.

The initial installation was on UNIX with Oracle for data storage. I did not have any personal involvement with that installation. As a user, I can say that it worked OK.

As of now, we run it on Linux under Apache Tomcat and with Oracle. The move, which was done at the same time as a release upgrade, did not introduce any problems.

My personal installation experience was a private workstation test installation. It was done without any problems.

Some of our installation work was "from the box", when the business requirement was standard. If the business requirement wasn't standard, we customized Confluence and added add-ons to it.

The setup was easy.

Initial setup was kind of straightforward. We learned how to use it as the issues/necessities appeared.