Confluence Intranet: Linchpin vs. Refined

Linchpin vs Refined: Confluence Intranet solutions compared

Confluence is an excellent basis for your corporate intranet. But only together with Linchpin or Refined you get your interface and functions that make Confluence a central hub for communication, the provision of important information and the extended arm of your company. But you're probably asking yourself the questions, which app should I use for my intranet? Linchpin vs Refined. Which solution is better?

In the following we have examined the Linchpin and Refined in more detail and recorded the most important differences in a clear table.

Linchpin vs Refined

Target groupPeople looking for an intranet solution with social media features.For people who want to use Confluence as an intranet.
Product Use CaseCreate a social intranet that matches your company's look and feel and creates a familiar work environment.Add structure, themes, layouts, and navigation to Confluence to create intranet, documentation, and collaboration pages for projects.
SummaryWith Linchpin, you can customize your Confluence to your brand and add social features like team events and microblogging. There are also modules to support different use cases like content personalization or extranet features.An out-of-the-box solution that is very easy to use and covers most requirements in terms of design. Among the most important features is a navigation system that organizes the entire space into categories. With the theme and website designs you can create a structure for your content and intranet layout.
Advantages and limitationsEasy to install and use. Theming with Logo and individual colors for buttons, header icons, etc. Extensive intranet features with microblogging, personalized content, localization, custom navigation, advanced profiles and more.Quick to set up and you can get great results with minimal effort. There are limitations as far as customizing the design, the navigation and news-streams. Social functions like events, org charts, extensive profiles and microblog are missing.
success storyBSH Linchpin Success StoryEEX Refined Success Story

Read more about what an intranet should be able to do and how to find the best solution for your company in this article: How to find the right intranet for your company.

Theme and Features

Theme and design features

Design / Themes for Confluence
Different designs per Confluence space
Personalization of designs* (to some extent)
Inherit design elements from global designs to space and adapt automatically.
Easy to update (even with major UI changes)

*Basically, the design of Confluence Confluence can be customized with both intranet providers. However, Linchpin offers more functions, e.g. a more extensive customization of the header or the fonts. This can be seen in the demo-instances.

Further intranet features

The ability to like posts, entries, etc.
The ability to comment on posts, entries, etc.
Simple design features, so teams can manage their own spaces without a web designer.
Personalization of menus(global menu can be created and structured, but no further customization possible)
Social functions besides the normal Confluence (microblogging, events / RSVP function, profiles, organigrams) (via Apps on the Marketplace)
App Center for a personalized set of legacy systems (no SSO of legacy apps) (via Apps on the Marketplace)
Terms of Use for Compliance with Laws. (via Apps on the Marketplace)
Touchscreen and native mobile app.

Summary and recommendation: Linchpin vs Refined

Why we love itTransform Confluence into a modular, fully personalized social intranet platform.Customize Confluence design partially (which is sufficient in most cases), very quick & easy setup.
Theming & Personalization⭐ ⭐ ⭐ ⭐⭐ ⭐ ⭐ ⭐ 
User-friendliness⭐ ⭐ ⭐ ⭐ ⭐ ⭐ ⭐ ⭐ ⭐ 
Social Intranet Features⭐ ⭐ ⭐ ⭐ ⭐ ⭐ ⭐ ⭐ 
Implementation effortMediumLow


If you're looking for a simple and relatively inexpensive upgrade to Confluence's design and navigation, you should go with Refined.


If you want to use Confluence as the basis for a full-fledged social intranet, Linchpin is probably the right solution for you.

Here you can find more information and Success Stories from former projects to intranet with Confluence, Refined and Linchpin.

Do you need support with the implementation of an intranet in your company? Feel free to send us a message or call us directly.

Jira Service Management Personalization

Personalization of your Jira Service Desk for Customers and Employees

You put lots of effort into communication with your customers and try every day to improve your customer service and the customer experience. Along with a professional team, a website, and active social media profiles, goes a modern ITSM tool such as Jira Service Management for your employees and customers. Still, many enterprises make the mistake of defaulting to generic layouts and not fully exploiting the potential. 

But here is precisely where the wheat is separated from the chaff. That is why a personalized Jira Service Management tailored to your customers and employees is a tool that you should not ignore. 

In the end, you’d want to leave an outstanding impression by the very first visit or problem. Right “out of the box”, Jira Service Management offers some native customization possibilities which you absolutely should use. Besides the integrated functions, you can also link your Jira Service Management to a Confluence Wiki and, as an example, extend it and further personalize it with Scroll Viewport. 

Use Case - DAV Jira Service Management with Scroll Viewport

Personalization Jira Service Management

4 essential adjustments to Jira Service Management

1. Adjustment and personalization of the User Interface

Atlassian already integrated some new features for personalizing your customer portal and help center with Jira Service Management Version 4.1. From this version you have the option of adapting the user interface according to your wishes and, for example, adapting it to your corporate identity / design. In this way you ensure that your brand or visual identity is also visible here.

With Service Management Version 4.2, access to the source code was also given. This allows you to personalize your service management even further and adapt it to your needs. However, it must be mentioned at this point that this is not possible without extensive developer knowledge. 

Do you need support in adapting your Jira Service Management customer portal? We would be happy to advise you on all questions relating to service management. Find out more here.

Adaptation of Jira Service Management with the help of plugins

Before you start now and commission your developers to fully adapt the service management, you can first use plugins. 

A plugin with which you can adapt your Jira Service Management instance is“Refined for Jira - Sites and Themes”.This allows you to create appealing support and project management pages with personalized themes, layout and navigation. In addition, the system learns and shows your users pages that are tailored to them. 

Personalization Jira Service Management

Another plugin that allows you to personalize the interface is“Theme Extension for Jira Service Management”.This comes with the function of using preset themes and displaying your content in the form of maps, making information even more accessible to your users. 

2. Set up customer-specific inquiries

The help center is usually one of the first touchpoints that your customers or employees touch in the support process. As a rule, they can then choose from several portals and request types, which is often overwhelming. No matter what question or problem there is, your users should always be able to find the right contact point on your site.

You can create recurring requests in the project settings of your Jira Service Management. It is best to use important keywords or phrases (keyphrases) that best describe the problem your users are facing. For example, you can use the keyword ‘Hardware Issue’ for problems with laptops, printers or other technical office equipment. However, make sure that you always use the language of your users in order to avoid confusion in the topics. 

Also note that ‘Request Type’ and ‘Issue Type’ are not the same. Problems in hardware or software can be different types of inquiries for the user, but are assigned as one issue in your support system.

3. Add custom fields to the request form

Out of the box, only the summary, description and attachment fields are available in the request form in Jira Service Management. But this is often not enough to either describe the problem correctly or to classify it correctly. In addition, the standard terms in Jira are not known to everyone and should therefore be changed in any case.

Jira Service Management offers you the opportunity to set up individual and personalized request types and tailor them to your users. Furthermore, you can also give certain issues a fixed priority or always assign them to the same support employee. 

To be able to create custom requests, you first need to create custom fields that you can then add to the request types. You are spoiled for choice and can add text fields, checkboxes, date pickers, lists or even payment methods.

Source: K15t

4. Linking a knowledge database with Confluence and Scroll Viewport

Your support and service team may not want to answer the same questions over and over again. That is why it often makes sense to expand modern ITSM platforms such as Jira Service Management with a self-service. For example, you can link your Jira to a knowledge database such as Confluence and provide your users with articles with which they can take their problems into their own hands. 

Jira Service Management comes with a standard search function that allows your users to search through the database. Therefore, it makes sense to store answers to frequent customer questions directly in Confluence. 

A tool that links your help center with artificial intelligence and your Confluence pages is Scroll ViewportThis allows your team to continuously improve your help center and expand it with new self-service articles without having to leave the platforms you are using. The ingenious thing about Scroll Viewport is that you can equip your help center with an individual link (custom domain). So your users still have the feeling of being in the vicinity of your company. 

A personalized Jira Service Management makes your users happy

Personalization and customization are essential steps that you should definitely consider when using Jira Service Management. However, the standard settings are often not enough to give your users the flexibility they need to describe their problems or assign them correctly internally. With plugins, themes and individual settings, you can configure your Jira Service Management according to your wishes and requirements. In this way you also ensure that both your employees and customers are satisfied, always find the right information and you can always improve your customer service.

Do you need support in adapting your Jira Service Management customer portal? We would be happy to advise you on all questions relating to service management. Find out more here..

Would you like to learn more about the possibilities of Jira Service Management and Confluence as a knowledgebase? In our use case, we show you how you can use Jira Service Management, Confluence and Scroll Viewport to create a dynamic service desk for an association with 1.3 Million members. have built.

To the Use Case - DAV Jira Service Management with Scroll Viewport