IT Department Intranet Software

The IT department has a dual role in Intranet deployment - they are concerned both with the project itself as stakeholders and they are a department with their own functional requirements.

 Read Case Study

The IT Department Intranet Functional Requirements

The IT department have similar needs as other departments in terms of information provision and access. They will have policies and operational documents that need version controlling and sharing with the correct members of staff and will normally have some key team members introduced on departmental pages as well as staff directories
They also have particular departmental requirements in terms of IT work :

IT Department Functional Requirements

The Support Desk

This can be provided using the Business Process Management engine of Claromentis - or they may wish to make sure that either an existing support desk can be accessed from the intranet - or relevant ticket summaries can be displayed back to the user.

The Support Desk


IT often need to make important time limited important announcements concerned with system availability, upgrades and other events that can impact the service to users.


Knowledge Base

The knowledge base with it's strong support for videos can make an ideal platform for tips and tricks so that IT can provide focussed information on various technology aspects to help users. It also has strong functionality for asking questions and endorsing answers - IT is often a category within the knowledge base.

Knowledge Base

Interactive Channels

They often have a wish to humanise what is sometimes seen as a faceless function accessed only in times of stress - social streams provide not only quick access in terms of questions and shared experience but also a warmer way of interacting than the more formal support ticketing systems

Social streams in IT Departments

Project Role

Although with modern Intranets IT skills are not required to launch or maintain the system, the IT department will certainly be involved in the project at the early stages. Their interests are normally centered on the following top 10 IT factors when considering an Intranet :

Project Role

  • Technology sets: What technology is used in the solution and what implications are there for cross platform portability, licensing costs, databases required, longevity and internal support.

  • The deployment options: IT departments have preferences about cloud vs on-premise deployments.

  • Disaster Recovery: How easy is it to restore the access after various failure scenarios?

  • Security: How is security of access and information assured?

  • Integration: What options are available for integration with existing systems and data? The intranet has a key role in presenting summaries from external systems to certain users and this should be facilitated in the platform chosen.

  • Support for existing user access systems: Although Active Directory dominates the market in terms of the central database controlling user access alternatives are used. The system must be able to integrate seamlessly and provide single sign on and carry over any existing permissions into the intranet.

  • Support for custom development: Even with the broad functionality provided by modern intranet platforms like Claromentis there will often be a need for custom development. The IT team may wish to code themselves, or be reassured that there is a vendor custom team, or that service is provided by an external community of developers who are familiar with the API.

  • Browser Support: Customers often force particular browser versions for users - either for support reasons or because a legacy application is preventing upgrades. The intranet is a core platform and what browsers it supports is an important access - especially as the digital workplace extends out beyond the firewalls and users may have their own browser preferences when not in the office.

  • Mobile Support: Mobile access is important for most organisations and critical for certain sectors like construction. The It department will normally review the responsive browser design and also the functionality of the local applications provided for both IoS and Android.

  • Scalability: How scalable is the solution - does it support multiple application servers? If on premise can it easily be deployed and scaled in the VM or physical server environment that the company uses?

How can we help?