Droptica Outlines Drupal Extranet Planning for Client and Partner Portals

Planning guidance from Droptica explains how Drupal can support extranets for clients, partners, resellers, and sales agents, with emphasis on authenticated access, content modelling, and per-user data. Maciej Lukianski outlined the approach in a blog post published on 24 June 2026. The post distinguishes extranets from employee-facing intranets and treats them as controlled portals for price lists, order information, training material, and account-specific documents.

The guide is most useful for teams planning gated Drupal areas because it separates access into public, audience-gated, and per-user layers. It recommends entity reference fields to connect accounts with companies, orders, partner tiers, and other data, so dashboard views can be filtered by the current user rather than hard-coded around individual cases. It also warns that per-user access must verify ownership on every request and should not rely on editable URL parameters.

For access control, the post identifies Group, Permissions by Term, and Content Access as relevant options, depending on whether access is organised around companies, taxonomy terms, or content types. It also points to Search API, Gin, Drupal core's Content Moderation, Views Bulk Operations, Dynamic Page Cache, BigPipe, private file storage, and noindex handling as operational concerns for authenticated portals. The post does not provide version numbers or configuration examples, so it should be read as an architecture-level checklist rather than an implementation tutorial.