New blog posts

Quickstart guides

If you haven't checked them out yet, we now have a full set of guides to get you up and running with Jiglu as fast as possible.


For administrators, there are guides to configuring Jiglu:

We also have a couple of checklists of things you need to gather or think about before you start:


For ordinary users there are guides to system basics, things you need to know in Jiglu groups, using your personal Radar home page and everything to do with tagging:

If you're looking for more on the technology and how to install Jiglu, then you should also check out the installation space.

Written by Stephen Hebditch. Published on .

Collaboration software's missing pieces

Back in 2003 when I first started developing collaboration systems, a lot of organisations had something like this:

  • An email system in which lots of useful conversations resided but which was difficult to search and often limited in how much was kept.
  • A content management system in which more valuable information was held, but which was not part of users’ everyday workflow and was not really geared to easy contributions.

Skip forward sixteen years and frankly things haven’t improved that much:

  • Conversations moving to Slack or Microsoft Teams have just opened up another silo, while the splintering of discussions into tinier pieces makes finding information later more of a challenge.
  • Important information, while now more likely to be held in a dedicated collaboration system like Confluence or SharePoint, is still isolated from where conversations are mainly taking place.

This isn’t a new problem. For several decades people working in the knowledge management field have been considering the problems of tacit knowledge versus explicit knowledge and ways that organisations can better capture information of value. When we designed Jiglu, we looked for how we could bridge the divide between those two sides:

  • Making it easy to transfer information from conversations into a more formal setting. If something comes up in an email discussion or in a group instant message then with just a few clicks it can be transferred into the knowledge wiki.
  • Supporting different roles within a collaboration space, so some members can be involved just with contributing while others can do more organisation, such as taking useful information from conversations and making it suitable for long-term retention.
  • Using simple workflow to ensure that knowledge is of a suitable quality: you can transfer something in a conversation then come back to it later to work on or have others work on it; for bigger teams you can require approval from a certain number of members before something is published; after a certain amount of time has elapsed then entries can go back for review to ensure they are still valid.

Once an entry has been published in the wiki, Jiglu also helps you connect it to other resources:

  • There’s an audit trail back from a published entry in the knowledge wiki to the conversation where it originally came from. Sometimes it’s useful to see the original context and who said it.
  • Jiglu’s automatic tagging engine connects conversations and content, so if a new discussion is taking place it’s very easy to see what else is known on that topic, whether it’s explicit information in a knowledge entry or a tacit information in a group email discussion or instant message.
  • Search encompasses both content and conversations, prioritising the wiki entries where knowledge is being retained for the long term but also letting you find the nuggets that may be buried deeper in conversations.

Once you’ve captured something in the wiki, that isn’t the end point either. Jiglu lets you easily start discussions around entries, which in turn can feed back into updates to an entry or perhaps a new one.


It’s all part of a continual cycle that we hope better brings together these two sides, eliminating the information silos and ensuring teams can work together more effectively. And for the future we’re looking at ways that we can use AI to better support users in these processes.

If you’d like to try it out, it’s very easy to get started with Jiglu.

Written by Stephen Hebditch. Published on .

Jiglu's summer of security

Right from the start we've designed and built Jiglu with security as one of the most important considerations. From the beginning Jiglu has had a strong role-based permissioning model that ensures users only have access to appropriate resources. An extensive unit test suite ensures that API calls cannot breach that model. Since then we've added additional security features, such as two-factor authentication and password encryption upgrades to ensure we continue to meet current best practice. We've also added new user account integrity features, including additional workflow options to prevent accounts being taken over.

It's always good to get an outside view of flaws that may have been overlooked and this summer with one of our customers a source code security review and a penetration test of their product installation were carried out. This work found some cases where we had not considered how the product might be used in a malicious way, a number of recommendations for hardening the product against vulnerabilities and several script injection flaws in the web application that had been missed. We were pleased though that the core integrity of our security model was not an issue.

With Jiglu 11.8 and 11.9 we addressed all these issues. Significant enhancements to our test suite were also made to better safeguard against future web application vulnerabilities slipping through. You can find the details of all these changes in our release notes.

With our latest version we think Jiglu is now an even better solution for collaborating securely and in an environment where you get to keep total control of your own data. None of your data, metadata or user behaviour gets shared with anyone else, ever.

If you haven't tried Jiglu yet then give it a spin, or drop us a line to if there's anything you'd like to know more about.

Written by Stephen Hebditch. Published on .

Improved Amazon Web Services integration in Jiglu 11.6

It's the first release of 2019, filling in a few gaps before we get down to work on the next major release due in the summer.

Amazon Web Services has become a key platform for us over the past year. For customers hosted on the platform we're pleased to announce a new integration with Amazon Simple Email Service, which gives the advantage of spam and virus filtering on incoming email for a small additional monthly charge. We also added new spam filtering options in the product, letting you decide how to handle messages that are potential spam.

11.6 also has a handful of smaller improvements and fixes, including simpler configuration when running in a distributed server environment.

You can find the full release notes here. If you'd like to try out Jiglu then you can get started here.

Written by Stephen Hebditch. Published on .

Everything bigger enterprises need in Jiglu 11.5

It's the last release of 2018, a year in which I feel we've made huge strides with Jiglu - a better user experience, the latest technologies and all the features you'd expect in a modern collaboration suite.


The last three releases have focussed on filling-out some of the requirements needed for bigger enterprises. I'll be writing more on some of these in the new year, but for now here's a summary of what we've added recently:

  • Virus scanner integration, so attachments and other shared documents get checked before they are made available for download.
  • Auditing improvements and a new email newsletter for administrators that summarises important changes to the system that they should know about.
  • Retention improvements, so everything contributed can always be kept with inappropriate content withdrawn from viewing rather than deleted.
  • Categories for groups, so they can easily be flagged with internal security access levels.
  • Invitations that let you pre-select multiple groups a user will be joined to when they register with a one-time token, making administrator workflow easier and eliminating the need to ever distribute passwords.
  • Improvements to automated workflow so users can make changes themselves but administrators can quickly approve them when necessary.

There have also been lots of minor enhancements for end users and some performance improvements too.

You can find the full release notes here. If you'd like to try out Jiglu then you can get started here.

Written by Stephen Hebditch. Published on .

Mentions and better notifications in Jiglu 11.2

It's been a busy summer for Jiglu with a steady stream of updates and improvements as we strive to give all our users the best experience possible.

One thing people told us was missing from our group instant messaging was mentions - those @somebody shortcuts that many social networks have to let you quickly bring somebody else into the conversation. However, we didn't want to limit them just to live talk, so we've brought them in across all the different types of content in Jiglu, from instant messages to blog comments to email messages. Mentions also get tagged, so you can easily track them wherever they happen to be, and summarised in the daily email newsletter.


To support this new change we've added a new notification stream to users' home pages. In one place this consolidates all your mentions, all the responses to things you've written and all the updates that other people have made to your wiki entries or blog posts.


Browser notifications additionally alert you each time there's a new mention, response or update for you.


There's lots of smaller improvements too. You can find the full release notes here. If you'd like to try out Jiglu then you can get started here.

Written by Stephen Hebditch. Published on .

Little things to make life easier in Jiglu 11.1

Jiglu 11.1 is out today. This is a minor release with a number of small improvements and fixes to the product.

The biggest change is the ability to now configure an LDAP user directory through Jiglu's web interface rather than needing to edit a configuration file. Now all but the lowest-level settings can be managed through the web, making it easier than ever to get started with a cloud-hosted system.

There's also a small number of new features that round out the collaboration functionality, including easier embedding of videos and being able to find holes in the knowledge wiki that ought to be filled.

You can find the full release notes here. If you'd like to try out Jiglu then you can get started here.

Written by Stephen Hebditch. Published on .

Tighter security, easier file sharing and simpler branding in Jiglu 11.0

We're pleased to announce the release of Jiglu 11.0. This release concentrates on features that customers have told us will make their work safer and easier.

  • Two-factor authentication, providing better protection for accounts by requiring the entry of an additional code generated with Google Authenticator when logging on.
  • Bulk file upload, letting you easily create multiple knowledge entries from files dragged and dropped onto a page and optionally creating editable content from suitable files.
  • User-editable themes, letting you choose the main colours of the system to match your own organisation’s branding.

There are also a large number of smaller improvements, many again from customer feedback, that will make the product easier to use and more consistent in how it operates.

You can find the full release notes here. If you'd like to try out Jiglu then you can get started here.

Written by Stephen Hebditch. Published on .

New features in Jiglu 10.5

We're pleased to announce the full release of Jiglu 10.5.

The biggest improvements in this release are to threaded discussions. Jiglu now keeps track of which threads users have read, so it can flag those with new messages, and allows administrators to split threads as well as merge them. We also improved the handling of large attachments when they are sent out on email, particularly for people who have opted to receive daily digests rather than individual messages.

You can find the full release notes here. If you'd like to try out Jiglu then you can get started here.

Written by Stephen Hebditch. Published on .

Collaboration's hidden pain point

The last decade has seen funding for local government in the UK shrink by around a third. For those still employed, the last thing they have time for is a platform that needs extensive and continual admin in order to function. Here's how we help one local government customer make the most of the time they have available.


Jiglu was built from the start to allow organisations and their teams to delegate activities according to what is right for them.

Our customer is a team that spans several councils in the local area as well as involving coordination with some outside agencies and specialists at other authorities. Rather than needing someone central to manage membership, anyone who is a member of one of a collaboration space can invite anyone else appropriate to join, whether they are already a user of the system or not. At a time when staff churn can be an issue the group can quickly and easily bring in the necessary people and get them up to speed.


If you get an invite to a space and you're already a user then with a couple of clicks you can accept the invitation. If you're not yet a user then you'll be invited to self-register instead - something only those with an invite can do. The registration form can also ask extra questions configured by the system administrators, for example their job title or phone number. These can be made available to others in the user's profile page or kept private so only those who have been given the role of system administrator can see them.



When a new user registers they will first need to confirm their email address, making sure they do work for the organisation they said. However, the system administrators still want a final check that they are really supposed to be there. Jiglu's user workflow enables those from with email addresses at the core councils to be approved automatically, saving time on the most common cases. For everyone else a task will be created for one of the administrators to approve them, which could involve them checking up on the extra info they provided when registering.


There's also a full audit trail available showing what invitations were made, who did the inviting and who approved a new user.


As people move on to new jobs they can be easily dropped from spaces or the system while still maintaining their previous contributions and the audit trails of their activities. Again there are self-service options so users can themselves leave spaces or the system, with notifications to administrators if necessary.

Each organisation and team is different. This is what works for one customer, but Jiglu lets you find the level of delegation that's right for you.

Written by Stephen Hebditch. Published on .