Structuring digital assets across multiple tiers requires clean file-level permissions. When offering foundational documentation alongside production execution files, the architecture needs to deliver exact assets per tier without cluttering the storefront with multiple product pages.
The Problem
Digital storefronts often route uploaded files globally to every tier by default. If Tier 1 includes only the system guide and Tier 2 includes the full agent schema, a global file setting accidentally sends raw workflow assets to buyers who only requested the guide.
The Setup
Rather than creating fragmented checkout pages, file permissions are scoped directly on each asset row:
System Guide (PDF): Assigned globally across all tiers so every user gets foundational documentation.
Workflow Schema (.rai): Scoped strictly to upper tiers. Removing the entry tier tag prevents raw file delivery to tier 1 buyers.
The Takeaway
In low-code and agentic builds, the execution schema is the core build file. Explicitly scoping variant access on the backend keeps delivery automated, prevents asset leaks, and maintains a single clean storefront URL.
Top comments (0)