# Permission model The permission model defines how ownership, access, and reuse rights are controlled within the Interoperable Asset Store. It ensures that only authorized users can register assets, approve reuse, and decrypt source files, while all actions remain verifiable through on-chain records. The owner of a parent asset has full control over its reuse. Only the owner can approve or reject reuse proposals submitted by other studios. Until approval is granted, the integrating studio cannot access the encrypted IPFS files associated with the parent asset. This protects the creator’s intellectual property and ensures that no asset can be integrated into a game without explicit permission. Once a proposal is approved, the protocol grants the integrating studio permission to decrypt the asset files through wallet-based access. This access is tied directly to the approval event and cannot be transferred or extended without another approval. Approved studios may then mint a child asset, which completes the permission sequence for reuse. Child assets cannot be reused or listed for reuse, and no additional permissions can be derived from them. All reuse must originate from the original parent asset, keeping the permission hierarchy simple and predictable. All approvals, rejections, and related events are stored on-chain, allowing any participant in the ecosystem to verify the status and history of a parent asset and its child assets. This creates a transparent permission system that protects creators, supports studios, and keeps asset integration fully accountable. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://infinity-games.gitbook.io/infinity-games-docs/interoperable-asset-store/architecture/permission-model.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.