ClientPress is built around two levels of structure: portals and hubs. Understanding how they relate to each other will help you organize your client work effectively.
Portals #
A portal is the top-level container for a client relationship. Each portal has its own URL, branding, team members, and features. Portals are created and managed in your WordPress admin under Portals → All Portals.
Every portal supports:
- A primary client (one account)
- Additional sub-clients (multiple accounts)
- Assigned project managers
- Its own accent color, logo, and icon
- All enabled tabs: Discussion, Tasks, Files, Deliverables, and more
Portal URLs follow this pattern:
yoursite.com/client-portal/{portal-slug}/
Hubs (Child Portals) #
A hub is a child portal nested underneath a parent portal. Hubs share the same client access as the root portal — you do not need to reassign clients or project managers to each hub individually.
Hubs are useful when a single client has multiple distinct workstreams, projects, or departments that each need their own separate space.
Example:
- Portal: Acme Corp
- Hub: Website Redesign
- Hub: Brand Identity
- Hub: Q3 Campaign
Each hub is a fully independent portal space with its own Discussion, Tasks, Files, Deliverables, Tools, and all other tabs. Content in a hub (files, tasks, messages, etc.) is scoped entirely to that hub and does not appear in the parent portal or other hubs.
Each hub has its own URL:
yoursite.com/client-portal/acme-corp/website-redesign/
Individual views within a hub follow the same pattern:
yoursite.com/client-portal/acme-corp/website-redesign/files/
yoursite.com/client-portal/acme-corp/website-redesign/tasks/
How Hubs Appear to Clients #
When a portal has hubs, a Hubs tab appears in the portal navigation. Clicking it opens a dropdown listing all available hubs. Clients click a hub name to enter that space.
If no hubs exist, the Hubs tab is hidden by default. You can control this behavior under Settings → ClientPress → Features → Hide Hubs tab when empty.
Creating a Hub #
- Open the parent portal in your WordPress admin.
- In the portal navigation area (visible when viewing the portal), click New Hub — or —
- Go to Portals → Add New and set the Parent Portal field in the sidebar to the root portal.
- Give the hub a title, configure its settings, and publish it.
The hub will immediately appear under the parent portal’s Hubs dropdown for any user who has access to that portal.
Access and Permissions #
Hubs inherit access from the root portal. This means:
- The primary client of the root portal can access all its hubs automatically.
- Sub-clients assigned to the root portal can also access all hubs.
- Project managers assigned to the root portal have access to all hubs.
You do not need to re-assign users to individual hubs.
When to Use Hubs vs. Separate Portals #
- Same client, multiple ongoing projects — Use hubs under one portal
- Different clients, or separate billing relationships — Use separate portals
- One client, one project — A single portal is sufficient — no hubs needed
- One client, multiple departments needing separate conversations — Use hubs
