Give each customer their documents through a controlled access route.
A hidden website link is not enough when documents belong to particular customers. ImbaHub can specify and develop a focused document portal with controlled downloads. Document types, identity, customer relationships and operating responsibilities determine the solution. This is a separate development scope, rather than a promised standard Imba CMS feature.
- Identity
Who is requesting the file?
- Customer relationship
Does this person have access to this customer's material?
- Delivery
Permitted requests receive the right file; other requests receive a controlled refusal.
A document listing does not replace checks at download time.
The button disappears after revocation, but the old file link works. Accepted?
Not if the requirement is to stop future file access. Test the actual request and the agreed lifetime of shared links.
Define who can do what with each document
Start with one limited document workflow. Identify who may invite a user, attach them to a customer account, publish a file and revoke access. Being logged in must not automatically expose every customer's material.
Fictional example: two contract customers each need their own delivery specification. An administrator publishes each document against the correct customer relationship. The brief must also cover contacts who change employer and contracts that end. Use synthetic files during development.
Protect the download route as well as the page
The access model needs to cover listings, metadata, previews and the actual download. Hiding a button or discouraging indexing does not protect a file that remains available at a public address.
We review identity, storage, delivery and any temporary download links together. If a link remains valid for a limited period, that limitation must be compatible with the revocation requirement. Operational records should provide useful traceability without unnecessarily copying document contents or secret links.
| Decision | Requirement to define | Acceptance exercise |
|---|---|---|
| Customer relationship | Which account owns this document? | Customer B cannot fetch customer A's test file |
| Role | Who can share and who can read? | Readers cannot grant themselves more access |
| File delivery | Where is access decided? | Direct file requests are checked |
| Revocation | When must a change take effect? | An existing session and an old link are tested |
| Operations | Who reviews accounts and failures? | An owner can trace and resolve the exception |
Build a usable first workflow that can be tested
An initial delivery can cover invitation, sign-in, a document list, downloading and revocation for one document type. We define expired sessions, missing access and a support route so customers can understand what to do next.
Test the intended customer, another customer, an anonymous request and a revoked user. Testing takes place within an agreed environment and permission boundary. Particularly sensitive material requires its own risk assessment and suitable operating arrangements; it is not needed for an initial scoping conversation.
Hand over responsibilities and limits
Handover needs to cover account administration, storage, operational records, updates, restoration and incident contact. Successful normal sign-in does not establish that the access model is complete. Customer relationships and storage changes need ongoing attention.
Removing portal access cannot ordinarily recall a copy already downloaded to someone's device. Make that limit clear in the brief and user information. We propose scope and price after reviewing the actual document workflow.
Sources and further reading
Questions, answered
Can noindex protect private files?
No. Indexing instructions are not access controls. The file delivery itself needs suitable protection.
Does revocation remove downloaded copies?
Not ordinarily. It can stop future access under the chosen design, but does not automatically erase copies on a recipient's device.