Testing Permissions
Permission testing verifies that each identity can perform only allowed actions on allowed resources, including through direct requests. Build a role-and-resource matrix and test both permitted and forbidden cases at the backend boundary.
What You Will Be Able to Decide
- Explain testing permissions in product and business terms.
- Apply this decision: Build a role-and-resource matrix and test both permitted and forbidden cases at the backend boundary.
- Recognise this material risk: the interface hides an action but the API still allows it for another user's resource.
- Ask a consultant for evidence rather than reassurance.
A founder needs evidence that the product works beyond the most convenient demonstration path.
Permission testing verifies that each identity can perform only allowed actions on allowed resources, including through direct requests.
A consultant can recommend and implement the technical approach. The founder still needs to decide which outcome matters, which risk is acceptable, and what evidence is sufficient.
The Founder Situation
A founder needs evidence that the product works beyond the most convenient demonstration path.
The immediate question is testing permissions. The technical label matters only because it changes a product decision, a responsibility, or the evidence required before launch.
Technical term
Testing Permissions
Permission testing verifies that each identity can perform only allowed actions on allowed resources, including through direct requests.
Treat it like a clause in a commercial agreement: its value comes from making expectations and consequences clear, not from sounding formal.
What Matters in Practice
Start with the product consequence, then choose the simplest technical treatment that protects it. A longer tool list is not a stronger plan.
For this decision, the useful standard is that the same expected result can be reproduced under normal, invalid, and failure conditions.
- Make the decision explicit: Build a role-and-resource matrix and test both permitted and forbidden cases at the backend boundary.
- Ask what evidence would show that the chosen approach works.
- Name the person or provider responsible when the approach fails.
- Record the result in the test plan and recorded evidence.
A Proportionate Decision
Build a role-and-resource matrix and test both permitted and forbidden cases at the backend boundary.
The principal risk is that the interface hides an action but the api still allows it for another user's resource. This does not require the most expensive possible solution. It requires the consequence to be understood and the control to match it.
- Describe the user or business outcome that must be protected.
- Identify the most credible failure and its consequence.
- Compare the simplest adequate approach with one realistic alternative.
- Set a review point for when the decision may need to change.
Strong Evidence and Weak Reassurance
Warning Signs
- Nobody can explain how testing permissions changes a user or business outcome.
- The proposal does not address this risk: the interface hides an action but the API still allows it for another user's resource.
- The only evidence is a successful demonstration of the easiest path.
- The decision has no named owner, boundary, or review point.
- A provider-specific feature is being mistaken for a permanent product requirement.
Questions to Ask a Consultant
- What decision are we making about testing permissions?
- Which user or business outcome does the recommendation protect?
- How have we reduced or accepted this risk: the interface hides an action but the API still allows it for another user's resource.
- What evidence can I review without relying on the original implementer?
- What is deliberately deferred, and when will it be reconsidered?
- Who owns the accounts, data, documentation, and recovery process?
Key takeaway
Key Takeaway
Permission testing verifies that each identity can perform only allowed actions on allowed resources, including through direct requests. The founder's job is to make the consequence explicit; the consultant's job is to recommend and demonstrate a proportionate implementation.