What is an intranet? Uses, and how it differs from an extranet and the internet

You told a new hire “the leave form is on the intranet” and the first answer was “which intranet?” Announcements sit in one manager’s e-mail and in another’s WhatsApp group; policies are in the third folder of the shared drive; the lunch menu is on a sheet of paper taped to the door. The information exists in the company, but nobody knows where to look for it. “Intranet” is often named as the cure for this mess, yet not everyone means the same thing: to some it is an internal website, to some a file-sharing space, to others the portal where business processes run. This article simplifies the concept and lists the decisions you need to make when setting one up.

An intranet is a closed web platform open only to an organization’s own employees, bringing announcements, documents, forms and business processes together in one place. It uses the same technology as the internet, meaning a browser and web pages; the difference is that it is not open to everyone. You need a user account to get in, and each user sees only the sections they are authorized to see.

What are an intranet and an extranet? How do they differ from the internet?

In practice the boundaries are blurred. On the same platform, one section can be open only to employees and another to selected external users. What matters is not the name of the technology but who can see what; that is why setup starts from permission design, not from the menu.

What is an intranet used for?

• Announcements and news: management messages, new-starter notes, holidays and policy changes are published in a single feed.
• Document and policy archive: procedures, forms and handbooks are read from a single source, so the question “which version is current?” comes up less often.
• Forms and requests: requests such as leave, asset assignment, support and purchasing go through a recorded flow instead of an e-mail chain.
• People and team directory: it is easy to find who works in which unit and who their manager is.
• Training and onboarding content: a new employee reaches the information they need in the first days on their own.
• Feedback: surveys and suggestion channels carry the employee’s voice to managers.

First-generation intranets were sites you read: news, a phone directory, a lunch menu. Employees gradually stop visiting a page that is only there to be read. Second-generation intranets are where work gets done: leave is requested, approvals are given, visitors are registered. The habit forms because employees do their daily work there. That is the real difference between an “internal website” and a “portal”.

Can you build an intranet with a shared folder, e-mail and WhatsApp?

In a small team, yes, and it is often enough. With a few people, few documents and a single office, a shared folder and an e-mail list do the job; managing a separate platform may be an unnecessary burden. As the company grows, things start to break at these points:

• An announcement goes out by e-mail, but nobody knows who read it and who did not see it.
• The same form sits in three folders in three different versions.
• Permissions are managed by hand, folder by folder; people who do not need certain documents can open them, and people who do need them cannot.
• Closing the access of someone who leaves or changes role gets forgotten.
• Field and production staff have no corporate e-mail address; the message lands in WhatsApp and the record stays on personal phones.

A concrete example: in a two-shift manufacturing company, management sends a new workplace safety instruction by e-mail. Office staff read it, but most line workers have no corporate e-mail address. The instruction is passed on only in part to the group on the shift supervisor’s phone. A month later, when an incident happens, there is no record behind the sentence “we had announced it.” The problem is not management’s indifference; it is that there is no trace showing whose hands the announcement reached.

How do you set up an intranet?

Before choosing any software, setup is a matter of three decisions. Until these three are clear, even the nicest interface stays empty.

Server: where will the platform run?

Whether you run the platform on your own server or in a third-party cloud decides where the data will sit. With a solution running on your own server, access, backup and data location are in your hands; in return you need a person or a service provider to run it. Make the decision together with IT, based on how sensitive the data is.

Users and permissions: who will see what?

Define the user list and the roles up front: employee, unit manager, HR, senior management. For each role, write down which menus will be visible and whether viewing and acting rights are granted separately. Who removes access when someone changes role or leaves is also part of this design. For example, when a manager goes on leave, can the person covering for them be given temporary access, does that access close by itself at the end of the period, and is the change recorded? If the answers to these questions are clear from the start, permissions will not become a headache later.

Content ownership: who will update the page?

Every section needs an owner: internal communications for announcements, HR for policies, IT for information security rules. A page without an owner goes stale over time and employees stop trusting the platform. Starting small helps here too: launch with announcements and one workflow, then add new sections once usage has settled.

Five common mistakes in intranet projects

1. Loading everything on day one. Hundreds of old documents are moved over and it is still unclear which one is current. First pick the few documents people look for most.
2. Leaving permissions for last. The platform is set up open to everyone, then someone wants to restrict it; by then sensitive documents are already in circulation. Design permissions at the start.
3. Building one-way communication. A platform that only flows from management to employees draws little interest. There must also be a channel for requests, questions and feedback.
4. Forgetting mobile. Some employees are not at a computer all day. A platform that does not open on a phone does not reach them.
5. Leaving it without owners. Once the excitement of the launch passes, nobody updates the content. Set section owners and an update rhythm at the very beginning.

What these mistakes have in common is treating an intranet as a software installation. It is really a job of reorganizing how information flows through the organization, and it has more to do with ownership, permissions and habit than with technology.

What sets a corporate portal apart from an intranet?

YazSis KurumsalPortal is the second-generation form of the intranet: alongside announcements, it runs work such as leave, asset assignment, visitors, tasks and requests across 33 modules, on a shared user, permission and notification infrastructure. It runs on the customer’s own server; employees use it from their phone browser without installing an app. On the announcements side, the Announcements & News Management module targets announcements by person, team, department or location, publishes them on a schedule via the portal, e-mail and SMS, and shows who has read them in a distribution report. E-mail and SMS are sent from the organization’s own SMTP and NetGSM accounts.

Which one suits you? If you will only share announcements and documents, a simple internal site may be enough. If employees request leave, open requests, receive assigned assets or host visitors, those jobs need to move into recorded flows; at that point you need not an internal site but a portal with a shared user and permission infrastructure. You do not have to take everything at once either: start with the modules you need, and add new modules to the same infrastructure as the need grows.

If you want to start with the announcement flow, you can see the audience targeting, scheduling and read tracking in detail on the Announcements & News Management page.