Insurance intranet development

Post-merger insurer uses a global intranet to coordinate its workforce

Influential Software helped this insurer unite staff from multiple companies worldwide through our custom insurance intranet development services.

Device representing insurance intranet development project

Executive brief

Consolidation with global intranet

When several insurance companies merged into a new entity, the company needed to bring its disparate staff and documents together. Influential Software solved this challenge with custom insurance intranet development in SharePoint. The benefits of this global intranet were:

custom user permissions

united documents and processes

better workforce cohesion

full compliance across countries

Wondering how the company achieved this with our insurance intranet development services? Read on to learn more.

The full story

Purple arrow encouraging readers to scroll down for the rest of the insurance intranet development case study

The challenge

Need for post-merger unification

At the time of this project, the insurance company had engaged us to provide support for its pre-existing intranet. This service included remote maintenance and development via VPN, as well as an intranet support helpdesk.


But there was soon another challenge: the company had decided to merge with several smaller insurers under a new name. This merger meant the existing intranet no longer encapsulated all the company’s teams and processes.


Post-merger, the old intranet experienced the following issues:


  • a lack of appropriate user roles and permissions for new staff
  • no ability to coordinate processes across multiple countries
  • a need to meet more complex compliance rules in a multinational context
  • a requirement for rebranding to reflect the company’s new identity


These drawbacks convinced the insurance company that SharePoint intranet development was an urgent necessity.

The solution

Fresh insurance intranet development

Based on our proven SharePoint expertise, the insurer engaged our software engineers to build the new global intranet.


Use of best practices and out-of-the-box functionality wherever possible helped us shorten the intranet build time. This approach meant fewer development hours and greater value for the client.


Through SharePoint Active Directory integration, we created a seamless corporate news hub. Features included custom forms, workflows, and metadata-based navigation tools. We specified distinct access permissions for users based on their roles within the company.


Finally, we linked the intranet to the company’s internal and external applications, providing a single interface for all business processes.

The benefits

Supporting the company’s new identity

With the global intranet in place, the insurance company was able to manage its new workforce effectively across countries. Staff had the tools they needed to complete their business tasks quickly and efficiently. And the business was safe from the risk of data compliance breaches.


In summary, the outcomes of this insurance intranet development project were:


  • bringing staff from several companies together under one banner
  • coordinating multiple teams’ work across divisions and countries
  • keeping all staff informed of company news and regulations
  • enabling collaboration while maintaining compliance
  • providing security through role-based access permissions


Following on from this success, the company has since engaged Influential to migrate its intranet to the latest SharePoint version. We also continue to provide ad-hoc intranet development and support whenever required.

Work with intranet specialists

From insurance to banking, retail to county councils, organisations of all sizes trust our intranet solutions. Find out more on our digital portals page.


5th January 2021
SharePoint, intranet, digital portals, software development, Active Directory

Privacy Preference Center




Analytics cookies collect information that is used either in aggregate form to help us understand how our Websites are being used or how effective our marketing campaigns are, or to help us customise our Websites for you.

Google Analytics
The cookie _gcl_au is used by Google Analytics to understand user interaction with the website.

For example, in order for Google Analytics to determine that two distinct hits belong to the same user, a unique identifier, associated with that particular user, must be sent with each hit.

The analytics.js library accomplishes this via the Client ID field, a unique, randomly generated string that gets stored in the browsers cookies, so subsequent visits to the same site can be associated with the same user.

By default, analytics.js uses a single, first-party cookie named _ga to store the Client ID, but the cookie's name, domain, and expiration time can all be customized. Other cookies created by analytics.js include _gid, AMP_TOKEN and _gac_. These cookies store other randomly generated ids and campaign information about the user.

Google Analytics
_gcl_au, _gid, _ga, gtm_preview


WordPress uses cookies for authentication. That means that in order to log in to our WordPress site, you must have cookies enabled in your browser.

There are two types of cookies set by WordPress.
1 — Session cookies — These are ‘strictly necessary’ cookies as WordPress will not be able to function without it.
2 — Comment cookies — These are not ‘strictly necessary’ cookies and are set when users leave a comment on a post.

Wordpress Session cookies:
Users are those people who have registered an account with the WordPress site.

Wordpress comments:
Comments are usually turned off by default.
If by chance they are still active on a post, asides being turned off when spotted, data from these are not saved by Influential.
- When visitors comment on a post, they too get cookies stored on their computer. This is purely a convenience so that the visitor won’t need to re-type all their information again when they want to leave another comment. Three cookies are set for commenters:

Wordpress, Intercom
comment_author_{HASH} comment_author_email_{HASH} comment_author_url_{HASH} wordpress_[hash] wordpress_logged_in_[hash] wordpress_test_cookie wp-settings-{time}-[UID]