Intranet and Portals
An intranet is an internal website accessible only to staff, providing organisational news, policies, service access, and navigation to other systems. Portals extend this concept by aggregating content and functionality from multiple sources into role-specific or context-specific views. For organisations with staff distributed across headquarters, regional hubs, country offices, and field locations, these platforms serve as the primary digital entry point for accessing organisational information and services.
The distinction between intranets and portals reflects architectural rather than functional boundaries. A basic intranet presents static content through a content management system. A portal adds dynamic aggregation, pulling information from HR systems, project databases, and external feeds into personalised dashboards. Most modern implementations blend both approaches, presenting a unified staff experience regardless of underlying complexity.
- Intranet
- Internal web platform providing organisational content, news, policies, and navigation to staff. Access restricted to authenticated users within the organisation.
- Portal
- Web application aggregating content and services from multiple backend systems into unified views, often with personalisation based on role, location, or preferences.
- Content Management System
- Software enabling non-technical users to create, edit, and publish web content without programming knowledge. Powers most intranet implementations.
- Widget
- Self-contained component displaying specific content or functionality within a portal page. Examples include news feeds, calendar views, and system status indicators.
- Taxonomy
- Hierarchical classification structure organising content by topic, department, geography, or other dimensions. Enables consistent navigation and search.
- Social Intranet
- Intranet emphasising interaction and community features: activity streams, user profiles, commenting, and peer-to-peer communication alongside traditional content publishing.
Platform Architecture
Intranet architecture ranges from single-server deployments serving small organisations to distributed systems spanning multiple data centres for global operations. The fundamental components remain consistent across scales: a content management layer for creating and organising information, a presentation layer for rendering pages, an authentication layer controlling access, and integration points connecting to other organisational systems.
+------------------------------------------------------------------+| INTRANET ARCHITECTURE |+------------------------------------------------------------------+| || +------------------------+ +------------------------+ || | PRESENTATION | | AUTHENTICATION | || | | | | || | +--------+ +--------+ | | +------------------+ | || | | Web | | Mobile | | | | Identity | | || | | Browser| | App | | | | Provider | | || | +---+----+ +---+----+ | | | (SSO/SAML) | | || | | | | | +--------+---------+ | || +-----|----------|-------+ +-----------|------------+ || | | | || +-----+----+-------------------------+ || | || v || +--------------------------------+ || | INTRANET PLATFORM | || | | || | +-------+ +-------+ +-------+ | || | | CMS | | Search| | Cache | | || | | Engine| | Index | | Layer | | || | +---+---+ +---+---+ +---+---+ | || | | | | | || +-----|---------|---------|------+ || | | | || v v v || +--------------------------------+ || | CONTENT STORAGE | || | | || | +-------+ +-------+ +-------+ | || | | Pages | | Media | | Meta- | | || | | | | Assets| | data | | || | +-------+ +-------+ +-------+ | || +--------------------------------+ || || +---------------------------+ +---------------------------+ || | INTEGRATION LAYER | | EXTERNAL SYSTEMS | || | | | | || | +-------+ +-------+ | | +-------+ +-------+ | || | | API | | Web |<------+--->| | HRIS | | Project| | || | | Gateway| | hooks | | | | | | Mgmt | | || | +-------+ +-------+ | | +-------+ +-------+ | || | | | | || | +-------+ +-------+ | | +-------+ +-------+ | || | | RSS | | Email |<------+--->| | Calendar| | News | | || | | Feeds | | Notif | | | | | | Feeds | | || | +-------+ +-------+ | | +-------+ +-------+ | || +---------------------------+ +---------------------------+ |+------------------------------------------------------------------+The content management engine stores pages, media assets, and metadata in a structured database. Search indexing occurs either in real-time as content changes or through scheduled crawls, depending on platform capabilities and content volume. A caching layer reduces database load for frequently accessed pages, with cache invalidation triggered by content updates.
Authentication integrates with the organisation’s identity provider through SAML or OpenID Connect, enabling single sign-on from other organisational systems. This integration eliminates separate intranet credentials and ensures access terminates automatically when staff leave the organisation.
The integration layer connects the intranet to backend systems, enabling dynamic content display. A country office portal might show pending leave requests from the HR system, upcoming project deadlines from the programme management system, and recent announcements from headquarters. These integrations use APIs where available, falling back to RSS feeds or scheduled data imports for systems lacking API support.
Platform Options
Intranet platforms divide into purpose-built social intranets designed specifically for internal communication, collaboration platforms with intranet capabilities, general-purpose content management systems adapted for internal use, and collaboration suite components. Selection depends on existing infrastructure, technical capacity, budget, and specific requirements around social features, content management depth, and integration.
Purpose-Built Open Source Intranets
HumHub provides a social intranet specifically designed for internal organisational communication. The platform centres on spaces (collaborative areas for teams, projects, or topics), activity streams showing recent content and interactions, and user profiles enabling staff discovery. Built-in modules cover wikis, files, calendars, tasks, and polls. The modular architecture allows enabling only required features, keeping the interface focused. HumHub runs on PHP with MySQL or MariaDB, deployable on modest infrastructure. LDAP and SAML integration connects to enterprise identity providers. The platform suits organisations prioritising social interaction and community building over complex content hierarchies. Active development continues with regular releases, and commercial support is available alongside the open source community edition.
Open Social builds on Drupal to deliver a complete social intranet and community platform. Developed by GoalGorilla with explicit focus on nonprofits, NGOs, and social enterprises, Open Social packages Drupal’s power into an accessible distribution requiring minimal Drupal expertise to deploy. Features include activity streams, events, groups, topics, and content management. The platform handles multilingual content natively, relevant for international organisations. Open Social inherits Drupal’s extensive integration capabilities while hiding architectural complexity behind a streamlined interface. Organisations gain Drupal’s flexibility for future customisation without requiring Drupal expertise at launch. The platform runs on standard Drupal infrastructure: PHP with MySQL, MariaDB, or PostgreSQL.
Tiki Wiki CMS Groupware combines wiki, CMS, and groupware in a single integrated application rather than bolting together separate components. Built-in features span wikis, blogs, forums, file galleries, calendars, trackers (structured data), workflows, and forms. This breadth makes Tiki suitable for organisations wanting comprehensive functionality without managing multiple integrations. The all-in-one approach means features work together natively: wiki pages can embed tracker data, workflows can route forum posts, calendars can pull from trackers. Tiki runs on PHP with MySQL or MariaDB. The unified architecture reduces integration complexity at the cost of flexibility to swap individual components.
eXo Platform offers an enterprise-grade open source digital workplace combining intranet, collaboration, and knowledge management. Features include activity streams, spaces, wikis, documents, calendars, and task management. The platform emphasises integration through its app centre and API framework. eXo runs on Java application servers, requiring more infrastructure expertise than PHP alternatives but offering robust scalability. Community and enterprise editions exist, with the community edition providing full functionality suitable for most organisations.
Collaboration Platforms with Intranet Capabilities
Nextcloud evolved from file synchronisation into a comprehensive collaboration hub with substantial intranet capabilities. The dashboard provides a personalised starting point displaying activity, notifications, calendar events, and widgets pulling from various sources. Nextcloud includes collaborative document editing (through Collabora Online or OnlyOffice integration), calendar, contacts, mail client, and video conferencing (Talk). The app ecosystem extends functionality with news readers, forms, project boards, and announcement tools. For organisations already using or considering Nextcloud for file storage, extending it as an intranet avoids deploying separate platforms. Nextcloud runs on PHP with MySQL, MariaDB, or PostgreSQL, with extensive documentation supporting various deployment configurations including Docker.
Mattermost provides team messaging with increasingly broad collaboration features. While primarily a Slack alternative, Mattermost’s Boards (kanban and project management), Playbooks (workflows and runbooks), and channel organisation create intranet-adjacent capabilities. Organisations centring internal communication on persistent chat rather than traditional web pages find Mattermost addresses core intranet needs differently. The platform runs on Go with PostgreSQL or MySQL, offering excellent performance characteristics. Self-hosted deployment gives complete data control. Mattermost integrates with identity providers through SAML and supports extensive webhook and API integrations.
ONLYOFFICE Workspace combines document editing with project management, mail, calendar, CRM, and community features in an integrated platform. The community features provide blog, forum, wiki, and bookmarks suited for intranet use. Organisations choosing ONLYOFFICE for document collaboration gain intranet capabilities without additional platforms. The platform runs as Docker containers or native installation on Linux servers.
Content Management Systems Adapted for Intranet Use
General-purpose CMS platforms serve as intranets when social features matter less than content management sophistication. These options suit organisations with existing CMS expertise, requirements for complex content architecture, or needs to integrate heavily with external web properties using the same platform.
Drupal offers the most sophisticated content architecture among CMS options. The platform separates content structure from presentation, enabling reuse across contexts. A policy document entered once appears in policy libraries, relevant department pages, and search results with consistent metadata. Drupal’s permissions system supports granular access control by role, department, and content type. Open Social (described above) provides a quicker path to Drupal-powered intranet than building from scratch. Direct Drupal implementation suits organisations with Drupal expertise wanting maximum architectural control.
Wagtail provides a modern Python-based CMS with excellent content modelling. Built on Django, Wagtail offers a streamlined editor interface while supporting complex page types and relationships. Organisations with Python development capacity find Wagtail more maintainable than PHP alternatives. Multi-site support enables managing multiple intranets from single installations.
WordPress with membership plugins provides the most accessible CMS-based option for organisations lacking dedicated technical staff. Converting WordPress to intranet requires membership plugins restricting access, identity provider integration through SAML plugins, and search engine indexing prevention. The approach works for basic content publishing but lacks native social intranet features.
Commercial Platforms with Nonprofit Programmes
Microsoft SharePoint integrates with Microsoft 365 deployments, providing intranet capabilities alongside document management, team sites, and workflow automation. Organisations using Microsoft 365 through nonprofit programmes access SharePoint within existing subscriptions. SharePoint sites inherit Microsoft 365 permissions, search integrates with other Microsoft content, and the platform connects natively to Teams, Outlook, and other Microsoft services. Data residency depends on tenant configuration, with CLOUD Act considerations for US-headquartered hosting.
Google Sites within Google Workspace provides basic intranet capabilities for organisations using Google’s collaboration suite. Sites offers drag-and-drop page building with automatic integration to Drive, Calendar, and other Workspace components. The platform lacks advanced features found in dedicated intranet solutions but requires no additional licensing or infrastructure. Suitable for small organisations needing simple internal sites.
Confluence from Atlassian serves organisations using Atlassian products for project management and development. The platform combines wiki-style editing with structured spaces and templates. Atlassian offers community licensing for registered nonprofits, providing free access to cloud products for qualifying organisations.
Selection Framework
Platform selection begins with understanding primary intranet purpose. Social intranets emphasising staff interaction and community suit purpose-built platforms like HumHub or Open Social. Content-heavy intranets with complex information architecture suit Drupal or Wagtail. Organisations wanting to extend existing investments consider Nextcloud (if already deployed for files), SharePoint (if committed to Microsoft 365), or Mattermost (if centring communication on chat).
+-------------------------------------------------------------------+| PLATFORM SELECTION FRAMEWORK |+-------------------------------------------------------------------+| || Primary Purpose || | || v || +----+----+ +----+----+ +----+------+ +----+-----+ || | Social | | Content | | Extend | | Simple | || | interact| | publish | | existing | | content | || +---------+ +---------+ +-----------+ +----------+ || | | | | || v v v v || +---------+ +---------+ +-----------+ +----------+ || | HumHub | | Drupal/ | | Nextcloud | | WordPress| || | Open | | Open | | Mattermost| | Google | || | Social | | Social | | SharePoint| | Sites | || | eXo | | Wagtail | | | | | || +---------+ +---------+ +-----------+ +----------+ || || Additional Factors: || +-------------------------------------------------------------+ || | Technical capacity | Self-host viable? Drupal/Python skills?| || | Data sovereignty | Self-host required? Jurisdiction? | || | Integration needs | API availability? Existing connectors? | || | Multilingual | Native support? Translation workflow? | || | Mobile/offline | PWA? Native apps? Offline sync? | || +-------------------------------------------------------------+ |+-------------------------------------------------------------------+Technical capacity determines whether self-hosted options are viable. HumHub and Nextcloud require standard PHP hosting achievable with modest Linux administration skills. eXo and Mattermost require more infrastructure expertise. Open Social and Drupal require Drupal knowledge for customisation. Organisations lacking technical capacity or preferring operational simplicity deploy managed SaaS offerings or collaboration suite components.
Data sovereignty requirements influence hosting decisions. Self-hosted options provide complete data control on infrastructure within any jurisdiction. Cloud offerings introduce vendor jurisdiction considerations and data residency constraints.
Integration requirements shape decisions when the intranet must pull content from specific backend systems. Drupal and eXo offer the most extensive integration capabilities. Purpose-built social intranets provide standard integrations but less flexibility for custom requirements.
Content Governance
Intranet content requires ongoing governance to remain accurate, current, and useful. Without governance structures, intranets accumulate outdated pages, broken links, and contradictory information that erodes staff trust in the platform. Effective governance assigns clear ownership, establishes review cycles, and provides mechanisms for quality control.
Content ownership assigns responsibility for specific content areas to individuals or teams. The HR department owns employee handbook pages, the IT team owns service documentation, programme teams own project information. Ownership includes authority to create and edit content within the assigned area, responsibility for accuracy, and accountability for review cycles. A published ownership matrix prevents disputes over who maintains specific content and identifies gaps where no owner exists.
Review cycles ensure content remains current. Annual review suits stable reference content like policies and procedures. Quarterly review applies to content referencing external factors that change more frequently, such as donor requirements or regulatory guidance. News and announcements require no review cycle but should archive automatically after defined periods to prevent the common intranet problem of “news” sections showing items from several years ago.
Publishing workflows control content quality before publication. A minimal workflow requires author submission and editor approval. More complex workflows add legal review for policy content, communications review for external-facing messaging, or technical review for IT documentation. Workflow complexity should match content risk: routine departmental updates need less scrutiny than organisation-wide policy changes.
+----------------------------------------------------------------+| CONTENT PUBLISHING WORKFLOW |+----------------------------------------------------------------+| || +----------+ || | Author | || | creates | || | draft | || +----+-----+ || | || v || +----+-----+ +----------+ || | Submit +---->| Editor | || | for | | review | || | review | +----+-----+ || +----------+ | || | || +-----------+-----------+ || | | || v v || +----+-----+ +-----+----+ || | Approved | | Changes | || | | | required | || +----+-----+ +-----+----+ || | | || | v || | +-----+----+ || | | Return | || | | to author| || | +-----+----+ || | | || | +-----------+ || | | || v v || +----+-----------+----+ || | | || | PUBLISHED | || | | || +----------+----------+ || | || v || +----------+----------+ || | Scheduled review | || | (based on content | || | type) | || +---------------------+ || |+----------------------------------------------------------------+Archival policies address content that reaches end of life. Time-limited content like event announcements should archive automatically on specified dates. Superseded content like previous policy versions requires explicit archival when replacements publish. Archived content remains accessible through direct links or search but no longer appears in navigation or content listings. Some organisations require permanent deletion of archived content after retention periods expire, necessitating integration with records management processes.
Information Architecture
Information architecture determines how staff find content on the intranet. Poor architecture forces staff to rely on search for everything, unsuccessfully when they cannot formulate effective queries. Effective architecture provides multiple paths to content: hierarchical navigation for browsing, search for known-item finding, and cross-linking for discovery.
Navigation structure combines departmental organisation with functional categories. A primary navigation might include sections for News, Departments, Services, Policies, and Resources. Within Departments, each unit maintains its own section with team information, contacts, and department-specific content. The Services section organises content by what staff need to do rather than which department provides it: IT support, HR requests, travel booking, expense claims. This dual structure accommodates both “I need to contact Finance” and “I need to submit an expense claim” mental models.
Taxonomy provides consistent classification across content. A well-designed taxonomy enables faceted search filtering and related content suggestions. Core taxonomy dimensions include department or unit, content type (policy, procedure, form, news), topic or subject area, and geographic applicability. Content receives tags from each relevant dimension, enabling queries like “all IT policies applicable to Kenya” through combined filtering.
Search configuration determines whether staff can find content effectively. Enterprise search platforms index intranet content alongside other organisational repositories, providing unified search across intranets, document management systems, and other sources. Intranet-specific search indexes only intranet content but receives deeper configuration. Search tuning includes synonym handling (staff searching “holiday” should find “annual leave” content), acronym expansion, and relevance weighting that prioritises recent content and authoritative sources.
+------------------------------------------------------------------+| INFORMATION ARCHITECTURE |+------------------------------------------------------------------+| || +------------------------+ +------------------------+ || | NAVIGATION | | TAXONOMY | || | (hierarchical) | | (classification) | || | | | | || | News | | Department | || | Departments | | - Finance | || | - Finance | | - Programmes | || | - HR | | - IT | || | - IT | | | || | - Programmes | | Content Type | || | Services | | - Policy | || | - Submit expense | | - Procedure | || | - Request leave | | - Form | || | - IT support | | - News | || | Policies | | | || | Resources | | Geography | || | | | - Global | || +------------------------+ | - East Africa | || | - Kenya | || +------------------------+ +------------------------+ || | SEARCH | || | (discovery) | +------------------------+ || | | | CROSS-LINKS | || | Full-text indexing | | (relationships) | || | Faceted filtering | | | || | Synonym handling | | Related policies | || | Relevance ranking | | See also | || | | | Parent/child pages | || +------------------------+ +------------------------+ || |+------------------------------------------------------------------+Personalisation and Targeting
Personalisation tailors intranet content to individual staff members based on their profile attributes, behaviour, or explicit preferences. Targeting delivers specific content to defined audience segments without requiring individual configuration. Both mechanisms address the challenge of presenting relevant information to staff with diverse roles, locations, and interests.
Profile-based personalisation uses attributes from the identity provider or HR system to customise the intranet experience. A staff member based in Kenya sees Nairobi office news prominently while London headquarters updates appear in a secondary section. A programme manager sees project dashboards and donor reports while a finance officer sees budget summaries and payment queues. The intranet queries user attributes at login and adjusts content presentation accordingly.
Location-based targeting delivers content to staff in specific geographic areas. An announcement about office closure due to local conditions reaches only affected staff rather than the entire organisation. Emergency communications target specific countries or regions. This targeting requires accurate location data in staff profiles and mechanisms for staff temporarily in different locations to receive relevant local information.
Role-based targeting segments content by job function or level. Leadership communications might target managers and above. Technical bulletins target IT staff. Safeguarding updates target programme staff. The targeting system references role classifications from the HR system, requiring consistent role taxonomy across systems.
Behavioural personalisation adapts content based on staff interactions. Frequently visited sections appear prominently. Related content suggestions reflect previous reading patterns. This approach requires analytics infrastructure tracking user behaviour and recommendation algorithms processing that data. Privacy considerations apply: staff should understand what behavioural data the intranet collects and how it influences their experience.
+------------------------------------------------------------------+| PERSONALISATION MODEL |+------------------------------------------------------------------+| || +----------------+ || | User Profile | || | | || | - Department | || | - Location | || | - Role | || | - Language | || +-------+--------+ || | || v || +-------+--------+ +------------------+ || | Personalisation|<----| Content Targeting| || | Engine | | Rules | || +-------+--------+ +------------------+ || | || v || +-------+--------+ || | Page Assembly | || | | || | +------------+ | || | | Global nav | | || | +------------+ | || | +------------+ | || | | Targeted | | <-- Based on location/role || | | news | | || | +------------+ | || | +------------+ | || | | Role | | <-- Based on job function || | | dashboard | | || | +------------+ | || | +------------+ | || | | Local | | <-- Based on office location || | | content | | || | +------------+ | || +----------------+ || |+------------------------------------------------------------------+Multi-Office and Multilingual Considerations
Organisations operating across multiple countries face additional intranet complexity. Content relevance varies by location, language preferences differ, and connectivity constraints affect platform design. Addressing these factors requires architectural decisions about content structure, translation workflows, and performance optimisation.
Content scoping determines what content applies where. Global content like organisational policies applies everywhere. Regional content like East Africa programme updates applies to multiple countries. Local content like Nairobi office building access procedures applies to single locations. The intranet presents appropriately scoped content to each user while maintaining global coherence.
Multi-site architecture enables distinct intranet instances for different locations while sharing common elements. A headquarters intranet, regional intranets, and country office intranets operate as separate sites with shared navigation, branding, and global content. This architecture allows local autonomy over local content while maintaining organisational consistency. Staff see a unified experience despite content originating from multiple sources.
Translation workflows handle multilingual content requirements. Machine translation provides rapid first drafts but requires human review for accuracy, particularly for policies and procedures where mistranslation carries risk. Professional translation ensures quality but introduces delay and cost. The workflow tracks translation status, prevents publication of outdated translations when source content changes, and indicates clearly when translations are unavailable.
Language presentation offers staff their preferred language where translations exist, with fallback to the source language for untranslated content. Language preference derives from user profile settings or browser language headers. Content displays language indicators showing whether the current version is original or translated, enabling staff to access source content when preferred.
Performance optimisation addresses connectivity constraints in field locations. Content delivery networks cache static assets at geographic edge locations, reducing latency for images, stylesheets, and scripts. Aggressive caching of infrequently changing content reduces bandwidth requirements. Image optimisation reduces file sizes while maintaining acceptable quality. Progressive enhancement ensures core content loads first, with enhanced features loading as bandwidth allows.
Offline access extends intranet utility to disconnected contexts. Service workers cache key pages for offline viewing. Mobile applications download content libraries for offline reference. Synchronisation protocols update cached content when connectivity resumes. Critical content like emergency procedures, contact directories, and essential policies prioritises offline availability.
Mobile Access
Staff increasingly access intranets from mobile devices, particularly field-based personnel whose primary computing device is a smartphone. Mobile access strategies range from responsive web design ensuring the intranet displays correctly on small screens to dedicated mobile applications with offline capabilities.
Responsive design adapts intranet layout to screen dimensions. Navigation collapses into menus suitable for touch interaction. Content reflows to single-column layouts readable without horizontal scrolling. Images scale proportionally. Tables transform into card-based displays or horizontal scrolling regions. This approach maintains a single codebase serving all devices, reducing development and maintenance effort.
Progressive web applications extend responsive web capabilities with app-like features. Service workers enable offline access to cached content. Push notifications alert staff to important updates. Home screen installation creates app icons without app store distribution. PWAs suit organisations wanting mobile app functionality without native application development.
Native mobile applications provide the richest mobile experience but require separate development for iOS and Android platforms. Native apps access device features like cameras, biometrics, and local storage more fully than web applications. Offline synchronisation handles larger content volumes more reliably. Push notifications integrate with operating system notification centres. Native development costs more than responsive web but proves justified for organisations with substantial field workforces relying primarily on mobile devices.
Platform-specific mobile apps ship with several intranet solutions. HumHub, eXo Platform, Nextcloud, and Mattermost all provide official mobile applications for iOS and Android. These pre-built apps eliminate custom mobile development for organisations deploying those platforms.
Analytics and Engagement
Analytics measure intranet usage, identifying popular content, underutilised sections, and navigation patterns. Engagement metrics assess whether staff find the intranet valuable and use it effectively. Together, these measurements inform content strategy, identify improvement opportunities, and demonstrate intranet value to stakeholders.
Page view analytics track what content staff access. High-traffic pages warrant prominent placement and careful maintenance. Low-traffic pages require investigation: does the content lack relevance, visibility, or quality? Self-hosted analytics platforms like Matomo and Plausible provide web metrics without third-party data sharing. Matomo in particular offers detailed analytics suitable for intranet use, including heatmaps and session recordings in its paid tiers.
Search analytics reveal what staff seek and whether they find it. Failed searches indicate content gaps or search configuration problems. Frequent searches for specific terms suggest navigation improvements that surface popular content more prominently. Search term analysis identifies emerging information needs before formal content requests arrive.
Engagement metrics measure intranet contribution to staff effectiveness. Survey instruments assess perceived usefulness, ease of finding information, and content quality. Task completion studies measure whether staff can accomplish specific goals using the intranet. Net Promoter Score approaches ask whether staff would recommend the intranet to colleagues, providing a single comparable metric over time.
User feedback mechanisms enable staff to report problems and suggest improvements directly. Feedback widgets on each page capture page-specific input. Contact forms or email addresses receive general feedback. Feedback requires triage and response processes to demonstrate that input receives attention.
Governance dashboards track content health metrics: pages overdue for review, content without assigned owners, broken links, outdated references. These operational metrics support content governance by highlighting maintenance requirements before problems affect staff experience.
Implementation Considerations
Organisations with Limited IT Capacity
HumHub provides the most accessible purpose-built intranet for organisations without dedicated technical staff. The platform installs on standard PHP hosting with MySQL, achievable through managed hosting providers or simple Linux VPS configurations. The installer guides configuration, and the admin interface enables ongoing management without command-line access.
Implementation requires:
- Hosted environment with PHP 8.0+ and MySQL 5.7+
- SMTP configuration for email notifications
- LDAP or SAML configuration connecting to identity provider
- Initial space structure reflecting organisational units
- Essential modules enabled: wiki, files, calendar, polls
Initial deployment achieves functional social intranet within 1-2 weeks. A single person maintaining the platform alongside other duties can sustain this implementation. Content creation distributes across the organisation through space administrators.
For organisations already using Nextcloud for file sharing, extending it with dashboard, announcements, and forms apps provides intranet capabilities without deploying additional platforms. This approach trades purpose-built intranet features for reduced platform complexity.
Organisations preferring managed services without self-hosting explore commercial options. Several purpose-built intranet vendors offer nonprofit pricing, and Microsoft 365 nonprofit subscriptions include SharePoint for organisations accepting Microsoft’s ecosystem.
Organisations with Established IT Functions
Organisations with dedicated IT staff and infrastructure capacity choose from the full platform range based on specific requirements.
Open Social suits organisations wanting sophisticated content management alongside social features, particularly those with multilingual requirements or complex information architecture. The Drupal foundation provides extensive customisation potential. Implementation spans 2-4 months with dedicated resources, including content migration, theme development, and integration work.
eXo Platform suits organisations wanting comprehensive digital workplace functionality with strong integration capabilities. The Java platform requires more infrastructure expertise but scales well for large deployments. Commercial support options provide implementation assistance and ongoing maintenance.
Nextcloud with collaboration apps suits organisations wanting unified file storage, collaboration, and intranet capabilities. This approach reduces platform count and simplifies the technology landscape. Implementation builds on existing Nextcloud deployments or establishes new installations.
Self-hosted platforms provide complete data control, relevant for organisations with data sovereignty requirements or operating in contexts where third-party cloud services introduce risk.
Organisations with Federated Structures
Federated organisations with autonomous country offices or member organisations face unique intranet challenges. Centralised intranets cannot serve diverse local needs. Fully decentralised approaches lose organisational coherence and duplicate effort.
Hybrid architectures provide global content and navigation centrally while enabling local sites for country-specific content. HumHub spaces can represent country offices with local administration. Open Social and Drupal support multi-site configurations. SharePoint hub sites connect multiple site collections into coherent navigation.
Governance requires clear delineation of central versus local content responsibility. Global policies and standards publish centrally. Country-specific procedures and local news publish locally. Navigation and branding maintain consistency while allowing local identity expression.
Multi-tenant platforms serve consortia or membership organisations where distinct entities require separate intranets with shared infrastructure. Each tenant operates an independent intranet while sharing platform costs and technical maintenance.
Migration Considerations
Migrating from existing intranets involves content inventory, migration tooling, redirect mapping, and user transition. Content inventory identifies what exists on the current platform, its ownership, and its continued relevance. Migration provides opportunity to retire outdated content rather than carrying it forward.
Automated migration tools extract content from source platforms and import to target platforms. Migration fidelity varies: text content transfers cleanly while complex formatting, embedded media, and interactive elements require manual recreation. Migration testing in staging environments identifies problems before cutover.
URL redirects preserve links to migrated content. Staff bookmarks, external references, and search engine results pointing to old URLs redirect to new locations. Redirect mapping becomes impractical for sites with thousands of pages; in such cases, redirecting old site URLs to search results for equivalent queries provides partial continuity.
User transition requires communication and training. Advance announcement prepares staff for change. Training resources explain new navigation and features. Support channels address questions during transition. Post-migration feedback collection identifies problems requiring attention.