imbahub
Menu +
EN
Talk to us
IMBAHUB / Knowledge & guides

When does a static website need a separate private portal?

Public content and private customer tasks have different requirements. Treat authentication and authorised data access as application responsibilities rather than hidden public-page features.

Compare the decision, not just the headline
  1. Public information

    Static website. Keep it easy to discover.

  2. Private documents

    Authorised retrieval. Check direct requests.

  3. Customer-specific work

    Account-aware application. Test different permissions.

Public content and private customer tasks have different requirements. Treat authentication and authorised data access as application responsibilities rather than hidden public-page features.

Try this before deciding

Create two controlled test accounts with different permissions. Check direct document access, signed-out access and revoked access. Use non-sensitive fixtures and verify the authorisation boundary, not just whether the menu item disappears.

Draw the boundary around the protected information

List which material is public, which requires an account and which is specific to an individual customer. Hiding a link or omitting a page from search does not create access control. A static public website can sit alongside a separate portal, but the portal needs a system that decides what each signed-in user may retrieve.

Buy the private workflow as its own scope

Define account creation, access changes, document retrieval and support. Include what happens when a user leaves or a document is replaced. Do not accept a mock sign-in screen as proof that data access is protected. Keeping the public marketing site simple may be sensible, while the private application receives the implementation and review its tasks require.

A practical check before you buy

Create two controlled test accounts with different permissions. Check direct document access, signed-out access and revoked access. Use non-sensitive fixtures and verify the authorisation boundary, not just whether the menu item disappears.

DecisionWhat to considerWhat to check
Public informationStatic websiteKeep it easy to discover
Private documentsAuthorised retrievalCheck direct requests
Customer-specific workAccount-aware applicationTest different permissions

An illustrative business scenario

A UK membership body can keep public programme information separate from documents available only to authorised members.

This is an illustrative scenario, not a claim about an ImbaHub client or a promised result.

Discuss the right scope with ImbaHub

ImbaHub builds fast static websites with Astro, with editing through Imba CMS and Imba Builder. Start with the customer task described in this guide and ask which content, integrations and ongoing responsibilities your project needs. Agree the scope before comparing the investment.

Sources and further reading

Questions, answered

Is a hidden or noindex page a private customer portal?

No. Those measures do not establish authorisation. Protected information needs effective access checks in the system that serves it.

IMBAHUB

What would you like to make possible?

Public content and private customer tasks have different requirements. Treat authentication and authorised data access as application responsibilities rather than hidden public-page features.

Talk to us
Product interface set to English in an isolated environment with fictional English demo content.

Product interface set to English in an isolated environment with fictional English demo content.