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.
| Decision | What to consider | What to check |
|---|---|---|
| Public information | Static website | Keep it easy to discover |
| Private documents | Authorized retrieval | Check direct requests |
| Customer-specific work | Account-aware application | Test different permissions |
An illustrative business scenario
A US B2B supplier can keep its public catalog separate from customer-specific documents and account workflows.
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.