Design intent
Make responsibility explicit
Define resource identity, ownership and hierarchy, then decide which roles or custom permissions apply and where enforcement occurs. Keep resource creation and deletion aligned with the authorization model.
Features / Resource modelling
Custom Resources
Represent application-specific objects as resources so roles and access rules can be attached to the thing being protected.
Explore the design intent, review practical decisions and validate exact behavior against your deployed configuration.
Why it matters
Make the policy understandable before you automate it.
If authorization only understands generic application-wide roles, teams may resort to hard-coded checks or broad privileges for every resource instance.
Worked scenario
See it in context
A project resource carries explicit memberships; access to one project does not automatically imply access to every project in the tenant.
Boundary to verify
Do not rely on interface alone
Confirm enforcement at the relevant server, API, resource or operational decision point. A hidden button or an informative dashboard is not, by itself, an authorization control.
Practical path
From intent to verified outcome.
Use these stages as a review guide. Exact settings and enforcement points depend on the configured deployment and connected systems.
Define the boundary
Identify the actor, target resource and operation that custom resources is meant to govern.
Configure the policy
Define resource identity, ownership and hierarchy, then decide which roles or custom permissions apply and where enforcement occurs. Keep resource creation and deletion aligned with the authorization model.
Exercise the edge cases
A project resource carries explicit memberships; access to one project does not automatically imply access to every project in the tenant. Also test the path that should be denied, deferred or sent for review.
Review the outcome
Check that the resulting state is understandable and that the decision can be investigated later. For audit-enabled operations, confirm the relevant actor and context are captured.
Before rollout
Questions worth answering.
A capability is easier to operate when ownership, failure behavior and verification are defined upfront.
- Confirm the subject, resource and scope affected by custom resources.
- What is the resource boundary, who owns it, and where must a permission check execute?
- Test the expected path and at least one denied, expired or incomplete path.
- Make ownership, failure handling and review evidence clear before rollout.
This page describes a design approach based on WebFrolic’s documented product model. Verify feature availability and exact behavior in your environment before relying on it for a control requirement.
Related capabilities
Explore what connects to this.
Follow the related areas to understand how this capability fits within identity, access, lifecycle and operations.
Evaluate with your scenario
Start with a concrete workflow.
Share the identities, resource boundary and decision you want to test. The walkthrough can focus on the relevant behavior rather than a generic feature tour.