Knowledge integration with Confluence.
July 21, 2016
Knowledge integration with Confluence.
Score 8 out of 10
Vetted Review
Verified User
Overall Satisfaction with Atlassian Confluence
We use confluence as our main knowledge repository across the company for mostly technical documentation and process but also for new employee on boarding and some HR specific documentation. We also use it for ongoing project planning and collaboration work.
- Confluence integrates closely with JIRA if you are already using that for ticketing and user stories in an agile environment.
- The user interface is intuitive enough for non technical users but has enough functionality for the more savvy user too.
- It has good performance from an end user perspective even when deployed as a single instance for 100 users.
- Confluence is java based and therefore prone to all the usual resource and configuration issues.
- It can be difficult to upgrade if you use a lot of third party plugins or customizations.
- We use Duo auth for MFA and it requires manual configuration changes that upgrades do not automatically handle.
- Users have fully adopted this as their technical knowledge repository.
- System Adminstrators are less enamoured with it due to the difficulties with upgrades and troubleshooting issues.
- Teams are able to collaborate more freely and across time zones by utilizing Confluence for project work and as a knowledge base.
Mediawiki was our previous knowledge repository. It works well as a standalone system but does not have the integration with other Atlassian products or crowd authentication that makes user management uniform across platforms.