Definition:
An intranet is a private digital environment that uses network and web technologies to share information, applications and resources within an organisation. Access is limited to authorised people, teams or partners and is controlled through identities, permissions and internal policies.
Although it may use the same protocols as the Internet, an intranet is not a public part of the Web. Its scope is defined by the organisation and may range from a document portal to a workspace with search, directories, communications, approval workflows and access to corporate tools.
How an intranet works
An intranet combines a private access layer with digital services intended for a defined group. It may be hosted on an organisation’s own servers, on cloud computing infrastructure or in a hybrid model. Users normally enter through a browser or application after confirming their identity.
Its operation depends on several components working together to show each person the resources relevant to them:
- Identity and permissions: They authenticate users and determine which areas, documents or actions are available to each profile.
- Content and applications: They bring together internal news, policies, forms, calendars, knowledge bases and work tools.
- Network and connection: They carry information through protocols such as TCP/IP and HTTPS, both on the premises and from authorised remote locations.
- Search and organisation: They classify resources using menus, metadata, categories and internal search engines.
Remote access may be protected with a VPN, an access proxy, multi-factor authentication or other technologies. However, a VPN and an intranet perform different functions: the former establishes a protected connection, while the latter provides the internal content and services.
What an intranet is used for
An intranet acts as a common entry point to an organisation’s information. Its main purpose is to reduce the fragmentation of documents and channels, make resources easier to find and maintain a recognised version of policies, procedures or forms.
Specific uses depend on the activity and structure of each organisation. Common examples include:
- Internal communication: Publishing notices, news, events and messages for the whole workforce or selected groups.
- Document management: Organising manuals, templates, policies and files with permissions and version control.
- Collaboration: Sharing project spaces, calendars, tasks and working materials.
- Employee services: Centralising requests, directories, training, onboarding and access to applications.
- Knowledge management: Retaining procedures, resolved questions and experience that would otherwise remain scattered among people and tools.
An intranet does not have to hold every system physically. It can act as a portal that integrates existing applications and presents different access points according to a user’s role, department, location or project.
Origin and evolution
Organisations had internal networks before the Web, but the concept of an intranet spread during the 1990s as businesses and institutions began using Internet protocols and web browsers on private networks. This made it possible to present internal information through tools similar to those used by public websites.
Early intranets often focused on static pages, directories and document repositories. Over time, they added content management systems, search engines, forums, workflows and connections to corporate systems. Distributed work later increased the importance of secure access away from the office and cloud-hosted services.
Today, the term covers both traditional internal portals and digital workplace environments that bring content and applications together. The technology may change, but the central idea remains: a restricted space governed by the organisation.
Differences from the Internet and an extranet
The Internet, an intranet and an extranet may share technologies, but they differ in audience and access control. The Internet is a global public network; an intranet serves an organisation’s internal environment; and an extranet opens a limited part of those resources to authorised third parties.
For example, a company may publish commercial information on its website, manage policies and tools on its intranet and provide suppliers with an ordering area on an extranet. The difference depends not only on where each service is hosted, but also on who can access it, which identity they use and which permissions they receive.
Advantages and limitations
When it is well organised, an intranet makes shared information easier to access, avoids duplication and allows documents to be updated from a central point. It can also shorten internal searches and processes, especially when it integrates the directory, search engine and applications used every day.
These advantages are not automatic. A confusing structure, poor search, content without an owner or incorrectly configured permissions can turn it into another difficult repository. Adoption also falls when important information remains scattered across email, folders and parallel tools.
Intranet governance
Managing an intranet covers technical security as well as editorial maintenance. The organisation needs to define owners, publishing criteria, review periods and rules for archiving content. Each user should have only the access required for their role.
Common controls include multi-factor authentication, encrypted communications, backups, activity logging and periodic permission reviews. Accounts and access also need to be removed when a person’s relationship with the organisation changes. A private intranet reduces public exposure, but it cannot by itself eliminate mistakes, compromised credentials or insider threats.