Write expected decisions before testing
Create two separate test customers with one file each and an administrator. Specify which roles can view names, open previews, download and share. Include a user who has no customer relationship at all.
In the fictional exercise, customer A may read A's delivery sheet and customer B may read only B's. Distinguish intentionally permitted sharing from an access failure. Also agree how quickly revocation must affect sessions and temporary links.
Exercise the file route outside the listing
Open an authorised test file, identify its actual delivery route and try it with the right test account, the wrong account and no login. Test separate metadata or preview routes too. Change only test identifiers within the authorised sample.
A hidden button proves only that the interface changed. Establish whether a direct request still delivers the file. A hard-to-guess filename alone does not establish that customer boundaries are enforced.
| Exercise | Expected decision | Evidence to record |
|---|---|---|
| Right customer, valid permission | Intended download allowed | Correct file and version |
| Other test customer | No unauthorised file or metadata | Controlled refusal on every delivery route |
| Anonymous request | No unauthorised delivery | No file through its direct address |
| Revoked customer relationship | Agreed restriction takes effect | Existing session and new request |
| Previously created sharing link | Follows the agreed revocation rule | Actual result and any remaining lifetime |
Revoke access while the session stays open
Leave the test user's portal open and remove permission through the intended administration process. Request a fresh listing, preview and download in that same session. Repeat from a second browser session if concurrent sessions are supported.
Then try a sharing link created earlier. If it remains usable until expiry, that must match the requirement and be documented. If immediate blocking is required but the architecture cannot provide it, resolve the design or requirement before acceptance.
State what the result establishes
Check that the customer understands the refusal and has a support route without errors revealing another account's files. Confirm that an operator can trace the test event without placing secret links or document content in broadly accessible logs.
Record environment, date, roles, document version, observation and retest. A passing sample is not a complete security certification. Revoking portal permission does not erase downloaded copies; their handling is a separate issue.