Testing Portal Permissions Before Launch
Permission testing should include actions a user is not allowed to perform. A successful login and a visible project prove only part of the access model.

Test across separate accounts
Create sample projects for two different customers and a staff account. Try viewing, editing, commenting and downloading files with each role. Include direct requests to record addresses rather than relying only on navigation that hides restricted links.
Practical checklist
- Test anonymous access.
- Test access to another customer's project.
- Test restricted administrative actions.
- Repeat checks for files and comments.
How to review the result
Record the expected result for each role and action before running the tests. A denied request is a successful test when the permission model requires it.