# Account Permissions When you start your agent (or change settings later), you will typically sign two types of permissions: *** **1) Token Approvals** Token approvals allow your Sail Account to interact with specific contracts (for example, a yield source or router) using a specific token. Approvals are scoped to a token and spender. They do not give someone control over your wallet. They simply allow smart contracts to move a token under the constraints of your permissions. Approvals are common in DeFi. Sail surfaces them in the UI so you can review what you are signing. *** **2) Agent Permissions (Session Keys)** Session keys are what make Sail feel agentic: you do not need to sign every rebalance, claim, swap, or bridge. Your agent receives a scoped, revocable permission to execute on your behalf. The permission is limited to what you chose in onboarding or personalization (networks, stablecoins, protocols, actions). You can update or revoke these permissions at any time from the app. *** **What You Should Expect to See at Signing Time** Sail shows you the exact permissions you are authorizing before you sign, including what the agent can do and where it can do it. This is intentional: you should be able to verify the scope before granting access. *** **Where to Review or Change Permissions** Open the Profile Menu, then Personalization, to review and update what your agent is allowed to do. If you expand scope (new protocols or actions), Sail will request new permissions. If you reduce scope, Sail will stop using anything outside your updated rules. --- # 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://docs.sail.money/security/permissions-and-keys/quickstart.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.