# Access Control Moving far beyond simple wallet ownership, Functor Network introduces a sophisticated, **programmable access control** layer. Using **dynamic**, **rule-based logic** and **session-based permissions**, developers and users can define granular, context-aware parameters for any onchain operation. This moves security and permissions from a binary "all or nothing" model to one of nuanced, temporary, and **scoped access.** A "[session key](/functor-network-docs/core-concepts/glossary.md#session-key)" can be generated to grant an application or agent a specific set of permissions for a limited time, dramatically enhancing security and user experience. This unlocks a new tier of onchain interactions and primitives: ### **Granular Access Management** Define exactly what actions a third party (like a new DeFi protocol or a gaming application) can perform on your behalf. \ \ \&#xNAN;*For example, approve a protocol to swap a specific token up to a certain amount, but nothing else.* ### **Time-Based and Streaming Approvals** Grant permissions that are only valid for a specific duration or allow for continuous "streaming" of approvals for applications like recurring payments or subscriptions, without needing to sign a new transaction each time. ### **Context-Aware Operations** Set rules that only permit transactions under specific onchain conditions. *For instance, an operation might only be approved if a specific asset’s price is within a certain range or if a DAO governance vote has passed.* --- # 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://functor.gitbook.io/functor-network-docs/use-cases/access-control.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.